aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/drivers/iio/industrialio-trigger.c
diff options
context:
space:
mode:
authorDmitry Rokosov <DDRokosov@sberdevices.ru>2022-06-07 18:39:18 +0000
committerJonathan Cameron <Jonathan.Cameron@huawei.com>2022-06-18 14:26:17 +0100
commit4a08069461ac9822855116d24fbf11d5fb223cd1 (patch)
tree94ebd37612bc3f5f4f828bdad2215e0b3b2ff2ff /drivers/iio/industrialio-trigger.c
parentMerge branch 'immutable-qcom-spmi-rradc' into togreg (diff)
downloadwireguard-linux-4a08069461ac9822855116d24fbf11d5fb223cd1.tar.xz
wireguard-linux-4a08069461ac9822855116d24fbf11d5fb223cd1.zip
iio: trigger: warn about non-registered iio trigger getting attempt
As a part of patch series about wrong trigger register() and get() calls order in the some IIO drivers trigger initialization path: https://lore.kernel.org/all/20220524181150.9240-1-ddrokosov@sberdevices.ru/ runtime WARN_ONCE() is added to alarm IIO driver authors who make such a mistake. When an IIO driver allocates a new IIO trigger, it should register it before calling the get() operation. In other words, each IIO driver must abide by IIO trigger alloc()/register()/get() calls order. Signed-off-by: Dmitry Rokosov <ddrokosov@sberdevices.ru> Link: https://lore.kernel.org/r/20220607183907.20017-1-ddrokosov@sberdevices.ru Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Diffstat (limited to 'drivers/iio/industrialio-trigger.c')
-rw-r--r--drivers/iio/industrialio-trigger.c2
1 files changed, 2 insertions, 0 deletions
diff --git a/drivers/iio/industrialio-trigger.c b/drivers/iio/industrialio-trigger.c
index d89bf90650d5..26d610d4cbb8 100644
--- a/drivers/iio/industrialio-trigger.c
+++ b/drivers/iio/industrialio-trigger.c
@@ -576,6 +576,8 @@ struct iio_trigger *viio_trigger_alloc(struct device *parent,
if (trig->name == NULL)
goto free_descs;
+ INIT_LIST_HEAD(&trig->list);
+
trig->subirq_chip.name = trig->name;
trig->subirq_chip.irq_mask = &iio_trig_subirqmask;
trig->subirq_chip.irq_unmask = &iio_trig_subirqunmask;