On Wed, Aug 5, 2009 at 12:06 PM, Hiremath, Vaibhav<hvaibhav@xxxxxx> wrote: >> -----Original Message----- >> From: Magnus Damm [mailto:magnus.damm@xxxxxxxxx] >> Sent: Wednesday, August 05, 2009 8:01 AM >> To: Karicheri, Muralidharan >> Cc: Hiremath, Vaibhav; Hans Verkuil; linux-media@xxxxxxxxxxxxxxx; >> davinci-linux-open-source@xxxxxxxxxxxxxxxxxxxx; linux- >> omap@xxxxxxxxxxxxxxx; eduardo.valentin@xxxxxxxxx; 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@xxxxxx> 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 -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
