From: troy.kisky@boundarydevices.com (Troy Kisky)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] i2c i.MX: Fix divider table
Date: Fri, 06 Jul 2012 10:41:54 -0700 [thread overview]
Message-ID: <4FF72362.5020704@boundarydevices.com> (raw)
In-Reply-To: <20120706062852.GZ30009@pengutronix.de>
On 7/5/2012 11:28 PM, Sascha Hauer wrote:
> On Fri, Jul 06, 2012 at 08:52:50AM +0800, Richard Zhao wrote:
>> On Thu, Jul 05, 2012 at 06:01:53PM +0200, Sascha Hauer wrote:
>>> On Thu, Jul 05, 2012 at 10:52:39PM +0800, Richard Zhao wrote:
>>>> On Thu, Jul 05, 2012 at 03:10:26PM +0200, Sascha Hauer wrote:
>>>>> Measurements on i.MX1 and i.MX53 have shown that the divider values
>>>>> in the datasheets are wrong. the values from first, third and fourth
>>>>> column were all measured to be 8 higher than in the datasheet. It
>>>>> should be safe to assume that the SoCs between i.MX1 and i.MX53 behave
>>>>> the same as the i2c unit is unchanged since the i.MX1.
>>>> We may need to check with IC guys? Or you've done?
>>> I don't have contact to the IC guys. Could you do this? I'd be
>>> interested in the results.
>> Sure, but it may be slow, as you know, many people are in summer break.
> Thanks. It can take longer, the resulting frequencies are all too low,
> so we are on the safe side.
>
> Sascha
>
You mean safe before the patch is applied, not after. Right?
Troy
next prev parent reply other threads:[~2012-07-06 17:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-05 13:10 [PATCH] i2c i.MX: Fix divider table Sascha Hauer
2012-07-05 14:23 ` Baruch Siach
2012-07-05 14:52 ` Richard Zhao
2012-07-05 16:01 ` Sascha Hauer
2012-07-06 0:52 ` Richard Zhao
2012-07-06 6:28 ` Sascha Hauer
2012-07-06 17:41 ` Troy Kisky [this message]
2012-07-11 6:01 ` Richard Zhao
2012-07-11 18:38 ` Sascha Hauer
2012-07-11 19:11 ` Troy Kisky
2012-07-11 19:44 ` Sascha Hauer
2012-07-12 0:45 ` Richard Zhao
2012-07-05 18:06 ` Shubhrajyoti Datta
2012-07-05 18:47 ` Sascha Hauer
2012-07-08 9:14 ` Shubhrajyoti Datta
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=4FF72362.5020704@boundarydevices.com \
--to=troy.kisky@boundarydevices.com \
--cc=linux-arm-kernel@lists.infradead.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).