linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: SPI devices and OF
Date: Thu, 5 Apr 2007 10:33:37 +0200	[thread overview]
Message-ID: <20070405083337.GB9910@localhost.localdomain> (raw)
In-Reply-To: <4850DC60-A560-4A38-8416-ADA776B69509@kernel.crashing.org>

On Wed, Apr 04, 2007 at 11:34:11AM -0500, Kumar Gala wrote:
> 
> On Apr 4, 2007, at 6:51 AM, Vitaly Wool wrote:
> 
> 
> I don't think this is a good idea for SPI devices.  The effort vs  
> reward isn't worth it.  The simple fact that the 'chip select'  
> mechanism ends up being board specific is too much of a pain to  
> figure out how to deal with in the device tree.  I think its ok if we  
> put information about the controller in the tree, but trying to do  
> the devices as well at this point doesn't seem like its much of a win.

It would be much easier to provide some board specific functions which
registers the spi devices instead of doing it in the device tree.
But there is one problem with that: If there is more than one spi
controller in the tree, how do you differentiate them?


Sascha

  parent reply	other threads:[~2007-04-05  8:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-04 11:09 SPI devices and OF Sascha Hauer
2007-04-04 11:51 ` Vitaly Wool
2007-04-04 16:34   ` Kumar Gala
2007-04-04 17:03     ` Arnd Bergmann
2007-04-04 17:12       ` Kumar Gala
2007-04-05  7:32         ` Benjamin Herrenschmidt
2007-04-05 15:00           ` Milton Miller
2007-04-05  8:33     ` Sascha Hauer [this message]
2007-04-04 15:57 ` Milton Miller
2007-04-05  8:50   ` Sascha Hauer
2007-04-05 14:44     ` Milton Miller
2007-04-05 19:11       ` Sascha Hauer
2007-04-05 19:52         ` Arnd Bergmann

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=20070405083337.GB9910@localhost.localdomain \
    --to=s.hauer@pengutronix.de \
    --cc=galak@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.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 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).