From: Felix Radensky <felix@embedded-sol.com>
To: Wolfgang Grandegger <wg@grandegger.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: I2C bus clock on MPC85XX systems
Date: Tue, 22 Dec 2009 20:16:48 +0200 [thread overview]
Message-ID: <4B310D10.4090307@embedded-sol.com> (raw)
In-Reply-To: <4B30F165.2060300@grandegger.com>
Hi, Wolfgang
Wolfgang Grandegger wrote:
> Felix Radensky wrote:
>
>> Hi,
>>
>> Almost all MPC85XX based systems have the compatible=:"fsl-i2c" in
>> respective
>> i2c device tree nodes. This causes FSL i2c driver to use the following
>> "backward
>> compatible" values: FSR=0x31 DFSR=0x10. This is regardless of CCB clock
>> frequency and i2c clock prescaler.
>>
>> On my custom MPC8536 based board with 432MHz CCB clock this results in
>> 65KHz i2c clock frequency (checked with scope). U-Boot correctly configures
>> the clock to 400KHz.
>>
>> I've fixed the problem by modifying device tree to use different
>> compatible value,
>> similar to what socrates board does. Is this the right approach ?
>>
>
> Are you aware of the properties described in
> "Documentation/powerpc/dts-bindings/fsl/i2c.txt":
>
> http://lxr.linux.no/#linux+v2.6.32/Documentation/powerpc/dts-bindings/fsl/i2c.txt
>
> Wolfgang.
>
>
Sure, I'm aware of these properties. I've used
compatible = "fsl,mpc8543-i2c", "fsl-i2c";
clock-frequency = <400000>;
for my custom board.
I think, however, that device trees for FSL reference designs should use
them as well, to avoid setting i2c
clock to some strange values. I may be wrong, but I think most custom
board developers borrow from
reference device trees, so having a sane starting point would help.
Thanks.
Felix.
next prev parent reply other threads:[~2009-12-22 18:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-22 15:38 I2C bus clock on MPC85XX systems Felix Radensky
2009-12-22 16:18 ` Wolfgang Grandegger
2009-12-22 18:16 ` Felix Radensky [this message]
2009-12-22 18:40 ` Wolfgang Grandegger
2009-12-22 19:06 ` Felix Radensky
2009-12-22 19:20 ` Wolfgang Grandegger
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=4B310D10.4090307@embedded-sol.com \
--to=felix@embedded-sol.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=wg@grandegger.com \
/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).