From: "Grant Likely" <grant.likely@secretlab.ca>
To: "David Brownell" <david-b@pacbell.net>
Cc: fabrizio.garetto@gmail.com, linux-kernel@vger.kernel.org,
linuxppc-dev@ozlabs.org, spi-devel-general@lists.sourceforge.net,
Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Subject: Re: [spi-devel-general] [PATCH 3/4] spi: Add OF binding support for SPI busses
Date: Sat, 24 May 2008 00:25:47 -0600 [thread overview]
Message-ID: <fa686aa40805232325w65d4f706i50798121a8cce263@mail.gmail.com> (raw)
In-Reply-To: <200805221926.24112.david-b@pacbell.net>
On Thu, May 22, 2008 at 8:26 PM, David Brownell <david-b@pacbell.net> wrote:
> On Wednesday 21 May 2008, Grant Likely wrote:
>> > spi-controller {
>> > #address-cells = 2;
>> > #size-cells = 0;
>> > some-device@0,f000 { reg = < 0 f000 >; } // CS 0, SPI address f000
>> > some-device@1,f000 { reg = < 1 f000 >; } // CS 1, SPI address f000
>> > some-device@1,ff00 { reg = < 1 ff00 >; } // CS 1, SPI address ff00
>> > }
>>
>> For SPI the CS # *is* the address. :-)
>>
>> Unlike I2C, SPI doesn't impose any protocol on the data. It is all
>> anonymous data out, anonymous data in, a clock and a chip select.
>
> Very true ... but then there are SPI chips which embed addressing.
>
> I have in mind the mcp23s08 (and mcp23s17) GPIO expanders, which
> support up to four chips wired in parallel on a given chipselect.
> The devices are distinguished by how two address pins are wired;
> and two bits in the command byte must match them. (I think they
> just recycled an I2C design into the SPI world.)
Very good point. Okay, so we cannot assume any correlation between
the number of CS lines and the number of child nodes to the SPI bus.
Cheers,
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next prev parent reply other threads:[~2008-05-24 6:25 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
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 [this message]
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=fa686aa40805232325w65d4f706i50798121a8cce263@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=david-b@pacbell.net \
--cc=fabrizio.garetto@gmail.com \
--cc=g.liakhovetski@gmx.de \
--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).