[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <98d01db3-3eba-0731-0dd9-4310ed293bd6@tuxon.dev>
Date: Tue, 15 Aug 2023 08:19:44 +0300
From: claudiu beznea <claudiu.beznea@...on.dev>
To: Mihai.Sain@...rochip.com, robh+dt@...nel.org,
krzysztof.kozlowski+dt@...aro.org, conor+dt@...nel.org,
Nicolas.Ferre@...rochip.com, Cristian.Birsan@...rochip.com,
alexandre.belloni@...tlin.com, andre.przywara@....com,
Jerry.Ray@...rochip.com, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Cc: Andrei.Simion@...rochip.com
Subject: Re: [PATCH] ARM: dts: at91: sama5d29_curiosity: Add device tree for
sama5d29_curiosity board
Hi, Mihai,
On 8/10/23 09:47, Mihai.Sain@...rochip.com wrote:
>> +&i2s0 {
>> + pinctrl-names = "default";
>> + pinctrl-0 = <&pinctrl_i2s0_default>;
>> + status = "okay";
> I see no sound bindings on DT. Is there any reason for having this here?
> # i2s0 bus is wired to RPi 40-pin connector. I want to have this node and its pinctrl here.
> # i2c1, flx4-spi, pwm0, uart1 are also wired to Rpi connector, and are defined here.
> # The same logic we apply also for mikroBUS sockets: i2c, pwm, spi and uart nodes are defined here.
>
Can you use it (either with user space tools or other kernel consumers) w/o
additional device tree bindings?
Powered by blists - more mailing lists