From: Jia Wang <wangjia@ultrarisc.com>
To: sashiko-reviews@lists.linux.dev
Cc: Jia Wang via B4 Relay <devnull+wangjia.ultrarisc.com@kernel.org>,
conor+dt@kernel.org, devicetree@vger.kernel.org,
robh@kernel.org
Subject: Re: [PATCH v2 2/2] pinctrl: ultrarisc: Add UltraRISC DP1000 pinctrl driver
Date: Sat, 06 Jun 2026 14:06:25 +0800 [thread overview]
Message-ID: <178072598572.310568.4489785072318421270.b4-reply@b4> (raw)
In-Reply-To: <20260601102233.F2E711F00898@smtp.kernel.org>
On 2026-06-01 10:22 +0000, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Medium] The Kconfig symbol ARCH_ULTRARISC is referenced in 'depends on' and 'default' but is not defined anywhere in the kernel tree.
> --
>
> commit ae98cd11bdead29c422db358de808560e3f3ab23
> Author: Jia Wang <wangjia@ultrarisc.com>
>
> pinctrl: ultrarisc: Add UltraRISC DP1000 pinctrl driver
>
> This commit adds support for the pin controller on the UltraRISC DP1000 SoC.
> It provides mux selection for pins in ports A, B, C, D, and LPC, as well as
> basic pin configuration controls.
>
> [ ... ]
>
> > diff --git a/drivers/pinctrl/ultrarisc/Kconfig b/drivers/pinctrl/ultrarisc/Kconfig
> > new file mode 100644
> > index 0000000000000..a9257dda5d656
> > --- /dev/null
> > +++ b/drivers/pinctrl/ultrarisc/Kconfig
> > @@ -0,0 +1,23 @@
> > +# SPDX-License-Identifier: GPL-2.0-only
> > +
> > +config PINCTRL_ULTRARISC
> > + tristate
> > + depends on OF
> > + depends on ARCH_ULTRARISC || COMPILE_TEST
>
> [Severity: Medium]
> Does ARCH_ULTRARISC exist in the kernel tree? I couldn't find a definition for
> this Kconfig symbol. If it's missing, this driver will only be selectable
> when COMPILE_TEST is enabled, leaving it disabled for its actual hardware
> target.
>
> > + select PINMUX
> > + select GENERIC_PINCTRL_GROUPS
> > + select GENERIC_PINCONF
> > + select GENERIC_PINMUX_FUNCTIONS
> > + select GPIOLIB
> > +
> > +config PINCTRL_ULTRARISC_DP1000
> > + tristate "UltraRISC DP1000 SoC Pinctrl driver"
> > + select PINCTRL_ULTRARISC
> > + depends on OF && HAS_IOMEM
> > + depends on ARCH_ULTRARISC || COMPILE_TEST
> > + default ARCH_ULTRARISC
>
> [Severity: Medium]
> Similarly here, ARCH_ULTRARISC is used in the depends on and default directives
> but appears to be undefined.
>
Thanks. ARCH_ULTRARISC comes from a separate series referenced in the cover
letter.
> --
> Sashiko AI review · https://sashiko.dev/#/patchset/20260601-ultrarisc-pinctrl-v2-0-07ac5130a96d@ultrarisc.com?part=2
>
Best regards,
Jia Wang
prev parent reply other threads:[~2026-06-06 6:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-01 9:56 [PATCH v2 0/2] pinctrl: ultrarisc: add DP1000 pinctrl support Jia Wang via B4 Relay
2026-06-01 9:56 ` [PATCH v2 1/2] dt-bindings: pinctrl: Add UltraRISC DP1000 pinctrl controller Jia Wang via B4 Relay
2026-06-01 10:06 ` sashiko-bot
2026-06-06 5:56 ` Jia Wang
2026-06-02 16:53 ` Conor Dooley
2026-06-06 6:01 ` Jia Wang
2026-06-01 9:56 ` [PATCH v2 2/2] pinctrl: ultrarisc: Add UltraRISC DP1000 pinctrl driver Jia Wang via B4 Relay
2026-06-01 10:22 ` sashiko-bot
2026-06-06 6:06 ` Jia Wang [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=178072598572.310568.4489785072318421270.b4-reply@b4 \
--to=wangjia@ultrarisc.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=devnull+wangjia.ultrarisc.com@kernel.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