From: Florian Fainelli <f.fainelli@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>,
Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: David Miller <davem@davemloft.net>, netdev <netdev@vger.kernel.org>
Subject: Re: [PATCHv2 net-next] dsa: Support multiple MDIO busses
Date: Sun, 09 Aug 2015 11:33:55 -0700 [thread overview]
Message-ID: <55C79D13.1050608@gmail.com> (raw)
In-Reply-To: <20150809173517.GC11157@lunn.ch>
Le 08/09/15 10:35, Andrew Lunn a écrit :
>>> The optional mii-bus properties i'm adding should be used in
>>> preference to this global one, for this switch. Keeping the names the
>>> same makes sense. But i did drop the dsa prefix to indicate it is
>>> local, not global scope,
>>
>> Dropping a vendor prefix usually means that it's (standardized)
>> common property name. I don't know where you took the "local" scope
>> thing...
>
> DSA has at least three levels of hierarchy. The following is the
> example from the binding documentation. There is a 'global' scope
> dsa,mii-bus = <&mii_bus0> in the top level, which is mandatory. This
> patch allows optional 'local' scope mii bus to be specified at an
> individual switch level. The 'local' value, if present, will override
> the 'global' value.
>
> Maybe more properties should use the dsa prefix? But dsa is not a
> vendor prefix, it just refers to "Distributed Switch Architecture",
> the scheme for accessing a number of Ethernet switches connected
> together in a cluster. But as the binding has grown, this prefix has
> not been used with new properties.
Maybe it was not very smart to use the "dsa," prefixing initially, but I
agree with Andrew's naming of things here, we are already local to the
switch tree so dropping the prefix sounds reasonable.
>
> Andrew
>
> dsa@0 {
> compatible = "marvell,dsa";
> #address-cells = <2>;
> #size-cells = <0>;
>
> interrupts = <10>;
> dsa,ethernet = <ðernet0>;
> dsa,mii-bus = <&mii_bus0>;
>
> switch@0 {
> #address-cells = <1>;
> #size-cells = <0>;
> reg = <16 0>; /* MDIO address 16, switch 0 in tree */
>
> port@0 {
> reg = <0>;
> label = "lan1";
> phy-handle = <&phy0>;
> };
>
> port@1 {
> reg = <1>;
> label = "lan2";
> };
>
> port@5 {
> reg = <5>;
> label = "cpu";
> };
>
> switch0port6: port@6 {
> reg = <6>;
> label = "dsa";
> link = <&switch1port0
> &switch2port0>;
> };
> };
>
> switch@1 {
> #address-cells = <1>;
> #size-cells = <0>;
> reg = <17 1>; /* MDIO address 17, switch 1 in tree */
> mii-bus = <&mii_bus1>;
>
> switch1port0: port@0 {
> reg = <0>;
> label = "dsa";
> link = <&switch0port6>;
> };
> switch1port1: port@1 {
> reg = <1>;
> label = "dsa";
> link = <&switch2port1>;
> };
> };
>
> switch@2 {
> #address-cells = <1>;
> #size-cells = <0>;
> reg = <18 2>; /* MDIO address 18, switch 2 in tree */
> mii-bus = <&mii_bus1>;
>
> switch2port0: port@0 {
> reg = <0>;
> label = "dsa";
> link = <&switch1port1
> &switch0port6>;
> };
> };
> };
>
--
Florian
prev parent reply other threads:[~2015-08-09 18:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-09 1:29 [PATCHv2 net-next] dsa: Support multiple MDIO busses Andrew Lunn
2015-08-09 12:39 ` Sergei Shtylyov
2015-08-09 14:20 ` Andrew Lunn
2015-08-09 17:26 ` Sergei Shtylyov
2015-08-09 17:35 ` Andrew Lunn
2015-08-09 18:33 ` Florian Fainelli [this message]
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=55C79D13.1050608@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=sergei.shtylyov@cogentembedded.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.