On Thu, Jan 30, 2020 at 2:03 PM Peter Ujfalusi <peter.ujfalusi@xxxxxx> wrote: > > Hi Daniel, > > On 28/01/2020 17.14, Daniel Baluta wrote: > > Hi Peter, > > > > Liam mentioned that at some point (when working for OMAP) > > you might have had the same challenge I'm facing now. > > Sorry for the delay... > > > I'm trying to figure out how to properly manage resources needed by > > the IPs configured > > by DSP. > > > > On i.MX8 we the following scenario: > > > > - Application processor (arm64) exposes an ALSA sound card to applications > > - DSP (Hifi4) does the processing > > > > DSP has direct access to DAI registers but it doesn't have (easily) > > access to other resources > > like: pinctrl, power-domain, clocks, etc. > > > > I was wondering how did you tackled this for OMAP? > > It is (was, as the AESS/ABE support is not upstream) bit different. > From the audio backend we do not touch the DAI registers, all setup is > done on the Linux side and the AESS 'only' managing the data flow. > > So the back-ends are the DAIs and they are managed by Linux, the > front-end is AESS. DAIs are configured by fixing up the hw_params for > them in the AESS (front-end) stack, so they are configured correctly for > the use case. I see. Thanks! _______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
