[PATCH 0/8] mfd: Fix wakeup source leaks on device unbind
From: Krzysztof Kozlowski
Date: Sun Apr 06 2025 - 15:50:33 EST
Device can be unbound, so driver must also release memory for the wakeup
source. Use devm for driver already having devm interface and manually
disable wakeup for drivers still having remove() callback to keep
consistent ordering of cleanups.
I did not update the drivers with suppress_bind_attrs and no error paths
after device_init_wakeup() because it would not bring any benefits.
Best regards,
Krzysztof
---
Krzysztof Kozlowski (8):
mfd: 88pm886: Fix wakeup source leaks on device unbind
mfd: as3722: Fix wakeup source leaks on device unbind
mfd: max14577: Fix wakeup source leaks on device unbind
mfd: max77541: Fix wakeup source leaks on device unbind
mfd: max77705: Fix wakeup source leaks on device unbind
mfd: max8925: Fix wakeup source leaks on device unbind
mfd: rt5033: Fix wakeup source leaks on device unbind
mfd: sprd-sc27xx: Fix wakeup source leaks on device unbind
drivers/mfd/88pm886.c | 6 +++++-
drivers/mfd/as3722.c | 4 +++-
drivers/mfd/max14577.c | 1 +
drivers/mfd/max77541.c | 2 +-
drivers/mfd/max77705.c | 4 +++-
drivers/mfd/max8925-i2c.c | 1 +
drivers/mfd/rt5033.c | 6 +++++-
drivers/mfd/sprd-sc27xx-spi.c | 5 ++++-
8 files changed, 23 insertions(+), 6 deletions(-)
---
base-commit: a4cda136f021ad44b8b52286aafd613030a6db5f
change-id: 20250406-mfd-device-wakekup-leak-a98a99acb1fa
Best regards,
--
Krzysztof Kozlowski <krzysztof.kozlowski@xxxxxxxxxx>