Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Paulo Zanoni <przanoni@gmail.com>
To: intel-gfx@lists.freedesktop.org
Cc: Paulo Zanoni <paulo.r.zanoni@intel.com>
Subject: [PATCH 2/2] drm/i915: don't always force the panel's fixed_mode
Date: Fri,  3 Feb 2012 17:48:21 -0200	[thread overview]
Message-ID: <1328298501-24867-1-git-send-email-przanoni@gmail.com> (raw)

From: Paulo Zanoni <paulo.r.zanoni@intel.com>

My laptop has two 1440x900 modes: one is the fixed_mode and the other
has different timings. If I use xrandr to switch from the fixed mode to
the "other" 1440x900 mode, xrandr will tell me the change was
successful, but nothing was actually done: I'm still using the
fixed_mode. This patch allows us to use other modes if hdisplay and
vdisplay are the same.

Signed-off-by: Paulo Zanoni <paulo.r.zanoni@intel.com>
---
 drivers/gpu/drm/i915/intel_panel.c |    6 ++++++
 1 files changed, 6 insertions(+), 0 deletions(-)

Apply on top of danvet's interlaced branch.

diff --git a/drivers/gpu/drm/i915/intel_panel.c b/drivers/gpu/drm/i915/intel_panel.c
index 230a141..62ca771 100644
--- a/drivers/gpu/drm/i915/intel_panel.c
+++ b/drivers/gpu/drm/i915/intel_panel.c
@@ -36,6 +36,12 @@ void
 intel_fixed_panel_mode(struct drm_display_mode *fixed_mode,
 		       struct drm_display_mode *adjusted_mode)
 {
+	/* Allow modes that match the panel fixed_mode resolution but have
+	 * different timings */
+	if (adjusted_mode->hdisplay == fixed_mode->hdisplay &&
+	    adjusted_mode->vdisplay == fixed_mode->vdisplay)
+		return;
+
 	adjusted_mode->hdisplay = fixed_mode->hdisplay;
 	adjusted_mode->hsync_start = fixed_mode->hsync_start;
 	adjusted_mode->hsync_end = fixed_mode->hsync_end;
-- 
1.7.8.3

             reply	other threads:[~2012-02-03 19:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-03 19:48 Paulo Zanoni [this message]
2012-02-08 22:53 ` [PATCH 2/2] drm/i915: don't always force the panel's fixed_mode Daniel Vetter
2012-02-08 23:18   ` Chris Wilson

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=1328298501-24867-1-git-send-email-przanoni@gmail.com \
    --to=przanoni@gmail.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=paulo.r.zanoni@intel.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