From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: David Veenstra <davidjulianveenstra@gmail.com>
Cc: <lars@metafoo.de>, <jic23@kernel.org>,
<Michael.Hennerich@analog.com>, <knaack.h@gmx.de>,
<linux-iio@vger.kernel.org>, <devel@driverdev.osuosl.org>
Subject: Re: [PATCH 07/11] staging: iio: ad2s1200: Ensure udelay(1) in all necessary code paths
Date: Fri, 23 Mar 2018 13:20:24 +0000 [thread overview]
Message-ID: <20180323142024.00005edb@huawei.com> (raw)
In-Reply-To: <0bf705c8d642bdd9d3a3b7e4653028a88df76ff9.1521379685.git.davidjulianveenstra@gmail.com>
On Sun, 18 Mar 2018 14:36:15 +0100
David Veenstra <davidjulianveenstra@gmail.com> wrote:
> After a successful spi transaction, a udelay(1) is needed.
> This doesn't happen for the default case of the switch statement
> in ad2s1200_read_raw. This patch makes sure that it does.
>
> Signed-off-by: David Veenstra <davidjulianveenstra@gmail.com>
Given this one can't actually happen as the chan->type
is always one of the two options, I can't see the point
in making sure we sleep.
The default is really just there to catch bugs and to suppress
the build warning we would otherwise get.
So I am unconvinced on this patch.
Jonathan
> ---
> drivers/staging/iio/resolver/ad2s1200.c | 8 +++++---
> 1 file changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/staging/iio/resolver/ad2s1200.c b/drivers/staging/iio/resolver/ad2s1200.c
> index e0e7c88368ed..6ce9ca13094a 100644
> --- a/drivers/staging/iio/resolver/ad2s1200.c
> +++ b/drivers/staging/iio/resolver/ad2s1200.c
> @@ -78,20 +78,22 @@ static int ad2s1200_read_raw(struct iio_dev *indio_dev,
> switch (chan->type) {
> case IIO_ANGL:
> *val = vel >> 4;
> + ret = IIO_VAL_INT;
> break;
> case IIO_ANGL_VEL:
> *val = sign_extend32((s16)vel >> 4, 11);
> + ret = IIO_VAL_INT;
> break;
> default:
> - mutex_unlock(&st->lock);
> - return -EINVAL;
> + ret = -EINVAL;
> + break;
> }
>
> /* delay (2 * AD2S1200_TSCLK + 20) ns for sample pulse */
> udelay(1);
> mutex_unlock(&st->lock);
>
> - return IIO_VAL_INT;
> + return ret;
> }
>
> static const struct iio_chan_spec ad2s1200_channels[] = {
next prev parent reply other threads:[~2018-03-23 13:20 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-18 13:33 [PATCH 00/11] staging: iio: ad2s1200: Driver clean up David Veenstra
2018-03-18 13:34 ` [PATCH 01/11] staging: iio: ad2s1200: Sort includes alphabetically David Veenstra
2018-03-18 13:34 ` [PATCH 02/11] staging: iio: ad2s1200: Reverse Christmas tree order David Veenstra
2018-03-18 13:34 ` [PATCH 03/11] staging: iio: ad2s1200: Add blank lines David Veenstra
2018-03-18 13:35 ` [PATCH 04/11] staging: iio: ad2s1200: Add kernel docs to driver state David Veenstra
2018-03-18 13:35 ` [PATCH 05/11] staging: iio: ad2s1200: Introduce variable for repeated value David Veenstra
2018-03-23 13:17 ` Jonathan Cameron
2018-03-24 12:22 ` David Julian Veenstra
2018-03-24 14:04 ` Jonathan Cameron
2018-03-18 13:35 ` [PATCH 06/11] staging: iio: ad2s1200: Improve readability with be16_to_cpup David Veenstra
2018-03-18 13:36 ` [PATCH 07/11] staging: iio: ad2s1200: Ensure udelay(1) in all necessary code paths David Veenstra
2018-03-23 13:20 ` Jonathan Cameron [this message]
2018-03-24 12:26 ` David Julian Veenstra
2018-03-18 13:36 ` [PATCH 08/11] staging: iio: ad2s1200: Replace legacy gpio ABI with modern ABI David Veenstra
2018-03-23 13:23 ` Jonathan Cameron
2018-03-18 13:36 ` [PATCH 09/11] staging: iio: ad2s1200: Add scaling factor for IIO_ANGL_VEL channel David Veenstra
2018-03-18 13:37 ` [PATCH 10/11] staging: iio: ad2s1200: Replace angle channel with inclination channel David Veenstra
2018-03-23 13:27 ` Jonathan Cameron
2018-03-24 12:36 ` David Julian Veenstra
2018-03-24 14:12 ` Jonathan Cameron
2018-03-24 14:57 ` David Julian Veenstra
2018-03-24 17:40 ` Jonathan Cameron
2018-03-18 13:37 ` [PATCH 11/11] Move resolver ad2c1200 driver out of staging to mainline iio David Veenstra
2018-03-23 13:29 ` 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=20180323142024.00005edb@huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=Michael.Hennerich@analog.com \
--cc=davidjulianveenstra@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--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).