On Mon, Jun 16, 2025 at 8:34 PM Arnd Bergmann <arnd@xxxxxxxx> wrote: > > 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. Hi Arnd, I thought about this, but I am not sure whether its worth it since we need LAN969x arch anyway for other drivers that currently depend on LAN966x or SparX-5 but will be extended for LAN969x (I have this already queued locally but need this to land first). I hope this makes sense Regards, Robert > > Arnd -- Robert Marko Staff Embedded Linux Engineer Sartura d.d. Lendavska ulica 16a 10000 Zagreb, Croatia Email: robert.marko@xxxxxxxxxx Web: www.sartura.hr
