Each dma-buf has an associated size and it's reasonable for userspace
to want to know what it is.
Since userspace already has an fd, expose the size using the
size = lseek(fd, SEEK_END, 0); lseek(fd, SEEK_CUR, 0);
idiom.
Signed-off-by: Christopher James Halse Rogers
Hi Hans,
Thanks for the patch, this will still simplify driver writing :-)
On Mon, Jul 29, 2013 at 6:10 PM, Hans Verkuil hverk...@xs4all.nl wrote:
From: Hans Verkuil hans.verk...@cisco.com
This module makes it easy to filter valid timings from the full list of
CEA and DMT timings based on
Hi Hans,
Thanks for the patch.
On Mon, Jul 29, 2013 at 6:10 PM, Hans Verkuil hverk...@xs4all.nl wrote:
From: Hans Verkuil hans.verk...@cisco.com
v4l2-common.c contained a bunch of dv-timings related functions.
Move that to the new v4l2-dv-timings.c which is a more appropriate
place for
Hi Hans,
Thanks for the patch.
On Mon, Jul 29, 2013 at 6:10 PM, Hans Verkuil hverk...@xs4all.nl wrote:
From: Hans Verkuil hans.verk...@cisco.com
It is very common to have to calculate the total width and height of the
blanking and the full frame, so add a few defines that deal with that.
Hi Hans,
Thanks for the patch.
On Mon, Jul 29, 2013 at 6:10 PM, Hans Verkuil hverk...@xs4all.nl wrote:
From: Hans Verkuil hans.verk...@cisco.com
Use the new defines to calculate the full blanking and frame sizes.
Signed-off-by: Hans Verkuil hans.verk...@cisco.com
Cc: Lad, Prabhakar
Hi Sylwester,
On 2 August 2013 16:28, Sylwester Nawrocki s.nawro...@samsung.com wrote:
Hi Vikas,
On 08/02/2013 12:10 PM, Vikas Sajjan wrote:
yeah, we could not allocate CMA region for FIMD, because the function
dma_declare_contiguous() needs dev as the first argument and we have
access to
On Saturday, August 03, 2013 12:19:54 AM you wrote:
Hello,
diff --git a/utils/qv4l2/Makefile.am b/utils/qv4l2/Makefile.am
index 22d4c17..eed25b0 100644
--- a/utils/qv4l2/Makefile.am
+++ b/utils/qv4l2/Makefile.am
@@ -4,7 +4,8 @@ qv4l2_SOURCES = qv4l2.cpp general-tab.cpp ctrl-tab.cpp
Hi,
On 02/08/13 17:03, Archit Taneja wrote:
+struct vpdma_data_format vpdma_yuv_fmts[] = {
+ [VPDMA_DATA_FMT_Y444] = {
+ .data_type = DATA_TYPE_Y444,
+ .depth = 8,
+ },
This, and all the other tables, should probably be consts?
+static void
Hi Hans,
Thanks for the patch.
On Mon, Jul 29, 2013 at 6:11 PM, Hans Verkuil hverk...@xs4all.nl wrote:
From: Hans Verkuil hans.verk...@cisco.com
Use the new blanking and frame size defines. This also fixed a bug in
these drivers: they assumed that the height for interlaced formats was
the
Fixed the YUY2 shaders to support scaling.
The new solution has cleaner shader code and texture upload
uses a better format for OpenGL.
Signed-off-by: Bård Eirik Winther bwint...@cisco.com
---
utils/qv4l2/capture-win-gl.cpp | 68 ++
1 file changed, 35
Created a function to get the total margins (window frame) in pixels
outside the actual video frame beeing displayed.
Signed-off-by: Bård Eirik Winther bwint...@cisco.com
---
utils/qv4l2/capture-win.cpp | 14 ++
utils/qv4l2/capture-win.h | 2 ++
2 files changed, 12 insertions(+),
Fixes the issue when the window was beeing resized/moved
and the frame image would become black.
Signed-off-by: Bård Eirik Winther bwint...@cisco.com
---
utils/qv4l2/capture-win-gl.cpp | 6 ++
1 file changed, 6 insertions(+)
diff --git a/utils/qv4l2/capture-win-gl.cpp
Signed-off-by: Bård Eirik Winther bwint...@cisco.com
---
utils/qv4l2/capture-win.cpp | 24 ++--
utils/qv4l2/capture-win.h | 8 +++-
utils/qv4l2/general-tab.cpp | 36
utils/qv4l2/general-tab.h | 3 +++
utils/qv4l2/qv4l2.cpp |
Signed-off-by: Bård Eirik Winther bwint...@cisco.com
---
utils/qv4l2/qv4l2.cpp | 77 ++-
utils/qv4l2/qv4l2.h | 2 +-
2 files changed, 41 insertions(+), 38 deletions(-)
diff --git a/utils/qv4l2/qv4l2.cpp b/utils/qv4l2/qv4l2.cpp
index
Adds hotkey CTRL + F for both CaptureWin and main Capture menu.
Resets the scaling of CaptureWin to fit frame size.
Signed-off-by: Bård Eirik Winther bwint...@cisco.com
---
utils/qv4l2/capture-win.cpp | 3 +++
utils/qv4l2/capture-win.h | 1 +
utils/qv4l2/qv4l2.cpp | 1 +
3 files changed,
Signed-off-by: Bård Eirik Winther bwint...@cisco.com
---
utils/qv4l2/capture-win-gl.cpp | 26 --
utils/qv4l2/capture-win-gl.h | 8
utils/qv4l2/capture-win-qt.cpp | 24 +-
utils/qv4l2/capture-win-qt.h | 5 ++
utils/qv4l2/capture-win.cpp| 106
The patch series depends on the qv4l2 ALSA and OpenGL patch series.
This adds scaling and aspect ratio support to the qv4l2 CaptureWin.
It also fixes some issues with the original OpenGL patch series,
as well as adding tweaks and improvements left out in the original patches.
Some of the
On 02/08/13 17:03, Archit Taneja wrote:
Create functions which the VPE driver can use to create a VPDMA descriptor and
add it to a VPDMA descriptor list. These functions take a pointer to an
existing
list, and append the configuration/data/control descriptor header to the list.
In the case
On 02/08/13 17:03, 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 YUV420 coplanar, YUV422 coplanar or YUV422
interleaved video formats.
Hi Bård,
Some comments below...
On 08/05/2013 10:56 AM, Bård Eirik Winther wrote:
Signed-off-by: Bård Eirik Winther bwint...@cisco.com
---
utils/qv4l2/capture-win.cpp | 24 ++--
utils/qv4l2/capture-win.h | 8 +++-
utils/qv4l2/general-tab.cpp | 36
While trying to get boot-logo up on exynos5420 SMDK which has eDP panel
connected with resolution 2560x1600, following error occured even with
IOMMU enabled:
[0.88] [drm:lowlevel_buffer_allocate] *ERROR* failed to allocate buffer.
[0.89] [drm] Initialized exynos 1.0.0 20110530 on minor 0
Hi Sylwester,
Thank you for the review.
Will address all your review comments.
Some responses below:
[snip]
+
+static int fimc_md_register_sensor_entities(struct fimc_md *fmd)
+{
+ struct device_node *of_node = fmd-pdev-dev.of_node;
+ int ret;
+
+ /*
+* Runtime
Hi Sachin,
Thank you for the review.
On Mon, Aug 5, 2013 at 10:51 AM, Sachin Kamat sachin.ka...@linaro.org wrote:
On 2 August 2013 20:32, Arun Kumar K arun...@samsung.com wrote:
From: Shaik Ameer Basha shaik.am...@samsung.com
This patch adds support for media device for EXYNOS5 SoCs.
The
Hi Arun,
On 08/05/2013 12:06 PM, Arun Kumar K wrote:
Hi Sylwester,
Thank you for the review.
Will address all your review comments.
Some responses below:
Thanks, it took me a while to review this nearly 10k of code.
But fortunately I could spent some more time at the computer
this weekend
Hi Sachin,
On 08/05/2013 07:12 AM, Sachin Kamat wrote:
On 2 August 2013 12:02, Sachin Kamat sachin.ka...@linaro.org wrote:
__is_set_init_isp_aa and fimc_is_hw_set_tune currently do not have
any callers. However these functions may be used in the future. Hence
instead of deleting them,
On Monday 05 August 2013 01:43 PM, Tomi Valkeinen wrote:
Hi,
On 02/08/13 17:03, Archit Taneja wrote:
+struct vpdma_data_format vpdma_yuv_fmts[] = {
+ [VPDMA_DATA_FMT_Y444] = {
+ .data_type = DATA_TYPE_Y444,
+ .depth = 8,
+ },
This, and
On Sun, Aug 04, 2013 at 01:56:49PM +0100, Rajil Saraswat wrote:
Hi,
I have a HP MCE ir transreceiver which is recognised as Fintek device.
The receiver works fine, however the transmitter only works when there
is no X session running.
When X is stopped and the following command is
Hi Sylwester,
On 5 August 2013 16:35, Sylwester Nawrocki s.nawro...@samsung.com wrote:
Hi Sachin,
On 08/05/2013 07:12 AM, Sachin Kamat wrote:
On 2 August 2013 12:02, Sachin Kamat sachin.ka...@linaro.org wrote:
__is_set_init_isp_aa and fimc_is_hw_set_tune currently do not have
any callers.
On Monday 05 August 2013 02:41 PM, Tomi Valkeinen wrote:
On 02/08/13 17:03, Archit Taneja wrote:
Create functions which the VPE driver can use to create a VPDMA descriptor and
add it to a VPDMA descriptor list. These functions take a pointer to an existing
list, and append the
On 05/08/13 14:26, Archit Taneja wrote:
On Monday 05 August 2013 01:43 PM, Tomi Valkeinen wrote:
+/*
+ * submit a list of DMA descriptors to the VPE VPDMA, do not wait
for completion
+ */
+int vpdma_submit_descs(struct vpdma_data *vpdma, struct
vpdma_desc_list *list)
+{
+/* we always
MFC driver use custom bindings for managing reserved memory. Those bindings
are not really specific to MFC device and no even well discussed. They can
be easily replaced with generic, platform independent code for handling
reserved and contiguous memory.
Two additional child devices for each
This patch removes custom initialization of reserved memory regions from
s5p-mfc driver. Memory initialization can be now handled by generic
code.
Signed-off-by: Marek Szyprowski m.szyprow...@samsung.com
---
drivers/media/platform/s5p-mfc/s5p_mfc.c | 75 ++
1 file
Hello,
This patch series are an attempt to cleanup the reserved memory device
tree bindings for MFC device. MFC device has two memory ports (AXI
masters), which are used to do DMA. Usually separate memory regions are
being defined for each of those memory ports to improve performance.
Some
On 05/08/13 15:05, Archit Taneja wrote:
On Monday 05 August 2013 02:41 PM, Tomi Valkeinen wrote:
There's quite a bit of code in these dump functions, and they are always
called. I'm sure getting that data is good for debugging, but I presume
they are quite useless for normal use. So I think
I seek your consent to present you as the next of kin to the account
of a deceased client for claims valued at Fourteen million, three
hundred thousand Pounds.
Contact me through my private email for details: halawani@ovi.com
Mr. Halawani, Azhar Abdulrahim.
Solicitors Legal Services
On Mon, Aug 5, 2013 at 5:44 AM, Vikas Sajjan vikas.saj...@linaro.org wrote:
While trying to get boot-logo up on exynos5420 SMDK which has eDP panel
connected with resolution 2560x1600, following error occured even with
IOMMU enabled:
[0.88] [drm:lowlevel_buffer_allocate] *ERROR* failed to
On Monday 05 of August 2013 15:14:42 Vikas Sajjan wrote:
While trying to get boot-logo up on exynos5420 SMDK which has eDP panel
connected with resolution 2560x1600, following error occured even with
IOMMU enabled:
[0.88] [drm:lowlevel_buffer_allocate] *ERROR* failed to allocate
buffer.
Hi Sylwester,
On Sun, Aug 4, 2013 at 3:12 AM, Sylwester Nawrocki
sylvester.nawro...@gmail.com wrote:
On 08/02/2013 05:02 PM, Arun Kumar K wrote:
This driver is for the FIMC-IS IP available in Samsung Exynos5
SoC onwards. This patch adds the core files for the new driver.
Signed-off-by: Arun
Hello Julia,
IMHO keep the patch as it is.
It does not change any code that is good.
Suspicious code that comes up here can be addressed
in a separate patch.
just my 2 cents,
re,
wh
Am 05.08.2013 18:19, schrieb Julia Lawall:
On Mon, 5 Aug 2013, Dan Carpenter wrote:
On Mon, Aug 05, 2013 at
On Mon, 5 Aug 2013, walter harms wrote:
Hello Julia,
IMHO keep the patch as it is.
It does not change any code that is good.
Suspicious code that comes up here can be addressed
in a separate patch.
OK, thanks!
julia
--
To unsubscribe from this list: send the line unsubscribe linux-media in
On Mon, 5 Aug 2013, Dan Carpenter wrote:
On Mon, Aug 05, 2013 at 04:47:39PM +0200, Julia Lawall wrote:
diff --git a/drivers/media/i2c/ov7670.c b/drivers/media/i2c/ov7670.c
index e8a1ce2..4a5a5dc 100644
--- a/drivers/media/i2c/ov7670.c
+++ b/drivers/media/i2c/ov7670.c
@@ -1369,8 +1369,8 @@
On Mon, 5 Aug 2013 18:19:18 +0200 (CEST)
Julia Lawall julia.law...@lip6.fr wrote:
Oops, thanks for spotting that. I'm not sure whether it is safe to abort
these calls as soon as the first one fails, but perhaps I could introduce
some more variables, and test them all afterwards.
Yes, it
On 08/03/2013 03:41 PM, Sylwester Nawrocki wrote:
On 08/02/2013 05:02 PM, Arun Kumar K wrote:
The patch adds the DT binding documentation for Samsung
Exynos5 SoC series imaging subsystem (FIMC-IS).
diff --git
a/Documentation/devicetree/bindings/media/exynos5-fimc-is.txt
On Mon, Aug 05, 2013 at 06:24:43PM +0200, walter harms wrote:
Hello Julia,
IMHO keep the patch as it is.
It does not change any code that is good.
Suspicious code that comes up here can be addressed
in a separate patch.
Gar... No, if we silence static checker warnings without fixing the
On 08/05/13 21:26, Marek Szyprowski wrote:
Hello,
Hi,
This patch series are an attempt to cleanup the reserved memory device
tree bindings for MFC device. MFC device has two memory ports (AXI
masters), which are used to do DMA. Usually separate memory regions are
being defined for each of
Hello,
Here's the sixth version of the VSP1 engine (a Video Signal Processor found
in several Renesas R-Car SoCs) driver. This version adds a videobuf2 mmap
locking fix and improves the documentation patch (thanks to Hans for the
discussion we had on IRC, hopefully we won't need another round
From: Katsuya Matsubara ma...@igel.co.jp
Each source entity maintains a pointer to the counterpart sink
entity while an enabled link connects them. It should be managed by
the setup_link callback in the media controller framework at runtime.
However, enabled links which connect RPFs and WPFs that
From: Katsuya Matsubara ma...@igel.co.jp
The VSP1 driver allows to define the maximum number of each module
such as RPF, WPF, and UDS in a platform data definition.
This suppresses operations for nonexistent or unused modules.
Signed-off-by: Katsuya Matsubara ma...@igel.co.jp
Signed-off-by:
The graph traversal API (media_entity_graph_walk_*) doesn't support
cyclic graphs and will fail to correctly walk a graph when circular
links exist. Support circular graph traversal by checking whether an
entity has already been visited before pushing it to the stack.
Signed-off-by: Laurent
The V4L2_MBUS_FMT_YUV10_1X30 code is documented as being equal to
0x2014, while the v4l2-mediabus.h header defines it as 0x2016. Fix the
documentation.
Signed-off-by: Laurent Pinchart laurent.pinchart+rene...@ideasonboard.com
Acked-by: Sakari Ailus sakari.ai...@iki.fi
Acked-by: Hans Verkuil
Explain how the two operations must handle formats and validate buffer
sizes when used with VIDIOC_CREATE_BUFS.
Signed-off-by: Laurent Pinchart laurent.pinchart+rene...@ideasonboard.com
Acked-by: Hans Verkuil hans.verk...@cisco.com
---
include/media/videobuf2-core.h | 11 +++
1 file
NV16M and NV61M are planar YCbCr 4:2:2 and YCrCb 4:2:2 formats with a
luma plane followed by an interleaved chroma plane. The planes are not
required to be contiguous in memory, and the formats can only be used
with the multi-planar formats API.
Signed-off-by: Laurent Pinchart
Signed-off-by: Laurent Pinchart laurent.pinchart+rene...@ideasonboard.com
Reviewed-by: Sylwester Nawrocki s.nawro...@samsung.com
Acked-by: Hans Verkuil hans.verk...@cisco.com
---
Documentation/DocBook/media/v4l/subdev-formats.xml | 609 +
Documentation/DocBook/media_api.tmpl
The vb2_fop_mmap() function is a plug-in implementation of the mmap()
file operation that calls vb2_mmap() on the queue associated with the
video device. Neither the vb2_fop_mmap() function nor the v4l2_mmap()
mmap handler in the V4L2 core take any lock, leading to race conditions
between mmap()
The VIDIOC_CREATE_BUFS ioctl takes a format argument that must contain a
valid format supported by the driver. Clarify the documentation.
Signed-off-by: Laurent Pinchart laurent.pinchart+rene...@ideasonboard.com
---
.../DocBook/media/v4l/vidioc-create-bufs.xml | 41 ++
I have the exact same device and it works fine with 3.10.4 vanilla,
whether X is running out or not. Please can you send the output of
usbmon while issuing irsend (just the interface with the mce device).
Thanks
Sean
Please find attached two traces.
- X.txt from inside an X session where
On Mon, Aug 5, 2013 at 1:10 PM, Tom Cooksey tom.cook...@arm.com wrote:
Hi Rob,
+linux-media, +linaro-mm-sig for discussion of video/camera
buffer constraints...
On Fri, Jul 26, 2013 at 11:58 AM, Tom Cooksey tom.cook...@arm.com
wrote:
* It abuses flags parameter of
Hi Mauro, I have tested using dvb5-scan, and the results are the same
(no results, and no error logs) :(
Do you have any clue why it is not working with this kernel version ?
Thanks and regards...
On Thu, Aug 1, 2013 at 2:15 PM, Mauro Carvalho Chehab
m.che...@samsung.com wrote:
Em Thu, 1 Aug
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media
v4l_for_linus
for some drivers fixes (em28xx, coda, usbtv, s5p, hdpvr and ml86v7667) and
at a fix for media DocBook.
Thanks!
Mauro
-
The following changes since commit
If v4l2_fh_open() fails in dev_open(), gspca_dev-module left locked.
The patch adds module_put(gspca_dev-module) on this path.
Found by Linux Driver Verification project (linuxtesting.org).
Signed-off-by: Alexey Khoroshilov khoroshi...@ispras.ru
---
drivers/media/usb/gspca/gspca.c | 6 +-
1
Em Mon, 05 Aug 2013 16:09:56 -0300
Luis Polasek lpola...@gmail.com escreveu:
Hi Mauro, I have tested using dvb5-scan, and the results are the same (no
results, and no error logs) :(
Do you have any clue why it is not working with this kernel version ?
c/c Oliver and Patrick, who maintains
On Mon, Aug 05, 2013 at 07:17:10PM +0100, Rajil Saraswat wrote:
Please find attached two traces.
- X.txt from inside an X session where irsend doesnt trigger ir led.
-noX.txt from virtual console with X stopped. irsend triggers the ir led.
Also, i have made sure input for this device is
Hello,
the in-kernel stkwebcam driver (by Jaime Velasco Juan and Nicolas VIVIEN)
supports only two webcam types (USB IDs 0x174f:0xa311 and 0x05e1:0x0501).
There are many other Syntek webcam types that are not supported by this
driver (such as 0x174f:0x6a31 in Asus F5RL laptop).
There is an
Vážení E-mail užívateľa;
Prekročili ste 23432 boxy nastaviť svoje
Webová služba / Administrátor, a budete mať problémy pri odosielaní a
prijímať e-maily, kým znova overiť. Musíte aktualizovať kliknutím na
odkaz nižšie a vyplňte údaje pre overenie vášho účtu
Prosím, kliknite na odkaz nižšie alebo
On 08/05/2013 06:53 PM, Stephen Warren wrote:
On 08/03/2013 03:41 PM, Sylwester Nawrocki wrote:
On 08/02/2013 05:02 PM, Arun Kumar K wrote:
The patch adds the DT binding documentation for Samsung
Exynos5 SoC series imaging subsystem (FIMC-IS).
diff --git
Hi Sylwester,
On Sun, Aug 4, 2013 at 3:13 AM, Sylwester Nawrocki
sylvester.nawro...@gmail.com wrote:
On 08/02/2013 05:02 PM, Arun Kumar K wrote:
This patch adds all the common header files used by the fimc-is
driver. It includes the commands for interfacing with the firmware
and error codes
While trying to get boot-logo up on exynos5420 SMDK which has eDP panel
connected with resolution 2560x1600, following error occured even with
IOMMU enabled:
[0.88] [drm:lowlevel_buffer_allocate] *ERROR* failed to allocate buffer.
[0.89] [drm] Initialized exynos 1.0.0 20110530 on minor 0
67 matches
Mail list logo
