All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ned Forrester <nforrester-/d+BM93fTQY@public.gmane.org>
To: David Brownell <david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
Cc: spi-devel
	<spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: SPI Framework chip select
Date: Sat, 01 Mar 2008 20:14:06 -0500	[thread overview]
Message-ID: <47C9FF5E.5060503@whoi.edu> (raw)
In-Reply-To: <200803011237.51349.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>

David Brownell wrote:
> On Friday 29 February 2008, Ned Forrester wrote:
>> David Brownell wrote:
> 
>>> The chipselect number is always useful when the SPI bus has more
>>> than one slave; it's how the slaves are distinguished.
>> Ahh... Here is a place where pxa2xx-spi departs from the SPI framework
>> by choice.  That driver never uses spi_device.chip_select
> 
> Not directly.  Indirectly, since each chip_select is associated
> with a unique pxa2xx_spi_chip.cs_control().  The chipselect number
> (and signal) still distinguishes chips from each other.

Maybe we're just discussing semantics, but the last sentence does not
apply to this driver.  pxa2xx_spi.c never references the field
spi_device.chip_select.  The string "chip_select" appears nowhere in the
code.  You can assign spi_device.chip_select=0 for all chips, and as
long as you supply a unique
spi_device->controller_data->pxa2xx_spi_chip.cs_control for each chip,
chip select will work as intended.

So in the sense that I mean, spi_device.chip_select field is unused; it
does not need to be unique between chips.  Yes, of course there have to
be unique spi_device structures for each chip, and through a driver
private means (spi_device.controller_data) the chip select mechanism for
each chip becomes known to the driver.

It was this lack of example for any use of spi_device.chip_select in
pxa2xx_spi.c that led to my confusion about how spi_device.chip_select
was supposed to be used.

-- 
Ned Forrester                                       nforrester-/d+BM93fTQY@public.gmane.org
Oceanographic Systems Lab                                  508-289-2226
Applied Ocean Physics and Engineering Dept.
Woods Hole Oceanographic Institution          Woods Hole, MA 02543, USA
http://www.whoi.edu/sbl/liteSite.do?litesiteid=7212
http://www.whoi.edu/hpb/Site.do?id=1532
http://www.whoi.edu/page.do?pid=10079


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

  parent reply	other threads:[~2008-03-02  1:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-29 18:52 SPI Framework chip select Ned Forrester
     [not found] ` <47C85451.1030809-/d+BM93fTQY@public.gmane.org>
2008-02-29 20:04   ` David Brownell
     [not found]     ` <200802291204.33911.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
2008-02-29 20:53       ` Ned Forrester
     [not found]         ` <47C870D5.7000109-/d+BM93fTQY@public.gmane.org>
2008-02-29 21:38           ` David Brownell
     [not found]             ` <200802291338.55149.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
2008-02-29 22:30               ` Ned Forrester
     [not found]                 ` <47C88793.1050205-/d+BM93fTQY@public.gmane.org>
2008-03-01 20:37                   ` David Brownell
     [not found]                     ` <200803011237.51349.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
2008-03-02  1:14                       ` Ned Forrester [this message]
     [not found]                         ` <47C9FF5E.5060503-/d+BM93fTQY@public.gmane.org>
2008-03-02  2:58                           ` David Brownell
     [not found]                             ` <200803011858.14400.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
2008-03-02 14:08                               ` Ned Forrester

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=47C9FF5E.5060503@whoi.edu \
    --to=nforrester-/d+bm93ftqy@public.gmane.org \
    --cc=david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org \
    --cc=spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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.