This patch adjusts boolean assignments from 0/1 to false/true.
And accordingly, it also adjusts the if conditions.
Signed-off-by: Heba Aamer heba93aa...@gmail.com
---
drivers/staging/media/lirc/lirc_serial.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git
This patch series change the media controller API to allow adding
support for DVB media controller support.
I removed the actual implementation from this series, in order to
better identify the API bits required to add media controller support
to DVB. They'll be sent o a separate patch series,
Most of the DVB subdevs have already their own devnode.
Add support for them at the media controller API.
Signed-off-by: Mauro Carvalho Chehab mche...@osg.samsung.com
diff --git a/include/uapi/linux/media.h b/include/uapi/linux/media.h
index 418f4fec391a..4c8f26243252 100644
---
Add MEDIA_ENT_T_V4L2_SUBDEV_TUNER to represent the V4L2
(and dvb) tuner subdevices.
Signed-off-by: Mauro Carvalho Chehab mche...@osg.samsung.com
diff --git a/include/uapi/linux/media.h b/include/uapi/linux/media.h
index 4c8f26243252..52cc2a6b19b7 100644
--- a/include/uapi/linux/media.h
+++
The previous provision for DVB media controller support were to
define an ID (likely meaning the adapter number) for the DVB
devnodes.
This is just plain wrong. Just like V4L, DVB devices (and ALSA,
or whatever) are identified via a (major, minor) tuple.
This is enough to uniquely identify a
Em Mon, 26 Jan 2015 09:00:46 -0500
Devin Heitmueller dheitmuel...@kernellabs.com escreveu:
For media-ctl, it is easier to handle major/minor, in order to identify
the associated devnode name. Btw, media-ctl currently assumes that all
devnode devices are specified by v4l.major/v4l.minor.
It is actually trivial to get the device nodes once you have the
major/minor. The media-ctl library does that for you. See:
No objection then.
On a related note, you would be very well served to consider testing
your dvb changes with a device that has more than one DVB tuner (such
as the
This patch fixes following spare warnings:
drivers/media/platform/am437x/am437x-vpfe.c:66:28: warning: symbol
'vpfe_standards' was not declared. Should it be static?
drivers/media/platform/am437x/am437x-vpfe.c:2202:57: warning: incorrect type in
argument 2 (different address spaces)
Em Mon, 26 Jan 2015 14:11:50 +0100
Hans Verkuil hverk...@xs4all.nl escreveu:
On 01/26/2015 01:47 PM, Mauro Carvalho Chehab wrote:
The previous provision for DVB media controller support were to
define an ID (likely meaning the adapter number) for the DVB
devnodes.
This is just plain
tree: git://linuxtv.org/media_tree.git master
head: e32b31ae45c18679c186e67aa41d0e2318cae487
commit: 417d2e507edcb5cf15eb344f86bd3dd28737f24e [66/93] [media] media:
platform: add VPFE capture driver support for AM437X
reproduce:
# apt-get install sparse
git checkout
The bits are the same, but register is 0xf4 on ADV7611 instead of 0xfc.
When reading back the value in log_status, differentiate both.
Signed-off-by: Jean-Michel Hautbois jean-michel.hautb...@vodalys.com
---
drivers/media/i2c/adv7604.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
On Mon, Jan 26, 2015 at 12:50 AM, John Klug ski.brim...@gmail.com wrote:
I have a new PCTV card with CX23880 (not CX23883 as shown in the picture):
http://www.linuxtv.org/wiki/index.php/Pinnacle_PCTV_HD_Card_(800i)
The description is out of date with respect to my recent card.
It did not
For media-ctl, it is easier to handle major/minor, in order to identify
the associated devnode name. Btw, media-ctl currently assumes that all
devnode devices are specified by v4l.major/v4l.minor.
I suspect part of the motivation for the id that corresponds to the
adapter field was to make it
On 01/26/2015 01:47 PM, Mauro Carvalho Chehab wrote:
The previous provision for DVB media controller support were to
define an ID (likely meaning the adapter number) for the DVB
devnodes.
This is just plain wrong. Just like V4L, DVB devices (and ALSA,
or whatever) are identified via a
On 01/26/2015 02:34 PM, Mauro Carvalho Chehab wrote:
Em Mon, 26 Jan 2015 14:11:50 +0100
Hans Verkuil hverk...@xs4all.nl escreveu:
On 01/26/2015 01:47 PM, Mauro Carvalho Chehab wrote:
The previous provision for DVB media controller support were to
define an ID (likely meaning the adapter
Hans and Laurent,
-Original Message-
From: Hans Verkuil [mailto:hverk...@xs4all.nl]
Sent: Thursday, January 22, 2015 1:44 AM
To: Laurent Pinchart; Chris Kohn
Cc: linux-media@vger.kernel.org; Michal Simek; Hyun Kwon;
devicet...@vger.kernel.org
Subject: Re: [PATCH v4 08/10] v4l:
Hello to anyone,
I'm working on a problem with V4L2 on Linux Kernel 2.6.37.
The problem arise when I try to query a video device to list the
controls it provides.
When is call
ioctl(fd, VIDIOC_QUERYCTRL, queryctrl)
the function doesn't return 0 and errno is set to EINVAL
This happen for
This commit moves the buffer in use logic from the .buf_cleanup
handler into .stop_streaming, based on advice that this is its
proper logical home.
By ensuring the list of pointers in priv-queue_buf[] is managed
as soon as possible, we avoid warnings concerning buffers in ACTIVE
state when the
This is version 3 of the hotfix patchset for video support on Lager,
in which we aim to fix the kernel's warnings about unexpected buffer
states. It replaces the following series:
http://comments.gmane.org/gmane.linux.drivers.video-input-infrastructure/87009
This version of the
From: Ian Molton ian.mol...@codethink.co.uk
The code that tests that capture from a stream has stopped is
presently insufficient and the potential for a race condition
exists where frame capture may generate an interrupt between
requesting the capture process halt and freeing buffers.
This patch
Kyle Sanderson kyle.leet at gmail.com writes:
[585870.001641] saa7164_cmd_send() No free sequences
[585870.001645] saa7164_api_i2c_write() error, ret(1) = 0xc
[585870.001650] tda10048_writereg: writereg error (ret == -5)
Any tips? I've tried a couple horrible kernel patches but didn't
Hi Russell!
On 21 January 2015 at 23:01, Russell King - ARM Linux
li...@arm.linux.org.uk wrote:
On Wed, Jan 21, 2015 at 09:46:47AM +0530, Sumit Semwal wrote:
+static int calc_constraints(struct device *dev,
+ struct dma_buf_constraints *calc_cons)
+{
+ struct
Guennadi:
I am working on a SPI interface camera sensor now, trying to
work out a patch for soc_camera for you to review.
thanks.
Kassey
2014-11-07 5:55 GMT+08:00 Guennadi Liakhovetski g.liakhovet...@gmx.de:
Hi Kassey,
On Mon, 27 Oct 2014, Kassey wrote:
hi, Dmitri:
is there
I moved it to a dual boot system, and it works in windows, and the
same error in Linux.
The chips are marked:
Conexant CX23880
Samsung S5H1411
Cirrus CS5340CZZ
Atmel ATMLH138
three out of four are a different part number than the Wiki.
It is Board T1213044 stamped on
This adds support for spi interface sub device for soc_camera.
Signed-off-by: Kassey Li kass...@nvidia.com
---
drivers/media/platform/soc_camera/soc_camera.c | 51
include/media/soc_camera.h | 11 +
2 files changed, 62 insertions(+)
diff
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 Jan 27 04:01:01 CET 2015
git branch: test
git hash: e32b31ae45c18679c186e67aa41d0e2318cae487
gcc
tree: git://linuxtv.org/media_tree.git master
head: e32b31ae45c18679c186e67aa41d0e2318cae487
commit: 417d2e507edcb5cf15eb344f86bd3dd28737f24e [66/93] [media] media:
platform: add VPFE capture driver support for AM437X
drivers/media/platform/am437x/am437x-vpfe.c:2027 vpfe_start_streaming()
From: Kassey Li kass...@nvidia.com
This adds support for spi interface sub device for
soc_camera.
Signed-off-by: Kassey Li kass...@nvidia.com
---
drivers/media/platform/soc_camera/soc_camera.c | 51
include/media/soc_camera.h | 10 +
2 files
Hi Florian,
Thanks for the reply!
On Vi, 2015-01-23 at 17:46 +0100, Florian Echtler wrote:
Hello Teodora,
On 23.01.2015 14:05, Baluta, Teodora wrote:
The fingerprint sensor acts more like a scanner device, so the
closest type is the V4L2_CAP_VIDEO_CAPTURE. However, this is not a
On 01/23/2015 12:07 PM, Sean Young wrote:
On Thu, Jan 22, 2015 at 05:04:35PM +0100, Kamil Debski wrote:
Add the CEC framework.
-snip-
+Remote control handling
+---
+
+The CEC framework provides two ways of handling the key messages of remote
+control. In the first case,
Hi!
I found a problem on vc032x gspca usb webcam subdriver: bytesperline
property is wrong for YUYV and YVYU formats.
With recent v4l-utils library (=0.9.1), that uses bytesperline for
pixel format conversion, the result is a wrong jerky image.
Patch tested on my laptop (USB webcam Logitech
On Fri, Jan 9, 2015 at 9:37 AM, Pavel Machek pa...@ucw.cz wrote:
On Fri 2015-01-09 16:22:51, Jacek Anaszewski wrote:
Some LED devices support two operation modes - torch and flash.
This patch provides support for flash LED devices in the LED subsystem
by introducing new sysfs attributes and
On Mon, Jan 12, 2015 at 12:04 AM, Jacek Anaszewski
j.anaszew...@samsung.com wrote:
Hi Pavel,
Thanks for the review.
On 01/09/2015 06:40 PM, Pavel Machek wrote:
Hi!
The documentation being added contains overall description of the
LED Flash Class and the related sysfs attributes.
33 matches
Mail list logo
