From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
To: alsa-devel@alsa-project.org
Cc: Liam Girdwood <liam.r.girdwood@linux.intel.com>,
Mark Brown <broonie@kernel.org>,
Jarkko Nikula <jarkko.nikula@linux.intel.com>,
Liam Girdwood <lgirdwood@gmail.com>
Subject: [PATCH 1/2] ASoC: Intel: Move extended fw base and size fields in struct sst_pdata
Date: Tue, 18 Feb 2014 16:42:02 +0200 [thread overview]
Message-ID: <1392734523-5109-1-git-send-email-jarkko.nikula@linux.intel.com> (raw)
Move fw_base and fw_size fields in struct sst_pdata under ACPI data for
clarifying that these are not related to firmware file but for platform
specific extended firmware area reserved by the BIOS.
Signed-off-by: Jarkko Nikula <jarkko.nikula@linux.intel.com>
Acked-by: Liam Girdwood <liam.r.girdwood@linux.intel.com>
---
sound/soc/intel/sst-dsp.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/sound/soc/intel/sst-dsp.h b/sound/soc/intel/sst-dsp.h
index 0ce5c8d91794..d134359fecac 100644
--- a/sound/soc/intel/sst-dsp.h
+++ b/sound/soc/intel/sst-dsp.h
@@ -147,12 +147,12 @@ struct sst_pdata {
u32 lpe_size;
u32 pcicfg_base;
u32 pcicfg_size;
+ u32 fw_base;
+ u32 fw_size;
int irq;
/* Firmware */
const char *fw_filename;
- u32 fw_base;
- u32 fw_size;
/* DMA */
u32 dma_base;
--
1.8.5.3
next reply other threads:[~2014-02-18 14:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-18 14:42 Jarkko Nikula [this message]
2014-02-18 14:42 ` [PATCH 2/2] ASoC: Intel: sst-acpi: Request firmware before SST platform driver probing Jarkko Nikula
2014-02-18 14:58 ` Takashi Iwai
2014-02-19 6:57 ` Jarkko Nikula
2014-02-19 7:09 ` Jarkko Nikula
2014-02-19 7:15 ` Takashi Iwai
2014-02-19 7:28 ` Jarkko Nikula
2014-02-19 4:41 ` [PATCH 1/2] ASoC: Intel: Move extended fw base and size fields in struct sst_pdata 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=1392734523-5109-1-git-send-email-jarkko.nikula@linux.intel.com \
--to=jarkko.nikula@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=liam.r.girdwood@linux.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