linux-kernel - Re: [PATCH v7 0/6] arm64: lan969x: Add support for Microchip LAN969x SoC

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <3ba837f8-70bb-4b9e-a9f9-0e71b9e073c4@app.fastmail.com>
Date: Mon, 16 Jun 2025 20:34:34 +0200
From: "Arnd Bergmann" <arnd@...db.de>
To: "Robert Marko" <robert.marko@...tura.hr>,
 "Catalin Marinas" <catalin.marinas@....com>, "Will Deacon" <will@...nel.org>,
 "Olivia Mackall" <olivia@...enic.com>,
 "Herbert Xu" <herbert@...dor.apana.org.au>,
 "David S . Miller" <davem@...emloft.net>, "Vinod Koul" <vkoul@...nel.org>,
 "Andi Shyti" <andi.shyti@...nel.org>, "Mark Brown" <broonie@...nel.org>,
 linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
 linux-crypto@...r.kernel.org, dmaengine@...r.kernel.org,
 linux-i2c@...r.kernel.org, linux-spi@...r.kernel.org,
 "Pengutronix Kernel Team" <kernel@...gutronix.de>, ore@...gutronix.de,
 luka.perkov@...tura.hr, "Daniel Machon" <daniel.machon@...rochip.com>
Subject: Re: [PATCH v7 0/6] arm64: lan969x: Add support for Microchip LAN969x SoC

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