From: sashiko-bot@kernel.org
To: "John Madieu" <john.madieu.xa@bp.renesas.com>
Cc: conor+dt@kernel.org, wsa+renesas@sang-engineering.com,
robh@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v4 7/8] arm64: dts: renesas: rzg3e-smarc-som: add audio pinmux definitions
Date: Mon, 25 May 2026 12:28:42 +0000 [thread overview]
Message-ID: <20260525122843.10D481F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260525110603.4018170-8-john.madieu.xa@bp.renesas.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The device tree node `sound_clk` uses an underscore instead of a hyphen, violating naming conventions.
--
commit d0daff3ab55c18eb7640dc053ae11aaa9c14d357
Author: John Madieu <john.madieu.xa@bp.renesas.com>
arm64: dts: renesas: rzg3e-smarc-som: add audio pinmux definitions
This commit adds pinmux definitions for the SSI3 and SSI4 audio interfaces
on the RZ/G3E SMARC SoM. It configures the sound clock pins and the sound
data and control pins.
> diff --git a/arch/arm64/boot/dts/renesas/rzg3e-smarc-som.dtsi b/arch/arm64/boot/dts/renesas/rzg3e-smarc-som.dtsi
> index 493f6783d5833..f4532a06cc31d 100644
> --- a/arch/arm64/boot/dts/renesas/rzg3e-smarc-som.dtsi
> +++ b/arch/arm64/boot/dts/renesas/rzg3e-smarc-som.dtsi
[ ... ]
> @@ -353,6 +353,18 @@ sd2-pwen {
> };
> };
>
> + sound_clk_pins: sound_clk {
[Severity: Low]
This isn't a bug, but should this node name use a hyphen instead of an
underscore?
According to the Devicetree specification, node names should use hyphens
rather than underscores to separate words. Using an underscore here might
trigger compiler warnings for node_name_chars_strict. Renaming the node to
sound-clk would align with standard DT conventions.
> + pinmux = <RZG3E_PORT_PINMUX(4, 2, 8)>, /* AUDIO_CLKB */
> + <RZG3E_PORT_PINMUX(4, 3, 8)>; /* AUDIO_CLKC */
> + };
> +
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260525110603.4018170-1-john.madieu.xa@bp.renesas.com?part=7
next prev parent reply other threads:[~2026-05-25 12:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-25 11:05 [PATCH v4 0/8] arm64: dts: renesas: Add RZ/G3E audio enablement John Madieu
2026-05-25 11:05 ` [PATCH v4 1/8] dt-bindings: clock: renesas: Add audio clock inputs for RZ/V2H family John Madieu
2026-05-25 11:19 ` sashiko-bot
2026-05-25 16:56 ` Conor Dooley
2026-05-25 11:05 ` [PATCH v4 2/8] clk: renesas: r9a09g047: Add audio clock and reset support John Madieu
2026-05-25 11:05 ` [PATCH v4 3/8] arm64: dts: renesas: rzv2h: Add audio clock inputs John Madieu
2026-05-25 11:41 ` sashiko-bot
2026-05-25 11:05 ` [PATCH v4 4/8] arm64: dts: renesas: r9a09g047: Add RZ/G3E Sound support John Madieu
2026-05-25 11:06 ` [PATCH v4 5/8] arm64: dts: renesas: rzg3e-smarc-som: Add Versa3 clock generator John Madieu
2026-05-25 11:06 ` [PATCH v4 6/8] arm64: dts: renesas: rzg3e-smarc-som: Add I2C1 support John Madieu
2026-05-25 11:06 ` [PATCH v4 7/8] arm64: dts: renesas: rzg3e-smarc-som: add audio pinmux definitions John Madieu
2026-05-25 12:28 ` sashiko-bot [this message]
2026-05-25 11:06 ` [PATCH v4 8/8] arm64: dts: renesas: r9a09g047e57-smarc: add DA7212 audio codec support John Madieu
2026-05-25 12:49 ` sashiko-bot
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=20260525122843.10D481F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=john.madieu.xa@bp.renesas.com \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=wsa+renesas@sang-engineering.com \
/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