* RE: Linux Plumbers Conference 2009: V4L2 API discussions
2009-08-04 17:13 ` Hiremath, Vaibhav
@ 2009-08-04 20:14 ` Karicheri, Muralidharan
2009-08-05 2:31 ` Magnus Damm
2009-08-04 22:15 ` Mike Booth
2009-08-06 15:18 ` Aguirre Rodriguez, Sergio Alberto
2 siblings, 1 reply; 14+ messages in thread
From: Karicheri, Muralidharan @ 2009-08-04 20:14 UTC (permalink / raw)
To: Hiremath, Vaibhav, Hans Verkuil, linux-media@vger.kernel.org
Cc: Magnus Damm, davinci-linux-open-source@linux.davincidsp.com,
linux-omap@vger.kernel.org, eduardo.valentin@nokia.com,
Dongsoo, Nathaniel Kim
Hans,
I plan to register for this. Following are some of the issues that I face today while porting TI DaVinci video drivers to open source:-
1) VPBE display drivers (DM6446,DM355 & DM365): Current implementation of display drivers uses encoder manager (encoders registers with this framework) and display manager (allocating video and OSD layers, managing the OSD hardware etc.). Both FBDev and V4l2 bridge drivers interfaces with these for display timing information and resource allocation. The encoders are developed using a encoder interface that are protocol independent vs sub devices framework in open source that are v4l2 specific. The protocol independent interface was used to avoid building v4l2 sub system when using FBDev devices (That driver VPBE). Internal driver uses SysFs interface to change output and standard at the active encoder (Same functionality is removed from v4l2 display device). I plan to discuss this with you in detail so that we could start working on the porting. I will also go through your RFC to find out if any thing is applicable related to this work
2) Previewer & Resizer driver. I am working with Vaibhav who had worked on an RFC for this. The previewer and resizer devices are doing memory to memory operations. Also should be flexible to use these hardware with capture driver to do on the fly preview and resize. The TI hardware is parameter intensive. We believe these parameters are to be exported to user space through IOCTLs and would require addition of new IOCTLs and extension of control IDs. We will be working with you on this as well.
3) Setting up timing information in capture and display sub devices (example for HD resolution capture and display) . I think Your media processor RFC discuss this.
Murali Karicheri
Software Design Engineer
Texas Instruments Inc.
Germantown, MD 20874
new phone: 301-407-9583
Old Phone : 301-515-3736 (will be deprecated)
email: m-karicheri2@ti.com
>-----Original Message-----
>From: davinci-linux-open-source-bounces@linux.davincidsp.com
>[mailto:davinci-linux-open-source-bounces@linux.davincidsp.com] On Behalf
>Of Hiremath, Vaibhav
>Sent: Tuesday, August 04, 2009 1:13 PM
>To: Hans Verkuil; linux-media@vger.kernel.org
>Cc: Magnus Damm; davinci-linux-open-source@linux.davincidsp.com; linux-
>omap@vger.kernel.org; eduardo.valentin@nokia.com; Dongsoo, Nathaniel Kim
>Subject: RE: Linux Plumbers Conference 2009: V4L2 API discussions
>
>
>
>> -----Original Message-----
>> From: davinci-linux-open-source-bounces@linux.davincidsp.com
>> [mailto:davinci-linux-open-source-bounces@linux.davincidsp.com] On
>> Behalf Of Hans Verkuil
>> Sent: Tuesday, August 04, 2009 12:42 PM
>> To: linux-media@vger.kernel.org
>> Cc: eduardo.valentin@nokia.com; davinci-linux-open-
>> source@linux.davincidsp.com; linux-omap@vger.kernel.org; Magnus
>> Damm; Dongsoo, Nathaniel Kim
>> Subject: Linux Plumbers Conference 2009: V4L2 API discussions
>>
>> Hi all,
>>
>> During this years Plumbers Conference I will be organizing a session
>> (or
>> possibly more than one) on what sort of new V4L2 APIs are needed to
>> support the new SoC devices. These new APIs should also solve the
>> problem
>> of how to find all the related alsa/fb/ir/dvb devices that a typical
>> video
>> device might create.
>>
>> A proposal was made about a year ago (note that this is a bit
>> outdated
>> by now, but the basics are still valid):
>>
>> http://www.archivum.info/video4linux-list%40redhat.com/2008-
>> 07/msg00371.html
>>
>> In the past year the v4l2 core has evolved enough so that we can
>> finally
>> start thinking about this for real.
>>
>> I would like to know who will be attending this conference. I also
>> urge
>> anyone who is working in this area and who wants to have a say in
>> this to
>> attend the conference. The goal is to prepare a new RFC with a
>> detailed
>> proposal on the new APIs that are needed to fully support all the
>> new
>> SoCs. So the more input we get, the better the end-result will be.
>>
>[Hiremath, Vaibhav] Hi Hans,
>
>I will be attending the conference and along with above mentioned RFC I
>would want to discuss some of the open issues, forthcoming TI devices,
>their complexity and required software interfaces (media processor (as you
>mentioned above)) and similar stuff.
>
>
>I will work with you offline before sharing the details here with the
>community.
>
>Thanks,
>Vaibhav Hiremath
>
>> Early-bird registration is still possible up to August 5th (that's
>> tomorrow :-) ).
>>
>> Regards,
>>
>> Hans
>>
>> --
>> Hans Verkuil - video4linux developer - sponsored by TANDBERG Telecom
>>
>> _______________________________________________
>> Davinci-linux-open-source mailing list
>> Davinci-linux-open-source@linux.davincidsp.com
>> http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-
>> source
>_______________________________________________
>Davinci-linux-open-source mailing list
>Davinci-linux-open-source@linux.davincidsp.com
>http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Linux Plumbers Conference 2009: V4L2 API discussions
2009-08-04 20:14 ` Karicheri, Muralidharan
@ 2009-08-05 2:31 ` Magnus Damm
2009-08-05 3:06 ` Hiremath, Vaibhav
0 siblings, 1 reply; 14+ messages in thread
From: Magnus Damm @ 2009-08-05 2:31 UTC (permalink / raw)
To: Karicheri, Muralidharan
Cc: Hiremath, Vaibhav, Hans Verkuil, linux-media@vger.kernel.org,
davinci-linux-open-source@linux.davincidsp.com,
linux-omap@vger.kernel.org, eduardo.valentin@nokia.com,
Dongsoo, Nathaniel Kim
On Wed, Aug 5, 2009 at 5:14 AM, Karicheri,
Muralidharan<m-karicheri2@ti.com> wrote:
> 2) Previewer & Resizer driver. I am working with Vaibhav who had worked on an RFC for this. The previewer and resizer devices are doing memory to memory operations. Also should be flexible to use these hardware with capture driver to do on the fly preview and resize. The TI hardware is parameter intensive. We believe these parameters are to be exported to user space through IOCTLs and would require addition of new IOCTLs and extension of control IDs. We will be working with you on this as well.
FWIW, for our SuperH Mobile devices we make use of UIO and user space
libraries to support for our on-chip multimedia blocks. These blocks
do scaling, rotation, color space conversion and hardware
encode/decode of various formats including h264 and mpeg4 in HD
resolution.
Apart from UIO we use V4L2 for the camera capture interface driver
sh_mobile_ceu_camera.c. It has support for on the fly color space
conversion and scaling/cropping. The CEU driver is making use of
videobuf-dma-contig.c and the USERPTR changes included in 2.6.31-rc
gives the driver zero copy frame capture support.
All of this is of course available upstream.
Cheers,
/ magnus
^ permalink raw reply [flat|nested] 14+ messages in thread
* RE: Linux Plumbers Conference 2009: V4L2 API discussions
2009-08-05 2:31 ` Magnus Damm
@ 2009-08-05 3:06 ` Hiremath, Vaibhav
2009-08-05 3:57 ` Magnus Damm
0 siblings, 1 reply; 14+ messages in thread
From: Hiremath, Vaibhav @ 2009-08-05 3:06 UTC (permalink / raw)
To: Magnus Damm, Karicheri, Muralidharan
Cc: Hans Verkuil, linux-media@vger.kernel.org,
davinci-linux-open-source@linux.davincidsp.com,
linux-omap@vger.kernel.org, eduardo.valentin@nokia.com,
Dongsoo, Nathaniel Kim
> -----Original Message-----
> From: Magnus Damm [mailto:magnus.damm@gmail.com]
> Sent: Wednesday, August 05, 2009 8:01 AM
> To: Karicheri, Muralidharan
> Cc: Hiremath, Vaibhav; Hans Verkuil; linux-media@vger.kernel.org;
> davinci-linux-open-source@linux.davincidsp.com; linux-
> omap@vger.kernel.org; eduardo.valentin@nokia.com; Dongsoo, Nathaniel
> Kim
> Subject: Re: Linux Plumbers Conference 2009: V4L2 API discussions
>
> On Wed, Aug 5, 2009 at 5:14 AM, Karicheri,
> Muralidharan<m-karicheri2@ti.com> wrote:
> > 2) Previewer & Resizer driver. I am working with Vaibhav who had
> worked on an RFC for this. The previewer and resizer devices are
> doing memory to memory operations. Also should be flexible to use
> these hardware with capture driver to do on the fly preview and
> resize. The TI hardware is parameter intensive. We believe these
> parameters are to be exported to user space through IOCTLs and would
> require addition of new IOCTLs and extension of control IDs. We will
> be working with you on this as well.
>
> FWIW, for our SuperH Mobile devices we make use of UIO and user
> space
> libraries to support for our on-chip multimedia blocks. These blocks
> do scaling, rotation, color space conversion and hardware
> encode/decode of various formats including h264 and mpeg4 in HD
> resolution.
>
> Apart from UIO we use V4L2 for the camera capture interface driver
> sh_mobile_ceu_camera.c. It has support for on the fly color space
> conversion and scaling/cropping. The CEU driver is making use of
> videobuf-dma-contig.c and the USERPTR changes included in 2.6.31-rc
> gives the driver zero copy frame capture support.
>
> All of this is of course available upstream.
[Hiremath, Vaibhav] Thanks Magnus,
I will definitely take reference from this device and driver code. I think now I have one more device which has similar capabilities. Can you please share or point me to the spec/TRM for SuperH Mobile device for my reference?
Currently we are referring to Davinci, OMAP and Samsung S3C6400X devices, the user configurable/exported parameters are very different.
Thanks
Vaibhav
>
> Cheers,
>
> / magnus
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Linux Plumbers Conference 2009: V4L2 API discussions
2009-08-05 3:06 ` Hiremath, Vaibhav
@ 2009-08-05 3:57 ` Magnus Damm
0 siblings, 0 replies; 14+ messages in thread
From: Magnus Damm @ 2009-08-05 3:57 UTC (permalink / raw)
To: Hiremath, Vaibhav
Cc: Karicheri, Muralidharan, Hans Verkuil,
linux-media@vger.kernel.org,
davinci-linux-open-source@linux.davincidsp.com,
linux-omap@vger.kernel.org, eduardo.valentin@nokia.com,
Dongsoo, Nathaniel Kim
On Wed, Aug 5, 2009 at 12:06 PM, Hiremath, Vaibhav<hvaibhav@ti.com> wrote:
>> -----Original Message-----
>> From: Magnus Damm [mailto:magnus.damm@gmail.com]
>> Sent: Wednesday, August 05, 2009 8:01 AM
>> To: Karicheri, Muralidharan
>> Cc: Hiremath, Vaibhav; Hans Verkuil; linux-media@vger.kernel.org;
>> davinci-linux-open-source@linux.davincidsp.com; linux-
>> omap@vger.kernel.org; eduardo.valentin@nokia.com; Dongsoo, Nathaniel
>> Kim
>> Subject: Re: Linux Plumbers Conference 2009: V4L2 API discussions
>>
>> On Wed, Aug 5, 2009 at 5:14 AM, Karicheri,
>> Muralidharan<m-karicheri2@ti.com> wrote:
>> > 2) Previewer & Resizer driver. I am working with Vaibhav who had
>> worked on an RFC for this. The previewer and resizer devices are
>> doing memory to memory operations. Also should be flexible to use
>> these hardware with capture driver to do on the fly preview and
>> resize. The TI hardware is parameter intensive. We believe these
>> parameters are to be exported to user space through IOCTLs and would
>> require addition of new IOCTLs and extension of control IDs. We will
>> be working with you on this as well.
>>
>> FWIW, for our SuperH Mobile devices we make use of UIO and user
>> space
>> libraries to support for our on-chip multimedia blocks. These blocks
>> do scaling, rotation, color space conversion and hardware
>> encode/decode of various formats including h264 and mpeg4 in HD
>> resolution.
>>
>> Apart from UIO we use V4L2 for the camera capture interface driver
>> sh_mobile_ceu_camera.c. It has support for on the fly color space
>> conversion and scaling/cropping. The CEU driver is making use of
>> videobuf-dma-contig.c and the USERPTR changes included in 2.6.31-rc
>> gives the driver zero copy frame capture support.
>>
>> All of this is of course available upstream.
> [Hiremath, Vaibhav] Thanks Magnus,
>
> I will definitely take reference from this device and driver code. I think now I have one more device which has similar capabilities. Can you please share or point me to the spec/TRM for SuperH Mobile device for my reference?
The multimedia software is used on a wide range of devices, so it's
hard to come up with a specific device. Google may give you some
examples.
> Currently we are referring to Davinci, OMAP and Samsung S3C6400X devices, the user configurable/exported parameters are very different.
This is why we do the most of the multimedia pipe line in user space
using UIO . High level frameworks like gstreamer and openmax are
suitable for this kind of stuff IMO.
Cheers,
/ magnus
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Linux Plumbers Conference 2009: V4L2 API discussions
2009-08-04 17:13 ` Hiremath, Vaibhav
2009-08-04 20:14 ` Karicheri, Muralidharan
@ 2009-08-04 22:15 ` Mike Booth
2009-08-06 15:18 ` Aguirre Rodriguez, Sergio Alberto
2 siblings, 0 replies; 14+ messages in thread
From: Mike Booth @ 2009-08-04 22:15 UTC (permalink / raw)
To: Hiremath, Vaibhav
Cc: Hans Verkuil, linux-media@vger.kernel.org,
eduardo.valentin@nokia.com,
davinci-linux-open-source@linux.davincidsp.com,
linux-omap@vger.kernel.org, Magnus Damm, Dongsoo, Nathaniel Kim
On Wed, 5 Aug 2009 03:13:29 Hiremath, Vaibhav wrote:
> > -----Original Message-----
> > From: davinci-linux-open-source-bounces@linux.davincidsp.com
> > [mailto:davinci-linux-open-source-bounces@linux.davincidsp.com] On
> > Behalf Of Hans Verkuil
> > Sent: Tuesday, August 04, 2009 12:42 PM
> > To: linux-media@vger.kernel.org
> > Cc: eduardo.valentin@nokia.com; davinci-linux-open-
> > source@linux.davincidsp.com; linux-omap@vger.kernel.org; Magnus
> > Damm; Dongsoo, Nathaniel Kim
> > Subject: Linux Plumbers Conference 2009: V4L2 API discussions
> >
> > Hi all,
> >
> > During this years Plumbers Conference I will be organizing a session
> > (or
> > possibly more than one) on what sort of new V4L2 APIs are needed to
> > support the new SoC devices. These new APIs should also solve the
> > problem
> > of how to find all the related alsa/fb/ir/dvb devices that a typical
> > video
> > device might create.
> >
> > A proposal was made about a year ago (note that this is a bit
> > outdated
> > by now, but the basics are still valid):
> >
> > http://www.archivum.info/video4linux-list%40redhat.com/2008-
> > 07/msg00371.html
> >
> > In the past year the v4l2 core has evolved enough so that we can
> > finally
> > start thinking about this for real.
> >
> > I would like to know who will be attending this conference. I also
> > urge
> > anyone who is working in this area and who wants to have a say in
> > this to
> > attend the conference. The goal is to prepare a new RFC with a
> > detailed
> > proposal on the new APIs that are needed to fully support all the
> > new
> > SoCs. So the more input we get, the better the end-result will be.
>
> [Hiremath, Vaibhav] Hi Hans,
>
> I will be attending the conference and along with above mentioned RFC I
> would want to discuss some of the open issues, forthcoming TI devices,
> their complexity and required software interfaces (media processor (as you
> mentioned above)) and similar stuff.
>
> I will work with you offline before sharing the details here with the
> community.
>
> Thanks,
> Vaibhav Hiremath
>
> > Early-bird registration is still possible up to August 5th (that's
> > tomorrow :-) ).
> >
> > Regards,
> >
> > Hans
> >
> > --
> > Hans Verkuil - video4linux developer - sponsored by TANDBERG Telecom
> >
> > _______________________________________________
> > Davinci-linux-open-source mailing list
> > Davinci-linux-open-source@linux.davincidsp.com
> > http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-
> > source
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
does this mean that the definition of "howto" signal to noise and signal
strength might get fixed up?
Mike
^ permalink raw reply [flat|nested] 14+ messages in thread
* RE: Linux Plumbers Conference 2009: V4L2 API discussions
2009-08-04 17:13 ` Hiremath, Vaibhav
2009-08-04 20:14 ` Karicheri, Muralidharan
2009-08-04 22:15 ` Mike Booth
@ 2009-08-06 15:18 ` Aguirre Rodriguez, Sergio Alberto
2 siblings, 0 replies; 14+ messages in thread
From: Aguirre Rodriguez, Sergio Alberto @ 2009-08-06 15:18 UTC (permalink / raw)
To: Hiremath, Vaibhav, Hans Verkuil, linux-media@vger.kernel.org
Cc: eduardo.valentin@nokia.com,
davinci-linux-open-source@linux.davincidsp.com,
linux-omap@vger.kernel.org, Magnus Damm, Dongsoo, Nathaniel Kim
> -----Original Message-----
> From: linux-omap-owner@vger.kernel.org [mailto:linux-omap-
> owner@vger.kernel.org] On Behalf Of Hiremath, Vaibhav
> Sent: Tuesday, August 04, 2009 12:13 PM
> To: Hans Verkuil; linux-media@vger.kernel.org
> Cc: eduardo.valentin@nokia.com; davinci-linux-open-
> source@linux.davincidsp.com; linux-omap@vger.kernel.org; Magnus Damm;
> Dongsoo, Nathaniel Kim
> Subject: RE: Linux Plumbers Conference 2009: V4L2 API discussions
>
>
>
> > -----Original Message-----
> > From: davinci-linux-open-source-bounces@linux.davincidsp.com
> > [mailto:davinci-linux-open-source-bounces@linux.davincidsp.com] On
> > Behalf Of Hans Verkuil
> > Sent: Tuesday, August 04, 2009 12:42 PM
> > To: linux-media@vger.kernel.org
> > Cc: eduardo.valentin@nokia.com; davinci-linux-open-
> > source@linux.davincidsp.com; linux-omap@vger.kernel.org; Magnus
> > Damm; Dongsoo, Nathaniel Kim
> > Subject: Linux Plumbers Conference 2009: V4L2 API discussions
> >
> > Hi all,
> >
> > During this years Plumbers Conference I will be organizing a session
> > (or
> > possibly more than one) on what sort of new V4L2 APIs are needed to
> > support the new SoC devices. These new APIs should also solve the
> > problem
> > of how to find all the related alsa/fb/ir/dvb devices that a typical
> > video
> > device might create.
> >
> > A proposal was made about a year ago (note that this is a bit
> > outdated
> > by now, but the basics are still valid):
> >
> > http://www.archivum.info/video4linux-list%40redhat.com/2008-
> > 07/msg00371.html
> >
> > In the past year the v4l2 core has evolved enough so that we can
> > finally
> > start thinking about this for real.
> >
> > I would like to know who will be attending this conference. I also
> > urge
> > anyone who is working in this area and who wants to have a say in
> > this to
> > attend the conference. The goal is to prepare a new RFC with a
> > detailed
> > proposal on the new APIs that are needed to fully support all the
> > new
> > SoCs. So the more input we get, the better the end-result will be.
> >
> [Hiremath, Vaibhav] Hi Hans,
>
> I will be attending the conference and along with above mentioned RFC I
> would want to discuss some of the open issues, forthcoming TI devices,
> their complexity and required software interfaces (media processor (as you
> mentioned above)) and similar stuff.
Hans, Vaibhav,
I'll be attending this conference too. I just got approval from my boss ;).
I'm starting to take the v4l2_subdev migration task as a high priority now, since most of the stability related issues in some proprietary platform are gone now. :)
Actually, I'm also interested on the discussions about the Preview/Resizer Wrappers.
Meet you there.
Regards,
Sergio
>
>
> I will work with you offline before sharing the details here with the
> community.
>
> Thanks,
> Vaibhav Hiremath
>
> > Early-bird registration is still possible up to August 5th (that's
> > tomorrow :-) ).
> >
> > Regards,
> >
> > Hans
> >
> > --
> > Hans Verkuil - video4linux developer - sponsored by TANDBERG Telecom
> >
> > _______________________________________________
> > Davinci-linux-open-source mailing list
> > Davinci-linux-open-source@linux.davincidsp.com
> > http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-
> > source
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 14+ messages in thread