From: David Brownell <david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
To: spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Cc: linuxppc-dev-mnsaURCQ41sdnm+yROfE0A@public.gmane.org,
Stephen Street
<stephen-nl6u4wocdmy51APUEpUfAkEOCMrvLtNR@public.gmane.org>
Subject: Re: [PATCH 2/3] [SPI] Add new mode: SPI_LOOP
Date: Thu, 26 Jul 2007 20:07:07 -0700 [thread overview]
Message-ID: <200707262007.07537.david-b@pacbell.net> (raw)
In-Reply-To: <20070726135051.GB5550-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
On Thursday 26 July 2007, Anton Vorontsov wrote:
> Loopback mode is supported by various controllers, this mode
> is useful for testing, especially in conjunction with spidev
> driver.
ISTR that Stephen Street provided a loopback mode for debug
in his pxa2xx_spi code. And I know you're fight that this
mode shows up in a lot of hardware.
Comments, anyone? This seems like a fair way to expose this
mechanism. And I tend to agree that it'd mostly be useful in
conjunction with "spidev".
Anton -- assuming this goes in, it'd be nice if you could
contribute a simple test program using this, which we could
keep in Documentation/spi somewhere. (Maybe with other testing
notes, if anyone comes up with such.)
- Dave
> ...
>
> --- a/include/linux/spi/spi.h
> +++ b/include/linux/spi/spi.h
> @@ -77,6 +77,7 @@ struct spi_device {
> #define SPI_CS_HIGH 0x04 /* chipselect active high? */
> #define SPI_LSB_FIRST 0x08 /* per-word bits-on-wire */
> #define SPI_3WIRE 0x10 /* SI/SO signals shared */
> +#define SPI_LOOP 0x20 /* loopback mode */
> u8 bits_per_word;
> int irq;
> void *controller_state;
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
WARNING: multiple messages have this Message-ID (diff)
From: David Brownell <david-b@pacbell.net>
To: spi-devel-general@lists.sourceforge.net
Cc: linuxppc-dev@ozlabs.org, Stephen Street <stephen@streetfiresound.com>
Subject: Re: [spi-devel-general] [PATCH 2/3] [SPI] Add new mode: SPI_LOOP
Date: Thu, 26 Jul 2007 20:07:07 -0700 [thread overview]
Message-ID: <200707262007.07537.david-b@pacbell.net> (raw)
In-Reply-To: <20070726135051.GB5550@localhost.localdomain>
On Thursday 26 July 2007, Anton Vorontsov wrote:
> Loopback mode is supported by various controllers, this mode
> is useful for testing, especially in conjunction with spidev
> driver.
ISTR that Stephen Street provided a loopback mode for debug
in his pxa2xx_spi code. And I know you're fight that this
mode shows up in a lot of hardware.
Comments, anyone? This seems like a fair way to expose this
mechanism. And I tend to agree that it'd mostly be useful in
conjunction with "spidev".
Anton -- assuming this goes in, it'd be nice if you could
contribute a simple test program using this, which we could
keep in Documentation/spi somewhere. (Maybe with other testing
notes, if anyone comes up with such.)
- Dave
> ...
>
> --- a/include/linux/spi/spi.h
> +++ b/include/linux/spi/spi.h
> @@ -77,6 +77,7 @@ struct spi_device {
> #define SPI_CS_HIGH 0x04 /* chipselect active high? */
> #define SPI_LSB_FIRST 0x08 /* per-word bits-on-wire */
> #define SPI_3WIRE 0x10 /* SI/SO signals shared */
> +#define SPI_LOOP 0x20 /* loopback mode */
> u8 bits_per_word;
> int irq;
> void *controller_state;
next prev parent reply other threads:[~2007-07-27 3:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-26 13:47 [PATCH 0/3] [SPI] loopback mode support, [POWERPC] loopback mode for spi_mpc83xx Anton Vorontsov
2007-07-26 13:47 ` Anton Vorontsov
[not found] ` <20070726134754.GA3539-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2007-07-26 13:50 ` [PATCH 1/3] [SPI] Sync spidev.{h, c} with spi.h Anton Vorontsov
2007-07-26 13:50 ` [PATCH 1/3] [SPI] Sync spidev.{h,c} " Anton Vorontsov
[not found] ` <20070726135041.GA5550-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2007-07-27 3:02 ` [PATCH 1/3] [SPI] Sync spidev.{h, c} " David Brownell
2007-07-27 3:02 ` [spi-devel-general] " David Brownell
2007-07-26 13:50 ` [PATCH 2/3] [SPI] Add new mode: SPI_LOOP Anton Vorontsov
2007-07-26 13:50 ` Anton Vorontsov
[not found] ` <20070726135051.GB5550-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2007-07-27 3:07 ` David Brownell [this message]
2007-07-27 3:07 ` [spi-devel-general] " David Brownell
[not found] ` <200707262007.07537.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
2007-07-27 3:34 ` Ned Forrester
2007-07-27 3:34 ` [spi-devel-general] " Ned Forrester
[not found] ` <46A967D5.30606-/d+BM93fTQY@public.gmane.org>
2007-08-01 18:25 ` David Brownell
2007-08-01 18:25 ` [spi-devel-general] " David Brownell
2007-07-27 13:27 ` Anton Vorontsov
2007-07-27 13:27 ` [spi-devel-general] " Anton Vorontsov
2007-07-26 13:51 ` [PATCH 3/3] [POWERPC][SPI] spi_mpc83xx: add support for loopback mode Anton Vorontsov
2007-07-26 13:51 ` Anton Vorontsov
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=200707262007.07537.david-b@pacbell.net \
--to=david-b-ybekhbn/0ldr7s880joybq@public.gmane.org \
--cc=linuxppc-dev-mnsaURCQ41sdnm+yROfE0A@public.gmane.org \
--cc=spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=stephen-nl6u4wocdmy51APUEpUfAkEOCMrvLtNR@public.gmane.org \
/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.