leds: lp5860: Fix LED teardown ordering using devm_add_action_or_reset()
PATCH v3 1/1 leds: lp5860: Fix LED teardown ordering using devm_add_action_or_reset()
From: Surendra Singh Chouhan <[email protected]>
The driver previously disabled the chip in its remove callback before devres unregistered the LEDs. LED unregistration turns the LEDs off through the driver brightness callback, which accessed disabled hardware.
Fix this by registering a devm action via devm_add_action_or_reset() immediately after enabling the chip in lp5860_device_init(). Due to devm LIFO (Last-In, First-Out) teardown ordering, devm will automatically unregister all multicolor LEDs before the devm action disables the chip.
In addition, use scoped_guard(mutex, &lp->lock) to restrict the initial mode setting lock scope, avoiding holding the mutex across lp5860_init_dt(), which would cause a self-deadlock when registering subleds.
Finally, convert mutex_init() to devm_mutex_init() and declare the local variable ret in lp5860_probe(), allowing lp5860_device_remove() and lp5860_remove() to be removed completely.
---
v3:
- Use scoped_guard(mutex, &lp->lock) in lp5860_device_init() so the lock is released before calling lp5860_init_dt(), preventing a self-deadlock during subled registration.
- Declare missing local variable 'ret' in lp5860_probe().
- Capitalize patch title per LED subsystem guidelines.
v2:
- Use full name "Surendra Singh Chouhan" in From header and Signed-off-by.
- Convert chip disable sequence to devm_add_action_or_reset() as suggested by Lee Jones.
- Use devm_mutex_init() for lock initialization.
drivers/leds/rgb/leds-lp5860-core.c | 42 +++++++++++++---------------- drivers/leds/rgb/leds-lp5860-spi.c | 15 +++-------- drivers/leds/rgb/leds-lp5860.h | 1 - 3 files changed, 22 insertions(+), 36 deletions(-)
drivers/leds/rgb/leds-lp5860-core.c +18 -24
@@ -188,6 +188,13 @@ static int lp5860_init_dt(struct lp5860 *lp)return 0 ; } +static void lp5860_disable_action (void *data) +{ +struct lp5860 *lp = data; + +lp5860_chip_enable (lp,LP5860_CHIP_DISABLE ); +} +int lp5860_device_init (struct device *dev) {struct lp5860 *lp =dev_get_drvdata (dev);
@@ -197,38 +204,25 @@ int lp5860_device_init(struct device *dev)if (ret)return ret; + ret =devm_add_action_or_reset (dev, lp5860_disable_action, lp); +if (ret) +return ret; +/* * Set to 8-bit PWM data without VSYNC. * Data is sent out for display instantly after received. */ -mutex_lock (&lp->lock); - ret =regmap_update_bits (lp->regmap,LP5860_REG_DEV_INITIAL ,LP5860_MODE_MASK , -LP5860_MODE_1 <<LP5860_MODE_SHIFT ); -if (ret) - goto err_disable; -mutex_unlock (&lp->lock); - - ret =lp5860_init_dt (lp); -if (ret) - goto err_disable; - -return 0 ; + scoped_guard(mutex, &lp->lock) { + ret =regmap_update_bits (lp->regmap,LP5860_REG_DEV_INITIAL ,LP5860_MODE_MASK , +LP5860_MODE_1 <<LP5860_MODE_SHIFT ); +if (ret) +return ret; + } -err_disable: -mutex_unlock (&lp->lock); -lp5860_chip_enable (lp,LP5860_CHIP_DISABLE ); -return ret; +return lp5860_init_dt (lp); }EXPORT_SYMBOL_GPL (lp5860_device_init); -void lp5860_device_remove (struct device *dev) -{ -struct lp5860 *lp =dev_get_drvdata (dev); - -lp5860_chip_enable (lp,LP5860_CHIP_DISABLE ); -} -EXPORT_SYMBOL_GPL (lp5860_device_remove); -MODULE_AUTHOR ("Steffen Trumtrar <[email protected]>" );MODULE_DESCRIPTION ("TI LP5860 RGB LED core driver" );MODULE_LICENSE ("GPL" );
drivers/leds/rgb/leds-lp5860-spi.c +4 -11
@@ -38,6 +38,7 @@ static int lp5860_probe(struct spi_device *spi)struct device *dev = &spi->dev;struct lp5860 *lp5860;unsigned int multi_leds; +int ret; multi_leds =device_get_child_node_count (dev);if (!multi_leds) {
@@ -61,22 +62,15 @@ static int lp5860_probe(struct spi_device *spi) "Failed to initialise Regmap.\n"); lp5860->dev = dev; -mutex_init (&lp5860->lock); + ret =devm_mutex_init (dev, &lp5860->lock); +if (ret) +return ret;spi_set_drvdata (spi, lp5860);return lp5860_device_init (dev); } -static void lp5860_remove (struct spi_device *spi) -{ -struct lp5860 *lp5860 =spi_get_drvdata (spi); - -mutex_destroy (&lp5860->lock); - -lp5860_device_remove (&spi->dev); -} -static const struct of_device_id lp5860_of_match[] = { { .compatible ="ti,lp5860" }, {}
@@ -89,7 +83,6 @@ static struct spi_driver lp5860_driver = { .of_match_table = lp5860_of_match, }, .probe = lp5860_probe, - .remove = lp5860_remove, };module_spi_driver (lp5860_driver);
drivers/leds/rgb/leds-lp5860.h +0 -1
@@ -263,6 +263,5 @@ struct lp5860 { };int lp5860_device_init (struct device *dev); -void lp5860_device_remove (struct device *dev);#endif /* _DRIVERS_LEDS_RGB_LP5860_H */
Signature · 1 line
2.55.0
[email protected]
AI reviewSashiko has reviewed this patch and found no issues. It looks great!
Quoted 16 lines
From: Surendra Singh Chouhan <[email protected]>
The driver previously disabled the chip in its remove callback before devres unregistered the LEDs. LED unregistration turns the LEDs off through the driver brightness callback, which accessed disabled hardware.
Fix this by registering a devm action via
devm_add_action_or_reset()immediately after enabling the chip inlp5860_device_init(). Due to devm LIFO (Last-In, First-Out) teardown ordering, devm will automatically unregister all multicolor LEDs before the devm action disables the chip.In addition, use
scoped_guard(mutex, &lp->lock)to restrict the initial mode setting lock scope, avoiding holding the mutex acrosslp5860_init_dt(), which would cause a self-deadlock when registering subleds.
Quoted 6 lines
Finally, convert
mutex_init()todevm_mutex_init()and declare the local variable ret inlp5860_probe(), allowinglp5860_device_remove()andlp5860_remove()to be removed completely.Fixes f0a66563aa2d ("leds: Add support for TI LP5860 LED driver chip")Signed-off-by Surendra Singh Chouhan <[email protected]>
Sashiko has reviewed this patch and found no issues. It looks great!
Signature · 1 line
Sashiko AI review · https://sashiko.dev/#/patchset/[email protected]?part=1
Quoted 33 lines · On Wed, 12 Aug 2026, [email protected] wrote:
From: Surendra Singh Chouhan <[email protected]>
The driver previously disabled the chip in its remove callback before devres unregistered the LEDs. LED unregistration turns the LEDs off through the driver brightness callback, which accessed disabled hardware.
Fix this by registering a devm action via
devm_add_action_or_reset()immediately after enabling the chip inlp5860_device_init(). Due to devm LIFO (Last-In, First-Out) teardown ordering, devm will automatically unregister all multicolor LEDs before the devm action disables the chip.In addition, use
scoped_guard(mutex, &lp->lock)to restrict the initial mode setting lock scope, avoiding holding the mutex acrosslp5860_init_dt(), which would cause a self-deadlock when registering subleds.Finally, convert
mutex_init()todevm_mutex_init()and declare the local variable ret inlp5860_probe(), allowinglp5860_device_remove()andlp5860_remove()to be removed completely.Fixes f0a66563aa2d ("leds: Add support for TI LP5860 LED driver chip")Signed-off-by Surendra Singh Chouhan <[email protected]>---
v3:
- Usescoped_guard(mutex, &lp->lock)inlp5860_device_init()so the lock is released before callinglp5860_init_dt(), preventing a self-deadlock during subled registration.
- Declare missing local variable 'ret' inlp5860_probe().
- Capitalize patch title per LED subsystem guidelines.v2:
- Use full name "Surendra Singh Chouhan" in From header and Signed-off-by.
- Convert chip disable sequence todevm_add_action_or_reset()as suggested by Lee Jones.
- Usedevm_mutex_init()for lock initialization.
Quoted 4 lines
drivers/leds/rgb/leds-lp5860-core.c | 42 +++++++++++++---------------- drivers/leds/rgb/leds-lp5860-spi.c | 15 +++-------- drivers/leds/rgb/leds-lp5860.h | 1 - 3 files changed, 22 insertions(+), 36 deletions(-)
This no longer applies.
Please rebase onto -next or my LEDs tree and resubmit with my:
Signature · 1 line
Lee Jones