[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <169748713689.982818.14313668807415400753.b4-ty@sntech.de>
Date: Mon, 16 Oct 2023 22:12:18 +0200
From: Heiko Stuebner <heiko@...ech.de>
To: Christopher Obbard <chris.obbard@...labora.com>,
linux-rockchip@...ts.infradead.org
Cc: Heiko Stuebner <heiko@...ech.de>,
Judy Hsiao <judyhsiao@...omium.org>,
linux-arm-kernel@...ts.infradead.org,
Brian Norris <briannorris@...omium.org>,
Rob Herring <robh+dt@...nel.org>,
Caleb Connolly <kc@...tmarketos.org>,
Yogesh Hegde <yogi.kernel@...il.com>,
Arnaud Ferraris <arnaud.ferraris@...labora.com>,
FUKAUMI Naoki <naoki@...xa.com>,
Corentin Labbe <clabbe@...libre.com>,
devicetree@...r.kernel.org, Johan Jonker <jbx6244@...il.com>,
Conor Dooley <conor+dt@...nel.org>,
linux-kernel@...r.kernel.org,
Rick Wertenbroek <rick.wertenbroek@...il.com>,
kernel@...labora.com,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Jagan Teki <jagan@...rulasolutions.com>
Subject: Re: [PATCH v1 0/2] Fix i2s0 pin conflict on ROCK Pi 4 RK3399 boards
On Fri, 13 Oct 2023 12:47:25 +0100, Christopher Obbard wrote:
> i2s0 fails to probe on my Radxa ROCK 4SE and ROCK Pi 4B boards with:
>
> rockchip-pinctrl pinctrl: pin gpio3-29 already requested by leds; cannot claim for ff880000.i2s
> rockchip-pinctrl pinctrl: pin-125 (ff880000.i2s) status -22
> rockchip-pinctrl pinctrl: could not request pin 125 (gpio3-29) from group i2s0-8ch-bus-bclk-off on device rockchip-pinctrl
> rockchip-i2s ff880000.i2s: Error applying setting, reverse things back
> rockchip-i2s ff880000.i2s: bclk disable failed -22
>
> [...]
Applied, thanks!
[1/2] arm64: dts: rockchip: Add i2s0-2ch-bus-bclk-off pins to RK3399
commit: 3975e72b164dc8347a28dd0d5f11b346af534635
[2/2] arm64: dts: rockchip: Fix i2s0 pin conflict on ROCK Pi 4 boards
commit: 8cd79b729e746cb167f1563d015a93fc0a079899
Best regards,
--
Heiko Stuebner <heiko@...ech.de>
Powered by blists - more mailing lists