public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: cache the EDID for eDP panels
Date: Wed, 6 Jun 2012 09:23:18 +0200	[thread overview]
Message-ID: <20120606072318.GA4699@phenom.ffwll.local> (raw)
In-Reply-To: <20120605144115.31ca3da7@jbarnes-desktop>

On Tue, Jun 05, 2012 at 02:41:15PM -0700, Jesse Barnes wrote:
> On Tue, 05 Jun 2012 22:38:02 +0100
> Chris Wilson <chris@chris-wilson.co.uk> wrote:
> 
> > On Tue, 5 Jun 2012 14:26:11 -0700, Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
> > > Yeah that makes sense.  Not sure how much this conflicts with Daniel's
> > > hot plug rework either; there's likely some overlap.
> > 
> > We could have made that Daniel's problem.... ;)
> > http://lists.freedesktop.org/archives/intel-gfx/2011-April/010401.html
> 
> Hey look I even reviewed it.
> 
> Pick up the pieces, Daniel! :)

I agree looks nice. Can I ask for a resend? Afaics all the stuff got
acks/r-bs safe for patch 6 (maybe just drop that one). And I agree with
Jesse's bikeshed on patch 8, is_panel sounds more like what we want.

Dunno about patch 10, killing that pointless flicker would certainly be
nice. I guess we could just merge it and see what happens, then claim
innonce when getting caught with our hands in the cookie jar ;-)

Oh, and I don't think there's much overlap with the hpd stuff of mine,
that only caches edids at ->detect time and relies on core drm changes to
make calls to ->detect happen less often.
-Daniel
-- 
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48

  reply	other threads:[~2012-06-06  7:21 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-05 20:54 [PATCH] drm/i915: cache the EDID for eDP panels Jesse Barnes
2012-06-05 21:02 ` Chris Wilson
2012-06-05 21:26   ` Jesse Barnes
2012-06-05 21:38     ` Chris Wilson
2012-06-05 21:41       ` Jesse Barnes
2012-06-06  7:23         ` Daniel Vetter [this message]
2012-06-06  7:23 ` Jani Nikula
2012-06-06  7:36 ` Takashi Iwai
2012-06-14 17:20   ` Jesse Barnes
  -- strict thread matches above, loose matches on Subject: below --
2012-06-14 17:19 Jesse Barnes
2012-06-14 18:30 Jesse Barnes
2012-06-14 18:37 ` Chris Wilson
2012-06-14 18:55   ` Jesse Barnes
2012-06-14 19:02 Jesse Barnes
2012-06-14 19:28 Jesse Barnes
2012-06-14 19:42 ` Chris Wilson
2012-06-14 19:44   ` Jesse Barnes
2012-06-15  7:34 ` Jani Nikula
2012-06-15 17:31   ` Jesse Barnes
2012-06-15 17:41     ` Daniel Vetter
2012-06-15  8:21 ` Chris Wilson
2012-06-15 10:52   ` Jani Nikula
2012-06-15 10:55     ` 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=20120606072318.GA4699@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jbarnes@virtuousgeek.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