The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
	Conor Dooley <conor@kernel.org>,
	Nicolas Ferre <nicolas.ferre@microchip.com>,
	Claudiu Beznea <claudiu.beznea@tuxon.dev>
Cc: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, brgl@kernel.org
Subject: Re: [PATCH] arm64: Kconfig: provide a top-level switch for Microchip platforms
Date: Thu, 26 Feb 2026 15:49:06 +0100	[thread overview]
Message-ID: <84da053d-97d5-4d07-8e76-b162a5b23d2a@kernel.org> (raw)
In-Reply-To: <20260226143615.65788-1-bartosz.golaszewski@oss.qualcomm.com>

On 26/02/2026 15:36, Bartosz Golaszewski wrote:
> Microchip is the only platform that doesn't have a top-level switch for
> disabling all SoC families. Align it with other platforms and update the
> arm64 defconfig to keep the default config the same.
> 
> Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
> ---
>  arch/arm64/Kconfig.platforms | 10 ++++------
>  arch/arm64/configs/defconfig |  1 +
>  2 files changed, 5 insertions(+), 6 deletions(-)
> 
> diff --git a/arch/arm64/Kconfig.platforms b/arch/arm64/Kconfig.platforms
> index 54eb1d7fd419b..72c812e76b0b1 100644
> --- a/arch/arm64/Kconfig.platforms
> +++ b/arch/arm64/Kconfig.platforms
> @@ -188,16 +188,15 @@ config ARCH_MESON
>  	  This enables support for the arm64 based Amlogic SoCs
>  	  such as the s905, S905X/D, S912, A113X/D or S905X/D2
>  
> -menu "Microchip SoC support"
> +menuconfig ARCH_MICROCHIP
> +	bool "Microchip SoC support"
>  
> -config ARCH_MICROCHIP
> -	bool
> +if ARCH_MICROCHIP

This will surprise all out-of-tree non-defconfig users, because their
boards will stop working (drivers depend on ARCH_LAN969X|ARCH_SPARX5
which will be now disabled), but I like the consistency.

I guess this will go via Microchip arm64 soc tree.

Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>

Best regards,
Krzysztof

  reply	other threads:[~2026-02-26 14:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-26 14:36 [PATCH] arm64: Kconfig: provide a top-level switch for Microchip platforms Bartosz Golaszewski
2026-02-26 14:49 ` Krzysztof Kozlowski [this message]
2026-02-27  8:42   ` Bartosz Golaszewski
2026-02-27  8:48     ` Arnd Bergmann
2026-02-27  8:51       ` Bartosz Golaszewski
2026-02-27  9:21         ` Krzysztof Kozlowski
2026-02-27  9:28           ` Arnd Bergmann
2026-02-27 10:15             ` Conor Dooley
2026-02-27 10:37               ` Krzysztof Kozlowski
2026-02-27 11:17                 ` Daniel Machon
2026-03-11  8:32                   ` Bartosz Golaszewski
2026-03-11  8:58                     ` Krzysztof Kozlowski
2026-03-18  8:21                       ` Bartosz Golaszewski
2026-03-18  8:59                         ` claudiu beznea
2026-02-27  9:19     ` Krzysztof Kozlowski

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=84da053d-97d5-4d07-8e76-b162a5b23d2a@kernel.org \
    --to=krzk@kernel.org \
    --cc=arnd@arndb.de \
    --cc=bartosz.golaszewski@oss.qualcomm.com \
    --cc=brgl@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=claudiu.beznea@tuxon.dev \
    --cc=conor@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicolas.ferre@microchip.com \
    --cc=will@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