Searched hist:"474 b62d6eee733abdcd36f8e3e5ce504fbb9110b" (Results 1 – 4 of 4) sorted by relevance
| /openbmc/linux/include/sound/ |
| H A D | soc-dapm.h | diff 474b62d6eee733abdcd36f8e3e5ce504fbb9110b Tue Jan 18 10:14:44 CST 2011 Mark Brown <broonie@opensource.wolfsonmicro.com> ASoC: Provide per widget type callback when executing DAPM sequences
Many modern devices have features such as DC servos which take time to start.
Currently these are handled by per-widget events but this makes it difficult
to paralleise operations on multiple widgets, meaning delays can end up
being needlessly serialised. By providing a callback to drivers when all
widgets of a given type have been handled during a DAPM sequence the core
allows drivers to start operations separately and wait for them to complete
much more simply.
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
Acked-by: Liam Girdwood <lrg@slimlogic.co.uk>
|
| H A D | soc.h | diff 474b62d6eee733abdcd36f8e3e5ce504fbb9110b Tue Jan 18 10:14:44 CST 2011 Mark Brown <broonie@opensource.wolfsonmicro.com> ASoC: Provide per widget type callback when executing DAPM sequences
Many modern devices have features such as DC servos which take time to start.
Currently these are handled by per-widget events but this makes it difficult
to paralleise operations on multiple widgets, meaning delays can end up
being needlessly serialised. By providing a callback to drivers when all
widgets of a given type have been handled during a DAPM sequence the core
allows drivers to start operations separately and wait for them to complete
much more simply.
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
Acked-by: Liam Girdwood <lrg@slimlogic.co.uk>
|
| /openbmc/linux/sound/soc/ |
| H A D | soc-dapm.c | diff 474b62d6eee733abdcd36f8e3e5ce504fbb9110b Tue Jan 18 10:14:44 CST 2011 Mark Brown <broonie@opensource.wolfsonmicro.com> ASoC: Provide per widget type callback when executing DAPM sequences
Many modern devices have features such as DC servos which take time to start.
Currently these are handled by per-widget events but this makes it difficult
to paralleise operations on multiple widgets, meaning delays can end up
being needlessly serialised. By providing a callback to drivers when all
widgets of a given type have been handled during a DAPM sequence the core
allows drivers to start operations separately and wait for them to complete
much more simply.
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
Acked-by: Liam Girdwood <lrg@slimlogic.co.uk>
|
| H A D | soc-core.c | diff 474b62d6eee733abdcd36f8e3e5ce504fbb9110b Tue Jan 18 10:14:44 CST 2011 Mark Brown <broonie@opensource.wolfsonmicro.com> ASoC: Provide per widget type callback when executing DAPM sequences
Many modern devices have features such as DC servos which take time to start.
Currently these are handled by per-widget events but this makes it difficult
to paralleise operations on multiple widgets, meaning delays can end up
being needlessly serialised. By providing a callback to drivers when all
widgets of a given type have been handled during a DAPM sequence the core
allows drivers to start operations separately and wait for them to complete
much more simply.
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
Acked-by: Liam Girdwood <lrg@slimlogic.co.uk>
|