[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20231028162313.5babf107@jic23-huawei>
Date: Sat, 28 Oct 2023 16:23:13 +0100
From: Jonathan Cameron <jic23@...nel.org>
To: Ramona Gradinariu <ramona.gradinariu@...log.com>
Cc: <nuno.sa@...log.com>, <robh+dt@...nel.org>,
<krzysztof.kozlowski+dt@...aro.org>, <conor+dt@...nel.org>,
<linux-iio@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<devicetree@...r.kernel.org>
Subject: Re: [PATCH v3 0/3] iio: imu: adis: Use spi cs inactive delay
On Fri, 27 Oct 2023 17:03:55 +0300
Ramona Gradinariu <ramona.gradinariu@...log.com> wrote:
> A delay is needed each time the chip selected becomes inactive,
> even after burst data readings are performed.
> Currently, there is no delay added after a burst reading
> and in case a new SPI transfer is performed before
> the needed delay, the adis device becomes unresponsive until
> reset.
>
> This commit is adding the needed delay directly to the spi driver,
> using the cs_inactive parameter, in case it is not set and is
> removing the additional chip select change delay present in adis
> APIs to remove the double delay.
Series applied.
I'm a bit confused though as this one is turning up in patchwork.
Meh, maybe a delay and it will show up soon.
Jonathan
>
> Ramona Gradinariu (3):
> iio: imu: adis: Use spi cs inactive delay
> dt-bindings: adis16475: Add 'spi-cs-inactive-delay-ns' property
> dt-bindings: adis16460: Add 'spi-cs-inactive-delay-ns' property
>
> .../bindings/iio/imu/adi,adis16460.yaml | 4 ++++
> .../bindings/iio/imu/adi,adis16475.yaml | 4 ++++
> drivers/iio/imu/adis.c | 18 ++++++------------
> 3 files changed, 14 insertions(+), 12 deletions(-)
>
> --
> 2.34.1
>
Powered by blists - more mailing lists