summaryrefslogtreecommitdiff
path: root/include/linux/debugobjects.h
diff options
context:
space:
mode:
authorVladimir Oltean <vladimir.oltean@nxp.com>2026-05-21 09:12:36 +0300
committerJakub Kicinski <kuba@kernel.org>2026-05-23 04:40:48 +0300
commit5fe0b938bde709795422c24e27ed493c7c5fa4a3 (patch)
treef28160e242eef4211ef8d6377fb13292647a33d1 /include/linux/debugobjects.h
parentfd1cdeddd7bc37419415a5a596d18f27f61c0225 (diff)
downloadlinux-5fe0b938bde709795422c24e27ed493c7c5fa4a3.tar.xz
net: dsa: microchip: don't reset on shutdown or driver removal
The ksz_switch driver is one of the few which reset the switch when unbinding the driver or shutting down - in the same category with ar9331_sw_remove(), bcm_sf2_sw_remove(), and ks8995_remove(), vsc73xx_remove() and lan9303_remove(). I don't think there exists any requirement to do this, and in fact it does create complications for WoL, as the code already shows. My issue with this logic is that it is the only thing keeping dev_ops->reset() necessary, which I would like to remove after individual KSZ switch families get their own setup() and teardown() methods that don't go through dev_ops. Don't reset the switch when unbinding the driver or shutting down. Remove the exit callbacks from the ksz_dev_ops. Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com> Signed-off-by: Bastien Curutchet (Schneider Electric) <bastien.curutchet@bootlin.com> Link: https://patch.msgid.link/20260521-clean-ksz-2nd-series-v3-1-75c38971c19a@bootlin.com Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'include/linux/debugobjects.h')
0 files changed, 0 insertions, 0 deletions