mainwindow.ui: reduce font size of text to avoid truncation
reduce font size from 16 to 12
Signed-off-by: Eric Ruei <e-ruei1@ti.com>
reduce font size from 16 to 12
Signed-off-by: Eric Ruei <e-ruei1@ti.com>
loopback : trans-key-mode and zorder property settings
Original trans-kay-mode and zorder property is not working with
DSS driver in Processor SDK 5.0. Only the gui layer is seen and no video
layer is seeen.
Following changes in the DRM properties enabled the original behaviour
of the demo -
1. The zorder of the GUI plane has to be lower then the video plane
2. In addition to this, "trans-key=mode" property needed to change from
original value 2 to 1. This change was needed only on AM57x SoC. For
AM437x SoC, no changes in trns-key-mode value needed.
SOme more changes done to the code but they have no impact on the
fucntionality of the demo. They are there for demonstration purpose only
1. Demonstarted setting of "trans-key", "background","alphablender" and
"global_alpha" value settings. They can be used to change the background
color, or the tranparency value or to enable global alpha blending.
Signed-off-by: Manisha Agrawal <manisha.agrawal@ti.com>
Original trans-kay-mode and zorder property is not working with
DSS driver in Processor SDK 5.0. Only the gui layer is seen and no video
layer is seeen.
Following changes in the DRM properties enabled the original behaviour
of the demo -
1. The zorder of the GUI plane has to be lower then the video plane
2. In addition to this, "trans-key=mode" property needed to change from
original value 2 to 1. This change was needed only on AM57x SoC. For
AM437x SoC, no changes in trns-key-mode value needed.
SOme more changes done to the code but they have no impact on the
fucntionality of the demo. They are there for demonstration purpose only
1. Demonstarted setting of "trans-key", "background","alphablender" and
"global_alpha" value settings. They can be used to change the background
color, or the tranparency value or to enable global alpha blending.
Signed-off-by: Manisha Agrawal <manisha.agrawal@ti.com>
Run time support for allocating memory CMEM vs OMAP_BO driver
Following modifications:
1. The application was earlier build time selcting CMEM vs OMAP DRM memory for capture
buffer allocation. This has changed to select the memory type run time
as command line arguments.
2. Fix the pointer mishandling bug in cmem buffer allocation.
3. Build time warning fix for unused parameter.
Signed-off-by: Manisha Agrawal <manisha.agrawal@ti.com>
Following modifications:
1. The application was earlier build time selcting CMEM vs OMAP DRM memory for capture
buffer allocation. This has changed to select the memory type run time
as command line arguments.
2. Fix the pointer mishandling bug in cmem buffer allocation.
3. Build time warning fix for unused parameter.
Signed-off-by: Manisha Agrawal <manisha.agrawal@ti.com>
cmem : common build for AM437x and AM57x
CMEM library inclusion is enabled for AM437x platform. Earlier the
inclusion was selective for AM57x build only as the CMEM driver was not
available in AM437x Processor SDK. That has changed since PSDK version
3.3.
Signed-off-by: Manisha Agrawal <manisha.agrawal@ti.com>
CMEM library inclusion is enabled for AM437x platform. Earlier the
inclusion was selective for AM57x build only as the CMEM driver was not
available in AM437x Processor SDK. That has changed since PSDK version
3.3.
Signed-off-by: Manisha Agrawal <manisha.agrawal@ti.com>
dual-cam-demo : Conditional build
Added support for conditional inclusion of the CMEM library when
building the code on AM57xx platform.
Added support for conditional inclusion of the CMEM library when
building the code on AM57xx platform.
CMEM buf : CPU processing on read-write cache buffer
Many application requires to do CPU based processings on camera captured
video. Current example application allocates the capture driver buffer
from omapdrm that doesn't support read cache property on those buffers.
It results in 10x to 50x slow proeccsing by CPU compared to when buffers
are allocated through malloc (having read cache property). To enable CPU
for read cache buffer access on those capture buffers, buffers are
allocated from CMEM driver that support the cache operations on it's
allocated buffer. CMEM API usage are demonstrated in loopback.c file to
allocate the buffers and export the fd to capture and display driver
using dmabuf export feature.
Many application requires to do CPU based processings on camera captured
video. Current example application allocates the capture driver buffer
from omapdrm that doesn't support read cache property on those buffers.
It results in 10x to 50x slow proeccsing by CPU compared to when buffers
are allocated through malloc (having read cache property). To enable CPU
for read cache buffer access on those capture buffers, buffers are
allocated from CMEM driver that support the cache operations on it's
allocated buffer. CMEM API usage are demonstrated in loopback.c file to
allocate the buffers and export the fd to capture and display driver
using dmabuf export feature.
loopback : fix tearing issue
The demo tearing effect. It wasn't using page flip interrupt handler to
manage the queue for shared buffer between capture and display. Fix the
problem.
The demo tearing effect. It wasn't using page flip interrupt handler to
manage the queue for shared buffer between capture and display. Fix the
problem.
loopback : bug fix for resolution less then 640
Application was run time modifying the capture resolution to 640x480
when the display resolution width is lower then 640. At the time of
atomic mode setting, application was using default build time capture
resoution. This caused application failure with lower resolution display
like in AM437x-SK board that has display resolution of size 480x272.
Signed-off-by: Manisha Agrawal <manisha.agrawal@ti.com>
Application was run time modifying the capture resolution to 640x480
when the display resolution width is lower then 640. At the time of
atomic mode setting, application was using default build time capture
resoution. This caused application failure with lower resolution display
like in AM437x-SK board that has display resolution of size 480x272.
Signed-off-by: Manisha Agrawal <manisha.agrawal@ti.com>
loopback : remove accidental line break
In prior checkin, accidenatl line break was introducced. Remove the
same.
Signed-off-by: Manisha Agrawal <manisha.agrawal@ti.com>
In prior checkin, accidenatl line break was introducced. Remove the
same.
Signed-off-by: Manisha Agrawal <manisha.agrawal@ti.com>
loopback : fix single camera use case
The plane scaling resolution setting for single camera use case was
improper. Fixed the issue.
The plane scaling resolution setting for single camera use case was
improper. Fixed the issue.
mainwindow : Remove dead code
Remove another dead code from the file.
Remove another dead code from the file.
mainwindow : remove dead code
Removed the dead code related to the single camera functionality.
Improved code indentation.
Signed-off-by: Manisha Agrawal <manisha.agrawal@ti.com>
Removed the dead code related to the single camera functionality.
Improved code indentation.
Signed-off-by: Manisha Agrawal <manisha.agrawal@ti.com>
mainwindow : use Mutex to access drm resource
Mutex is used rather using global variables to prevent simultaneous
access to drm resource by loopback and main thread.
Mutex is used rather using global variables to prevent simultaneous
access to drm resource by loopback and main thread.
loopback: Migrate to drm Atmoic Mode APIs
1. Migrate the demo from drm non-atomic mode to drm atmoic mode APIs.
2. Add support for run time detection of SoC to enable SoC specific
settings without passing user arguements to the fucntion.
3. Code cleanup related to buffer allocation and usage
1. Migrate the demo from drm non-atomic mode to drm atmoic mode APIs.
2. Add support for run time detection of SoC to enable SoC specific
settings without passing user arguements to the fucntion.
3. Code cleanup related to buffer allocation and usage
Bug fixes for clicking exit button and single camera use case on AM4 GP EVM
1) Add NULL pointer check for free_vid_buffers: fix "128 pages are still in use"
when clicking the Exit button
2) Correct the way of end-streaming: fix the issue of ending streaming on wrong
cap device when only the built-in camera is there on AM4 GP EVM
Signed-off-by: Hongmei Gou <h-gou@ti.com>
Signed-off-by: Manisha Agrawal <manisha.agrawal@ti.com>
1) Add NULL pointer check for free_vid_buffers: fix "128 pages are still in use"
when clicking the Exit button
2) Correct the way of end-streaming: fix the issue of ending streaming on wrong
cap device when only the built-in camera is there on AM4 GP EVM
Signed-off-by: Hongmei Gou <h-gou@ti.com>
Signed-off-by: Manisha Agrawal <manisha.agrawal@ti.com>
added support for demo working with single or dual camera. Earlier it worked only with dual camera
cleanup related to connector settings that aren't required for this demo use case. Along with it, fixed the bug in capture_frame(). v4l2_dequeue_buffer() wasn't happening in that function as a result of two frame delay logic before retuning the buffers back to capture queue.
no memcpy between capture and display drivers. Achieved using dmabuf, no jitter by introducing two frames delay of two frames between capture and display driver. Wait for 2015 LTS to get tthe async drmModeSetPlane() issue resolved
Removed direct access of DSS register.Insted used omapdrm APIs to change the DSS properties
fix for frozen video display when PIP is disabled
removed hard coding of display resolution and used crtc plane resolution to set the same
Added support for HDMI display. Added the workaround to clear the PIP box windows seen when PIP displayed. This issue is seen on QT5 as QWSServer is no more supported
Makefile.build: Use qmake instead of qmake2
Signed-off-by: Franklin S. Cooper Jr <fcooper@ti.com>
Signed-off-by: Franklin S. Cooper Jr <fcooper@ti.com>
dual_camera: Allow building on Qt 5 and Qt 4
Signed-off-by: Franklin S Cooper Jr <fcooper@ti.com>
Signed-off-by: Franklin S Cooper Jr <fcooper@ti.com>
changed display user level APIs from fbdev to libdrm
Fix for DSS scaling error on very small screens
header file update for double buffer patch
Added double buffering to display to eliminate tearing
Move license to individual file
Fixed jpeg image glitch & single camera mode GUI DSS blending issue
Correct link to Matrix description document
Renaming files
* Rename files to remove arm_multimedia since these demos are not apart of the
multimedia group in Matrix.
Signed-off-by: Franklin S. Cooper Jr <fcooper@ti.com>
* Rename files to remove arm_multimedia since these demos are not apart of the
multimedia group in Matrix.
Signed-off-by: Franklin S. Cooper Jr <fcooper@ti.com>
Improved v4l2 stream on function
Cleaned up v4l2/fbdev init and touched up PiP Settings
Camera images now scale to all display resolutions
Rename SDK Makefile back to Makefile.build
* This insures that Qt users will have qmake generate "Makefile" instead of
App-Makefile which is the expected/default behavior.
Signed-off-by: Franklin S. Cooper Jr <fcooper@ti.com>
* This insures that Qt users will have qmake generate "Makefile" instead of
App-Makefile which is the expected/default behavior.
Signed-off-by: Franklin S. Cooper Jr <fcooper@ti.com>
Use the correct name for the moc file to fix the build error
Signed-off-by: Franklin S. Cooper Jr <fcooper@ti.com>
Signed-off-by: Franklin S. Cooper Jr <fcooper@ti.com>
Complete architecture overhaul due to the genius of Franklin C. FPS limited to ~30.
Cleaned up V4L2 init
Fixed incorrect touchscreen calibration
Added index number to saved images. Set PiP scaling to 1/2 to avoid DSS errors
Additional minior cleanup
Remove unecessary variables from Makefile
Signed-off-by: Franklin S Cooper Jr <fcooper@ti.com>
Signed-off-by: Franklin S Cooper Jr <fcooper@ti.com>
Update Makefile
* Update Makefile to throw an error if destination directory doesn't exist.
* By default only build release version
* Rename Makefile.build to Makefile
* Have qmake generate App-Makefile as the makefile name.
Signed-off-by: Franklin S Cooper Jr <fcooper@ti.com>
* Update Makefile to throw an error if destination directory doesn't exist.
* By default only build release version
* Rename Makefile.build to Makefile
* Have qmake generate App-Makefile as the makefile name.
Signed-off-by: Franklin S Cooper Jr <fcooper@ti.com>
Added initial jpeg capture support and added workaround for 720p 1/4 scaling issue
Improved GUI for single camera mode
Added support for any resolution and overhauled fb init
Enable single camera mode
-Program no longer fails if /dev/video1 is not available
-Removed DSS configuration from script and put it into program
-Added matrix desciption
-Program no longer fails if /dev/video1 is not available
-Removed DSS configuration from script and put it into program
-Added matrix desciption
Update Makefile.build
* Add default value for MATRIX_APP_DIR variable.
* Correct the path where the Matrix files should be copied to
* Delete temp file.
* Add default value for MATRIX_APP_DIR variable.
* Correct the path where the Matrix files should be copied to
* Delete temp file.
Update dual camera script
* Update the dual camera script so that Matrix is closed before the application
is ran.
* When the application is complete open Matrix back up.
Signed-off-by: Franklin S. Cooper Jr <fcooper@ti.com>
* Update the dual camera script so that Matrix is closed before the application
is ran.
* When the application is complete open Matrix back up.
Signed-off-by: Franklin S. Cooper Jr <fcooper@ti.com>
Updated Makefile to work with OE integration
Add Makefile build target
Use correct shell script name
Add files for Matrix integration
Initial commit