* [PATCH] iio: gyro: mpu3050: use devm_iio_trigger_register()
@ 2026-05-20 11:04 Stepan Ionichev
2026-05-20 11:31 ` Stepan Ionichev
0 siblings, 1 reply; 2+ messages in thread
From: Stepan Ionichev @ 2026-05-20 11:04 UTC (permalink / raw)
To: jic23
Cc: linus.walleij, dlechner, nuno.sa, andy, hcazarim, linux-iio,
linux-kernel, sozdayvek
mpu3050_trigger_probe() allocates the DRDY trigger with
devm_iio_trigger_alloc() but registers it with plain
iio_trigger_register(). mpu3050_common_remove() never calls
iio_trigger_unregister(), so on module unload the trigger stays
in the global trigger list while its memory is later released by
devm, leaving a dangling entry.
Switch to devm_iio_trigger_register() so the registration is
undone in the same devm scope as the allocation.
Signed-off-by: Stepan Ionichev <sozdayvek@gmail.com>
---
drivers/iio/gyro/mpu3050-core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/iio/gyro/mpu3050-core.c b/drivers/iio/gyro/mpu3050-core.c
index d84e04e4b..596919318 100644
--- a/drivers/iio/gyro/mpu3050-core.c
+++ b/drivers/iio/gyro/mpu3050-core.c
@@ -1127,7 +1127,7 @@ static int mpu3050_trigger_probe(struct iio_dev *indio_dev, int irq)
mpu3050->trig->ops = &mpu3050_trigger_ops;
iio_trigger_set_drvdata(mpu3050->trig, indio_dev);
- ret = iio_trigger_register(mpu3050->trig);
+ ret = devm_iio_trigger_register(&indio_dev->dev, mpu3050->trig);
if (ret)
goto err_iio_trigger;
--
2.43.0
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2026-05-20 11:31 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2026-05-20 11:04 [PATCH] iio: gyro: mpu3050: use devm_iio_trigger_register() Stepan Ionichev
2026-05-20 11:31 ` Stepan Ionichev
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®