[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250928105316.782d076e@jic23-huawei>
Date: Sun, 28 Sep 2025 10:53:16 +0100
From: Jonathan Cameron <jic23@...nel.org>
To: Marcelo Schmitt <marcelo.schmitt@...log.com>
Cc: <linux-iio@...r.kernel.org>, <devicetree@...r.kernel.org>,
<linux-doc@...r.kernel.org>, <linux-spi@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <michael.hennerich@...log.com>,
<nuno.sa@...log.com>, <eblanc@...libre.com>, <dlechner@...libre.com>,
<andy@...nel.org>, <robh@...nel.org>, <krzk+dt@...nel.org>,
<conor+dt@...nel.org>, <corbet@....net>, <marcelo.schmitt1@...il.com>
Subject: Re: [PATCH v3 4/8] iio: adc: ad4030: Reduce register access
transfer speed
On Fri, 26 Sep 2025 17:39:42 -0300
Marcelo Schmitt <marcelo.schmitt@...log.com> wrote:
> Configuration register accesses are not considered a critical path in terms
> of time to complete. Even though register access transfers can run at high
> speeds, nanosecond completion times are not required as device
> configuration is usually done step by step from user space. Also, high
> frequency transfers hinder debug with external tools since they require
> faster clocked equipment. Reduce register access transfer speed.
So making debug with external tools easier isn't usually a justification we'd
make to slow things down by default.
Is there another reason for this being useful as opposed to not a problem
to do? If it had been done this way in the first place I wouldn't have
minded, but to make a change I'd like either some others to jump in and
say, yes please do this, or a reason beyond you are using tooling that can't
cope with 80 MHz and don't want to hack the driver when you need
to slow it down (my tools can't cope with that rate either!)
J
Powered by blists - more mailing lists