Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932407AbbD0L0M (ORCPT ); Mon, 27 Apr 2015 07:26:12 -0400 Received: from mezzanine.sirena.org.uk ([106.187.55.193]:39226 "EHLO mezzanine.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752431AbbD0L0J (ORCPT ); Mon, 27 Apr 2015 07:26:09 -0400 Date: Mon, 27 Apr 2015 12:25:39 +0100 From: Mark Brown To: Hans de Goede Cc: Michal Suchanek , Maxime Ripard , Martin Sperl , linux-sunxi , Jonathan Corbet , linux-spi , linux-doc , Linux Kernel Mailing List Message-ID: <20150427112539.GR22845@sirena.org.uk> References: <20150426103257.GJ22845@sirena.org.uk> <20150426110144.GK22845@sirena.org.uk> <553CCABA.3090504@redhat.com> <12F80B18-7418-430E-94F7-5A20C133BA9A@martin.sperl.org> <20150426125113.GF5627@lukather> <20150427093618.GL22845@sirena.org.uk> <553E099C.4070208@redhat.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="VtpJd9mrbM613+PJ" Content-Disposition: inline In-Reply-To: <553E099C.4070208@redhat.com> X-Cookie: Your present plans will be successful. User-Agent: Mutt/1.5.23 (2014-03-12) X-SA-Exim-Connect-IP: 94.175.94.161 X-SA-Exim-Mail-From: broonie@sirena.org.uk Subject: Re: [linux-sunxi] [PATCH 2/3] spidev: Add DT binding example. 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: 2358 Lines: 54 --VtpJd9mrbM613+PJ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Mon, Apr 27, 2015 at 12:04:12PM +0200, Hans de Goede wrote: > Have you seen my mail about the raspberry pi use-case? Using dt-overlays > simply is not an acceptable answer there. There are legitimate use-cases > for a "generic spi bus" concept with the bus only being accessible via > spidev. > Blocking this use-case because you do not believe it is a valid use-case > is not going to help, this will just lead to the custom distros these > boards are shipping doing some ugly hack, which is not what we want > IMHO. I don't think you've fully considered your use case here. As I said in my reply to your earlier e-mail I think what you're looking for here is something like better UI around overlays. Registering a SPI bus without knowing what's connected to it doesn't allow generic maker style usage of the board, it's just as likely to hinder a user as help them. For example, if someone wants to use the SPI pins for another function such as GPIO they'll have to handle that (and may have problems with pin conflicts causing electrical issues if they do load up the DT with spidev in it). If someone has a SPI device they want to bind an in kernel driver to they'll have to handle that, if they want to use a GPIO to provide an additional chip select they'll have to handle that too. Note that the discussion here isn't about userspace drivers, it's about how the hardware is described. --VtpJd9mrbM613+PJ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJVPhyzAAoJECTWi3JdVIfQi8sH/1A26Uo69m489HaQt59Ivm8r +JAlbBYoZqSkjI3nAUVJNjISxlzgkC/HFOz07a9sEbedwJZK+XJn/Do2OwafnaMU hzvrRxpcKvzfqp8Uf802IpYBhngribPWJsNTzwqO5LL8e/TGMU04TPLsraAGk7KI ROKGxS7VLrXUHTuW+BNo1JqIrTMyoVVQdhWTbRIAYVNNBwkU/hbtfvnilfoUtNEs Fz9TlTrqEdpQURLaNmDSvaMYCrPen/49EFh6O44lfwa9i1rPfeva8HMyustCp6gD vH/7Qk31Z2Fkf+v5tc0kn6ev8ZE5z7GT4It52nkwEFj36EBZoljcGvUrRdkQpck= =Ei2G -----END PGP SIGNATURE----- --VtpJd9mrbM613+PJ-- -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/