From: "Nuno Sá" <noname.nuno@gmail.com>
To: David Lechner <dlechner@baylibre.com>,
Jonathan Cameron <jic23@kernel.org>,
linux-iio@vger.kernel.org
Cc: "Mudit Sharma" <muditsharma.info@gmail.com>,
"Julien Stephan" <jstephan@baylibre.com>,
"Mariel Tinaco" <Mariel.Tinaco@analog.com>,
"Angelo Dureghello" <adureghello@baylibre.com>,
"Gustavo Silva" <gustavograzs@gmail.com>,
"Nuno Sa" <nuno.sa@analog.com>,
"João Paulo Gonçalves" <joao.goncalves@toradex.com>,
"ChiYuan Huang" <cy_huang@richtek.com>,
"Ramona Alexandra Nechita" <ramona.nechita@analog.com>,
"Trevor Gamblin" <tgamblin@baylibre.com>,
"Guillaume Stols" <gstols@baylibre.com>,
"Cosmin Tanislav" <demonsingur@gmail.com>,
"Marcelo Schmitt" <marcelo.schmitt@analog.com>,
"Gwendal Grignou" <gwendal@chromium.org>,
"Antoni Pokusinski" <apokusinski01@gmail.com>,
"Tomasz Duszynski" <tomasz.duszynski@octakon.com>,
"Jonathan Cameron" <Jonathan.Cameron@huawei.com>
Subject: Re: [PATCH v2 11/27] iio: adc: ad4695: Stop using iio_device_claim_direct_scoped()
Date: Mon, 17 Feb 2025 10:48:03 +0000 [thread overview]
Message-ID: <a8b34cb7270ab2045894a978797023a8c7fafd63.camel@gmail.com> (raw)
In-Reply-To: <6db4821e-9cfe-4256-a357-51a00a50d083@baylibre.com>
On Sun, 2025-02-16 at 13:00 -0600, David Lechner wrote:
> On 2/16/25 12:19 PM, Jonathan Cameron wrote:
> > On Sun, 9 Feb 2025 18:06:08 +0000
> > Jonathan Cameron <jic23@kernel.org> wrote:
> >
> > > From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> > >
> > > This complex cleanup.h use case of conditional guards has proved
> > > to be more trouble that it is worth in terms of false positive compiler
> > > warnings and hard to read code.
> > >
> > > Move directly to the new claim/release_direct() that allow sparse
> > > to check for unbalanced context. In some cases code is factored
> > > out to utility functions that can do a direct return with the
> > > claim and release around the call.
> > >
> > > Reviewed-by: David Lechner <dlechner@baylibre.com>
> > > Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> > > ---
> > > v2: Typo in commit description (David).
> > > Note there are several sets current in flight that touch this driver.
> > > I'll rebase as necessary depending on what order the dependencies resolve.
> > I've done this rebase and applied on the testing branch of iio.git.
> >
> > Would appreciate a sanity check if anyone has time though!
> >
> > New code is as follows. The one corner I was not sure on was
> > that for calibbias reading the direct mode claim was held for a long
> > time. That seems to be unnecessary as we have a copy of osr anyway
> > in that function used for other purposes.
> >
>
> ...
>
> > case IIO_CHAN_INFO_CALIBBIAS:
> > - switch (chan->type) {
> > - case IIO_VOLTAGE:
> > - iio_device_claim_direct_scoped(return -EBUSY,
> > indio_dev) {
> > - ret = regmap_read(st->regmap16,
> > - AD4695_REG_OFFSET_IN(chan-
> > >scan_index),
> > - ®_val);
> > - if (ret)
> > - return ret;
> > -
> > - tmp = sign_extend32(reg_val, 15);
> > -
> > - switch (cfg->oversampling_ratio) {
> > - case 1:
> > - *val = tmp / 4;
> > - *val2 = abs(tmp) % 4 * MICRO / 4;
> > - break;
> > - case 4:
> > - *val = tmp / 2;
> > - *val2 = abs(tmp) % 2 * MICRO / 2;
> > - break;
> > - case 16:
> > - *val = tmp;
> > - *val2 = 0;
> > - break;
> > - case 64:
> > - *val = tmp * 2;
> > - *val2 = 0;
> > - break;
> > - default:
> > - return -EINVAL;
> > - }
> > -
> > - if (tmp < 0 && *val2) {
> > - *val *= -1;
> > - *val2 *= -1;
> > - }
> > -
> > - return IIO_VAL_INT_PLUS_MICRO;
> > + switch (chan->type)
> > + case IIO_VOLTAGE: {
> > + if (!iio_device_claim_direct(indio_dev))
> > + return -EBUSY;
> > + ret = regmap_read(st->regmap16,
> > + AD4695_REG_OFFSET_IN(chan-
> > >scan_index),
> > + ®_val);
> > + iio_device_release_direct(indio_dev);
> > + if (ret)
> > + return ret;
> > ////THIS IS THE BIT I WOuLD LIKE EYES on.
>
> Looks fine to me.
+1
- Nuno Sá
>
> > +
> > + tmp = sign_extend32(reg_val, 15);
> > +
> > + switch (osr) {
> > + case 1:
> > + *val = tmp / 4;
> > + *val2 = abs(tmp) % 4 * MICRO / 4;
> > + break;
> > + case 4:
> > + *val = tmp / 2;
> > + *val2 = abs(tmp) % 2 * MICRO / 2;
> > + break;
> > + case 16:
> > + *val = tmp;
> > + *val2 = 0;
> > + break;
> > + case 64:
> > + *val = tmp * 2;
> > + *val2 = 0;
> > + break;
> > + default:
> > + return -EINVAL;
> > + }
> > +
> > + if (tmp < 0 && *val2) {
> > + *val *= -1;
> > + *val2 *= -1;
> > }
> > - unreachable();
> > +
> > + return IIO_VAL_INT_PLUS_MICRO;
> > default:
> > return -EINVAL;
> > }
next prev parent reply other threads:[~2025-02-17 10:48 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-09 18:05 [PATCH v2 00/27] iio: improve handling of direct mode claim and release Jonathan Cameron
2025-02-09 18:05 ` [PATCH v2 01/27] iio: core: Rework claim and release of direct mode to work with sparse Jonathan Cameron
2025-02-17 10:38 ` Nuno Sá
2025-02-17 12:57 ` Jonathan Cameron
2025-02-22 15:51 ` Andy Shevchenko
2025-02-22 17:23 ` Jonathan Cameron
2025-02-22 20:58 ` Andy Shevchenko
2025-02-25 6:25 ` Jonathan Cameron
2025-02-25 7:09 ` Andy Shevchenko
2025-02-09 18:05 ` [PATCH v2 02/27] iio: chemical: scd30: Use guard(mutex) to allow early returns Jonathan Cameron
2025-02-17 10:56 ` Nuno Sá
2025-02-09 18:06 ` [PATCH v2 03/27] iio: chemical: scd30: Switch to sparse friendly claim/release_direct() Jonathan Cameron
2025-02-09 18:06 ` [PATCH v2 04/27] iio: temperature: tmp006: Stop using iio_device_claim_direct_scoped() Jonathan Cameron
2025-02-09 18:06 ` [PATCH v2 05/27] iio: proximity: sx9310: " Jonathan Cameron
2025-02-09 18:06 ` [PATCH v2 06/27] iio: proximity: sx9324: " Jonathan Cameron
2025-02-09 18:06 ` [PATCH v2 07/27] iio: proximity: sx9360: " Jonathan Cameron
2025-02-09 18:06 ` [PATCH v2 08/27] iio: accel: adxl367: " Jonathan Cameron
2025-02-17 10:44 ` Nuno Sá
2025-02-09 18:06 ` [PATCH v2 09/27] iio: adc: ad4000: " Jonathan Cameron
2025-02-17 10:45 ` Nuno Sá
2025-02-09 18:06 ` [PATCH v2 10/27] iio: adc: ad4130: " Jonathan Cameron
2025-02-17 10:45 ` Nuno Sá
2025-02-09 18:06 ` [PATCH v2 11/27] iio: adc: ad4695: " Jonathan Cameron
2025-02-16 18:19 ` Jonathan Cameron
2025-02-16 19:00 ` David Lechner
2025-02-17 10:48 ` Nuno Sá [this message]
2025-02-17 13:04 ` Jonathan Cameron
2025-02-17 10:48 ` Nuno Sá
2025-02-09 18:06 ` [PATCH v2 12/27] iio: adc: ad7606: " Jonathan Cameron
2025-02-17 10:49 ` Nuno Sá
2025-02-09 18:06 ` [PATCH v2 13/27] iio: adc: ad7625: " Jonathan Cameron
2025-02-17 10:49 ` Nuno Sá
2025-02-09 18:06 ` [PATCH v2 14/27] iio: adc: ad7779: " Jonathan Cameron
2025-02-17 10:50 ` Nuno Sá
2025-02-09 18:06 ` [PATCH v2 15/27] iio: adc: ad9467: " Jonathan Cameron
2025-02-17 10:50 ` Nuno Sá
2025-02-09 18:06 ` [PATCH v2 16/27] iio: adc: max1363: " Jonathan Cameron
2025-02-17 10:51 ` Nuno Sá
2025-02-09 18:06 ` [PATCH v2 17/27] iio: adc: rtq6056: " Jonathan Cameron
2025-02-09 18:06 ` [PATCH v2 18/27] iio: adc: ti-adc161s626: " Jonathan Cameron
2025-02-09 18:06 ` [PATCH v2 19/27] iio: adc: ti-ads1119: " Jonathan Cameron
2025-02-09 18:06 ` [PATCH v2 20/27] iio: addac: ad74413r: " Jonathan Cameron
2025-02-17 10:52 ` Nuno Sá
2025-02-09 18:06 ` [PATCH v2 21/27] iio: chemical: ens160: " Jonathan Cameron
2025-02-09 18:06 ` [PATCH v2 22/27] iio: dac: ad3552r-hs: " Jonathan Cameron
2025-02-17 10:53 ` Nuno Sá
2025-02-09 18:06 ` [PATCH v2 23/27] iio: dac: ad8460: " Jonathan Cameron
2025-02-17 10:52 ` Nuno Sá
2025-02-09 18:06 ` [PATCH v2 24/27] iio: dummy: " Jonathan Cameron
2025-02-17 10:55 ` Nuno Sá
2025-02-09 18:06 ` [PATCH v2 25/27] iio: imu: bmi323: " Jonathan Cameron
2025-02-09 18:06 ` [PATCH v2 26/27] iio: light: bh1745: " Jonathan Cameron
2025-02-09 18:06 ` [PATCH v2 27/27] iio: Drop iio_device_claim_direct_scoped() and related infrastructure Jonathan Cameron
2025-02-17 10:57 ` Nuno Sá
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=a8b34cb7270ab2045894a978797023a8c7fafd63.camel@gmail.com \
--to=noname.nuno@gmail.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=Mariel.Tinaco@analog.com \
--cc=adureghello@baylibre.com \
--cc=apokusinski01@gmail.com \
--cc=cy_huang@richtek.com \
--cc=demonsingur@gmail.com \
--cc=dlechner@baylibre.com \
--cc=gstols@baylibre.com \
--cc=gustavograzs@gmail.com \
--cc=gwendal@chromium.org \
--cc=jic23@kernel.org \
--cc=joao.goncalves@toradex.com \
--cc=jstephan@baylibre.com \
--cc=linux-iio@vger.kernel.org \
--cc=marcelo.schmitt@analog.com \
--cc=muditsharma.info@gmail.com \
--cc=nuno.sa@analog.com \
--cc=ramona.nechita@analog.com \
--cc=tgamblin@baylibre.com \
--cc=tomasz.duszynski@octakon.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