From: addy.ke@rock-chips.com (addy ke)
To: linux-arm-kernel@lists.infradead.org
Subject: About RK3288 i2c scl duty cycle
Date: Thu, 18 Sep 2014 09:26:27 +0800 [thread overview]
Message-ID: <541A34C3.6000400@rock-chips.com> (raw)
In-Reply-To: <CAD=FV=VEUVxxZ8ZP89qhSOmvX_LgMvnczNx17qdMTGCapZj3uw@mail.gmail.com>
Add public list
On 2014/9/17 23:17, Doug Anderson wrote:
> Addy,
>
> On Tue, Sep 16, 2014 at 6:30 PM, addy.ke at rock-chips.com
> <addy.ke@rock-chips.com> wrote:
>> hi, all
>
> Any reason why you didn't add some public lists? It seems like this
> is a perfect discussion for linux-i2c.
>
>
>> According to i2c-bus specification(version2.1, page 32, Table5, FAST-MODE):
>> The minimum LOW period of the scl clock is <1.3us>, and the minimum HIGH
>> period of the scl clock is <0.6us>.
>> T(min_low) : T(min_high) ~= 2 : 1
>>
>> If <DIVH = DIVL> in fast mode(scl rate = 400Khz)
>> 1?Under ideal conditions, T(scl_low) = T(scl_high) = <1.25us>
>> 2?Our measurement, T(scl_low) = <1.3us>, T(scl_high) = <1.25us>
>>
>> The low period of the scl clock is critical.
>>
>> Do we need set <DIVL:DIVH = 1 : 2> to increase T(scl_low)? // T(scl_low )
>> : T(scl_High) = 2 : 1
>
> I can't say I've ever looked at that pat of the i2c spec before, but
> what you say seems reasonable to me. ...well for 400kHz, at least.
> At 100kHz you shouldn't use the same 2:1 ratio.
Yes, in normal-mode(100K) we can be only used 1:1 ratio.
But in FAST-MODE maybe we must use 2:1 ratio.
----
In Table 5(Characteristics of the SDA and SCL bus lines for F/S-mode I2C-bus devices)
1)FAST-MODE(400K):
The minimum LOW period of the scl clock 1.3us
the minimum HIGH period of the scl clock 0.6us
T(min_low) : T(min_high) ~= 2 : 1
But I can't see any ratio about In FAST-mode(400k) and Normal-mode(100k).
2)Normal-MODE(100K):
The minimum LOW period of the scl clock 4.7us
the minimum HIGH period of the scl clock 4.0us
T(min_low) : T(min_high) ~= 1 : 1
3) HS-mode(3.4M)
ratio of 1 to 2 is required, decribed as follows:
Hs-mode master devices generate a serial clock signal with a HIGH to LOW ratio of 1 to 2
>
> I'm sure other drivers have solved this problem too, so maybe you can
> copy some code. In i2c-designware-core.c you can see them doing all
> the calculations you need, I think.
>
>
> -Doug
>
>
>
next parent reply other threads:[~2014-09-18 1:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2014091709302172205233@rock-chips.com>
[not found] ` <CAD=FV=VEUVxxZ8ZP89qhSOmvX_LgMvnczNx17qdMTGCapZj3uw@mail.gmail.com>
2014-09-18 1:26 ` addy ke [this message]
2014-09-18 4:17 ` About RK3288 i2c scl duty cycle Doug Anderson
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=541A34C3.6000400@rock-chips.com \
--to=addy.ke@rock-chips.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).