Re: [Workshop-2011] Media summit/KS-2012 proposals
Hi Hans, On Wednesday 05 September 2012 10:28:30 Hans Verkuil wrote: On Wed 5 September 2012 10:04:41 Jun Nie wrote: Is there any summary for this summit or presentation material? I am looking forward for some idea on CEC. It is really complex in functionality. Maybe other guys is expecting simiar fruite from summit too. Yes, there will be a summit report. It's not quite finished yet, I think. With respect to CEC we had some useful discussions. It will have to be a new class of device (/dev/cecX), so the userspace API will be separate from drm or v4l. This is a repeat of a comment from the KS discussion: what about using the socket API instead of a device node ? And the kernel will have to take care of the core CEC protocol w.r.t. control and discovery due to the HDMI 1.4a requirements. I plan on starting work on this within 1-2 weeks. My CEC presentation can be found here: http://hverkuil.home.xs4all.nl/presentations/v4l2-workshop-cec.odp -- Regards, Laurent Pinchart -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [Workshop-2011] Media summit/KS-2012 proposals
On Thu 13 September 2012 03:01:34 Laurent Pinchart wrote: Hi Hans, On Wednesday 05 September 2012 10:28:30 Hans Verkuil wrote: On Wed 5 September 2012 10:04:41 Jun Nie wrote: Is there any summary for this summit or presentation material? I am looking forward for some idea on CEC. It is really complex in functionality. Maybe other guys is expecting simiar fruite from summit too. Yes, there will be a summit report. It's not quite finished yet, I think. With respect to CEC we had some useful discussions. It will have to be a new class of device (/dev/cecX), so the userspace API will be separate from drm or v4l. This is a repeat of a comment from the KS discussion: what about using the socket API instead of a device node ? What benefit would that give me? I frankly don't think it maps that well to a socket API. Some parts of the CEC protocol are more or less network like, but others are point-to-point. Basically CEC is a mess, protocol-wise, and I much prefer a char-device where you have more flexibility. Regards, Hans And the kernel will have to take care of the core CEC protocol w.r.t. control and discovery due to the HDMI 1.4a requirements. I plan on starting work on this within 1-2 weeks. My CEC presentation can be found here: http://hverkuil.home.xs4all.nl/presentations/v4l2-workshop-cec.odp -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [Workshop-2011] Media summit/KS-2012 proposals
On Thu September 6 2012 06:09:44 Jun Nie wrote: 2012/9/5 Hans Verkuil hverk...@xs4all.nl: On Wed 5 September 2012 10:04:41 Jun Nie wrote: Is there any summary for this summit or presentation material? I am looking forward for some idea on CEC. It is really complex in functionality. Maybe other guys is expecting simiar fruite from summit too. Yes, there will be a summit report. It's not quite finished yet, I think. With respect to CEC we had some useful discussions. It will have to be a new class of device (/dev/cecX), so the userspace API will be separate from drm or v4l. And the kernel will have to take care of the core CEC protocol w.r.t. control and discovery due to the HDMI 1.4a requirements. I plan on starting work on this within 1-2 weeks. My CEC presentation can be found here: http://hverkuil.home.xs4all.nl/presentations/v4l2-workshop-cec.odp Regards, Hans Thanks for quick response! It's good to know that CEC is independent with DRM/V4L for my HDMI implementation is FB/lcd-device based. CEC is also deserved to have independent management in both hardware signal and functionality. Someone also expressed similar thoughts before. Will remote control protocal parsing are done in userspace reference library? Or not decided yet? Are you referring to the remote control pass-through functionality? I don't know yet whether that will go through a userspace library or through the RC kernel subsystem, or possibly both. Most of the other non-system messages will go to a userspace library. But I haven't started coding yet, so it is very early days :-) The main thing is that at least I now have a high-level design that I can start to work with. Regards, Hans -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [Workshop-2011] Media summit/KS-2012 proposals
2012/9/6 Hans Verkuil hverk...@xs4all.nl: On Thu September 6 2012 06:09:44 Jun Nie wrote: 2012/9/5 Hans Verkuil hverk...@xs4all.nl: On Wed 5 September 2012 10:04:41 Jun Nie wrote: Is there any summary for this summit or presentation material? I am looking forward for some idea on CEC. It is really complex in functionality. Maybe other guys is expecting simiar fruite from summit too. Yes, there will be a summit report. It's not quite finished yet, I think. With respect to CEC we had some useful discussions. It will have to be a new class of device (/dev/cecX), so the userspace API will be separate from drm or v4l. And the kernel will have to take care of the core CEC protocol w.r.t. control and discovery due to the HDMI 1.4a requirements. I plan on starting work on this within 1-2 weeks. My CEC presentation can be found here: http://hverkuil.home.xs4all.nl/presentations/v4l2-workshop-cec.odp Regards, Hans Thanks for quick response! It's good to know that CEC is independent with DRM/V4L for my HDMI implementation is FB/lcd-device based. CEC is also deserved to have independent management in both hardware signal and functionality. Someone also expressed similar thoughts before. Will remote control protocal parsing are done in userspace reference library? Or not decided yet? Are you referring to the remote control pass-through functionality? I don't know yet whether that will go through a userspace library or through the RC kernel subsystem, or possibly both. I mean all the feature that can involved in handhold remote control, one touch play, standby, on screen display, etc, such as play/pause/poweroff. I want to mention all non CDC features that can be implemented in user space. They are hard to be covered by any sub-system and user space library is more proper. Just like your metaphor, kitchen sink for CEC. I like your words. Most of the other non-system messages will go to a userspace library. Does routing/address is included in system message here? But I haven't started coding yet, so it is very early days :-) The main thing is that at least I now have a high-level design that I can start to work with. Regards, Hans -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [Workshop-2011] Media summit/KS-2012 proposals
On Thu 6 September 2012 12:29:17 Jun Nie wrote: 2012/9/6 Hans Verkuil hverk...@xs4all.nl: On Thu September 6 2012 06:09:44 Jun Nie wrote: 2012/9/5 Hans Verkuil hverk...@xs4all.nl: On Wed 5 September 2012 10:04:41 Jun Nie wrote: Is there any summary for this summit or presentation material? I am looking forward for some idea on CEC. It is really complex in functionality. Maybe other guys is expecting simiar fruite from summit too. Yes, there will be a summit report. It's not quite finished yet, I think. With respect to CEC we had some useful discussions. It will have to be a new class of device (/dev/cecX), so the userspace API will be separate from drm or v4l. And the kernel will have to take care of the core CEC protocol w.r.t. control and discovery due to the HDMI 1.4a requirements. I plan on starting work on this within 1-2 weeks. My CEC presentation can be found here: http://hverkuil.home.xs4all.nl/presentations/v4l2-workshop-cec.odp Regards, Hans Thanks for quick response! It's good to know that CEC is independent with DRM/V4L for my HDMI implementation is FB/lcd-device based. CEC is also deserved to have independent management in both hardware signal and functionality. Someone also expressed similar thoughts before. Will remote control protocal parsing are done in userspace reference library? Or not decided yet? Are you referring to the remote control pass-through functionality? I don't know yet whether that will go through a userspace library or through the RC kernel subsystem, or possibly both. I mean all the feature that can involved in handhold remote control, one touch play, standby, on screen display, etc, such as play/pause/poweroff. I want to mention all non CDC features that can be implemented in user space. They are hard to be covered by any sub-system and user space library is more proper. Just like your metaphor, kitchen sink for CEC. I like your words. Yes, that will all be userspace. My plan is to have the CEC adapter driver handle the core CEC protocol, allow other drivers to intercept messages that are relevant for them and send messages themselves, and anything that remains will be available to userspace for which a new library will be created. Now, don't ask me about any of the details, since I don't have them yet :-) My plan is to start working on this next week or the week after. Are you willing to test early versions of this work? Can you test HDMI 1.4a features as well? Testing this might well be one of the harder things to do. Regards, Hans -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [Workshop-2011] Media summit/KS-2012 proposals
2012/9/6 Hans Verkuil hverk...@xs4all.nl: On Thu 6 September 2012 12:29:17 Jun Nie wrote: 2012/9/6 Hans Verkuil hverk...@xs4all.nl: On Thu September 6 2012 06:09:44 Jun Nie wrote: 2012/9/5 Hans Verkuil hverk...@xs4all.nl: On Wed 5 September 2012 10:04:41 Jun Nie wrote: Is there any summary for this summit or presentation material? I am looking forward for some idea on CEC. It is really complex in functionality. Maybe other guys is expecting simiar fruite from summit too. Yes, there will be a summit report. It's not quite finished yet, I think. With respect to CEC we had some useful discussions. It will have to be a new class of device (/dev/cecX), so the userspace API will be separate from drm or v4l. And the kernel will have to take care of the core CEC protocol w.r.t. control and discovery due to the HDMI 1.4a requirements. I plan on starting work on this within 1-2 weeks. My CEC presentation can be found here: http://hverkuil.home.xs4all.nl/presentations/v4l2-workshop-cec.odp Regards, Hans Thanks for quick response! It's good to know that CEC is independent with DRM/V4L for my HDMI implementation is FB/lcd-device based. CEC is also deserved to have independent management in both hardware signal and functionality. Someone also expressed similar thoughts before. Will remote control protocal parsing are done in userspace reference library? Or not decided yet? Are you referring to the remote control pass-through functionality? I don't know yet whether that will go through a userspace library or through the RC kernel subsystem, or possibly both. I mean all the feature that can involved in handhold remote control, one touch play, standby, on screen display, etc, such as play/pause/poweroff. I want to mention all non CDC features that can be implemented in user space. They are hard to be covered by any sub-system and user space library is more proper. Just like your metaphor, kitchen sink for CEC. I like your words. Yes, that will all be userspace. My plan is to have the CEC adapter driver handle the core CEC protocol, allow other drivers to intercept messages that are relevant for them and send messages themselves, and anything that remains will be available to userspace for which a new library will be created. Now, don't ask me about any of the details, since I don't have them yet :-) My plan is to start working on this next week or the week after. Are you willing to test early versions of this work? Can you test HDMI 1.4a features as well? Testing this might well be one of the harder things to do. I am willing to test or contribute to the library. But my hardware does not include HEAC. So my test scope limites to the features that can be implemented in user space. Regards, Hans -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [Workshop-2011] Media summit/KS-2012 proposals
Is there any summary for this summit or presentation material? I am looking forward for some idea on CEC. It is really complex in functionality. Maybe other guys is expecting simiar fruite from summit too. B.R. Jun -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [Workshop-2011] Media summit/KS-2012 proposals
On Wed 5 September 2012 10:04:41 Jun Nie wrote: Is there any summary for this summit or presentation material? I am looking forward for some idea on CEC. It is really complex in functionality. Maybe other guys is expecting simiar fruite from summit too. Yes, there will be a summit report. It's not quite finished yet, I think. With respect to CEC we had some useful discussions. It will have to be a new class of device (/dev/cecX), so the userspace API will be separate from drm or v4l. And the kernel will have to take care of the core CEC protocol w.r.t. control and discovery due to the HDMI 1.4a requirements. I plan on starting work on this within 1-2 weeks. My CEC presentation can be found here: http://hverkuil.home.xs4all.nl/presentations/v4l2-workshop-cec.odp Regards, Hans -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [Workshop-2011] Media summit/KS-2012 proposals
2012/9/5 Hans Verkuil hverk...@xs4all.nl: On Wed 5 September 2012 10:04:41 Jun Nie wrote: Is there any summary for this summit or presentation material? I am looking forward for some idea on CEC. It is really complex in functionality. Maybe other guys is expecting simiar fruite from summit too. Yes, there will be a summit report. It's not quite finished yet, I think. With respect to CEC we had some useful discussions. It will have to be a new class of device (/dev/cecX), so the userspace API will be separate from drm or v4l. And the kernel will have to take care of the core CEC protocol w.r.t. control and discovery due to the HDMI 1.4a requirements. I plan on starting work on this within 1-2 weeks. My CEC presentation can be found here: http://hverkuil.home.xs4all.nl/presentations/v4l2-workshop-cec.odp Regards, Hans Thanks for quick response! It's good to know that CEC is independent with DRM/V4L for my HDMI implementation is FB/lcd-device based. CEC is also deserved to have independent management in both hardware signal and functionality. Someone also expressed similar thoughts before. Will remote control protocal parsing are done in userspace reference library? Or not decided yet? B.R. Jun -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [Workshop-2011] Media summit/KS-2012 proposals
2012/8/3 Hans Verkuil hverk...@xs4all.nl: On Fri August 3 2012 07:37:13 Jun Nie wrote: 2012/8/1 Hans Verkuil hverk...@xs4all.nl: On Tue 31 July 2012 19:58:23 Mauro Carvalho Chehab wrote: In order to sum-up the discussions around the media summit, this is what we've got so far: Proposals proposed by =|= Common device tree bindings for media devices Sylvester Nawrocki / Guennadi Liakhovetski ALSA and V4L/Media Controller Steven Toth / Laurent Pinchart ARM and needed features for V4L/DVB Steven Toth Intel media SDK Steven Toth V4L compiance tool Hans Verkuil V4L2 API ambiguities Hans Verkuil Media Controller library Laurent Pincart / Sakari Ailus SoC Vendors feedback – how to help them to go upstream – Android's V4L2 cam library Laurent Pincart / Guennadi Liakhovetski / Palash Bandyopadhyay / Naveen Krishnamurthy Synchronization, shared resource and optimizations Pawel Osciak V4L2/DVB issues from userspace perspective Rémi Denis-Courmont As we'll have only one day for the summit, we may need to remove some themes, or maybe to get an extra time during LPC for the remaining discussions. Possible attendents: === Guennadi Liakhovetski Laurent Pinchart Mauro Carvalho Chehab Michael Krufky Naveen Krishnamurthy +1 seat from ST (waiting Naveen to define who will be the other seat) Palash Bandyopadhyay Pawel Osciak Rémi Denis-Courmont Sakari Ailus Steven Toth Sylvester Nawrocki Am I missing something? Are there other proposals or people intending to participate? Yes: I would like to discuss how to add support for HDMI CEC to the kernel. In particularly I need some feedback from the GPU driver developers on what their ideas are, since CEC is something that touches both V4L2 and GPU. I am not familiar with CEC implementation in GPU. As far as I am aware there isn't any. But CEC should be independent in functionality with audio/video though it is A/V related. I prefer to support only CEC frame TX/RX in kernel. CEC include different category features that need parsing and may need application interaction. Venders may also configure some features as not supported. If kernel support more than TX/RX, policy may be separated to user space part and kernel space part. The kernel interface also becomes complex, maybe ambiguous too. An user space library is more suitable for this task to interact with OS/media player/audio control/etc. I wish that were possible. Our current implementation internally is as you proposed, but we recently discovered that for HDMI 1.4a this won't fly. There the CEC channel is also used for control of the ethernet and audio return channel, and even for hotplug detect in some cases. That's something that has to be handled entirely in kernelspace. So some parts of the CEC protocol have to be internally processed, other parts have to be processed in userspace. Thanks for your reminder. I was not aware of HEAC/ARC dependence on CEC for our product does not include these features. Maybe we can parse CDC CEC message in kernel and leave others to user space. But it is also an ugly propose. BTW: Do you see any scenario that EDID is changed dynamically? I do not know why to add hot-plug to CEC control while no physical HPD changes. This really complicates things and it makes it even more important that the subsystems that need CEC work together on this. Regards, Hans -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [Workshop-2011] Media summit/KS-2012 proposals
On Mon August 6 2012 15:22:38 Jun Nie wrote: 2012/8/3 Hans Verkuil hverk...@xs4all.nl: On Fri August 3 2012 07:37:13 Jun Nie wrote: 2012/8/1 Hans Verkuil hverk...@xs4all.nl: On Tue 31 July 2012 19:58:23 Mauro Carvalho Chehab wrote: In order to sum-up the discussions around the media summit, this is what we've got so far: Proposals proposed by =|= Common device tree bindings for media devices Sylvester Nawrocki / Guennadi Liakhovetski ALSA and V4L/Media Controller Steven Toth / Laurent Pinchart ARM and needed features for V4L/DVB Steven Toth Intel media SDK Steven Toth V4L compiance tool Hans Verkuil V4L2 API ambiguities Hans Verkuil Media Controller library Laurent Pincart / Sakari Ailus SoC Vendors feedback – how to help them to go upstream – Android's V4L2 cam library Laurent Pincart / Guennadi Liakhovetski / Palash Bandyopadhyay / Naveen Krishnamurthy Synchronization, shared resource and optimizations Pawel Osciak V4L2/DVB issues from userspace perspective Rémi Denis-Courmont As we'll have only one day for the summit, we may need to remove some themes, or maybe to get an extra time during LPC for the remaining discussions. Possible attendents: === Guennadi Liakhovetski Laurent Pinchart Mauro Carvalho Chehab Michael Krufky Naveen Krishnamurthy +1 seat from ST (waiting Naveen to define who will be the other seat) Palash Bandyopadhyay Pawel Osciak Rémi Denis-Courmont Sakari Ailus Steven Toth Sylvester Nawrocki Am I missing something? Are there other proposals or people intending to participate? Yes: I would like to discuss how to add support for HDMI CEC to the kernel. In particularly I need some feedback from the GPU driver developers on what their ideas are, since CEC is something that touches both V4L2 and GPU. I am not familiar with CEC implementation in GPU. As far as I am aware there isn't any. But CEC should be independent in functionality with audio/video though it is A/V related. I prefer to support only CEC frame TX/RX in kernel. CEC include different category features that need parsing and may need application interaction. Venders may also configure some features as not supported. If kernel support more than TX/RX, policy may be separated to user space part and kernel space part. The kernel interface also becomes complex, maybe ambiguous too. An user space library is more suitable for this task to interact with OS/media player/audio control/etc. I wish that were possible. Our current implementation internally is as you proposed, but we recently discovered that for HDMI 1.4a this won't fly. There the CEC channel is also used for control of the ethernet and audio return channel, and even for hotplug detect in some cases. That's something that has to be handled entirely in kernelspace. So some parts of the CEC protocol have to be internally processed, other parts have to be processed in userspace. Thanks for your reminder. I was not aware of HEAC/ARC dependence on CEC for our product does not include these features. Maybe we can parse CDC CEC message in kernel and leave others to user space. But it is also an ugly propose. BTW: Do you see any scenario that EDID is changed dynamically? I do not know why to add hot-plug to CEC control while no physical HPD changes. Switching between an EDID for analog or digital input when using a DVI-I cable is the most common use-case that I know of. But this does not apply as such to an HDMI connector since that's digital only. Another might be that a simple EDID is setup when the device boots, and once it is booted and all the features of the device are known a more advanced EDID might be written. I'm sure that there are more creative uses as well... Regards, Hans -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [Workshop-2011] Media summit/KS-2012 proposals
On Fri August 3 2012 07:37:13 Jun Nie wrote: 2012/8/1 Hans Verkuil hverk...@xs4all.nl: On Tue 31 July 2012 19:58:23 Mauro Carvalho Chehab wrote: In order to sum-up the discussions around the media summit, this is what we've got so far: Proposals proposed by =|= Common device tree bindings for media devices Sylvester Nawrocki / Guennadi Liakhovetski ALSA and V4L/Media Controller Steven Toth / Laurent Pinchart ARM and needed features for V4L/DVB Steven Toth Intel media SDK Steven Toth V4L compiance tool Hans Verkuil V4L2 API ambiguities Hans Verkuil Media Controller library Laurent Pincart / Sakari Ailus SoC Vendors feedback – how to help them to go upstream – Android's V4L2 cam library Laurent Pincart / Guennadi Liakhovetski / Palash Bandyopadhyay / Naveen Krishnamurthy Synchronization, shared resource and optimizations Pawel Osciak V4L2/DVB issues from userspace perspective Rémi Denis-Courmont As we'll have only one day for the summit, we may need to remove some themes, or maybe to get an extra time during LPC for the remaining discussions. Possible attendents: === Guennadi Liakhovetski Laurent Pinchart Mauro Carvalho Chehab Michael Krufky Naveen Krishnamurthy +1 seat from ST (waiting Naveen to define who will be the other seat) Palash Bandyopadhyay Pawel Osciak Rémi Denis-Courmont Sakari Ailus Steven Toth Sylvester Nawrocki Am I missing something? Are there other proposals or people intending to participate? Yes: I would like to discuss how to add support for HDMI CEC to the kernel. In particularly I need some feedback from the GPU driver developers on what their ideas are, since CEC is something that touches both V4L2 and GPU. I am not familiar with CEC implementation in GPU. As far as I am aware there isn't any. But CEC should be independent in functionality with audio/video though it is A/V related. I prefer to support only CEC frame TX/RX in kernel. CEC include different category features that need parsing and may need application interaction. Venders may also configure some features as not supported. If kernel support more than TX/RX, policy may be separated to user space part and kernel space part. The kernel interface also becomes complex, maybe ambiguous too. An user space library is more suitable for this task to interact with OS/media player/audio control/etc. I wish that were possible. Our current implementation internally is as you proposed, but we recently discovered that for HDMI 1.4a this won't fly. There the CEC channel is also used for control of the ethernet and audio return channel, and even for hotplug detect in some cases. That's something that has to be handled entirely in kernelspace. So some parts of the CEC protocol have to be internally processed, other parts have to be processed in userspace. This really complicates things and it makes it even more important that the subsystems that need CEC work together on this. Regards, Hans -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [Workshop-2011] Media summit/KS-2012 proposals
2012/8/1 Hans Verkuil hverk...@xs4all.nl: On Tue 31 July 2012 19:58:23 Mauro Carvalho Chehab wrote: In order to sum-up the discussions around the media summit, this is what we've got so far: Proposals proposed by =|= Common device tree bindings for media devices Sylvester Nawrocki / Guennadi Liakhovetski ALSA and V4L/Media Controller Steven Toth / Laurent Pinchart ARM and needed features for V4L/DVB Steven Toth Intel media SDK Steven Toth V4L compiance tool Hans Verkuil V4L2 API ambiguities Hans Verkuil Media Controller library Laurent Pincart / Sakari Ailus SoC Vendors feedback – how to help them to go upstream – Android's V4L2 cam library Laurent Pincart / Guennadi Liakhovetski / Palash Bandyopadhyay / Naveen Krishnamurthy Synchronization, shared resource and optimizations Pawel Osciak V4L2/DVB issues from userspace perspective Rémi Denis-Courmont As we'll have only one day for the summit, we may need to remove some themes, or maybe to get an extra time during LPC for the remaining discussions. Possible attendents: === Guennadi Liakhovetski Laurent Pinchart Mauro Carvalho Chehab Michael Krufky Naveen Krishnamurthy +1 seat from ST (waiting Naveen to define who will be the other seat) Palash Bandyopadhyay Pawel Osciak Rémi Denis-Courmont Sakari Ailus Steven Toth Sylvester Nawrocki Am I missing something? Are there other proposals or people intending to participate? Yes: I would like to discuss how to add support for HDMI CEC to the kernel. In particularly I need some feedback from the GPU driver developers on what their ideas are, since CEC is something that touches both V4L2 and GPU. I am not familiar with CEC implementation in GPU. But CEC should be independent in functionality with audio/video though it is A/V related. I prefer to support only CEC frame TX/RX in kernel. CEC include different category features that need parsing and may need application interaction. Venders may also configure some features as not supported. If kernel support more than TX/RX, policy may be separated to user space part and kernel space part. The kernel interface also becomes complex, maybe ambiguous too. An user space library is more suitable for this task to interact with OS/media player/audio control/etc. I'm not sure what the best place is to do this, it's a fairly specialized topic. It might be better suited to just get a few interested devs together in the evening or during some other suitable time and just see if we can hammer out some scheme. I'll have a presentation on the topic ready. Rob, what are your ideas on this? Who else might be interested in this? Regards, Hans -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [Workshop-2011] Media summit/KS-2012 proposals
On Tue 31 July 2012 19:58:23 Mauro Carvalho Chehab wrote: In order to sum-up the discussions around the media summit, this is what we've got so far: Proposals proposed by =|= Common device tree bindings for media devices Sylvester Nawrocki / Guennadi Liakhovetski ALSA and V4L/Media Controller Steven Toth / Laurent Pinchart ARM and needed features for V4L/DVB Steven Toth Intel media SDK Steven Toth V4L compiance tool Hans Verkuil V4L2 API ambiguities Hans Verkuil Media Controller library Laurent Pincart / Sakari Ailus SoC Vendors feedback – how to help them to go upstream – Android's V4L2 cam library Laurent Pincart / Guennadi Liakhovetski / Palash Bandyopadhyay / Naveen Krishnamurthy Synchronization, shared resource and optimizations Pawel Osciak V4L2/DVB issues from userspace perspective Rémi Denis-Courmont As we'll have only one day for the summit, we may need to remove some themes, or maybe to get an extra time during LPC for the remaining discussions. Possible attendents: === Guennadi Liakhovetski Laurent Pinchart Mauro Carvalho Chehab Michael Krufky Naveen Krishnamurthy +1 seat from ST (waiting Naveen to define who will be the other seat) Palash Bandyopadhyay Pawel Osciak Rémi Denis-Courmont Sakari Ailus Steven Toth Sylvester Nawrocki Am I missing something? Are there other proposals or people intending to participate? Yes: I would like to discuss how to add support for HDMI CEC to the kernel. In particularly I need some feedback from the GPU driver developers on what their ideas are, since CEC is something that touches both V4L2 and GPU. I'm not sure what the best place is to do this, it's a fairly specialized topic. It might be better suited to just get a few interested devs together in the evening or during some other suitable time and just see if we can hammer out some scheme. I'll have a presentation on the topic ready. Rob, what are your ideas on this? Who else might be interested in this? Regards, Hans -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: [Workshop-2011] Media summit/KS-2012 proposals
Mauro, Can you add Sri Deevi to the list too? Thanks, Palash -Original Message- From: workshop-2011-boun...@linuxtv.org [mailto:workshop-2011-boun...@linuxtv.org] On Behalf Of Mauro Carvalho Chehab Sent: Tuesday, July 31, 2012 10:58 AM To: workshop-2...@linuxtv.org; Linux Media Mailing List Subject: [Workshop-2011] Media summit/KS-2012 proposals In order to sum-up the discussions around the media summit, this is what we've got so far: Proposals proposed by =|= Common device tree bindings for media devices Sylvester Nawrocki / Guennadi Liakhovetski ALSA and V4L/Media Controller Steven Toth / Laurent Pinchart ARM and needed features for V4L/DVB Steven Toth Intel media SDK Steven Toth V4L compiance tool Hans Verkuil V4L2 API ambiguities Hans Verkuil Media Controller library Laurent Pincart / Sakari Ailus SoC Vendors feedback - how to help them to go upstream - Android's V4L2 cam library Laurent Pincart / Guennadi Liakhovetski / Palash Bandyopadhyay / Naveen Krishnamurthy Synchronization, shared resource and optimizations Pawel Osciak V4L2/DVB issues from userspace perspective Rémi Denis-Courmont As we'll have only one day for the summit, we may need to remove some themes, or maybe to get an extra time during LPC for the remaining discussions. Possible attendents: === Guennadi Liakhovetski Laurent Pinchart Mauro Carvalho Chehab Michael Krufky Naveen Krishnamurthy +1 seat from ST (waiting Naveen to define who will be the other seat) Palash Bandyopadhyay Pawel Osciak Rémi Denis-Courmont Sakari Ailus Steven Toth Sylvester Nawrocki Am I missing something? Are there other proposals or people intending to participate? Regards, Mauro ___ Workshop-2011 mailing list workshop-2...@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/workshop-2011 Conexant E-mail Firewall (Conexant.Com) made the following annotations - ** Legal Disclaimer This email may contain confidential and privileged material for the sole use of the intended recipient. Any unauthorized review, use or distribution by others is strictly prohibited. If you have received the message in error, please advise the sender by reply email and delete the message. Thank you. ** - -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [Workshop-2011] Media summit/KS-2012 proposals
Hi Mauro, On Tuesday 31 July 2012 14:58:23 Mauro Carvalho Chehab wrote: In order to sum-up the discussions around the media summit, this is what we've got so far: Proposals proposed by =|== === Common device tree bindings for media devices Sylvester Nawrocki / Guennadi Liakhovetski ALSA and V4L/Media ControllerSteven Toth / Laurent Pinchart ARM and needed features for V4L/DVB Steven Toth Intel media SDK Steven Toth V4L compiance tool Hans Verkuil V4L2 API ambiguities Hans Verkuil Media Controller library Laurent Pincart / Sakari Ailus SoC Vendors feedback – how to help them to go upstream – Android's V4L2 cam library Laurent Pincart / Guennadi Liakhovetski / Palash Bandyopadhyay / Naveen Krishnamurthy Synchronization, shared resource and optimizations Pawel Osciak V4L2/DVB issues from userspace perspective Rémi Denis-Courmont As we'll have only one day for the summit, we may need to remove some themes, or maybe to get an extra time during LPC for the remaining discussions. Possible attendents: === Guennadi Liakhovetski Laurent Pinchart Mauro Carvalho Chehab Michael Krufky Naveen Krishnamurthy +1 seat from ST (waiting Naveen to define who will be the other seat) Palash Bandyopadhyay Pawel Osciak Rémi Denis-Courmont Sakari Ailus Steven Toth Sylvester Nawrocki Am I missing something? Are there other proposals or people intending to participate? I think Hans Verkuil is. -- Regards, Laurent Pinchart -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
