Skip to content

fix(tlv): revert mute handling fix for MINMAX_MUTE type - #14

Open
deepin-ci-robot wants to merge 1 commit into
masterfrom
backport/fix-tlv-mute-minmax-mute
Open

fix(tlv): revert mute handling fix for MINMAX_MUTE type#14
deepin-ci-robot wants to merge 1 commit into
masterfrom
backport/fix-tlv-mute-minmax-mute

Conversation

@deepin-ci-robot

Copy link
Copy Markdown
Contributor

Problem Before the Change

The previous upstream commit 41039b49 ("snd_tlv_convert_to_dB: Fix mute
handling for MINMAX_MUTE type") introduced a regression: volume values
above the minimum but whose computed dB equals the minimum dB were
incorrectly reported as MUTE. This affects controls using the
SND_CTL_TLVT_DB_MINMAX_MUTE TLV type, where the hardware is muted only
at the lowest hardware volume value (not the lowest dB value).

What This PR Changes

Reverts upstream commit 41039b49, restoring the original
snd_tlv_convert_to_dB() behavior that mutes only when
volume <= rangemin (or the range is empty) for MINMAX_MUTE type, and
reports the proper interpolated dB value for all other volume levels.

Problem Solved After the Change

Volume values above the minimum now report correct dB values instead of
being incorrectly muted, matching the expected hardware behavior for
SND_CTL_TLVT_DB_MINMAX_MUTE controls.

Changes

  • Add debian/patches/fix-tlv-revert-mute-handling-minmax-mute.patch
  • Modify debian/patches/series
  • Modify debian/changelog

Upstream

alsa-project/alsa-lib@96f23dd

Generated-By: glm-5.2
Co-Authored-By: deepin-ci-robot packages@deepin.org

This reverts commit 41039b49ad3e20506134864028c77aeaba4c0d51.

SND_CTL_TLVT_DB_MINMAX_MUTE means that the hardware is muted on lowest
hardware volume value (not on lowest dB value).

Changes:
  - Add debian/patches/fix-tlv-revert-mute-handling-minmax-mute.patch
  - Modify debian/patches/series
  - Modify debian/changelog

Upstream: alsa-project/alsa-lib@96f23dd

Generated-By: glm-5.2
Co-Authored-By: deepin-ci-robot <packages@deepin.org>
@deepin-ci-robot

Copy link
Copy Markdown
Contributor Author

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign zeno-sole for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@github-actions

Copy link
Copy Markdown

TAG Bot

TAG: 1.2.15.3-1deepin8
EXISTED: no
DISTRIBUTION: unstable

@qaqland

qaqland commented Aug 13, 2026

Copy link
Copy Markdown
Member

我给上游改错了,上游后来发现并进行了 revert

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants