* [PATCH] gpio: GPIO_BLZP1600 should depend on ARCH_BLAIZE
@ 2025-04-09 9:22 Geert Uytterhoeven
2025-04-09 13:31 ` Nikolaos Pasaloukos
2025-04-14 20:31 ` Bartosz Golaszewski
0 siblings, 2 replies; 3+ messages in thread
From: Geert Uytterhoeven @ 2025-04-09 9:22 UTC (permalink / raw)
To: Linus Walleij, Bartosz Golaszewski, Nikolaos Pasaloukos
Cc: linux-gpio, linux-kernel, Geert Uytterhoeven
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
--
2.43.0
^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: [PATCH] gpio: GPIO_BLZP1600 should depend on ARCH_BLAIZE
2025-04-09 9:22 [PATCH] gpio: GPIO_BLZP1600 should depend on ARCH_BLAIZE Geert Uytterhoeven
@ 2025-04-09 13:31 ` Nikolaos Pasaloukos
2025-04-14 20:31 ` Bartosz Golaszewski
1 sibling, 0 replies; 3+ messages in thread
From: Nikolaos Pasaloukos @ 2025-04-09 13:31 UTC (permalink / raw)
To: Geert Uytterhoeven, Linus Walleij, Bartosz Golaszewski
Cc: linux-gpio, linux-kernel
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>
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH] gpio: GPIO_BLZP1600 should depend on ARCH_BLAIZE
2025-04-09 9:22 [PATCH] gpio: GPIO_BLZP1600 should depend on ARCH_BLAIZE Geert Uytterhoeven
2025-04-09 13:31 ` Nikolaos Pasaloukos
@ 2025-04-14 20:31 ` Bartosz Golaszewski
1 sibling, 0 replies; 3+ messages in thread
From: Bartosz Golaszewski @ 2025-04-14 20:31 UTC (permalink / raw)
To: Linus Walleij, Nikolaos Pasaloukos, Geert Uytterhoeven
Cc: Bartosz Golaszewski, linux-gpio, linux-kernel
On Wed, 09 Apr 2025 11:22:35 +0200, 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.
>
>
Applied, thanks!
[1/1] gpio: GPIO_BLZP1600 should depend on ARCH_BLAIZE
https://git.kernel.org/brgl/linux/c/df9b3454a00ed9e4c85295611b28b7041fc2a1d9
Best regards,
--
Bartosz Golaszewski <brgl@bgdev.pl>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2025-04-14 20:31 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-04-09 9:22 [PATCH] gpio: GPIO_BLZP1600 should depend on ARCH_BLAIZE Geert Uytterhoeven
2025-04-09 13:31 ` Nikolaos Pasaloukos
2025-04-14 20:31 ` Bartosz Golaszewski
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox