[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <165583076931.271995.9857794745310978104.b4-ty@kernel.org>
Date: Tue, 21 Jun 2022 17:59:29 +0100
From: Mark Brown <broonie@...nel.org>
To: judyhsiao@...omium.org, heiko@...ech.de
Cc: perex@...ex.cz, linux-kernel@...r.kernel.org, wenst@...omium.org,
Liam Girdwood <lgirdwood@...il.com>,
linux-rockchip@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org, briannorris@...omium.org,
robh+dt@...nel.org, alsa-devel@...a-project.org
Subject: Re: (subset) [PATCH v4 0/3] ASoC: rockchip: i2s: switch BCLK to GPIO
On Sun, 19 Jun 2022 09:53:21 +0000, Judy Hsiao wrote:
> The patches series is to fix the unexpected large DC output
> voltage of Max98357a that burns the speakers on the rockchip
> platform when BCLK and SD_MODE are ON but LRCLK is OFF.
>
> Changes Since V4:
> -- Fix indentation in the driver. (Align parameters with the parenthesis
> placement.)
> -- Fix incorrect return type of rockchip_snd_rxctrl.
> Changes Since V3:
> -- Fix indentation in the documentation.
> -- Put pinctrl-1 right after pinctrl-0 in dtsi.
> -- Fix indentation in the driver.
> -- Remove unnecessary dev_dbg() in the driver.
> Changes Since V2:
> -- Add documents of i2s pinctrl-names.
> -- Fix dtsi syntax error.
> -- Include the dtsi change and the driver change in the same series.
> -- Ensure that driver gets both bclk_on and bclk_off states before using them.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/3] ASoC: rockchip: i2s: switch BCLK to GPIO
commit: 44f362c2cc6dd0c5e3cb499c4fb4ed45b63a6196
[3/3] ASoC: dt-bindings: rockchip: Document pinctrl-names for i2s
(no commit info)
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