From: Bhuvanchandra DV <bhuvanchandra.dv@toradex.com>
To: Mark Brown <broonie@kernel.org>
Cc: <gregkh@linuxfoundation.org>, <stefan@agner.ch>,
<linux-kernel@vger.kernel.org>, <linux-spi@vger.kernel.org>,
Stefan Agner <stefan.agner@toradex.com>,
Bhuvanchandra <bhuvanchandra.dv@toradex.com>
Subject: Re: [RFC 1/2] spi: spidev: Use 'new_id' sysfs file for enabling spidev
Date: Wed, 20 Apr 2016 18:41:11 +0530 [thread overview]
Message-ID: <57177FEF.8080906@toradex.com> (raw)
In-Reply-To: <20160420121704.GI3217@sirena.org.uk>
On 04/20/2016 05:47 PM, Mark Brown wrote:
> 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.
The device which i was pointing earlier is the SPI master device(spiB.C)
not the external h/w device interfaced to it. Yes, DT will describe the
h/w interfaced on SPI master device(spiB.C). In case of spidev we are
not supposed to describe in DT as it is not a real h/w. The intention of
this patchset is to completely avoid spidev in DT and load it via sysfs
new_id file for selected SPI master device(spiB.C).
>
--
Best regards,
Bhuvan
next prev parent reply other threads:[~2016-04-20 13:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-18 11:18 [RFC 0/2] sysfs new_id file support for spidev Bhuvanchandra DV
2016-04-18 11:18 ` [RFC 1/2] spi: spidev: Use 'new_id' sysfs file for enabling spidev Bhuvanchandra DV
2016-04-18 13:01 ` Mark Brown
2016-04-20 12:13 ` Bhuvanchandra DV
2016-04-20 12:17 ` Mark Brown
2016-04-20 13:11 ` Bhuvanchandra DV [this message]
2016-04-20 13:52 ` Mark Brown
2016-04-18 11:18 ` [RFC 2/2] spi core: Add new sysfs 'num_chipselect' file Bhuvanchandra DV
2016-04-18 12:14 ` Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=57177FEF.8080906@toradex.com \
--to=bhuvanchandra.dv@toradex.com \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=stefan.agner@toradex.com \
--cc=stefan@agner.ch \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome