public inbox for linux-iio@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Lorenzo Bianconi <lorenzo@kernel.org>
Cc: Jonathan Cameron <jic23@kernel.org>,
	Lorenzo Bianconi <lorenzo.bianconi@redhat.com>,
	<linux-iio@vger.kernel.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	Denis CIOCCA <denis.ciocca@st.com>
Subject: Re: [PATCH v3] iio: common: st_sensors: fix possible infinite loop in st_sensors_irq_thread
Date: Mon, 11 Jan 2021 13:10:52 +0000	[thread overview]
Message-ID: <20210111131052.000031dc@Huawei.com> (raw)
In-Reply-To: <20210111082134.GA2258@lore-desk>

On Mon, 11 Jan 2021 09:21:34 +0100
Lorenzo Bianconi <lorenzo@kernel.org> wrote:

> > On Tue, 22 Dec 2020 11:53:57 +0100
> > Lorenzo Bianconi <lorenzo.bianconi@redhat.com> wrote:
> >   
> > > >    
> 
> [...]
> 
> > It's a very minor gamble, so I've applied it to the fixes-togreg branch of
> > iio.git.  Fingers crossed no one hits the corner case and has somehow been
> > getting away with it.
> > 
> > Thanks,  
> 
> Hi Jonathan,
> 
> I am not able to find this commit in your tree. Am I missing something?

oops. Now pushed out.

J

> 
> Regards,
> Lorenzo
> 
> > 
> > Jonathan
> >   
> > >   
> > > > Regards,
> > > > Lorenzo
> > > >    
> > > > >
> > > > > It's possible we would be better falling back to interrupt free support
> > > > > in that case rather than failing to probe at all.
> > > > > I think that would be best done by moving the check out to the
> > > > > various per type drivers so we fail in the same fashion as no irq
> > > > > provided + a warning.    
> > > >
> > > >    
> > > > >
> > > > > thanks,
> > > > >
> > > > > Jonathan
> > > > >
> > > > >    
> > > > > > ---
> > > > > > Changes since v2:
> > > > > > - return -EOPNOTSUPP if the drv requests edge IRQ and the sensor does not support
> > > > > >   status register
> > > > > >
> > > > > > Changes since v1:
> > > > > > - return true if the sensor does not have stat_drdy register
> > > > > > ---
> > > > > >  .../common/st_sensors/st_sensors_trigger.c    | 31 ++++++++++---------
> > > > > >  1 file changed, 17 insertions(+), 14 deletions(-)
> > > > > >
> > > > > > diff --git a/drivers/iio/common/st_sensors/st_sensors_trigger.c b/drivers/iio/common/st_sensors/st_sensors_trigger.c
> > > > > > index 0507283bd4c1..2dbd2646e44e 100644
> > > > > > --- a/drivers/iio/common/st_sensors/st_sensors_trigger.c
> > > > > > +++ b/drivers/iio/common/st_sensors/st_sensors_trigger.c
> > > > > > @@ -23,35 +23,31 @@
> > > > > >   * @sdata: Sensor data.
> > > > > >   *
> > > > > >   * returns:
> > > > > > - * 0 - no new samples available
> > > > > > - * 1 - new samples available
> > > > > > - * negative - error or unknown
> > > > > > + * false - no new samples available or read error
> > > > > > + * true - new samples available
> > > > > >   */
> > > > > > -static int st_sensors_new_samples_available(struct iio_dev *indio_dev,
> > > > > > -                                         struct st_sensor_data *sdata)
> > > > > > +static bool st_sensors_new_samples_available(struct iio_dev *indio_dev,
> > > > > > +                                          struct st_sensor_data *sdata)
> > > > > >  {
> > > > > >       int ret, status;
> > > > > >
> > > > > >       /* How would I know if I can't check it? */
> > > > > >       if (!sdata->sensor_settings->drdy_irq.stat_drdy.addr)
> > > > > > -             return -EINVAL;
> > > > > > +             return true;
> > > > > >
> > > > > >       /* No scan mask, no interrupt */
> > > > > >       if (!indio_dev->active_scan_mask)
> > > > > > -             return 0;
> > > > > > +             return false;
> > > > > >
> > > > > >       ret = regmap_read(sdata->regmap,
> > > > > >                         sdata->sensor_settings->drdy_irq.stat_drdy.addr,
> > > > > >                         &status);
> > > > > >       if (ret < 0) {
> > > > > >               dev_err(sdata->dev, "error checking samples available\n");
> > > > > > -             return ret;
> > > > > > +             return false;
> > > > > >       }
> > > > > >
> > > > > > -     if (status & sdata->sensor_settings->drdy_irq.stat_drdy.mask)
> > > > > > -             return 1;
> > > > > > -
> > > > > > -     return 0;
> > > > > > +     return !!(status & sdata->sensor_settings->drdy_irq.stat_drdy.mask);    
> > > > >
> > > > > No need for the !! as you can rely on type conversion to a boolean.
> > > > >    
> > > > > >  }
> > > > > >
> > > > > >  /**
> > > > > > @@ -180,9 +176,15 @@ int st_sensors_allocate_trigger(struct iio_dev *indio_dev,
> > > > > >
> > > > > >       /* Tell the interrupt handler that we're dealing with edges */
> > > > > >       if (irq_trig == IRQF_TRIGGER_FALLING ||
> > > > > > -         irq_trig == IRQF_TRIGGER_RISING)
> > > > > > +         irq_trig == IRQF_TRIGGER_RISING) {
> > > > > > +             if (!sdata->sensor_settings->drdy_irq.stat_drdy.addr) {
> > > > > > +                     dev_err(&indio_dev->dev,
> > > > > > +                             "edge IRQ not supported w/o stat register.\n");
> > > > > > +                     err = -EOPNOTSUPP;
> > > > > > +                     goto iio_trigger_free;
> > > > > > +             }
> > > > > >               sdata->edge_irq = true;
> > > > > > -     else
> > > > > > +     } else {
> > > > > >               /*
> > > > > >                * If we're not using edges (i.e. level interrupts) we
> > > > > >                * just mask off the IRQ, handle one interrupt, then
> > > > > > @@ -190,6 +192,7 @@ int st_sensors_allocate_trigger(struct iio_dev *indio_dev,
> > > > > >                * interrupt handler top half again and start over.
> > > > > >                */
> > > > > >               irq_trig |= IRQF_ONESHOT;
> > > > > > +     }
> > > > > >
> > > > > >       /*
> > > > > >        * If the interrupt pin is Open Drain, by definition this    
> > > > >    
> > >   
> >   
> 


  reply	other threads:[~2021-01-11 13:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-08 14:36 [PATCH v3] iio: common: st_sensors: fix possible infinite loop in st_sensors_irq_thread Lorenzo Bianconi
2020-12-09 14:41 ` Andy Shevchenko
2020-12-09 14:42   ` Andy Shevchenko
2020-12-13 15:04 ` Jonathan Cameron
2020-12-13 19:23   ` Lorenzo Bianconi
2020-12-22 10:53     ` Lorenzo Bianconi
2020-12-30 12:08       ` Jonathan Cameron
2021-01-11  8:21         ` Lorenzo Bianconi
2021-01-11 13:10           ` Jonathan Cameron [this message]
2021-01-11 13:26             ` Lorenzo Bianconi

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=20210111131052.000031dc@Huawei.com \
    --to=jonathan.cameron@huawei.com \
    --cc=denis.ciocca@st.com \
    --cc=jic23@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=lorenzo.bianconi@redhat.com \
    --cc=lorenzo@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