linux-kernel - Re: [PATCH 2/4] dt-bindings: arm: Document Microchip LAN969x

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: <20251208-absolute-diploma-6575729ab43f@spud>
Date: Mon, 8 Dec 2025 17:10:33 +0000
From: Conor Dooley <conor@...nel.org>
To: Robert Marko <robert.marko@...tura.hr>
Cc: robh@...nel.org, krzk+dt@...nel.org, conor+dt@...nel.org,
	gregkh@...uxfoundation.org, nicolas.ferre@...rochip.com,
	claudiu.beznea@...on.dev, mturquette@...libre.com, sboyd@...nel.org,
	richardcochran@...il.com, devicetree@...r.kernel.org,
	linux-kernel@...r.kernel.org, linux-usb@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org, linux-clk@...r.kernel.org,
	daniel.machon@...rochip.com, UNGLinuxDriver@...rochip.com,
	luka.perkov@...tura.hr
Subject: Re: [PATCH 2/4] dt-bindings: arm: Document Microchip LAN969x

On Mon, Dec 08, 2025 at 11:30:28AM +0100, Robert Marko wrote:
> On Wed, Dec 3, 2025 at 8:19 PM Conor Dooley <conor@...nel.org> wrote:
> >
> > On Wed, Dec 03, 2025 at 01:21:30PM +0100, Robert Marko wrote:
> > > Microchip LAN969x is a series of multi-port, multi-gigabit switches based
> > > on ARMv8 Cortex-A53 CPU.
> > >
> > > Signed-off-by: Robert Marko <robert.marko@...tura.hr>
> > > ---
> > >  .../bindings/arm/microchip,lan969x.yaml       | 32 +++++++++++++++++++
> >
> > This should not be in a unique file, put it in with the other microchip
> > arm devices please. Also, the wildcard in the compatible is not
> > permitted, only way it'd make sense is if these are different binnings
> > of the same silicon. If that's the case, you need to explain why,
> > because compatibles are meant to be soc-specific.
> 
> Hi Conor,
> The issue is that there is no unique place for Microchip SoC-s,
> LAN966x series is in the AT91 bindings
> while SparX-5 has its own bindings file.
> 
> What would you suggest in this case?

Ideally, arm/atmel-at91.yaml and arm/microchip,sparx5.yaml would just
become arm/microchip.yaml. The axi@...000000 thing in the sparx5 file
looks pointless and can be deleted IMO.


Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)