[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190401074940.GL2059@sirena.org.uk>
Date: Mon, 1 Apr 2019 14:49:40 +0700
From: Mark Brown <broonie@...nel.org>
To: Sowjanya Komatineni <skomatineni@...dia.com>
Cc: thierry.reding@...il.com, jonathanh@...dia.com, talho@...dia.com,
robh+dt@...nel.org, mark.rutland@....com, kyarlagadda@...dia.com,
ldewangan@...dia.com, linux-tegra@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-spi@...r.kernel.org,
devicetree@...r.kernel.org
Subject: Re: [PATCH V1 24/26] spi: tegra114: de-assert CS before SPI mode is
reset to its default
On Tue, Mar 26, 2019 at 10:56:45PM -0700, Sowjanya Komatineni wrote:
> With SW CS, during transfer completion CS is de-asserted by writing the
> default command1 register value to SPI_COMMAND1 register. With this both
> mode and CS state are set at the same time and if current transfer mode
> is different to default SPI mode and if mode change happens prior to CS
> de-assert, clock polarity can change while CS is active before transfer
> finishes.
This is a bug fix so I'd expect it to be much earlier in the series
before any of the new features.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists