In omap_vout_calculate_offset(), cur_display is assigned ovl-manager-device,
but
isn't used for anything. The corresponding code is removed.
Signed-off-by: Archit Taneja arc...@ti.com
---
drivers/media/video/omap/omap_vout.c |8
1 files changed, 0 insertions(+), 8 deletions
/
Archit Taneja (2):
V4L/DVB: OMAP_VOUT: Create a seperate vrfb functions library
V4L/DVB: OMAP_VOUT: Use rotation_type to choose between vrfb and
sdram rotation
drivers/media/video/omap/Kconfig |1 -
drivers/media/video/omap/Makefile |1 +
drivers/media/video/omap
vrfb function's have been moved around.
Signed-off-by: Archit Taneja arc...@ti.com
---
drivers/media/video/omap/omap_vout.c | 32 +--
drivers/media/video/omap/omap_vout_vrfb.c | 417 +
drivers/media/video/omap/omap_vout_vrfb.h | 40 +++
drivers/media/video/omap
in
omap_vout_vrfb.c
Signed-off-by: Archit Taneja arc...@ti.com
---
drivers/media/video/omap/Kconfig|1 -
drivers/media/video/omap/Makefile |1 +
drivers/media/video/omap/omap_vout.c| 470 ++-
drivers/media/video/omap/omap_voutdef.h |1 +
4 files
setting a non zero rotation value.
Archit Taneja (2):
V4L/DVB: OMAP_VOUT: Create a seperate vrfb functions library
V4L/DVB: OMAP_VOUT: Use rotation_type to choose between vrfb and
sdram buffers
drivers/media/video/omap/Kconfig |1 -
drivers/media/video/omap/Makefile
vrfb function's have been moved around.
Signed-off-by: Archit Taneja arc...@ti.com
---
drivers/media/video/omap/omap_vout.c | 32 +--
drivers/media/video/omap/omap_vout_vrfb.c | 417 +
drivers/media/video/omap/omap_vout_vrfb.h | 40 +++
drivers/media/video/omap
in
omap_vout_vrfb.c
Signed-off-by: Archit Taneja arc...@ti.com
---
drivers/media/video/omap/Kconfig|1 -
drivers/media/video/omap/Makefile |1 +
drivers/media/video/omap/omap_vout.c| 448 ++-
drivers/media/video/omap/omap_voutdef.h |1 +
4 files
is
VOUT_ROT_VRFB
When the rotation_type is set to VOUT_ROT_NONE, the S_CTRL ioctl prevents the
user setting
a non zero rotation or non zero mirror value.
Archit Taneja (3):
V4L/DVB: OMAP_VOUT: Move some functions and preprocessor defines from
omap_vout
V4L/DVB: OMAP_VOUT: Create a seperate vrfb
Move some functions from omap_vout.c to omap_voutlib.c and defines to
omap_voutdef.h
These will be required vrfb specific functions.
Signed-off-by: Archit Taneja arc...@ti.com
---
drivers/media/video/omap/omap_vout.c| 111 +--
drivers/media/video/omap
Create omap_vout_vrfb.c and omap_vout_vrfb.h, these contain functions which
omap_vout will call if the rotation type is set to VRFB rotation. It is
essentialy the code in omap_vout which is used for vrfb specific tasks.
Signed-off-by: Archit Taneja arc...@ti.com
---
drivers/media/video/omap
in
omap_vout_vrfb.c
Signed-off-by: Archit Taneja arc...@ti.com
---
drivers/media/video/omap/Kconfig|2 +-
drivers/media/video/omap/Makefile |1 +
drivers/media/video/omap/omap_vout.c| 449 ++-
drivers/media/video/omap/omap_voutdef.h | 13 +
4 files changed
rotation. A member rotation_type is introduced in
omapvideo_info,
this allows to call vrfb specific functions only if the rotation type is
VOUT_ROT_VRFB
When the rotation_type is set to VOUT_ROT_NONE, the S_CTRL ioctl prevents the
user setting
a non zero rotation or non zero mirror value.
Archit Taneja
Move some inline functions from omap_vout.c to omap_voutdef.h and independent
functions like omap_vout_alloc_buffer/omap_vout_free_buffer to omap_voutlib.c.
Reviewed-by: Vaibhav Hiremath hvaib...@ti.com
Signed-off-by: Archit Taneja arc...@ti.com
---
drivers/media/video/omap/omap_vout.c| 109
on the arch type in omap_vout_probe. The rotation_type
var is now used to choose between vrfb and non-vrfb calls.
Reviewed-by: Vaibhav Hiremath hvaib...@ti.com
Signed-off-by: Archit Taneja arc...@ti.com
---
drivers/media/video/omap/Kconfig |2 +-
drivers/media/video/omap/Makefile
requested in reqbuf. When the video
device is opened the next time, this check will prevent us to allocate a buffer
which is larger than what we requested the last time.
Don't use vout-buffer_size, always check with the parameters video1_bufsize
or video2_bufsize.
Signed-off-by: Archit Taneja arc
which affects omap_vout and has been posted recently on linux-media
(see OMAPDSS/OMAP_VOUT: Fix incorrect OMAP3-alpha compatibility setting). This
tree can be used as reference:
g...@gitorious.org:~boddob/linux-omap-dss2/archit-dss2-clone.git 'for_omap_vout'
Archit Taneja (5):
OMAP_VOUT: Fix check
requested in reqbuf. When the video
device is opened the next time, this check will prevent us to allocate a buffer
which is larger than what we requested the last time.
Don't use vout-buffer_size, always check with the parameters video1_bufsize
or video2_bufsize.
Signed-off-by: Archit Taneja arc
Currently, there is a lot of redundant code is between DPI and VENC panels, this
can be made common by moving out field/interlace specific code to a separate
function called omapvid_handle_interlace_display(). There is no functional
change made.
Signed-off-by: Archit Taneja arc...@ti.com
is not
sufficient to tell if we have received the correct irq, i.e, we shouldn't
proceed ahead if we get a VSYNC interrupt for LCD2 manager, or a VSYNC2
interrupt for LCD manager.
Fix this by correlating LCD manager to VSYNC interrupt and LCD2 manager
to VSYNC2 interrupt.
Signed-off-by: Archit Taneja arc
mode.
Signed-off-by: Archit Taneja arc...@ti.com
---
drivers/media/video/omap/omap_vout.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/media/video/omap/omap_vout.c
b/drivers/media/video/omap/omap_vout.c
index 20638c3..51cf6c2 100644
--- a/drivers/media/video/omap
by DSS2. This
leads to a crash at probe.
Signed-off-by: Archit Taneja arc...@ti.com
---
drivers/media/video/omap/omap_vout.c |8
1 files changed, 0 insertions(+), 8 deletions(-)
diff --git a/drivers/media/video/omap/omap_vout.c
b/drivers/media/video/omap/omap_vout.c
index 51cf6c2
Hi,
On Tuesday 20 September 2011 01:06 AM, Hiremath, Vaibhav wrote:
-Original Message-
From: Taneja, Archit
Sent: Friday, September 16, 2011 12:09 PM
To: Valkeinen, Tomi
Cc: Hiremath, Vaibhav; linux-o...@vger.kernel.org; Taneja, Archit; linux-
me...@vger.kernel.org; Molnar, Lajos
Hi,
On Wednesday 21 September 2011 03:35 PM, Hiremath, Vaibhav wrote:
-Original Message-
From: Taneja, Archit
Sent: Friday, September 16, 2011 3:31 PM
To: Hiremath, Vaibhav
Cc: Valkeinen, Tomi; linux-o...@vger.kernel.org; Semwal, Sumit; linux-
me...@vger.kernel.org; Taneja, Archit
Hi,
On Wednesday 21 September 2011 02:10 PM, Hiremath, Vaibhav wrote:
-Original Message-
From: Taneja, Archit
Sent: Friday, September 16, 2011 3:30 PM
To: Hiremath, Vaibhav
Cc: Valkeinen, Tomi; linux-o...@vger.kernel.org; Semwal, Sumit; linux-
me...@vger.kernel.org; Taneja, Archit
Hi,
On Wednesday 21 September 2011 07:04 PM, Hiremath, Vaibhav wrote:
-Original Message-
From: Taneja, Archit
Sent: Friday, September 16, 2011 3:31 PM
To: Hiremath, Vaibhav
Cc: Valkeinen, Tomi; linux-o...@vger.kernel.org; Semwal, Sumit; linux-
me...@vger.kernel.org; Taneja, Archit
Hi,
On Wednesday 21 September 2011 04:15 PM, Taneja, Archit wrote:
Hi,
On Wednesday 21 September 2011 03:35 PM, Hiremath, Vaibhav wrote:
-Original Message-
From: Taneja, Archit
Sent: Friday, September 16, 2011 3:31 PM
To: Hiremath, Vaibhav
Cc: Valkeinen, Tomi;
driver. Use
overlay cap OMAP_DSS_OVL_CAP_GLOBAL_ALPHA to check if overlay supports alpha
blending or not. Replace this with checks for VIDEO1 pipeline.
Cc: linux-media@vger.kernel.org
Cc: Lajos Molnar mol...@ti.com
Signed-off-by: Archit Taneja arc...@ti.com
---
Changes in v3:
- Fix some spelling
:~boddob/linux-omap-dss2/archit-dss2-clone.git
'for_omap_vout2'
Archit Taneja (5):
OMAP_VOUT: Fix check in reqbuf for buf_size allocation
OMAP_VOUT: CLEANUP: Remove redundant code from omap_vout_isr
OMAP_VOUT: Fix VSYNC IRQ handling in omap_vout_isr
OMAP_VOUT: Add support for DSI panels
in reqbuf. When the video
device is opened the next time, this check will prevent us to allocate a buffer
which is larger than what we requested the last time.
Don't use vout-buffer_size, always check with the parameters video1_bufsize
or video2_bufsize.
Signed-off-by: Archit Taneja arc...@ti.com
Currently, there is a lot of redundant code is between DPI and VENC panels, this
can be made common by moving out field/interlace specific code to a separate
function called omapvid_handle_interlace_display(). There is no functional
change made.
Signed-off-by: Archit Taneja arc...@ti.com
is not
sufficient to tell if we have received the correct irq, i.e, we shouldn't
proceed ahead if we get a VSYNC interrupt for LCD2 manager, or a VSYNC2
interrupt for LCD manager.
Fix this by correlating LCD manager to VSYNC interrupt and LCD2 manager
to VSYNC2 interrupt.
Signed-off-by: Archit Taneja arc
mode.
Signed-off-by: Archit Taneja arc...@ti.com
---
drivers/media/video/omap/omap_vout.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/media/video/omap/omap_vout.c
b/drivers/media/video/omap/omap_vout.c
index a0ca5f5..df0713c 100644
--- a/drivers/media/video/omap
by DSS2. This
leads to a crash at probe.
Signed-off-by: Archit Taneja arc...@ti.com
---
drivers/media/video/omap/omap_vout.c |8
1 files changed, 0 insertions(+), 8 deletions(-)
diff --git a/drivers/media/video/omap/omap_vout.c
b/drivers/media/video/omap/omap_vout.c
index df0713c
for DSI panels
Changes in v3:
- Remove patch OMAP_VOUT: Fix VSYNC IRQ handling in omap_vout_isr since its
still not clear whether its needed or not.
Refernce base:
g...@gitorious.org:~boddob/linux-omap-dss2/archit-dss2-clone.git
'for_omap_vout2'
Archit Taneja (4):
OMAP_VOUT: Fix check in reqbuf
in reqbuf. When the video
device is opened the next time, this check will prevent us to allocate a buffer
which is larger than what we requested the last time.
Don't use vout-buffer_size, always check with the parameters video1_bufsize
or video2_bufsize.
Signed-off-by: Archit Taneja arc...@ti.com
Currently, there is a lot of redundant code is between DPI and VENC panels, this
can be made common by moving out field/interlace specific code to a separate
function called omapvid_handle_interlace_display(). There is no functional
change made.
Signed-off-by: Archit Taneja arc...@ti.com
mode.
Signed-off-by: Archit Taneja arc...@ti.com
---
drivers/media/video/omap/omap_vout.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/media/video/omap/omap_vout.c
b/drivers/media/video/omap/omap_vout.c
index 01c24a4..7b8e87a 100644
--- a/drivers/media/video/omap
by DSS2. This
leads to a crash at probe.
Signed-off-by: Archit Taneja arc...@ti.com
---
drivers/media/video/omap/omap_vout.c |8
1 files changed, 0 insertions(+), 8 deletions(-)
diff --git a/drivers/media/video/omap/omap_vout.c
b/drivers/media/video/omap/omap_vout.c
index 7b8e87a
On Tuesday 27 September 2011 12:24 PM, Hiremath, Vaibhav wrote:
-Original Message-
From: Valkeinen, Tomi
Sent: Tuesday, September 27, 2011 12:19 PM
To: Hiremath, Vaibhav
Cc: Semwal, Sumit; Taneja, Archit; linux-o...@vger.kernel.org; linux-
me...@vger.kernel.org
Subject: RE: [PATCH 3/5]
On Tuesday 27 September 2011 11:40 AM, Valkeinen, Tomi wrote:
On Mon, 2011-09-26 at 17:29 +0530, Archit Taneja wrote:
Remove the code in omap_vout_probe() which calls display-driver-update() for
all the displays. This isn't correct because:
- An update in probe doesn't make sense, because we
On Tuesday 27 September 2011 12:37 PM, Valkeinen, Tomi wrote:
On Tue, 2011-09-27 at 12:32 +0530, Archit Taneja wrote:
On Tuesday 27 September 2011 11:40 AM, Valkeinen, Tomi wrote:
On Mon, 2011-09-26 at 17:29 +0530, Archit Taneja wrote:
Remove the code in omap_vout_probe() which calls display
Archit Taneja (5):
OMAP_VOUT: Fix check in reqbuf for buf_size allocation
OMAP_VOUT: CLEANUP: Remove redundant code from omap_vout_isr
OMAP_VOUT: Fix VSYNC IRQ handling in omap_vout_isr
OMAP_VOUT: Add support for DSI panels
OMAP_VOUT: Increase MAX_DISPLAYS to a larger value
drivers/media
.
Signed-off-by: Archit Taneja arc...@ti.com
---
drivers/media/video/omap/omap_vout.c |6 +-
1 files changed, 5 insertions(+), 1 deletions(-)
diff --git a/drivers/media/video/omap/omap_vout.c
b/drivers/media/video/omap/omap_vout.c
index d9e64f3..e64a83c 100644
--- a/drivers/media/video/omap
Currently, there is a lot of redundant code is between DPI and VENC panels, this
can be made common by moving out field/interlace specific code to a separate
function called omapvid_handle_interlace_display(). There is no functional
change made.
Signed-off-by: Archit Taneja arc...@ti.com
is not
sufficient to tell if we have received the correct irq, i.e, we shouldn't
proceed ahead if we get a VSYNC interrupt for LCD2 manager, or a VSYNC2
interrupt for LCD manager.
Fix this by correlating LCD manager to VSYNC interrupt and LCD2 manager
to VSYNC2 interrupt.
Signed-off-by: Archit Taneja arc
mode.
Signed-off-by: Archit Taneja arc...@ti.com
---
drivers/media/video/omap/omap_vout.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/media/video/omap/omap_vout.c
b/drivers/media/video/omap/omap_vout.c
index 6bc2620..65374b5 100644
--- a/drivers/media/video/omap
for more than 3
displays.
Signed-off-by: Archit Taneja arc...@ti.com
---
drivers/media/video/omap/omap_voutdef.h |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/media/video/omap/omap_voutdef.h
b/drivers/media/video/omap/omap_voutdef.h
index d793501..27a95d2 100644
rotation. A member rotation_type is introduced in
omapvideo_info, this allows to call vrfb specific functions only if the rotation
type is VOUT_ROT_VRFB. When the rotation_type is set to VOUT_ROT_NONE, the
S_CTRL ioctl prevents the user setting a non zero rotation or non zero mirror
value.
Archit Taneja
Move some inline functions from omap_vout.c to omap_voutdef.h and independent
functions like omap_vout_alloc_buffer/omap_vout_free_buffer to omap_voutlib.c.
Signed-off-by: Archit Taneja arc...@ti.com
---
drivers/media/video/omap/omap_vout.c| 109 ---
drivers
on the arch type in omap_vout_probe. The rotation_type
var is now used to choose between vrfb and non-vrfb calls.
Signed-off-by: Archit Taneja arc...@ti.com
---
drivers/media/video/omap/Kconfig |7 +-
drivers/media/video/omap/Makefile |1 +
drivers/media/video/omap
Hi,
On Tuesday 07 June 2011 02:35 PM, Hiremath, Vaibhav wrote:
-Original Message-
From: Taneja, Archit
Sent: Friday, May 27, 2011 12:31 PM
To: linux-media@vger.kernel.org
Cc: Hiremath, Vaibhav; Taneja, Archit
Subject: [PATCH 1/2] OMAP_VOUT: CLEANUP: Move some functions and macros
from
Hi Vaibhav,
On Friday 27 May 2011 12:31 PM, Taneja, Archit wrote:
Introduce omap_vout_vrfb.c and omap_vout_vrfb.h, for all VRFB related API's,
making OMAP_VOUT driver independent from VRFB. This is required for OMAP4 DSS,
since OMAP4 doesn't have VRFB block.
Added new enum vout_rotation_type
On Monday 13 June 2011 10:13 AM, Hiremath, Vaibhav wrote:
-Original Message-
From: Taneja, Archit
Sent: Monday, June 13, 2011 10:17 AM
To: Hiremath, Vaibhav
Cc: linux-media@vger.kernel.org
Subject: Re: [PATCH 2/2] OMAP_VOUT: Create separate file for VRFB related
API's
Hi Vaibhav,
On
v1:
- add a patch to make rotation related functions names more descriptive.
- remove unnecessary externs, add static to some local functions.
- improve patch description.
Archit Taneja (3):
OMAP_VOUT: CLEANUP: Move generic functions and macros to common files
OMAP_VOUT: CLEANUP: Make rotation
Add static identifier to functions that are used locally in omap_vout.c
Signed-off-by: Archit Taneja arc...@ti.com
---
drivers/media/video/omap/omap_vout.c| 117 +-
drivers/media/video/omap/omap_voutdef.h | 62
drivers/media/video/omap
Rename rotation_enabled() and rotate_90_or_270() to is_rotation_enabled()
and is_rotation_90_or_270() to make them more descriptive.
Signed-off-by: Archit Taneja arc...@ti.com
---
drivers/media/video/omap/omap_vout.c| 26 +-
drivers/media/video/omap/omap_voutdef.h
on the arch type in omap_vout_probe. The rotation_type
var is now used to choose between vrfb and non-vrfb calls.
Signed-off-by: Archit Taneja arc...@ti.com
---
drivers/media/video/omap/Kconfig |7 +-
drivers/media/video/omap/Makefile |1 +
drivers/media/video/omap
Hi,
On Friday 17 June 2011 01:44 AM, Hiremath, Vaibhav wrote:
From: Vaibhav Hiremathhvaib...@ti.com
The usecase where, user allocates small size of buffer
through bootargs (video1_bufsize/video2_bufsize) and later from application
tries to set the format which requires larger buffer size,
Hi,
On Friday 17 June 2011 03:33 PM, Hiremath, Vaibhav wrote:
-Original Message-
From: Taneja, Archit
Sent: Friday, June 17, 2011 2:16 PM
To: Hiremath, Vaibhav
Cc: linux-media@vger.kernel.org; mche...@redhat.com; hverk...@xs4all.nl
Subject: Re: [PATCH] omap_vout: Added check in reqbuf
Hi,
On Friday 17 June 2011 03:53 PM, Hiremath, Vaibhav wrote:
-Original Message-
From: Taneja, Archit
Sent: Friday, June 17, 2011 3:57 PM
To: Hiremath, Vaibhav
Cc: linux-media@vger.kernel.org; mche...@redhat.com; hverk...@xs4all.nl
Subject: Re: [PATCH] omap_vout: Added check in reqbuf
Hi,
On Friday 01 July 2011 04:44 PM, Mauro Carvalho Chehab wrote:
Em 01-07-2011 19:49, Archit Taneja escreveu:
Hi,
On Friday 01 July 2011 11:48 AM, Mauro Carvalho Chehab wrote:
Em 22-06-2011 16:32, hvaib...@ti.com escreveu:
The following changes since commit
The DSS2 driver does not support the configuration of the update_mode of a
panel anymore. Remove the setting of update_mode done in omap_vout_probe().
Ignore configuration of TE since omap_vout driver doesn't support manual update
displays anyway.
Signed-off-by: Archit Taneja arc...@ti.com
.
These changes are required as the DSS2 driver since 3.3 kernel doesn't let you
set the overlay info with paddr as 0.
Signed-off-by: Archit Taneja arc...@ti.com
---
drivers/media/video/omap/omap_vout.c | 36 -
1 files changed, 5 insertions(+), 31 deletions(-)
diff
On Monday 12 March 2012 03:34 PM, Hiremath, Vaibhav wrote:
On Wed, Mar 07, 2012 at 14:31:16, Taneja, Archit wrote:
The omap_vout driver tries to set the DSS overlay_info using set_overlay_info()
when the physical address for the overlay is still not configured. This happens
in omap_vout_probe()
Hi,
On Friday 16 March 2012 03:46 PM, Archit Taneja wrote:
On Monday 12 March 2012 03:34 PM, Hiremath, Vaibhav wrote:
On Wed, Mar 07, 2012 at 14:31:16, Taneja, Archit wrote:
The omap_vout driver tries to set the DSS overlay_info using
set_overlay_info()
when the physical address
On Monday 19 March 2012 02:15 PM, Hiremath, Vaibhav wrote:
On Fri, Mar 16, 2012 at 16:41:27, Taneja, Archit wrote:
Hi,
On Friday 16 March 2012 03:46 PM, Archit Taneja wrote:
On Monday 12 March 2012 03:34 PM, Hiremath, Vaibhav wrote:
On Wed, Mar 07, 2012 at 14:31:16, Taneja, Archit wrote
Hi Hans,
On Thursday 29 August 2013 06:58 PM, Hans Verkuil wrote:
On Thu 29 August 2013 14:32:49 Archit Taneja wrote:
VPE is a block which consists of a single memory to memory path which can
perform chrominance up/down sampling, de-interlacing, scaling, and color space
conversion of raster
all the output channel DMAs.
- Removed the DT and hwmod patches from this series. DRA7xx support is not
yet got in the 3.12 merge window. Will deal with those separately.
Archit Taneja (4):
v4l: ti-vpe: Create a vpdma helper library
v4l: ti-vpe: Add helpers for creating VPDMA descriptors
, this function will take care
of loading VPDMA firmware and returning a vpdma_data instance back to the VPE
driver. The VIP driver will also call the same init function to initialize
it's
own VPDMA instance.
Signed-off-by: Archit Taneja arc...@ti.com
---
drivers/media/platform/ti-vpe/vpdma.c
the descriptors in a way such that it's easy to see
the values of different fields in the descriptors.
Signed-off-by: Archit Taneja arc...@ti.com
---
drivers/media/platform/ti-vpe/vpdma.c | 268 +++
drivers/media/platform/ti-vpe/vpdma.h | 48 +++
drivers/media/platform/ti-vpe
ports.
Signed-off-by: Archit Taneja arc...@ti.com
---
drivers/media/platform/ti-vpe/vpe.c | 392
1 file changed, 358 insertions(+), 34 deletions(-)
diff --git a/drivers/media/platform/ti-vpe/vpe.c
b/drivers/media/platform/ti-vpe/vpe.c
index 549681e..a892b69
Hi Hans, Laurent,
On Friday 06 September 2013 03:42 PM, Archit Taneja wrote:
VPE(Video Processing Engine) is an IP found on DRA7xx, this series adds VPE as a
mem to mem v4l2 driver, and VPDMA as a helper library.
The first version of the patch series described VPE in detail, you can have
Hi,
On Friday 20 September 2013 04:41 AM, Russell King wrote:
The correct way for a driver to specify the coherent DMA mask is
not to directly access the field in the struct device, but to use
dma_set_coherent_mask(). Only arch and bus code should access this
member directly.
Convert all
Hi,
On Monday 16 September 2013 12:29 PM, Archit Taneja wrote:
Hi Hans, Laurent,
On Friday 06 September 2013 03:42 PM, Archit Taneja wrote:
VPE(Video Processing Engine) is an IP found on DRA7xx, this series
adds VPE as a
mem to mem v4l2 driver, and VPDMA as a helper library.
The first
On Monday 07 October 2013 01:25 PM, Hans Verkuil wrote:
Hi Archit,
I've got a few comments below...
On 09/06/2013 12:12 PM, Archit Taneja wrote:
VPE is a block which consists of a single memory to memory path which can
perform chrominance up/down sampling, de-interlacing, scaling, and color
On Monday 07 October 2013 03:04 PM, Hans Verkuil wrote:
On 10/07/2013 11:16 AM, Archit Taneja wrote:
On Monday 07 October 2013 01:25 PM, Hans Verkuil wrote:
Hi Archit,
I've got a few comments below...
On 09/06/2013 12:12 PM, Archit Taneja wrote:
VPE is a block which consists of a single
On Monday 07 October 2013 07:32 PM, Hans Verkuil wrote:
On 10/07/2013 12:22 PM, Archit Taneja wrote:
On Monday 07 October 2013 03:04 PM, Hans Verkuil wrote:
On 10/07/2013 11:16 AM, Archit Taneja wrote:
On Monday 07 October 2013 01:25 PM, Hans Verkuil wrote:
Hi Archit,
I've got a few
Hi Hans,
On Friday 11 October 2013 01:16 PM, Hans Verkuil wrote:
On 10/09/2013 04:29 PM, Archit Taneja wrote:
VPE is a block which consists of a single memory to memory path which can
perform chrominance up/down sampling, de-interlacing, scaling, and color space
conversion of raster or tiled
/15/2013 03:47 PM, Archit Taneja wrote:
Hi Hans,
On Friday 11 October 2013 01:16 PM, Hans Verkuil wrote:
On 10/09/2013 04:29 PM, Archit Taneja wrote:
VPE is a block which consists of a single memory to memory path
which can perform chrominance up/down sampling, de-interlacing,
scaling, and color
in v5:
- updated how pix-colorspace is set.
- adds comments on what our private control ID is used for.
Archit Taneja (4):
v4l: ti-vpe: Create a vpdma helper library
v4l: ti-vpe: Add helpers for creating VPDMA descriptors
v4l: ti-vpe: Add VPE mem to mem driver
v4l: ti-vpe: Add de
the descriptors in a way such that it's easy to see
the values of different fields in the descriptors.
Acked-by: Hans Verkuil hans.verk...@cisco.com
Signed-off-by: Archit Taneja arc...@ti.com
---
drivers/media/platform/ti-vpe/vpdma.c | 268 +++
drivers/media/platform/ti-vpe/vpdma.h
ports.
Acked-by: Hans Verkuil hans.verk...@cisco.com
Signed-off-by: Archit Taneja arc...@ti.com
---
drivers/media/platform/ti-vpe/vpe.c | 392
1 file changed, 358 insertions(+), 34 deletions(-)
diff --git a/drivers/media/platform/ti-vpe/vpe.c
b/drivers/media
, this function will take care
of loading VPDMA firmware and returning a vpdma_data instance back to the VPE
driver. The VIP driver will also call the same init function to initialize
it's
own VPDMA instance.
Acked-by: Hans Verkuil hans.verk...@cisco.com
Signed-off-by: Archit Taneja arc...@ti.com
Hi,
On Friday 18 October 2013 03:46 AM, Jan Kara wrote:
Hello,
I was auditing get_user_pages() users and I've noticed that
omap_vout_uservirt_to_phys() is apparently called for arbitrary address
passed from userspace. If this address is in VM_IO vma, we use
vma-vm_pgoff for mapping the
On Friday 18 October 2013 06:41 PM, Jan Kara wrote:
On Fri 18-10-13 14:59:17, Archit Taneja wrote:
Hi,
On Friday 18 October 2013 03:46 AM, Jan Kara wrote:
Hello,
I was auditing get_user_pages() users and I've noticed that
omap_vout_uservirt_to_phys() is apparently called for arbitrary
.
On Friday 02 August 2013 19:33:43 Archit Taneja wrote:
Add a DT node for VPE in dra7.dtsi. This is experimental because we might
need to split the VPE address space a bit more, and also because the IRQ
line described is accessible the IRQ crossbar driver is added for DRA7XX.
Cc: Rajendra Nayak rna
.
Reviewed-by: Archit Taneja arc...@ti.com
Thanks,
Archit
Signed-off-by: Wei Yongjun yongjun_...@trendmicro.com.cn
---
drivers/media/platform/ti-vpe/vpe.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/media/platform/ti-vpe/vpe.c
b/drivers/media/platform/ti-vpe
.
Reviewed-by: Archit Taneja arc...@ti.com
Thanks,
Archit
Signed-off-by: Wei Yongjun yongjun_...@trendmicro.com.cn
---
drivers/media/platform/ti-vpe/vpe.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/media/platform/ti-vpe/vpe.c
b/drivers/media/platform/ti-vpe
On Wednesday 30 October 2013 08:40 AM, Wei Yongjun wrote:
From: Wei Yongjun yongjun_...@trendmicro.com.cn
Fix to return a negative error code from the error handling
case instead of 0, as done elsewhere in this function.
Reviewed-by: Archit Taneja arc...@ti.com
Thanks,
Archit
Signed-off
Hi Dan,
On Friday 08 November 2013 03:31 PM, Dan Carpenter wrote:
devm_ioremap() returns NULL on error, it doesn't return an ERR_PTR.
Signed-off-by: Dan Carpenter dan.carpen...@oracle.com
diff --git a/drivers/media/platform/ti-vpe/vpe.c
b/drivers/media/platform/ti-vpe/vpe.c
index
Hi Laurent,
On Friday 09 August 2013 03:41 AM, Laurent Pinchart wrote:
Hi Archit,
Thank you for the patch.
On Friday 02 August 2013 19:33:43 Archit Taneja wrote:
Add a DT node for VPE in dra7.dtsi. This is experimental because we might
need to split the VPE address space a bit more, and also
-by: Archit Taneja arc...@ti.com
---
drivers/media/platform/ti-vpe/vpdma.c | 4 +--
drivers/media/platform/ti-vpe/vpdma.h | 5 +++-
drivers/media/platform/ti-vpe/vpe.c | 53 ++-
3 files changed, 46 insertions(+), 16 deletions(-)
diff --git a/drivers/media/platform
in for the 3.13-rc fixes.
Archit Taneja (2):
v4l: ti-vpe: Fix the data_type value for UYVY VPDMA format
v4l: ti-vpe: make sure VPDMA line stride constraints are met
drivers/media/platform/ti-vpe/vpdma.c | 4 +--
drivers/media/platform/ti-vpe/vpdma.h | 5 ++-
drivers/media/platform/ti
The data_type value to be programmed in the data descriptors to fetch/write a
UYVY buffer was not mentioned correctly in the older DRA7x documentation. This
caused VPE to fail with UYVY color formats.
Update the data_type value to fix functionality when UYVY format is used.
Signed-off-by: Archit
. This requires configuring the
output data descriptors differently.
Also, make the default colorspace V4L2_COLORSPACE_SMPTE170M as that resembles
the Standard Definition colorspace more closely.
Signed-off-by: Archit Taneja arc...@ti.com
---
drivers/media/platform/ti-vpe/vpe.c | 95
relative to the sub-block, and not the
VPE IP as a whole. In order for VPDMA to configure registers, it requires it's
offset from the top level VPE module. A macro called GET_OFFSET_TOP is added to
return the offset of the register relative to the VPE IP.
Signed-off-by: Archit Taneja arc...@ti.com
to get the CSC register offset relative to the
VPE IP in the vpe driver.
Signed-off-by: Archit Taneja arc...@ti.com
---
drivers/media/platform/ti-vpe/Makefile | 2 +-
drivers/media/platform/ti-vpe/csc.c | 76
drivers/media/platform/ti-vpe/csc.h | 65
case, and possibly more
cases in the future.
Signed-off-by: Archit Taneja arc...@ti.com
---
drivers/media/platform/ti-vpe/vpdma.c | 36 +--
drivers/media/platform/ti-vpe/vpdma.h | 7 +++
2 files changed, 41 insertions(+), 2 deletions(-)
diff --git a/drivers/media
-off-by: Archit Taneja arc...@ti.com
---
drivers/media/platform/ti-vpe/sc.c | 132 ++--
drivers/media/platform/ti-vpe/sc.h | 4 +-
drivers/media/platform/ti-vpe/vpe.c | 24 +--
3 files changed, 149 insertions(+), 11 deletions(-)
diff --git a/drivers/media
on the branch:
git://linuxtv.org/media_tree.git master
Archit Taneja (8):
v4l: ti-vpe: create a scaler block library
v4l: ti-vpe: support loading of scaler coefficients
v4l: ti-vpe: make vpe driver load scaler coefficients
v4l: ti-vpe: enable basic scaler support
v4l: ti-vpe: create a color space
1 - 100 of 218 matches
Mail list logo
