linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jagadeesh Bhaskar Pakaravoor <jagadeeshbp-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Nishanth Menon <menon.nishanth-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Kevin Hilman
	<khilman-1D3HCaltpLuhEniVeURVKkEOCMrvLtNR@public.gmane.org>,
	Syed Rafiuddin <rafiuddin.syed-l0cyMroinI0@public.gmane.org>,
	linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org,
	linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH][RFC] OMAP4: I2C Support for OMAP_4430SDP
Date: Thu, 4 Jun 2009 16:41:36 -0500	[thread overview]
Message-ID: <561678670906041441y4c592e61h71fd3cf6869bcf46@mail.gmail.com> (raw)
In-Reply-To: <782515bb0905291052h1d70be5em7cfdeeda903c39fc-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

> why is this 2600? omap3 could do 3.3Mhz.
>
There is a silicon issue reported on TWL5030 which says that it can
not operate at the stipulated highest frequency of 3.3MHz.

The information I got is this:
"I2C data hold time in HS mode is higher than specification when
reading I2C registers. This leads to a data setup issue which
introduces a frequency limitation in HS mode (can not reach 3.4MHz as
specified in I2C standard). The limitation is for the Control I2C, and
for SmartReflex I2C when using other products than OMAP34xx with SR.
HS mode is working OK for SR I2C when using OMAP34xx."

-- 
With regards,

Jagadeesh Bhaskar P
--------------------
Bugs are by far the largest and most successful class of entity, with
nearly a million known species. In this respect they outnumber all the
other known creatures about four to one.
—Professor Snopes' Encyclopedia of Animal Life
-------

  parent reply	other threads:[~2009-06-04 21:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-29 14:38 [PATCH][RFC] OMAP4: I2C Support for OMAP_4430SDP Syed Rafiuddin
     [not found] ` <55272.192.168.10.89.1243607905.squirrel-pJFUjGLopx31T2qfsofKZtBPR1lH4CV8@public.gmane.org>
2009-05-29 15:24   ` Kevin Hilman
     [not found]     ` <878wkghqzi.fsf-1D3HCaltpLuhEniVeURVKkEOCMrvLtNR@public.gmane.org>
2009-05-29 17:52       ` Nishanth Menon
     [not found]         ` <782515bb0905291052h1d70be5em7cfdeeda903c39fc-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-06-04 21:41           ` Jagadeesh Bhaskar Pakaravoor [this message]
     [not found]             ` <561678670906041441y4c592e61h71fd3cf6869bcf46-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-06-05  2:28               ` Nishanth Menon

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=561678670906041441y4c592e61h71fd3cf6869bcf46@mail.gmail.com \
    --to=jagadeeshbp-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org \
    --cc=khilman-1D3HCaltpLuhEniVeURVKkEOCMrvLtNR@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=menon.nishanth-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=rafiuddin.syed-l0cyMroinI0@public.gmane.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).