From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: "J.D. Schroeder" <Linux.HWI@garmin.com>
Cc: linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
linux-fbdev@vger.kernel.org, misael.lopez@ti.com,
Jim Lodes <jim.lodes@garmin.com>,
"J.D. Schroeder" <jay.schroeder@garmin.com>
Subject: Re: [PATCH v2] OMAPDSS: HDMI5: Change DDC timings
Date: Wed, 27 Apr 2016 05:55:05 +0000 [thread overview]
Message-ID: <57205439.3010303@ti.com> (raw)
In-Reply-To: <1461259669-5194-1-git-send-email-Linux.HWI@garmin.com>
[-- Attachment #1.1: Type: text/plain, Size: 816 bytes --]
On 21/04/16 20:27, J.D. Schroeder wrote:
> From: Jim Lodes <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.
>
> Signed-off-by: Jim Lodes <jim.lodes@garmin.com>
> Signed-off-by: J.D. Schroeder <jay.schroeder@garmin.com>
> ---
> drivers/gpu/drm/omapdrm/dss/hdmi5_core.c | 4 ++--
> drivers/video/fbdev/omap2/omapfb/dss/hdmi5_core.c | 4 ++--
> 2 files changed, 4 insertions(+), 4 deletions(-)
Thanks! Queuing this for 4.7.
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-04-27 5:55 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
2016-04-21 17:27 ` [PATCH v2] " J.D. Schroeder
2016-04-27 5:55 ` Tomi Valkeinen [this message]
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=57205439.3010303@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).