From: Guenter Roeck <linux@roeck-us.net>
To: netdev@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
Andrew Lunn <andrew@lunn.ch>,
Florian Fainelli <f.fainelli@gmail.com>,
linux-kernel@vger.kernel.org, Guenter Roeck <linux@roeck-us.net>
Subject: [RFT/RFC PATCH 0/8] net: dsa: mv88e6xxx: Add support for HW bridging
Date: Mon, 23 Feb 2015 11:35:42 -0800 [thread overview]
Message-ID: <1424720150-27564-1-git-send-email-linux@roeck-us.net> (raw)
This patch series applies on top of net-next, plus Florian's patches
integrating dsa with SWITCHDEV for HW bridging. It also requires the patch
'net: dsa: Ensure that port array elements are initialized before being used'.
HW bridging support is currently only enabled for MV8865352, but it should be
straightforward to enable support for other Marvell chips by adding three lines
of initialization code to the respective source; see patch 8/8 for details.
mv886e3131.c would also have to use mv88e6xxx_setup_port_common().
Patches 1-3 prepare the mv88e6xxx code for adding HW bridging support.
Patch 4 adds core HW bridging support to the mv88e6xxx code. Patch 5-7
prepare the drivers for mv88e6352, mv88e6123_61_65, and mv88e6171 for
HW bridging support, without actually enabling it. Patch 8 enables
HW bridging support in the mv88e6352 driver.
Patches 5 and 8 could possibly be merged, but I thought it was better
to keep them separate because they logically serve a different purpose.
Testing has been minimal, and only with MV88E6352. Ports can be added to
and removed from a bridge, and I have been able to pass data through a port
configured as bridge port.
next reply other threads:[~2015-02-23 19:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-23 19:35 Guenter Roeck [this message]
2015-02-23 19:35 ` [RFT/RFC PATCH 1/8] net: dsa: mv88e6xxx: Factor out common initialization code Guenter Roeck
2015-02-23 19:35 ` [RFT/RFC PATCH 2/8] net: dsa: mv88e6xxx: Provide function for common port initialization Guenter Roeck
2015-02-23 19:35 ` [RFT/RFC PATCH 3/8] net: dsa: mv88e6xxx: Split mv88e6xxx_reg_read and mv88e6xxx_reg_write Guenter Roeck
2015-02-23 19:35 ` [RFT/RFC PATCH 4/8] net: dsa: mv88e6xxx: Add Hardware bridging support Guenter Roeck
2015-02-23 19:35 ` [RFT/RFC PATCH 5/8] net: dsa: mv88e6352: Use common port initialization code Guenter Roeck
2015-02-23 19:35 ` [RFT/RFC PATCH 6/8] net: dsa: mv88e6123_61_65: Use common port configuration Guenter Roeck
2015-02-23 19:35 ` [RFT/RFC PATCH 7/8] net: dsa: mv88e6171: " Guenter Roeck
2015-02-23 19:35 ` [RFT/RFC PATCH 8/8] net: dsa: mv88e6352: Add support for hardware bridging Guenter Roeck
2015-03-08 16:40 ` [RFT/RFC PATCH 0/8] net: dsa: mv88e6xxx: Add support for HW bridging Guenter Roeck
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=1424720150-27564-1-git-send-email-linux@roeck-us.net \
--to=linux@roeck-us.net \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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).