On 10/01/2015 10:48 AM, Shuah Khan wrote:
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
Another topic:
Discuss the following patch series to Update ALSA, and au0828 drivers to use Managed Media Controller API. This patch series is based on current MC API. I am working on porting the patch series to MC next gen. Hope to have the patch series out for that in a week.
Let's discuss this to see if this work should be held off until MC next gen.
https://www.mail-archive.com/linux-media@vger.kernel.org/msg92572.html
thanks, -- Shuah