From: Nikolaos Pasaloukos <nikolaos.pasaloukos@blaize.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] gpio: GPIO_BLZP1600 should depend on ARCH_BLAIZE
Date: Wed, 9 Apr 2025 14:31:18 +0100 [thread overview]
Message-ID: <b371a702-e70b-454f-b3e2-3fc63c10190d@blaize.com> (raw)
In-Reply-To: <a75af4b623579a193b4a59350c063969aabb5b71.1744190524.git.geert+renesas@glider.be>
On 09/04/2025 10:22, Geert Uytterhoeven wrote:
> The Blaize BLZP1600 GPIO controller is only present on BLaize BLZP1600
> SoCs. Hence add a dependency on ARCH_BLAIZE, to prevent asking the user
> about this driver when configuring a kernel without Blaize platform
> support.
>
> Fixes: 602ae04f56542d8e ("gpio: Enable Blaize BLZP1600 GPIO support")
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> drivers/gpio/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/gpio/Kconfig b/drivers/gpio/Kconfig
> index ae458fdb9da7dd8a..5f8cd5445c7121ae 100644
> --- a/drivers/gpio/Kconfig
> +++ b/drivers/gpio/Kconfig
> @@ -216,6 +216,7 @@ config GPIO_BCM_XGS_IPROC
> config GPIO_BLZP1600
> tristate "Blaize BLZP1600 GPIO support"
> default y if ARCH_BLAIZE
> + depends on ARCH_BLAIZE || COMPILE_TEST
> depends on OF_GPIO
> select GPIO_GENERIC
> select GPIOLIB_IRQCHIP
Reviewed-by: Nikolaos Pasaloukos <nikolaos.pasaloukos@blaize.com>
next prev parent reply other threads:[~2025-04-09 13:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-09 9:22 [PATCH] gpio: GPIO_BLZP1600 should depend on ARCH_BLAIZE Geert Uytterhoeven
2025-04-09 13:31 ` Nikolaos Pasaloukos [this message]
2025-04-14 20:31 ` Bartosz Golaszewski
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=b371a702-e70b-454f-b3e2-3fc63c10190d@blaize.com \
--to=nikolaos.pasaloukos@blaize.com \
--cc=brgl@bgdev.pl \
--cc=geert+renesas@glider.be \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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