From: Matt Ranostay <matt.ranostay@konsulko.com>
To: Jeremy Fertic <jeremyfertic@gmail.com>
Cc: "open list:IIO SUBSYSTEM AND DRIVERS" <linux-iio@vger.kernel.org>,
Jonathan Cameron <jic23@kernel.org>
Subject: Re: [PATCH v4 1/3] iio: chemical: atlas-sensor: allow probe without interrupt line
Date: Thu, 6 Feb 2020 20:59:48 -0800 [thread overview]
Message-ID: <CAJCx=g=tNfTptvCunJ7fwrZyYsKVmKieWyLEeL5C1dCnGMd-AA@mail.gmail.com> (raw)
In-Reply-To: <20200207005320.GA3589@r2700x.localdomain>
On Thu, Feb 6, 2020 at 4:53 PM Jeremy Fertic <jeremyfertic@gmail.com> wrote:
>
> On Wed, Feb 05, 2020 at 10:13:30PM -0800, Matt Ranostay wrote:
> > Sensors don't actually need a interrupt line to give valid readings,
> > and can triggered with CONFIG_IIO_HRTIMER_TRIGGER as well. Remove
> > the required check for interrupt, and continue along in the probe
> > function.
> >
> > Signed-off-by: Matt Ranostay <matt.ranostay@konsulko.com>
> > ---
> > drivers/iio/chemical/atlas-sensor.c | 27 ++++++++++++---------------
> > 1 file changed, 12 insertions(+), 15 deletions(-)
> >
> > diff --git a/drivers/iio/chemical/atlas-sensor.c b/drivers/iio/chemical/atlas-sensor.c
> > index 2f0a6fed2589..2e34c82cb65d 100644
> > --- a/drivers/iio/chemical/atlas-sensor.c
> > +++ b/drivers/iio/chemical/atlas-sensor.c
> > @@ -572,11 +572,6 @@ static int atlas_probe(struct i2c_client *client,
> > if (ret)
> > return ret;
> >
> > - if (client->irq <= 0) {
> > - dev_err(&client->dev, "no valid irq defined\n");
> > - return -EINVAL;
> > - }
> > -
> > ret = chip->calibration(data);
> > if (ret)
> > return ret;
> > @@ -596,16 +591,18 @@ static int atlas_probe(struct i2c_client *client,
> >
> > init_irq_work(&data->work, atlas_work_handler);
> >
> > - /* interrupt pin toggles on new conversion */
> > - ret = devm_request_threaded_irq(&client->dev, client->irq,
> > - NULL, atlas_interrupt_handler,
> > - IRQF_TRIGGER_RISING |
> > - IRQF_TRIGGER_FALLING | IRQF_ONESHOT,
> > - "atlas_irq",
> > - indio_dev);
> > - if (ret) {
> > - dev_err(&client->dev, "request irq (%d) failed\n", client->irq);
> > - goto unregister_buffer;
> > + if (client->irq <= 0) {
>
> Should this be > 0 ?
>
Ah yes good catch :/
- Matt
> Jeremy
>
> > + /* interrupt pin toggles on new conversion */
> > + ret = devm_request_threaded_irq(&client->dev, client->irq,
> > + NULL, atlas_interrupt_handler,
> > + IRQF_TRIGGER_RISING |
> > + IRQF_TRIGGER_FALLING | IRQF_ONESHOT,
> > + "atlas_irq",
> > + indio_dev);
> > +
> > + if (ret)
> > + dev_warn(&client->dev,
> > + "request irq (%d) failed\n", client->irq);
> > }
> >
> > ret = atlas_set_powermode(data, 1);
> > --
> > 2.20.1
> >
next prev parent reply other threads:[~2020-02-07 5:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-06 6:13 [PATCH v4 0/3] iio: chemical: atlas-sensor: add DO support Matt Ranostay
2020-02-06 6:13 ` [PATCH v4 1/3] iio: chemical: atlas-sensor: allow probe without interrupt line Matt Ranostay
2020-02-07 0:53 ` Jeremy Fertic
2020-02-07 4:59 ` Matt Ranostay [this message]
2020-02-08 16:39 ` Jonathan Cameron
2020-02-09 2:12 ` Matt Ranostay
2020-02-09 2:16 ` Matt Ranostay
2020-02-14 13:27 ` Jonathan Cameron
2020-02-06 6:13 ` [PATCH v4 2/3] iio: chemical: atlas-sensor: add DO-SM module support Matt Ranostay
2020-02-08 16:41 ` Jonathan Cameron
2020-02-06 6:13 ` [PATCH v4 3/3] dt-bindings: iio: chemical: consolidate atlas-sensor docs Matt Ranostay
2020-02-06 21:52 ` Rob Herring
2020-02-08 16:34 ` 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='CAJCx=g=tNfTptvCunJ7fwrZyYsKVmKieWyLEeL5C1dCnGMd-AA@mail.gmail.com' \
--to=matt.ranostay@konsulko.com \
--cc=jeremyfertic@gmail.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
/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).