All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Daniel Baluta <daniel.baluta@gmail.com>,
	Matt Ranostay <mranostay@gmail.com>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
	Peter Meerwald <pmeerw@pmeerw.net>,
	"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC v1 0/4] iio: new chemical sensor framework and channel types
Date: Sat, 5 Sep 2015 16:55:27 +0100	[thread overview]
Message-ID: <55EB106F.8040401@kernel.org> (raw)
In-Reply-To: <CAEnQRZD=Sy6qPK3+pA_gxqZEdNYRCqUK5O0dk7k16f0D7M-Sow@mail.gmail.com>

On 05/09/15 09:20, Daniel Baluta wrote:
> On Sat, Sep 5, 2015 at 8:53 AM, Matt Ranostay <mranostay@gmail.com> wrote:
>> Initial RFC for new chemical sensor framework, IIO_CONCENTRATION,
>> and IIO_RESISTANCE channel types.
>>
>> Important notes:
>> * Not been tested on real hardware yet but that isn't the main RFC reason and
>>   once hardware is in hand it will be verified
>> * Reason the IIO_CONCENTRATION type isn't in percent but has modifiers for ppm
>>   and ppb is the scale value for the latter would cause a integer overflow
>>   using IIO_VAL_FRACTIONAL
Then add a a return type that deals with that issue.
Perhaps IIO_VAL_FRACTIONAL_DIVMILLION or
something like that.  Will just do the normal calculation but when outputting
append a load of leading zeros.  So val/(val2 * 1000000) = (val/val2) / 1000000
so decimal shift right 6 digits.
> 
> Please add this details also in the commit message introducing
> IIO_CONCENTRATION. Readers
> will faster find commit messages than cover letter.
Indeed, I wouldn't even have read the cover letter (tend to like jumping in the
deep end ;) except that I wondered what Daniel was commenting on!
> 
> Interesting patches Matt! :)
Indeed!
> 
> thanks,
> Daniel.
> --
> 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
> 


      reply	other threads:[~2015-09-05 15:55 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-05  5:53 [RFC v1 0/4] iio: new chemical sensor framework and channel types Matt Ranostay
2015-09-05  5:53 ` [RFC v1 1/4] iio: chemical: Add IIO_CONCENTRATION channel type Matt Ranostay
2015-09-05  7:23   ` Peter Meerwald
2015-09-05 15:51   ` Jonathan Cameron
2015-09-05  5:53 ` [RFC v1 2/4] iio: resistance: add IIO_RESISTANCE " Matt Ranostay
2015-09-05 15:57   ` Jonathan Cameron
2015-09-05  5:53 ` [RFC v1 3/4] devicetree: add SGX Sensortech vendor id Matt Ranostay
2015-09-05  8:10   ` Daniel Baluta
2015-09-05  5:53 ` [RFC v1 4/4] iio: chemical: add SGX VZ89x VOC sensor support Matt Ranostay
2015-09-05  7:45   ` Peter Meerwald
2015-09-05  8:02     ` Matt Ranostay
2015-09-05  8:11       ` Peter Meerwald
2015-09-05 22:58         ` Matt Ranostay
2015-09-05  8:08   ` Daniel Baluta
2015-09-05 16:14   ` Jonathan Cameron
2015-09-05 22:17     ` Matt Ranostay
2015-09-05  8:20 ` [RFC v1 0/4] iio: new chemical sensor framework and channel types Daniel Baluta
2015-09-05 15:55   ` 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=55EB106F.8040401@kernel.org \
    --to=jic23@kernel.org \
    --cc=daniel.baluta@gmail.com \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mranostay@gmail.com \
    --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.