From: Andrew Lunn <andrew@lunn.ch>
To: Rafa?? Mi??ecki <zajec5@gmail.com>
Cc: "David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, Jonas Gorski <jogo@openwrt.org>,
Florian Fainelli <f.fainelli@gmail.com>,
Hauke Mehrtens <hauke@hauke-m.de>,
Felix Fietkau <nbd@openwrt.org>, Jiri Pirko <jiri@resnulli.us>
Subject: Re: [PATCH] net: phy: b53: switchdev driver for Broadcom BCM53xx switches
Date: Tue, 24 Feb 2015 22:51:55 +0100 [thread overview]
Message-ID: <20150224215155.GA15633@lunn.ch> (raw)
In-Reply-To: <1424799727-30946-1-git-send-email-zajec5@gmail.com>
On Tue, Feb 24, 2015 at 06:42:07PM +0100, Rafa?? Mi??ecki wrote:
> BCM53xx is series of Broadcom Ethernet switches that can be found in
> various (mostly home) routers.
> They are quite simple switches with mainly just support for:
> 1) Tagging incoming packets (PVID)
> 2) Untagging outgoing packets
> 3) Forwarding all packets across a single VLAN
>
> This driver is split into common code (module) and bus specific code.
> Right now only PHY (MDIO) support is included, other could follow after
> accepting this driver. It was successfully tested on BCM4706 SoC with
> BCM53125.
>
> You could notice it's yet another try of submitting b53 driver. This
> time it was modified to use recently introduced switchdev API which
> hopefully make it possible to accept it mainline.
>
> Signed-off-by: Rafa?? Mi??ecki <zajec5@gmail.com>
> ---
> Example usage. My BCM4706 router has switch with 6 ports:
> 0: WAN port
> 1-4: LAN ports
> 8: CPU connected port (on-SoC Ethernet device)
>
> I decided to use VLAN 1 for WAN and VLAN 2 for LAN. I was able to
> successfully configure it using:
>
> bridge vlan add vid 1 dev sw0p1 pvid untagged
> bridge vlan add vid 1 dev sw0p2 pvid untagged
> bridge vlan add vid 1 dev sw0p3 pvid untagged
> bridge vlan add vid 1 dev sw0p4 pvid untagged
> bridge vlan add vid 1 dev sw0p8
>
> bridge vlan add vid 2 dev sw0p0 pvid untagged
> bridge vlan add vid 2 dev sw0p8
> ---
> drivers/net/phy/Kconfig | 2 +
> drivers/net/phy/Makefile | 1 +
> drivers/net/phy/b53/Kconfig | 12 +
> drivers/net/phy/b53/Makefile | 2 +
> drivers/net/phy/b53/b53_common.c | 961 +++++++++++++++++++++++++++++++++++++++
> drivers/net/phy/b53/b53_mdio.c | 418 +++++++++++++++++
> drivers/net/phy/b53/b53_priv.h | 299 ++++++++++++
> drivers/net/phy/b53/b53_regs.h | 313 +++++++++++++
Hi Rafa??
I have a question about the location. Why drivers/net/phy?
Andrew
next prev parent reply other threads:[~2015-02-24 21:54 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 17:42 [PATCH] net: phy: b53: switchdev driver for Broadcom BCM53xx switches Rafał Miłecki
2015-02-24 17:47 ` Rafał Miłecki
2015-02-24 21:51 ` Andrew Lunn [this message]
2015-02-24 22:29 ` Rafał Miłecki
2015-02-25 0:51 ` Andrew Lunn
2015-02-24 22:30 ` Andy Gospodarek
2015-02-24 22:50 ` Rafał Miłecki
2015-02-24 22:55 ` Florian Fainelli
2015-02-25 0:15 ` Andrew Lunn
2015-02-25 0:39 ` Florian Fainelli
2015-02-25 7:03 ` Rafał Miłecki
2015-02-25 8:07 ` Jiri Pirko
2015-02-25 14:03 ` Andrew Lunn
2015-02-25 14:17 ` Rafał Miłecki
2015-02-25 14:19 ` Andrew Lunn
2015-02-26 14:58 ` Rafał Miłecki
2015-02-26 15:18 ` Andrew Lunn
2015-02-26 15:30 ` Rafał Miłecki
2015-02-26 15:36 ` Andrew Lunn
2015-02-26 15:49 ` Rafał Miłecki
2015-02-26 16:21 ` Andrew Lunn
2015-02-26 17:58 ` Florian Fainelli
2015-02-26 18:26 ` Scott Feldman
2015-02-26 17:57 ` Florian Fainelli
2015-02-25 15:46 ` Andy Gospodarek
2015-02-25 17:23 ` Rafał Miłecki
2015-02-25 21:56 ` Andrew Lunn
2015-02-26 0:53 ` Scott Feldman
2015-02-26 4:21 ` Andy Gospodarek
2015-02-26 6:47 ` Jiri Pirko
2015-02-26 7:14 ` B Viswanath
2015-02-26 14:13 ` Andy Gospodarek
2015-02-26 14:19 ` Scott Feldman
2015-02-26 14:44 ` Jiri Pirko
2015-02-27 22:21 ` David Miller
2015-02-26 17:52 ` Florian Fainelli
2015-02-26 17:51 ` Florian Fainelli
2015-02-25 6:44 ` Rafał Miłecki
2015-02-24 22:48 ` Florian Fainelli
2015-02-24 22:56 ` Rafał Miłecki
2015-02-24 22:59 ` Florian Fainelli
2015-02-25 2:10 ` David Miller
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=20150224215155.GA15633@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=hauke@hauke-m.de \
--cc=jiri@resnulli.us \
--cc=jogo@openwrt.org \
--cc=nbd@openwrt.org \
--cc=netdev@vger.kernel.org \
--cc=zajec5@gmail.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).