public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Iain Hunter <drhunter95@gmail.com>,
	lothar.felten@gmail.com, iain@hunterembedded.co.uk,
	Lars-Peter Clausen <lars@metafoo.de>,
	Alexandru Ardelean <alexandru.ardelean@analog.com>,
	Gwendal Grignou <gwendal@chromium.org>,
	Matt Ranostay <matt.ranostay@konsulko.com>,
	Arnd Bergmann <arnd@arndb.de>,
	Zeng Tao <prime.zeng@hisilicon.com>,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] workaround regression in ina2xx introduced by cb47755725da("time: Prevent undefined behaviour in timespec64_to_ns()")
Date: Thu, 30 Sep 2021 17:20:18 +0100	[thread overview]
Message-ID: <20210930172018.5b4e6660@jic23-huawei> (raw)
In-Reply-To: <20210930171844.0c67b0ff@jic23-huawei>

On Thu, 30 Sep 2021 17:18:44 +0100
Jonathan Cameron <jic23@kernel.org> wrote:

> On Sun, 26 Sep 2021 23:18:42 +0200
> Thomas Gleixner <tglx@linutronix.de> wrote:
> 
> > On Sun, Sep 26 2021 at 18:16, Iain Hunter wrote:  
> > > --- a/drivers/iio/adc/ina2xx-adc.c
> > > +++ b/drivers/iio/adc/ina2xx-adc.c
> > > @@ -817,10 +817,10 @@ static int ina2xx_capture_thread(void *data)
> > >  		 */
> > >  		do {
> > >  			timespec64_add_ns(&next, 1000 * sampling_us);
> > > -			delta = timespec64_sub(next, now);
> > > -			delay_us = div_s64(timespec64_to_ns(&delta), 1000);
> > > -		} while (delay_us <= 0);
> > > +		} while (timespec64_compare(&next, &now) < 0);
> > >  
> > > +		delta = timespec64_sub(next, now);
> > > +		delay_us = div_s64(timespec64_to_ns(&delta), 1000);    
> > 
> > This whole timespec dance does not make any sense and can be completely
> > avoided by using just scalar nanoseconds. Untested patch below.
> > 
> > Thanks,
> > 
> >         tglx  
> 
> Thanks Thomas.
> 
> Iain could you test this approach?

Ah. Just seen v4, so I guess you did.

Thanks,

J
> 
> Thanks,
> 
> Jonathan
> 
> > ---
> > --- a/drivers/iio/adc/ina2xx-adc.c
> > +++ b/drivers/iio/adc/ina2xx-adc.c
> > @@ -775,7 +775,7 @@ static int ina2xx_capture_thread(void *d
> >  	struct ina2xx_chip_info *chip = iio_priv(indio_dev);
> >  	int sampling_us = SAMPLING_PERIOD(chip);
> >  	int ret;
> > -	struct timespec64 next, now, delta;
> > +	ktime_t next, now, delta;
> >  	s64 delay_us;
> >  
> >  	/*
> > @@ -785,7 +785,7 @@ static int ina2xx_capture_thread(void *d
> >  	if (!chip->allow_async_readout)
> >  		sampling_us -= 200;
> >  
> > -	ktime_get_ts64(&next);
> > +	next = ktime_get();
> >  
> >  	do {
> >  		while (!chip->allow_async_readout) {
> > @@ -798,7 +798,7 @@ static int ina2xx_capture_thread(void *d
> >  			 * reset the reference timestamp.
> >  			 */
> >  			if (ret == 0)
> > -				ktime_get_ts64(&next);
> > +				next = ktime_get();
> >  			else
> >  				break;
> >  		}
> > @@ -807,7 +807,7 @@ static int ina2xx_capture_thread(void *d
> >  		if (ret < 0)
> >  			return ret;
> >  
> > -		ktime_get_ts64(&now);
> > +		now = ktime_get();
> >  
> >  		/*
> >  		 * Advance the timestamp for the next poll by one sampling
> > @@ -816,11 +816,10 @@ static int ina2xx_capture_thread(void *d
> >  		 * multiple times, i.e. samples are dropped.
> >  		 */
> >  		do {
> > -			timespec64_add_ns(&next, 1000 * sampling_us);
> > -			delta = timespec64_sub(next, now);
> > -			delay_us = div_s64(timespec64_to_ns(&delta), 1000);
> > -		} while (delay_us <= 0);
> > +			next = ktime_add_us(next, sampling_us);
> > +		} while (next <= now);
> >  
> > +		delay_us = ktime_to_us(ktime_sub(next, now));
> >  		usleep_range(delay_us, (delay_us * 3) >> 1);
> >  
> >  	} while (!kthread_should_stop());
> > 
> >   
> 


      reply	other threads:[~2021-09-30 16:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-26 17:16 [PATCH v3] workaround regression in ina2xx introduced by cb47755725da("time: Prevent undefined behaviour in timespec64_to_ns()") Iain Hunter
2021-09-26 21:18 ` Thomas Gleixner
2021-09-30 16:18   ` Jonathan Cameron
2021-09-30 16:20     ` 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=20210930172018.5b4e6660@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=alexandru.ardelean@analog.com \
    --cc=arnd@arndb.de \
    --cc=drhunter95@gmail.com \
    --cc=gwendal@chromium.org \
    --cc=iain@hunterembedded.co.uk \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lothar.felten@gmail.com \
    --cc=matt.ranostay@konsulko.com \
    --cc=prime.zeng@hisilicon.com \
    --cc=tglx@linutronix.de \
    /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