public inbox for linux-serial@vger.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Arnd Bergmann <arnd@kernel.org>
Cc: Robert Marko <robert.marko@sartura.hr>,
	Russell King <linux@armlinux.org.uk>,
	Nicolas Ferre <nicolas.ferre@microchip.com>,
	Alexandre Belloni <alexandre.belloni@bootlin.com>,
	Claudiu Beznea <claudiu.beznea@tuxon.dev>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>,
	Olivia Mackall <olivia@selenic.com>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	"David S . Miller" <davem@davemloft.net>,
	Vinod Koul <vkoul@kernel.org>, Andi Shyti <andi.shyti@kernel.org>,
	Lee Jones <lee@kernel.org>, Mark Brown <broonie@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jiri Slaby <jirislaby@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org,
	dmaengine@vger.kernel.org, linux-i2c@vger.kernel.org,
	linux-spi@vger.kernel.org, linux-serial@vger.kernel.org,
	Oleksij Rempel <o.rempel@pengutronix.de>,
	Daniel Machon <daniel.machon@microchip.com>,
	luka.perkov@sartura.hr
Subject: Re: [PATCH v8 01/10] arm64: Add config for Microchip SoC platforms
Date: Thu, 3 Jul 2025 15:21:36 +0100	[thread overview]
Message-ID: <20250703-lapped-itunes-1cd711479f75@spud> (raw)
In-Reply-To: <ea353170-6e03-4231-afc2-3dc45253931d@app.fastmail.com>

[-- Attachment #1: Type: text/plain, Size: 2150 bytes --]

On Wed, Jul 02, 2025 at 09:57:10PM +0200, Arnd Bergmann wrote:
> On Wed, Jul 2, 2025, at 20:35, Robert Marko wrote:
> > Currently, Microchip SparX-5 SoC is supported and it has its own symbol.
> >
> > However, this means that new Microchip platforms that share drivers need
> > to constantly keep updating depends on various drivers.
> >
> > So, to try and reduce this lets add ARCH_MICROCHIP symbol that drivers
> > could instead depend on.
> 
> Thanks for updating the series to my suggestion!
> 
> > @@ -174,6 +160,27 @@ config ARCH_MESON
> >  	  This enables support for the arm64 based Amlogic SoCs
> >  	  such as the s905, S905X/D, S912, A113X/D or S905X/D2
> > 
> > +menuconfig ARCH_MICROCHIP
> > +	bool "Microchip SoC support"
> > +
> > +if ARCH_MICROCHIP
> > +
> > +config ARCH_SPARX5
> > +	bool "Microchip Sparx5 SoC family"
> 
> This part is the one bit I'm not sure about: The user-visible
> arm64 CONFIG_ARCH_* symbols are usually a little higher-level,
> so I don't think we want both ARCH_MICROCHIP /and/ ARCH_SPARX5
> here, or more generally speaking any of the nested ARCH_*
> symbols.
> 
> This version of your patch is going to be slightly annoying
> to existing sparx5 users because updating an old .config
> breaks when ARCH_MICROCHIP is not enabled.
> 
> The two options that I would prefer here are 
> 
> a) make ARCH_SPARX5 a hidden symbol in order to keep the
>    series bisectable, remove it entirely once all references
>    are moved over to ARCH_MICROCHIP
> 
> b) Make ARCH_MICROCHIP a hidden symbol that is selected by
>    ARCH_SPARX5 but keep the menu unchanged.
> 
> Let's see what the sparx5 and at91 maintainers think about
> these options.
> 
> The other patches all look fine to me.

One more fun thing to consider is that we ended up defining
ARCH_MICROCHIP on riscv because people didn't want to have an
ARCH_MICROCHIP_POLARFIRE symbol enabling the pic64gx SoC. Therefore,
anything that relies on CONFIG_AT91 to be only selectable by users on
arm/arm64 when moved to CONFIG_ARCH_MICROCHIP (as this patch does) will
become selectable on riscv as a result.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  parent reply	other threads:[~2025-07-03 14:21 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-02 18:35 [PATCH v8 00/10] arm64: lan969x: Add support for Microchip LAN969x SoC Robert Marko
2025-07-02 18:35 ` [PATCH v8 01/10] arm64: Add config for Microchip SoC platforms Robert Marko
2025-07-02 19:57   ` Arnd Bergmann
2025-07-03 12:25     ` Robert Marko
2025-07-03 13:55       ` Nicolas Ferre
2025-07-04 17:36         ` Robert Marko
2025-08-11 12:20           ` Daniel Machon
2025-07-03 14:21     ` Conor Dooley [this message]
2025-07-02 18:36 ` [PATCH v8 02/10] ARM: at91: select ARCH_MICROCHIP Robert Marko
2025-07-02 18:36 ` [PATCH v8 03/10] arm64: lan969x: Add support for Microchip LAN969x SoC Robert Marko
2025-07-02 18:36 ` [PATCH v8 04/10] mfd: at91-usart: Make it selectable for ARCH_MICROCHIP Robert Marko
2025-07-23  8:39   ` (subset) " Lee Jones
2025-07-24 10:04     ` Lee Jones
2025-07-27 12:55       ` Robert Marko
2025-07-02 18:36 ` [PATCH v8 05/10] tty: serial: atmel: make " Robert Marko
2025-07-02 18:36 ` [PATCH v8 06/10] spi: " Robert Marko
2025-07-02 18:36 ` [PATCH v8 07/10] i2c: at91: " Robert Marko
2025-07-02 18:36 ` [PATCH v8 08/10] dma: xdmac: " Robert Marko
2025-07-02 18:36 ` [PATCH v8 09/10] char: hw_random: atmel: " Robert Marko
2025-07-02 18:36 ` [PATCH v8 10/10] crypto: atmel-aes: " Robert Marko
2025-07-23 12:29 ` (subset) [PATCH v8 00/10] arm64: lan969x: Add support for Microchip LAN969x SoC Vinod Koul
2025-07-31  8:05   ` Claudiu Beznea
2025-09-03 13:16     ` Alexander Dahl
2025-09-03 14:01       ` Nicolas Ferre

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=20250703-lapped-itunes-1cd711479f75@spud \
    --to=conor@kernel.org \
    --cc=alexandre.belloni@bootlin.com \
    --cc=andi.shyti@kernel.org \
    --cc=arnd@kernel.org \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=claudiu.beznea@tuxon.dev \
    --cc=daniel.machon@microchip.com \
    --cc=davem@davemloft.net \
    --cc=dmaengine@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=jirislaby@kernel.org \
    --cc=lee@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=luka.perkov@sartura.hr \
    --cc=nicolas.ferre@microchip.com \
    --cc=o.rempel@pengutronix.de \
    --cc=olivia@selenic.com \
    --cc=robert.marko@sartura.hr \
    --cc=vkoul@kernel.org \
    --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