* DSA Switch: query: Switch configuration, data plane doesn't work whereas control plane works
@ 2024-12-24 9:30 sai kumar
2024-12-24 12:00 ` Vladimir Oltean
2024-12-25 17:53 ` Andrew Lunn
0 siblings, 2 replies; 7+ messages in thread
From: sai kumar @ 2024-12-24 9:30 UTC (permalink / raw)
To: netdev
Hi Team,
This could be basic question related to DSA, if possible please help
to share your feedback,. Thanks.
External CPU eth1 ---RGMII---- Switch Port 0 (cpu port)
Switch Port 1 (lan1) --- DHCP client
I am using marvell 88E6390 evaluation board, modified the device tree
to support MDIO control over USB.
The switch control plane works, we are unable to dump registers and
see port status.
The kernel version on board with external cpu is 6.1
I have connected a dhcp client to port 1 of the switch and the
discover packet is not reaching the cpu port (port 0) and external cpu
interface eth1.
Using the bridge without vlan to configure, able to see the client
device mac addr in bridge fdb show
with vlan id as 4095.
tcpdump on external cpu port eth1 and bridge br0 to listen for
incoming packets from the client . No discover packets are being
received on those interfaces.
Could you please let us know if any configuration is being missed for
switch data plane to work ? Thanks.
The below are the commands used to configure the bridge:
ip link set eth1 up
ip link set lan1 up
ip link set lan2 up
ip link set lan3 up
ip link set lan4 up
ip link set lan5 up
ip link set lan6 up
ip link set lan7 up
ip link set lan8 up
ip link add br0 type bridge
ip link set br0 up
ip link set lan1 master br0
ip link set lan2 master br0
ip link set lan3 master br0
ip link set lan4 master br0
ip link set lan5 master br0
ip link set lan6 master br0
ip link set lan7 master br0
ip link set lan8 master br0
bridge link show
6: lan1@eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 master br0
state forwarding priority 32 cost 19
7: lan2@eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 master br0
state disabled priority 32 cost 100
8: lan3@eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 master br0
state disabled priority 32 cost 100
9: lan4@eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 master br0
state disabled priority 32 cost 100
10: lan5@eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 master br0
state disabled priority 32 cost 100
11: lan6@eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 master br0
state disabled priority 32 cost 100
12: lan7@eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 master br0
state disabled priority 32 cost 100
13: lan8@eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 master br0
state disabled priority 32 cost 100
bridge vlan show
port vlan-id
bridge fdb show
xx:xx:xx:01:cf:c1 dev lan1 master br0 permanent
xx:xx:xx:8e:27:01 dev lan1 vlan 4095 self
Below are the debug logs:
./mv88e6xxx_dump --ports
Using device <mdio_bus/mvusb-1-1:1.0:00>
0 1 2 3 4 5 6 7 8 9 10
00 Port status 0e07 1d0f 100f 100f 100f 100f 100f 100f 100f 0049 0049
01 Physical control e03e 0003 0003 0003 0003 0003 0003 0003 0003 0003 0003
02 Flow control 0100 0100 0100 0100 0100 0100 0100 0100 0100 0000 0000
03 Switch ID 3901 3901 3901 3901 3901 3901 3901 3901 3901 3901 3901
04 Port control 013f 043f 043c 043c 043c 043c 043c 043c 043c 007c 007c
05 Port control 1 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
06 Port base VLAN map 07fe 01fd 01fb 01f7 01ef 01df 01bf 017f 00ff 05ff 03ff
07 Def VLAN ID & Prio 0000 0fff 0fff 0fff 0fff 0fff 0fff 0fff 0fff 0001 0001
08 Port control 2 2c80 2080 2080 2080 2080 2080 2080 2080 2080 2080 2080
09 Egress rate control 0001 0001 0001 0001 0001 0001 0001 0001 0001 0001 0001
0a Egress rate control 2 0000 0000 0000 0000 0000 0000 0000 0000 0000 8000 8000
0b Port association vec 0001 0002 0004 0008 0010 0020 0040 0080 0100 0200 0400
0c Port ATU control 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0d Override 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0e Policy control 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0f Port ether type 9100 9100 9100 9100 9100 9100 9100 9100 9100 9100 9100
10 Reserved 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
11 Reserved 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
12 Reserved 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
13 Reserved 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
14 Reserved 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
15 Reserved 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
16 LED control 0000 0033 0033 0033 0033 0033 0033 0033 0033 0033 0033
17 IP prio map table 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
18 IEEE prio map table 3e07 3e07 3e07 3e07 3e07 3e07 3e07 3e07 3e07 0000 0000
19 Port control 3 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
1a Reserved 0000 0000 0000 0000 7d40 01c0 0000 0000 0000 0000 0000
1b Queue counters 8000 8000 8000 8000 8000 8000 8000 8000 8000 8000 8000
1c Queue control 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
1d Reserved 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
1e Cut through control 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
1f Debug counters 0000 009f 0000 0000 0000 0000 0000 0000 0000 0000 0000
./mv88e6xxx_dump --port 0
Using device <mdio_bus/mvusb-1-1:1.0:00>
00 Port status 0x0e07
Transmit Pause Enable bit 0
Receive Pause Enable bit 0
802.3 PHY Detected 0
Link Status Up
Duplex Full
Speed 1000 Mbps
Duplex Fixed 0
EEE Enabled 0
Transmitter Paused 0
Flow Control 0
Config Mode 0x7
01 Physical control 0xe03e
RGMII Receive Timing Control Delay
RGMII Transmit Timing Control Delay
Force Speed 1
Alternate Speed Mode Normal
MII PHY Mode MAC
EEE force value 0
Force EEE 0
Link's Forced value Up
Force Link 1
Duplex's Forced value Full
Force Duplex 1
Force Speed 1000 Mbps
02 Flow control 0x0100
03 Switch ID 0x3901
04 Port control 0x013f
Source Address Filtering controls Disabled
Egress Mode Unmodified
Ingress & Egress Header Mode 0
IGMP and MLD Snooping 0
Frame Mode DSA
VLAN Tunnel 0
TagIfBoth 0
Initial Priority assignment Tag & IP Priority
Egress Flooding mode Allow unknown DA
Port State Forwarding
05 Port control 1 0x0000
Message Port 0
LAG Port 0
VTU Page 0
LAG ID 0
FID[11:4] 0x000
06 Port base VLAN map 0x07fe
FID[3:0] 0x000
Force Mapping 0
VLANTable 1 2 3 4 5 6 7 8 9 10
07 Def VLAN ID & Prio 0x0000
Default Priority 0x0
Force to use Default VID 0
Default VLAN Identifier 0
08 Port control 2 0x2c80
Force good FCS in the frame 0
Allow bad FCS 0
Jumbo Mode 10240
802.1QMode Secure
Discard Tagged Frames 0
Discard Untagged Frames 0
Map using DA hits 1
ARP Mirror enable 0
Egress Monitor Source Port 0
Ingress Monitor Source Port 0
Allow VID of Zero 0
Default Queue Priority 0x0
09 Egress rate control 0x0001
0a Egress rate control 2 0x0000
0b Port association vec 0x0001
0c Port ATU control 0x0000
0d Override 0x0000
0e Policy control 0x0000
0f Port ether type 0x9100
10 Reserved 0x0000
11 Reserved 0x0000
12 Reserved 0x0000
13 Reserved 0x0000
14 Reserved 0x0000
15 Reserved 0x0000
16 LED control 0x0000
17 IP prio map table 0x0000
18 IEEE prio map table 0x3e07
19 Port control 3 0x0000
1a Reserved 0x0000
1b Queue counters 0x8000
1c Queue control 0x0000
1d Reserved 0x0000
1e Cut through control 0x0000
1f Debug counters 0x0000
./mv88e6xxx_dump --port 1
Using device <mdio_bus/mvusb-1-1:1.0:00>
00 Port status 0x1d0f
Transmit Pause Enable bit 0
Receive Pause Enable bit 0
802.3 PHY Detected 1
Link Status Up
Duplex Full
Speed 100 or 200 Mbps
Duplex Fixed 0
EEE Enabled 0
Transmitter Paused 0
Flow Control 0
Config Mode 0xf
01 Physical control 0x0003
RGMII Receive Timing Control Default
RGMII Transmit Timing Control Default
Force Speed 0
Alternate Speed Mode Normal
MII PHY Mode MAC
EEE force value 0
Force EEE 0
Link's Forced value Down
Force Link 0
Duplex's Forced value Half
Force Duplex 0
Force Speed 10 Gb or 2500 Mbps
02 Flow control 0x0100
03 Switch ID 0x3901
04 Port control 0x043f
Source Address Filtering controls Disabled
Egress Mode Unmodified
Ingress & Egress Header Mode 0
IGMP and MLD Snooping 1
Frame Mode Normal
VLAN Tunnel 0
TagIfBoth 0
Initial Priority assignment Tag & IP Priority
Egress Flooding mode Allow unknown DA
Port State Forwarding
05 Port control 1 0x0000
Message Port 0
LAG Port 0
VTU Page 0
LAG ID 0
FID[11:4] 0x000
06 Port base VLAN map 0x01fd
FID[3:0] 0x000
Force Mapping 0
VLANTable 0 2 3 4 5 6 7 8
07 Def VLAN ID & Prio 0x0fff
Default Priority 0x0
Force to use Default VID 0
Default VLAN Identifier 4095
08 Port control 2 0x2080
Force good FCS in the frame 0
Allow bad FCS 0
Jumbo Mode 10240
802.1QMode Disabled
Discard Tagged Frames 0
Discard Untagged Frames 0
Map using DA hits 1
ARP Mirror enable 0
Egress Monitor Source Port 0
Ingress Monitor Source Port 0
Allow VID of Zero 0
Default Queue Priority 0x0
09 Egress rate control 0x0001
0a Egress rate control 2 0x0000
0b Port association vec 0x0002
0c Port ATU control 0x0000
0d Override 0x0000
0e Policy control 0x0000
0f Port ether type 0x9100
10 Reserved 0x0000
11 Reserved 0x0000
12 Reserved 0x0000
13 Reserved 0x0000
14 Reserved 0x0000
15 Reserved 0x0000
16 LED control 0x0033
17 IP prio map table 0x0000
18 IEEE prio map table 0x3e07
19 Port control 3 0x0000
1a Reserved 0x0000
1b Queue counters 0x8000
1c Queue control 0x0000
1d Reserved 0x0000
1e Cut through control 0x0000
1f Debug counters 0x00a1
./mv88e6xxx_dump --vtu
Using device <mdio_bus/mvusb-1-1:1.0:00>
VTU:
V - a member, egress not modified
U - a member, egress untagged
T - a member, egress tagged
X - not a member, Ingress frames with VID discarded
P VID 0123456789a FID SID QPrio FPrio VidPolicy
0 0 VVVVVVVVVVV 0 0 - - 1
0 4095 VVVVVVVVVVV 1 0 - - 0
./mv88e6xxx_dump --atu
Using device <mdio_bus/mvusb-1-1:1.0:00>
ATU:
FID MAC T 0123456789A Prio State
1 xx:xx:xx:01:cf:c1 10000000000 0 Static
1 xx:xx:xx:8e:27:01 01000000000 0 Age 7
1 ff:ff:ff:ff:ff:ff 11111111100 0 Static
./mv88e6xxx_dump --global1
Using device <mdio_bus/mvusb-1-1:1.0:00>
Global1:
00 Global status c801
01 ATU FID 0001
02 VTU FID 0001
03 VTU SID 0000
04 Global control 40a8
05 VTU operations 4000
06 VTU VID 2fff
07 VTU/STU Data 0-7 0000
08 VTU/STU Data 8-10 003c
09 Reserved 0000
0a ATU control 0509
0b ATU operations 4000
0c ATU data 1ff7
0d ATU MAC bytes 0 & 1 ffff
0e ATU MAC bytes 2 & 3 ffff
0f ATU MAC bytes 4 & 5 ffff
10 Reserved 0000
11 Reserved 0000
12 Reserved 0000
13 Reserved 0000
14 Reserved 0000
15 Reserved 0000
16 Reserved 0000
17 Reserved 0000
18 Reserved 0000
19 Reserved 0000
1a Monitor & management Control 03ff
1b Total free counter 03fe
1c Global control 2 07c0
1d Stats operation 441f
1e Stats counter bytes 3 & 2 0000
1f Stats counter bytes 1 & 0 0000
./mv88e6xxx_dump --global2
Using device <mdio_bus/mvusb-1-1:1.0:00>
Global2:
00 Interrupt source 0000
01 Interrupt mask 81fe
02 Reserved 0000
03 Reserved 0000
04 Flow control delays 0258
05 Managment 0400
06 Device mapping 1f1f
07 LAG mask 77ff
08 LAG mapping 7800
09 Ingress rate command 2a00
0a Ingress rate data 0000
0b Cross chip port VLAN addr 3010
0c Cross chip port VLAN data 01ff
0d Switch MAC/WoL/WoF 0542
0e ATU Stats 0003
0f Priority override table 0f00
10 Reserved 0000
11 Reserved 0000
12 Energy management 0000
13 IMP comm/debug 0303
14 EEPROM command 0000
15 EEPROM addr 0000
16 AVB/TSN command 0000
17 AVB/TSN data 0000
18 SMI PHY command 1456
19 SMI PHY data 0000
1a Scratch & Misc 0000
1b Watchdog control 1100
1c QoS Weights 0000
1d Misc 0000
1e Reserved 0000
1f Cut through control 0000
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: DSA Switch: query: Switch configuration, data plane doesn't work whereas control plane works
2024-12-24 9:30 DSA Switch: query: Switch configuration, data plane doesn't work whereas control plane works sai kumar
@ 2024-12-24 12:00 ` Vladimir Oltean
2024-12-24 12:50 ` sai kumar
2024-12-25 17:53 ` Andrew Lunn
1 sibling, 1 reply; 7+ messages in thread
From: Vladimir Oltean @ 2024-12-24 12:00 UTC (permalink / raw)
To: sai kumar; +Cc: netdev
On Tue, Dec 24, 2024 at 03:00:17PM +0530, sai kumar wrote:
> Hi Team,
>
> This could be basic question related to DSA, if possible please help
> to share your feedback,. Thanks.
>
>
> External CPU eth1 ---RGMII---- Switch Port 0 (cpu port)
> Switch Port 1 (lan1) --- DHCP client
>
> I am using marvell 88E6390 evaluation board, modified the device tree
> to support MDIO control over USB.
> The switch control plane works, we are unable to dump registers and
unable -> able, right?
> see port status.
>
> The kernel version on board with external cpu is 6.1
>
> I have connected a dhcp client to port 1 of the switch and the
> discover packet is not reaching the cpu port (port 0) and external cpu
> interface eth1.
> Using the bridge without vlan to configure, able to see the client
> device mac addr in bridge fdb show
> with vlan id as 4095.
>
> tcpdump on external cpu port eth1 and bridge br0 to listen for
> incoming packets from the client . No discover packets are being
> received on those interfaces.
>
> Could you please let us know if any configuration is being missed for
> switch data plane to work ? Thanks.
>
>
> The below are the commands used to configure the bridge:
I don't immediately see something obviously wrong. Could you run
ethtool -S on lan1 and on eth0, and try to find a positive correlation
between the DHCP requests and a certain packet counter incrementing in
the switch? We should determine whether there is packet loss in the
switch or whether there is some other reason for the lack of connectivity.
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: DSA Switch: query: Switch configuration, data plane doesn't work whereas control plane works
2024-12-24 12:00 ` Vladimir Oltean
@ 2024-12-24 12:50 ` sai kumar
2024-12-24 16:00 ` Vladimir Oltean
0 siblings, 1 reply; 7+ messages in thread
From: sai kumar @ 2024-12-24 12:50 UTC (permalink / raw)
To: Vladimir Oltean; +Cc: netdev
Thanks Vladimir for your inputs.
I tried checking the statistics, the in_broadcasts count increases
with respect to client dhcp discover broadcasts.
But the same is not happening with external cpu port eth1, the eth1
in_broadcasts and in_accepted are 0 , Observing the rx frame errors on
eth1 but
this count doesn't match to the clients broadcast packets count.
ethtool -S lan1
NIC statistics:
tx_packets: 7
tx_bytes: 626
rx_packets: 0
rx_bytes: 0
in_good_octets: 18112
in_bad_octets: 0
in_unicast: 0
in_broadcasts: 51
in_multicasts: 5
in_pause: 0
in_undersize: 0
in_fragments: 0
in_oversize: 0
in_jabber: 0
in_rx_error: 0
in_fcs_error: 0
out_octets: 7792
out_unicast: 0
out_broadcasts: 105
out_multicasts: 12
out_pause: 0
excessive: 0
collisions: 0
deferred: 0
single: 0
multiple: 0
out_fcs_error: 0
late: 0
hist_64bytes: 105
hist_65_127bytes: 17
hist_128_255bytes: 0
hist_256_511bytes: 51
hist_512_1023bytes: 0
hist_1024_max_bytes: 0
in_discards: 0
in_filtered: 0
in_accepted: 56
in_bad_accepted: 0
in_good_avb_class_a: 0
in_good_avb_class_b: 0
in_bad_avb_class_a: 0
in_bad_avb_class_b: 0
tcam_counter_0: 0
tcam_counter_1: 0
tcam_counter_2: 0
tcam_counter_3: 0
in_da_unknown: 5
in_management: 4
out_queue_0: 117
out_queue_1: 0
out_queue_2: 0
out_queue_3: 0
out_queue_4: 0
out_queue_5: 0
out_queue_6: 0
out_queue_7: 0
out_cut_through: 0
out_octets_a: 0
out_octets_b: 0
out_management: 0
atu_member_violation: 0
atu_miss_violation: 0
atu_full_violation: 0
vtu_member_violation: 0
vtu_miss_violation: 0
ethtool -S eth1
NIC statistics:
interrupts [CPU 0]: 12
interrupts [CPU 1]: 9
interrupts [CPU 2]: 5
interrupts [CPU 3]: 7
interrupts [TOTAL]: 33
rx packets [CPU 0]: 0
rx packets [CPU 1]: 0
rx packets [CPU 2]: 0
rx packets [CPU 3]: 0
rx packets [TOTAL]: 0
tx packets [CPU 0]: 2
tx packets [CPU 1]: 0
tx packets [CPU 2]: 12
tx packets [CPU 3]: 0
tx packets [TOTAL]: 14
tx recycled [CPU 0]: 0
tx recycled [CPU 1]: 0
tx recycled [CPU 2]: 0
tx recycled [CPU 3]: 0
tx recycled [TOTAL]: 0
tx confirm [CPU 0]: 6
tx confirm [CPU 1]: 3
tx confirm [CPU 2]: 2
tx confirm [CPU 3]: 3
tx confirm [TOTAL]: 14
tx S/G [CPU 0]: 0
tx S/G [CPU 1]: 0
tx S/G [CPU 2]: 0
tx S/G [CPU 3]: 0
tx S/G [TOTAL]: 0
rx S/G [CPU 0]: 0
rx S/G [CPU 1]: 0
rx S/G [CPU 2]: 0
rx S/G [CPU 3]: 0
rx S/G [TOTAL]: 0
tx error [CPU 0]: 0
tx error [CPU 1]: 0
tx error [CPU 2]: 0
tx error [CPU 3]: 0
tx error [TOTAL]: 0
rx error [CPU 0]: 6
rx error [CPU 1]: 6
rx error [CPU 2]: 3
rx error [CPU 3]: 4
rx error [TOTAL]: 19
bp count [CPU 0]: 128
bp count [CPU 1]: 128
bp count [CPU 2]: 128
bp count [CPU 3]: 128
bp count [TOTAL]: 512
rx dma error: 0
rx frame physical error: 2
rx frame size error: 17
rx header error: 0
rx csum error: 0
qman cg_tdrop: 0
qman wred: 0
qman error cond: 0
qman early window: 0
qman late window: 0
qman fq tdrop: 0
qman fq retired: 0
qman orp disabled: 0
congestion time (ms): 0
entered congestion: 0
congested (0/1): 0
p00_in_good_octets: 0
p00_in_bad_octets: 2
p00_in_unicast: 0
p00_in_broadcasts: 0
p00_in_multicasts: 0
p00_in_pause: 0
p00_in_undersize: 0
p00_in_fragments: 0
p00_in_oversize: 0
p00_in_jabber: 0
p00_in_rx_error: 1
p00_in_fcs_error: 0
p00_out_octets: 45440
p00_out_unicast: 0
p00_out_broadcasts: 312
p00_out_multicasts: 63
p00_out_pause: 0
p00_excessive: 0
p00_collisions: 0
p00_deferred: 0
p00_single: 0
p00_multiple: 0
p00_out_fcs_error: 0
p00_late: 0
p00_hist_64bytes: 0
p00_hist_65_127bytes: 306
p00_hist_128_255bytes: 8
p00_hist_256_511bytes: 61
p00_hist_512_1023bytes: 0
p00_hist_1024_max_bytes: 0
p00_in_discards: 0
p00_in_filtered: 0
p00_in_accepted: 0
p00_in_bad_accepted: 0
p00_in_good_avb_class_a: 0
p00_in_good_avb_class_b: 0
p00_in_bad_avb_class_a: 0
p00_in_bad_avb_class_b: 0
p00_tcam_counter_0: 0
p00_tcam_counter_1: 0
p00_tcam_counter_2: 0
p00_tcam_counter_3: 0
p00_in_da_unknown: 0
p00_in_management: 0
p00_out_queue_0: 373
p00_out_queue_1: 0
p00_out_queue_2: 0
p00_out_queue_3: 0
p00_out_queue_4: 0
p00_out_queue_5: 0
p00_out_queue_6: 2
p00_out_queue_7: 0
p00_out_cut_through: 0
p00_out_octets_a: 0
p00_out_octets_b: 0
p00_out_management: 11
p00_atu_member_violation: 0
p00_atu_miss_violation: 0
p00_atu_full_violation: 0
p00_vtu_member_violation: 0
p00_vtu_miss_violation: 0
On Tue, Dec 24, 2024 at 5:30 PM Vladimir Oltean <olteanv@gmail.com> wrote:
>
> On Tue, Dec 24, 2024 at 03:00:17PM +0530, sai kumar wrote:
> > Hi Team,
> >
> > This could be basic question related to DSA, if possible please help
> > to share your feedback,. Thanks.
> >
> >
> > External CPU eth1 ---RGMII---- Switch Port 0 (cpu port)
> > Switch Port 1 (lan1) --- DHCP client
> >
> > I am using marvell 88E6390 evaluation board, modified the device tree
> > to support MDIO control over USB.
> > The switch control plane works, we are unable to dump registers and
>
> unable -> able, right?
[SK] Yes, typo it was able.
>
> > see port status.
> >
> > The kernel version on board with external cpu is 6.1
> >
> > I have connected a dhcp client to port 1 of the switch and the
> > discover packet is not reaching the cpu port (port 0) and external cpu
> > interface eth1.
> > Using the bridge without vlan to configure, able to see the client
> > device mac addr in bridge fdb show
> > with vlan id as 4095.
> >
> > tcpdump on external cpu port eth1 and bridge br0 to listen for
> > incoming packets from the client . No discover packets are being
> > received on those interfaces.
> >
> > Could you please let us know if any configuration is being missed for
> > switch data plane to work ? Thanks.
> >
> >
> > The below are the commands used to configure the bridge:
>
> I don't immediately see something obviously wrong. Could you run
> ethtool -S on lan1 and on eth0, and try to find a positive correlation
> between the DHCP requests and a certain packet counter incrementing in
> the switch? We should determine whether there is packet loss in the
> switch or whether there is some other reason for the lack of connectivity.
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: DSA Switch: query: Switch configuration, data plane doesn't work whereas control plane works
2024-12-24 12:50 ` sai kumar
@ 2024-12-24 16:00 ` Vladimir Oltean
2024-12-25 8:53 ` sai kumar
0 siblings, 1 reply; 7+ messages in thread
From: Vladimir Oltean @ 2024-12-24 16:00 UTC (permalink / raw)
To: sai kumar; +Cc: netdev
On Tue, Dec 24, 2024 at 06:20:38PM +0530, sai kumar wrote:
> Thanks Vladimir for your inputs.
>
> I tried checking the statistics, the in_broadcasts count increases
> with respect to client dhcp discover broadcasts.
> But the same is not happening with external cpu port eth1, the eth1
> in_broadcasts and in_accepted are 0 , Observing the rx frame errors on
> eth1 but
> this count doesn't match to the clients broadcast packets count.
>
> ethtool -S lan1
> NIC statistics:
> tx_packets: 7
> tx_bytes: 626
> rx_packets: 0
> rx_bytes: 0
> in_good_octets: 18112
> in_bad_octets: 0
> in_unicast: 0
> in_broadcasts: 51
> in_multicasts: 5
> in_pause: 0
> in_undersize: 0
> in_fragments: 0
> in_oversize: 0
> in_jabber: 0
> in_rx_error: 0
> in_fcs_error: 0
> out_octets: 7792
> out_unicast: 0
> out_broadcasts: 105
> out_multicasts: 12
> out_pause: 0
> excessive: 0
> collisions: 0
> deferred: 0
> single: 0
> multiple: 0
> out_fcs_error: 0
> late: 0
> hist_64bytes: 105
> hist_65_127bytes: 17
> hist_128_255bytes: 0
> hist_256_511bytes: 51
> hist_512_1023bytes: 0
> hist_1024_max_bytes: 0
> in_discards: 0
> in_filtered: 0
> in_accepted: 56
> in_bad_accepted: 0
> in_good_avb_class_a: 0
> in_good_avb_class_b: 0
> in_bad_avb_class_a: 0
> in_bad_avb_class_b: 0
> tcam_counter_0: 0
> tcam_counter_1: 0
> tcam_counter_2: 0
> tcam_counter_3: 0
> in_da_unknown: 5
> in_management: 4
> out_queue_0: 117
> out_queue_1: 0
> out_queue_2: 0
> out_queue_3: 0
> out_queue_4: 0
> out_queue_5: 0
> out_queue_6: 0
> out_queue_7: 0
> out_cut_through: 0
> out_octets_a: 0
> out_octets_b: 0
> out_management: 0
> atu_member_violation: 0
> atu_miss_violation: 0
> atu_full_violation: 0
> vtu_member_violation: 0
> vtu_miss_violation: 0
>
>
> ethtool -S eth1
> NIC statistics:
> interrupts [CPU 0]: 12
> interrupts [CPU 1]: 9
> interrupts [CPU 2]: 5
> interrupts [CPU 3]: 7
> interrupts [TOTAL]: 33
> rx packets [CPU 0]: 0
> rx packets [CPU 1]: 0
> rx packets [CPU 2]: 0
> rx packets [CPU 3]: 0
> rx packets [TOTAL]: 0
> tx packets [CPU 0]: 2
> tx packets [CPU 1]: 0
> tx packets [CPU 2]: 12
> tx packets [CPU 3]: 0
> tx packets [TOTAL]: 14
> tx recycled [CPU 0]: 0
> tx recycled [CPU 1]: 0
> tx recycled [CPU 2]: 0
> tx recycled [CPU 3]: 0
> tx recycled [TOTAL]: 0
> tx confirm [CPU 0]: 6
> tx confirm [CPU 1]: 3
> tx confirm [CPU 2]: 2
> tx confirm [CPU 3]: 3
> tx confirm [TOTAL]: 14
> tx S/G [CPU 0]: 0
> tx S/G [CPU 1]: 0
> tx S/G [CPU 2]: 0
> tx S/G [CPU 3]: 0
> tx S/G [TOTAL]: 0
> rx S/G [CPU 0]: 0
> rx S/G [CPU 1]: 0
> rx S/G [CPU 2]: 0
> rx S/G [CPU 3]: 0
> rx S/G [TOTAL]: 0
> tx error [CPU 0]: 0
> tx error [CPU 1]: 0
> tx error [CPU 2]: 0
> tx error [CPU 3]: 0
> tx error [TOTAL]: 0
> rx error [CPU 0]: 6
> rx error [CPU 1]: 6
> rx error [CPU 2]: 3
> rx error [CPU 3]: 4
> rx error [TOTAL]: 19
> bp count [CPU 0]: 128
> bp count [CPU 1]: 128
> bp count [CPU 2]: 128
> bp count [CPU 3]: 128
> bp count [TOTAL]: 512
> rx dma error: 0
> rx frame physical error: 2
> rx frame size error: 17
> rx header error: 0
> rx csum error: 0
> qman cg_tdrop: 0
> qman wred: 0
> qman error cond: 0
> qman early window: 0
> qman late window: 0
> qman fq tdrop: 0
> qman fq retired: 0
> qman orp disabled: 0
> congestion time (ms): 0
> entered congestion: 0
> congested (0/1): 0
> p00_in_good_octets: 0
> p00_in_bad_octets: 2
> p00_in_unicast: 0
> p00_in_broadcasts: 0
> p00_in_multicasts: 0
> p00_in_pause: 0
> p00_in_undersize: 0
> p00_in_fragments: 0
> p00_in_oversize: 0
> p00_in_jabber: 0
> p00_in_rx_error: 1
> p00_in_fcs_error: 0
> p00_out_octets: 45440
> p00_out_unicast: 0
> p00_out_broadcasts: 312
> p00_out_multicasts: 63
> p00_out_pause: 0
> p00_excessive: 0
> p00_collisions: 0
> p00_deferred: 0
> p00_single: 0
> p00_multiple: 0
> p00_out_fcs_error: 0
> p00_late: 0
> p00_hist_64bytes: 0
> p00_hist_65_127bytes: 306
> p00_hist_128_255bytes: 8
> p00_hist_256_511bytes: 61
> p00_hist_512_1023bytes: 0
> p00_hist_1024_max_bytes: 0
> p00_in_discards: 0
> p00_in_filtered: 0
> p00_in_accepted: 0
> p00_in_bad_accepted: 0
> p00_in_good_avb_class_a: 0
> p00_in_good_avb_class_b: 0
> p00_in_bad_avb_class_a: 0
> p00_in_bad_avb_class_b: 0
> p00_tcam_counter_0: 0
> p00_tcam_counter_1: 0
> p00_tcam_counter_2: 0
> p00_tcam_counter_3: 0
> p00_in_da_unknown: 0
> p00_in_management: 0
> p00_out_queue_0: 373
> p00_out_queue_1: 0
> p00_out_queue_2: 0
> p00_out_queue_3: 0
> p00_out_queue_4: 0
> p00_out_queue_5: 0
> p00_out_queue_6: 2
> p00_out_queue_7: 0
> p00_out_cut_through: 0
> p00_out_octets_a: 0
> p00_out_octets_b: 0
> p00_out_management: 11
> p00_atu_member_violation: 0
> p00_atu_miss_violation: 0
> p00_atu_full_violation: 0
> p00_vtu_member_violation: 0
> p00_vtu_miss_violation: 0
Hmmm....
I recognize the ethtool stats as belonging to the DPAA1 Ethernet driver.
And I see that the Marvell 6390 has undocumented EDSA tag support, thus
using DSA (with no EtherType) by default. This reminds me of this
discussion with Tobias Waldekranz. The FMan parser sees errors due to
the somewhat controversial Marvell original DSA tag decisions:
https://lore.kernel.org/netdev/20210323102326.3677940-1-tobias@waldekranz.com/
Could you please force EDSA with this switch and see if the packet loss
situation improves? Simplest way would be:
ip link set eth0 down
echo edsa > /sys/class/net/eth0/dsa/tagging
ip link set lan1 up
If this helps, I would recommend reading
Documentation/devicetree/bindings/net/dsa/dsa-port.yaml to see how to
make this board use edsa persistently.
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: DSA Switch: query: Switch configuration, data plane doesn't work whereas control plane works
2024-12-24 16:00 ` Vladimir Oltean
@ 2024-12-25 8:53 ` sai kumar
0 siblings, 0 replies; 7+ messages in thread
From: sai kumar @ 2024-12-25 8:53 UTC (permalink / raw)
To: Vladimir Oltean; +Cc: netdev
Thanks Vladimir for your inputs.
While trying to follow your suggestion to update the device tree with
dsa-tag-protocol = "edsa";
Found there is a mismatch with respect to phymode; in cpu port port 0
phy-mode = "rgmii-id"; and fman enet phy-connection-type = "rgmii";
I tried changing the phy-mode of switch cpu port to match fman enet phy mode,
Now the switch works as expected and dhcp discover of client connected
to port 1 reaches external cpu enet port eth1 with even tag protocol
as dsa.
and errors vanished on eth1.
Somehow this missed the radar earlier since eth1 link got up quietly,
and didn't observe any error in dmesg with respect to phymode mismatch
between fman eth1 and switch cpu port 0.
Thanks for your help for immediate responses.
cat /sys/class/net/eth1/dsa/tagging
dsa
ethtool -S eth1
NIC statistics:
interrupts [CPU 0]: 33
interrupts [CPU 1]: 19
interrupts [CPU 2]: 15
interrupts [CPU 3]: 24
interrupts [TOTAL]: 91
rx packets [CPU 0]: 16
rx packets [CPU 1]: 11
rx packets [CPU 2]: 9
rx packets [CPU 3]: 18
rx packets [TOTAL]: 54
tx packets [CPU 0]: 1
tx packets [CPU 1]: 21
tx packets [CPU 2]: 10
tx packets [CPU 3]: 5
tx packets [TOTAL]: 37
tx recycled [CPU 0]: 0
tx recycled [CPU 1]: 0
tx recycled [CPU 2]: 0
tx recycled [CPU 3]: 0
tx recycled [TOTAL]: 0
tx confirm [CPU 0]: 17
tx confirm [CPU 1]: 8
tx confirm [CPU 2]: 6
tx confirm [CPU 3]: 6
tx confirm [TOTAL]: 37
tx S/G [CPU 0]: 0
tx S/G [CPU 1]: 0
tx S/G [CPU 2]: 0
tx S/G [CPU 3]: 0
tx S/G [TOTAL]: 0
rx S/G [CPU 0]: 0
rx S/G [CPU 1]: 0
rx S/G [CPU 2]: 0
rx S/G [CPU 3]: 0
rx S/G [TOTAL]: 0
tx error [CPU 0]: 0
tx error [CPU 1]: 0
tx error [CPU 2]: 0
tx error [CPU 3]: 0
tx error [TOTAL]: 0
rx error [CPU 0]: 0
rx error [CPU 1]: 0
rx error [CPU 2]: 0
rx error [CPU 3]: 0
rx error [TOTAL]: 0
bp count [CPU 0]: 112
bp count [CPU 1]: 117
bp count [CPU 2]: 119
bp count [CPU 3]: 110
bp count [TOTAL]: 458
rx dma error: 0
rx frame physical error: 0
rx frame size error: 0
rx header error: 0
rx csum error: 0
qman cg_tdrop: 0
qman wred: 0
qman error cond: 0
qman early window: 0
qman late window: 0
qman fq tdrop: 0
qman fq retired: 0
qman orp disabled: 0
congestion time (ms): 0
entered congestion: 0
congested (0/1): 0
p00_in_good_octets: 2404
p00_in_bad_octets: 0
p00_in_unicast: 0
p00_in_broadcasts: 0
p00_in_multicasts: 24
p00_in_pause: 0
p00_in_undersize: 0
p00_in_fragments: 0
p00_in_oversize: 0
p00_in_jabber: 0
p00_in_rx_error: 0
p00_in_fcs_error: 0
p00_out_octets: 14374
p00_out_unicast: 0
p00_out_broadcasts: 37
p00_out_multicasts: 14
p00_out_pause: 0
p00_excessive: 0
p00_collisions: 0
p00_deferred: 0
p00_single: 0
p00_multiple: 0
p00_out_fcs_error: 0
p00_late: 0
p00_hist_64bytes: 0
p00_hist_65_127bytes: 38
p00_hist_128_255bytes: 0
p00_hist_256_511bytes: 37
p00_hist_512_1023bytes: 0
p00_hist_1024_max_bytes: 0
p00_in_discards: 0
p00_in_filtered: 0
p00_in_accepted: 24
p00_in_bad_accepted: 0
p00_in_good_avb_class_a: 0
p00_in_good_avb_class_b: 0
p00_in_bad_avb_class_a: 0
p00_in_bad_avb_class_b: 0
p00_tcam_counter_0: 0
p00_tcam_counter_1: 0
p00_tcam_counter_2: 0
p00_tcam_counter_3: 0
p00_in_da_unknown: 24
p00_in_management: 15
p00_out_queue_0: 46
p00_out_queue_1: 0
p00_out_queue_2: 0
p00_out_queue_3: 5
p00_out_queue_4: 0
p00_out_queue_5: 0
p00_out_queue_6: 0
p00_out_queue_7: 0
p00_out_cut_through: 0
p00_out_octets_a: 0
p00_out_octets_b: 0
p00_out_management: 13
p00_atu_member_violation: 0
p00_atu_miss_violation: 0
p00_atu_full_violation: 0
p00_vtu_member_violation: 0
p00_vtu_miss_violation: 0
On Tue, Dec 24, 2024 at 9:30 PM Vladimir Oltean <olteanv@gmail.com> wrote:
>
> On Tue, Dec 24, 2024 at 06:20:38PM +0530, sai kumar wrote:
> > Thanks Vladimir for your inputs.
> >
> > I tried checking the statistics, the in_broadcasts count increases
> > with respect to client dhcp discover broadcasts.
> > But the same is not happening with external cpu port eth1, the eth1
> > in_broadcasts and in_accepted are 0 , Observing the rx frame errors on
> > eth1 but
> > this count doesn't match to the clients broadcast packets count.
> >
> > ethtool -S lan1
> > NIC statistics:
> > tx_packets: 7
> > tx_bytes: 626
> > rx_packets: 0
> > rx_bytes: 0
> > in_good_octets: 18112
> > in_bad_octets: 0
> > in_unicast: 0
> > in_broadcasts: 51
> > in_multicasts: 5
> > in_pause: 0
> > in_undersize: 0
> > in_fragments: 0
> > in_oversize: 0
> > in_jabber: 0
> > in_rx_error: 0
> > in_fcs_error: 0
> > out_octets: 7792
> > out_unicast: 0
> > out_broadcasts: 105
> > out_multicasts: 12
> > out_pause: 0
> > excessive: 0
> > collisions: 0
> > deferred: 0
> > single: 0
> > multiple: 0
> > out_fcs_error: 0
> > late: 0
> > hist_64bytes: 105
> > hist_65_127bytes: 17
> > hist_128_255bytes: 0
> > hist_256_511bytes: 51
> > hist_512_1023bytes: 0
> > hist_1024_max_bytes: 0
> > in_discards: 0
> > in_filtered: 0
> > in_accepted: 56
> > in_bad_accepted: 0
> > in_good_avb_class_a: 0
> > in_good_avb_class_b: 0
> > in_bad_avb_class_a: 0
> > in_bad_avb_class_b: 0
> > tcam_counter_0: 0
> > tcam_counter_1: 0
> > tcam_counter_2: 0
> > tcam_counter_3: 0
> > in_da_unknown: 5
> > in_management: 4
> > out_queue_0: 117
> > out_queue_1: 0
> > out_queue_2: 0
> > out_queue_3: 0
> > out_queue_4: 0
> > out_queue_5: 0
> > out_queue_6: 0
> > out_queue_7: 0
> > out_cut_through: 0
> > out_octets_a: 0
> > out_octets_b: 0
> > out_management: 0
> > atu_member_violation: 0
> > atu_miss_violation: 0
> > atu_full_violation: 0
> > vtu_member_violation: 0
> > vtu_miss_violation: 0
> >
> >
> > ethtool -S eth1
> > NIC statistics:
> > interrupts [CPU 0]: 12
> > interrupts [CPU 1]: 9
> > interrupts [CPU 2]: 5
> > interrupts [CPU 3]: 7
> > interrupts [TOTAL]: 33
> > rx packets [CPU 0]: 0
> > rx packets [CPU 1]: 0
> > rx packets [CPU 2]: 0
> > rx packets [CPU 3]: 0
> > rx packets [TOTAL]: 0
> > tx packets [CPU 0]: 2
> > tx packets [CPU 1]: 0
> > tx packets [CPU 2]: 12
> > tx packets [CPU 3]: 0
> > tx packets [TOTAL]: 14
> > tx recycled [CPU 0]: 0
> > tx recycled [CPU 1]: 0
> > tx recycled [CPU 2]: 0
> > tx recycled [CPU 3]: 0
> > tx recycled [TOTAL]: 0
> > tx confirm [CPU 0]: 6
> > tx confirm [CPU 1]: 3
> > tx confirm [CPU 2]: 2
> > tx confirm [CPU 3]: 3
> > tx confirm [TOTAL]: 14
> > tx S/G [CPU 0]: 0
> > tx S/G [CPU 1]: 0
> > tx S/G [CPU 2]: 0
> > tx S/G [CPU 3]: 0
> > tx S/G [TOTAL]: 0
> > rx S/G [CPU 0]: 0
> > rx S/G [CPU 1]: 0
> > rx S/G [CPU 2]: 0
> > rx S/G [CPU 3]: 0
> > rx S/G [TOTAL]: 0
> > tx error [CPU 0]: 0
> > tx error [CPU 1]: 0
> > tx error [CPU 2]: 0
> > tx error [CPU 3]: 0
> > tx error [TOTAL]: 0
> > rx error [CPU 0]: 6
> > rx error [CPU 1]: 6
> > rx error [CPU 2]: 3
> > rx error [CPU 3]: 4
> > rx error [TOTAL]: 19
> > bp count [CPU 0]: 128
> > bp count [CPU 1]: 128
> > bp count [CPU 2]: 128
> > bp count [CPU 3]: 128
> > bp count [TOTAL]: 512
> > rx dma error: 0
> > rx frame physical error: 2
> > rx frame size error: 17
> > rx header error: 0
> > rx csum error: 0
> > qman cg_tdrop: 0
> > qman wred: 0
> > qman error cond: 0
> > qman early window: 0
> > qman late window: 0
> > qman fq tdrop: 0
> > qman fq retired: 0
> > qman orp disabled: 0
> > congestion time (ms): 0
> > entered congestion: 0
> > congested (0/1): 0
> > p00_in_good_octets: 0
> > p00_in_bad_octets: 2
> > p00_in_unicast: 0
> > p00_in_broadcasts: 0
> > p00_in_multicasts: 0
> > p00_in_pause: 0
> > p00_in_undersize: 0
> > p00_in_fragments: 0
> > p00_in_oversize: 0
> > p00_in_jabber: 0
> > p00_in_rx_error: 1
> > p00_in_fcs_error: 0
> > p00_out_octets: 45440
> > p00_out_unicast: 0
> > p00_out_broadcasts: 312
> > p00_out_multicasts: 63
> > p00_out_pause: 0
> > p00_excessive: 0
> > p00_collisions: 0
> > p00_deferred: 0
> > p00_single: 0
> > p00_multiple: 0
> > p00_out_fcs_error: 0
> > p00_late: 0
> > p00_hist_64bytes: 0
> > p00_hist_65_127bytes: 306
> > p00_hist_128_255bytes: 8
> > p00_hist_256_511bytes: 61
> > p00_hist_512_1023bytes: 0
> > p00_hist_1024_max_bytes: 0
> > p00_in_discards: 0
> > p00_in_filtered: 0
> > p00_in_accepted: 0
> > p00_in_bad_accepted: 0
> > p00_in_good_avb_class_a: 0
> > p00_in_good_avb_class_b: 0
> > p00_in_bad_avb_class_a: 0
> > p00_in_bad_avb_class_b: 0
> > p00_tcam_counter_0: 0
> > p00_tcam_counter_1: 0
> > p00_tcam_counter_2: 0
> > p00_tcam_counter_3: 0
> > p00_in_da_unknown: 0
> > p00_in_management: 0
> > p00_out_queue_0: 373
> > p00_out_queue_1: 0
> > p00_out_queue_2: 0
> > p00_out_queue_3: 0
> > p00_out_queue_4: 0
> > p00_out_queue_5: 0
> > p00_out_queue_6: 2
> > p00_out_queue_7: 0
> > p00_out_cut_through: 0
> > p00_out_octets_a: 0
> > p00_out_octets_b: 0
> > p00_out_management: 11
> > p00_atu_member_violation: 0
> > p00_atu_miss_violation: 0
> > p00_atu_full_violation: 0
> > p00_vtu_member_violation: 0
> > p00_vtu_miss_violation: 0
>
> Hmmm....
>
> I recognize the ethtool stats as belonging to the DPAA1 Ethernet driver.
>
> And I see that the Marvell 6390 has undocumented EDSA tag support, thus
> using DSA (with no EtherType) by default. This reminds me of this
> discussion with Tobias Waldekranz. The FMan parser sees errors due to
> the somewhat controversial Marvell original DSA tag decisions:
> https://lore.kernel.org/netdev/20210323102326.3677940-1-tobias@waldekranz.com/
>
> Could you please force EDSA with this switch and see if the packet loss
> situation improves? Simplest way would be:
>
> ip link set eth0 down
> echo edsa > /sys/class/net/eth0/dsa/tagging
> ip link set lan1 up
>
> If this helps, I would recommend reading
> Documentation/devicetree/bindings/net/dsa/dsa-port.yaml to see how to
> make this board use edsa persistently.
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: DSA Switch: query: Switch configuration, data plane doesn't work whereas control plane works
2024-12-24 9:30 DSA Switch: query: Switch configuration, data plane doesn't work whereas control plane works sai kumar
2024-12-24 12:00 ` Vladimir Oltean
@ 2024-12-25 17:53 ` Andrew Lunn
2024-12-26 5:00 ` sai kumar
1 sibling, 1 reply; 7+ messages in thread
From: Andrew Lunn @ 2024-12-25 17:53 UTC (permalink / raw)
To: sai kumar; +Cc: netdev
On Tue, Dec 24, 2024 at 03:00:17PM +0530, sai kumar wrote:
> Hi Team,
>
> This could be basic question related to DSA, if possible please help
> to share your feedback,. Thanks.
>
>
> External CPU eth1 ---RGMII---- Switch Port 0 (cpu port)
How do you have your RGMII delays configured?
Andrew
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: DSA Switch: query: Switch configuration, data plane doesn't work whereas control plane works
2024-12-25 17:53 ` Andrew Lunn
@ 2024-12-26 5:00 ` sai kumar
0 siblings, 0 replies; 7+ messages in thread
From: sai kumar @ 2024-12-26 5:00 UTC (permalink / raw)
To: Andrew Lunn; +Cc: netdev
Hi Andrew,
Sorry my mail getting bounced back due to not being in plain text mode.
the issue got resolved, issue was mismatch in phymode between
eth1(rgmii) and switch port0(rgmii-id) in device tree.
The Port 0 RGMII currently set as default as per data sheet, didn't
modify its port registers. The issue was the configuration side on
device tree for port 0, cpu port.
While trying to follow Vladimir's suggestion to update the device tree with
dsa-tag-protocol = "edsa";
Found there is a mismatch with respect to phymode; in cpu port port 0
phy-mode = "rgmii-id"; and fman enet phy-connection-type = "rgmii";
I tried changing the phy-mode of switch cpu port to match fman enet phy mode,
Now the switch works as expected and dhcp discover of client connected
to port 1 reaches external cpu enet port eth1 with even tag protocol
as dsa.
and errors vanished on eth1.
Somehow this missed the radar earlier since eth1 link got up quietly,
and didn't observe any error in dmesg with respect to phymode mismatch
between fman eth1 and switch cpu port 0.
Thanks for your help for immediate responses
On Wed, Dec 25, 2024 at 11:23 PM Andrew Lunn <andrew@lunn.ch> wrote:
>
> On Tue, Dec 24, 2024 at 03:00:17PM +0530, sai kumar wrote:
> > Hi Team,
> >
> > This could be basic question related to DSA, if possible please help
> > to share your feedback,. Thanks.
> >
> >
> > External CPU eth1 ---RGMII---- Switch Port 0 (cpu port)
>
> How do you have your RGMII delays configured?
>
> Andrew
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2024-12-26 5:00 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-12-24 9:30 DSA Switch: query: Switch configuration, data plane doesn't work whereas control plane works sai kumar
2024-12-24 12:00 ` Vladimir Oltean
2024-12-24 12:50 ` sai kumar
2024-12-24 16:00 ` Vladimir Oltean
2024-12-25 8:53 ` sai kumar
2024-12-25 17:53 ` Andrew Lunn
2024-12-26 5:00 ` sai kumar
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox