From: Jonathan Cameron <jic23@kernel.org>
To: Kurt Borja <kuurtb@gmail.com>
Cc: "David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: adc: ti-ads1018: Drop iio_device_claim_buffer_mode() call
Date: Sun, 21 Dec 2025 18:49:58 +0000 [thread overview]
Message-ID: <20251221184958.2d825e2e@jic23-huawei> (raw)
In-Reply-To: <20251216-ads1018-patch-v1-1-cf41d193e187@gmail.com>
On Tue, 16 Dec 2025 19:52:01 -0500
Kurt Borja <kuurtb@gmail.com> wrote:
> Drop iio_device_claim_buffer_mode() call in ads1018_trigger_handler() as
> it's not actually protecting anything.
>
> Signed-off-by: Kurt Borja <kuurtb@gmail.com>
I squashed this in. One comment inline.
> ---
> drivers/iio/adc/ti-ads1018.c | 12 +++---------
> 1 file changed, 3 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/iio/adc/ti-ads1018.c b/drivers/iio/adc/ti-ads1018.c
> index af08702b62d2..b34184f68e63 100644
> --- a/drivers/iio/adc/ti-ads1018.c
> +++ b/drivers/iio/adc/ti-ads1018.c
> @@ -557,9 +557,6 @@ static irqreturn_t ads1018_trigger_handler(int irq, void *p)
> } scan = {};
> int ret;
>
> - if (iio_device_claim_buffer_mode(indio_dev))
> - goto out_notify_done;
> -
> if (iio_trigger_using_own(indio_dev)) {
> disable_irq(ads1018->drdy_irq);
> ret = ads1018_spi_read_exclusive(ads1018, &scan.conv, true);
> @@ -568,14 +565,11 @@ static irqreturn_t ads1018_trigger_handler(int irq, void *p)
> ret = spi_read(ads1018->spi, ads1018->rx_buf, sizeof(ads1018->rx_buf));
> scan.conv = ads1018->rx_buf[0];
> }
> - if (ret)
> - goto out_release_buffer;
>
> - iio_push_to_buffers_with_ts(indio_dev, &scan, sizeof(scan), pf->timestamp);
> + if (!ret)
Generally I fairly strongly prefer error paths out of line but in this
case I'd rather just get this merged than go around again so I'll leave
this as it stands.
Thanks,
Jonathan
> + iio_push_to_buffers_with_ts(indio_dev, &scan, sizeof(scan),
> + pf->timestamp);
>
> -out_release_buffer:
> - iio_device_release_buffer_mode(indio_dev);
> -out_notify_done:
> iio_trigger_notify_done(indio_dev->trig);
>
> return IRQ_HANDLED;
>
> ---
> base-commit: a7b10f0963c651a6406d958a5f64b9c5594f84da
> change-id: 20251216-ads1018-patch-ad02382e0a04
>
next prev parent reply other threads:[~2025-12-21 18:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-17 0:52 [PATCH] iio: adc: ti-ads1018: Drop iio_device_claim_buffer_mode() call Kurt Borja
2025-12-21 18:49 ` Jonathan Cameron [this message]
2025-12-22 22:47 ` Kurt Borja
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=20251221184958.2d825e2e@jic23-huawei \
--to=jic23@kernel.org \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=kuurtb@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.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