linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Peter Meerwald <pmeerw@pmeerw.net>, linux-iio@vger.kernel.org
Cc: Kravchenko Oleksandr <x0199363@ti.com>
Subject: Re: [PATCH 1/2] iio:accel:bma180: Use modifier instead of index in channel specification
Date: Sat, 11 Jan 2014 11:39:24 +0000	[thread overview]
Message-ID: <52D12D6C.2020007@kernel.org> (raw)
In-Reply-To: <1389389841-7389-1-git-send-email-pmeerw@pmeerw.net>



On 10/01/14 21:37, Peter Meerwald wrote:
> should use channel modifiers (X/Y/Z), not channel indices
> timestamp channel has scan index 3, not 4
>
Aag.  Whilst a correct fix, this is going to result in a userspace ABI
change.  Driver has been in since 3.12.  We may need to maintain
both ABI's for now and then deprecate it at some point.  Easiest way to do this
will be to have two sets of iio_chan_specs pointing at the same underlying
real channels.

Anyone have a strong opinion about this?

Good spot by the way!

> Signed-off-by: Peter Meerwald <pmeerw@pmeerw.net>
> Cc: Kravchenko Oleksandr <x0199363@ti.com>
> ---
>   drivers/iio/accel/bma180.c | 16 ++++++++--------
>   1 file changed, 8 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/iio/accel/bma180.c b/drivers/iio/accel/bma180.c
> index 3bec922..bfec313 100644
> --- a/drivers/iio/accel/bma180.c
> +++ b/drivers/iio/accel/bma180.c
> @@ -447,14 +447,14 @@ static const struct iio_chan_spec_ext_info bma180_ext_info[] = {
>   	{ },
>   };
>
> -#define BMA180_CHANNEL(_index) {					\
> +#define BMA180_CHANNEL(_axis) {					\
>   	.type = IIO_ACCEL,						\
> -	.indexed = 1,							\
> -	.channel = (_index),						\
> +	.modified = 1,							\
> +	.channel2 = IIO_MOD_##_axis,					\
>   	.info_mask_separate = BIT(IIO_CHAN_INFO_RAW) |			\
>   		BIT(IIO_CHAN_INFO_LOW_PASS_FILTER_3DB_FREQUENCY),	\
>   	.info_mask_shared_by_type = BIT(IIO_CHAN_INFO_SCALE),		\
> -	.scan_index = (_index),						\
> +	.scan_index = AXIS_##_axis,					\
>   	.scan_type = {							\
>   		.sign = 's',						\
>   		.realbits = 14,						\
> @@ -465,10 +465,10 @@ static const struct iio_chan_spec_ext_info bma180_ext_info[] = {
>   }
>
>   static const struct iio_chan_spec bma180_channels[] = {
> -	BMA180_CHANNEL(AXIS_X),
> -	BMA180_CHANNEL(AXIS_Y),
> -	BMA180_CHANNEL(AXIS_Z),
> -	IIO_CHAN_SOFT_TIMESTAMP(4),
> +	BMA180_CHANNEL(X),
> +	BMA180_CHANNEL(Y),
> +	BMA180_CHANNEL(Z),
> +	IIO_CHAN_SOFT_TIMESTAMP(3),
>   };
>
>   static irqreturn_t bma180_trigger_handler(int irq, void *p)
>

  parent reply	other threads:[~2014-01-11 11:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-10 21:37 [PATCH 1/2] iio:accel:bma180: Use modifier instead of index in channel specification Peter Meerwald
2014-01-10 21:37 ` [PATCH 2/2] iio:accel:bma180: Make LOW_PASS_FILTER_3DB_FREQUENCY shared_by_type Peter Meerwald
2014-01-11 11:44   ` Jonathan Cameron
2014-02-08 11:40     ` Jonathan Cameron
2014-02-15 11:05       ` Jonathan Cameron
2014-01-11 11:39 ` Jonathan Cameron [this message]
2014-01-11 15:25   ` [PATCH 1/2] iio:accel:bma180: Use modifier instead of index in channel specification Peter Meerwald
2014-02-08 11:37     ` 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=52D12D6C.2020007@kernel.org \
    --to=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=pmeerw@pmeerw.net \
    --cc=x0199363@ti.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;
as well as URLs for NNTP newsgroup(s).