linux-kernel - Re: [RFC 1/2] spi: spidev: Use 'new_id' sysfs file for enabling spidev

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20160420121704.GI3217@sirena.org.uk>
Date:	Wed, 20 Apr 2016 13:17:04 +0100
From:	Mark Brown <broonie@...nel.org>
To:	Bhuvanchandra DV <bhuvanchandra.dv@...adex.com>
Cc:	gregkh@...uxfoundation.org, stefan@...er.ch,
	linux-kernel@...r.kernel.org, linux-spi@...r.kernel.org,
	Stefan Agner <stefan.agner@...adex.com>
Subject: Re: [RFC 1/2] spi: spidev: Use 'new_id' sysfs file for enabling
 spidev

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.

Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)