I would like to add the following topics for discussion at the upcoming Media Workshop
- ENT_F_IO appears to be too generic, requiring additional steps to determine what kind of IO function it is really is. I propose preserving and allowing enough uniqueness to enable drivers to tag the functions when they create them. For example, if AUDIO functions are all tagged ENT_F_IO, bridge driver has to determine what kind of IO it really is. This requires finding the Interface entity associated with the function entity or comparing entity name strings. Instead, if a function can be tagged as Audio Capture when it gets created, these additional steps aren't necessary.
- Discuss snd-usb-audio control interface mapping to media. snd-usb-audio creates a control device file which could be exposed in a media graph. In some cases, it is a simple mixer control. Expose ENT_F_MIXER entity with an associated interface node MEDIA_INTF_T_ALSA_CONTROL
thanks, -- Shuah