(Resend including list as well) <div class="gmail_quote">On 17 Feb 2014 09:30, "Arun Raghavan" <<a href="mailto:arun@accosted.net">arun@accosted.net</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> On 16 February 2014 16:33, Tanu Kaskinen <<a href="mailto:tanu.kaskinen@linux.intel.com">tanu.kaskinen@linux.intel.com</a>> wrote: [...] > Yes, I can and I will start the implementation from the volume control > objects, but let's not stop the discussion about volume classes / audio > groups, because I will need to implement a client API for working with > volume classes anyway. The sooner I know how to do it, the better. We have 3 orthogonal issues here: 1. Addition of volume control objects / information to allow balance to be represented adequately 2. Creation and control of volume classes 3. Adding a "main volume" concept I suggest we discuss each in a separate thread to keep the discussion manageable. Right now, I'll address the first, viz. volume control objects. I'm not completely clear what you're trying to achieve with volume control objects right now - are you just trying to fix the balance problem, or ...? I see the point you're making about the potential applicability of associating multiple volume controls with a single device, but I'd like to understand what you'll be solving with the patch set you'd be submitting with this infrastructure. Mainly, I ask this because I don't want to add infrastructure and especially public API for features we don't have yet and don't seem to have a clear path for either (namely controlling equalizer, AGC, and other such parameters) Cheers, Arun </blockquote></div>