Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: <broonie@kernel.org>
Cc: <lgirdwood@gmail.com>, <johan+linaro@kernel.org>,
	<srinivas.kandagatla@linaro.org>, <marex@denx.de>,
	<linux-sound@vger.kernel.org>, <patches@opensource.cirrus.com>
Subject: Re: [PATCH] ASoC: ops: Revert addition of min whilst checking platform max
Date: Fri, 28 Feb 2025 10:44:01 +0000	[thread overview]
Message-ID: <Z8GTcW8AgaezL8FE@opensource.cirrus.com> (raw)
In-Reply-To: <20250227143513.3283891-1-ckeepax@opensource.cirrus.com>

On Thu, Feb 27, 2025 at 02:35:13PM +0000, Charles Keepax wrote:
> This reverts commit 9bdd10d57a88 ("ASoC: ops: Shift tested values in
> snd_soc_put_volsw() by +min").
> 
> There are two ways the platform_max could be interpreted; the maximum
> register value, or the maximum value the control can be set to. The
> patch moved from treating the value as a control value to a register
> one. When the patch was applied it was technically correct as
> snd_soc_limit_volume() also used the register interpretation. However,
> even then all the other usages treated platform_max as a control
> value, and snd_soc_limit_volume() has since been updated to also
> do so in commit fb9ad24485087 ("ASoC: ops: add correct range
> check for limiting volume"). That patch however, missed updating
> snd_soc_put_volsw() back to the control interpretation. The control
> interpretation makes more sense as limiting is typically done from
> the machine driver, so it is appropriate to use the customer facing
> representation rather than the internal codec representation.
> 

Seems there is also one other case in snd_soc_info_volsw_range
than needs fixed will do a v2 and resend.

Thanks,
Charles

      reply	other threads:[~2025-02-28 10:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-27 14:35 [PATCH] ASoC: ops: Revert addition of min whilst checking platform max Charles Keepax
2025-02-28 10:44 ` Charles Keepax [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=Z8GTcW8AgaezL8FE@opensource.cirrus.com \
    --to=ckeepax@opensource.cirrus.com \
    --cc=broonie@kernel.org \
    --cc=johan+linaro@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-sound@vger.kernel.org \
    --cc=marex@denx.de \
    --cc=patches@opensource.cirrus.com \
    --cc=srinivas.kandagatla@linaro.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