[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a1968447-5dd9-e309-6a3e-48ed05c2ab93@gmail.com>
Date: Sun, 22 Mar 2020 14:09:22 -0700
From: Florian Fainelli <f.fainelli@...il.com>
To: Rob Herring <robh@...nel.org>
Cc: Oleksij Rempel <o.rempel@...gutronix.de>,
Mark Rutland <mark.rutland@....com>,
devicetree@...r.kernel.org, Andrew Lunn <andrew@...n.ch>,
Marek Vasut <marex@...x.de>, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org,
Pengutronix Kernel Team <kernel@...gutronix.de>,
David Jander <david@...tonic.nl>,
"David S. Miller" <davem@...emloft.net>,
Heiner Kallweit <hkallweit1@...il.com>
Subject: Re: [PATCH v4 1/4] dt-bindings: net: phy: Add support for NXP TJA11xx
On 3/20/2020 4:05 PM, Rob Herring wrote:
>>>> Because the primary PHY0 can be autodetected by the bus scan.
>>>> But I have nothing against your suggestions. Please, some one should say the
>>>> last word here, how exactly it should be implemented?
>>
>> It's not for me to decide, I was hoping the Device Tree maintainers
>> could chime in, your current approach would certainly work although it
>> feels visually awkward.
>
> Something like this is what I'd do:
>
> ethernet-phy@4 {
> compatible = "nxp,tja1102";
> reg = <4 5>;
> };
But the parent (MDIO bus controller) has #address-cells = 1 and
#size-cells = 0, so how can this be made to work without creating two
nodes or a first node encapsulating another one?
--
Florian
Powered by blists - more mailing lists