[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2025121622404642e6f789@mail.local>
Date: Tue, 16 Dec 2025 23:40:46 +0100
From: Alexandre Belloni <alexandre.belloni@...tlin.com>
To: Conor Dooley <conor@...nel.org>
Cc: Robert Marko <robert.marko@...tura.hr>, robh@...nel.org,
krzk+dt@...nel.org, conor+dt@...nel.org,
nicolas.ferre@...rochip.com, claudiu.beznea@...on.dev,
Steen.Hegelund@...rochip.com, daniel.machon@...rochip.com,
UNGLinuxDriver@...rochip.com, herbert@...dor.apana.org.au,
davem@...emloft.net, vkoul@...nel.org, linux@...ck-us.net,
andi.shyti@...nel.org, lee@...nel.org, andrew+netdev@...n.ch,
edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com,
linusw@...nel.org, olivia@...enic.com, radu_nicolae.pirea@....ro,
richard.genoud@...tlin.com, gregkh@...uxfoundation.org,
jirislaby@...nel.org, mturquette@...libre.com, sboyd@...nel.org,
richardcochran@...il.com, wsa+renesas@...g-engineering.com,
romain.sioen@...rochip.com, Ryan.Wanner@...rochip.com,
lars.povlsen@...rochip.com, tudor.ambarus@...aro.org,
charan.pedumuru@...rochip.com, kavyasree.kotagiri@...rochip.com,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, linux-crypto@...r.kernel.org,
dmaengine@...r.kernel.org, linux-hwmon@...r.kernel.org,
linux-i2c@...r.kernel.org, netdev@...r.kernel.org,
linux-gpio@...r.kernel.org, linux-spi@...r.kernel.org,
linux-serial@...r.kernel.org, linux-usb@...r.kernel.org,
linux-clk@...r.kernel.org, mwalle@...nel.org,
luka.perkov@...tura.hr
Subject: Re: [PATCH v2 04/19] dt-bindings: arm: move AT91 to generic
Microchip binding
On 16/12/2025 19:21:27+0000, Conor Dooley wrote:
> On Tue, Dec 16, 2025 at 06:26:44PM +0100, Alexandre Belloni wrote:
> > On 16/12/2025 17:56:20+0100, Robert Marko wrote:
> > > On Tue, Dec 16, 2025 at 5:29 PM Alexandre Belloni
> > > <alexandre.belloni@...tlin.com> wrote:
> > > >
> > > > On 15/12/2025 17:35:21+0100, Robert Marko wrote:
> > > > > Create a new binding file named microchip.yaml, to which all Microchip
> > > > > based devices will be moved to.
> > > > >
> > > > > Start by moving AT91, next will be SparX-5.
> > > >
> > > > Both lines of SoCs are designed by different business units and are
> > > > wildly different and while both business units are currently owned by
> > > > the same company, there are no guarantees this will stay this way so I
> > > > would simply avoid merging both.
> > >
> > > Hi Alexandre,
> > >
> > > The merge was requested by Conor instead of adding a new binding for LAN969x [1]
> > >
> > > [1] https://patchwork.kernel.org/project/linux-arm-kernel/patch/20251203122313.1287950-2-robert.marko@sartura.hr/
> > >
> >
> > I would still keep them separate, SparX-5 is closer to what is
> > devicetree/bindings/mips/mscc.txt than to any atmel descended SoCs.
>
> If you don't want the sparx-5 stuff in with the atmel bits, that's fine,
> but I stand over my comments about this lan969x stuff not getting a file
> of its own.
> Probably that means putting it in the atmel file, alongside the lan966x
> boards that are in there at the moment.
I'm fine with this.
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
Powered by blists - more mailing lists