From: javier.martinez@collabora•co.uk (Javier Martinez Canillas)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 1/3] ARM: dts: Add SPI flash node for Peach boards
Date: Wed, 19 Nov 2014 11:07:14 +0100 [thread overview]
Message-ID: <546C6BD2.4020802@collabora.co.uk> (raw)
In-Reply-To: <CAD=FV=Xkei_wxa3jWb8bPvuynbSyq4o=ezjVD0+e04aOPCAM+Q@mail.gmail.com>
Hello Doug,
Thanks for your feedback.
On 11/18/2014 06:50 PM, Doug Anderson wrote:
> This is common practice in the Chrome OS tree, but we've gotten
> pushback from upstream questioning about whether "spidev" is really a
> physical device. See:
>
> http://www.spinics.net/lists/linux-samsung-soc/msg29563.html
>
I see, I thought that it was a common practice in the mainline kernel
too since I saw that many board DTS currently have a spidev node:
$ git grep 'compatible = "spidev"' arch/arm/boot/dts/ | wc -l
19
>
> I don't really have an answer for something better to do here but I
> figured I'd at least bring up the point.
>
I wonder how the spidev user-space interface is supposed to be used
when booting with Device Trees.
Best regards,
Javier
next prev parent reply other threads:[~2014-11-19 10:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-17 17:43 [PATCH 0/3] ARM: dts: Add spidev nodes for Exynos Chromebooks Javier Martinez Canillas
2014-11-17 17:43 ` [PATCH 1/3] ARM: dts: Add SPI flash node for Peach boards Javier Martinez Canillas
2014-11-18 17:50 ` Doug Anderson
2014-11-19 10:07 ` Javier Martinez Canillas [this message]
2014-11-19 17:19 ` Doug Anderson
2014-11-19 17:29 ` Javier Martinez Canillas
2014-11-19 17:47 ` Mark Brown
2014-11-19 17:59 ` Javier Martinez Canillas
2014-11-17 17:43 ` [PATCH 2/3] ARM: dts: Add spidev registration to exynos5250-snow Javier Martinez Canillas
2014-11-17 17:43 ` [PATCH 3/3] ARM: exynos_defconfig: Enable user mode SPI device support Javier Martinez Canillas
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=546C6BD2.4020802@collabora.co.uk \
--to=javier.martinez@collabora$(echo .)co.uk \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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