From: Mark Brown <broonie@kernel.org>
To: Liam Girdwood <liam.r.girdwood@linux.intel.com>
Cc: "Koul, Vinod" <vinod.koul@intel.com>,
alsa-devel@alsa-project.org,
Jarkko Nikula <jarkko.nikula@linux.intel.com>,
Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [PATCHv2] ASoC: Intel: sst-acpi: Request firmware before SST platform driver probing
Date: Wed, 19 Feb 2014 23:14:45 +0900 [thread overview]
Message-ID: <20140219141445.GC2669@sirena.org.uk> (raw)
In-Reply-To: <1392817832.2351.51.camel@loki>
[-- Attachment #1.1: Type: text/plain, Size: 1047 bytes --]
On Wed, Feb 19, 2014 at 01:50:32PM +0000, Liam Girdwood wrote:
> On Wed, 2014-02-19 at 21:25 +0900, Mark Brown wrote:
> > The more usual thing to do here is to only request the firmware when the
> > device is actually being used (in this case on open). This also allows
> > the firmware to be replaced easily at runtime which is helpful too. It
> > seems like this is still an improvement though so I've applied it.
> Fwiw, we need to load the FW at probe time since it will contain the FW
> topology for the SST drivers. The next phase for the SST FW is to use
> the ASoC firmware loader for DAPM, Kcontrols + DAI links (Vinod is
> working on patch for DAI links iirc, I will be back to the fw loader
> next week if all goes to plan). The good news is that the ASoC FW loader
> can also unload FW so we should be able to re-load FW at runtime too :)
I had thought the firmware loader would be able to cope with the
firmware getting loaded and unloaded at runtime, several of the
potential users actively want to be able to switch firmwares?
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2014-02-19 14:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-19 8:30 [PATCHv2] ASoC: Intel: sst-acpi: Request firmware before SST platform driver probing Jarkko Nikula
2014-02-19 12:25 ` Mark Brown
2014-02-19 13:50 ` Liam Girdwood
2014-02-19 14:14 ` Mark Brown [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=20140219141445.GC2669@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=jarkko.nikula@linux.intel.com \
--cc=lgirdwood@gmail.com \
--cc=liam.r.girdwood@linux.intel.com \
--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