All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: Guneshwor Singh <guneshwor.o.singh@intel.com>
Cc: Takashi Iwai <tiwai@suse.de>,
	liam.r.girdwood@linux.intel.com, alsa-devel@alsa-project.org,
	Mark Brown <broonie@kernel.org>,
	Patches Audio <patches.audio@intel.com>
Subject: Re: [PATCH 4/5] ASoC: Intel: bxtn: Assign sram address to sst structure
Date: Thu, 29 Jun 2017 11:25:30 +0530	[thread overview]
Message-ID: <20170629055530.GF19154@localhost> (raw)
In-Reply-To: <20170629030408.4383-5-guneshwor.o.singh@intel.com>

On Thu, Jun 29, 2017 at 08:34:07AM +0530, Guneshwor Singh wrote:
> To read dsp registers via debugfs, assign sram address
> in dsp_init().
> 
> Signed-off-by: Guneshwor Singh <guneshwor.o.singh@intel.com>
> ---
>  sound/soc/intel/skylake/bxt-sst.c | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/sound/soc/intel/skylake/bxt-sst.c b/sound/soc/intel/skylake/bxt-sst.c
> index f5e7dbb1ba39..cf11b84888b9 100644
> --- a/sound/soc/intel/skylake/bxt-sst.c
> +++ b/sound/soc/intel/skylake/bxt-sst.c
> @@ -573,6 +573,10 @@ int bxt_sst_dsp_init(struct device *dev, void __iomem *mmio_base, int irq,
>  	sst->fw_ops = bxt_fw_ops;
>  	sst->addr.lpe = mmio_base;
>  	sst->addr.shim = mmio_base;
> +	sst->addr.sram0_base = BXT_ADSP_SRAM0_BASE;
> +	sst->addr.sram1_base = BXT_ADSP_SRAM1_BASE;
> +	sst->addr.w0_stat_sz = SKL_ADSP_W0_STAT_SZ;
> +	sst->addr.w0_up_sz = SKL_ADSP_W0_UP_SZ;

I think you need to modfiy the order and this and following change. With
last patch applied and this not present, you would break if someone tries to
read debugfs file as these adresses are NULL, so add these values first and
then the usage :)

>  
>  	sst_dsp_mailbox_init(sst, (BXT_ADSP_SRAM0_BASE + SKL_ADSP_W0_STAT_SZ),
>  			SKL_ADSP_W0_UP_SZ, BXT_ADSP_SRAM1_BASE, SKL_ADSP_W1_SZ);
> -- 
> 2.13.0
> 

-- 
~Vinod

  reply	other threads:[~2017-06-29  5:52 UTC|newest]

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

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=20170629055530.GF19154@localhost \
    --to=vinod.koul@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=guneshwor.o.singh@intel.com \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=patches.audio@intel.com \
    --cc=tiwai@suse.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.