[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160626124843.GP28202@sirena.org.uk>
Date: Sun, 26 Jun 2016 13:48:43 +0100
From: Mark Brown <broonie@...nel.org>
To: Andi Shyti <andi@...zian.org>
Cc: Andi Shyti <andi.shyti@...sung.com>, 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
Subject: Re: [PATCH 1/5] spi: do not fail if the CS line is not connected
On Sun, Jun 19, 2016 at 03:09:02PM +0900, Andi Shyti wrote:
> > > This is true, but there are cases where the CS is not connected
> > > and this case needs to be treated separately to allow the device
> > > to work.
> > In what way? It is just as easy for a device with no physical chip
> > select to have a logical chip select of 0 that it does nothing with as
> > it is for that device to handle any other number.
> That is indeed my case: the s3c64xx doesn't send anything, unless
> I manually enable CS (from the next patches I need to write '0'
> in the CS register). But I need smoething to tell to the
> device that the CS line is not connected, for example a flag in
> the DTS.
I'm sorry but I just don't understand what you're saying here. You are
saying that there is no chip select but you need to enable the chip
select?
Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)
Powered by blists - more mailing lists