networking/dsa/sja1105.rst

39 VLAN Lookup                    yes                yes
81 Depending on VLAN awareness state, the following operating modes are possible
84 - Mode 1 (VLAN-unaware): a port is in this mode when it is used as a standalone
86 - Mode 2 (fully VLAN-aware): a port is in this mode when it is enslaved to a
87   bridge with ``vlan_filtering=1``. Access to the entire VLAN range is given to
92 - Mode 3 (best-effort VLAN-aware): a port is in this mode when enslaved to a
97   port*), and shared VLAN learning is performed (FDB lookup is done only by
122   [   61.204770] sja1105 spi0.1: Reset switch and programmed static config. Reason: VLAN filtering
126   [   64.682927] sja1105 spi0.1: Reset switch and programmed static config. Reason: VLAN filtering
155 \* "maximum of 7 non-pvid VLANs per port": Decoding VLAN-tagged packets on the
156 CPU in mode 3 is possible through VLAN retagging of packets that go from the
160 interested in this VLAN, they need to apply retagging in the reverse direction,
190 Also consider the following commands, that add VLAN 100 to every sja1105 user
237 SJA1105 switch 1 consumes 1 retagging entry for each VLAN on each user port
238 towards the CPU. It also consumes 1 retagging entry for each non-pvid VLAN that
247 - 3 retagging entries for VLAN 100 installed on the user ports of SJA1105
249   interested in it. The VLAN 1 is a pvid on SJA1105 switch 2 and does not need
256 - 4 retagging entries for VLAN 100 installed on the user ports of SJA1105
265 one bridge's ports from another's) or at the VLAN port membership level
269 The hardware tags all traffic internally with a port-based VLAN (pvid), or it
270 decodes the VLAN information from the 802.1Q tag. Advanced VLAN classification
271 is not possible. Once attributed a VLAN tag, frames are checked against the
272 port's membership rules and dropped at ingress if they don't match any VLAN.
276 Normally the hardware is not configurable with respect to VLAN awareness, but
282 all bridges should have the same level of VLAN awareness (either both have
284 that VLAN awareness is global at the switch level is that once a bridge with
327 on the VLAN PCP bits (if no VLAN is present, the port-based default is used).
329 ``vlan_filtering``, the EtherType recognized by the switch as being VLAN can
331 for tagging. Therefore, the switch ignores the VLAN PCP if used in standalone
336 offloaded flows can be steered to TX queues based on the VLAN PCP, but the DSA
338 queue with VLAN awareness active, it is necessary to create a VLAN
339 sub-interface on the DSA master port, and send normal (0x8100) VLAN-tagged
340 towards the switch, with the VLAN PCP bits set appropriately.
344 disregards any VLAN PCP bits even if present. The traffic class for management
403 - VLAN-aware virtual links: these match on destination MAC address, VLAN ID and
404   VLAN PCP.
405 - VLAN-unaware virtual links: these match on destination MAC address only.
407 The VLAN awareness state of the bridge (vlan_filtering) cannot be changed while
419 CPU and to swp3. This type of key (DA only) when the port's VLAN awareness
440 tuple composed of destination MAC address, VLAN ID and VLAN PCP). Packets which