From: Jonathan Cameron <jic23@kernel.org>
To: Narcisa Ana Maria Vasile <narcisaanamaria12@gmail.com>
Cc: Richard Lai <richard@richardman.com>,
Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: chemical: ccs811: Renamed resistance member in ccs811_reading struct
Date: Sat, 24 Feb 2018 11:06:21 +0000 [thread overview]
Message-ID: <20180224110621.3d8b40b6@archlinux> (raw)
In-Reply-To: <20180220202450.GA11057@nati-X550JK>
On Tue, 20 Feb 2018 22:24:50 +0200
Narcisa Ana Maria Vasile <narcisaanamaria12@gmail.com> wrote:
> On Sat, Feb 17, 2018 at 02:14:42PM +0000, Jonathan Cameron wrote:
> > On Wed, 14 Feb 2018 01:08:35 +0000
> > Richard Lai <richard@richardman.com> wrote:
> >
> > > The resistance member in ccs811_reading struct is an unsigned 16-bit
> > > integer variable used to store RAW_DATA register bytes read from CCS811.
> > > It is kind of misleading to name this struct member as resistance.
> > >
> > > About the RAW_DATA register bytes, the CCS811 datasheet states that:
> > > -----
> > > Two byte read only register which contains the latest readings from the
> > > sense resistor.
> > >
> > > The most significant 6 bits of the Byte 0 contain the value of the current
> > > through the sensor (0μA to 63μA).
> > >
> > > The lower 10 bits contain (as computed from the ADC) the readings of the
> > > voltage across the sensor with the selected current (1023 = 1.65V)"
> > > -----
> > >
> True.
>
> > > Hence, the RAW_DATA register byte contains information about electric
> > > current and voltage of the CCS811 sensor. Calling this struct member
> > > 'resistance' is kind of misleading, although both electric current and
> > > voltage are needed to calculate the electrical resistance of the sensor
> > > using Ohm's law, V = I x R, in which a new channel type of IIO_RESISTANCE
> > > may be added to the driver in the future.
> > >
>
>
> > > Signed-off-by: Richard Lai <richard@richardman.com>
> > This seems logical to me, but I'd just like to let it sit for a few
> > more days to let Narcisa have time to respond.
> >
> I agree, Richard's suggestion is a better fit as a name for this
> register.
Cool. Ideally please give a formal
Acked-by: as then it is recorded in the record rather than deep in an email
archive.
Applied to the togreg branch of iio.git and pushed out as testing for
the autobuilders to play with it.
Thanks,
Jonathan
> > Feel free to give me a poke if it looks like I have forgotten this
> > in a week or so.
> >
> > Thanks,
> >
> > Jonathan
> >
> > > ---
> > > drivers/iio/chemical/ccs811.c | 6 +++---
> > > 1 file changed, 3 insertions(+), 3 deletions(-)
> > >
> > > diff --git a/drivers/iio/chemical/ccs811.c b/drivers/iio/chemical/ccs811.c
> > > index 8e8beb7..e6f6bc4 100644
> > > --- a/drivers/iio/chemical/ccs811.c
> > > +++ b/drivers/iio/chemical/ccs811.c
> > > @@ -66,7 +66,7 @@ struct ccs811_reading {
> > > __be16 voc;
> > > u8 status;
> > > u8 error;
> > > - __be16 resistance;
> > > + __be16 raw_data;
> > > } __attribute__((__packed__));
> > >
> > > struct ccs811_data {
> > > @@ -202,12 +202,12 @@ static int ccs811_read_raw(struct iio_dev *indio_dev,
> > >
> > > switch (chan->type) {
> > > case IIO_VOLTAGE:
> > > - *val = be16_to_cpu(data->buffer.resistance) &
> > > + *val = be16_to_cpu(data->buffer.raw_data) &
> > > CCS811_VOLTAGE_MASK;
> > > ret = IIO_VAL_INT;
> > > break;
> > > case IIO_CURRENT:
> > > - *val = be16_to_cpu(data->buffer.resistance) >> 10;
> > > + *val = be16_to_cpu(data->buffer.raw_data) >> 10;
> > > ret = IIO_VAL_INT;
> > > break;
> > > case IIO_CONCENTRATION:
> >
prev parent reply other threads:[~2018-02-24 11:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-14 1:08 [PATCH] iio: chemical: ccs811: Renamed resistance member in ccs811_reading struct Richard Lai
2018-02-17 14:14 ` Jonathan Cameron
2018-02-20 20:24 ` Narcisa Ana Maria Vasile
2018-02-24 11:06 ` 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=20180224110621.3d8b40b6@archlinux \
--to=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=narcisaanamaria12@gmail.com \
--cc=pmeerw@pmeerw.net \
--cc=richard@richardman.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).