Linux IIO development
 help / color / mirror / Atom feed
From: Francesco Dolcini <francesco@dolcini.it>
To: "João Paulo Gonçalves" <jpaulo.silvagoncalves@gmail.com>
Cc: nattan <nattanferreira58@gmail.com>,
	francesco@dolcini.it, jic23@kernel.org,
	lucasantonio.santos@usp.br, linux-iio@vger.kernel.org
Subject: Re: [PATCH] iio: adc: ti-ads1119: Prevent concurrent access during
Date: Sun, 20 Apr 2025 23:17:06 +0200	[thread overview]
Message-ID: <20250420211706.GB5621@francesco-nb> (raw)
In-Reply-To: <c2golk6627ybfpw3t7lnerritq2yysi5zhdlvahnvhxoevmojn@j3d2stvivkyk>

On Sun, Apr 20, 2025 at 01:07:28PM -0300, João Paulo Gonçalves wrote:
> > Use iio_device_claim_direct() to protect register access via debugfs
> > from conflicting with buffered capture modes. This prevents data
> > corruption and ensures correct device operation when users access
> > registers while streaming data.
> > 
> 
> but debugfs is meant to be used during development/integration,
> where this probably is not an issue.

Is even worth doing any such a change? I assume Jonathan will have an
opinion on what's the expectation for an IIO driver.

Nattan, can you explain why you need such a change? What is the use
case?

Francesco


  reply	other threads:[~2025-04-20 21:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-19 23:23 [PATCH] iio: adc: ti-ads1119: Prevent concurrent access during nattan
2025-04-20 16:07 ` João Paulo Gonçalves
2025-04-20 21:17   ` Francesco Dolcini [this message]
2025-04-21 13:23     ` Jonathan Cameron
2025-04-21 14:42       ` Marcelo Schmitt
2025-04-25  8:10         ` Jonathan Cameron
2025-04-22 18:04     ` Nattan Ferreira
2025-04-25  8:14       ` Jonathan Cameron

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=20250420211706.GB5621@francesco-nb \
    --to=francesco@dolcini.it \
    --cc=jic23@kernel.org \
    --cc=jpaulo.silvagoncalves@gmail.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=lucasantonio.santos@usp.br \
    --cc=nattanferreira58@gmail.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