linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: "J.D. Schroeder" <Linux.HWI@garmin.com>,
	linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
	linux-fbdev@vger.kernel.org, misael.lopez@ti.com
Cc: "Lodes, Jim" <jim.lodes@garmin.com>,
	"J.D. Schroeder" <jay.schroeder@garmin.com>
Subject: Re: [PATCH] OMAPDSS: HDMI5: Change DDC timings
Date: Thu, 21 Apr 2016 14:38:43 +0000	[thread overview]
Message-ID: <5718E5F3.2080504@ti.com> (raw)
In-Reply-To: <1461196973-20370-1-git-send-email-Linux.HWI@garmin.com>


[-- Attachment #1.1: Type: text/plain, Size: 805 bytes --]

Hi,

On 21/04/16 03:02, J.D. Schroeder wrote:
> From: "Lodes, Jim" <jim.lodes@garmin.com>
> 
> The DDC scl high and low times were set to the minimum values
> from the i2c specification, but the i2c specification takes into
> account the rise time and fall time to calculate the frequency.
> To pass HDMI certification DDC can not exceed 100kHz therefore in
> a system where the rise times and fall times are negligible the high
> and low times for scl need to be 10us.

Thanks, makes sense. Did you measure the rise & fall times? Do you get
more or less exactly 100kHz with the new times?

> Signed-off-by: Lodes, Jim <jim.lodes@garmin.com>

The email format should be

Firstname Lastname <firstname.lastname@foo.bar>

Or something similar, but not "Lastname, Firstname"

 Tomi


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-04-21 14:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-21  0:02 [PATCH] OMAPDSS: HDMI5: Change DDC timings J.D. Schroeder
2016-04-21 14:38 ` Tomi Valkeinen [this message]
2016-04-21 16:04   ` J.D. Schroeder
2016-04-21 17:27 ` [PATCH v2] " J.D. Schroeder
2016-04-27  5:55   ` Tomi Valkeinen

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=5718E5F3.2080504@ti.com \
    --to=tomi.valkeinen@ti.com \
    --cc=Linux.HWI@garmin.com \
    --cc=jay.schroeder@garmin.com \
    --cc=jim.lodes@garmin.com \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=misael.lopez@ti.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).