From: Mark Brown <broonie@kernel.org>
To: alsa-devel@alsa-project.org, srinivas.kandagatla@linaro.org
Cc: perex@perex.cz, tiwai@suse.com, linux-sound@vger.kernel.org,
linux-kernel@vger.kernel.org, johan+linaro@kernel.org
Subject: Re: [PATCH 0/2] ASoC: qcom: Limit Digital gains on speaker
Date: Tue, 05 Dec 2023 13:11:50 +0000 [thread overview]
Message-ID: <170178191007.32878.14836362585756098271.b4-ty@kernel.org> (raw)
In-Reply-To: <20231204124736.132185-1-srinivas.kandagatla@linaro.org>
On Mon, 04 Dec 2023 12:47:34 +0000, srinivas.kandagatla@linaro.org wrote:
> Limit the speaker digital gains to 0dB so that the users will not damage them.
> Currently there is a limit in UCM, but this does not stop the user form
> changing the digital gains from command line. So limit this in driver
> which makes the speakers more safer without active speaker protection in
> place.
>
> Apart from this there is also a range check fix in snd_soc_limit_volume
> to allow setting this limit correctly.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/2] ASoC: ops: add correct range check for limiting volume
commit: fb9ad24485087e0f00d84bee7a5914640b2b9024
[2/2] ASoC: qcom: sc8280xp: Limit speaker digital volumes
commit: 716d4e5373e9d1ae993485ab2e3b893bf7104fb1
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
Thanks,
Mark
next prev parent reply other threads:[~2023-12-05 13:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-04 12:47 srinivas.kandagatla
2023-12-04 12:47 ` [PATCH 1/2] ASoC: ops: add correct range check for limiting volume srinivas.kandagatla
2023-12-04 13:51 ` Johan Hovold
2023-12-04 12:47 ` [PATCH 2/2] ASoC: qcom: sc8280xp: Limit speaker digital volumes srinivas.kandagatla
2023-12-04 13:54 ` Johan Hovold
2023-12-05 13:11 ` Mark Brown [this message]
2023-12-11 8:08 ` [PATCH 0/2] ASoC: qcom: Limit Digital gains on speaker Johan Hovold
2023-12-11 12:40 ` Greg Kroah-Hartman
2023-12-11 12:54 ` Greg Kroah-Hartman
2023-12-11 13:29 ` Johan Hovold
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=170178191007.32878.14836362585756098271.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=johan+linaro@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=srinivas.kandagatla@linaro.org \
--cc=tiwai@suse.com \
/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
all inboxes | Powered by JetHome®