From: "J.D. Schroeder" <Linux.HWI@garmin.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.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 16:04:23 +0000 [thread overview]
Message-ID: <5718FA07.6080501@garmin.com> (raw)
In-Reply-To: <5718E5F3.2080504@ti.com>
On 04/21/2016 09:38 AM, Tomi Valkeinen wrote:
> Thanks, makes sense. Did you measure the rise & fall times? Do you get
> more or less exactly 100kHz with the new times?
Rise time is around 600 nsec and fall time is around 140 nsec. When the clock frequency is measured we get right at 100 kHz and the rise and fall times are negligible. When the HDMI certification test equipment is attached it is just slightly less than 100 kHz, which is okay. The HDMI specification states less than 100 kHz is acceptable not greater. If a particular system has slower rise and fall times then that should be okay also. This change ensures that we stay below 100 kHz regardless of the rise and fall times.
>> Signed-off-by: Lodes, Jim <jim.lodes@garmin.com>
>
> The email format should be
>
> Firstname Lastname <firstname.lastname@foo.bar>
Yes. I'll fix the email and resubmit.
next prev parent reply other threads:[~2016-04-21 16:04 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
2016-04-21 16:04 ` J.D. Schroeder [this message]
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=5718FA07.6080501@garmin.com \
--to=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 \
--cc=tomi.valkeinen@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).