Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: "Nuno Sá" <noname.nuno@gmail.com>
Cc: "David Lechner" <dlechner@baylibre.com>,
	"Michael Hennerich" <Michael.Hennerich@analog.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 v2] iio: adc: ad7124: change setup reg allocation strategy
Date: Sat, 27 Sep 2025 19:25:51 +0100	[thread overview]
Message-ID: <20250927192551.2b81d838@jic23-huawei> (raw)
In-Reply-To: <3bbd51983f5bf67b6fd061f28b8b260370beac70.camel@gmail.com>

On Fri, 26 Sep 2025 13:27:00 +0100
Nuno Sá <noname.nuno@gmail.com> wrote:

> On Tue, 2025-09-23 at 16:48 -0500, David Lechner wrote:
> > Change the allocation strategy of the 8 SETUP registers from a least-
> > recently-used (LRU) to a first-come-first-served basis.
> > 
> > The AD7124 chips can have up to 16 channels enabled at a time in the
> > sequencer for buffered reads, but only have 8 SETUP configurations
> > (namely the OFFSET, GAIN, CONFIG and FILTER registers) that must be
> > shared among the 16 channels.  This means some of the channels must use
> > the exact same configuration parameters so that they can share a single
> > SETUP group of registers.  The previous LRU strategy did not keep track
> > of how many different configurations were requested at the same time,
> > so if there were more than 8 different configurations requested, some
> > channels would end up using the incorrect configuration because the slot
> > assigned to them would also be assigned to a different configuration
> > that wrote over it later.
> > 
> > Adding such tracking to solve this would make an already complex
> > algorithm even more complex.  Instead we can replace it with a simpler
> > first-come-first-serve strategy.  This makes it easy to track how many
> > different configurations are being requested at the same time.  This
> > comes at the expense of slightly longer setup times for buffered reads
> > since all setup registers must be written each time when a buffered read
> > is enabled.  But this is generally not considered a hot path where
> > performance is critical, so should be acceptable.
> > 
> > This new strategy also makes hardware debugging easier since SETUPs are
> > now assigned in a deterministic manner and in a logical order.
> > 
> > Signed-off-by: David Lechner <dlechner@baylibre.com>
> > ---  
> 
> Hi David,
> 
> LGTM
> 
Agreed.
> Reviewed-by: Nuno Sá <nuno.sa@analog.com>
Applied to the testing branch of iio.git.

  reply	other threads:[~2025-09-27 18:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-23 21:48 [PATCH v2] iio: adc: ad7124: change setup reg allocation strategy David Lechner
2025-09-26 12:27 ` Nuno Sá
2025-09-27 18:25   ` Jonathan Cameron [this message]
2025-10-27 12:15 ` Andy Shevchenko

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=20250927192551.2b81d838@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=Michael.Hennerich@analog.com \
    --cc=andy@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=noname.nuno@gmail.com \
    --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