From: claudiu beznea <claudiu.beznea@tuxon.dev>
To: Mihai.Sain@microchip.com, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
Nicolas.Ferre@microchip.com, Cristian.Birsan@microchip.com,
alexandre.belloni@bootlin.com, andre.przywara@arm.com,
Jerry.Ray@microchip.com, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: Andrei.Simion@microchip.com
Subject: Re: [PATCH] ARM: dts: at91: sama5d29_curiosity: Add device tree for sama5d29_curiosity board
Date: Tue, 15 Aug 2023 08:19:44 +0300 [thread overview]
Message-ID: <98d01db3-3eba-0731-0dd9-4310ed293bd6@tuxon.dev> (raw)
In-Reply-To: <PH8PR11MB6804E49B5946F4A9D60837E18213A@PH8PR11MB6804.namprd11.prod.outlook.com>
Hi, Mihai,
On 8/10/23 09:47, Mihai.Sain@microchip.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?
next prev parent reply other threads:[~2023-08-15 5:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-04 10:10 Mihai Sain
2023-08-04 16:28 ` Conor Dooley
2023-08-09 4:56 ` claudiu beznea
2023-08-10 6:47 ` Mihai.Sain
2023-08-15 5:19 ` claudiu beznea [this message]
2023-08-16 9:05 ` Mihai.Sain
2023-08-16 14:38 ` Conor Dooley
2023-08-17 5:31 ` claudiu beznea
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=98d01db3-3eba-0731-0dd9-4310ed293bd6@tuxon.dev \
--to=claudiu.beznea@tuxon.dev \
--cc=Andrei.Simion@microchip.com \
--cc=Cristian.Birsan@microchip.com \
--cc=Jerry.Ray@microchip.com \
--cc=Mihai.Sain@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andre.przywara@arm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®