From: Imre Deak <imre.deak@intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
Paulo R Zanoni <paulo.r.zanoni@intel.com>
Subject: Re: [RFC] Runtime display PM for VLV/BYT
Date: Wed, 16 Oct 2013 17:45:47 +0300 [thread overview]
Message-ID: <1381934747.22425.23.camel@intelbox> (raw)
In-Reply-To: <CAKMK7uEZwChXCwdP09jfDZboz1zALyvOp+Sf9GziGaYpBhtyrA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1208 bytes --]
On Wed, 2013-10-16 at 00:09 +0200, Daniel Vetter wrote:
> On Tue, Oct 15, 2013 at 8:15 PM, Imre Deak <imre.deak@intel.com> wrote:
> > Related to this: I made intel_encoder_get_hw_state() only check if the
> > power well is on and return false if it's not to indicate that the
> > encoder is off. I also thought of doing the same as you and take a ref
> > instead, not sure what's the right way. Maybe doing the readout only if
> > the power is on, but also making sure we have a reference in this case?
> > So with a new helper we'd have in intel_encoder_get_hw_state():
>
> I think the approach we've quickly discussed in today's call is
> probably simplest: We grab a temporary reference to all the display
> power wells around all the dpms/modeset functions and ignore any power
> well checks on top of that. The hw will (well, should) be in the power
> on default state, so nothing should magically turn on if we don't want
> that.
Ok, I'm fine with this too for now, later it can be improved if needed.
I added a new POWER_DOMAIN_INIT for keeping all power wells on through
driver init->first modeset and suspend->first modeset, that could be
used for this purpose too.
--Imre
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 490 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:[~2013-10-16 14:45 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-14 23:07 [RFC] Runtime display PM for VLV/BYT Jesse Barnes
2013-10-14 23:07 ` [PATCH 1/5] drm/i915/vlv: power well support " Jesse Barnes
2013-10-14 23:07 ` [PATCH 2/5] drm/i915: add display power well report out to debugfs Jesse Barnes
2013-10-14 23:07 ` [PATCH 3/5] drm/i915/vlv: suspend/resume fixes for VLV/BYT Jesse Barnes
2013-10-14 23:07 ` [PATCH 4/5] drm/i915: take power well refs when needed Jesse Barnes
2013-10-15 19:54 ` Paulo Zanoni
2013-10-15 20:40 ` Jesse Barnes
2013-10-15 20:47 ` Paulo Zanoni
2013-10-15 20:57 ` Jesse Barnes
2013-10-15 21:03 ` Paulo Zanoni
2013-10-16 11:10 ` Imre Deak
2013-10-16 15:08 ` Jesse Barnes
2013-10-17 13:01 ` Imre Deak
2013-10-14 23:07 ` [PATCH 5/5] drm/i915/vlv: support save/restore of display state around power well toggle Jesse Barnes
2013-10-15 20:09 ` Paulo Zanoni
2013-10-15 20:42 ` Jesse Barnes
2013-10-16 8:54 ` Daniel Vetter
2013-10-15 8:06 ` [RFC] Runtime display PM for VLV/BYT Ville Syrjälä
2013-10-15 12:16 ` Imre Deak
2013-10-15 16:23 ` Jesse Barnes
2013-10-15 18:15 ` Imre Deak
2013-10-15 22:09 ` Daniel Vetter
2013-10-16 14:45 ` Imre Deak [this message]
2013-10-15 9:59 ` Daniel Vetter
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=1381934747.22425.23.camel@intelbox \
--to=imre.deak@intel.com \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=paulo.r.zanoni@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.