From: Nicolas Ferre <nicolas.ferre@microchip.com>
To: 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>, <lee@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>
Cc: <luka.perkov@sartura.hr>
Subject: Re: [PATCH v9 3/9] arm64: lan969x: Add support for Microchip LAN969x SoC
Date: Fri, 22 Aug 2025 15:31:58 +0200 [thread overview]
Message-ID: <d05d7de0-bfc8-4184-bd18-b3ffb50fbb76@microchip.com> (raw)
In-Reply-To: <20250813174720.540015-4-robert.marko@sartura.hr>
On 13/08/2025 at 19:44, Robert Marko wrote:
> This adds support for the Microchip LAN969x ARMv8-based SoC switch family.
>
> Signed-off-by: Robert Marko <robert.marko@sartura.hr>
Acked-by: Nicolas Ferre <nicolas.ferre@microchip.com>
> ---
> Changes in v9:
> * Select ARCH_MICROCHIP when ARCH_LAN969X is selected as its now hidden
>
> Changes in v8:
> * Place LAN969x under ARCH_MICROCHIP as suggested by Arnd and drop review
> tags due to this
>
> arch/arm64/Kconfig.platforms | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
>
> diff --git a/arch/arm64/Kconfig.platforms b/arch/arm64/Kconfig.platforms
> index bfea380100a6..31bddd1a17de 100644
> --- a/arch/arm64/Kconfig.platforms
> +++ b/arch/arm64/Kconfig.platforms
> @@ -177,6 +177,21 @@ menu "Microchip SoC support"
> config ARCH_MICROCHIP
> bool
>
> +config ARCH_LAN969X
> + bool "Microchip LAN969X SoC family"
> + select PINCTRL
> + select DW_APB_TIMER_OF
> + select ARCH_MICROCHIP
> + help
> + This enables support for the Microchip LAN969X ARMv8-based
> + SoC family of TSN-capable gigabit switches.
> +
> + The LAN969X Ethernet switch family provides a rich set of
> + switching features such as advanced TCAM-based VLAN and QoS
> + processing enabling delivery of differentiated services, and
> + security through TCAM-based frame processing using versatile
> + content aware processor (VCAP).
> +
> config ARCH_SPARX5
> bool "Microchip Sparx5 SoC family"
> select PINCTRL
> --
> 2.50.1
>
next prev parent reply other threads:[~2025-08-22 13:32 UTC|newest]
Thread overview: 21+ 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 [this message]
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-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
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=d05d7de0-bfc8-4184-bd18-b3ffb50fbb76@microchip.com \
--to=nicolas.ferre@microchip.com \
--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=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=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;
as well as URLs for NNTP newsgroup(s).