From: "Péter Ujfalusi" <peter.ujfalusi@linux.intel.com>
To: lgirdwood@gmail.com, broonie@kernel.org
Cc: linux-sound@vger.kernel.org, kai.vehmanen@linux.intel.com,
seppo.ingalsuo@linux.intel.com, stable@vger.kernel.org,
niranjan.hy@ti.com, ckeepax@opensource.cirrus.com
Subject: Re: [PATCH] ASoC: soc-ops: Correct the max value for clamp in soc_mixer_reg_to_ctl()
Date: Wed, 17 Dec 2025 14:17:00 +0200 [thread overview]
Message-ID: <404fca17-4505-4b7f-8e2a-ed75a8fac1d0@linux.intel.com> (raw)
In-Reply-To: <20251217120623.16620-1-peter.ujfalusi@linux.intel.com>
On 17/12/2025 14:06, Peter Ujfalusi wrote:
> In 'normal' controls the mc->min is the minimum value the register can
> have, the mc->max is the maximum (the steps between are max - min).
>
> SX types are defined differently: mc->min is the minimum value and the
> mc->max is the steps.
>
> The max parameter of soc_mixer_reg_to_ctl() is the number of steps in
> either type.
>
> To have correct register value range in clamp the maximum value that needs
> to be used is mc->min + max, which will be equal to mc->max for 'normal'
> controls and mc->min + mc->max for SX ones.
>
> The original clamp broke SX controls and rendered some of them impossible
> to even set, like the cs42l43's Headphone Digital Volume, where the
> min is smaller than the max (min=283, max=229 - 229 steps starting from
when the min is bigger than the max, sorry, will resend with corrected
message
> val 283).
>
> The soc_mixer_ctl_to_reg() correctly uses the max parameter instead of
> mc->max, so storing the value was correct.
>
> Fixes: a0ce874cfaaa ("ASoC: ops: improve snd_soc_get_volsw")
> Cc: stable@vger.kernel.org
> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@linux.intel.com>
> ---
> sound/soc/soc-ops.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/sound/soc/soc-ops.c b/sound/soc/soc-ops.c
> index ce86978c158d..6a18c56a9746 100644
> --- a/sound/soc/soc-ops.c
> +++ b/sound/soc/soc-ops.c
> @@ -148,7 +148,7 @@ static int soc_mixer_reg_to_ctl(struct soc_mixer_control *mc, unsigned int reg_v
> if (mc->sign_bit)
> val = sign_extend32(val, mc->sign_bit);
>
> - val = clamp(val, mc->min, mc->max);
> + val = clamp(val, mc->min, mc->min + max);
> val -= mc->min;
>
> if (mc->invert)
--
Péter
next prev parent reply other threads:[~2025-12-17 12:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-17 12:06 [PATCH] ASoC: soc-ops: Correct the max value for clamp in soc_mixer_reg_to_ctl() Peter Ujfalusi
2025-12-17 12:16 ` Mark Brown
2025-12-17 12:20 ` Péter Ujfalusi
2025-12-17 12:36 ` Richard Fitzgerald
2025-12-17 12:38 ` Péter Ujfalusi
2025-12-17 12:40 ` Richard Fitzgerald
2025-12-17 12:44 ` Mark Brown
2025-12-17 13:01 ` Péter Ujfalusi
2025-12-17 13:16 ` Richard Fitzgerald
2025-12-17 13:54 ` Péter Ujfalusi
2025-12-17 13:56 ` Mark Brown
2025-12-17 13:59 ` Péter Ujfalusi
2025-12-17 14:00 ` Mark Brown
2025-12-17 14:19 ` Péter Ujfalusi
2025-12-17 14:22 ` Mark Brown
2025-12-17 13:18 ` Mark Brown
2025-12-17 12:17 ` Péter Ujfalusi [this message]
2025-12-17 12:47 ` Charles Keepax
2025-12-17 13:13 ` Péter Ujfalusi
2025-12-17 13:42 ` Charles Keepax
2025-12-17 14:31 ` Péter Ujfalusi
2025-12-17 15:00 ` Charles Keepax
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=404fca17-4505-4b7f-8e2a-ed75a8fac1d0@linux.intel.com \
--to=peter.ujfalusi@linux.intel.com \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=kai.vehmanen@linux.intel.com \
--cc=lgirdwood@gmail.com \
--cc=linux-sound@vger.kernel.org \
--cc=niranjan.hy@ti.com \
--cc=seppo.ingalsuo@linux.intel.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