From: Grant Likely <grant.likely@secretlab.ca>
To: spi-devel-general@lists.sourceforge.net, rob@landley.net,
rob.herring@calxeda.com
Cc: devicetree-discuss@lists.ozlabs.org,
Linux OMAP Mailing List <linux-omap@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Tony Lindgren <tony@atomide.com>, Felipe Balbi <balbi@ti.com>
Subject: Re: [PATCH 2/2] spi: devicetree: add support for loopback mode
Date: Sat, 15 Dec 2012 00:32:24 +0000 [thread overview]
Message-ID: <20121215003224.CBFD93E0BEC@localhost> (raw)
In-Reply-To: <1355301960-21523-2-git-send-email-balbi@ti.com>
On Wed, 12 Dec 2012 10:46:00 +0200, Felipe Balbi <balbi@ti.com> wrote:
> there are a few spi master drivers which make
> use of that flag but there is no way to pass it
> through devicetree.
>
> This patch just creates a way to pass SPI_LOOP
> via devicetree.
I don't understand how this would be useful since loopback mode is
really just a test feature. Is there any reason to do loopback for
something other than test?
I think it would be better to add a sysfs or debugfs property to
manipulate the SPI_LOOP flag from userspace. What do you think?
g.
>
> Signed-off-by: Felipe Balbi <balbi@ti.com>
> ---
> Documentation/devicetree/bindings/spi/spi-bus.txt | 2 ++
> drivers/spi/spi.c | 2 ++
> 2 files changed, 4 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/spi/spi-bus.txt b/Documentation/devicetree/bindings/spi/spi-bus.txt
> index 296015e..1949586 100644
> --- a/Documentation/devicetree/bindings/spi/spi-bus.txt
> +++ b/Documentation/devicetree/bindings/spi/spi-bus.txt
> @@ -55,6 +55,8 @@ contain the following properties.
> chip select active high
> - spi-3wire - (optional) Empty property indicating device requires
> 3-wire mode.
> +- spi-loopback - (optional) Empty property indicating device requires
> + loopback mode.
>
> If a gpio chipselect is used for the SPI slave the gpio number will be passed
> via the cs_gpio
> diff --git a/drivers/spi/spi.c b/drivers/spi/spi.c
> index 3f1b9ee..6bcdc03 100644
> --- a/drivers/spi/spi.c
> +++ b/drivers/spi/spi.c
> @@ -868,6 +868,8 @@ static void of_register_spi_devices(struct spi_master *master)
> spi->mode |= SPI_CS_HIGH;
> if (of_find_property(nc, "spi-3wire", NULL))
> spi->mode |= SPI_3WIRE;
> + if (of_find_property(nc, "spi-loopback", NULL))
> + spi->mode |= SPI_LOOP;
>
> /* Device speed */
> prop = of_get_property(nc, "spi-max-frequency", &len);
> --
> 1.8.1.rc1.5.g7e0651a
>
--
Grant Likely, B.Sc, P.Eng.
Secret Lab Technologies, Ltd.
WARNING: multiple messages have this Message-ID (diff)
From: Grant Likely <grant.likely@secretlab.ca>
To: Felipe Balbi <balbi@ti.com>,
spi-devel-general@lists.sourceforge.net, rob@landley.net,
rob.herring@calxeda.com
Cc: devicetree-discuss@lists.ozlabs.org,
Linux OMAP Mailing List <linux-omap@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Tony Lindgren <tony@atomide.com>, Felipe Balbi <balbi@ti.com>
Subject: Re: [PATCH 2/2] spi: devicetree: add support for loopback mode
Date: Sat, 15 Dec 2012 00:32:24 +0000 [thread overview]
Message-ID: <20121215003224.CBFD93E0BEC@localhost> (raw)
In-Reply-To: <1355301960-21523-2-git-send-email-balbi@ti.com>
On Wed, 12 Dec 2012 10:46:00 +0200, Felipe Balbi <balbi@ti.com> wrote:
> there are a few spi master drivers which make
> use of that flag but there is no way to pass it
> through devicetree.
>
> This patch just creates a way to pass SPI_LOOP
> via devicetree.
I don't understand how this would be useful since loopback mode is
really just a test feature. Is there any reason to do loopback for
something other than test?
I think it would be better to add a sysfs or debugfs property to
manipulate the SPI_LOOP flag from userspace. What do you think?
g.
>
> Signed-off-by: Felipe Balbi <balbi@ti.com>
> ---
> Documentation/devicetree/bindings/spi/spi-bus.txt | 2 ++
> drivers/spi/spi.c | 2 ++
> 2 files changed, 4 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/spi/spi-bus.txt b/Documentation/devicetree/bindings/spi/spi-bus.txt
> index 296015e..1949586 100644
> --- a/Documentation/devicetree/bindings/spi/spi-bus.txt
> +++ b/Documentation/devicetree/bindings/spi/spi-bus.txt
> @@ -55,6 +55,8 @@ contain the following properties.
> chip select active high
> - spi-3wire - (optional) Empty property indicating device requires
> 3-wire mode.
> +- spi-loopback - (optional) Empty property indicating device requires
> + loopback mode.
>
> If a gpio chipselect is used for the SPI slave the gpio number will be passed
> via the cs_gpio
> diff --git a/drivers/spi/spi.c b/drivers/spi/spi.c
> index 3f1b9ee..6bcdc03 100644
> --- a/drivers/spi/spi.c
> +++ b/drivers/spi/spi.c
> @@ -868,6 +868,8 @@ static void of_register_spi_devices(struct spi_master *master)
> spi->mode |= SPI_CS_HIGH;
> if (of_find_property(nc, "spi-3wire", NULL))
> spi->mode |= SPI_3WIRE;
> + if (of_find_property(nc, "spi-loopback", NULL))
> + spi->mode |= SPI_LOOP;
>
> /* Device speed */
> prop = of_get_property(nc, "spi-max-frequency", &len);
> --
> 1.8.1.rc1.5.g7e0651a
>
--
Grant Likely, B.Sc, P.Eng.
Secret Lab Technologies, Ltd.
next prev parent reply other threads:[~2012-12-15 0:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-12 8:45 [PATCH 1/2] spi: omap2: disable DMA requests before complete() Felipe Balbi
2012-12-12 8:45 ` Felipe Balbi
2012-12-12 8:45 ` Felipe Balbi
[not found] ` <1355301960-21523-1-git-send-email-balbi-l0cyMroinI0@public.gmane.org>
2012-12-12 8:46 ` [PATCH 2/2] spi: devicetree: add support for loopback mode Felipe Balbi
2012-12-12 8:46 ` Felipe Balbi
2012-12-12 8:46 ` Felipe Balbi
2012-12-15 0:32 ` Grant Likely [this message]
2012-12-15 0:32 ` Grant Likely
2012-12-15 14:55 ` Felipe Balbi
2012-12-15 14:55 ` Felipe Balbi
2012-12-16 21:14 ` Grant Likely
2012-12-16 21:14 ` Grant Likely
2012-12-15 0:35 ` [PATCH 1/2] spi: omap2: disable DMA requests before complete() Grant Likely
2012-12-15 0:35 ` Grant Likely
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=20121215003224.CBFD93E0BEC@localhost \
--to=grant.likely@secretlab.ca \
--cc=balbi@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=spi-devel-general@lists.sourceforge.net \
--cc=tony@atomide.com \
/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.