Em Tue, 20 Oct 2015 14:22:09 +0100 Mark Brown escreveu: > On Tue, Oct 20, 2015 at 12:55:37PM +0100, Liam Girdwood wrote: > > On Mon, 2015-10-19 at 14:46 -0600, Shuah Khan wrote: > > > > You can find the media graph that includes ALSA Mixer Function and > > > Control Interface (Device: /dev/snd/controlC2), PCM Audio Capture > > > Function and PCM Audio Capture interface (Device: /dev/snd/pcmC2D0c) > > > at: > > > > https://drive.google.com/open?id=0B0NIL0BQg-AlbjZkcElJb2RtVk0 > > > Looks nice. Fwiw, the graph will probably get a lot bigger when we show > > the audio DSP and codec paths (as DSPs and codecs have multiple muxes > > and mixers). It may be good to have a cmd line option to stop at certain > > nodes on the graph to avoid over populated/complex graphs ? > > Having the ability to describe which physical device things are part of > would probably help a lot with the rendering here - I'm guessing that a > lot of filtering is likely to be things like collapsing down devices not > being looked at right now into a single block in the graph and it'd > probably help with user comprehesibilty provide a mapping back to things > they can see in the physical world. > > This doesn't entirely correspond with struct device due to MFD and > multi-function USB stuff but it'd be a good start I expect. Yeah, collapsing devices make sense. Sakari is working on a properties API to be added to Media Controller entities/interfaces/links. Perhaps he could add this requirement to the API he's working with. Regards, Mauro