From: ville.syrjala@linux.intel.com
To: dri-devel@lists.freedesktop.org
Cc: intel-gfx@lists.freedesktop.org
Subject: [PATCH 0/4] drm/edid: Recognize 60Hz and 59.94Hz CEA modes v2
Date: Wed, 24 Apr 2013 19:07:14 +0300 [thread overview]
Message-ID: <1366819638-5260-1-git-send-email-ville.syrjala@linux.intel.com> (raw)
The same old CEA mode 60 Hz vs. 59.94 Hz handling series.
While reviewing v1, Paulo noticed a missing EXPORT_SYMBOL(),
which is now fixed. Everything else is unchanged.
From my POV this is ready to go in. The only real questions is
whether or not we want to populate the connector's mode list
with both 60Hz and 59.94 Hz variants. But that's an orthogonal
issue, and doesn't prevent us from merging this set.
Ville Syrjälä (4):
drm: Remove explicit vrefresh initialization from DRM_MODE()
drm: Add drm_mode_equal_no_clocks()
drm/edid: Populate vrefresh for CEA modes
drm/edid: Check both 60Hz and 59.94Hz when looking for a CEA mode
drivers/gpu/drm/drm_edid.c | 220 ++++++++++++++++++++++++++++++--------------
drivers/gpu/drm/drm_modes.c | 22 ++++-
include/drm/drm_crtc.h | 3 +-
3 files changed, 176 insertions(+), 69 deletions(-)
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2013-04-24 16:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-24 16:07 ville.syrjala [this message]
2013-04-24 16:07 ` [PATCH 1/4] drm: Remove explicit vrefresh initialization from DRM_MODE() ville.syrjala
2013-04-24 16:07 ` [PATCH v2 2/4] drm: Add drm_mode_equal_no_clocks() ville.syrjala
2013-04-24 16:07 ` [PATCH 3/4] drm/edid: Populate vrefresh for CEA modes ville.syrjala
2013-04-24 16:07 ` [PATCH 4/4] drm/edid: Check both 60Hz and 59.94Hz when looking for a CEA mode ville.syrjala
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=1366819638-5260-1-git-send-email-ville.syrjala@linux.intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.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