From: "Troy Mitchell" <troy.mitchell@linux.spacemit.com>
To: "Han Gao" <gaohan@iscas.ac.cn>,
"Linus Walleij" <linusw@kernel.org>,
"Yixun Lan" <dlan@kernel.org>,
"Hendrik Hamerlinck" <hendrik.hamerlinck@hammernet.be>,
"Anand Moon" <linux.amoon@gmail.com>,
"Junhui Liu" <junhui.liu@pigmoral.tech>,
"Troy Mitchell" <troy.mitchell@linux.spacemit.com>
Cc: <linux-gpio@vger.kernel.org>, <linux-riscv@lists.infradead.org>,
<spacemit@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
"Han Gao" <rabenda.cn@gmail.com>
Subject: Re: [PATCH] pinctrl: spacemit: fix NULL check in spacemit_pin_set_config
Date: Wed, 20 May 2026 14:19:03 +0800 [thread overview]
Message-ID: <DINAAUZDL8PS.3KJXPTIHPXQQY@linux.spacemit.com> (raw)
In-Reply-To: <20260519164007.122574-1-gaohan@iscas.ac.cn>
On Wed May 20, 2026 at 12:40 AM CST, Han Gao wrote:
> spacemit_pin_set_config() looks up the per-pin descriptor with
> spacemit_get_pin() then checks the wrong variable for failure:
>
> const struct spacemit_pin *spin = spacemit_get_pin(pctrl, pin);
> ...
> if (!pin)
> return -EINVAL;
>
> reg = spacemit_pin_to_reg(pctrl, spin->pin);
>
> pin is an unsigned int pin id, where 0 (GPIO_0 / gmac0_rxdv on K3) is a
> valid pin, so rejecting it here drops the PAD config write for the first
> pin of every group. On K3 Pico-ITX the GMAC RGMII group lists pin 0 as
> its first entry, so its drive-strength / bias configuration was silently
> ignored.
>
> The intended guard is against spacemit_get_pin() returning NULL when the
> pin id isn't in the SoC's pin table. Check spin instead, which both
> restores PAD setup for pin 0 and prevents a NULL deref on spin->pin.
>
> Fixes: a83c29e1d145 ("pinctrl: spacemit: add support for SpacemiT K1 SoC")
> Signed-off-by: Han Gao <gaohan@iscas.ac.cn>
Thanks.
Reviewed-by: Troy Mitchell <troy.mitchell@linux.spacemit.com>
next prev parent reply other threads:[~2026-05-20 6:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 16:40 Han Gao
2026-05-19 23:21 ` Yixun Lan
2026-05-25 8:48 ` Linus Walleij
2026-05-25 13:16 ` Yixun Lan
2026-05-20 6:19 ` Troy Mitchell [this message]
2026-05-25 8:47 ` Linus Walleij
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=DINAAUZDL8PS.3KJXPTIHPXQQY@linux.spacemit.com \
--to=troy.mitchell@linux.spacemit.com \
--cc=dlan@kernel.org \
--cc=gaohan@iscas.ac.cn \
--cc=hendrik.hamerlinck@hammernet.be \
--cc=junhui.liu@pigmoral.tech \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux.amoon@gmail.com \
--cc=rabenda.cn@gmail.com \
--cc=spacemit@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
Powered by JetHome