YUVRGBdisplay:Add application to display uyvy There is no IP in dra7x, am57x that generates uyvy data. To display this format buffers with wayland , a file based application is added. YUVRGBdisplay application reads one frame of raw YUV data at a time from a file and submits to display. The formats tested with this application are nv12, yuyv, uyvy and abgr32. This application expects width, height and colorformat of raw file as arguments. Examples to test this application Displaying a yuyv file with kms YUVRGBdisplay -s 32:1920x1080 yuyv_720x480.raw -W 720 -H 480 -c yuyv Displaying a uyvy file with wayland backend YUVRGBdisplay -w 1920x1080 uyvy_640x480.raw -W 640 -H 480 -c uyvy Displaying a NV12 file with kmscube backend YUVRGBdisplay --kmscube --connector 32 nv12_352x288.raw -W 352 -H 288 -c nv12 Displaying a ABGR32 file with wayland backend YUVRGBdisplay -w 1280x800 argb32_1920x1080.raw -W 1920 -H 1080 -c abgr32 Signed-off-by: Ramprasad N <x0038811@ti.com>
display-wayland: Replace scaler with viewporter scaler protocol is no more supported with wayland-protocols and has been replaced with viewporter protocols Signed-off-by: Ramprasad N <x0038811@ti.com>
viddec3test: dce_buf_lock & unlock of OutBuf_fd Earlier the dce_buf_lock and dce_buf_unlock for OutBuf_fd was done based on eof flag. Resulting memory leak during long run. This patch handles the buffer locking & unlocking properly. Along with code cleanup. Signed-off-by: Amai Prashanth Kumar <x0270680@ti.com> Signed-off-by: Karthik Ramanan <a0393906@ti.com>
display-wayland: enable cropping support On Wayland, the video was displayed along with the padded region resulting green-strip in edges. This patch will crop the padded region being displayed. Signed-off-by: Subhajit Paul <a0132170@ti.com> Signed-off-by: Amai Prashanth Kumar <x0270680@ti.com>
viddec3test:Handling outBufsInUseFlag for interlaced contents When outBufsInUseFlag is set in case of interlaced streams, for second field decoding, new output buffer should not be sent but the buffer which was sent for first field decoding needs to be sent. Thsi patch takes care of this issue. Signed-off-by: Ramprasad N <x0038811@ti.com>
capturevpedisplay: Use single plane for input format As VIP cannot handle multiplane buffer make sure that the shared buffers are allocated as single plane entities. The VPE output buffers can be set to use muliplane buffers as needed. Signed-off-by: Benoit Parrot <bparrot@ti.com>
vpe: Remove unnecessary G_FMT call Remove superfluous G_FMT call prior to calling S_FMT as it would force to manually zero out returned parameter value we don't need. Using S_FMT and specifying only what we need should yield acceptable default values for the part we don't care about. This is standard v4l2 behavior. Signed-off-by: Benoit Parrot <bparrot@ti.com>