Re: Spi slave devices with two chip selects, how best to handle?

[Jonathan Cameron <jic23-KWPb1pKIrIJaa/9Udqfwiw@public.gmane.org>]

On 11/26/10 04:19, David Brownell wrote:
> 
> 
> --- On Thu, 11/25/10, Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org> wrote:
> 
>>> as to be able to pair them up. Anyone have a better
>> idea or an example of
>>> what someone else has done in similar circumstances?
>>
>> Have a single driver private data structure that contains
>> and
>> registers 2 spi_device instances.  Have both
>> spi_device instances
>> point back at the same driver private data structure.
> 
> And consider having a chardev or blockdev to
> access (indirectly) both the read and write
> sides of the chip. using that driver-private
> structure.  ((and, tricky, making the linkage
> between the three devices visible through the
> driver model, if you can).
Thanks all.  This is looking complex enough that I'll probably
want to actually have the part or leave it to someone who does...

One for your list Michael (I can put suitable element in your
tracker if that is helpful?)

Jonathan

------------------------------------------------------------------------------
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev