[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YNnNNkjOiH6hd2l9@lunn.ch>
Date: Mon, 28 Jun 2021 15:23:02 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Lukasz Majewski <lukma@...x.de>
Cc: "David S . Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
Madalin Bucur <madalin.bucur@....nxp.com>,
Nicolas Ferre <nicolas.ferre@...rochip.com>,
Joakim Zhang <qiangqing.zhang@....com>,
Florian Fainelli <f.fainelli@...il.com>,
Vladimir Oltean <olteanv@...il.com>, netdev@...r.kernel.org,
Arnd Bergmann <arnd@...db.de>,
Mark Einon <mark.einon@...il.com>,
NXP Linux Team <linux-imx@....com>,
linux-kernel@...r.kernel.org
Subject: Re: [RFC 2/3] net: Provide switchdev driver for NXP's More Than IP
L2 switch
> The best I could get would be:
>
> ð_switch {
> compatible = "imx,mtip-l2switch";
> reg = <0x800f8000 0x400>, <0x800fC000 0x4000>;
>
> interrupts = <100>;
> status = "okay";
>
> ethernet-ports {
> port1@1 {
> reg = <1>;
> label = "eth0";
> phys = <&mac0 0>;
> };
>
> port2@2 {
> reg = <2>;
> label = "eth1";
> phys = <&mac1 1>;
> };
> };
> };
>
> Which would abuse the "phys" properties usages - as 'mac[01]' are
> referring to ethernet controllers.
This is not how a dedicated driver would have its binding. We should
not establish this as ABI.
So, sorry, but no.
Andrew
Powered by blists - more mailing lists