Re: [PATCH 1/3] ASoC: omap-abe-twl6040: No need to register DMIC routes seperatly

[Mark Brown <broonie@kernel.org>]

[-- Attachment #1.1: Type: text/plain, Size: 1144 bytes --]

On Mon, Mar 10, 2014 at 10:24:49AM +0100, Lars-Peter Clausen wrote:
> On 03/10/2014 10:12 AM, Mark Brown wrote:

> >In general anything keying this stuff off DT is going to have that sort
> >of thing going on - most if not all of the things that are registering
> >in several chunks are doing so because some of it is conditional.

> Before we had the support for card table based setup you'd had to
> register them in chunks, because the components became available one
> after another and you couldn't register DAPM elements for one
> component in the callback of another one. When using the table based
> setup the widgets are registered before all components are
> registered and the routes are registered after all the components
> have been registered.

No, that's not the case at all - what makes you think that's the case?
All table based setup did was move things from code to data, I'm not
sure what you mean by registering DAPM elements from one component in
the callback for another.  The only thing that should be registering
things for other components is the card and the general idea was to
register everything in late_probe().

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]