From: ning.a.zhang@intel.com
To: chris@chris-wilson.co.uk, jani.nikula@linux.intel.com,
joonas.lahtinen@linux.intel.com
Cc: intel-gfx@lists.freedesktop.org, Zhang Ning <ning.a.zhang@intel.com>
Subject: [PATCH 0/1] idea for optimize i915 initial time with eDP
Date: Thu, 20 Sep 2018 16:49:04 +0800 [thread overview]
Message-ID: <20180920084905.27032-1-ning.a.zhang@intel.com> (raw)
From: Zhang Ning <ning.a.zhang@intel.com>
I find it on Broxton Gorden Peak, its BIOS doesn't have GOP driver.
displays are powered on by Linux kernel (i915 driver). not BIOS.
For eDP panel, power on it requires to fully powered off, that means wait enough time.
when i915 tries to power on eDP panel, it set last_off_timestamp to driver init time,
this assumes eDP is already powered on.
this is not right on no GOP system, eDP is never powered on.
Then set it to kernel time 0, I know this not right, in two way:
1, this is not *real* last_off_timestamp, can't set an negtive timestamp.
2, no check system with GOP or without GOP, or check whether eDP is powered on.
due to I don't have system with GOP and eDP, can't fully verify my idea.
Zhang Ning (1):
initial panel_power_off_time should be 0
drivers/gpu/drm/i915/intel_dp.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
2.18.0
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2018-09-20 8:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-20 8:49 ning.a.zhang [this message]
2018-09-20 8:49 ` [PATCH 1/1] initial panel_power_off_time should be 0 ning.a.zhang
2018-09-25 9:55 ` Jani Nikula
2018-09-25 14:53 ` Ville Syrjälä
2018-09-26 2:03 ` Zhang, Ning A
2018-09-20 9:35 ` ✗ Fi.CI.CHECKPATCH: warning for idea for optimize i915 initial time with eDP Patchwork
2018-09-20 10:00 ` ✗ Fi.CI.BAT: failure " Patchwork
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=20180920084905.27032-1-ning.a.zhang@intel.com \
--to=ning.a.zhang@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox