From: Jonathan Cameron <jic23@kernel.org>
To: David Lechner <dlechner@baylibre.com>
Cc: linux-iio@vger.kernel.org, linux-staging@lists.linux.dev,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Axel Haslam" <ahaslam@baylibre.com>,
"Philip Molloy" <pmolloy@baylibre.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 12/17] iio: event: add optional event label support
Date: Tue, 10 Oct 2023 16:59:17 +0100 [thread overview]
Message-ID: <20231010165917.4c1cb0a9@jic23-huawei> (raw)
In-Reply-To: <20231005-ad2s1210-mainline-v4-12-ec00746840fc@baylibre.com>
On Thu, 5 Oct 2023 19:50:29 -0500
David Lechner <dlechner@baylibre.com> wrote:
> This adds a new optional field to struct iio_info to allow drivers to
> specify a label for the event. This is useful for cases where there are
> many events or the event attribute name is not descriptive enough or
> where an event doesn't have any other attributes.
>
> The implementation is based on the existing label support for channels.
> So either all events of a device have a label attribute or none do.
>
> Signed-off-by: David Lechner <dlechner@baylibre.com>
Was going to moan about lack of docs, but I see they are in later patches.
Ok. General feature is fine. Applied.
Jonathan
> ---
>
> v4 changes: New patch in v4.
>
> drivers/iio/industrialio-event.c | 55 ++++++++++++++++++++++++++++++++++++++++
> include/linux/iio/iio.h | 8 ++++++
> 2 files changed, 63 insertions(+)
>
> diff --git a/drivers/iio/industrialio-event.c b/drivers/iio/industrialio-event.c
> index 19f7a91157ee..910c1f14abd5 100644
> --- a/drivers/iio/industrialio-event.c
> +++ b/drivers/iio/industrialio-event.c
> @@ -355,6 +355,21 @@ static ssize_t iio_ev_value_store(struct device *dev,
> return len;
> }
>
> +static ssize_t iio_ev_label_show(struct device *dev,
> + struct device_attribute *attr,
> + char *buf)
> +{
> + struct iio_dev *indio_dev = dev_to_iio_dev(dev);
> + struct iio_dev_attr *this_attr = to_iio_dev_attr(attr);
> +
> + if (indio_dev->info->read_event_label)
> + return indio_dev->info->read_event_label(indio_dev,
> + this_attr->c, iio_ev_attr_type(this_attr),
> + iio_ev_attr_dir(this_attr), buf);
> +
> + return -EINVAL;
> +}
> +
> static int iio_device_add_event(struct iio_dev *indio_dev,
> const struct iio_chan_spec *chan, unsigned int spec_index,
> enum iio_event_type type, enum iio_event_direction dir,
> @@ -411,6 +426,41 @@ static int iio_device_add_event(struct iio_dev *indio_dev,
> return attrcount;
> }
>
> +static int iio_device_add_event_label(struct iio_dev *indio_dev,
> + const struct iio_chan_spec *chan,
> + unsigned int spec_index,
> + enum iio_event_type type,
> + enum iio_event_direction dir)
> +{
> + struct iio_dev_opaque *iio_dev_opaque = to_iio_dev_opaque(indio_dev);
> + char *postfix;
> + int ret;
> +
> + if (!indio_dev->info->read_event_label)
> + return 0;
> +
> + if (dir != IIO_EV_DIR_NONE)
> + postfix = kasprintf(GFP_KERNEL, "%s_%s_label",
> + iio_ev_type_text[type],
> + iio_ev_dir_text[dir]);
> + else
> + postfix = kasprintf(GFP_KERNEL, "%s_label",
> + iio_ev_type_text[type]);
> + if (postfix == NULL)
> + return -ENOMEM;
> +
> + ret = __iio_add_chan_devattr(postfix, chan, &iio_ev_label_show, NULL,
> + spec_index, IIO_SEPARATE, &indio_dev->dev, NULL,
> + &iio_dev_opaque->event_interface->dev_attr_list);
> +
> + kfree(postfix);
> +
> + if (ret < 0)
> + return ret;
> +
> + return 1;
> +}
> +
> static int iio_device_add_event_sysfs(struct iio_dev *indio_dev,
> struct iio_chan_spec const *chan)
> {
> @@ -448,6 +498,11 @@ static int iio_device_add_event_sysfs(struct iio_dev *indio_dev,
> if (ret < 0)
> return ret;
> attrcount += ret;
> +
> + ret = iio_device_add_event_label(indio_dev, chan, i, type, dir);
> + if (ret < 0)
> + return ret;
> + attrcount += ret;
> }
> ret = attrcount;
> return ret;
> diff --git a/include/linux/iio/iio.h b/include/linux/iio/iio.h
> index 7bfa1b9bc8a2..d0ce3b71106a 100644
> --- a/include/linux/iio/iio.h
> +++ b/include/linux/iio/iio.h
> @@ -427,6 +427,8 @@ struct iio_trigger; /* forward declaration */
> * @write_event_config: set if the event is enabled.
> * @read_event_value: read a configuration value associated with the event.
> * @write_event_value: write a configuration value for the event.
> + * @read_event_label: function to request label name for a specified label,
> + * for better event identification.
> * @validate_trigger: function to validate the trigger when the
> * current trigger gets changed.
> * @update_scan_mode: function to configure device and scan buffer when
> @@ -511,6 +513,12 @@ struct iio_info {
> enum iio_event_direction dir,
> enum iio_event_info info, int val, int val2);
>
> + int (*read_event_label)(struct iio_dev *indio_dev,
> + struct iio_chan_spec const *chan,
> + enum iio_event_type type,
> + enum iio_event_direction dir,
> + char *label);
> +
> int (*validate_trigger)(struct iio_dev *indio_dev,
> struct iio_trigger *trig);
> int (*update_scan_mode)(struct iio_dev *indio_dev,
>
next prev parent reply other threads:[~2023-10-10 15:59 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-06 0:50 [PATCH v4 00/17] iio: resolver: move ad2s1210 out of staging David Lechner
2023-10-06 0:50 ` [PATCH v4 01/17] staging: iio: resolver: ad2s1210: do not use fault register for dummy read David Lechner
2023-10-10 15:38 ` Jonathan Cameron
2023-10-06 0:50 ` [PATCH v4 02/17] staging: iio: resolver: ad2s1210: implement hysteresis as channel attr David Lechner
2023-10-10 15:40 ` Jonathan Cameron
2023-10-06 0:50 ` [PATCH v4 03/17] staging: iio: resolver: ad2s1210: convert fexcit to channel attribute David Lechner
2023-10-10 15:41 ` Jonathan Cameron
2023-10-06 0:50 ` [PATCH v4 04/17] staging: iio: resolver: ad2s1210: convert resolution to devicetree property David Lechner
2023-10-10 15:43 ` Jonathan Cameron
2023-10-06 0:50 ` [PATCH v4 05/17] staging: iio: resolver: ad2s1210: add phase lock range support David Lechner
2023-10-10 15:46 ` Jonathan Cameron
2023-10-06 0:50 ` [PATCH v4 06/17] staging: iio: resolver: ad2s1210: add triggered buffer support David Lechner
2023-10-10 15:47 ` Jonathan Cameron
2023-10-06 0:50 ` [PATCH v4 07/17] staging: iio: resolver: ad2s1210: convert LOT threshold attrs to event attrs David Lechner
2023-10-10 15:54 ` Jonathan Cameron
2023-10-06 0:50 ` [PATCH v4 08/17] staging: iio: resolver: ad2s1210: convert LOS threshold to event attr David Lechner
2023-10-10 15:52 ` Jonathan Cameron
2023-10-06 0:50 ` [PATCH v4 09/17] staging: iio: resolver: ad2s1210: convert DOS overrange " David Lechner
2023-10-10 15:55 ` Jonathan Cameron
2023-10-06 0:50 ` [PATCH v4 10/17] staging: iio: resolver: ad2s1210: convert DOS mismatch " David Lechner
2023-10-10 15:56 ` Jonathan Cameron
2023-10-06 0:50 ` [PATCH v4 11/17] staging: iio: resolver: ad2s1210: rename DOS reset min/max attrs David Lechner
2023-10-10 15:57 ` Jonathan Cameron
2023-10-06 0:50 ` [PATCH v4 12/17] iio: event: add optional event label support David Lechner
2023-10-10 15:59 ` Jonathan Cameron [this message]
2023-10-06 0:50 ` [PATCH v4 13/17] staging: iio: resolver: ad2s1210: implement fault events David Lechner
2023-10-10 16:05 ` Jonathan Cameron
2023-10-06 0:50 ` [PATCH v4 14/17] staging: iio: resolver: ad2s1210: add register/fault support summary David Lechner
2023-10-10 16:07 ` Jonathan Cameron
2023-10-06 0:50 ` [PATCH v4 15/17] staging: iio: resolver: ad2s1210: add label attribute support David Lechner
2023-10-10 16:08 ` Jonathan Cameron
2023-10-06 0:50 ` [PATCH v4 16/17] staging: iio: resolver: ad2s1210: remove fault attribute David Lechner
2023-10-10 16:09 ` Jonathan Cameron
2023-10-06 0:50 ` [PATCH v4 17/17] staging: iio: resolver: ad2s1210: simplify code with guard(mutex) David Lechner
2023-10-10 16:17 ` Jonathan Cameron
2023-10-10 17:40 ` David Lechner
2023-10-10 17:46 ` Jonathan Cameron
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=20231010165917.4c1cb0a9@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=ahaslam@baylibre.com \
--cc=dlechner@baylibre.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=nuno.sa@analog.com \
--cc=pmolloy@baylibre.com \
/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