From: Jonathan Cameron <jic23@kernel.org>
To: Matt Ranostay <matt.ranostay@konsulko.com>
Cc: Jonathan Cameron <Jonathan.Cameron@huawei.com>,
"open list:IIO SUBSYSTEM AND DRIVERS" <linux-iio@vger.kernel.org>
Subject: Re: [PATCH] iio: chemical: atlas-sensor: correct DO-SM channels
Date: Sat, 25 Apr 2020 14:37:25 +0100 [thread overview]
Message-ID: <20200425143725.70f488aa@archlinux> (raw)
In-Reply-To: <CAJCx=gnjj6pp9=aEKohdmxrsm+aRgSO9wus3p8oLd01JQGoOUw@mail.gmail.com>
On Wed, 22 Apr 2020 20:43:15 -0700
Matt Ranostay <matt.ranostay@konsulko.com> wrote:
> On Wed, Apr 22, 2020 at 8:42 PM Matt Ranostay
> <matt.ranostay@konsulko.com> wrote:
> >
> > On Wed, Apr 22, 2020 at 10:27 AM Jonathan Cameron
> > <Jonathan.Cameron@huawei.com> wrote:
> > >
> > > On Mon, 20 Apr 2020 02:28:47 +0300
> > > Matt Ranostay <matt.ranostay@konsulko.com> wrote:
> > >
> > > > IIO_CONCENTRATION channel for the DO-SM shouldn't be indexed as
> > > > there isn't more than one, and also ATLAS_CONCENTRATION_CHANNEL
> > > > macro scan_index define steps on the IIO_TIMESTAMP channel.
> > > >
> >
> > Fixes: 1a881ed8a43b (iio: chemical: atlas-sensor: add RTD-SM module support)
>
> Oops wrong change for Fixes tag. Sorry about that..
>
> Fixes: a751b8e48018 (iio: chemical: atlas-sensor: add DO-SM module support)
So the index thing isn't really a fix as such. It's perfectly valid for
a single channel to be indexed even if not required. Still it's your
driver so if you prefer it this way fair enough.
The other bit obviously is a fix so I'll just take this whole thing as a
fix. Applied to the fixes-togreg branch of iio.git
Thanks,
Jonathan
>
> >
> > > > Signed-off-by: Matt Ranostay <matt.ranostay@konsulko.com>
> > >
> > > Fixes tag?
> > >
> > > J
> > > > ---
> > > > drivers/iio/chemical/atlas-sensor.c | 14 +++++++++++++-
> > > > 1 file changed, 13 insertions(+), 1 deletion(-)
> > > >
> > > > diff --git a/drivers/iio/chemical/atlas-sensor.c
> > > > b/drivers/iio/chemical/atlas-sensor.c index
> > > > 82d470561ad3..7b199ce16ecf 100644 ---
> > > > a/drivers/iio/chemical/atlas-sensor.c +++
> > > > b/drivers/iio/chemical/atlas-sensor.c @@ -194,7 +194,19 @@ static
> > > > const struct iio_chan_spec atlas_orp_channels[] = { };
> > > >
> > > > static const struct iio_chan_spec atlas_do_channels[] = {
> > > > - ATLAS_CONCENTRATION_CHANNEL(0, ATLAS_REG_DO_DATA),
> > > > + {
> > > > + .type = IIO_CONCENTRATION,
> > > > + .address = ATLAS_REG_DO_DATA,
> > > > + .info_mask_separate =
> > > > + BIT(IIO_CHAN_INFO_RAW) |
> > > > BIT(IIO_CHAN_INFO_SCALE),
> > > > + .scan_index = 0,
> > > > + .scan_type = {
> > > > + .sign = 'u',
> > > > + .realbits = 32,
> > > > + .storagebits = 32,
> > > > + .endianness = IIO_BE,
> > > > + },
> > > > + },
> > > > IIO_CHAN_SOFT_TIMESTAMP(1),
> > > > {
> > > > .type = IIO_TEMP,
> > >
prev parent reply other threads:[~2020-04-25 13:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-19 23:28 [PATCH] iio: chemical: atlas-sensor: correct DO-SM channels Matt Ranostay
2020-04-22 17:27 ` Jonathan Cameron
2020-04-23 3:42 ` Matt Ranostay
2020-04-23 3:43 ` Matt Ranostay
2020-04-25 13:37 ` 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=20200425143725.70f488aa@archlinux \
--to=jic23@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=linux-iio@vger.kernel.org \
--cc=matt.ranostay@konsulko.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