From: Sriram Periyasamy <sriramx.periyasamy@intel.com>
To: ALSA ML <alsa-devel@alsa-project.org>, Mark Brown <broonie@kernel.org>
Cc: Takashi Iwai <tiwai@suse.de>,
Sriram Periyasamy <sriramx.periyasamy@intel.com>,
mturquette@baylibre.com, sboyd@codeaurora.org,
Patches Audio <patches.audio@intel.com>,
Liam Girdwood <liam.r.girdwood@linux.intel.com>,
Vinod Koul <vinod.koul@intel.com>,
linux-clk@vger.kernel.org
Subject: [PATCH v8 0/3] ASoC: Intel: Skylake: Add a clk driver to enable ssp clks early
Date: Mon, 29 Jan 2018 21:45:57 +0530 [thread overview]
Message-ID: <1517242560-22157-1-git-send-email-sriramx.periyasamy@intel.com> (raw)
Clock driver patches have been applied. These remaining patches are rebased
on "topic/intel". The first patch enables the mclk and ssp sclk early for
eve machine driver and the remaining two patches are effort to add more
meaning to the DSP replies for easy debugging.
Naveen M (1):
ASoC: Intel: eve: Enable mclk and ssp sclk early
Subhransu S. Prusty (2):
ASoC: Intel: Skylake: Make DSP replies more human readable
ASoC: Intel: Skylake: Add FW reply for MCLK/SCLK IPC
sound/soc/intel/boards/Kconfig | 1 +
.../soc/intel/boards/kbl_rt5663_rt5514_max98927.c | 94 ++++++++++++++++++++++
sound/soc/intel/skylake/skl-sst-ipc.c | 50 +++++++++---
3 files changed, 134 insertions(+), 11 deletions(-)
--
2.7.4
next reply other threads:[~2018-01-29 16:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-29 16:15 Sriram Periyasamy [this message]
2018-01-29 16:15 ` [alsa-devel] [PATCH v8 1/3] ASoC: Intel: eve: Enable mclk and ssp sclk early Sriram Periyasamy
2018-01-29 16:15 ` [alsa-devel] [PATCH v8 2/3] ASoC: Intel: Skylake: Make DSP replies more human readable Sriram Periyasamy
2018-01-29 16:16 ` [alsa-devel] [PATCH v8 3/3] ASoC: Intel: Skylake: Add FW reply for MCLK/SCLK IPC Sriram Periyasamy
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=1517242560-22157-1-git-send-email-sriramx.periyasamy@intel.com \
--to=sriramx.periyasamy@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=liam.r.girdwood@linux.intel.com \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=patches.audio@intel.com \
--cc=sboyd@codeaurora.org \
--cc=tiwai@suse.de \
--cc=vinod.koul@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).