From: Jonathan Cameron <jic23@kernel.org>
To: Sean Anderson <sean.anderson@linux.dev>
Cc: "Jean Delvare" <jdelvare@suse.com>,
"Guenter Roeck" <linux@roeck-us.net>,
linux-iio@vger.kernel.org, linux-hwmon@vger.kernel.org,
"Andy Shevchenko" <andy@kernel.org>,
"Nuno Sá" <nuno.sa@analog.com>,
linux-kernel@vger.kernel.org,
"David Lechner" <dlechner@baylibre.com>
Subject: Re: [PATCH 7/7] hwmon: iio: Add alarm support
Date: Sun, 27 Jul 2025 17:50:54 +0100 [thread overview]
Message-ID: <20250727175054.54fe5629@jic23-huawei> (raw)
In-Reply-To: <20250715012023.2050178-8-sean.anderson@linux.dev>
On Mon, 14 Jul 2025 21:20:23 -0400
Sean Anderson <sean.anderson@linux.dev> wrote:
> Add alarm support based on IIO threshold events. The alarm is cleared on
> read, but will be set again if the condition is still present. This is
> detected by disabling and re-enabling the event. The same trick is done
> when creating the attribute to detect already-triggered events.
>
> The alarms are updated by an event listener. To keep the notifier call
> chain short, we create one listener per iio device, shared across all
> hwmon devices.
>
> To avoid dynamic creation of alarms, alarms for all possible events are
> allocated at creation. Lookup is done by a linear scan, as I expect
> events to occur rarely. If performance becomes an issue, a binary search
> could be done instead (or some kind of hash lookup).
>
> Signed-off-by: Sean Anderson <sean.anderson@linux.dev>
A few minor comments inline.
Thanks,
Jonathan
> + * iio_hwmon_listener_get() - Get a listener for an IIO device
> + * @indio_dev: IIO device to listen to
> + *
> + * Look up or create a new listener for @indio_dev. The returned listener is
> + * registered with @indio_dev, but events still need to be manually enabled.
> + * You must call iio_hwmon_listener_put() when you are done.
> + *
> + * Return: Listener for @indio_dev, or an error pointer
> + */
> +static struct iio_hwmon_listener *iio_hwmon_listener_get(struct iio_dev *indio_dev)
> +{
> + struct iio_hwmon_listener *listener;
> + int err = -ENOMEM;
> + size_t i, j;
> +
> + guard(mutex)(&iio_hwmon_listener_lock);
Guard + unlock. However, in general combining cleanup.h stuff and
gotos is a bad idea. You might better off wrapping a function
with the lock in the outer function
Alternative, use local variables for ids and alarms. Use __free()
on those + return_ptr(listener) and no_free_ptr() as you assign
the elements of listener after there is no possibility of error.
> + list_for_each_entry(listener, &iio_hwmon_listeners, list) {
> + if (listener->indio_dev == indio_dev) {
Deep nest. I'd do
if (listener->indio_dev != indio-dev)
continue;
if (likely(listener->refcnt != UINT_MAX)
//Needs a comment on why this make sense as opposed to returning an error.
listener->refcnt++;
return listener;
> + if (likely(listener->refcnt != UINT_MAX))
> + listener->refcnt++;
> + return listener;
> + }
> + }
> +
> + listener = kzalloc(sizeof(*listener), GFP_KERNEL);
> + if (!listener)
> + goto err_unlock;
> +
> + listener->refcnt = 1;
> + listener->indio_dev = indio_dev;
> + listener->block.notifier_call = iio_hwmon_listener_callback;
> + for (i = 0; i < indio_dev->num_channels; i++)
> + listener->num_alarms += indio_dev->channels[i].num_event_specs;
> +
> + listener->ids = kcalloc(listener->num_alarms, sizeof(*listener->ids),
> + GFP_KERNEL);
> + listener->alarms = bitmap_zalloc(listener->num_alarms, GFP_KERNEL);
> + if (!listener->ids || !listener->alarms)
> + goto err_listener;
I'd prefer this split into a pair of checks and separate labels.
> +
> + i = 0;
> + for (j = 0; j < indio_dev->num_channels; j++) {
> + struct iio_chan_spec const *chan = &indio_dev->channels[j];
> + size_t k;
> +
> + for (k = 0; k < chan->num_event_specs; k++)
> + listener->ids[i++] =
> + iio_event_id(chan, chan->event_spec[k].type,
> + chan->event_spec[k].dir);
> + }
> +
> + err = iio_event_register(indio_dev, &listener->block);
> + if (err)
> + goto err_alarms;
> +
> + list_add(&listener->list, &iio_hwmon_listeners);
> + mutex_unlock(&iio_hwmon_listener_lock);
> + return listener;
> +
> +err_alarms:
> + kfree(listener->alarms);
> + kfree(listener->ids);
> +err_listener:
> + kfree(listener);
> +err_unlock:
> + mutex_unlock(&iio_hwmon_listener_lock);
> + return ERR_PTR(err);
> +}
> +
> +/**
> + * iio_hwmon_listener_put() - Release a listener
Maybe use a kref and kref_put() with a suitable release to
do the cleanup.
> + * @data: &struct iio_hwmon_listener to release
> + *
> + * For convenience, @data is void.
> + */
> +static void iio_hwmon_listener_put(void *data)
> +{
> + struct iio_hwmon_listener *listener = data;
> +
> + scoped_guard(mutex, &iio_hwmon_listener_lock) {
> + if (unlikely(listener->refcnt == UINT_MAX))
> + return;
> +
> + if (--listener->refcnt)
> + return;
> +
> + list_del(&listener->list);
> + iio_event_unregister(listener->indio_dev, &listener->block);
> + }
> +
> + kfree(listener->alarms);
> + kfree(listener->ids);
> + kfree(listener);
> +}
>
prev parent reply other threads:[~2025-07-27 16:51 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-15 1:20 [PATCH 0/7] hwmon: iio: Add alarm support Sean Anderson
2025-07-15 1:20 ` [PATCH 1/7] math64: Add div64_s64_rem Sean Anderson
2025-07-15 8:03 ` Andy Shevchenko
2025-07-15 17:36 ` Sean Anderson
2025-07-16 10:15 ` Andy Shevchenko
2025-07-15 1:20 ` [PATCH 2/7] iio: inkern: Add API for reading/writing events Sean Anderson
2025-07-15 8:18 ` Andy Shevchenko
2025-07-15 15:42 ` Sean Anderson
2025-07-16 9:28 ` Andy Shevchenko
2025-07-17 16:42 ` Sean Anderson
2025-07-27 15:55 ` Jonathan Cameron
2025-07-15 10:35 ` Nuno Sá
2025-07-15 15:43 ` Sean Anderson
2025-07-16 6:23 ` Nuno Sá
2025-07-27 16:13 ` Jonathan Cameron
2025-07-15 1:20 ` [PATCH 3/7] iio: Add in-kernel API for events Sean Anderson
2025-07-15 8:20 ` Andy Shevchenko
2025-07-15 15:47 ` Sean Anderson
2025-07-16 9:47 ` Andy Shevchenko
2025-07-15 11:09 ` Nuno Sá
2025-07-15 16:52 ` Sean Anderson
2025-07-27 16:21 ` Jonathan Cameron
2025-07-28 22:44 ` Sean Anderson
2025-07-29 18:33 ` Jonathan Cameron
2025-07-29 20:09 ` Sean Anderson
2025-07-31 12:59 ` Jonathan Cameron
2025-07-27 16:24 ` Jonathan Cameron
2025-07-15 1:20 ` [PATCH 4/7] hwmon: iio: Refactor scale calculation into helper Sean Anderson
2025-07-15 8:35 ` Andy Shevchenko
2025-07-15 1:20 ` [PATCH 5/7] hwmon: iio: Add helper function for creating attributes Sean Anderson
2025-07-15 8:38 ` Andy Shevchenko
2025-07-15 15:55 ` Sean Anderson
2025-07-16 10:00 ` Andy Shevchenko
2025-07-27 16:31 ` Jonathan Cameron
2025-07-15 1:20 ` [PATCH 6/7] hwmon: iio: Add min/max support Sean Anderson
2025-07-15 8:41 ` Andy Shevchenko
2025-07-15 16:05 ` Sean Anderson
2025-07-16 10:01 ` Andy Shevchenko
2025-07-17 16:11 ` Sean Anderson
2025-07-27 16:35 ` Jonathan Cameron
2025-07-28 22:32 ` Sean Anderson
2025-07-29 18:37 ` Jonathan Cameron
2025-07-15 1:20 ` [PATCH 7/7] hwmon: iio: Add alarm support Sean Anderson
2025-07-15 8:50 ` Andy Shevchenko
2025-07-15 16:20 ` Sean Anderson
2025-07-16 10:08 ` Andy Shevchenko
2025-07-17 16:23 ` Sean Anderson
2025-07-21 7:42 ` Andy Shevchenko
2025-07-21 14:24 ` Sean Anderson
2025-07-15 11:28 ` Nuno Sá
2025-07-15 17:02 ` Sean Anderson
2025-07-15 19:26 ` Guenter Roeck
2025-07-15 19:40 ` Sean Anderson
2025-07-16 6:37 ` Nuno Sá
2025-07-17 16:00 ` Sean Anderson
2025-07-31 10:52 ` Nuno Sá
2025-08-02 10:53 ` Jonathan Cameron
2025-07-15 16:13 ` kernel test robot
2025-07-15 19:34 ` Guenter Roeck
2025-07-15 20:08 ` Sean Anderson
2025-07-16 7:44 ` kernel test robot
2025-07-27 16:50 ` Jonathan Cameron [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250727175054.54fe5629@jic23-huawei \
--to=jic23@kernel.org \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=nuno.sa@analog.com \
--cc=sean.anderson@linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox