On Tue, Mar 11, 2014 at 4:45 AM, Laurent Pinchart
laurent.pinch...@ideasonboard.com wrote:
The video enum_dv_timings and dv_timings_cap operations are deprecated.
Implement the pad-level version of those operations to prepare for the
removal of the video version.
Signed-off-by: Laurent
On Tue, Mar 11, 2014 at 4:45 AM, Laurent Pinchart
laurent.pinch...@ideasonboard.com wrote:
The video enum_dv_timings and dv_timings_cap operations are deprecated
and unused. Remove them.
Signed-off-by: Laurent Pinchart laurent.pinch...@ideasonboard.com
Reviewed-by: Hans Verkuil
On Tue, Mar 11, 2014 at 4:45 AM, Laurent Pinchart
laurent.pinch...@ideasonboard.com wrote:
The video enum_dv_timings operation is deprecated. Implement the
pad-level version of the operation to prepare for the removal of the
video version.
Signed-off-by: Laurent Pinchart
On Tue, Mar 11, 2014 at 4:45 AM, Laurent Pinchart
laurent.pinch...@ideasonboard.com wrote:
The video enum_dv_timings and dv_timings_cap operations are deprecated
and unused. Remove them.
Signed-off-by: Laurent Pinchart laurent.pinch...@ideasonboard.com
Reviewed-by: Hans Verkuil
Hi Laurent,
Thanks for the patch.
On Tue, Mar 11, 2014 at 4:45 AM, Laurent Pinchart
laurent.pinch...@ideasonboard.com wrote:
The video-level enum_dv_timings and dv_timings_cap operations are
deprecated in favor of the pad-level versions. All subdev drivers
implement the pad-level versions,
Hi Laurent,
Thanks for the patch.
On Tue, Mar 11, 2014 at 4:45 AM, Laurent Pinchart
laurent.pinch...@ideasonboard.com wrote:
The video-level enum_dv_timings and dv_timings_cap operations are
deprecated in favor of the pad-level versions. All subdev drivers
implement the pad-level versions,
On Tue, Mar 11, 2014 at 4:45 AM, Laurent Pinchart
laurent.pinch...@ideasonboard.com wrote:
The video enum_dv_timings and dv_timings_cap operations are deprecated
and unused. Remove them.
Signed-off-by: Laurent Pinchart laurent.pinch...@ideasonboard.com
Reviewed-by: Hans Verkuil
On Tue, Mar 11, 2014 at 4:45 AM, Laurent Pinchart
laurent.pinch...@ideasonboard.com wrote:
Signed-off-by: Laurent Pinchart laurent.pinch...@ideasonboard.com
Acked-by: Lad, Prabhakar prabhakar.cse...@gmail.com
Regards,
--Prabhakar lad
---
include/media/v4l2-subdev.h| 4
This patch set mainly consists of minor fixes for the VPE driver. These fixes
ensure the following:
- The VPE module can be inserted and removed successively.
- Make sure that smaller resolutions like qcif work correctly.
- Prevent race condition between firmware loading and an open call to the
The video_device struct is currently embedded in the driver data struct vpe_dev.
A vpe_dev instance is allocated by the driver, and the memory for the vfd is a
part of this struct.
The v4l2 core, however, manages the removal of the vfd region, through the
video_device's .release() op, which
VPE has a ctrl parameter which decides how many mem to mem transactions the
active job from the job queue can perform.
The driver's job_ready() made sure that the number of ready source buffers are
sufficient for the job to execute successfully. But it didn't make sure if
there are sufficient
The vpe output and capture queues are initially configured to default values in
vpe_open(). A G_FMT before any S_FMTs will result in these values being
populated.
The colorspace and bytesperline parameter of this initial configuration are
incorrect. This breaks compliance when as we get
The vpe driver wasn't setting the correct field parameter for dequed CAPTURE
type buffers for the case where the captured output is progressive.
Set the field to V4L2_FIELD_NONE for the completed destination buffers when
the captured output is progressive.
For OUTPUT type buffers, a queued
Add selection ioctl ops. For VPE, cropping makes sense only for the input to
VPE(or V4L2_BUF_TYPE_VIDEO_OUTPUT/MPLANE buffers) and composing makes sense
only for the output of VPE(or V4L2_BUF_TYPE_VIDEO_CAPTURE/MPLANE buffers).
For the CAPTURE type, V4L2_SEL_TGT_COMPOSE results in VPE writing the
The minimum width and height for VPE input/output was kept as 128 pixels. VPE
doesn't have a constraint on the image height, it requires the image width to
be at least 16 bytes.
Change the minimum supported dimensions to 32x32. This allows us to de-interlace
qcif content. A smaller image size
For OMAP and DRA7x, we generally allocate video and graphics buffers through
omapdrm since the corresponding omap-gem driver provides DMM-Tiler backed
contiguous buffers. omapdrm is a dma-buf exporter. These buffers are used by
other drivers in the video pipeline.
Add VB2_DMABUF flag to the
The bus_info parameter in v4l2_capabilities expects a 'platform_' prefix. This
wasn't done in the driver and hence was breaking compliance. Update the bus_info
parameter accordingly.
Signed-off-by: Archit Taneja arc...@ti.com
---
drivers/media/platform/ti-vpe/vpe.c | 3 ++-
1 file changed, 2
Zero out the reserved formats in v4l2_pix_format_mplane and
v4l2_plane_pix_format members of the returned v4l2_format pointer when passed
through TRY_FMT ioctl.
This ensures that the user doesn't interpret the non-zero fields as some data
passed by the driver, and ensures compliance.
querycap currently returns V4L2_CAP_VIDEO_M2M as a capability, this should be
V4L2_CAP_VIDEO_M2M_MPLANE instead, as the driver supports multiplanar formats.
Signed-off-by: Archit Taneja arc...@ti.com
---
drivers/media/platform/ti-vpe/vpe.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
The dequed CAPTURE_MPLANE type buffers don't contain the flags that the
originally queued OUTPUT_MPLANE type buffers have. This breaks compliance.
Copy the source v4l2_buffer flags to the destination v4l2_buffer flags before
they are dequed.
Signed-off-by: Archit Taneja arc...@ti.com
---
Rename the memory block resource vpe_csc to csc since it also exists within
the VIP IP block. This would make the name more generic, and both VPE and VIP DT
nodes in the future can use it.
Signed-off-by: Archit Taneja arc...@ti.com
---
drivers/media/platform/ti-vpe/csc.c | 2 +-
1 file changed,
vpe fops(vpe_open in particular) should be called only when VPDMA firmware
is loaded. File operations on the video device are possible the moment it is
registered.
Currently, we register the video device for VPE at driver probe, after calling
a vpdma helper to initialize VPDMA and load firmware.
Some parameters of the VPE descriptors were understood incorrectly. They are now
fixed. The fixes are explained as follows:
- When adding an inbound data descriptor to the VPDMA descriptor list, we intend
to use c_rect as the cropped region fetched by VPDMA. Therefore, c_rect-width
shouldn't
On Tue, Mar 11, 2014 at 12:15:38AM +0100, Laurent Pinchart wrote:
The subdev EDID ioctls receive a pad field that must reference an
existing pad and an EDID field that must point to a buffer. Validate
both fields in the core code instead of duplicating validation in all
drivers.
On 03/10/14 23:43, Laurent Pinchart wrote:
Hi Hans,
On Wednesday 12 February 2014 16:01:17 Hans Verkuil wrote:
On 02/05/14 17:42, Laurent Pinchart wrote:
Replace the dummy video format operations by pad format operations that
configure the output format.
Signed-off-by: Laurent Pinchart
From: avnd kiran avnd.ki...@samsung.com
Latest MFC v6 firmware requires tile mode and loop filter
setting to be done as part of Init buffer command, in sync
with v7. Since there are two versions of v6 firmware with
different interfaces, it is differenciated using the version
number read back from
Hi Hans,
On Tuesday 11 March 2014 00:32:48 Hans Verkuil wrote:
On 03/11/2014 12:23 AM, Guennadi Liakhovetski wrote:
Hi Hans,
Thanks for taking care about this problem. I'm not sure it would be ok for
me to pull this specific patch via my tree, because it's for the V4L2
core, and the
On 03/11/14 10:33, Laurent Pinchart wrote:
Hi Hans,
On Tuesday 11 March 2014 00:32:48 Hans Verkuil wrote:
On 03/11/2014 12:23 AM, Guennadi Liakhovetski wrote:
Hi Hans,
Thanks for taking care about this problem. I'm not sure it would be ok for
me to pull this specific patch via my tree,
Pointer to device state has been moved to different location during
some change. PCTV 290e LNA function still uses old pointer, carried
over FE priv, and it crash.
Reported-by: Janne Kujanpää jik...@iki.fi
Signed-off-by: Antti Palosaari cr...@iki.fi
---
drivers/media/usb/em28xx/em28xx-dvb.c | 3
The g_std and s_std operations are video-related, move them to the video
ops where they belong.
Signed-off-by: Laurent Pinchart laurent.pinch...@ideasonboard.com
---
drivers/media/i2c/adv7180.c | 6 +-
drivers/media/i2c/adv7183.c | 4 ++--
Reviewed-by: Hans Verkuil hans.verk...@cisco.com
On 03/11/14 00:15, Laurent Pinchart wrote:
Signed-off-by: Laurent Pinchart laurent.pinch...@ideasonboard.com
---
include/media/v4l2-subdev.h| 4
include/uapi/linux/videodev2.h | 10 --
2 files changed, 12 insertions(+), 2
The following changes since commit f2d7313534072a5fe192e7cf46204b413acef479:
[media] drx-d: add missing braces in drxd_hard.c:DRXD_init (2014-03-09
09:20:50 -0300)
are available in the git repository at:
git://linuxtv.org/kdebski/media_tree_2.git master
for you to fetch changes up to
drivers/media/dvb-frontends/drx39xyj/drxj.c: In function
'ctrl_get_qam_sig_quality':
drivers/media/dvb-frontends/drx39xyj/drxj.c:9468:6: warning: variable 'ber_cnt'
set but not used [-Wunused-but-set-variable]
u32 ber_cnt = 0; /* BER count */
^
By reading the comment, it is said that
On 03/11/14 00:15, Laurent Pinchart wrote:
Validate the pad field in the core code whenever specified.
Signed-off-by: Laurent Pinchart laurent.pinch...@ideasonboard.com
---
.../DocBook/media/v4l/vidioc-dv-timings-cap.xml| 27 +++
There are two troubles there:
1) the bit error measure were not accumulating;
2) it was missing the bit count.
Fix them.
Signed-off-by: Mauro Carvalho Chehab m.che...@samsung.com
---
drivers/media/dvb-frontends/drx39xyj/drxj.c | 3 ++-
1 file changed, 2 insertions(+), 1
On 03/11/14 00:15, Laurent Pinchart wrote:
The subdev EDID ioctls receive a pad field that must reference an
existing pad and an EDID field that must point to a buffer. Validate
both fields in the core code instead of duplicating validation in all
drivers.
Signed-off-by: Laurent Pinchart
tree: git://linuxtv.org/media_tree.git master
head: 164e5cfb7d37e4826a8337029716f4885657d859
commit: 164e5cfb7d37e4826a8337029716f4885657d859 [499/499] [media] drx39xxj.h:
Fix undefined reference to attach function
config: make ARCH=m68k allmodconfig
All error/warnings:
In file included
Hi Hans,
On Tuesday 11 March 2014 11:45:09 Hans Verkuil wrote:
On 03/11/14 00:15, Laurent Pinchart wrote:
The subdev EDID ioctls receive a pad field that must reference an
existing pad and an EDID field that must point to a buffer. Validate
both fields in the core code instead of
On 03/11/14 11:57, Laurent Pinchart wrote:
Hi Hans,
On Tuesday 11 March 2014 11:45:09 Hans Verkuil wrote:
On 03/11/14 00:15, Laurent Pinchart wrote:
The subdev EDID ioctls receive a pad field that must reference an
existing pad and an EDID field that must point to a buffer. Validate
both
Hi Hans,
On Tuesday 11 March 2014 11:38:39 Hans Verkuil wrote:
On 03/11/14 00:15, Laurent Pinchart wrote:
Validate the pad field in the core code whenever specified.
Signed-off-by: Laurent Pinchart laurent.pinch...@ideasonboard.com
---
This message is generated daily by a cron job that builds media_tree for
the kernels and architectures in the list below.
Results of the daily build of media_tree:
date: Tue Mar 11 11:47:29 CET 2014
git branch: test
git hash: 0d49e7761173520ff02cec6f11d581f8ebca764d
gcc
Em Tue, 11 Mar 2014 18:48:53 +0800
kbuild test robot fengguang...@intel.com escreveu:
tree: git://linuxtv.org/media_tree.git master
head: 164e5cfb7d37e4826a8337029716f4885657d859
commit: 164e5cfb7d37e4826a8337029716f4885657d859 [499/499] [media]
drx39xxj.h: Fix undefined reference to
Hi Laurent,
Am Montag, den 10.03.2014, 20:19 +0100 schrieb Laurent Pinchart:
On Friday 07 March 2014 18:40:54 Philipp Zabel wrote:
While we look at of_graph_get_next_endpoint(), could you explain the
reason behind the extra reference count increase on the prev node:
/*
* Avoid
Em Mon, 10 Mar 2014 14:37:58 +
Grant Likely grant.lik...@linaro.org escreveu:
On Mon, 10 Mar 2014 10:26:30 -0300, Mauro Carvalho Chehab
m.che...@samsung.com wrote:
Em Fri, 07 Mar 2014 18:23:30 +
Grant Likely grant.lik...@linaro.org escreveu:
On Thu, 06 Mar 2014 18:13:20
Hi Hans,
On Tuesday 11 March 2014 10:05:00 Hans Verkuil wrote:
On 03/10/14 23:43, Laurent Pinchart wrote:
On Wednesday 12 February 2014 16:01:17 Hans Verkuil wrote:
On 02/05/14 17:42, Laurent Pinchart wrote:
Replace the dummy video format operations by pad format operations that
Hi Arun,
From: Arun Kumar K [mailto:arunkk.sams...@gmail.com] On Behalf Of Arun
Kumar K
Sent: Friday, March 07, 2014 9:26 AM
From: Pawel Osciak posc...@chromium.org
Currently, for formats that are not H264, MFC driver will check the
consumed stream size returned by the firmware and,
Hi Laurent,
On 03/11/14 12:16, Laurent Pinchart wrote:
Hi Hans,
On Tuesday 11 March 2014 10:05:00 Hans Verkuil wrote:
On 03/10/14 23:43, Laurent Pinchart wrote:
On Wednesday 12 February 2014 16:01:17 Hans Verkuil wrote:
On 02/05/14 17:42, Laurent Pinchart wrote:
Replace the dummy video
Hi Philipp,
On Monday 10 March 2014 16:40:30 Philipp Zabel wrote:
Am Montag, den 10.03.2014, 16:15 +0100 schrieb Laurent Pinchart:
On Monday 10 March 2014 14:58:15 Grant Likely wrote:
On Mon, 10 Mar 2014 14:52:53 +0100, Laurent Pinchart wrote:
On Monday 10 March 2014 12:18:20 Tomi
This message is generated daily by a cron job that builds media_tree for
the kernels and architectures in the list below.
Results of the daily build of media_tree:
date: Tue Mar 11 12:12:39 CET 2014
git branch: test
git hash: 0d49e7761173520ff02cec6f11d581f8ebca764d
gcc
Hi Laurent,
You can add my:
Reviewed-by: Hans Verkuil hans.verk...@cisco.com
for patches 28-35, 37-45 and 47.
For patches 46 and 48 (DT related) add my:
Acked-by: Hans Verkuil hans.verk...@cisco.com
For patches 26 and 27 I posted review comments, and patch 36 is removing
support for the
On 03/11/14 09:33, Archit Taneja wrote:
The minimum width and height for VPE input/output was kept as 128 pixels. VPE
doesn't have a constraint on the image height, it requires the image width to
be at least 16 bytes.
Change the minimum supported dimensions to 32x32. This allows us to
On 03/11/14 09:33, Archit Taneja wrote:
For OMAP and DRA7x, we generally allocate video and graphics buffers through
omapdrm since the corresponding omap-gem driver provides DMM-Tiler backed
contiguous buffers. omapdrm is a dma-buf exporter. These buffers are used by
other drivers in the video
On 03/11/14 09:33, Archit Taneja wrote:
The video_device struct is currently embedded in the driver data struct
vpe_dev.
A vpe_dev instance is allocated by the driver, and the memory for the vfd is a
part of this struct.
The v4l2 core, however, manages the removal of the vfd region,
Hi Laurent,
On 11/03/14 00:15, Laurent Pinchart wrote:
Empty port nodes are allowed but currently unsupported as the
v4l2_of_get_next_endpoint() function assumes that all port nodes have at
least an endpoint. Fix this.
Signed-off-by: Laurent Pinchart laurent.pinch...@ideasonboard.com
Hi Archit,
A few small comments below...
On 03/11/14 09:33, Archit Taneja wrote:
Add selection ioctl ops. For VPE, cropping makes sense only for the input to
VPE(or V4L2_BUF_TYPE_VIDEO_OUTPUT/MPLANE buffers) and composing makes sense
only for the output of VPE(or
On 03/11/14 09:33, Archit Taneja wrote:
querycap currently returns V4L2_CAP_VIDEO_M2M as a capability, this should be
V4L2_CAP_VIDEO_M2M_MPLANE instead, as the driver supports multiplanar formats.
Signed-off-by: Archit Taneja arc...@ti.com
Reviewed-by: Hans Verkuil hans.verk...@cisco.com
On 03/11/14 09:33, Archit Taneja wrote:
The bus_info parameter in v4l2_capabilities expects a 'platform_' prefix. This
wasn't done in the driver and hence was breaking compliance. Update the
bus_info
parameter accordingly.
Signed-off-by: Archit Taneja arc...@ti.com
Reviewed-by: Hans
On 03/11/14 09:33, Archit Taneja wrote:
The vpe output and capture queues are initially configured to default values
in
vpe_open(). A G_FMT before any S_FMTs will result in these values being
populated.
The colorspace and bytesperline parameter of this initial configuration are
incorrect.
On 03/11/14 09:33, Archit Taneja wrote:
Zero out the reserved formats in v4l2_pix_format_mplane and
v4l2_plane_pix_format members of the returned v4l2_format pointer when passed
through TRY_FMT ioctl.
This ensures that the user doesn't interpret the non-zero fields as some data
passed by
On 10.03.2014 21:38, Antti Palosaari wrote:
That is just same set I sent earlier too, but rebased to latest
media/master and 6 small compliance fix.
PULL request update. I rebased that again to todays media/master as
master was rebased.
The following changes since commit
Hi Sylwester,
Thank you for the patch.
On Thursday 06 March 2014 17:20:12 Sylwester Nawrocki wrote:
This patch documents following updates of the Exynos4 SoC camera subsystem
devicetree binding:
- addition of #clock-cells property to 'camera' node - the #clock-cells
property is needed
On 03/11/14 09:33, Archit Taneja wrote:
The vpe driver wasn't setting the correct field parameter for dequed CAPTURE
type buffers for the case where the captured output is progressive.
Set the field to V4L2_FIELD_NONE for the completed destination buffers when
the captured output is
On 03/11/14 09:33, Archit Taneja wrote:
The dequed CAPTURE_MPLANE type buffers don't contain the flags that the
originally queued OUTPUT_MPLANE type buffers have. This breaks compliance.
Copy the source v4l2_buffer flags to the destination v4l2_buffer flags before
they are dequed.
Hi Kamil,
On Tue, Mar 11, 2014 at 4:59 PM, Kamil Debski k.deb...@samsung.com wrote:
Hi Arun,
From: Arun Kumar K [mailto:arunkk.sams...@gmail.com] On Behalf Of Arun
Kumar K
Sent: Friday, March 07, 2014 9:26 AM
From: Pawel Osciak posc...@chromium.org
Currently, for formats that are not
On Tuesday 11 March 2014 05:51 PM, Hans Verkuil wrote:
Hi Archit,
A few small comments below...
On 03/11/14 09:33, Archit Taneja wrote:
Add selection ioctl ops. For VPE, cropping makes sense only for the input to
VPE(or V4L2_BUF_TYPE_VIDEO_OUTPUT/MPLANE buffers) and composing makes sense
only
Hi Mauro,
This patch series adds a bunch of docbook fixes, posted here earlier:
http://www.spinics.net/lists/linux-media/msg74059.html
and it adds a pci skeleton driver originally written for FOSDEM 2014 and
posted earlier here:
On 03/11/14 13:46, Archit Taneja wrote:
On Tuesday 11 March 2014 05:51 PM, Hans Verkuil wrote:
Hi Archit,
A few small comments below...
On 03/11/14 09:33, Archit Taneja wrote:
Add selection ioctl ops. For VPE, cropping makes sense only for the input to
VPE(or
On 11/03/14 13:43, Laurent Pinchart wrote:
We could scan the whole tree for entities, ports and endpoints once, in
the base oftree code, and put that into a graph structure, adding the
backlinks.
The of_graph_* helpers could then use that graph instead of the device
tree.
That could work.
On 03/10/2014 04:15 PM, Laurent Pinchart wrote:
Hi Grant,
On Monday 10 March 2014 14:58:15 Grant Likely wrote:
On Mon, 10 Mar 2014 14:52:53 +0100, Laurent Pinchart wrote:
On Monday 10 March 2014 12:18:20 Tomi Valkeinen wrote:
On 08/03/14 13:41, Grant Likely wrote:
Ok. If we go for single
On Tuesday 11 March 2014 06:19 PM, Hans Verkuil wrote:
On 03/11/14 13:46, Archit Taneja wrote:
On Tuesday 11 March 2014 05:51 PM, Hans Verkuil wrote:
Hi Archit,
A few small comments below...
On 03/11/14 09:33, Archit Taneja wrote:
snip
Yes. If for no other reason that I plan on adding
Hi Tomi,
On Tuesday 11 March 2014 14:59:20 Tomi Valkeinen wrote:
On 11/03/14 13:43, Laurent Pinchart wrote:
We could scan the whole tree for entities, ports and endpoints once, in
the base oftree code, and put that into a graph structure, adding the
backlinks. The of_graph_* helpers could
On 11/03/14 15:16, Laurent Pinchart wrote:
And if I gathered Grant's opinion correctly (correct me if I'm wrong),
he thinks things should be explicit, i.e. the bindings for, say, an
encoder should state that the encoder's output endpoint _must_ contain a
remote-endpoint property, whereas the
Hi Laurent,
Thanks for your review.
On 11/03/14 13:30, Laurent Pinchart wrote:
[...]
---
.../devicetree/bindings/media/samsung-fimc.txt | 34 -
1 file changed, 26 insertions(+), 8 deletions(-)
diff --git a/Documentation/devicetree/bindings/media/samsung-fimc.txt
Fix this linker warning:
WARNING: __divdi3 [media_build/v4l/drx39xyj.ko] undefined!
Signed-off-by: Gianluca Gennari gennar...@gmail.com
---
drivers/media/dvb-frontends/drx39xyj/drxj.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git
Hi,
Am Dienstag, den 11.03.2014, 15:27 +0200 schrieb Tomi Valkeinen:
On 11/03/14 15:16, Laurent Pinchart wrote:
And if I gathered Grant's opinion correctly (correct me if I'm wrong),
he thinks things should be explicit, i.e. the bindings for, say, an
encoder should state that the
On 10/03/14 07:53, Tomi Valkeinen wrote:
On 08/03/14 14:25, Grant Likely wrote:
Sure. If endpoints are logical, then only create the ones actually
hooked up. No problem there. But nor do I see any issue with having
empty connections if the board author things it makes sense to have them
in
On 03/10/2014 12:42 PM, Laurent Pinchart wrote:
Hi Andrzej,
I like that idea. I would prefer making the 'port' nodes mandatory and the
'ports' and 'endpoint' nodes optional. Leaving the 'port' node out
slightly decreases readability in my opinion, but making the 'endpoint'
node optional
Em Mon, 10 Feb 2014 07:28:31 +0200
Antti Palosaari cr...@iki.fi escreveu:
Moikka!
On 10.02.2014 01:44, GEORGE wrote:
b/drivers/media/rc/keymaps/rc-snazio-tvpvr-pro.c
new file mode 100644
index 000..44f0c81
--- /dev/null
+++ b/drivers/media/rc/keymaps/rc-snazio-tvpvr-pro.c
@@
Hi Sylwester,
On Tuesday 11 March 2014 14:38:37 Sylwester Nawrocki wrote:
Hi Laurent,
Thanks for your review.
You're welcome.
On 11/03/14 13:30, Laurent Pinchart wrote:
[...]
---
.../devicetree/bindings/media/samsung-fimc.txt | 34 +-
1 file changed, 26
Hi Grant,
Am Montag, den 10.03.2014, 14:58 + schrieb Grant Likely:
On Mon, 10 Mar 2014 14:52:53 +0100, Laurent Pinchart
laurent.pinch...@ideasonboard.com wrote:
On Monday 10 March 2014 12:18:20 Tomi Valkeinen wrote:
On 08/03/14 13:41, Grant Likely wrote:
Ok. If we go for single
Validate the pad field in the core code whenever specified.
Signed-off-by: Laurent Pinchart laurent.pinch...@ideasonboard.com
---
.../DocBook/media/v4l/vidioc-dv-timings-cap.xml| 27 +++
.../DocBook/media/v4l/vidioc-enum-dv-timings.xml | 30 +-
Replace the dummy video format operations by pad format operations that
configure the output format.
Signed-off-by: Laurent Pinchart laurent.pinch...@ideasonboard.com
---
drivers/media/i2c/adv7604.c | 280
include/media/adv7604.h | 56 -
The subdev EDID ioctls receive a pad field that must reference an
existing pad and an EDID field that must point to a buffer. Validate
both fields in the core code instead of duplicating validation in all
drivers.
Signed-off-by: Laurent Pinchart laurent.pinch...@ideasonboard.com
Acked-by: Sakari
The *_and_or() functions take an 'and' bitmask to be ANDed with the
register value before ORing it with th 'or' bitmask. As the functions
are used to mask and set bits selectively, this requires the caller to
invert the 'and' bitmask and is thus error prone. Replace those
functions with a
Parse the device tree node to populate platform data.
Signed-off-by: Laurent Pinchart laurent.pinch...@ideasonboard.com
Acked-by: Hans Verkuil hans.verk...@cisco.com
---
.../devicetree/bindings/media/i2c/adv7604.txt | 56 +
drivers/media/i2c/adv7604.c| 92
Hi Philipp,
On Tuesday 11 March 2014 16:07:00 Philipp Zabel wrote:
Am Montag, den 10.03.2014, 14:58 + schrieb Grant Likely:
On Mon, 10 Mar 2014 14:52:53 +0100, Laurent Pinchart wrote:
[snip]
In theory unidirectional links in DT are indeed enough. However, let's
not forget the
tree: git://linuxtv.org/media_tree.git master
head: 7b802ce7e8c67510389fdbbe29edd87a75df3a93
commit: 03fdfbfd3b5944bfd210541a83c9b222e2c20920 [448/499] [media] drx-j:
Prepare to use DVBv5 stats
config: make ARCH=m68k allmodconfig
Note: the linuxtv-media/master HEAD
On 03/11/2014 04:09 PM, Laurent Pinchart wrote:
Validate the pad field in the core code whenever specified.
Signed-off-by: Laurent Pinchart laurent.pinch...@ideasonboard.com
Reviewed-by: Hans Verkuil hans.verk...@cisco.com
Regards,
Hans
---
I just noticed from patchwork these old patches are pending. It appears
I have not pull requested or mail is just missed from the reason or the
other. They are just fine for 3.15, but m88ds3103: fix bug on
.set_tone() is stuff for 3.14 too. I know it is very late, but given
the fact it fixes
On 03/11/2014 04:09 PM, Laurent Pinchart wrote:
The subdev EDID ioctls receive a pad field that must reference an
existing pad and an EDID field that must point to a buffer. Validate
both fields in the core code instead of duplicating validation in all
drivers.
Signed-off-by: Laurent
tree: git://linuxtv.org/media_tree.git master
head: c3c2077d9579472b07581ecdaf6cc5a60b1700bc
commit: 03fdfbfd3b5944bfd210541a83c9b222e2c20920 [446/499] [media] drx-j:
Prepare to use DVBv5 stats
config: make ARCH=i386 allyesconfig
Note: the linuxtv-media/master HEAD
This patch documents following updates of the Exynos4 SoC camera subsystem
devicetree binding:
- addition of #clock-cells and clock-output-names properties to 'camera'
node - these are now needed so the image sensor sub-devices can reference
clocks provided by the camera host interface,
-
Hi Hans,
On Tuesday 11 March 2014 16:44:27 Hans Verkuil wrote:
On 03/11/2014 04:09 PM, Laurent Pinchart wrote:
The subdev EDID ioctls receive a pad field that must reference an
existing pad and an EDID field that must point to a buffer. Validate
both fields in the core code instead of
DROP that request! I will split it to 2 requests, one for 3.14 and one
for 3.15.
Antti
On 11.03.2014 17:42, Antti Palosaari wrote:
I just noticed from patchwork these old patches are pending. It appears
I have not pull requested or mail is just missed from the reason or the
other. They are
On 03/11/2014 05:08 PM, Laurent Pinchart wrote:
Hi Hans,
On Tuesday 11 March 2014 16:44:27 Hans Verkuil wrote:
On 03/11/2014 04:09 PM, Laurent Pinchart wrote:
The subdev EDID ioctls receive a pad field that must reference an
existing pad and an EDID field that must point to a buffer.
I have forgotten to pull request that earlier. It is simple one bit
wrong in one register.
regards
Antti
The following changes since commit 81d428cbdb9e630f4424bf81522cd35394beba76:
[media] saa7134: fix WARN_ON during resume (2014-03-11 10:17:06 -0300)
are available in the git repository
Hi Sylwester,
Thank you for the patch.
On Tuesday 11 March 2014 17:00:35 Sylwester Nawrocki wrote:
This patch documents following updates of the Exynos4 SoC camera subsystem
devicetree binding:
- addition of #clock-cells and clock-output-names properties to 'camera'
node - these are
Hi Hans,
On Tuesday 11 March 2014 17:11:07 Hans Verkuil wrote:
On 03/11/2014 05:08 PM, Laurent Pinchart wrote:
Hi Hans,
On Tuesday 11 March 2014 16:44:27 Hans Verkuil wrote:
On 03/11/2014 04:09 PM, Laurent Pinchart wrote:
The subdev EDID ioctls receive a pad field that must reference
These are reported by Coverity and has no functionality changes.
regards
Antti
The following changes since commit c3c2077d9579472b07581ecdaf6cc5a60b1700bc:
[media] nuvoton-cir: Activate PNP device when probing (2014-03-11
12:22:50 -0300)
are available in the git repository at:
Hi Laurent,
On 11/03/14 17:20, Laurent Pinchart wrote:
Image sensor nodes
--
@@ -97,8 +108,8 @@ Image sensor nodes
The sensor device nodes should be added to their control bus controller
(e.g. I2C0) nodes and linked to a port node in the csis or the
parallel-ports
1 - 100 of 126 matches
Mail list logo
