linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: David Miller <davem@davemloft.net>
Cc: scottwood@freescale.com, sparclinux@vger.kernel.org,
	paulus@samba.org, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 0/3]: Sparc OF I2C support.
Date: Fri, 22 Aug 2008 08:39:53 +1000	[thread overview]
Message-ID: <1219358393.21386.158.camel@pasglop> (raw)
In-Reply-To: <20080821.152857.84114588.davem@davemloft.net>

On Thu, 2008-08-21 at 15:28 -0700, David Miller wrote:
> From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> Date: Fri, 22 Aug 2008 08:05:02 +1000
> 
> > Apple additionally have different ways of representing multiple busses
> > on one controller though. On some machines, they just use bits 0xF00 of
> > the address as the bus number, which is a bit gross, and on some, they
> > have sub-nodes i2c-bus@NN under the controller.
> 
> Ok, Sun uses a 2-cell scheme.  We can handle both cases of reg
> encoding quite easily:
> 
> 1) If there is a single cell, tread bits 8 and above as bus number.
>    They will be zero on Sparc.

Depends if you want also to handle 10-bit addresses... though the
support for that could be enabled by an explicit property
10-bit-addresses in the controller node...  But as I said before, I
wouldn't worry too much about powermac for now, it's not using this code
and may never do.

> 2) If there are two cells, first cell is bus number.
> 
> For the hierarchical case, I'm not so sure how to handle it.
> 
> Also, last night, I posted patches to the I2C list to add bus
> addressing support to the I2C code and the PCF algo implementation.

Ben.

  reply	other threads:[~2008-08-21 22:40 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-21  7:10 [PATCH 0/3]: Sparc OF I2C support David Miller
2008-08-21 16:32 ` Scott Wood
2008-08-21 21:21   ` David Miller
2008-08-21 21:35     ` Scott Wood
2008-08-21 21:45       ` David Miller
2008-08-21 22:05         ` Benjamin Herrenschmidt
2008-08-21 22:27           ` David Miller
2008-08-21 22:38             ` Benjamin Herrenschmidt
2008-08-21 22:05       ` Benjamin Herrenschmidt
2008-08-21 22:28         ` David Miller
2008-08-21 22:39           ` Benjamin Herrenschmidt [this message]
2008-08-21 23:14       ` Grant Likely
2008-08-21 23:32         ` David Miller
2008-08-22  1:15           ` Josh Boyer
2008-08-22  3:53             ` David Miller
2008-08-22  4:18               ` Grant Likely
2008-08-22  4:22                 ` David Miller
2008-08-22  4:29                   ` Mitch Bradley
2008-08-22  4:30                     ` Grant Likely
2008-08-22  4:34                       ` Grant Likely
2008-08-22  4:37                         ` David Miller
2008-08-22  5:19                           ` Mitch Bradley
2008-08-22 16:00                             ` Yoder Stuart
2008-08-22 16:13                               ` Josh Boyer
2008-08-22 10:50               ` Josh Boyer
2008-08-22 11:06                 ` David Miller
2008-08-21 23:45         ` Jon Smirl
2008-08-22  2:33           ` Grant Likely
2008-08-22  2:39             ` Jon Smirl
2008-08-22 15:58               ` Scott Wood
2008-08-22 16:44               ` Grant Likely
2008-08-21 22:01   ` Benjamin Herrenschmidt
2008-08-21 21:53 ` Jon Smirl
2008-08-21 21:58   ` David Miller

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=1219358393.21386.158.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=davem@davemloft.net \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.org \
    --cc=scottwood@freescale.com \
    --cc=sparclinux@vger.kernel.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).