From: "Arnd Bergmann" <arnd@arndb.de>
To: "Robert Marko" <robert.marko@sartura.hr>,
"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>,
"Mark Brown" <broonie@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,
"Pengutronix Kernel Team" <kernel@pengutronix.de>,
ore@pengutronix.de, luka.perkov@sartura.hr,
"Daniel Machon" <daniel.machon@microchip.com>
Subject: Re: [PATCH v7 0/6] arm64: lan969x: Add support for Microchip LAN969x SoC
Date: Mon, 16 Jun 2025 20:34:34 +0200 [thread overview]
Message-ID: <3ba837f8-70bb-4b9e-a9f9-0e71b9e073c4@app.fastmail.com> (raw)
In-Reply-To: <20250613114148.1943267-1-robert.marko@sartura.hr>
On Fri, Jun 13, 2025, at 13:39, Robert Marko wrote:
> This patch series adds basic support for Microchip LAN969x SoC.
>
> It introduces the SoC ARCH symbol itself and allows basic peripheral
> drivers that are currently marked only for AT91 to be also selected for
> LAN969x.
>
> DTS and further driver will be added in follow-up series.
>
> Robert Marko (6):
> arm64: lan969x: Add support for Microchip LAN969x SoC
> spi: atmel: make it selectable for ARCH_LAN969X
> i2c: at91: make it selectable for ARCH_LAN969X
> dma: xdmac: make it selectable for ARCH_LAN969X
> char: hw_random: atmel: make it selectable for ARCH_LAN969X
> crypto: atmel-aes: make it selectable for ARCH_LAN969X
If the drivers on ARCH_LAN969X are largely shared with those on
ARCH_AT91, should they perhaps depend on a common symbol?
That could be either the existing ARCH_AT91 as we do with LAN966,
or perhaps ARCH_MICROCHIP, which is already used for riscv/polarfire.
Arnd
next prev parent reply other threads:[~2025-06-16 18:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-13 11:39 Robert Marko
2025-06-13 11:39 ` [PATCH v7 1/6] " Robert Marko
2025-06-13 12:10 ` Oleksij Rempel
2025-06-16 10:21 ` Daniel Machon
2025-06-30 13:18 ` Robert Marko
2025-06-13 11:39 ` [PATCH v7 2/6] spi: atmel: make it selectable for ARCH_LAN969X Robert Marko
2025-06-13 11:46 ` Mark Brown
2025-06-13 11:39 ` [PATCH v7 3/6] i2c: at91: " Robert Marko
2025-06-13 12:08 ` Oleksij Rempel
2025-06-13 11:39 ` [PATCH v7 4/6] dma: xdmac: " Robert Marko
2025-06-13 12:10 ` Oleksij Rempel
2025-06-13 11:39 ` [PATCH v7 5/6] char: hw_random: atmel: " Robert Marko
2025-06-13 12:07 ` Oleksij Rempel
2025-06-13 11:39 ` [PATCH v7 6/6] crypto: atmel-aes: " Robert Marko
2025-06-13 12:09 ` Oleksij Rempel
2025-06-23 5:49 ` Herbert Xu
2025-06-16 18:34 ` Arnd Bergmann [this message]
2025-06-30 13:21 ` [PATCH v7 0/6] arm64: lan969x: Add support for Microchip LAN969x SoC Robert Marko
2025-06-30 13:53 ` Arnd Bergmann
2025-07-02 11:07 ` Robert Marko
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=3ba837f8-70bb-4b9e-a9f9-0e71b9e073c4@app.fastmail.com \
--to=arnd@arndb.de \
--cc=andi.shyti@kernel.org \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=daniel.machon@microchip.com \
--cc=davem@davemloft.net \
--cc=dmaengine@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=kernel@pengutronix.de \
--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-spi@vger.kernel.org \
--cc=luka.perkov@sartura.hr \
--cc=olivia@selenic.com \
--cc=ore@pengutronix.de \
--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
all inboxes | Powered by JetHome®