summaryrefslogtreecommitdiffstats
path: root/drivers/net/dsa/b53/Kconfig
diff options
context:
space:
mode:
authorVladimir Oltean <vladimir.oltean@nxp.com>2022-11-21 14:55:40 +0100
committerJakub Kicinski <kuba@kernel.org>2022-11-23 05:41:45 +0100
commitd2be320495b93ffb469e53100ba1668d0cd7eedc (patch)
tree62c51ef61027523c39c0baf65dc60e103eefc850 /drivers/net/dsa/b53/Kconfig
parentnet: dsa: unexport dsa_dev_to_net_device() (diff)
downloadlinux-d2be320495b93ffb469e53100ba1668d0cd7eedc.tar.xz
linux-d2be320495b93ffb469e53100ba1668d0cd7eedc.zip
net: dsa: modularize DSA_TAG_PROTO_NONE
There is no reason that I can see why the no-op tagging protocol should be registered manually, so make it a module and make all drivers which have any sort of reference to DSA_TAG_PROTO_NONE select it. Note that I don't know if ksz_get_tag_protocol() really needs this, or if it's just the logic which is poorly written. All switches seem to have their own tagging protocol, and DSA_TAG_PROTO_NONE is just a fallback that never gets used. Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com> Reviewed-by: Florian Fainelli <f.fainelli@gmail.com> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'drivers/net/dsa/b53/Kconfig')
-rw-r--r--drivers/net/dsa/b53/Kconfig1
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/net/dsa/b53/Kconfig b/drivers/net/dsa/b53/Kconfig
index 90b525160b71..ebaa4a80d544 100644
--- a/drivers/net/dsa/b53/Kconfig
+++ b/drivers/net/dsa/b53/Kconfig
@@ -2,6 +2,7 @@
menuconfig B53
tristate "Broadcom BCM53xx managed switch support"
depends on NET_DSA
+ select NET_DSA_TAG_NONE
select NET_DSA_TAG_BRCM
select NET_DSA_TAG_BRCM_LEGACY
select NET_DSA_TAG_BRCM_PREPEND