From: Wang Xingchao <xingchao.wang@linux.intel.com>
To: daniel@ffwll.ch, tiwai@suse.de
Cc: alsa-devel@alsa-project.org, jocelyn.li@intel.com,
intel-gfx@lists.freedesktop.org,
Wang Xingchao <xingchao.wang@linux.intel.com>,
xingchao.wang@intel.com, liam.r.girdwood@intel.com,
david.henningsson@canonical.com
Subject: [PATCH 0/4 V5] Power-well API implementation for Haswell
Date: Thu, 23 May 2013 01:04:12 +0800 [thread overview]
Message-ID: <1369242256-32112-1-git-send-email-xingchao.wang@linux.intel.com> (raw)
Hi all,
This is V5 and here're some changes notes:
change from V4-->V5:
- fix reference count bug
- new patch on general runtime pm support for audio pci device
- new patch to avoid request_module() deadlock
change between V3-->V4:
- add new structure i915_power_well
- initialize drm_device pointer at module init time
- change function name
change between V2-->V3:
- make SND_HDA_I915 selectable
- use snd_printdd to output message
- add return error code check
- use symbol_request to replace symbol_get
- release power_well at azx_free
- some typo fixes
changes between V1-->V2:
- use reference count to track power-well usage
- remove external module, compiled into snd-hda-intel instead
- manage symbols and module loading properly
- remove IS_HSW macro, use flag instead
- remove audio callback for gfx driver to avoid dependency
- split whole patch into two pieces for easy review
- more typo fixes
Wang Xingchao (4):
i915/drm: Add private api for power well usage
ALSA: hda - Add power-welll support for haswell HDA
ALSA: hda - Fix runtime PM check
ALSA: hda - Continue probe in work context to avoid request_module
deadlock
drivers/gpu/drm/i915/i915_dma.c | 6 ++
drivers/gpu/drm/i915/i915_drv.h | 12 ++++
drivers/gpu/drm/i915/intel_drv.h | 4 ++
drivers/gpu/drm/i915/intel_pm.c | 92 ++++++++++++++++++++++++---
include/drm/i915_powerwell.h | 36 +++++++++++
sound/pci/hda/Kconfig | 10 +++
sound/pci/hda/Makefile | 3 +
sound/pci/hda/hda_i915.c | 75 ++++++++++++++++++++++
sound/pci/hda/hda_i915.h | 35 +++++++++++
sound/pci/hda/hda_intel.c | 132 ++++++++++++++++++++++++++++-----------
10 files changed, 360 insertions(+), 45 deletions(-)
create mode 100644 include/drm/i915_powerwell.h
create mode 100644 sound/pci/hda/hda_i915.c
create mode 100644 sound/pci/hda/hda_i915.h
--
1.8.1.2
next reply other threads:[~2013-05-22 17:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 17:04 Wang Xingchao [this message]
2013-05-22 17:04 ` [PATCH 1/4 V5] i915/drm: Add private api for power well usage Wang Xingchao
2013-05-23 15:14 ` Takashi Iwai
2013-05-22 17:04 ` [PATCH 2/4 V5] ALSA: hda - Add power-welll support for haswell HDA Wang Xingchao
2013-05-22 17:04 ` [PATCH 3/4] ALSA: hda - Fix runtime PM check Wang Xingchao
2013-05-23 6:02 ` Takashi Iwai
2013-05-23 7:53 ` Wang, Xingchao
2013-05-23 8:09 ` Takashi Iwai
2013-05-23 10:20 ` Wang, Xingchao
2013-05-23 12:34 ` David Henningsson
2013-05-23 12:39 ` [alsa-devel] " Takashi Iwai
2013-05-22 17:04 ` [PATCH 4/4] ALSA: hda - Continue probe in work context to avoid request_module deadlock Wang Xingchao
2013-05-23 6:47 ` Takashi Iwai
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=1369242256-32112-1-git-send-email-xingchao.wang@linux.intel.com \
--to=xingchao.wang@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=daniel@ffwll.ch \
--cc=david.henningsson@canonical.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jocelyn.li@intel.com \
--cc=liam.r.girdwood@intel.com \
--cc=tiwai@suse.de \
--cc=xingchao.wang@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