From: Jonathan Cameron <jic23@kernel.org>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Jonathan Cameron <jic23@cam.ac.uk>, linux-iio@vger.kernel.org
Subject: Re: [PATCH 6/7] staging:iio:ad7291: Use sign_extend32 instead of open-coding it
Date: Fri, 14 Jun 2013 21:54:27 +0100 [thread overview]
Message-ID: <51BB8303.8070105@kernel.org> (raw)
In-Reply-To: <1371225508-32190-6-git-send-email-lars@metafoo.de>
On 06/14/2013 04:58 PM, Lars-Peter Clausen wrote:
> This makes it a bit more obvious what is going on than open-coding it.
>
> Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
applied to the togreg branch of iio.git
> ---
> drivers/staging/iio/adc/ad7291.c | 11 +++--------
> 1 file changed, 3 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/staging/iio/adc/ad7291.c b/drivers/staging/iio/adc/ad7291.c
> index 2a7e6a7..c2709d6 100644
> --- a/drivers/staging/iio/adc/ad7291.c
> +++ b/drivers/staging/iio/adc/ad7291.c
> @@ -275,7 +275,6 @@ static int ad7291_read_event_value(struct iio_dev *indio_dev,
> struct ad7291_chip_info *chip = iio_priv(indio_dev);
> int ret;
> u16 uval;
> - s16 signval;
>
> ret = ad7291_i2c_read(chip, ad7291_threshold_reg(event_code), &uval);
> if (ret < 0)
> @@ -286,8 +285,7 @@ static int ad7291_read_event_value(struct iio_dev *indio_dev,
> *val = uval & AD7291_VALUE_MASK;
> return 0;
> case IIO_TEMP:
> - signval = (s16)((uval & AD7291_VALUE_MASK) << 4) >> 4;
> - *val = signval;
> + *val = sign_extend32(uval, 11);
> return 0;
> default:
> return -EINVAL;
> @@ -397,7 +395,6 @@ static int ad7291_read_raw(struct iio_dev *indio_dev,
> int ret;
> struct ad7291_chip_info *chip = iio_priv(indio_dev);
> u16 regval;
> - s16 signval;
>
> switch (mask) {
> case IIO_CHAN_INFO_RAW:
> @@ -433,8 +430,7 @@ static int ad7291_read_raw(struct iio_dev *indio_dev,
> AD7291_T_SENSE);
> if (ret < 0)
> return ret;
> - signval = (s16)((ret & AD7291_VALUE_MASK) << 4) >> 4;
> - *val = signval;
> + *val = sign_extend32(ret, 11);
> return IIO_VAL_INT;
> default:
> return -EINVAL;
> @@ -444,8 +440,7 @@ static int ad7291_read_raw(struct iio_dev *indio_dev,
> AD7291_T_AVERAGE);
> if (ret < 0)
> return ret;
> - signval = (s16)((ret & AD7291_VALUE_MASK) << 4) >> 4;
> - *val = signval;
> + *val = sign_extend32(ret, 11);
> return IIO_VAL_INT;
> case IIO_CHAN_INFO_SCALE:
> switch (chan->type) {
>
next prev parent reply other threads:[~2013-06-15 9:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-14 15:58 [PATCH 1/7] staging:iio:ad7291: Use IIO_VAL_FRACTIONAL_LOG2 Lars-Peter Clausen
2013-06-14 15:58 ` [PATCH 2/7] staging:iio:ad7291: Remove userspace reset Lars-Peter Clausen
2013-06-14 20:51 ` Jonathan Cameron
2013-06-14 15:58 ` [PATCH 3/7] staging:iio:ad7291: Remove unnecessary dev_info() from probe() Lars-Peter Clausen
2013-06-14 15:58 ` [PATCH 4/7] staging:iio:ad7291: Simplify threshold register lookup Lars-Peter Clausen
2013-06-14 15:58 ` [PATCH 5/7] staging:iio:ad7291: Use i2c_smbus_{read,write}_word_swapped instead of open-coding it Lars-Peter Clausen
2013-06-14 15:58 ` [PATCH 6/7] staging:iio:ad7291: Use sign_extend32 " Lars-Peter Clausen
2013-06-14 20:54 ` Jonathan Cameron [this message]
2013-06-14 15:58 ` [PATCH 7/7] staging:iio:ad7291: Rework regulator handling Lars-Peter Clausen
2013-06-14 20:55 ` Jonathan Cameron
2013-06-14 20:50 ` [PATCH 1/7] staging:iio:ad7291: Use IIO_VAL_FRACTIONAL_LOG2 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=51BB8303.8070105@kernel.org \
--to=jic23@kernel.org \
--cc=jic23@cam.ac.uk \
--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