From: Jonathan Cameron <jic23@cam.ac.uk>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: linux-iio@vger.kernel.org,
device-drivers-devel@blackfin.uclinux.org, drivers@analog.com
Subject: Re: [PATCH v2 1/6] staging:iio: Add extended IIO channel info
Date: Tue, 21 Feb 2012 15:40:11 +0000 [thread overview]
Message-ID: <4F43BADB.8090702@cam.ac.uk> (raw)
In-Reply-To: <1329738920-14281-1-git-send-email-lars@metafoo.de>
On 2/20/2012 11:55 AM, Lars-Peter Clausen wrote:
> Sometimes devices have per channel properties which either do not map nicely to
> the current channel info scheme (e.g. string properties) or are very device
> specific, so it does not make sense to add generic support for them.
>
> Currently drivers define these attributes by hand for each channel. Depending on
> the number of channels this can amount to quite a few lines of boilerplate code.
> Especially if a driver supports multiple variations of a chip with different
> numbers of channels. In this case it becomes necessary to have a individual
> attribute list per chip variation and also a individual iio_info struct.
>
> This patch introduces a new scheme for handling such per channel attributes
> called extended channel info attributes. A extended channel info attribute
> consist of a name, a flag whether it is shared and read and write callbacks.
> The read and write callbacks are similar to the {read,write}_raw callbacks and
> take a IIO device and a channel as their first parameters, but instead of
> pre-parsed integer values they directly get passed the raw string value, which
> has been written to the sysfs file.
>
> It is possible to assign a list of extended channel info attributes to a
> channel. For each extended channel info attribute the IIO core will create a new
> sysfs attribute conforming to the IIO channel naming spec for the channels type,
> similar as for normal info attributes. Read and write access to this sysfs
> attribute will be redirected to the extended channel info attributes read and
> write callbacks.
>
> Signed-off-by: Lars-Peter Clausen<lars@metafoo.de>
Other than one trivial nitpick.
Acked-by: Jonathan Cameron <jic23@kernel.org>
Note we'll have to be careful to make sure this facility doesn't get
abused. But that should be
no harder than currently with the attrs.
>
> ---
> Changes since v1:
> * Do not move the -EBUSY handling for duplicated shared attributes to
> __iio_add_chan_devattr since it will cause us to count shared attributes
> multiple times, thus allocating more attributes than we actually use.
> ---
> drivers/staging/iio/iio.h | 23 +++++++++++++
> drivers/staging/iio/industrialio-core.c | 54 +++++++++++++++++++++++++++++++
> 2 files changed, 77 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/staging/iio/iio.h b/drivers/staging/iio/iio.h
> index be6ced3..9140c2a 100644
> --- a/drivers/staging/iio/iio.h
> +++ b/drivers/staging/iio/iio.h
> @@ -88,6 +88,25 @@ enum iio_endian {
> IIO_LE,
> };
>
> +struct iio_chan_spec;
> +struct iio_dev;
> +
> +/**
> + * struct iio_chan_spec_ext_info - Extended channel info attribute
> + * @name: Info attribute name
> + * @shared: Whether this attribute is shared between all channels.
> + * @read: Read callback for this info attribute, may be NULL.
> + * @write: Write callback for this info attribute, may be NULL.
> + */
> +struct iio_chan_spec_ext_info {
> + const char *name;
> + bool shared;
> + ssize_t (*read)(struct iio_dev *, struct iio_chan_spec const *,
> + char *buf);
> + ssize_t (*write)(struct iio_dev *, struct iio_chan_spec const *,
> + const char *buf, size_t len);
> +};
> +
> /**
> * struct iio_chan_spec - specification of a single channel
> * @type: What type of measurement is the channel making.
> @@ -107,6 +126,9 @@ enum iio_endian {
> * @info_mask: What information is to be exported about this channel.
> * This includes calibbias, scale etc.
> * @event_mask: What events can this channel produce.
> + * @ext_info: Array of extended info attributes for this channel.
> + * The array is NULL terminated, the last element should
> + * have it's name field set to NULL.
> * @extend_name: Allows labeling of channel attributes with an
> * informative name. Note this has no effect codes etc,
> * unlike modifiers.
> @@ -141,6 +163,7 @@ struct iio_chan_spec {
> } scan_type;
> long info_mask;
> long event_mask;
> + const struct iio_chan_spec_ext_info *ext_info;
> char *extend_name;
> const char *datasheet_name;
> unsigned processed_val:1;
> diff --git a/drivers/staging/iio/industrialio-core.c b/drivers/staging/iio/industrialio-core.c
> index e4824fe..380b927 100644
> --- a/drivers/staging/iio/industrialio-core.c
> +++ b/drivers/staging/iio/industrialio-core.c
> @@ -144,6 +144,33 @@ static void __exit iio_exit(void)
> bus_unregister(&iio_bus_type);
> }
>
> +static ssize_t iio_read_channel_ext_info(struct device *dev,
> + struct device_attribute *attr,
> + char *buf)
> +{
> + struct iio_dev *indio_dev = dev_get_drvdata(dev);
> + struct iio_dev_attr *this_attr = to_iio_dev_attr(attr);
> + const struct iio_chan_spec_ext_info *ext_info;
> +
> + ext_info =&this_attr->c->ext_info[this_attr->address];
> +
> + return ext_info->read(indio_dev, this_attr->c, buf);
> +}
> +
> +static ssize_t iio_write_channel_ext_info(struct device *dev,
> + struct device_attribute *attr,
> + const char *buf,
> + size_t len)
> +{
> + struct iio_dev *indio_dev = dev_get_drvdata(dev);
> + struct iio_dev_attr *this_attr = to_iio_dev_attr(attr);
> + const struct iio_chan_spec_ext_info *ext_info;
> +
> + ext_info =&this_attr->c->ext_info[this_attr->address];
> +
> + return ext_info->write(indio_dev, this_attr->c, buf, len);
> +}
> +
> static ssize_t iio_read_channel_info(struct device *dev,
> struct device_attribute *attr,
> char *buf)
> @@ -423,6 +450,7 @@ static int iio_device_add_channel_sysfs(struct iio_dev *indio_dev,
> struct iio_chan_spec const *chan)
> {
> int ret, i, attrcount = 0;
> + const struct iio_chan_spec_ext_info *ext_info;
>
> if (chan->channel< 0)
> return 0;
> @@ -457,6 +485,32 @@ static int iio_device_add_channel_sysfs(struct iio_dev *indio_dev,
> goto error_ret;
> attrcount++;
> }
> +
> + if (chan->ext_info) {
> + unsigned int i = 0;
> + for (ext_info = chan->ext_info; ext_info->name; ext_info++) {
> + ret = __iio_add_chan_devattr(ext_info->name,
> + chan,
> + ext_info->read ?
> + &iio_read_channel_ext_info : NULL,
> + ext_info->write ?
> + &iio_write_channel_ext_info : NULL,
> + i,
> + ext_info->shared,
> + &indio_dev->dev,
> + &indio_dev->channel_attr_list);
> + i++;
> + if (ret == -EBUSY&& ext_info->shared)
> + continue;
> +
> + if (ret)
> + goto error_ret;
> +
> + attrcount++;
> + }
Excess blank line.
> +
> + }
> +
> ret = attrcount;
> error_ret:
> return ret;
prev parent reply other threads:[~2012-02-21 15:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-20 11:55 [PATCH v2 1/6] staging:iio: Add extended IIO channel info Lars-Peter Clausen
2012-02-20 11:55 ` [PATCH v2 2/6] staging:iio:dac:ad5064: Convert to extended channel info attributes Lars-Peter Clausen
2012-02-21 15:43 ` Jonathan Cameron
2012-02-20 11:55 ` [PATCH v2 3/6] staging:iio:dac:ad5064: Prepare driver for the addition of chip variants Lars-Peter Clausen
2012-02-21 15:12 ` Jonathan Cameron
2012-02-20 11:55 ` [PATCH v2 4/6] staging:iio:dac:ad5064: Add AD5025/AD5045/AD5065 support Lars-Peter Clausen
2012-02-21 15:13 ` Jonathan Cameron
2012-02-20 11:55 ` [PATCH v2 5/6] staging:iio:dac:ad5064: Add AD5628/AD5648/AD5668 support Lars-Peter Clausen
2012-02-21 15:36 ` Jonathan Cameron
2012-02-20 11:55 ` [PATCH v2 6/6] staging:iio:dac:ad5064: Add AD5666 support Lars-Peter Clausen
2012-02-21 15:40 ` 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=4F43BADB.8090702@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=device-drivers-devel@blackfin.uclinux.org \
--cc=drivers@analog.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).