Devicetree
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@intel.com>
Cc: Joshua Crofts <joshua.crofts1@gmail.com>,
	Jakub Szczudlo <jakubszczudlo40@gmail.com>,
	linux-iio@vger.kernel.org, andy@kernel.org,
	antoniu.miclaus@analog.com, conor+dt@kernel.org,
	devicetree@vger.kernel.org, dlechner@baylibre.com,
	duje@dujemihanovic.xyz, jishnu.prakash@oss.qualcomm.com,
	jorge.marques@analog.com, krzk+dt@kernel.org, linusw@kernel.org,
	linux-kernel@vger.kernel.org, marcelo.schmitt@analog.com,
	mazziesaccount@gmail.com, mike.looijmans@topic.nl,
	nuno.sa@analog.com, robh@kernel.org,
	sakari.ailus@linux.intel.com, wens@kernel.org
Subject: Re: [PATCH v4 1/3] iio: adc: Fix incorrect reading when datarate changed in single mode
Date: Mon, 29 Jun 2026 19:28:53 +0100	[thread overview]
Message-ID: <20260629192853.0b12a3ba@jic23-huawei> (raw)
In-Reply-To: <ajpUa1adlePVuqE1@ashevche-desk.local>

On Tue, 23 Jun 2026 12:39:55 +0300
Andy Shevchenko <andriy.shevchenko@intel.com> wrote:

> On Tue, Jun 23, 2026 at 11:29:53AM +0200, Joshua Crofts wrote:
> > On Tue, 23 Jun 2026 12:16:39 +0300
> > Andy Shevchenko <andriy.shevchenko@intel.com> wrote:  
> 
> ...
> 
> > > > +	return read_poll_timeout(ads1100_new_data_not_ready, data_ready,
> > > > +				 !data_ready, wait_time,  
> > 
> > I'd actually be all for using `data_ready != 0`, to make the condition more
> > readable.  
> 
> I am okay with either. It might be slightly clearer if the comparison is done
> for some dynamic counting or so, when 0 is not special.
> 
> ...
> 
> > > > +		PM_RUNTIME_ACQUIRE_AUTOSUSPEND(&data->client->dev, pm);    
> > >   
> > > > +    
> > > 
> > > This blank line is not needed as they are coupled, but I don't know if we have
> > > an agreed style in IIO for this.  
> > 
> > I'd be surprised if there was an agreed style, as there aren't any IIO drivers
> > that use this specific macro (not in mainline at least). Additionally, might I
> > suggest using `PM_RUNTIME_ACQUIRE_IF_ENABLED_AUTOSUSPEND` as it is more generic?  
> 
> We have other PM_ACQUIRE_*() macros in the drivers in IIO, so we have some style,
> but I haven't checked what is that.
> 
FWIW I'd expect no blank line to be the standard formatting for this.

J


  reply	other threads:[~2026-06-29 18:28 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-22 22:15 [PATCH v4 0/3] iio: adc: Add support for TI ADS1110 to ti-ads1100 driver Jakub Szczudlo
2026-06-22 22:15 ` [PATCH v4 1/3] iio: adc: Fix incorrect reading when datarate changed in single mode Jakub Szczudlo
2026-06-22 22:33   ` sashiko-bot
2026-06-23  9:16   ` Andy Shevchenko
2026-06-23  9:29     ` Joshua Crofts
2026-06-23  9:39       ` Andy Shevchenko
2026-06-29 18:28         ` Jonathan Cameron [this message]
2026-06-29 22:51     ` Jonathan Cameron
2026-06-30 11:36       ` Andy Shevchenko
2026-06-30 12:08         ` Matti Vaittinen
2026-06-30 12:28           ` Andy Shevchenko
2026-06-30 17:01             ` Jakub Szczudło
2026-06-27 22:31   ` David Lechner
2026-06-29 18:33     ` Jonathan Cameron
2026-06-29 18:55       ` David Lechner
2026-06-22 22:15 ` [PATCH v4 2/3] dt-bindings: iio: adc: ti,ads1100: add support for ADS1110 Jakub Szczudlo
2026-06-22 22:15 ` [PATCH v4 3/3] iio: adc: Add ti-ads1110 support to ti-ads1100 driver Jakub Szczudlo
2026-06-22 22:31   ` sashiko-bot
2026-06-23  9:23   ` Andy Shevchenko
2026-06-23 18:49     ` Jakub Szczudło
2026-06-27 22:42   ` David Lechner

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=20260629192853.0b12a3ba@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=andriy.shevchenko@intel.com \
    --cc=andy@kernel.org \
    --cc=antoniu.miclaus@analog.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=duje@dujemihanovic.xyz \
    --cc=jakubszczudlo40@gmail.com \
    --cc=jishnu.prakash@oss.qualcomm.com \
    --cc=jorge.marques@analog.com \
    --cc=joshua.crofts1@gmail.com \
    --cc=krzk+dt@kernel.org \
    --cc=linusw@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.schmitt@analog.com \
    --cc=mazziesaccount@gmail.com \
    --cc=mike.looijmans@topic.nl \
    --cc=nuno.sa@analog.com \
    --cc=robh@kernel.org \
    --cc=sakari.ailus@linux.intel.com \
    --cc=wens@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