From: Imre Deak <imre.deak@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org,
Paulo R Zanoni <paulo.r.zanoni@intel.com>
Subject: Re: [RFC] Runtime display PM for VLV/BYT
Date: Tue, 15 Oct 2013 15:16:11 +0300 [thread overview]
Message-ID: <1381839371.26119.12.camel@intelbox> (raw)
In-Reply-To: <20131015080606.GM13047@intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 2030 bytes --]
On Tue, 2013-10-15 at 11:06 +0300, Ville Syrjälä wrote:
> On Mon, Oct 14, 2013 at 04:07:44PM -0700, Jesse Barnes wrote:
> > This set adds bits needed for runtime power support, currently only
> > lightly tested on VLV/BYT:
> > 1) suspend/resume callbacks for different platforms
> > 2) save/restore of display state across a power well toggle
> > 3) get/put of display power well in critical places
> >
> > The TODO list still has a few items on it, and I'm looking for feedback:
> > 1) sprinkle around some power well WARNs so we can catch things easily
> > 2) add some tests using DPMS and NULL mode sets and comparing power
> > well state
> > 3) better debugfs support for multiple wells
> > 4) refcount of power well in debugfs (with ref holders?)
> > 5) more testing - I think the load time ref is still busted here and
> > on HSW
> > 6) convert HSW as well so DPMS will shut things down, not just mode
> > sets
> >
> > Thoughts or comments?
>
> I'd also like to see what Imre cooked up, and then come up with some
> grand unified design. Based on our discussions I think his power well
> abstraction sounded somewhat nicer and more general.
I've pushed what I have so far to:
https://github.com/ideak/linux/commits/powerwells
I've tested this on VLV with VGA output so far and somewhat on HSW. I'd
still have to check the need to do any HW state save/restore and the GFX
clock forcing, afaics Jesse has already code for these in his patchset.
> Also your locking seems to be fubar in places (frobbing with sideband
> while holding a spinlock). I think Imre converted the power wells to
> use a mutex everywhere.
Yea, I solved that by changing power_well->lock to be a mutex.
> Or perhaps we just start with your stuff and Imre rebases his stuff on
> top?
That works for me too. In any case would be nice to get some feedback
especially from Paulo as my changes are mostly about the current power
domain / well handling parts.
--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-15 12:16 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 [this message]
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
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=1381839371.26119.12.camel@intelbox \
--to=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=paulo.r.zanoni@intel.com \
--cc=ville.syrjala@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