Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751786AbcDRMOr (ORCPT ); Mon, 18 Apr 2016 08:14:47 -0400 Received: from mezzanine.sirena.org.uk ([106.187.55.193]:51204 "EHLO mezzanine.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751075AbcDRMOp (ORCPT ); Mon, 18 Apr 2016 08:14:45 -0400 Date: Mon, 18 Apr 2016 13:14:30 +0100 From: Mark Brown To: Bhuvanchandra DV Cc: gregkh@linuxfoundation.org, stefan@agner.ch, linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org, Stefan Agner Message-ID: <20160418121430.GA3217@sirena.org.uk> References: <1460978308-8062-1-git-send-email-bhuvanchandra.dv@toradex.com> <1460978308-8062-3-git-send-email-bhuvanchandra.dv@toradex.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="1ozVqH6bFr/3sC51" Content-Disposition: inline In-Reply-To: <1460978308-8062-3-git-send-email-bhuvanchandra.dv@toradex.com> X-Cookie: Tomorrow, you can be anywhere. User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: 2a01:348:6:8808:fab::3 X-SA-Exim-Mail-From: broonie@sirena.org.uk Subject: Re: [RFC 2/2] spi core: Add new sysfs 'num_chipselect' file 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 Content-Length: 1192 Lines: 32 --1ozVqH6bFr/3sC51 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Mon, Apr 18, 2016 at 04:48:28PM +0530, Bhuvanchandra DV wrote: > Add new sysfs 'num_chipselect' file to expose the maximum number > of chipselects a SPI master can support. > This allows to create a script in user space which automatically > creates a new spidev instance for every chipselect on a bus. This does not seem like a good idea, even if a chip select is supported in the IP that doesn't mean it's brought out safely on a board and pinmuxing may mean that the set of chip selects that can be used is sparse. --1ozVqH6bFr/3sC51 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJXFM9SAAoJECTWi3JdVIfQ1Q0H/iMSAujby1d2bQ+QPcTil+Li WZjl3QRdwwlDuftd4gww12j/KcYeXH+A8kY1aAsPC/uEokMxYYS1oZglBdh5bYoI 1+dfewldFWWx2+LOEvsZ5/F+5lGgV9HN1iVO7ij9NmrB6D6hf1IwbL4kS3waEQLz nRqB40b4I6Bqo4eV1R/A7D0prdrZviixMXLy3w6ataEJTSFuHGwUZ5a9R1ZLpN1H NtDydRn5sxr05IUh8FU/ufwHQuLYvgTgBfWACGkBJpAQ5TxLkYO6yJ1H2+Us44+1 5remg78tJxFKv6baVzFODuT1LXRXUzXagqTlhypv+y25MTrbZ5Hl1RzOSDsjJQY= =0XLl -----END PGP SIGNATURE----- --1ozVqH6bFr/3sC51--