On 10/02/2015 05:06 AM, Mauro Carvalho Chehab wrote:
Em Thu, 01 Oct 2015 16:43:21 -0600 Shuah Khan shuahkh@osg.samsung.com escreveu:
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
Why?
Maybe it is not necessary and my ALSA MC patch series and ALSA MC next gen will get reviewed before the summit.
What's exactly your proposal for the userspace API? Will that change after MC next gen?
It has no bearing on userspace API. I should have elaborated what is on my mind better. My question is related to:
1. The scope and the effort involved on my part. i.e if ALSA MC goes in first, ALSA MC next gen patches will change to just the ports to account for new API. 2. Would it make sense to introduce this feature now without coupling it to MC next gen. Pros and cons for both.
My intent is to run this by the maintainers and sub-system maintainers at this summit. If this topic isn't appropriate for the summit, then I withdraw my proposal for this topic.
thanks, -- Shuah