[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YiaouHFtlIG8nQxu@robh.at.kernel.org>
Date: Mon, 7 Mar 2022 18:52:08 -0600
From: Rob Herring <robh@...nel.org>
To: Christophe Leroy <christophe.leroy@...roup.eu>
Cc: devicetree@...r.kernel.org, Mark Brown <broonie@...nel.org>,
Pratyush Yadav <p.yadav@...com>, linux-spi@...r.kernel.org,
Rob Herring <robh+dt@...nel.org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 1/2] spi: Add optional number of additional clock
cycles to be generated
On Mon, 28 Feb 2022 16:15:45 +0100, Christophe Leroy wrote:
> Some components require a few clock cycles with chipselect off before
> or/and after the data transfer done with CS on.
>
> Typically IDT 801034 QUAD PCM CODEC datasheet states "Note *: CCLK
> should have one cycle before CS goes low, and two cycles after
> CS goes high".
>
> The cycles "before" are implicitely provided by all previous activity
> on the SPI bus. But the cycles "after" must be provided in order to
> achieve the SPI transfer.
>
> In order to use that kind of component, implement a new option for
> SPI slaves in order to implement trailing clock of a given number of
> bits with ChipSelect off at the end of the transfer.
>
> Signed-off-by: Christophe Leroy <christophe.leroy@...roup.eu>
> ---
> .../devicetree/bindings/spi/spi-peripheral-props.yaml | 5 +++++
> drivers/spi/spi.c | 7 +++++--
> include/linux/spi/spi.h | 1 +
> 3 files changed, 11 insertions(+), 2 deletions(-)
>
Acked-by: Rob Herring <robh@...nel.org>
Powered by blists - more mailing lists