From: Conor Dooley <conor@kernel.org>
To: Robert Marko <robert.marko@sartura.hr>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
gregkh@linuxfoundation.org, nicolas.ferre@microchip.com,
claudiu.beznea@tuxon.dev, mturquette@baylibre.com,
sboyd@kernel.org, richardcochran@gmail.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-clk@vger.kernel.org, daniel.machon@microchip.com,
UNGLinuxDriver@microchip.com, luka.perkov@sartura.hr
Subject: Re: [PATCH 2/4] dt-bindings: arm: Document Microchip LAN969x
Date: Fri, 12 Dec 2025 17:55:26 +0000 [thread overview]
Message-ID: <20251212-dazzler-agility-d45940bd27d2@spud> (raw)
In-Reply-To: <CA+HBbNHuYCq9oV4ZjWGjwnJM=oz-O85p_tqB+UnTBmivzDoowg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1962 bytes --]
On Fri, Dec 12, 2025 at 11:09:01AM +0100, Robert Marko wrote:
> On Mon, Dec 8, 2025 at 6:10 PM Conor Dooley <conor@kernel.org> wrote:
> >
> > 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@kernel.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@sartura.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@600000000 thing in the sparx5 file
> > looks pointless and can be deleted IMO.
>
> Ok, I merged them all in one generic microchip.yaml binding, but I noticed that
> arm/atmel-at91.yaml is licensed under GPL-2.0 while arm/microchip,sparx5.yaml
> is dual-licensed as its preferred for bindings.
>
> Is that going to be an issue?
I *think* everyone that contributed, other than maybe Wolfram has
already okayed any binding going to dual license. Just do it as a
standalone commit in the patchset and make sure you CC Michael Walle
and Wolfram Sang.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-12-12 17:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-03 12:21 [PATCH 1/4] dt-bindings: usb: Add Microchip LAN969x support Robert Marko
2025-12-03 12:21 ` [PATCH 2/4] dt-bindings: arm: Document Microchip LAN969x Robert Marko
2025-12-03 19:19 ` Conor Dooley
2025-12-08 10:30 ` Robert Marko
2025-12-08 17:10 ` Conor Dooley
2025-12-12 10:09 ` Robert Marko
2025-12-12 17:55 ` Conor Dooley [this message]
2025-12-03 12:21 ` [PATCH 3/4] include: dt-bindings: add LAN969x clock bindings Robert Marko
2025-12-03 19:22 ` Conor Dooley
2025-12-03 12:21 ` [PATCH 4/4] arm64: dts: microchip: add LAN969x support Robert Marko
2025-12-03 19:21 ` Conor Dooley
2025-12-15 11:36 ` Robert Marko
2025-12-15 12:32 ` Nicolas Ferre
2025-12-15 13:31 ` Robert Marko
2025-12-06 13:53 ` Claudiu Beznea
2025-12-06 18:06 ` Andrew Lunn
2025-12-08 17:15 ` Conor Dooley
2025-12-06 11:27 ` [PATCH 1/4] dt-bindings: usb: Add Microchip " Claudiu Beznea
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=20251212-dazzler-agility-d45940bd27d2@spud \
--to=conor@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=conor+dt@kernel.org \
--cc=daniel.machon@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=luka.perkov@sartura.hr \
--cc=mturquette@baylibre.com \
--cc=nicolas.ferre@microchip.com \
--cc=richardcochran@gmail.com \
--cc=robert.marko@sartura.hr \
--cc=robh@kernel.org \
--cc=sboyd@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