[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210628161429.5650221e@ktm>
Date: Mon, 28 Jun 2021 16:14:29 +0200
From: Lukasz Majewski <lukma@...x.de>
To: Andrew Lunn <andrew@...n.ch>
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
Hi Andrew,
> > 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.
Thanks for the clear statement about upstream requirements.
>
> Andrew
Best regards,
Lukasz Majewski
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma@...x.de
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists