From: Martin Fuzzey <mfuzzey@parkeon.com>
To: Grant Likely <grant.likely@secretlab.ca>,
spi-devel-general@lists.sourceforge.net
Cc: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] SPI: spidev: Add DT compatible string for spidev driver.
Date: Fri, 12 Apr 2013 14:56:21 +0200 [thread overview]
Message-ID: <20130412125621.9645.78102.stgit@localhost> (raw)
The spidev driver is useful to allow userspace access
to SPI devices that have no kernel SPI driver.
However DT requires a compatible tree to allow the driver
to be probed.
To avoid having to modify the driver for every extra device
add a generic "linux,spidev" compatible string that may be
used in the DT to match such devices.
Signed-off-by: Martin Fuzzey <mfuzzey@parkeon.com>
---
Documentation/devicetree/bindings/spi/spi-bus.txt | 3 +++
drivers/spi/spidev.c | 1 +
2 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/Documentation/devicetree/bindings/spi/spi-bus.txt b/Documentation/devicetree/bindings/spi/spi-bus.txt
index 296015e..3176587 100644
--- a/Documentation/devicetree/bindings/spi/spi-bus.txt
+++ b/Documentation/devicetree/bindings/spi/spi-bus.txt
@@ -59,6 +59,9 @@ contain the following properties.
If a gpio chipselect is used for the SPI slave the gpio number will be passed
via the cs_gpio
+For slave devices having no kernel driver the compatible string "linux,spidev"
+may be used to enable access from userspace via the spidev driver.
+
SPI example for an MPC5200 SPI bus:
spi@f00 {
#address-cells = <1>;
diff --git a/drivers/spi/spidev.c b/drivers/spi/spidev.c
index 2e0655d..c2447a8 100644
--- a/drivers/spi/spidev.c
+++ b/drivers/spi/spidev.c
@@ -646,6 +646,7 @@ static int spidev_remove(struct spi_device *spi)
static const struct of_device_id spidev_dt_ids[] = {
{ .compatible = "rohm,dh2228fv" },
+ { .compatible = "linux,spidev" },
{},
};
WARNING: multiple messages have this Message-ID (diff)
From: mfuzzey@parkeon.com (Martin Fuzzey)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] SPI: spidev: Add DT compatible string for spidev driver.
Date: Fri, 12 Apr 2013 14:56:21 +0200 [thread overview]
Message-ID: <20130412125621.9645.78102.stgit@localhost> (raw)
The spidev driver is useful to allow userspace access
to SPI devices that have no kernel SPI driver.
However DT requires a compatible tree to allow the driver
to be probed.
To avoid having to modify the driver for every extra device
add a generic "linux,spidev" compatible string that may be
used in the DT to match such devices.
Signed-off-by: Martin Fuzzey <mfuzzey@parkeon.com>
---
Documentation/devicetree/bindings/spi/spi-bus.txt | 3 +++
drivers/spi/spidev.c | 1 +
2 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/Documentation/devicetree/bindings/spi/spi-bus.txt b/Documentation/devicetree/bindings/spi/spi-bus.txt
index 296015e..3176587 100644
--- a/Documentation/devicetree/bindings/spi/spi-bus.txt
+++ b/Documentation/devicetree/bindings/spi/spi-bus.txt
@@ -59,6 +59,9 @@ contain the following properties.
If a gpio chipselect is used for the SPI slave the gpio number will be passed
via the cs_gpio
+For slave devices having no kernel driver the compatible string "linux,spidev"
+may be used to enable access from userspace via the spidev driver.
+
SPI example for an MPC5200 SPI bus:
spi at f00 {
#address-cells = <1>;
diff --git a/drivers/spi/spidev.c b/drivers/spi/spidev.c
index 2e0655d..c2447a8 100644
--- a/drivers/spi/spidev.c
+++ b/drivers/spi/spidev.c
@@ -646,6 +646,7 @@ static int spidev_remove(struct spi_device *spi)
static const struct of_device_id spidev_dt_ids[] = {
{ .compatible = "rohm,dh2228fv" },
+ { .compatible = "linux,spidev" },
{},
};
next reply other threads:[~2013-04-12 12:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-12 12:56 Martin Fuzzey [this message]
2013-04-12 12:56 ` [PATCH] SPI: spidev: Add DT compatible string for spidev driver Martin Fuzzey
2013-04-12 13:30 ` Maxime Ripard
2013-04-12 13:30 ` Maxime Ripard
2013-04-12 14:16 ` Martin Fuzzey
2013-04-12 14:16 ` Martin Fuzzey
2013-04-12 17:28 ` Lars-Peter Clausen
2013-04-12 17:28 ` Lars-Peter Clausen
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=20130412125621.9645.78102.stgit@localhost \
--to=mfuzzey@parkeon.com \
--cc=grant.likely@secretlab.ca \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=spi-devel-general@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.