All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@cam.ac.uk>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Michael Hennerich <michael.hennerich@analog.com>,
	linux-iio@vger.kernel.org,
	device-drivers-devel@blackfin.uclinux.org, drivers@analog.com
Subject: Re: [RFC PATCH 2/2] staging:iio: Introduce IIO_CHAN_INFO_*_MASK
Date: Fri, 21 Oct 2011 14:08:11 +0100	[thread overview]
Message-ID: <4EA16EBB.7010800@cam.ac.uk> (raw)
In-Reply-To: <1319199855-24834-2-git-send-email-lars@metafoo.de>

On 10/21/11 13:24, Lars-Peter Clausen wrote:
> Introduce IIO_CHAN_INFO_*_MASK defines which can be used for specifying channel
> a channel_spec info_mask attribute. This should be more convenient and also
> more readable than creating the mask manually in each driver using the shift
> operator.
> 
Fair enough.  Could call them IIO_CHAN_INFO_SCALE_SHARED_BIT etc?
Marginally more accurate.  MASK kind of implies multiple bits to
my mind...
> Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
> ---
> Patch based on linux-iio/master
> ---
>  drivers/staging/iio/iio.h |   37 +++++++++++++++++++++++++++++++++++++
>  1 files changed, 37 insertions(+), 0 deletions(-)
> 
> diff --git a/drivers/staging/iio/iio.h b/drivers/staging/iio/iio.h
> index d7c5f3f..7ff8c98 100644
> --- a/drivers/staging/iio/iio.h
> +++ b/drivers/staging/iio/iio.h
> @@ -46,6 +46,43 @@ enum iio_chan_info_enum {
>  	IIO_CHAN_INFO_AVERAGE_RAW_SEPARATE,
>  };
>  
> +#define IIO_CHAN_INFO_SCALE_SHARED_MASK				\
> +	BIT(IIO_CHAN_INFO_SCALE_SHARED)
> +#define IIO_CHAN_INFO_SCALE_SEPARATE_MASK			\
> +	BIT(IIO_CHAN_INFO_SCALE_SEPARATE)
> +#define IIO_CHAN_INFO_OFFSET_SHARED_MASK			\
> +	BIT(IIO_CHAN_INFO_OFFSET_SHARED)
> +#define IIO_CHAN_INFO_OFFSET_SEPARATE_MASK			\
> +	BIT(IIO_CHAN_INFO_OFFSET_SEPARATE)
> +#define IIO_CHAN_INFO_CALIBSCALE_SHARED_MASK			\
> +	BIT(IIO_CHAN_INFO_CALIBSCALE_SHARED)
> +#define IIO_CHAN_INFO_CALIBSCALE_SEPARATE_MASK			\
> +	BIT(IIO_CHAN_INFO_CALIBSCALE_SEPARATE)
> +#define IIO_CHAN_INFO_CALIBBIAS_SHARED_MASK			\
> +	BIT(IIO_CHAN_INFO_CALIBBIAS_SHARED)
> +#define IIO_CHAN_INFO_CALIBBIAS_SEPARATE_MASK			\
> +	BIT(IIO_CHAN_INFO_CALIBBIAS_SEPARATE)
> +#define IIO_CHAN_INFO_PEAK_SHARED_MASK				\
> +	BIT(IIO_CHAN_INFO_PEAK_SHARED)
> +#define IIO_CHAN_INFO_PEAK_SEPARATE_MASK			\
> +	BIT(IIO_CHAN_INFO_PEAK_SEPARATE)
> +#define IIO_CHAN_INFO_PEAK_SCALE_SHARED_MASK			\
> +	BIT(IIO_CHAN_INFO_PEAK_SCALE_SHARED)
> +#define IIO_CHAN_INFO_PEAK_SCALE_SHARED_MASK			\
> +	BIT(IIO_CHAN_INFO_PEAK_SCALE_SHARED)
> +#define IIO_CHAN_INFO_SCALE_SHARED_MASK				\
> +	BIT(IIO_CHAN_INFO_SCALE_SHARED)
> +#define IIO_CHAN_INFO_SCALE_SEPARATE_MASK			\
> +	BIT(IIO_CHAN_INFO_SCALE_SEPARATE)
> +#define IIO_CHAN_INFO_QUADRATURE_CORRECTION_RAW_SHARED_MASK	\
> +	BIT(IIO_CHAN_INFO_QUADRATURE_CORRECTION_RAW_SHARED)
> +#define IIO_CHAN_INFO_QUADRATURE_CORRECTION_RAW_SEPARATE_MASK	\
> +	BIT(IIO_CHAN_INFO_QUADRATURE_CORRECTION_RAW_SEPARATE)
> +#define IIO_CHAN_INFO_AVERAGE_RAW_SHARED_MASK			\
> +	BIT(IIO_CHAN_INFO_AVERAGE_RAW_SHARED)
> +#define IIO_CHAN_INFO_AVERAGE_RAW_SEPARATE_MASK			\
> +	BIT(IIO_CHAN_INFO_AVERAGE_RAW_SEPARATE)
> +
>  enum iio_endian {
>  	IIO_CPU,
>  	IIO_BE,


  reply	other threads:[~2011-10-21 13:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-21 12:24 [RFC 1/2] staging:iio: Do not use bitmasks for channel info addresses Lars-Peter Clausen
2011-10-21 12:24 ` [RFC PATCH 2/2] staging:iio: Introduce IIO_CHAN_INFO_*_MASK Lars-Peter Clausen
2011-10-21 13:08   ` Jonathan Cameron [this message]
2011-10-21 13:24 ` [RFC 1/2] staging:iio: Do not use bitmasks for channel info addresses Jonathan Cameron
2011-10-21 13:50   ` Lars-Peter Clausen
2011-10-21 14:09     ` 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=4EA16EBB.7010800@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 \
    --cc=michael.hennerich@analog.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.