- 31 Dec, 2011 17 commits
-
-
Mauro Carvalho Chehab authored
Instead of using DVBv3 parameters, rely on DVBv5 parameters to set the tuner. Signed-off-by:Mauro Carvalho Chehab <mchehab@redhat.com>
-
Mauro Carvalho Chehab authored
Instead of using DVBv3 parameters, rely on DVBv5 parameters to set the tuner. Signed-off-by: -
Mauro Carvalho Chehab authored
Instead of using DVBv3 parameters, rely on DVBv5 parameters to set the tuner. Signed-off-by: -
Mauro Carvalho Chehab authored
Instead of using DVBv3 parameters, rely on DVBv5 parameters to set the tuner. Signed-off-by: -
Mauro Carvalho Chehab authored
This standard is not properly documented, but its settings are at the tda18271dd driver, and are somewhat obvious, as they follow the same logic as DVB-T 7MHz. Signed-off-by: -
Mauro Carvalho Chehab authored
Instead of using DVBv3 parameters, rely on DVBv5 parameters to set the tuner. Signed-off-by: -
Mauro Carvalho Chehab authored
Instead of using DVBv3 parameters, rely on DVBv5 parameters to set the tuner. Signed-off-by: -
Mauro Carvalho Chehab authored
There is a bug on mxl5005s logic: when the bandwidth changes, but using the same delivery system, the code discard the set_params() reconfiguration request. This was happening because, in the previous coding, the bandwidth calculus were after the check for delivery system changes. The previous patch changed the logic to estimate the bandwidth to happend together with the changes at the delivery system. So, with a one-statement change, it is possible to make the tuner to reconfigure, in order to adjust to bandwidth changes. this will likely fix issues on countries that use 7MHz/8MHz DVB-T channels. Signed-off-by: -
Mauro Carvalho Chehab authored
Instead of using DVBv3 parameters, rely on DVBv5 parameters to set the tuner. Signed-off-by: -
Mauro Carvalho Chehab authored
Instead of using DVBv3 parameters, rely on DVBv5 parameters to set the tuner. Signed-off-by: -
Mauro Carvalho Chehab authored
Instead of using DVBv3 parameters, rely on DVBv5 parameters to set the tuner. Signed-off-by: -
Mauro Carvalho Chehab authored
Instead of using DVBv3 parameters, rely on DVBv5 parameters to set the tuner. Signed-off-by: -
Mauro Carvalho Chehab authored
This driver implements a fake get_bandwidth() callback. In reallity, the tuner driver won't adjust its low-pass filter based on a bandwidth, and were just providing a fake method for demods to read whatever was "set". This code is useless, as none of the drivers that use this tuner seems to require a get_bandwidth() callback. While here, convert set_params to use the DVBv5 way to pass parameters to tuners. Signed-off-by: -
Mauro Carvalho Chehab authored
This driver implements a fake get_bandwidth() callback. In reallity, the tuner driver won't adjust its low-pass filter based on a bandwidth, and were just providing a fake method for demods to read whatever was "set". This code is useless, as none of the drivers that use this tuner seems to require a get_bandwidth() callback. While here, convert set_params to use the DVBv5 way to pass parameters to tuners. Signed-off-by: -
Mauro Carvalho Chehab authored
This driver implements a fake get_bandwidth() callback. In reallity, the tuner driver won't adjust its low-pass filter based on a bandwidth, and were just providing a fake method for demods to read whatever was "set". This code is useless, as none of the drivers that use this tuner seems to require a get_bandwidth() callback. While here, convert set_params to use the DVBv5 way to pass parameters to tuners. Signed-off-by: -
Mauro Carvalho Chehab authored
Instead of just estimating the bandwidth for DVB-C annex A/C, also fill it at the core for ATSC and DVB-C annex B. This simplifies the logic inside the tuners, as all non-satellite tuners can just use c->bandwidth_hz for all supported delivery systems. It could make sense to latter use it also for satellite systems, as several DVB-S drivers have their own calculus. However, on DVB-S2 the bw estimation is a little more complex, and the existing drivers have some optimized calculus for bandwidth. So, let's not touch on it for now. Signed-off-by: -
Mauro Carvalho Chehab authored
SYS_DVBC_ANNEX_AC is an alias for SYS_DVBC_ANNEX_A. However, the first one is incorrect, as not all devices support both. So, replace its occurrences by the proper value (either SYS_DVBC_ANNEX_A or both SYS_DVBC_ANNEX_A and SYS_DVBC_ANNEX_C). Signed-off-by:
-
- 30 Dec, 2011 23 commits
-
-
David Fries authored
dvb_register calls videobuf_dvb_register_bus, but if that returns a failure the module will be unloaded without clearing the value of core->gate_ctrl which will cause an oops in macros called from video_open in cx88-video.c Signed-off-by:
David Fries <David@Fries.net> Cc: Mauro Carvalho Chehab <mchehab@infradead.org> Cc: Istvan Varga <istvan_v@mailbox.hu> Cc: Jonathan Nieder <jrnieder@gmail.com> Signed-off-by:
-
Dan Carpenter authored
dprintk() dereferences "ir". I'm not sure why gcc doesn't complain about this. Signed-off-by:
Dan Carpenter <dan.carpenter@oracle.com> Signed-off-by:
-
Mauro Carvalho Chehab authored
Signed-off-by: -
Aivar Päkk authored
This patch adds Kworld 355U and 380U support Signed-off-by:
Aivar Päkk <aivar11@gmail.com> Signed-off-by:
-
Malcolm Priestley authored
Stop dual frontend attach in warm state with single devices. Since this is a no reconnect device this occurs only after a warm system reboot. Signed-off-by:
Malcolm Priestley <tvboxspy@gmail.com> Signed-off-by:
-
Malcolm Priestley authored
Re: [git:v4l-dvb/for_v3.3] [media] it9135: add support for IT9135 9005 devices On Sun, 2011-12-11 at 11:55 +0100, Mauro Carvalho Chehab wrote: > This is an automatic generated email to let you know that the following patch were queued at the > http://git.linuxtv.org/media_tree.git tree: > > Subject: [media] it9135: add support for IT9135 9005 devices > Author: Malcolm Priestley <tvboxspy@gmail.com> > Date: Wed Nov 30 17:16:09 2011 -0300 > > Support add for IT9135 9005 devices > > With this patch IT9135 devices now move to using > dvb-usb-it9135-01.fw firmware > IT9137 remain on previous firmware. Hi Mauro, I have made a small mistake on this patch. I forgot to increase number of num_device_descs to 4. Signed-off-by:
-
Thomas Meyer authored
The advantage of kcalloc is, that will prevent integer overflows which could result from the multiplication of number of elements and size and it is also a bit nicer to read. The semantic patch that makes this change is available in https://lkml.org/lkml/2011/11/25/107Signed-off-by:
Thomas Meyer <thomas@m3y3r.de> Signed-off-by:
-
Thomas Meyer authored
The advantage of kcalloc is, that will prevent integer overflows which could result from the multiplication of number of elements and size and it is also a bit nicer to read. The semantic patch that makes this change is available in https://lkml.org/lkml/2011/11/25/107Signed-off-by:
-
Thomas Meyer authored
The advantage of kcalloc is, that will prevent integer overflows which could result from the multiplication of number of elements and size and it is also a bit nicer to read. The semantic patch that makes this change is available in https://lkml.org/lkml/2011/11/25/107Signed-off-by:
Laurent Pinchart <laurent.pinchart@ideasonboard.com> Signed-off-by:
-
Thomas Meyer authored
The advantage of kcalloc is, that will prevent integer overflows which could result from the multiplication of number of elements and size and it is also a bit nicer to read. The semantic patch that makes this change is available in https://lkml.org/lkml/2011/11/25/107Signed-off-by:
-
Andreas Oberritter authored
There are some issues and miss-behaves at the dvb fe thread: 1) dvb_shutdown_timeout should be dvb_shutdown_timeout * HZ instead of (dvb_shutdown_timeout * HZ + 1); 2) add a memory barrier to warrant that all CPU's will consider the new value for release_jiffies; 3) wake up dvb thread also when fepriv->exit == DVB_FE_NO_EXIT. Signed-off-by:
Andreas Oberritter <obi@linuxtv.org> Signed-off-by:
-
Stas Sergeev authored
The attached patch fixes the automute logic of saa7134. It avoids the white noise on the pulseaudio startup. (pulseaudio reads the saa7134 alsa device on startup) Signed-off-by: -
Xi Wang authored
Message-Id: <1322820073-19347-4-git-send-email-xi.wang@gmail.com> The error handling with (ret < 0) didn't work where ret is a u32. Use int instead. To be consistent we also change the functions to return an int. Signed-off-by:
Xi Wang <xi.wang@gmail.com> Signed-off-by:
-
Xi Wang authored
Message-Id: <1322820073-19347-3-git-send-email-xi.wang@gmail.com> The error handling with (ret < 0) didn't work where ret is a u32. Use int instead. To be consistent we also change the functions to return an int. Signed-off-by:
-
Xi Wang authored
Message-Id: <1322820073-19347-2-git-send-email-xi.wang@gmail.com> The error handling with (ret < 0) didn't work where ret is a u32. Use int instead. To be consistent we also change the functions to return an int. Signed-off-by:
-
Hans de Goede authored
Signed-off-by:
Hans de Goede <hdegoede@redhat.com> Signed-off-by:
-
Hans de Goede authored
Signed-off-by:
-
Hans de Goede authored
The new iso bandwidth calculation code accidentally has broken support for bulk mode cameras. This has broken the following drivers: finepix, jeilinj, ovfx2, ov534, ov534_9, se401, sq905, sq905c, sq930x, stv0680, vicam. Thix patch fixes this. Fix tested with: se401, sq905, sq905c, stv0680 & vicam cams. Signed-off-by:
-
Mauro Carvalho Chehab authored
It seems that a cut-and-past error were added by the last patch: drivers/media/video/videobuf2-core.c: In function ‘vb2_qbuf’: drivers/media/video/videobuf2-core.c:1099:14: warning: comparison between ‘enum v4l2_buf_type’ and ‘enum v4l2_memory’ [-Wenum-compare] On all places V4L2_MEMORY_USERPTR is used, it is associated with q->memory, and not b->type. So, the fix seems obvious. Cc: Andrzej Pietrasiewicz <andrzej.p@samsung.com> Cc: Kyungmin Park <kyungmin.park@samsung.com> Cc: Marek Szyprowski <m.szyprowski@samsung.com> Cc: Pawel Osciak <pawel@osciak.com> Signed-off-by: -
Andrzej Pietrasiewicz authored
This patch adds support for user pointer memory buffers to vmalloc videobuf2 allocator. Signed-off-by:
Andrzej Pietrasiewicz <andrzej.p@samsung.com> Signed-off-by:
Kyungmin Park <kyungmin.park@samsung.com> Signed-off-by:
Marek Szyprowski <m.szyprowski@samsung.com> CC: Pawel Osciak <pawel@osciak.com> Signed-off-by:
-
Marek Szyprowski authored
This patch is a result of review of mem_priv entry usage in videobuf2 core. It fixes all all potential places where it was not checked against NULL or zeroed after freeing as well as a few style issues. Signed-off-by:
-
Marek Szyprowski authored
This patch removes unused 'plane' argument from call_memop macro. Signed-off-by:
-
Marek Szyprowski authored
To get direct access to userspace memory pages vb2 allocator needs to gather read access on mmap semaphore in the current process. The same semaphore is taken before calling mmap operation, while both mmap and qbuf are called by the driver or v4l2 core with driver's lock held. To avoid a AB-BA deadlock (mmap_sem then driver's lock in mmap and driver's lock then mmap_sem in qbuf) the videobuf2 core release driver's lock, takes mmap_sem and then takes again driver's lock. get_userptr methods are now called with all needed locks already taken to avoid further lock magic inside memory allocator's code. Reported-by:
-
