From: Liam Girdwood <liam.r.girdwood@linux.intel.com>
To: jeeja.kp@intel.com
Cc: tiwai@suse.de, patches.audio@intel.com,
alsa-devel@alsa-project.org, broonie@kernel.org
Subject: Re: [PATCH v2 1/2] ASoC: Intel: bxtn: Store the FW/Library context at boot
Date: Thu, 12 Jan 2017 08:11:21 +0000 [thread overview]
Message-ID: <1484208681.2604.66.camel@loki> (raw)
In-Reply-To: <1484195084-24446-2-git-send-email-jeeja.kp@intel.com>
On Thu, 2017-01-12 at 09:54 +0530, jeeja.kp@intel.com wrote:
> From: Jeeja KP <jeeja.kp@intel.com>
>
> Store the DSP firmware/library at boot, so that for S3 to S0 transition
> use the stored ctx for downloading the firmware to DSP memory.
>
> Signed-off-by: Jeeja KP <jeeja.kp@intel.com>
> ---
> sound/soc/intel/skylake/bxt-sst.c | 55 +++++++++++++++++++++++++--------------
> 1 file changed, 36 insertions(+), 19 deletions(-)
>
> diff --git a/sound/soc/intel/skylake/bxt-sst.c b/sound/soc/intel/skylake/bxt-sst.c
> index 15a063a..7762d5a 100644
> --- a/sound/soc/intel/skylake/bxt-sst.c
> +++ b/sound/soc/intel/skylake/bxt-sst.c
> @@ -50,33 +50,47 @@ static unsigned int bxt_get_errorcode(struct sst_dsp *ctx)
> return sst_dsp_shim_read(ctx, BXT_ADSP_ERROR_CODE);
> }
>
> +static void sst_bxt_release_library(struct skl_lib_info *linfo, int lib_count)
> +{
> + int i;
> +
> + for (i = 1; i < lib_count; i++) {
It probably makes sense to replace 1 with a macro here to indicate the
first non base FW ID number. This can be done in other places too to
make the code more readable for library management.
Liam
next prev parent reply other threads:[~2017-01-12 8:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 4:24 [PATCH v2 0/2] ASoC: Intel: Skylake: Driver updates on DSP firmware jeeja.kp
2017-01-12 4:24 ` [PATCH v2 1/2] ASoC: Intel: bxtn: Store the FW/Library context at boot jeeja.kp
2017-01-12 8:11 ` Liam Girdwood [this message]
2017-01-12 15:11 ` Jeeja KP
2017-01-12 4:24 ` [PATCH v2 2/2] ASoC: Intel: bxtn: optimize ROM init retries jeeja.kp
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=1484208681.2604.66.camel@loki \
--to=liam.r.girdwood@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=jeeja.kp@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 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).