From: Marek Vasut <marek.vasut@mailbox.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
Marek Vasut <marek.vasut+renesas@mailbox.org>
Cc: linux-arm-kernel@lists.infradead.org,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Magnus Damm <magnus.damm@gmail.com>,
Rob Herring <robh@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: renesas: sparrow-hawk: Add overlay for WaveShare 2CH CANFD HAT
Date: Tue, 8 Sep 2026 19:02:48 +0200 [thread overview]
Message-ID: <f82ae578-fbe7-4834-bdde-d11e194a507f@mailbox.org> (raw)
In-Reply-To: <CAMuHMdWvLX7OZSkfEBA34wKtnoZ4asB6rWFJiLa=2+=fezqsCA@mail.gmail.com>
On 9/8/26 2:02 PM, Geert Uytterhoeven wrote:
Hello Geert,
>> +&pfc {
>> + msiof0_pins: spi-ws-2ch-canfd0 { /* SPI_0 */
>
> Node name should be "msiof0".
Do we also have to fix up
arch/arm64/boot/dts/renesas/r8a779g3-sparrow-hawk.dts this:
"
755 msiof1_pins: sound {
^^^^^
"
?
But I wonder, shouldn't the DTOs contain unique pinmux node names, which
cannot accidentally overlap with the base DT or other DTO node names ?
>> + groups = "msiof0_clk", "msiof0_txd", "msiof0_rxd";
>> + function = "msiof0";
>> + };
>> +};
>> +
>> +/*
>> + * PWM1 uses PWM1_B pin configuration for pin GP2_13. This conflicts
>> + * with SPI_1 CE_1 signal which is also on pin GP2_13. Disable PWM1
>> + * in case this hat is in use.
>> + */
>> +&pwm1 {
>> + status = "disabled";
>> +};
>
> Please move this node disabling pwm1 to the top, for compatibility
> with dynamic DT overlays.
Could you expand on that a bit ? What difference does the placement of
this node make within the DTSO ? Please pardon my ignorance.
The rest of the review items are addressed in V2.
Thank you for your help!
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2026-09-08 17:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-08 2:56 [PATCH] arm64: dts: renesas: sparrow-hawk: Add overlay for WaveShare 2CH CANFD HAT Marek Vasut
2026-09-08 12:02 ` Geert Uytterhoeven
2026-09-08 17:02 ` Marek Vasut [this message]
2026-09-09 7:56 ` Geert Uytterhoeven
2026-09-09 15:16 ` Marek Vasut
2026-09-09 15:20 ` Geert Uytterhoeven
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=f82ae578-fbe7-4834-bdde-d11e194a507f@mailbox.org \
--to=marek.vasut@mailbox.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=marek.vasut+renesas@mailbox.org \
--cc=robh@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;
as well as URLs for NNTP newsgroup(s).