> > Hi Vinod, > Interesting thread... > From what you know, in meego, what is the audio manager vs the platform policy > manager ? Any diagram showing this? > I'm starting to work on resource manager, so I'd like to collect all the > pieces of > the puzzle, and understand exactly how all this is planned to be designed... > I also feel not really comfortable with multiple path to control audio... So > I'd > like to understand a little bit more the architecture decisions and > requirements for > such implementations. > Do you have some documentation on this? > > Also, I'm a little bit surprised by "audio manager opens intel_sst_control for > routing". On meego can you elaborate which set_target_device call you're > thinking > about, and in which use case it would be needed? > Or are you talking about a generic split between audio controls, but some of > them > are not used on meego? (So far, I don't think intel_sst_control is used) > Sylvain, The set_target_device you used earlier gets done thru intel_sst_control.
The design is all data offload goes thru intel_sst and control thru intel_sst_control. For DSP I added a new device, which based on this discussion doesn't look to be a right idea. I am going to revise this to have only two devices now. One for data offload and one for control. ~Vinod _______________________________________________ Meego-kernel mailing list [email protected] http://lists.meego.com/listinfo/meego-kernel
