[Meego-kernel] [PATCH] Audio: Add ioctl interface for sending algorithm parameters

[Centelles, Sylvain]

> GST plugin opens intel_sst device for sound offload. The audio manager opens
> intel_sst_control for routing  and the platform policy manager will need to
> open
> this new device for algorithms.

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

> 
> Thanks
> ~Vinod
> _______________________________________________
> Meego-kernel mailing list
> Meego-kernel at lists.meego.com
> http://lists.meego.com/listinfo/meego-kernel
---------------------------------------------------------------------
Intel Corporation SAS (French simplified joint stock company)
Registered headquarters: "Les Montalets"- 2, rue de Paris, 
92196 Meudon Cedex, France
Registration Number:  302 456 199 R.C.S. NANTERRE
Capital: 4,572,000 Euros

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.