alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: "Singh, Guneshwor" <guneshwor.o.singh@intel.com>
To: alsa-devel@alsa-project.org, Mark Brown <broonie@kernel.org>
Cc: Takashi Iwai <tiwai@suse.de>,
	liam.r.girdwood@linux.intel.com,
	Vinod Koul <vinod.koul@intel.com>,
	Patches Audio <patches.audio@intel.com>
Subject: Re: [PATCH v3 0/4] Add debugfs support for skylake driver
Date: Thu, 29 Jun 2017 18:24:27 +0530	[thread overview]
Message-ID: <20170629125427.GA574@g2> (raw)
In-Reply-To: <20170629123608.5498-1-guneshwor.o.singh@intel.com>

On Thu, Jun 29, 2017 at 06:06:03PM +0530, Guneshwor Singh wrote:
> This series introduces debugfs support for skylake driver. It helps in
> debugging by providing module configurations which is loaded from topology.
> 
> It also allows to read the firmware registers which are a part of SRAM
> memory area accessible by host CPU through a memory window.
> 

Please ignore this, it was sent by mistake.

> Changes in v3:
> - Change debugfs parent from debugfs root to ASoC platform component
> 
> Changes in v2:
> - Re-ordered patch and squashed platform changes
> 
> Guneshwor Singh (1):
>   ASoC: Intel: Skylake: Add sram address to sst_addr structure
> 
> Sodhi, VunnyX (1):
>   ASoC: Intel: Skylake: Add support to read firmware registers
> 
> Vinod Koul (2):
>   ASoC: Intel: Skylake: Add debugfs support
>   ASoC: Intel: Skylake: Debugfs facility to dump module config
> 
>  sound/soc/intel/common/sst-dsp-priv.h  |   4 +
>  sound/soc/intel/skylake/Makefile       |   4 +
>  sound/soc/intel/skylake/bxt-sst.c      |   4 +
>  sound/soc/intel/skylake/skl-debug.c    | 268 +++++++++++++++++++++++++++++++++
>  sound/soc/intel/skylake/skl-pcm.c      |   6 +-
>  sound/soc/intel/skylake/skl-sst.c      |   5 +
>  sound/soc/intel/skylake/skl-topology.c |   3 +
>  sound/soc/intel/skylake/skl.c          |   2 +
>  sound/soc/intel/skylake/skl.h          |  26 ++++
>  9 files changed, 321 insertions(+), 1 deletion(-)
>  create mode 100644 sound/soc/intel/skylake/skl-debug.c
> 
> -- 
> 2.13.0
> 

      parent reply	other threads:[~2017-06-29 12:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-29 12:36 [PATCH v3 0/4] Add debugfs support for skylake driver Guneshwor Singh
2017-06-29 12:36 ` [PATCH v3 1/4] ASoC: Intel: Skylake: Add debugfs support Guneshwor Singh
2017-06-29 12:36 ` [PATCH v3 2/4] ASoC: Intel: Skylake: Debugfs facility to dump module config Guneshwor Singh
2017-06-29 12:36 ` [PATCH v3 3/4] ASoC: Intel: common: Add sram address to sst_addr structure Guneshwor Singh
2017-06-29 12:36 ` [PATCH v3 3/4] ASoC: Intel: Skylake: " Guneshwor Singh
2017-06-29 12:36 ` [PATCH v3 4/4] ASoC: Intel: Skylake: Add support to read firmware registers Guneshwor Singh
2017-06-30 12:29   ` Applied "ASoC: Intel: Skylake: Add support to read firmware registers" to the asoc tree Mark Brown
2017-06-29 12:54 ` Singh, Guneshwor [this message]

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=20170629125427.GA574@g2 \
    --to=guneshwor.o.singh@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=patches.audio@intel.com \
    --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).