From: Randy Dunlap <randy.dunlap@oracle.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: fabrizio.garetto@gmail.com, linux-kernel@vger.kernel.org,
linuxppc-dev@ozlabs.org, dbrownell@users.sourceforge.net,
spi-devel-general@lists.sourceforge.net
Subject: Re: [PATCH 3/4] spi: Add OF binding support for SPI busses
Date: Fri, 16 May 2008 13:47:20 -0700 [thread overview]
Message-ID: <20080516134720.22d0569b.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20080516193613.28030.13950.stgit@trillian.secretlab.ca>
On Fri, 16 May 2008 13:36:13 -0600 Grant Likely wrote:
> diff --git a/Documentation/powerpc/booting-without-of.txt b/Documentation/powerpc/booting-without-of.txt
> index 1d2a772..452c242 100644
> --- a/Documentation/powerpc/booting-without-of.txt
> +++ b/Documentation/powerpc/booting-without-of.txt
> @@ -2870,6 +2871,66 @@ platforms are moved over to use the flattened-device-tree model.
> reg = <0xe8000000 32>;
> };
>
> + s) SPI (Serial Peripheral Interface) busses
> +
> + SPI busses can be described with a node for the SPI master device
> + and a set of child nodes for each SPI slave on the bus. For this
> + discussion, it is assumed that the system's SPI controller is in
> + SPI master mode. This binding does not describe SPI controllers
> + in slave mode.
> +
> + The SPI master node requires the following properties:
> + - #address-cells - number of cells required to define a chip select
> + address on the SPI bus.
> + - #size-cells - should be zero.
> + - compatible - name of SPI bus controller following generic names
> + recommended practice.
> + No other properties are required in the spi bus node. It is assumed
~~~
> + that a driver for an SPI bus device will understand that it is an SPI bus.
> + However, the binding does not attempt to define the specific method for
> + assigning chip select numbers. Since SPI chip select configuration is
> + flexible and non-standardized, it is left out of this binding with the
> + assumption that board specific platform code will be used to manage
> + chip selects. Individual drivers can define additional properties to
> + support describing the chip select layout.
> +
> + SPI slave nodes must be children of the spi master node and can
~~~
> + contain the following properties.
> + - reg - (required) chip select address of device.
> + - compatible - (required) name of SPI device following generic names
> + recommended practice
> + - max-speed - (optional) Maximum SPI clocking speed of device in Hz
> + - spi,cpol - (optional) Device requires inverse clock polarity
> + - spi,cpha - (optional) Device requires shifted clock phase
> + - linux,modalias - (optional, Linux specific) Force binding of SPI device
> + to a particular spi_device driver. Useful for changing
> + driver binding between spidev and a kernel spi driver.
~~~
Hi,
You mostly capitalize "SPI" in sentences (i.e., when it's not part of
a function name or OF data), so could the 3 underlined instances of it
also be all caps?
Thanks,
---
~Randy
next prev parent reply other threads:[~2008-05-16 21:50 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-16 19:35 [RFC PATCH 0/4] Describe SPI devices in the OF device tree and add mpc5200-spi driver Grant Likely
2008-05-16 19:36 ` [PATCH 1/4] spi: Change modalias from a pointer to a character array Grant Likely
2008-05-16 19:36 ` [PATCH 2/4] spi: split up spi_new_device() to allow two stage registration Grant Likely
2008-05-22 0:17 ` David Brownell
2008-05-24 6:43 ` Grant Likely
2008-05-24 6:54 ` Grant Likely
2008-06-30 4:08 ` David Brownell
2008-06-17 7:28 ` Grant Likely
2008-06-30 4:10 ` David Brownell
2008-05-16 19:36 ` [PATCH 3/4] spi: Add OF binding support for SPI busses Grant Likely
2008-05-16 20:47 ` Randy Dunlap [this message]
2008-05-16 20:51 ` Grant Likely
2008-05-16 22:03 ` Anton Vorontsov
2008-05-16 22:14 ` Grant Likely
2008-05-16 22:49 ` Anton Vorontsov
2008-05-17 5:02 ` Grant Likely
2008-05-22 1:16 ` David Brownell
2008-05-24 6:24 ` Grant Likely
2008-05-19 13:17 ` Guennadi Liakhovetski
2008-05-19 15:57 ` Grant Likely
2008-05-19 16:30 ` Guennadi Liakhovetski
2008-05-20 5:13 ` Grant Likely
2008-05-20 15:26 ` Guennadi Liakhovetski
2008-05-20 15:48 ` Grant Likely
2008-05-21 19:11 ` Segher Boessenkool
2008-05-21 19:33 ` Grant Likely
2008-05-23 2:26 ` [spi-devel-general] " David Brownell
2008-05-24 6:25 ` Grant Likely
2008-05-24 7:13 ` David Brownell
2008-05-19 17:09 ` Gary Jennejohn
2008-05-19 17:19 ` Anton Vorontsov
2008-05-20 12:26 ` Gary Jennejohn
2008-05-21 15:19 ` Anton Vorontsov
2008-05-23 2:05 ` David Brownell
2008-05-24 6:26 ` Grant Likely
2008-05-24 16:50 ` Grant Likely
2008-05-24 17:14 ` Jochen Friedrich
2008-05-24 17:33 ` Grant Likely
2008-05-24 17:45 ` David Brownell
2008-05-25 4:56 ` Grant Likely
2008-05-24 17:43 ` David Brownell
2008-05-16 19:36 ` [PATCH 4/4] [CSB] Add new mpc5200-spi (non-psc) device driver Grant Likely
2008-05-16 19:42 ` Grant Likely
2008-05-16 20:27 ` [RFC PATCH 0/4] Describe SPI devices in the OF device tree and add mpc5200-spi driver Jon Smirl
2008-05-16 20:48 ` Grant Likely
2008-05-16 21:25 ` Jon Smirl
2008-05-16 21:32 ` Grant Likely
2008-05-16 21:42 ` Jon Smirl
2008-05-16 21:58 ` 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=20080516134720.22d0569b.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=dbrownell@users.sourceforge.net \
--cc=fabrizio.garetto@gmail.com \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).