Age | Commit message (Collapse) | Author |
|
Fail to register DSS isr's if mainclk is diabled since they write/read to DISPC
registers.
Signed-off-by: Archit Taneja <archit@ti.com>
|
|
Correct configuration for YUV422 formats involves allocating
YUV422 format in a 32-bit tiler container with half width.
Video pipeline rotation attributes must be configured when
using YUV422 formats.
Change-Id: I7126440874fb5e9eede600bf287704ecfa5ac481
Signed-off-by: Alberto Aguirre <a-aguirre@ti.com>
Signed-off-by: Archit Taneja <archit@ti.com>
|
|
Use of workqueues in Taal is causing issues with acquire_console_sem()
used in linux-fb. On destroying/creating workqueus after Taal suspend/resume
resolves the issue partially.
Signed-off-by: Archit Taneja <archit@ti.com>
|
|
A 4 byte TILER container is used instead of 2 byte container to preserve
the YUYV pixel content after rotation.
Some artifacts are still seen on 90 and 270 rotation and are being worked upon.
Signed-off-by: Archit Taneja <archit@ti.com>
|
|
Signed-off-by: Archit Taneja <archit@ti.com>
Signed-off-by: Samreen <samreen@ti.com>
|
|
Signed-off-by: David Sin <davidsin@ti.com>
|
|
Signed-off-by: David Sin <davidsin@ti.com>
Signed-off-by: Hari Kanigeri <h-kanigeri2@ti.com>
|
|
Fix for build error when building TILER as a module
Signed-off-by: David Sin <davidsin@ti.com>
|
|
Signed-off-by: David Sin <davidsin@ti.com>
|
|
|
|
This patch enables all 4 combinations of interlaced and progressive buffer and display devices.
1.Interlaced buffer & progressive display device
2.Interlaced buffer & Interlaced display device
3.progressive buffer & Interlaced display device
4.progressive buffer & progressive display device
Signed-off-by: Sujeet Kumar Baranwal <s-baranwal@ti.com>
Signed-off-by: Mukund Mittal <mmittal@ti.com>
|
|
Signed-off-by: Archit Taneja <archit@ti.com>
|
|
Replace BUG_ON macros with WARN_ON.
Signed-off-by: David Sin <davidsin@ti.com>
|
|
Sparse fixes.
Signed-off-by: David Sin <davidsin@ti.com>
|
|
Sparse fixes.
Signed-off-by: David Sin <davidsin@ti.com>
|
|
Sparse fixes.
Signed-off-by: David Sin <davidsin@ti.com>
|
|
vma flags are set by remap_pfn_range function in mmap function, so
don't need to set this seperatly in the function.
Signed-off-by: Hari Kanigeri <h-kanigeri2@ti.com>
Signed-off-by: David Sin <davidsin@ti.com>
|
|
It's possible that the mem struct assignment inside of
the kernel list doesn't assigned properly (e.g. NULL), which
causes a deref crash during the free call.
Signed-off-by: David Sin <davidsin@ti.com>
|
|
If free_list is empty the element won't be assigned
to NULL. Causing issues when freeing the pages.
Signed-off-by: Fernando Guzman Lugo <fernando.lugo@ti.com>
Signed-off-by: Bhavin Shah <bshah@ti.com>
Signed-off-by: David Sin <davidsin@ti.com>
|
|
|
|
|
|
Warning fixes for omap_vout.c and omap_wb.c
|
|
Setting proper default values for video / display
Kconfig files.
Signed-off-by: Ricardo Perez Olivares <x0081762@ti.com>
|
|
|
|
Signed-off-by: Mythri P K <mythripk@ti.com>
|
|
Signed-off-by: Mythri P K <mythripk@ti.com>
|
|
Signed-off-by: Mythri P K <mythripk@ti.com>
|
|
VID* Attributes
Signed-off-by: Mythri P K <mythripk@ti.com>
|
|
|
|
This patch adds a tiler notifier callback mechanism
for events. This covers file close events.
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
|
|
1) Allow multiple processes to open the v4l2 device, and set correctly the
device capabilities.
2) Make VIDIOC_S_FMT of overlay parameters take immediate effect, rather
than waiting for a buffer flip. This way the video position updates even
if the video playback is paused or slow.
Signed-off-by: Rob Clark <rob@ti.com>
Signed-off-by: Mayuresh Janorkar <mayur@ti.com>
|
|
|
|
Signed-off-by: Archit Taneja <archit@ti.com>
|
|
Signed-off-by: Archit Taneja <archit@ti.com>
|
|
|
|
The global_alpha value is now taken from the omap_overlay_info
structure, previously if the vidioc_s_fmt ioctl was called twice
,it led to an incorrect value being passed to the overlay cache.
This is a temporary fix.
Signed-off-by: Archit Taneja <archit@ti.com>
|
|
Signed-off-by: Mythri P K <mythripk@ti.com>
|
|
Signed-off-by: Archit Taneja <archit@ti.com>
|
|
Adds the crop support while STREAMON
Signed-off-by: Archit Taneja <archit@ti.com>
Signed-off-by: Guruswamy Senthilvadivu <svadivu@ti.com>
|
|
Restructs the omap_vout_isr to handle multiple displays
Signed-off-by: Lajos Molnar <molnar@ti.com>
Signed-off-by: Sumit Semwal <sumit.semwal@ti.com>
Signed-off-by: Guruswamy Senthilvadivu <svadivu@ti.com>
|
|
Adds the needed function and variable declarations
Signed-off-by: Lajos Molnar <molnar@ti.com>
Signed-off-by: Guruswamy Senthilvadivu <svadivu@ti.com>
|
|
Adds uv_addr for NV12. Changes video_mode_to_dss_mode API
Signed-off-by: Lajos Molnar <molnar@ti.com
Signed-off-by: Guruswamy Senthilvadivu <svadivu@ti.com>
|
|
Temporarily #ifdef VRFB related functions and calls
Signed-off-by: Guruswamy Senthilvadivu <svadivu@ti.com>
|
|
Selecting VRFB by default could be changed to depend on OMAP2,3
to allow OMAP4 only builds to go through.
Signed-off-by: Guruswamy Senthilvadivu <svadivu@ti.com>
|
|
Currently, the free page stack keeps 40MB worth of pages on hand.
Since there are still some system workarounds that are being resolved
using tiler memory, we need to temporarily adjust this figure. Also,
we haven't quite figured out what amount to keep that would strike a
balance between performance and memory consumption.
Signed-off-by: David Sin <davidsin@ti.com>
|
|
Signed-off-by: Bryan Wu <bryan.wu@canonical.com>
Signed-off-by: David Sin <davidsin@ti.com>
|
|
This patch will resolve the data inconsistency problems
seen in omap 4 es2.0. For es1.0, we were creating a
memory barrier using dsb() around the PAT reg accesses.
Additionally, we have added wmb() calls before the call to the
PAT refill function to ensure that the data reaches the main
memory beforehand.
Signed-off-by: David Sin <davidsin@ti.com>
|
|
|
|
Add logic to cap the total amount of pages to keep on hand.
Signed-off-by: David Sin <davidsin@ti.com>
|
|
Instead of allocating and freeing PAT page array
memory each time, allocate 128k upfront and reuse the
memory. This will avoid the possibilty of not being
able to obtain the memory after driver initialization.
Signed-off-by: David Sin <davidsin@ti.com>
|