From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Paulo Zanoni <przanoni@gmail.com>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
DRI Development <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 0/4] drm/edid: Recognize 60Hz and 59.94Hz CEA modes
Date: Thu, 18 Apr 2013 18:31:30 +0300 [thread overview]
Message-ID: <20130418153130.GT4469@intel.com> (raw)
In-Reply-To: <CA+gsUGRYNpUk8sdeBa4yUwLK1TRYMKMSjbx4Ckjy7zE6dNY=Mw@mail.gmail.com>
On Wed, Apr 17, 2013 at 05:38:57PM -0300, Paulo Zanoni wrote:
> 2013/4/17 <ville.syrjala@linux.intel.com>:
> > This series attempts to make our CEA mode matching recognize both the
> > 60Hz and 59.94Hz variants of the modes (and similarly for 24/23.97,
> > 30/29.97, etc.).
> >
> > The benefits should include:
> > - Send the correct VIC in the AVI infoframe
> > - Pick the correct RGB quantization range in automatic mode
>
> Everything looks correct, but I really didn't test anything. If you
> apply my comments from patch 2, then you have "Reviewed-by: Paulo
> Zanoni <paulo.r.zanoni@intel.com>" for all the 4 patches.
Thanks for the review.
>
> Optional bikeshedding: you could add a follow-up patch fixing the
> comments inside edid_cea_modes to reflect the correct Hz used,
> replacing, for example, "AxB@60Hz" with "AxB@59.94Hz". But I can
> certainly live without this :)
I think I'll defer on that one until we decide whether we want add
both 60Hz and 59.94HZ versions to the connector's mode list. Daniel
suggested we do it, but I disagree slightly since CEA-861 says that
monitors should only advertise one variant in their detailed timings.
I was thinking that we'd follow that rule here as well. But I can
be easily convinced otherwise, in case someone else has an
opinion...
--
Ville Syrjälä
Intel OTC
prev parent reply other threads:[~2013-04-18 15:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-17 17:37 [PATCH 0/4] drm/edid: Recognize 60Hz and 59.94Hz CEA modes ville.syrjala
2013-04-17 17:37 ` [PATCH 1/4] drm: Remove explicit vrefresh initialization from DRM_MODE() ville.syrjala
2013-04-17 17:37 ` [PATCH 2/4] drm: Add drm_mode_equal_no_clocks() ville.syrjala
2013-04-17 19:32 ` Paulo Zanoni
2013-04-17 17:37 ` [PATCH 3/4] drm/edid: Populate vrefresh for CEA modes ville.syrjala
2013-04-17 17:37 ` [PATCH 4/4] drm/edid: Check both 60Hz and 59.94Hz when looking for a CEA mode ville.syrjala
2013-04-17 20:38 ` [PATCH 0/4] drm/edid: Recognize 60Hz and 59.94Hz CEA modes Paulo Zanoni
2013-04-18 15:31 ` Ville Syrjälä [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=20130418153130.GT4469@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=przanoni@gmail.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