Linux GPIO subsystem development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Fil Dunsky" <filipp.dunsky@gmail.com>
Cc: devicetree@vger.kernel.org, linux-gpio@vger.kernel.org,
	linux-watchdog@vger.kernel.org, robh@kernel.org,
	conor+dt@kernel.org
Subject: Re: [PATCH v2 04/11] gpio: Add Cortina Systems CS75xx GPIO driver
Date: Tue, 13 Oct 2026 03:58:18 +0000	[thread overview]
Message-ID: <sashiko-outbox-168944@kernel.org> (raw)
In-Reply-To: <20261013-b4-cs75xx-s2-v2-4-94f8c0a90cda@gmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] kconfig: unmet direct dependency on HAS_IOMEM when selecting GPIO_GENERIC
--

commit c0cf3f24c2d064770186cd2502b93c7a6f2518be
Author: Fil Dunsky <filipp.dunsky@gmail.com>

gpio: Add Cortina Systems CS75xx GPIO driver
    
This commit introduces a new GPIO driver for the Cortina Systems CS75xx SoCs.
It handles data and direction registers using gpio-mmio, manages GPIO line 
pin multiplexing, and provides interrupt support.

> diff --git a/drivers/gpio/Kconfig b/drivers/gpio/Kconfig
> index dfdc9ee1a6b38..6b9524f25d24c 100644
> --- a/drivers/gpio/Kconfig
> +++ b/drivers/gpio/Kconfig
> @@ -300,6 +300,18 @@ config GPIO_CLPS711X
>  	help
>  	  Say yes here to support GPIO on CLPS711X SoCs.
>  
> +config GPIO_CS75XX
> +	tristate "Cortina Systems CS75xx GPIO support"
> +	depends on ARCH_CORTINA_ACCESS || COMPILE_TEST
> +	select GPIO_GENERIC

[Severity: Low]
Does this select statement cause a Kconfig unmet dependency warning?

Since GPIO_GENERIC depends on HAS_IOMEM, selecting it here without inheriting
the HAS_IOMEM dependency might cause build warnings or failures when compiling
with COMPILE_TEST enabled on architectures that lack HAS_IOMEM (such as UML).

Should this config also have a depends on HAS_IOMEM to prevent this?

> +	select GPIOLIB_IRQCHIP
> +	help
> +	  Say yes here to support the GPIO banks of the Cortina Systems
> +	  CS75xx SoCs, including their interrupts.

[ ... ]

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261013-b4-cs75xx-s2-v2-0-94f8c0a90cda@gmail.com?part=4

  reply	other threads:[~2026-10-13  3:58 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-13  3:46 [PATCH v2 00/11] Cortina Systems CS75xx: interrupt controller, GPIO, I2C and TWD watchdog Fil Dunsky via B4 Relay
2026-10-13  3:46 ` [PATCH v2 01/11] dt-bindings: interrupt-controller: Add Cortina Systems CS7542 peripheral interrupt controller Fil Dunsky via B4 Relay
2026-10-13  3:47 ` [PATCH v2 02/11] irqchip: Add Cortina Systems CS75xx " Fil Dunsky via B4 Relay
2026-10-13  3:47 ` [PATCH v2 03/11] dt-bindings: gpio: Add Cortina Systems CS7542 GPIO controller Fil Dunsky via B4 Relay
2026-10-13  3:53   ` sashiko-bot
2026-10-13  3:47 ` [PATCH v2 04/11] gpio: Add Cortina Systems CS75xx GPIO driver Fil Dunsky via B4 Relay
2026-10-13  3:58   ` sashiko-bot [this message]
2026-10-13  3:47 ` [PATCH v2 05/11] dt-bindings: i2c: Add Cortina Systems CS7542 I2C controller Fil Dunsky via B4 Relay
2026-10-13  3:47 ` [PATCH v2 06/11] i2c: Add Cortina Systems CS75xx I2C controller driver Fil Dunsky via B4 Relay
2026-10-13  4:04   ` sashiko-bot
2026-10-13  3:47 ` [PATCH v2 07/11] watchdog: Add ARM TWD (MPCore private) watchdog driver Fil Dunsky via B4 Relay
2026-10-13  4:10   ` sashiko-bot
2026-10-13  3:47 ` [PATCH v2 08/11] ARM: dts: cortina: cs7542: Add interrupt controller, GPIO and I2C Fil Dunsky via B4 Relay
2026-10-13  3:47 ` [PATCH v2 09/11] ARM: dts: cortina: almondplus: Add reset button and enable I2C Fil Dunsky via B4 Relay
2026-10-13  3:47 ` [PATCH v2 10/11] ARM: multi_v7_defconfig: Enable Cortina Systems CS75xx GPIO, I2C and TWD watchdog Fil Dunsky via B4 Relay
2026-10-13  6:13   ` Krzysztof Kozlowski
2026-10-13  6:19     ` Fil Dunsky
2026-10-13  3:47 ` [PATCH v2 11/11] MAINTAINERS: Add Cortina Systems CS75xx interrupt controller, GPIO and I2C Fil Dunsky via B4 Relay

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-168944@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=filipp.dunsky@gmail.com \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-watchdog@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