[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <295AB115-C189-430E-B361-4A892D7528C9@coresemi.io>
Date: Mon, 18 Aug 2025 17:21:32 +0900
From: "D. Jeff Dionne" <jeff@...esemi.io>
To: Krzysztof Kozlowski <krzk@...nel.org>
Cc: Geert Uytterhoeven <geert@...ux-m68k.org>,
Artur Rojek <contact@...ur-rojek.eu>,
Rob Landley <rob@...dley.net>,
John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de>,
Andrew Lunn <andrew+netdev@...n.ch>,
"David S . Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>,
Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
netdev@...r.kernel.org,
devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/3] dt-bindings: net: Add support for J-Core EMAC
On Aug 18, 2025, at 17:07, Krzysztof Kozlowski <krzk@...nel.org> wrote:
> git grep jcore,emac
>
> Gives me zero?
Um, right. It’s not upstream yet. Thanks for your work to get that done, Artur.
>> If an incompatible version comes up, it should use a different
>> (versioned?) compatible value.
>
> Versions are allowed if they follow some documented and known vendor SoC versioning scheme. Is this the case here?
>
> This is some sort of SoC, right? So it should have actual SoC name?
No. It’s a generic IP core for multiple SoCs, which do have names.
This is the correct naming scheme. All compatible devices and SoCs match properly.
J.
> Best regards,
> Krzysztof
Powered by blists - more mailing lists