[alsa-devel] [RFC 0/4] ASoC DSP topology

[Mark Brown]

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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: Digital signature
URL: <http://mailman.alsa-project.org/pipermail/alsa-devel/attachments/20150421/f5a13a7f/attachment.sig>