From: Timur Tabi <timur@freescale.com>
To: avorontsov@ru.mvista.com
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] CS4270 node is misplaced in the MPC8610 device tree
Date: Mon, 19 May 2008 14:20:50 -0500 [thread overview]
Message-ID: <4831D312.2050304@freescale.com> (raw)
In-Reply-To: <20080519184238.GA17046@polina.dev.rtsoft.ru>
Anton Vorontsov wrote:
> Hm... this should be controlled by the PIXIS' BRDCFG0's I2CSPAN and
> SERSEL bits:
Since these pins should not have changed from one kernel version to another, it
doesn't explain how my device "jumped" from I2C2 to I2C1. I'm debugging this now.
> 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).
I believe this is wrong. The chip documentation says that the pin controlled by
I2CSPAN selects which of the two inputs to use. It does not bridge.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2008-05-19 19:20 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
2008-05-19 19:20 ` Timur Tabi [this message]
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=4831D312.2050304@freescale.com \
--to=timur@freescale.com \
--cc=avorontsov@ru.mvista.com \
--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).