summaryrefslogtreecommitdiff
path: root/drivers/ata/pata_rb532_cf.c
diff options
context:
space:
mode:
authorVladimir Oltean <vladimir.oltean@nxp.com>2022-05-11 12:50:13 +0300
committerJakub Kicinski <kuba@kernel.org>2022-05-12 16:38:38 -0700
commite9b3ba439dcb975474accbae1a37b99f9df59bed (patch)
treec448f07ed73ce0e2a0a6d05a3f2e1b4c30dd08c3 /drivers/ata/pata_rb532_cf.c
parentf0a65f815f640499990d446d4f5d9090634fdf27 (diff)
net: dsa: felix: program host FDB entries towards PGID_CPU for tag_8021q too
I remembered why we had the host FDB migration procedure in place. It is true that host FDB entry migration can be done by changing the value of PGID_CPU, but the problem is that only host FDB entries learned while operating in NPI mode go to PGID_CPU. When the CPU port operates in tag_8021q mode, the FDB entries are learned towards the unicast PGID equal to the physical port number of this CPU port, bypassing the PGID_CPU indirection. So host FDB entries learned in tag_8021q mode are not migrated any longer towards the NPI port. Fix this by extracting the NPI port -> PGID_CPU redirection from the ocelot switch lib, moving it to the Felix DSA driver, and applying it for any CPU port regardless of its kind (NPI or tag_8021q). Fixes: a51c1c3f3218 ("net: dsa: felix: stop migrating FDBs back and forth on tag proto change") Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'drivers/ata/pata_rb532_cf.c')
0 files changed, 0 insertions, 0 deletions