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/3] ASoC: Intel: Skylake: Refine manifest module info
Date: Wed, 10 Aug 2016 09:40:47 +0530 [thread overview]
Message-ID: <1470802250-9232-1-git-send-email-vinod.koul@intel.com> (raw)
The module query uses a local structure dfw_config and then populates
module skl_module_cfg. Instead we can pass skl_module_cfg as argument
and get it updated in snd_skl_get_module_info()
Also we can optimize runtime processing by using driver list to populate
module info after init. That makes runtime query introduced earlier
redundant so remove that while keeping error messages.
Dharageswari R (1):
ASoC: Intel: Skylake: modify snd_skl_get_module_info args
Vinod Koul (2):
ASoC: Intel: Skylake: Populate modules after loading
ASoC: Intel: Skylake: remove module id query at runtime
sound/soc/intel/skylake/skl-pcm.c | 27 +++++++++++++++++++++++++++
sound/soc/intel/skylake/skl-sst-dsp.h | 7 ++++---
sound/soc/intel/skylake/skl-sst-utils.c | 10 +++++-----
sound/soc/intel/skylake/skl-topology.c | 22 ++++------------------
4 files changed, 40 insertions(+), 26 deletions(-)
--
1.9.1
next reply other threads:[~2016-08-10 4:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-10 4:10 Vinod Koul [this message]
2016-08-10 4:10 ` [PATCH 1/3] ASoC: Intel: Skylake: modify snd_skl_get_module_info args Vinod Koul
2016-08-10 4:10 ` [PATCH 2/3] ASoC: Intel: Skylake: Populate modules after loading Vinod Koul
2016-08-10 20:04 ` Applied "ASoC: Intel: Skylake: Populate modules after loading" to the asoc tree Mark Brown
2016-08-10 4:10 ` [PATCH 3/3] ASoC: Intel: Skylake: remove module id query at runtime Vinod Koul
2016-08-10 20:04 ` Applied "ASoC: Intel: Skylake: remove module id query at runtime" to the asoc tree Mark Brown
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=1470802250-9232-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).