On 03/10/2014 09:13 AM, Peter Ujfalusi wrote:
Hi,
On 03/08/2014 08:16 PM, Lars-Peter Clausen wrote:
When using table based DAPM setup there is no need to register DAPM elements for different sub-components separately. The widgets will be registered before the first sub-component is initialized, the routes are only added after the last sub-component has been initialized, meaning everything will be available when it is needed.
The reason why we add the DMIC routes in the way we do is that not all boards have DMIC in use. PandaBoards does not have DMIC while SDP/Blaze have. On PandaBoard we do not register the dmic dai link so the widgets are not going to be added and also the dmic DAI and codec will be not loaded on PandaBoards. I think this will cause some warning because of missing "DMic" widget?
Hm, ok, missed that part. Makes sense. I'll respin the patch to just use the card's DAPM context when registering the DMIC DAPM routes.
- Lars