From: sashiko-bot@kernel.org
To: "Esteban Urrutia" <esteuwu@proton.me>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH 3/3] pinctrl: qcom: Add SM8475 pinctrl driver
Date: Fri, 31 Jul 2026 18:23:40 +0000 [thread overview]
Message-ID: <20260731182340.88CA91F00AC4@smtp.kernel.org> (raw)
In-Reply-To: <20260731-sm8475-tlmm-v1-3-3007a8e4aa62@proton.me>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Duplicate element 'gpio81' in `prng_rosc_groups` array.
--
--- Patch [3]: [PATCH 3/3] pinctrl: qcom: Add SM8475 pinctrl driver ---
commit 69bbbdbf43f15e9fcc85a840c3553ca43e151ad0
Author: Esteban Urrutia <esteuwu@proton.me>
pinctrl: qcom: Add SM8475 pinctrl driver
This commit introduces a new pin controller driver for the Qualcomm SM8475
platform. It separates the SM8475 configurations from the SM8450 driver due
to differences in PLL clock groups.
> diff --git a/drivers/pinctrl/qcom/pinctrl-sm8475.c b/drivers/pinctrl/qcom/pinctrl-sm8475.c
> new file mode 100644
> index 0000000000000..79e2fce11d36d
> --- /dev/null
> +++ b/drivers/pinctrl/qcom/pinctrl-sm8475.c
[ ... ]
> +static const char * const pri_mi2s_groups[] = {
> + "gpio125",
> +};
> +
> +static const char * const prng_rosc_groups[] = {
> + "gpio73", "gpio75", "gpio81", "gpio83", "gpio81",
> +};
[Severity: Low]
This isn't a bug, but it looks like "gpio81" is listed twice in the
prng_rosc_groups array. Was this intentional, or a copy-paste error?
> +
> +static const char * const qdss_cti_groups[] = {
> + "gpio2", "gpio80", "gpio81", "gpio82", "gpio83", "gpio84", "gpio85", "gpio93",
> +};
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260731-sm8475-tlmm-v1-0-3007a8e4aa62@proton.me?part=3
prev parent reply other threads:[~2026-07-31 18:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 18:08 [PATCH 0/3] Pinctrl support for SM8475 Esteban Urrutia via B4 Relay
2026-07-31 18:08 ` [PATCH 1/3] pinctrl: qcom: Commonize pinctrl-sm8450 headers Esteban Urrutia via B4 Relay
2026-07-31 18:08 ` [PATCH 2/3] dt-bindings: pinctrl: qcom,sm8450-tlmm: Add compatible for SM8475 Esteban Urrutia via B4 Relay
2026-07-31 18:08 ` [PATCH 3/3] pinctrl: qcom: Add SM8475 pinctrl driver Esteban Urrutia via B4 Relay
2026-07-31 18:23 ` sashiko-bot [this message]
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=20260731182340.88CA91F00AC4@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=esteuwu@proton.me \
--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