From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933438AbcFQKrk (ORCPT ); Fri, 17 Jun 2016 06:47:40 -0400 Received: from mezzanine.sirena.org.uk ([106.187.55.193]:45324 "EHLO mezzanine.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752988AbcFQKri (ORCPT ); Fri, 17 Jun 2016 06:47:38 -0400 Date: Fri, 17 Jun 2016 11:47:25 +0100 From: Mark Brown To: Andi Shyti Cc: Kukjin Kim , Krzysztof Kozlowski , linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Andi Shyti Message-ID: <20160617104725.GC26099@sirena.org.uk> References: <1466150245-2648-1-git-send-email-andi.shyti@samsung.com> <1466150245-2648-2-git-send-email-andi.shyti@samsung.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="NKoe5XOeduwbEQHU" Content-Disposition: inline In-Reply-To: <1466150245-2648-2-git-send-email-andi.shyti@samsung.com> X-Cookie: news: gotcha User-Agent: Mutt/1.6.0 (2016-04-01) X-SA-Exim-Connect-IP: 2a01:348:6:8808:fab::3 X-SA-Exim-Mail-From: broonie@sirena.org.uk Subject: Re: [PATCH 1/5] spi: do not fail if the CS line is not connected X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: Yes (on mezzanine.sirena.org.uk) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --NKoe5XOeduwbEQHU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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). >=20 > 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. --NKoe5XOeduwbEQHU Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJXY9UIAAoJECTWi3JdVIfQ3BgH/2YUommqm4lK7fD/NVZqCS5T rTdaBmZouhd44wxQzcS1SSfJLiQzFJjQDwDfaZThlUWTsz55x08QBrAHcwopXRiO kkB45/z/1G3Y4EVJSl3WAD3a3CkaIfipneqUi4qjO7SOGA1W/A62JbpK5zBFUOvI WDLXBfKMwWKYa8fDHT0CUuM13wxuptLjL2K1d38GWOWbtQEOGTkktg8VnFTzxyQj kZdl0rxW8pUhc5HB4irAS/F+h76LrRzf8dRX8mIrXJKGciBtD4Uvm6rhLZ4S9Dva JvahBV2D6dAilzbjuvP2M9D9VWkcvVJJgtBnljy/gFxftLMU4GhOoiWjVirNr2k= =Ckc+ -----END PGP SIGNATURE----- --NKoe5XOeduwbEQHU--