[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160617104725.GC26099@sirena.org.uk>
Date: Fri, 17 Jun 2016 11:47:25 +0100
From: Mark Brown <broonie@...nel.org>
To: Andi Shyti <andi.shyti@...sung.com>
Cc: Kukjin Kim <kgene@...nel.org>,
Krzysztof Kozlowski <k.kozlowski@...sung.com>,
linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, Andi Shyti <andi@...zian.org>
Subject: Re: [PATCH 1/5] spi: do not fail if the CS line is not connected
On Fri, Jun 17, 2016 at 04:57:21PM +0900, Andi Shyti wrote:
> Some SPI connected devices do not have any CS line connected as
> some devices are alway enabled. Indeed, until now, a common
> workaround was to assign to num_chipselect a -1 value or 255
> (num_chipselect is unsigned).
>
> In this case do not fail and defer to the SPI device drivers the
> responsibility to check whether the num-cs is '0'.
A SPI controller always has one chip seelct, it may not be controllable
but it's at least logically present.
Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)
Powered by blists - more mailing lists