From: Daniel Vetter <daniel@ffwll.ch>
To: "Wang, Xingchao" <xingchao.wang@intel.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"Zanoni, Paulo R" <paulo.r.zanoni@intel.com>,
Takashi Iwai <tiwai@suse.de>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"Wysocki, Rafael J" <rafael.j.wysocki@intel.com>,
Wang Xingchao <xingchao.wang@linux.intel.com>,
"Girdwood, Liam R" <liam.r.girdwood@intel.com>,
"Li, Jocelyn" <jocelyn.li@intel.com>,
"Hindman, Gavin" <gavin.hindman@intel.com>,
"Barnes, Jesse" <jesse.barnes@intel.com>,
"Lin, Mengdong" <mengdong.lin@intel.com>
Subject: Re: [PATCH] drm/i915: Add private api for power well usage -- alignment between graphic team and audio team
Date: Sat, 27 Apr 2013 13:35:29 +0200 [thread overview]
Message-ID: <20130427113529.GT6169@phenom.ffwll.local> (raw)
In-Reply-To: <46B810F6945F7C4788E11DCE57EC4890109D3608@SHSMSX102.ccr.corp.intel.com>
On Sat, Apr 27, 2013 at 09:20:39AM +0000, Wang, Xingchao wrote:
> Let me throw a basic proposal on Audio driver side, please give your comments freely.
>
> it contains the power well control usage points:
> #1: audio request power well at boot up.
> I915 may shut down power well after bootup initialization, as there's no monitor connected outside or only eDP on pipe A.
> #2: audio request power on resume
> After exit from D3 mode, audio driver quest power on. This may happen at normal resume or runtime resume.
> #3: audio release power well control at suspend
> Audio driver will let i915 know it doensot need power well anymore as it's going to suspend. This may happened at normal suspend or runtime suspend point.
> #4: audio release power well when module unload
> Audio release power well at remove callback to let i915 know.
I miss the power well grab/dropping at runtime from the audio side. If the
audio driver forces the power well to be on the entire time it's loaded,
that's not good, since the power well stuff is very much for runtime PM.
We _must_ be able to switch off the power well whenever possible.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2013-04-27 11:35 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 6:58 [PATCH] drm/i915: Add private api for power well usage -- alignment between graphic team and audio team Li, Jocelyn
2013-04-26 7:24 ` Daniel Vetter
2013-04-26 7:53 ` Li, Jocelyn
2013-04-26 14:57 ` Daniel Vetter
2013-04-26 15:12 ` Takashi Iwai
2013-04-26 15:42 ` Daniel Vetter
2013-04-26 15:45 ` Takashi Iwai
2013-04-26 17:17 ` Daniel Vetter
2013-04-27 9:20 ` Wang, Xingchao
2013-04-27 11:35 ` Daniel Vetter [this message]
2013-04-29 15:02 ` Jesse Barnes
2013-04-30 10:29 ` David Henningsson
2013-04-30 14:38 ` Jesse Barnes
2013-05-02 3:17 ` Lin, Mengdong
2013-04-30 14:41 ` [alsa-devel] " Liam Girdwood
2013-05-02 14:49 ` David Henningsson
2013-05-03 8:28 ` [alsa-devel] " Wang, Xingchao
2013-05-03 12:02 ` David Henningsson
2013-05-03 14:31 ` Takashi Iwai
2013-05-02 7:11 ` Wang, Xingchao
2013-05-03 14:26 ` Takashi Iwai
2013-05-03 15:17 ` Wang, Xingchao
2013-04-27 8:54 ` Wang, Xingchao
2013-04-27 8:46 ` Wang, Xingchao
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=20130427113529.GT6169@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=alsa-devel@alsa-project.org \
--cc=daniel.vetter@ffwll.ch \
--cc=gavin.hindman@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jesse.barnes@intel.com \
--cc=jocelyn.li@intel.com \
--cc=liam.r.girdwood@intel.com \
--cc=mengdong.lin@intel.com \
--cc=paulo.r.zanoni@intel.com \
--cc=rafael.j.wysocki@intel.com \
--cc=tiwai@suse.de \
--cc=xingchao.wang@intel.com \
--cc=xingchao.wang@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