summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/git@git.tavy.me:linux.git
diff options
context:
space:
mode:
authorJakub Kicinski <kuba@kernel.org>2025-11-10 17:11:09 -0800
committerJakub Kicinski <kuba@kernel.org>2025-11-10 17:11:10 -0800
commitf5d8ec838b08e601e4652a81c9c444aed4f26829 (patch)
tree3b81acc49799cfcf60cd7251ec05bae12551acce /tools/perf/scripts/python/git@git.tavy.me:linux.git
parent7fc2bf8d30beebceac5841ad2227e0bd41abdf27 (diff)
parent2b3013ac03028a2364d8779719bb6bfbc0212435 (diff)
Merge branch 'net-dsa-b53-add-support-for-bcm5389-97-98-and-bcm63xx-arl-formats'
Jonas Gorski says: ==================== net: dsa: b53: add support for BCM5389/97/98 and BCM63XX ARL formats Currently b53 assumes that all switches apart from BCM5325/5365 use the same ARL formats, but there are actually multiple formats in use. Older switches use a format apparently introduced with BCM5387/BCM5389, while newer chips use a format apparently introduced with BCM5395. Note that these numbers are not linear, BCM5397/BCM5398 use the older format. In addition to that the switches integrated into BCM63XX SoCs use their own format. While accessing these normal read/write ARL entries are the same format as BCM5389 one, the search format is different. So in order to support all these different format, split all code accessing these entries into chip-family specific functions, and collect them in appropriate arl ops structs to keep the code cleaner. Sent as net-next since the ARL accesses have never worked before, and the extensive refactoring might be too much to warrant a fix. ==================== Link: https://patch.msgid.link/20251107080749.26936-1-jonas.gorski@gmail.com Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/git@git.tavy.me:linux.git')
0 files changed, 0 insertions, 0 deletions