[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <175563281972.270039.2781752507684682140.b4-ty@kernel.org>
Date: Tue, 19 Aug 2025 20:46:59 +0100
From: Mark Brown <broonie@...nel.org>
To: Srinivas Kandagatla <srini@...nel.org>,
Liam Girdwood <lgirdwood@...il.com>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, Jaroslav Kysela <perex@...ex.cz>,
Takashi Iwai <tiwai@...e.com>, Philipp Zabel <p.zabel@...gutronix.de>,
Linus Walleij <linus.walleij@...aro.org>,
Bartosz Golaszewski <brgl@...ev.pl>,
Mohammad Rafi Shaik <mohammad.rafi.shaik@....qualcomm.com>
Cc: linux-sound@...r.kernel.org, linux-arm-msm@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-gpio@...r.kernel.org, kernel@....qualcomm.com
Subject: Re: [PATCH v5 0/2] Handle shared reset GPIO for WSA883x speakers
On Fri, 15 Aug 2025 22:53:51 +0530, Mohammad Rafi Shaik wrote:
> On some Qualcomm platforms such as QCS6490-RB3Gen2, the multiple
> WSA8830/WSA8835 speakers share a common reset (shutdown) GPIO.
> To handle such cases, use the reset controller framework along with the
> "reset-gpio" driver.
>
> Tested on:
> - QCS6490-RB3Gen2
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/2] ASoC: dt-bindings: qcom,wsa8830: Add reset-gpios for shared line
commit: 126750523eac0ea79df672d9771eb483f7497b16
[2/2] ASoC: codecs: wsa883x: Handle shared reset GPIO for WSA883x speakers
commit: cf65182247761f7993737b710afe8c781699356b
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
Powered by blists - more mailing lists