8 Apr
2011
8 Apr
'11
7:13 p.m.
On Wed, 2011-04-06 at 11:38 +0900, Mark Brown wrote:
The DAPM pin operations currently require that the specific DAPM context that the pin being operated in is contained in be specified. With multi component and especially with the addition of a per-card DAPM context this isn't ideal as it means that things like disabling unused pins on CODECs require looking up the CODEC DAPM context.
Fix this by falling back to matching a widget in any context if there isn't a match in the current context. The code isn't ideal currently but will do the job.
Signed-off-by: Mark Brown broonie@opensource.wolfsonmicro.com
Acked-by: Liam Girdwood lrg@ti.com