From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: Peter Meerwald <pmeerw@pmeerw.net>
Cc: linux-iio@vger.kernel.org, jic23@kernel.org
Subject: Re: [PATCH] iio: Fix endianness issue in ak8975_read_axis()
Date: Thu, 05 Jun 2014 12:03:32 -0700 [thread overview]
Message-ID: <5390BF04.4050404@linux.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.01.1406052013270.29790@pmeerw.net>
On 06/05/2014 11:17 AM, Peter Meerwald wrote:
> Hello Srinivas,
>
>>> - /* Endian conversion of the measured values. */
>>> - raw = (s16) (le16_to_cpu(meas_reg));
>>> -
>>> /* Clamp to valid range. */
>>> - raw = clamp_t(s16, raw, -4096, 4095);
>>> - *val = raw;
>>> + *val = clamp_t(s16, ret, -4096, 4095);
>>> return IIO_VAL_INT;
>>>
>>> exit:
>>>
>> I did some experiments on little-endian platforms, so your change
>> won't hurt on x86.
>
> good!
>
>> Don't we need to convert for big-endian platforms?
>>
>> When I trace the path for i2c, I don't see any host order
>> conversion.
>
>> order word according to SMBUS specification, low byte on the bus first
>> case I2C_SMBUS_WORD_DATA:
>> case I2C_SMBUS_PROC_CALL:
>> data->word = msgbuf1[0] | (msgbuf1[1] << 8);
>> break;
>> }
>> But there is no host order conversion?
>
> data->word = msgbuf1[0] | (msgbuf1[1] << 8);
> will work irrespective of host endianness
> the story would be different for
> data->word = *(short *)msgbuf1;
> which works for little-endian, but not for big-endian
>
> so: don't worry :)
Oops, my bad. You are correct.
Thanks,
Srinivas
>
> p.
>
next prev parent reply other threads:[~2014-06-05 19:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 8:53 [PATCH] iio: Fix endianness issue in ak8975_read_axis() Peter Meerwald
2014-06-05 17:08 ` Srinivas Pandruvada
2014-06-05 18:17 ` Peter Meerwald
2014-06-05 19:03 ` Srinivas Pandruvada [this message]
2014-06-07 10:51 ` 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=5390BF04.4050404@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
/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.