From: Chris Wilson <chris@chris-wilson.co.uk>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Andreas Heider <andreas@meetr.de>,
Seth Forshee <seth.forshee@canonical.com>
Subject: Re: [PATCH 4/4] drm/i915: check LVDS for EDID on GPU switches
Date: Tue, 7 Jan 2014 10:45:53 +0000 [thread overview]
Message-ID: <20140107104553.GC8991@nuc-i3427.alporthouse.com> (raw)
In-Reply-To: <1389088723-30959-5-git-send-email-artagnon@gmail.com>
On Tue, Jan 07, 2014 at 03:28:43PM +0530, Ramkumar Ramachandra wrote:
> If the LVDS panel wasn't connected at boot then we won't have an EDID
> for it. To fix this, call intel_lvds_get_edid() from the vga_switcheroo
> reprobe callback.
I would rather have an iterator over all our connectors (or perhaps
encoders would be the right semantic, except we have
connectors==encoders) and a reprobe callback. Saves exporting private
functions and prevent me asking silly questions like what about eDP?
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2014-01-07 10:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-07 9:58 [PATCH 0/4] Get EDID late for VGA switcheroo Ramkumar Ramachandra
2014-01-07 9:58 ` [PATCH 1/4] drm/i915: add support for vga_switcheroo reprobe Ramkumar Ramachandra
2014-01-07 10:43 ` Chris Wilson
2014-01-07 10:53 ` Ramkumar Ramachandra
2014-01-07 9:58 ` [PATCH 2/4] drm/i915: factor out intel_lvds_get_edid() Ramkumar Ramachandra
2014-01-07 9:58 ` [PATCH 3/4] drm/i915: prepare intel_lvds_get_edid() for multiple calls Ramkumar Ramachandra
2014-01-07 9:58 ` [PATCH 4/4] drm/i915: check LVDS for EDID on GPU switches Ramkumar Ramachandra
2014-01-07 10:45 ` Chris Wilson [this message]
2014-01-07 11:12 ` Ramkumar Ramachandra
2014-01-07 11:48 ` Chris Wilson
2014-01-07 13:05 ` Ramkumar Ramachandra
2014-01-07 13:14 ` Chris Wilson
2014-01-07 13:54 ` [PATCH 0/4] Get EDID late for VGA switcheroo Seth Forshee
2014-01-07 14:30 ` Ramkumar Ramachandra
2014-01-07 14:42 ` andreas
2014-01-07 14:58 ` Ramkumar Ramachandra
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=20140107104553.GC8991@nuc-i3427.alporthouse.com \
--to=chris@chris-wilson.co.uk \
--cc=andreas@meetr.de \
--cc=artagnon@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=seth.forshee@canonical.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
all inboxes | Powered by JetHome®