public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Paulo Zanoni <przanoni@gmail.com>
Cc: "intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"Widawsky, Benjamin" <benjamin.widawsky@intel.com>
Subject: Re: How will Gfx driver support runtime PM on Haswell?
Date: Fri, 23 Aug 2013 10:10:44 -0700	[thread overview]
Message-ID: <20130823101044.4b8d3e32@jbarnes-desktop> (raw)
In-Reply-To: <CA+gsUGR5+zUMa5xvwRbGaNc-v+ViMKNh3i+YmNTdrhube-2DUA@mail.gmail.com>

On Fri, 23 Aug 2013 13:49:57 -0300
Paulo Zanoni <przanoni@gmail.com> wrote:

> 2013/8/22 Jesse Barnes <jbarnes@virtuousgeek.org>:
> > On Wed, 21 Aug 2013 15:29:17 +0000
> > "Lin, Mengdong" <mengdong.lin@intel.com> wrote:
> >
> >> Hi Ben,
> >>
> >> How will Gfx driver support runtime PM on Haswell? Will the Gfx driver trigger "Adapter Power State" notification to BIOS when GPU switch state between D0 and D3?
> >>
> >> We need to support RTD3 for HD-A legacy audio on Haswell Ultrabook. And this depends on Gfx driver to implement two BIOS notifications.
> >>
> >> Here is the background of this dependency:
> >> The target of HD-Audio RTD3 is that BIOS can power off the on-board 3rd party audio codec to save power in S0. This would help to save ~60mW.
> >> Please note that audio driver cannot power off the codec, because the codec power is controlled by some GPIO which is board specific.
> >>
> >> The BIOS will power off the audio codec when three requirements are met:
> >>
> >> (1)     System is running on battery
> >>
> >> (2)     HD-Audio controller is in D3. Means no active audio application is using the audio devices.
> >>
> >> (3)     All displays are off. This means system is in "User-Absent Mode", and a long latency for devices to resume back to D0 is allowed, such as ~300ms to power on the audio codec.
> >>
> >> For the 3rd requirement, BIOS needs Gfx driver to tell whether the system is in user-absent mode. It needs Gfx driver to triger two SCI SW notifications: Display Power State Notification and Adapter Power State Notification.
> >> 'Display Power State Notification' was implemented by Jani. But we were told that 'Adapter Power State' notification needs Gfx driver to support runtime PM at first.
> >>
> >> So would you please share some information about runtime PM support in Gfx driver?
> >
> > Paulo was going to test this on top of his PC8+ patchset.  AFAFIK the
> > only thing we  need to do is put the device into D3 when we enter the
> > PC8+ mode, and the BIOS will do the right thing (when we use the
> > OpRegion stuff Jani did anyway).
> >
> > Paulo, are you still out celebrating the PC8 bits or have you had a
> > chance to try this yet?
> 
> From Mengdong's email, it seems Jani's patch series implements exactly
> what was requested, except for the fact that our patch says "D1"
> instead of "D3" to the BIOS. Is there something else we need besides
> this?

I don't think so... well except for testing. :)  If you have something
that seems to work it's probably worthwhile to get Kristen to try it
out on her instrumented setup.

-- 
Jesse Barnes, Intel Open Source Technology Center

      reply	other threads:[~2013-08-23 17:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-21 15:29 How will Gfx driver support runtime PM on Haswell? Lin, Mengdong
2013-08-22 23:07 ` Jesse Barnes
2013-08-23 16:49   ` Paulo Zanoni
2013-08-23 17:10     ` Jesse Barnes [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=20130823101044.4b8d3e32@jbarnes-desktop \
    --to=jbarnes@virtuousgeek.org \
    --cc=benjamin.widawsky@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=przanoni@gmail.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