linux.git/Documentation/networking/dsa, branch v5.13

Documentation: networking: dsa: mention that the master is brought up automatically

2021-03-17T19:34:35+00:00

Since commit 9d5ef190e561 ("net: dsa: automatically bring up DSA master
when opening user port"), DSA manages the administrative status of the
host port automatically. Update the configuration steps to reflect this.

Signed-off-by: Vladimir Oltean 
Signed-off-by: David S. Miller

Documentation: networking: dsa: demote subsections to simple emphasized words

2021-03-17T19:34:34+00:00

"make htmldocs" complains:
configuration.rst:165: WARNING: duplicate label networking/dsa/configuration:single port, other instance in (...)
configuration.rst:212: WARNING: duplicate label networking/dsa/configuration:bridge, other instance in (...)
configuration.rst:252: WARNING: duplicate label networking/dsa/configuration:gateway, other instance in (...)

And for good reason, because the "single port", "bridge" and "gateway"
use cases are replicated twice, once for normal taggers and twice for
DSA_TAG_PROTO_NONE. So when trying to reference these sections via a
hyperlink such as:

https://www.kernel.org/doc/html/latest/networking/dsa/configuration.html#single-port

it will always reference the first occurrence, and never the second one.

This change makes the "single port", "bridge" and "gateway"
configuration examples consistent with the formatting used in the
"Configuration showcases" subsection.

Signed-off-by: Vladimir Oltean 
Signed-off-by: David S. Miller

Documentation: networking: dsa: add missing new line in devlink section

2021-03-17T19:34:34+00:00

"make htmldocs" produces these warnings:
Documentation/networking/dsa/dsa.rst:468: WARNING: Unexpected indentation.
Documentation/networking/dsa/dsa.rst:477: WARNING: Block quote ends without a blank line; unexpected unindent.

Fixes: 8411abbcad8e ("Documentation: networking: dsa: mention integration with devlink")
Reported-by: Stephen Rothwell 
Signed-off-by: Vladimir Oltean 
Signed-off-by: David S. Miller

Documentation: networking: dsa: add paragraph for the HSR/PRP offload

2021-03-16T22:13:45+00:00

Add a short summary of the methods that a driver writer must implement
for offloading a HSR/PRP network interface.

Signed-off-by: Vladimir Oltean 
Reviewed-by: Florian Fainelli 
Reviewed-by: George McCollister 
Signed-off-by: David S. Miller

Documentation: networking: dsa: add paragraph for the MRP offload

2021-03-16T22:13:44+00:00

Add a short summary of the methods that a driver writer must implement
for getting an MRP instance to work on top of a DSA switch.

Cc: Horatiu Vultur 
Signed-off-by: Vladimir Oltean 
Reviewed-by: Horatiu Vultur 
Signed-off-by: David S. Miller

Documentation: networking: dsa: add paragraph for the LAG offload

2021-03-16T22:13:44+00:00

Add a short summary of the methods that a driver writer must implement
for offloading a link aggregation group, and what is still missing.

Cc: Tobias Waldekranz 
Signed-off-by: Vladimir Oltean 
Reviewed-by: Florian Fainelli 
Reviewed-by: Tobias Waldekranz 
Signed-off-by: David S. Miller

Documentation: networking: dsa: mention integration with devlink

2021-03-16T22:13:44+00:00

Add a short summary of the devlink features supported by the DSA core.

Signed-off-by: Vladimir Oltean 
Reviewed-by: Florian Fainelli 
Reviewed-by: Andrew Lunn 
Signed-off-by: David S. Miller

Documentation: networking: dsa: document the port_bridge_flags method

2021-03-16T22:13:44+00:00

The documentation was already lagging behind by not mentioning the old
version of port_bridge_flags (port_set_egress_floods). So now we are
skipping one step and just explaining how a DSA driver should configure
address learning and flooding settings.

Signed-off-by: Vladimir Oltean 
Reviewed-by: Florian Fainelli 
Reviewed-by: Andrew Lunn 
Signed-off-by: David S. Miller

Documentation: networking: dsa: remove TODO about porting more vendor drivers

2021-03-16T22:13:44+00:00

On one hand, the link is dead and therefore useless.

On the other hand, there are always more drivers to port, but at this
stage, DSA does not need to affirm itself as the driver model to use for
Ethernet-connected switches (since we already have 15 tagging protocols
supported and probably more switch families from various vendors), so
there is nothing actionable to do.

Signed-off-by: Vladimir Oltean 
Reviewed-by: Florian Fainelli 
Reviewed-by: Andrew Lunn 
Signed-off-by: David S. Miller

Documentation: networking: dsa: remove references to switchdev prepare/commit

2021-03-16T22:13:44+00:00

After the recent series containing commit bae33f2b5afe ("net: switchdev:
remove the transaction structure from port attributes"), there aren't
prepare/commit transactional phases anymore in most of the switchdev
objects/attributes, and as a result, there aren't any in the DSA driver
API either. So remove this piece.

Signed-off-by: Vladimir Oltean 
Reviewed-by: Florian Fainelli 
Reviewed-by: Andrew Lunn 
Signed-off-by: David S. Miller