diff options
| author | Luiz Angelo Daros de Luca <luizluca@gmail.com> | 2024-04-27 02:11:29 -0300 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2024-04-29 13:35:40 +0100 |
| commit | 4f580e9aced1816398c1c64f178302a22b8ea6e2 (patch) | |
| tree | 3b24b9f3b73056468912e316ba120b02fb346037 /tools/testing/selftests/drivers/net/lib/py/env.py | |
| parent | 5edc6585aafefa3d44fb8a84adf241d90227f7a3 (diff) | |
net: dsa: realtek: do not assert reset on remove
The necessity of asserting the reset on removal was previously
questioned, as DSA's own cleanup methods should suffice to prevent
traffic leakage[1].
When a driver has subdrivers controlled by devres, they will be
unregistered after the main driver's .remove is executed. If it asserts
a reset, the subdrivers will be unable to communicate with the hardware
during their cleanup. For LEDs, this means that they will fail to turn
off, resulting in a timeout error.
[1] https://lore.kernel.org/r/20240123215606.26716-9-luizluca@gmail.com/
Signed-off-by: Luiz Angelo Daros de Luca <luizluca@gmail.com>
Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'tools/testing/selftests/drivers/net/lib/py/env.py')
0 files changed, 0 insertions, 0 deletions