public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Anton Vorontsov <avorontsov@ru•mvista.com>
To: Timur Tabi <timur@freescale•com>
Cc: linuxppc-dev@ozlabs•org
Subject: Re: [PATCH] CS4270 node is misplaced in the MPC8610 device tree
Date: Mon, 19 May 2008 22:42:38 +0400	[thread overview]
Message-ID: <20080519184238.GA17046@polina.dev.rtsoft.ru> (raw)
In-Reply-To: <4831C4F0.6060000@freescale.com>

On Mon, May 19, 2008 at 01:20:32PM -0500, Timur Tabi wrote:
> Timur Tabi wrote:
> > The CS4270 is using the second I2C bus, not the first, on the Freescale
> > MPC8610 HPCD, so its node in the device tree belongs under 'i2c@3100'
> > and not 'i2c@3000'.
> > 
> > Signed-off-by: Timur Tabi <timur@freescale•com>
> 
> Please disregard this patch.  It turns out that that both I2C controllers are
> connected to the same bus, so it technically doesn't matter which node a device
> is a child of.  However, tests show that sometimes one parent works, and
> sometimes the other parent works.

Hm... this should be controlled by the PIXIS' BRDCFG0's I2CSPAN and
SERSEL bits:

0: I2C1 and I2C2 buses are separated. System (boot sequencer EEPROM)
   is on I2C1, all others are on I2C2. MPC8610 SPI functions cannot be used.
1: I2C1 and I2C2 are bridged. MPC8610 SPI functions may be used. All I2C
   devices may be accessed via I2C1 controller and/or I2C2 (I2C2 depends on
   SERSEL setting).

-- 
Anton Vorontsov
email: cbouatmailru@gmail•com
irc://irc.freenode.net/bd2

  reply	other threads:[~2008-05-19 18:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-14 22:29 [PATCH] CS4270 node is misplaced in the MPC8610 device tree Timur Tabi
2008-05-19 18:20 ` Timur Tabi
2008-05-19 18:42   ` Anton Vorontsov [this message]
2008-05-19 19:20     ` Timur Tabi
2008-05-19 20:17       ` Timur Tabi

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=20080519184238.GA17046@polina.dev.rtsoft.ru \
    --to=avorontsov@ru$(echo .)mvista.com \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    --cc=timur@freescale$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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