From: sashiko-bot@kernel.org
To: "Ronald Claveau via B4 Relay"
<devnull+linux-kernel-dev.aliel.fr@kernel.org>
Cc: linux-amlogic@lists.infradead.org, neil.armstrong@linaro.org,
conor+dt@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] arm64: dts: amlogic: t7: Fix pwm_ao_c pinmux definitions
Date: Wed, 13 May 2026 23:44:32 +0000 [thread overview]
Message-ID: <20260513234433.7D0A0C19425@smtp.kernel.org> (raw)
In-Reply-To: <20260512-add-kvim4-sysled-v1-1-7178719a43e7@aliel.fr>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The commit provides an incomplete fix by resolving missing pin group suffixes for `pwm_ao_c` but overlooking identical bugs for `pwm_ao_g`, `pwm_ao_h`, and `pwm_vs` in the same device tree file.
--
commit 45b298237b81cf91a3c02cc08237c80e6356d308
Author: Ronald Claveau <linux-kernel-dev@aliel.fr>
arm64: dts: amlogic: t7: Fix pwm_ao_c pinmux definitions
The pwm_ao_c pin node was incomplete: it was missing the group name
suffix, conflating two distinct pin groups (pwm_ao_c_d and pwm_ao_c_e)
into a single, ambiguous entry.
> diff --git a/arch/arm64/boot/dts/amlogic/amlogic-t7.dtsi b/arch/arm64/boot/dts/amlogic/amlogic-t7.dtsi
> index 7fe72c94ed623..62f6b9baad28b 100644
> --- a/arch/arm64/boot/dts/amlogic/amlogic-t7.dtsi
> +++ b/arch/arm64/boot/dts/amlogic/amlogic-t7.dtsi
> @@ -400,9 +400,17 @@ mux {
> };
> };
>
> - pwm_ao_c_pins: pwm-ao-c {
> + pwm_ao_c_d_pins: pwm-ao-c-d {
> mux {
> - groups = "pwm_ao_c";
> + groups = "pwm_ao_c_d";
Should we also fix the regressions for pwm_ao_g, pwm_ao_h, and pwm_vs in
this commit?
In this same device tree file, pwm_ao_g_pins, pwm_ao_h_pins, and pwm_vs_pins
are defined using the same generic string pattern:
arch/arm64/boot/dts/amlogic/amlogic-t7.dtsi:
pwm_ao_g_pins: pwm-ao-g {
mux {
groups = "pwm_ao_g";
function = "pwm_ao_g";
bias-disable;
};
};
In drivers/pinctrl/meson/pinctrl-amlogic-t7.c, these generic groups do not
exist as valid pin arrays. The driver only defines suffixed variants like
pwm_ao_g_d11, pwm_ao_g_d7, pwm_ao_g_e, pwm_ao_h_d5, pwm_ao_h_d10, pwm_vs_y,
and pwm_vs_h.
If any future or out-of-tree board tries to use these existing nodes, won't
it result in a pinctrl lookup failure at runtime?
> + function = "pwm_ao_c";
> + bias-disable;
> + };
> + };
> +
> + pwm_ao_c_e_pins: pwm-ao-c-e {
> + mux {
> + groups = "pwm_ao_c_e";
> function = "pwm_ao_c";
> bias-disable;
> };
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260512-add-kvim4-sysled-v1-0-7178719a43e7@aliel.fr?part=1
next prev parent reply other threads:[~2026-05-13 23:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 17:47 [PATCH 0/2] Khadas VIM4 PWM status LED support Ronald Claveau via B4 Relay
2026-05-12 17:47 ` [PATCH 1/2] arm64: dts: amlogic: t7: Fix pwm_ao_c pinmux definitions Ronald Claveau via B4 Relay
2026-05-13 8:04 ` Neil Armstrong
2026-05-13 23:44 ` sashiko-bot [this message]
2026-05-12 17:47 ` [PATCH 2/2] arm64: dts: amlogic: t7: khadas-vim4: add PWM-driven status LED Ronald Claveau via B4 Relay
2026-05-13 8:05 ` Neil Armstrong
2026-05-13 10:26 ` Ronald Claveau
2026-05-13 23:51 ` sashiko-bot
2026-05-13 8:29 ` [PATCH 0/2] Khadas VIM4 PWM status LED support Neil Armstrong
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=20260513234433.7D0A0C19425@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=devnull+linux-kernel-dev.aliel.fr@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=neil.armstrong@linaro.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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