From: Ander Conselvan De Oliveira <conselvan2@gmail.com>
To: ville.syrjala@linux.intel.com
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 0/2] drm/i915: Try to sort out ironlake_check_fdi_lanes()
Date: Thu, 12 Mar 2015 09:28:45 +0200 [thread overview]
Message-ID: <1426145325.2645.5.camel@gmail.com> (raw)
In-Reply-To: <1426092751-20036-1-git-send-email-ville.syrjala@linux.intel.com>
On Wed, 2015-03-11 at 18:52 +0200, ville.syrjala@linux.intel.com wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> So these on top of Ander's latest FDI bifurcation patch [1] should hopefully
> result in something sane. Didn't test them though, but assuming Ander
> has that test somewhere maybe some of the problematic cases I identified [2]
> could be checked with these.
I run the tests I wrote here and they all passed. However, the tests
don't cover the eDP on pipe C case. Moreover, I don't have an IVB laptop
I could use for testing that case.
Ander
> [1] http://lists.freedesktop.org/archives/intel-gfx/2015-March/061802.html
> [2] http://lists.freedesktop.org/archives/intel-gfx/2015-March/061806.html
>
> Ville Syrjälä (2):
> drm/i915: Rewrite some some of the FDI lane checks
> drm/i915: Rewrite IVB FDI bifurcation conflict checks
>
> drivers/gpu/drm/i915/intel_display.c | 40 ++++++++++++++++++------------------
> 1 file changed, 20 insertions(+), 20 deletions(-)
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2015-03-12 7:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-11 16:52 [PATCH 0/2] drm/i915: Try to sort out ironlake_check_fdi_lanes() ville.syrjala
2015-03-11 16:52 ` [PATCH 1/2] drm/i915: Rewrite some some of the FDI lane checks ville.syrjala
2015-03-11 16:52 ` [PATCH 2/2] drm/i915: Rewrite IVB FDI bifurcation conflict checks ville.syrjala
2015-03-12 7:35 ` Ander Conselvan De Oliveira
2015-03-12 9:51 ` Daniel Vetter
2015-03-12 7:28 ` Ander Conselvan De Oliveira [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=1426145325.2645.5.camel@gmail.com \
--to=conselvan2@gmail.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ville.syrjala@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.