[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <163447061131.1864024.8259786717418291207.b4-ty@kernel.org>
Date: Sun, 17 Oct 2021 12:45:06 +0100
From: Mark Brown <broonie@...nel.org>
To: Nicolas Frattaroli <frattaroli.nicolas@...il.com>
Cc: Mark Brown <broonie@...nel.org>,
Liam Girdwood <lgirdwood@...il.com>,
Rob Herring <robh+dt@...nel.org>,
Philipp Zabel <p.zabel@...gutronix.de>,
linux-rockchip@...ts.infradead.org, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
Jaroslav Kysela <perex@...ex.cz>, alsa-devel@...a-project.org,
Heiko Stuebner <heiko@...ech.de>, linux-kernel@...r.kernel.org,
Takashi Iwai <tiwai@...e.com>
Subject: Re: (subset) [PATCH 0/4] Getting rid of the reset controller in i2s-tdm
On Sat, 16 Oct 2021 12:53:49 +0200, Nicolas Frattaroli wrote:
> after some discussion with Heiko on IRC, he has admitted to me
> that the rockchip,cru property, and its corresponding half a reset
> controller in the driver, is weighing heavily on his mind.
>
> The background is that if the lrck only uses one clock for both rx
> and tx direction, then according to the downstream driver, the rx
> and tx resets should be asserted at roughly the same time to keep
> things in sync.
>
> [...]
Applied, thanks!
[1/4] ASoC: rockchip: i2s-tdm: Strip out direct CRU use
commit: d6365d0f0a03c1feb28d86dfd192972ddc647013
[2/4] ASoC: dt-bindings: rockchip: i2s-tdm: Drop rockchip,cru property
commit: 4e52cb9e2c22c9d860910794c82461064baadd9f
Best regards,
--
Mark Brown <broonie@...nel.org>
Powered by blists - more mailing lists