From: Mark Brown <broonie@kernel.org>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: Liam Girdwood <liam.r.girdwood@linux.intel.com>,
Takashi Iwai <tiwai@suse.de>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"Koul, Vinod" <vinod.koul@intel.com>
Subject: Re: [RFC 0/4] ASoC DSP topology
Date: Tue, 21 Apr 2015 10:28:12 +0100 [thread overview]
Message-ID: <20150421092812.GA22845@sirena.org.uk> (raw)
In-Reply-To: <5535F513.8030902@ti.com>
[-- Attachment #1.1: Type: text/plain, Size: 901 bytes --]
On Tue, Apr 21, 2015 at 09:58:27AM +0300, Peter Ujfalusi wrote:
> It is not entirely clear for me based on the first look, but who is
> responsible to initiate the topology load? Is it the component or machine
> driver? We have had issues with deferred probing when the component driver was
> in charge of loading the firmware. I got around this by initiating the FW load
> from the machine driver and via callbacks I notified the component driver to
> take over from that point. This fixed the probe order and I can also handle
> cases when the filesystem does not have the firmware so I can fall back to
> 'legacy' mode.
Could you expand on those issues please? I'd *really* not expect the
machine driver to be involved in loading firmware for a component driver
(think how this is going to affect generic drivers) and it's not obvious
to me what impact this might have on deferred probe either.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2015-04-21 9:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-16 20:48 [RFC 0/4] ASoC DSP topology Liam Girdwood
2015-04-20 21:40 ` Mark Brown
2015-04-21 6:58 ` Peter Ujfalusi
2015-04-21 9:28 ` Mark Brown [this message]
2015-04-21 10:03 ` Liam Girdwood
2015-04-21 12:30 ` Peter Ujfalusi
2015-04-21 15:23 ` Liam Girdwood
2015-04-21 16:39 ` Mark Brown
2015-04-22 4:10 ` Vinod Koul
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=20150421092812.GA22845@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=liam.r.girdwood@linux.intel.com \
--cc=peter.ujfalusi@ti.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