public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Imre Deak <imre.deak@intel.com>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
	"Zanoni, Paulo R" <paulo.r.zanoni@intel.com>
Subject: Re: Power saving using Display port HPD
Date: Tue, 15 Apr 2014 23:13:25 +0200	[thread overview]
Message-ID: <20140415211325.GC10722@phenom.ffwll.local> (raw)
In-Reply-To: <1397592062.2715.19.camel@ideak-mobl>

On Tue, Apr 15, 2014 at 11:01:02PM +0300, Imre Deak wrote:
> On Tue, 2014-04-15 at 21:32 +0200, Daniel Vetter wrote:
> > On Mon, Apr 14, 2014 at 11:17:53AM +0300, Imre Deak wrote:
> > > On Mon, 2014-04-14 at 09:47 +0200, Daniel Vetter wrote:
> > > > On Mon, Apr 14, 2014 at 9:43 AM, Arun Chandran <achandran@mvista.com> wrote:
> > > > > 1)  Revert the commit 77961eb984c7e5394bd29cc7be2ab0bf0cc7e7b1.
> > > > > With this commit DP hotplug events are not coming after doing "xset dpms
> > > > > force off"
> > > > >
> > > > > commit bfcbf45b5b458ebdc38118ca67279a1cd90e085d
> > > > > Author: Arun Chandran <achandran@mvista.com>
> > > > > Date:   Fri Apr 11 16:16:32 2014 +0530
> > > > >
> > > > >     Revert "drm/i915: power domains: add vlv power wells"
> > > > >
> > > > >     This reverts commit 77961eb984c7e5394bd29cc7be2ab0bf0cc7e7b1.
> > > > 
> > > > So this breaks DP hotplug detection? Imre?
> > > 
> > > Yes, unfortunately. I made this clear in my patchset [1] and it was also
> > > discussed on IRC. If there isn't any (e)DP,HDMI pipe active we power
> > > down the DPIO HW block responsible normally for DP and HDMI hotplug
> > > detection.
> > > 
> > > There is one possible solution: the pin that is used for HPD detection
> > > can be used either normally in the above way, where it's controlled by
> > > the DPIO block, or as a GPIO where it's controlled by the GPIO HW block
> > > which is on even if we power down the DPIO. So during power down periods
> > > we could reconfigure that pin to work as a GPIO and treat any interrupts
> > > arriving it as an HPD event. I haven't had yet time to investigate this.
> > > 
> > > Another way is to turn on polling while powered down. This would also
> > > make VGA hotplug work, for which we don't have a GPIO alternative as
> > > above.
> > > 
> > > [1] 
> > > http://lists.freedesktop.org/archives/intel-gfx/2014-February/040232.html
> > 
> > Iirc we've agreed that when all screens are off it's ok to no longer
> > support hotplug. Or is this only the case when _only_ the DP port is off
> > but e.g. another port (edp or mipi) is on?
> 
> If eDP is on HPD should work fine since the DPIO block is on. With only
> MIPI on, we would atm turn off the DPIO, so I assume we would again lose
> HPD :( But I haven't tested this last scenario.
> 
> Btw, I think Antti is planning to look into the GPIO workaround thing,
> so if that works out we'd get back HPD for DP and HDMI at least (but not
> for VGA).

Yeah, this is a bit worse. Otoh most byt platforms actually shipping will
only have a hdmi port externally, so I think we could just enable the
required power well always as long as we're not in D3. Imo when the
integrated panel is on, hotplug really should work.

Or maybe we should just switch between hotplug and polling on byt for vga.

> > I'm asking since currently on hsw/bdw hotplug also doesn't work when you
> > switch everything off ...
> 
> Hm, on BDW/HSW we mask all interrupts at runtime suspend->D3 state, so
> that's the reason there .. I don't know if it's possible to get a
> wake-up signal on an HPD event in D3, I haven't checked this myself,
> maybe Paulo knows. But I doubt. CC'ing him.
> 
> It's a bit different than VLV, since there we lose HPD already in D0,
> when the display side is off. On BDW,HSW in that case we still have HPD,
> although probably shortly afterwards (10 sec) runtime supend->D3 follows
> anyway.

Hm, we need to tune the default runtime value. If all screens are of we
should be able to do runtime pm in a few seconds, so anything more than 1
second is massive overkill imo.

For the overall hotplug in D3 issue I think we can wait until someone
screams with an actual use-case.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

      reply	other threads:[~2014-04-15 21:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-10  6:36 Power saving using Display port HPD Arun Chandran
2014-04-10  7:22 ` Jani Nikula
2014-04-10  7:24 ` Daniel Vetter
2014-04-10  7:39   ` Jani Nikula
2014-04-10 10:28   ` Arun Chandran
2014-04-14  7:43     ` Arun Chandran
2014-04-14  7:47       ` Daniel Vetter
2014-04-14  8:17         ` Imre Deak
2014-04-15 19:32           ` Daniel Vetter
2014-04-15 20:01             ` Imre Deak
2014-04-15 21:13               ` Daniel Vetter [this message]

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=20140415211325.GC10722@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=imre.deak@intel.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox