From: Greg KH <gregkh@linuxfoundation.org>
To: Charles Keepax <ckeepax@opensource.cirrus.com>
Cc: stable@vger.kernel.org, broonie@kernel.org, lgirdwood@gmail.com,
niranjan.hy@ti.com, patches@opensource.cirrus.com
Subject: Re: [PATCH] ASoC: ops: fix snd_soc_get_volsw for sx controls
Date: Wed, 11 Feb 2026 16:45:59 +0100 [thread overview]
Message-ID: <2026021111-lecturer-heap-aab2@gregkh> (raw)
In-Reply-To: <20260211152032.1075568-1-ckeepax@opensource.cirrus.com>
On Wed, Feb 11, 2026 at 03:20:32PM +0000, Charles Keepax wrote:
> From: Stefan Binding <sbinding@opensource.cirrus.com>
>
> [ Upstream commit 095d621141826a2841dae85b52c784c147ea99d3 ]
>
> SX controls are currently broken, since the clamp introduced in
> commit a0ce874cfaaa ("ASoC: ops: improve snd_soc_get_volsw") does not
> handle SX controls, for example where the min value in the clamp is
> greater than the max value in the clamp.
>
> Add clamp parameter to prevent clamping in SX controls.
> The nature of SX controls mean that it wraps around 0, with a variable
> number of bits, therefore clamping the value becomes complicated and
> prone to error.
>
> Fixes 35 kunit tests for soc_ops_test_access.
>
> Fixes: a0ce874cfaaa ("ASoC: ops: improve snd_soc_get_volsw")
>
> CC: stable@vger.kernel.org # 6.17
> Co-developed-by: Charles Keepax <ckeepax@opensource.cirrus.com>
> Signed-off-by: Stefan Binding <sbinding@opensource.cirrus.com>
> Tested-by: Peter Ujfalusi <peter.ujfalusi@linux.intel.com>
> Link: https://patch.msgid.link/20251216134938.788625-1-sbinding@opensource.cirrus.com
> Signed-off-by: Mark Brown <broonie@kernel.org>
> Signed-off-by: Charles Keepax <ckeepax@opensource.cirrus.com>
> ---
>
> This is a necessary fix to an earlier change that broke SX ALSA controls
> (see fixes tag), this causes volumes to get set incorrectly on several
> production laptops. It has already been backported to 6.18 stable, however
> seems to have been missed on 6.17. I suspect it was missed due to a
> minor conflict that I have resolved here.
6.17.y is long end-of-life, there is nothing we can do there anymore,
please do not use that kernel tree at this time. Always look at the
front page of kernel.org for the information about what branches are
still under development, and what ones are not.
thanks,
greg k-h
prev parent reply other threads:[~2026-02-11 15:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-11 15:20 [PATCH] ASoC: ops: fix snd_soc_get_volsw for sx controls Charles Keepax
2026-02-11 15:45 ` Greg KH [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026021111-lecturer-heap-aab2@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=lgirdwood@gmail.com \
--cc=niranjan.hy@ti.com \
--cc=patches@opensource.cirrus.com \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox