On Thu, Mar 12, 2020 at 05:51:59AM -0500, Pierre-Louis Bossart wrote:
On 3/12/20 4:52 AM, Guennadi Liakhovetski wrote:
This makes DPCM runtime update functions available for external calling. As an example, virtualised ASoC component drivers may need to call these when managing shared DAPM routes that are used by more than one driver (i.e. when host driver and guest drivers have a DAPM path from guest PCM to host DAI where some parts are owned by host driver and others by guest driver).
My understanding of Mark's feedback was to avoid exposing DPCM functions to other subsystems, since there's a long-term desire to move to a different domain-based handling instead of the existing FE/BE split.
While we have it I can see that some individual driver might need to fiddle about with it though, after all a big problem currently is that the abstraction isn't terribly abstract.