From: Jonathan Cameron <jic23@kernel.org>
To: Matt Ranostay <mranostay@gmail.com>
Cc: Jonathan Cameron <jic23@jic23.retrosnub.co.uk>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: Re: [PATCH] iio: hdc100x: correct IIO_CHAN_INFO_OFFSET value
Date: Sun, 11 Oct 2015 13:53:47 +0100 [thread overview]
Message-ID: <561A5BDB.6050401@kernel.org> (raw)
In-Reply-To: <CAKzfze94uQuG9OeyP8yMsR=Zfe94tzBScHTvPJ8g0ppcKv60Lg@mail.gmail.com>
On 05/10/15 06:57, Matt Ranostay wrote:
> On Tue, Sep 29, 2015 at 10:33 AM, Jonathan Cameron <jic23@kernel.org> wrote:
>> On 29/09/15 05:19, Matt Ranostay wrote:
>>> On Mon, Sep 28, 2015 at 2:08 AM, Jonathan Cameron
>>> <jic23@jic23.retrosnub.co.uk> wrote:
>>>>
>>>>
>>>> On 27 September 2015 23:35:29 BST, Matt Ranostay <mranostay@gmail.com> wrote:
>>>>> On Sun, Sep 27, 2015 at 6:29 AM, Jonathan Cameron <jic23@kernel.org>
>>>>> wrote:
>>>>>> On 27/09/15 07:18, Matt Ranostay wrote:
>>>>>>> Previous offset wasn't applied in the correct order and invalid.
>>>>>>> This patchset fixes this issue, and also has the correct scale value
>>>>>>> applied to the offset.
>>>>>>>
>>>>>>> Signed-off-by: Matt Ranostay <mranostay@gmail.com>
>>>>>> Oops, missed that.
>>>>>>
>>>>>> Given it's provided in the datasheet as effectively a fractional
>>>>> value
>>>>>> would val = -40000, val2 = 65536 and type = IIO_FRACTIONAL not be
>>>>> cleaner
>>>>>> and give the same answer?
>>>>>>
>>>>> Actually not because the way the datasheet states it ((value / 2**16)
>>>>> * 165) - 40, so the scale value needs to be applied to the -40
>>>>> offset (165/65536)
>>>> Good point. Can't we do (-40*165)/65536 ?
>>>
>>> Nope.
>>>
>>> scale = 165<<2 / 65536
>>> offset = 40 / scale
>>>
>>> Maybe we should add a new IIO_CHAN_INFO_SCALED_OFFSET that uses the
>>> scale value and a divisor that returns an IIO_FRACTIONAL?
>> Hmm. Would get messy fast.
>>
>> Lets just go with your original fixed point option below. If someone later figures
>> out a neater way of doing it, good for them ;)
>
> Ok that works.
Applied to the togreg branch of iio.git - initially pushed out as testing for the
autobuilders to play with it.
Thanks,
Jonathan
>>
>> J
>>>
>>>
>>>>>
>>>>>> Speaking of which, for the scale are we loosing any precision by
>>>>> shifting
>>>>>> the bottom of the fraction right 2 rather than the top left 2 which
>>>>> would have
>>>>>> the same result?
>>>>>
>>>>> Ah possibly. But I suspect isn't anything measurable...
>>>>>
>>>>>>
>>>>>> Jonathan
>>>>>>> ---
>>>>>>> drivers/iio/humidity/hdc100x.c | 5 +++--
>>>>>>> 1 file changed, 3 insertions(+), 2 deletions(-)
>>>>>>>
>>>>>>> diff --git a/drivers/iio/humidity/hdc100x.c
>>>>> b/drivers/iio/humidity/hdc100x.c
>>>>>>> index 2824578..a7f61e8 100644
>>>>>>> --- a/drivers/iio/humidity/hdc100x.c
>>>>>>> +++ b/drivers/iio/humidity/hdc100x.c
>>>>>>> @@ -221,8 +221,9 @@ static int hdc100x_read_raw(struct iio_dev
>>>>> *indio_dev,
>>>>>>> }
>>>>>>> break;
>>>>>>> case IIO_CHAN_INFO_OFFSET:
>>>>>>> - *val = -40;
>>>>>>> - return IIO_VAL_INT;
>>>>>>> + *val = -3971;
>>>>>>> + *val2 = 879096;
>>>>>>> + return IIO_VAL_INT_PLUS_MICRO;
>>>>>>> default:
>>>>>>> return -EINVAL;
>>>>>>> }
>>>>>>>
>>>>>>
>>>>
>>>> --
>>>> Sent from my Android device with K-9 Mail. Please excuse my brevity.
>>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2015-10-11 12:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-27 6:18 [PATCH] iio: hdc100x: correct IIO_CHAN_INFO_OFFSET value Matt Ranostay
2015-09-27 13:29 ` Jonathan Cameron
2015-09-27 22:35 ` Matt Ranostay
2015-09-28 9:08 ` Jonathan Cameron
2015-09-29 4:19 ` Matt Ranostay
2015-09-29 6:21 ` Matt Ranostay
2015-09-29 17:30 ` Jonathan Cameron
2015-09-29 17:33 ` Jonathan Cameron
2015-10-05 5:57 ` Matt Ranostay
2015-10-11 12:53 ` Jonathan Cameron [this message]
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=561A5BDB.6050401@kernel.org \
--to=jic23@kernel.org \
--cc=jic23@jic23.retrosnub.co.uk \
--cc=linux-iio@vger.kernel.org \
--cc=mranostay@gmail.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).