[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <163364264608.649699.437992626098307061.b4-ty@kernel.org>
Date: Thu, 7 Oct 2021 22:37:31 +0100
From: Mark Brown <broonie@...nel.org>
To: Nicolas Frattaroli <frattaroli.nicolas@...il.com>
Cc: Mark Brown <broonie@...nel.org>, devicetree@...r.kernel.org,
Philipp Zabel <p.zabel@...gutronix.de>,
linux-rockchip@...ts.infradead.org,
Heiko Stuebner <heiko@...ech.de>, linux-kernel@...r.kernel.org,
alsa-devel@...a-project.org, Jaroslav Kysela <perex@...ex.cz>,
Takashi Iwai <tiwai@...e.com>,
Liam Girdwood <lgirdwood@...il.com>,
linux-arm-kernel@...ts.infradead.org,
Rob Herring <robh+dt@...nel.org>
Subject: Re: (subset) [PATCH v5 0/4] Rockchip I2S/TDM controller
On Fri, 1 Oct 2021 19:15:27 +0200, Nicolas Frattaroli wrote:
> this is version 5 of the I2S/TDM driver patchset. A big thanks
> to everyone who has provided their valuable feedback so far.
>
> Changes in v5:
> driver:
> - change comment style of the first comment to C++ style
> - make refcount non-atomic, as it's only ever used inside
> a spinlock
> - use newer SND_SOC_DAIFMT_CB* defines
> - change ternary statements to if/else conditions
> - make _clk_compensation_put return 1 if clock changed
> - implement set_bclk_ratio callback
> - always set half frame sync mode in TDM mode
> - automatically enable mclk-calibrate mode when the clocks for
> it are specified in the device tree
> bindings:
> - add Reviewed-by: Rob Herring
> - drop rockchip,frame-width property (done by set_bclk_ratio)
> - drop rockchip,fsync-half-frame property
> - drop rockchip,mclk-calibrate property
> dts:
> - drop empty codec block from Quartz64 device tree
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/4] ASoC: rockchip: add support for i2s-tdm controller
commit: 081068fd641403994f0505e6b91e021d3925f348
[2/4] ASoC: dt-bindings: rockchip: add i2s-tdm bindings
commit: 510f1c133aedcf69847786c14681e7f7bf4db778
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