alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: alsa-devel@alsa-project.org
Cc: liam.r.girdwood@linux.intel.com, patches.audio@intel.com,
	broonie@kernel.org, Vinod Koul <vinod.koul@intel.com>
Subject: [PATCH 0/2] ASoC: Intel: Skylake: Add HDA link management
Date: Thu, 28 Apr 2016 19:30:57 +0530	[thread overview]
Message-ID: <1461852059-20518-1-git-send-email-vinod.koul@intel.com> (raw)

HDA links are always kept On, this patch adds link management routines in hdac
extended core and it's use in Skylake driver.
One more patch to add support in codec will follow this

The aim of serial is to shut down the links when not in use and keep them
active when a user is active. The user can activate link by taking reference
to the link when required.

When all links are shutdown, the command DMAs are turned off as well. On
first link power up, the command DMAs are turned on first.


First patch touches HDA core, and second one is dependent on it so Takashi
if you are okay, pls ACK it and we cna merge thru ASoC tree

Vinod Koul (2):
  ALSA: hdac: add link pm and ref counting
  ASoC: Intel: Skylake: add link mangement

 include/sound/hdaudio_ext.h         | 13 ++++++++
 sound/hda/ext/hdac_ext_bus.c        |  3 ++
 sound/hda/ext/hdac_ext_controller.c | 62 +++++++++++++++++++++++++++++++++++++
 sound/soc/intel/skylake/skl-pcm.c   |  1 -
 sound/soc/intel/skylake/skl.c       | 34 ++++++++++++++++++++
 5 files changed, 112 insertions(+), 1 deletion(-)

-- 
1.9.1

             reply	other threads:[~2016-04-28 13:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-28 14:00 Vinod Koul [this message]
2016-04-28 14:00 ` [PATCH 1/2] ALSA: hdac: add link pm and ref counting Vinod Koul
2016-04-29  9:05   ` Takashi Iwai
2016-05-02  9:02     ` Vinod Koul
2016-04-28 14:00 ` [PATCH 2/2] ASoC: Intel: Skylake: add link mangement Vinod Koul

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=1461852059-20518-1-git-send-email-vinod.koul@intel.com \
    --to=vinod.koul@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=patches.audio@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;
as well as URLs for NNTP newsgroup(s).