From: Andrew Lunn <andrew@lunn.ch>
To: David Miller <davem@davemloft.net>
Cc: Guenter Roeck <linux@roeck-us.net>,
Florian Fainelli <f.fainelli@gmail.com>,
Vivien Didelot <vivien.didelot@savoirfairelinux.com>,
netdev <netdev@vger.kernel.org>, Andrew Lunn <andrew@lunn.ch>
Subject: [PATCH net-next 0/3] D in DSA patches
Date: Mon, 17 Aug 2015 23:52:49 +0200 [thread overview]
Message-ID: <1439848372-4055-1-git-send-email-andrew@lunn.ch> (raw)
The D in DSA is distributed, meaning multiple switches can be
connected together. Currently no mainline system does this, and so the
code is broken. This patchset contains two fixes, and a small helper.
With three of more switches, the current device tree binding is not
sufficient to express the routing between the switches. The first
patch extends the binding, in a backwards compatible way, to allow a
link between a switch to describe all the switches accessible over the
link, not just the direct neighbor.
The third patch fixes the port configuration on newer devices for
links connecting switches.
Andrew Lunn (3):
net: dsa: Allow multi hop routes to be expressed
net: dsa: Add dsa_is_dsa_port() helper
dsa: mv88e6xxx: Set DSA mode based on chip abilities
Documentation/devicetree/bindings/net/dsa/dsa.txt | 33 +++++++++++++++----
drivers/net/dsa/mv88e6xxx.c | 16 +++++----
include/net/dsa.h | 5 +++
net/dsa/dsa.c | 40 +++++++++++++++++------
4 files changed, 71 insertions(+), 23 deletions(-)
--
2.5.0
next reply other threads:[~2015-08-17 22:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-17 21:52 Andrew Lunn [this message]
2015-08-17 21:52 ` [PATCH net-next 1/3] net: dsa: Allow multi hop routes to be expressed Andrew Lunn
2015-08-17 21:52 ` [PATCH net-next 2/3] net: dsa: Add dsa_is_dsa_port() helper Andrew Lunn
2015-08-17 21:52 ` [PATCH net-next 3/3] dsa: mv88e6xxx: Set DSA mode based on chip abilities Andrew Lunn
2015-08-18 21:17 ` [PATCH net-next 0/3] D in DSA patches David Miller
2015-08-19 21:25 ` Florian Fainelli
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=1439848372-4055-1-git-send-email-andrew@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=linux@roeck-us.net \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@savoirfairelinux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).