Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Joseph Telaak" <joseph@telaak.dev>
Cc: linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
	robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH 2/2] pinctrl: Add Siflower SF19A2890 pin controller driver
Date: Wed, 04 Nov 2026 07:34:12 +0000	[thread overview]
Message-ID: <sashiko-outbox-196802@kernel.org> (raw)
In-Reply-To: <20261104-sf19a2890-pinctrl-v1-2-4bb83afdbacf@telaak.dev>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] pinctrl: sf19a2890: Kconfig depends on undefined MACH_SIFLOWER_MIPS
--

commit ac52cbc972a93961baa0d00dc4d81d67b2ec8a72
Author: Joseph Telaak <joseph@telaak.dev>

pinctrl: Add Siflower SF19A2890 pin controller driver

This commit adds a pin controller driver for the Siflower SF19A2890 SoC,
supporting pinmuxing, GPIO mux switching, and pad configuration such as
bias, input enable, Schmitt trigger, and drive strength.

> diff --git a/drivers/pinctrl/Kconfig b/drivers/pinctrl/Kconfig
> index dc7138302c55c..1321eb679fcdd 100644
> --- a/drivers/pinctrl/Kconfig
> +++ b/drivers/pinctrl/Kconfig
> @@ -562,6 +562,20 @@ config PINCTRL_SCMI
>  	  It uses SCMI Message Protocol to interact with the
>  	  firmware providing all the pinctrl controls.
>  
> +config PINCTRL_SF19A2890
> +	tristate "Siflower SF19A2890 pin controller"
> +	depends on MACH_SIFLOWER_MIPS || COMPILE_TEST
> +	depends on OF
> +	default MACH_SIFLOWER_MIPS

[Severity: Low]
Is MACH_SIFLOWER_MIPS defined in the tree? Because MACH_SIFLOWER_MIPS does
not exist in any Kconfig file, PINCTRL_SF19A2890 in drivers/pinctrl/Kconfig
cannot be enabled on MIPS configurations unless COMPILE_TEST is set, and
default MACH_SIFLOWER_MIPS always evaluates to n.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261104-sf19a2890-pinctrl-v1-0-4bb83afdbacf@telaak.dev?part=2

  reply	other threads:[~2026-11-04  7:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-04  7:21 [PATCH 0/2] pinctrl: Add the Siflower SF19A2890 pin controller Joseph Telaak via B4 Relay
2026-11-04  7:21 ` [PATCH 1/2] dt-bindings: pinctrl: Add " Joseph Telaak via B4 Relay
2026-11-04 23:49   ` Conor Dooley
2026-11-05  0:45     ` Joseph Telaak
2026-11-04  7:21 ` [PATCH 2/2] pinctrl: Add Siflower SF19A2890 pin controller driver Joseph Telaak via B4 Relay
2026-11-04  7:34   ` sashiko-bot [this message]
2026-11-04 23:54   ` Conor Dooley
2026-11-05  0:54     ` Joseph Telaak
2026-11-05  1:35       ` Conor Dooley
2026-11-05  4:45         ` Joseph Telaak
2026-11-05 12:13   ` kernel test robot
2026-11-06 17:01   ` Uwe Kleine-König
2026-11-08 22:07     ` Joseph Telaak

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=sashiko-outbox-196802@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=joseph@telaak.dev \
    --cc=linux-gpio@vger.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