On Mon, Jun 23, 2014 at 10:04:05AM +0530, Vinod Koul wrote:
On Sun, Jun 22, 2014 at 11:12:36AM +0100, Mark Brown wrote:
Please be more specific about this - what do they offer that runtime PM and widgets don't offer?
Well you are assuming that folks writing DSP FW will not have some wiered sequence!
Neverthless, i can think of two scenarios to control fw loading and sequences:
- DMICs attached to DSP doing record but data getting consumed by DSP. No data
goes to host cpu. No PCM/parameters here, so we can do a simple Input-Output loop. Somthing reverse of what we can do with Codec vibra. Widgets will not tell me when to load DSP FW. Since no device handle, no runtime here!
Why not? If there's a DAPM context there must be a struct device for it and if there's an audio path there should be widgets on it.
- SoC DSP generating clock for codec and audio ICs even when no data is
generated by SoC. This is not true for I2S but for other bus prtocols like Slimbus.
This sounds like something runtime PM would work fine for?