Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754254AbcDTMRT (ORCPT ); Wed, 20 Apr 2016 08:17:19 -0400 Received: from mezzanine.sirena.org.uk ([106.187.55.193]:56748 "EHLO mezzanine.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751791AbcDTMRR (ORCPT ); Wed, 20 Apr 2016 08:17:17 -0400 Date: Wed, 20 Apr 2016 13:17:04 +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: <20160420121704.GI3217@sirena.org.uk> References: <1460978308-8062-1-git-send-email-bhuvanchandra.dv@toradex.com> <1460978308-8062-2-git-send-email-bhuvanchandra.dv@toradex.com> <20160418130126.GC3217@sirena.org.uk> <5717726C.2090302@toradex.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="NzlXNccsnmbvA4eK" Content-Disposition: inline In-Reply-To: <5717726C.2090302@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 1/2] spi: spidev: Use 'new_id' sysfs file for enabling spidev 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: 1326 Lines: 34 --NzlXNccsnmbvA4eK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wed, Apr 20, 2016 at 05:43:32PM +0530, Bhuvanchandra DV wrote: > SPI drivers bind to the device as configured in DT, but in case of > spidev(non DT approach) the device is not available in hand to bind the > driver. So tried this approach of creating the device and then bind spidev. > I agree this is not a standard way we bind SPI devices. With out a device > available, seems it is not possible to bind spidev in non DT approach. > Please correct me if i'm wrong. The DT should describe the hardware so the DT should describe whatever device is connected to the spidev, what you're trying to do is have spidev bind to these new compatible strings. --NzlXNccsnmbvA4eK Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJXF3M/AAoJECTWi3JdVIfQ5vwH/jwdoqIDuj8ECfsJhiog2CdQ V3Sa+sqqybwD9rStSEADKDFAdV8tMydxXeHS8CbOaO87gU3o46B9260SyocDKaxX T0QnsV+J+mPmNP8Wsy5cWJpmHij1hnVYzLGBvVxYq4ZJ1atR3gFsen8cb0R8pt03 ndrblsMQua7FULIxSZozOhp/Oic3zJJclwOv9qGMfudmi2oBsLkj1mwFvrdQPYPD c6lupU66wEMoRjXLZauZRe8oz12bpvzumBpoVpjnv78dU89oIR1lbPN1mbVSBlVg +2gGTZt9//VansO12UNWdm98cBd+z+muzPHyMfwD42mmPi3iH0xDOFUHPjrkJvo= =8RLN -----END PGP SIGNATURE----- --NzlXNccsnmbvA4eK--