Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932590AbbD0KqY (ORCPT ); Mon, 27 Apr 2015 06:46:24 -0400 Received: from mezzanine.sirena.org.uk ([106.187.55.193]:39152 "EHLO mezzanine.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932377AbbD0KqU (ORCPT ); Mon, 27 Apr 2015 06:46:20 -0400 Date: Mon, 27 Apr 2015 11:46:02 +0100 From: Mark Brown To: Michal Suchanek Cc: Maxime Ripard , Martin Sperl , Hans de Goede , linux-sunxi , Jonathan Corbet , linux-spi , linux-doc , Linux Kernel Mailing List Message-ID: <20150427104602.GO22845@sirena.org.uk> References: <20150426110144.GK22845@sirena.org.uk> <553CCABA.3090504@redhat.com> <12F80B18-7418-430E-94F7-5A20C133BA9A@martin.sperl.org> <20150426125113.GF5627@lukather> <20150426143359.GI5627@lukather> <20150426155404.GL5627@lukather> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="9ioi+DVKW/PB6LhC" Content-Disposition: inline In-Reply-To: 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: 1916 Lines: 47 --9ioi+DVKW/PB6LhC Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Sun, Apr 26, 2015 at 08:53:16PM +0200, Michal Suchanek wrote: > Do you have to describe a modem or terminal emulator in DT to connect > it to your serial port? You just describe the port. So here you have a > SPI port and it should be described in the DT as faithfully as the > serial port. Serial ports have runtime mechanisms defined for connecting devices to them (opening the device or attaching a line discipline). > Or do you suggest that I patch the compatible into spidev, write a > driver for it, and then back out the compatible from spidev and check > in the compatible again with the driver? Until someone provides a way of binding spidev to otherwise unbound devices that's exactly what is being suggested; if your main purpose in this is to write a kernel driver for the device then that would be a local modification to add the compatible (or you could just ignore the warning) until you get something in kernel space, no need to upstream. --9ioi+DVKW/PB6LhC Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJVPhNqAAoJECTWi3JdVIfQyrsH/RfUEHVGEPvD0zvuewuMJDln c/LxghVP9XmFWo5k1D+0cyUSHHtOK072cUVmj9DfuLWwcYAPgLiJWJolE+IxjJ1o tblmD3AgiodnJyt6MmeAgduz6vmcTv3OaF7d3kkEa2bQ0IzTeP3X9SmJ7yVWQB0H IJw58n+C+NAoW3XA/1z2Yq55NZp8n1pK37bs3krLXhzo8zMIknjr9EmCuoIzFsSJ R2+5DGodjmG8xUdREtAIjQfwttSNTnLMjU9yKdqgS8goIllQFVbmHiXwVpxIXoh+ sATRmCTRfPN6wgElUS6c9Rzm3Dfw0vPRy/uky/H5Pos+Zxg0kE9pdjnMxOU8soI= =sP5D -----END PGP SIGNATURE----- --9ioi+DVKW/PB6LhC-- -- 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/