From: Lars-Peter Clausen <lars@metafoo.de>
To: Marcus Folkesson <marcus.folkesson@gmail.com>
Cc: Jonathan Cameron <jic23@kernel.org>,
Sachin Kamat <sachin.kamat@linaro.org>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: adis16400: Set timestamp as the last element in chan_spec
Date: Fri, 24 Jan 2014 14:46:02 +0100 [thread overview]
Message-ID: <52E26E9A.9040002@metafoo.de> (raw)
In-Reply-To: <1390562644-25124-2-git-send-email-marcus.folkesson@gmail.com>
On 01/24/2014 12:24 PM, Marcus Folkesson wrote:
> This is necessary since timestamp is calculated as the last element
> in iio_compute_scan_bytes().
>
> Signed-off-by: Marcus Folkesson <marcus.folkesson@gmail.com>
Looks good, thanks.
Acked-by: Lars-Peter Clausen
That said, I think we should try to modify the core code so that the scan
index for the timestamp is auto assigned to be always the last one.
> ---
> drivers/iio/imu/adis16400.h | 1 +
> drivers/iio/imu/adis16400_core.c | 10 +++++-----
> 2 files changed, 6 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/iio/imu/adis16400.h b/drivers/iio/imu/adis16400.h
> index 2f8f9d6..0916bf6 100644
> --- a/drivers/iio/imu/adis16400.h
> +++ b/drivers/iio/imu/adis16400.h
> @@ -189,6 +189,7 @@ enum {
> ADIS16300_SCAN_INCLI_X,
> ADIS16300_SCAN_INCLI_Y,
> ADIS16400_SCAN_ADC,
> + ADIS16400_SCAN_TIMESTAMP,
> };
>
> #ifdef CONFIG_IIO_BUFFER
> diff --git a/drivers/iio/imu/adis16400_core.c b/drivers/iio/imu/adis16400_core.c
> index 3fb7757..7f98657 100644
> --- a/drivers/iio/imu/adis16400_core.c
> +++ b/drivers/iio/imu/adis16400_core.c
> @@ -632,7 +632,7 @@ static const struct iio_chan_spec adis16400_channels[] = {
> ADIS16400_MAGN_CHAN(Z, ADIS16400_ZMAGN_OUT, 14),
> ADIS16400_TEMP_CHAN(ADIS16400_TEMP_OUT, 12),
> ADIS16400_AUX_ADC_CHAN(ADIS16400_AUX_ADC, 12),
> - IIO_CHAN_SOFT_TIMESTAMP(12)
> + IIO_CHAN_SOFT_TIMESTAMP(ADIS16400_SCAN_TIMESTAMP),
> };
>
> static const struct iio_chan_spec adis16448_channels[] = {
> @@ -654,7 +654,7 @@ static const struct iio_chan_spec adis16448_channels[] = {
> .scan_type = IIO_ST('s', 16, 16, 0),
> },
> ADIS16400_TEMP_CHAN(ADIS16448_TEMP_OUT, 12),
> - IIO_CHAN_SOFT_TIMESTAMP(11)
> + IIO_CHAN_SOFT_TIMESTAMP(ADIS16400_SCAN_TIMESTAMP),
> };
>
> static const struct iio_chan_spec adis16350_channels[] = {
> @@ -672,7 +672,7 @@ static const struct iio_chan_spec adis16350_channels[] = {
> ADIS16400_MOD_TEMP_CHAN(X, ADIS16350_XTEMP_OUT, 12),
> ADIS16400_MOD_TEMP_CHAN(Y, ADIS16350_YTEMP_OUT, 12),
> ADIS16400_MOD_TEMP_CHAN(Z, ADIS16350_ZTEMP_OUT, 12),
> - IIO_CHAN_SOFT_TIMESTAMP(11)
> + IIO_CHAN_SOFT_TIMESTAMP(ADIS16400_SCAN_TIMESTAMP),
> };
>
> static const struct iio_chan_spec adis16300_channels[] = {
> @@ -685,7 +685,7 @@ static const struct iio_chan_spec adis16300_channels[] = {
> ADIS16400_AUX_ADC_CHAN(ADIS16300_AUX_ADC, 12),
> ADIS16400_INCLI_CHAN(X, ADIS16300_PITCH_OUT, 13),
> ADIS16400_INCLI_CHAN(Y, ADIS16300_ROLL_OUT, 13),
> - IIO_CHAN_SOFT_TIMESTAMP(14)
> + IIO_CHAN_SOFT_TIMESTAMP(ADIS16400_SCAN_TIMESTAMP),
> };
>
> static const struct iio_chan_spec adis16334_channels[] = {
> @@ -696,7 +696,7 @@ static const struct iio_chan_spec adis16334_channels[] = {
> ADIS16400_ACCEL_CHAN(Y, ADIS16400_YACCL_OUT, 14),
> ADIS16400_ACCEL_CHAN(Z, ADIS16400_ZACCL_OUT, 14),
> ADIS16400_TEMP_CHAN(ADIS16350_XTEMP_OUT, 12),
> - IIO_CHAN_SOFT_TIMESTAMP(8)
> + IIO_CHAN_SOFT_TIMESTAMP(ADIS16400_SCAN_TIMESTAMP),
> };
>
> static struct attribute *adis16400_attributes[] = {
>
next prev parent reply other threads:[~2014-01-24 13:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-24 11:24 iio: adis16400: Set timestamp as the last element in Marcus Folkesson
2014-01-24 11:24 ` [PATCH] iio: adis16400: Set timestamp as the last element in chan_spec Marcus Folkesson
2014-01-24 13:46 ` Lars-Peter Clausen [this message]
2014-02-08 11:25 ` 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=52E26E9A.9040002@metafoo.de \
--to=lars@metafoo.de \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcus.folkesson@gmail.com \
--cc=sachin.kamat@linaro.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