From: Lee Jones <lee@kernel.org>
To: Nicolas Ferre <nicolas.ferre@microchip.com>
Cc: Robert Marko <robert.marko@sartura.hr>,
linux@armlinux.org.uk, alexandre.belloni@bootlin.com,
claudiu.beznea@tuxon.dev, catalin.marinas@arm.com,
will@kernel.org, olivia@selenic.com, herbert@gondor.apana.org.au,
davem@davemloft.net, andi.shyti@kernel.org, broonie@kernel.org,
gregkh@linuxfoundation.org, jirislaby@kernel.org,
arnd@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org,
linux-i2c@vger.kernel.org, linux-spi@vger.kernel.org,
linux-serial@vger.kernel.org, o.rempel@pengutronix.de,
daniel.machon@microchip.com, luka.perkov@sartura.hr
Subject: Re: [PATCH v9 4/9] mfd: at91-usart: Make it selectable for ARCH_MICROCHIP
Date: Mon, 8 Sep 2025 15:16:33 +0100 [thread overview]
Message-ID: <20250908141633.GB9224@google.com> (raw)
In-Reply-To: <769c8dc4-4db6-4d2e-aa2f-f86aa7ccaf78@microchip.com>
On Thu, 04 Sep 2025, Nicolas Ferre wrote:
> On 02/09/2025 at 12:02, Lee Jones wrote:
> > On Wed, 13 Aug 2025, Robert Marko wrote:
> >
> > > LAN969x uses the Atmel USART, so make it selectable for ARCH_MICROCHIP to
> > > avoid needing to update depends in future if other Microchip SoC-s use it
> > > as well.
> > >
> > > Signed-off-by: Robert Marko <robert.marko@sartura.hr>
> > > ---
> > > drivers/mfd/Kconfig | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff --git a/drivers/mfd/Kconfig b/drivers/mfd/Kconfig
> > > index 425c5fba6cb1..8f11b2df1470 100644
> > > --- a/drivers/mfd/Kconfig
> > > +++ b/drivers/mfd/Kconfig
> > > @@ -138,7 +138,7 @@ config MFD_AAT2870_CORE
> > > config MFD_AT91_USART
> > > tristate "AT91 USART Driver"
> > > select MFD_CORE
> > > - depends on ARCH_AT91 || ARCH_LAN969X || COMPILE_TEST
> > > + depends on ARCH_MICROCHIP || COMPILE_TEST
> > > help
> > > Select this to get support for AT91 USART IP. This is a wrapper
> > > over at91-usart-serial driver and usart-spi-driver. Only one function
> >
> > Let me know when the deps are in Mainline.
>
> Hi Lee,
>
> I have tags from other maintainers, how about you give us your and we make
My? AB?
> this patch travel through arm-soc like the other ones?
Sure.
Acked-by: Lee Jones <lee@kernel.org>
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2025-09-08 14:16 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-13 17:44 [PATCH v9 0/9] arm64: lan969x: Add support for Microchip LAN969x SoC Robert Marko
2025-08-13 17:44 ` [PATCH v9 1/9] arm64: Add config for Microchip SoC platforms Robert Marko
2025-08-22 13:29 ` Nicolas Ferre
2025-08-13 17:44 ` [PATCH v9 2/9] ARM: at91: select ARCH_MICROCHIP Robert Marko
2025-08-22 13:30 ` Nicolas Ferre
2025-08-13 17:44 ` [PATCH v9 3/9] arm64: lan969x: Add support for Microchip LAN969x SoC Robert Marko
2025-08-22 13:31 ` Nicolas Ferre
2025-08-13 17:44 ` [PATCH v9 4/9] mfd: at91-usart: Make it selectable for ARCH_MICROCHIP Robert Marko
2025-09-02 10:02 ` Lee Jones
2025-09-04 13:03 ` Nicolas Ferre
2025-09-08 14:16 ` Lee Jones [this message]
2025-09-09 8:35 ` Nicolas Ferre
2025-08-13 17:44 ` [PATCH v9 5/9] tty: serial: atmel: make " Robert Marko
2025-08-14 10:11 ` Greg KH
2025-08-13 17:44 ` [PATCH v9 6/9] spi: " Robert Marko
2025-08-13 17:48 ` Mark Brown
2025-08-13 17:44 ` [PATCH v9 7/9] i2c: at91: " Robert Marko
2025-08-13 18:37 ` Wolfram Sang
2025-08-13 17:44 ` [PATCH v9 8/9] char: hw_random: atmel: " Robert Marko
2025-08-13 17:44 ` [PATCH v9 9/9] crypto: atmel-aes: " Robert Marko
2025-08-22 9:32 ` Herbert Xu
2025-08-22 13:33 ` [PATCH v9 0/9] arm64: lan969x: Add support for Microchip LAN969x SoC Nicolas Ferre
2025-08-25 6:27 ` Daniel Machon
2025-09-15 12:42 ` 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=20250908141633.GB9224@google.com \
--to=lee@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=gregkh@linuxfoundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=jirislaby@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=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