linux.git/net/dsa/switch.c, branch v4.15

Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net

2017-11-12T00:17:05+00:00

net: dsa: return after vlan prepare phase

2017-11-11T06:45:09+00:00

The current code does not return after successfully preparing the VLAN
addition on every ports member of a it. Fix this.

Fixes: 1ca4aa9cd4cc ("net: dsa: check VLAN capability of every switch")
Signed-off-by: Vivien Didelot 
Reviewed-by: Andrew Lunn 
Signed-off-by: David S. Miller

net: dsa: return after mdb prepare phase

2017-11-11T06:45:09+00:00

The current code does not return after successfully preparing the MDB
addition on every ports member of a multicast group. Fix this.

Fixes: a1a6b7ea7f2d ("net: dsa: add cross-chip multicast support")
Reported-by: Egil Hjelmeland 
Signed-off-by: Vivien Didelot 
Reviewed-by: Andrew Lunn 
Signed-off-by: David S. Miller

net: dsa: switch: Don't add CPU port to an mdb by default

2017-11-10T04:41:40+00:00

Now that the host indicates when a multicast group should be forwarded
from the switch to the host, don't do it by default.

Signed-off-by: Andrew Lunn 
Signed-off-by: David S. Miller

net: dsa: Remove switchdev dependency from DSA switch notifier chain

2017-08-07T21:48:48+00:00

Currently, the switchdev objects are embedded inside the DSA notifier
info. This patch removes this dependency. This is done as a preparation
stage before adding support for learning FDB through the switchdev
notification chain.

Signed-off-by: Arkadi Sharshevsky 
Reviewed-by: Florian Fainelli 
Reviewed-by: Vivien Didelot 
Signed-off-by: David S. Miller

net: dsa: Remove prepare phase for FDB

2017-08-07T21:48:47+00:00

The prepare phase for FDB add is unneeded because most of DSA devices
can have failures during bus transactions (SPI, I2C, etc.), thus, the
prepare phase cannot guarantee success of the commit stage.

The support for learning FDB through notification chain, which will be
introduced in the following patches, will provide the ability to notify
back the bridge about successful offload.

Signed-off-by: Arkadi Sharshevsky 
Reviewed-by: Vivien Didelot 
Reviewed-by: Florian Fainelli 
Signed-off-by: David S. Miller

net: dsa: Change DSA slave FDB API to be switchdev independent

2017-08-07T21:48:47+00:00

In order to support FDB add/del to be on a notifier chain the slave
API need to be changed to be switchdev independent.

Signed-off-by: Arkadi Sharshevsky 
Reviewed-by: Vivien Didelot 
Reviewed-by: Florian Fainelli 
Signed-off-by: David S. Miller

net: dsa: add cross-chip multicast support

2017-06-16T19:21:14+00:00

Similarly to how cross-chip VLAN works, define a bitmap of multicast
group members for a switch, now including its DSA ports, so that
multicast traffic can be sent to all switches of the fabric.

A switch may drop the frames if no user port is a member.

This brings support for multicast in a multi-chip environment.
As of now, all switches of the fabric must support the multicast
operations in order to program a single fabric port.

Reported-by: Jason Cobham 
Signed-off-by: Vivien Didelot 
Tested-by: Jason Cobham 
Reviewed-by: Florian Fainelli 
Signed-off-by: David S. Miller

net: dsa: add CPU and DSA ports as VLAN members

2017-06-08T15:43:32+00:00

In a multi-chip switch fabric, it is currently the responsibility of the
driver to add the CPU or DSA (interconnecting chips together) ports as
members of a new VLAN entry. This makes the drivers more complicated.

We want the DSA drivers to be stupid and the DSA core being the one
responsible for caring about the abstracted switch logic and topology.

Make the DSA core program the CPU and DSA ports as part of the VLAN.

This makes all chips of the data path to be aware of VIDs spanning the
the whole fabric and thus, seamlessly add support for cross-chip VLAN.

Reviewed-by: Florian Fainelli 
Signed-off-by: Vivien Didelot 
Signed-off-by: David S. Miller

net: dsa: check VLAN capability of every switch

2017-06-08T15:43:31+00:00

Now that the VLAN object is propagated to every switch chip of the
switch fabric, we can easily ensure that they all support the required
VLAN operations before modifying an entry on a single switch.

To achieve that, remove the condition skipping other target switches,
and add a bitmap of VLAN members, eventually containing the target port,
if we are programming the switch target.

This will allow us to easily add other VLAN members, such as the DSA or
CPU ports (to introduce cross-chip VLAN support) or the other port
members if we want to reduce hardware accesses later.

Reviewed-by: Florian Fainelli 
Signed-off-by: Vivien Didelot 
Signed-off-by: David S. Miller