From: Keith Packard <keithp@keithp.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Scott James Remnant <keybuk@google.com>
Cc: intel-gfx@lists.freedesktop.org,
"Stéphane Marchesin" <marcheu@google.com>,
"Daniel Stone" <daniels@collabora.com>
Subject: Re: i915_init takes a full second of kernel init time
Date: Thu, 15 Dec 2011 09:48:39 -0800 [thread overview]
Message-ID: <86sjklafpk.fsf@sumi.keithp.com> (raw)
In-Reply-To: <c55c5d$1d932o@AZSMGA002.ch.intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 746 bytes --]
On Thu, 15 Dec 2011 10:38:16 +0000, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> Reverting de842eff4101 (drm/i915: Wait for LVDS panel power sequence)
> should get another 0.4s back if intel_lvds_enable() is still in the
> critical path. After that the focus looks to be upon speeding up
> modeset.
*not* doing modeset for LVDS/eDP is the key here -- the panel is
probably already running, and all we need to do is change the scaling
parameters, which (on new hardware) doesn't require a full mode set.
I worked with vorlon to investigate what this would take and got pretty
far down the path; the big missing piece is that we have to have
a valid scanout buffer for the whole setup sequence.
--
keith.packard@intel.com
[-- Attachment #1.2: Type: application/pgp-signature, Size: 827 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2011-12-15 17:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-13 19:55 i915_init takes a full second of kernel init time Scott James Remnant
2011-12-13 20:02 ` Jesse Barnes
2011-12-13 21:34 ` Scott James Remnant
2011-12-13 22:01 ` Jesse Barnes
2011-12-13 22:21 ` Chris Wilson
2011-12-15 0:38 ` Scott James Remnant
2011-12-15 10:38 ` Chris Wilson
2011-12-15 17:48 ` Keith Packard [this message]
2011-12-15 21:48 ` Scott James Remnant
2011-12-15 22:22 ` Keith Packard
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=86sjklafpk.fsf@sumi.keithp.com \
--to=keithp@keithp.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniels@collabora.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=keybuk@google.com \
--cc=marcheu@google.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