On 05/30/2015 09:10 PM, Jemma Denson wrote:
The flexcop bridge chip has two banks of hardware pid filters -
an initial 6, and on some chip revisions an additional bank of 32.
A bug is present on the initial 6 - when changing transponders
one of two PAT packets from the old transponder would be
Currently the colors for the Y16 and Y16_BE pixelformats are in the range
0x-0xff00. So pure white (0x) is never created.
Improve this by using the same byte for both LSB and MSB so the full range
is achieved.
Signed-off-by: Hans Verkuil hans.verk...@cisco.com
diff --git
The DVB network API was not documented. There are just some
placeholders there.
Replace it by a proper documentation.
Signed-off-by: Mauro Carvalho Chehab mche...@osg.samsung.com
diff --git a/Documentation/DocBook/media/Makefile
b/Documentation/DocBook/media/Makefile
index
On 06/01/2015 12:44 PM, Sakari Ailus wrote:
Hi Hans,
Thanks for the RFC.
On Mon, Jun 01, 2015 at 11:44:51AM +0200, Hans Verkuil wrote:
One of the things that is really irritating is the fact that drivers that
use contig-dma sometimes want to support USERPTR, allowing applications to
pass
Implement DMABUF exporting and importing.
Signed-off-by: Hans Verkuil hans.verk...@cisco.com
diff --git a/drivers/media/usb/stk1160/stk1160-v4l.c
b/drivers/media/usb/stk1160/stk1160-v4l.c
index 749ad56..4d313ed 100644
--- a/drivers/media/usb/stk1160/stk1160-v4l.c
+++
On 27.05.15 14:05, Laurent Pinchart wrote:
Even though 'compatability' has a dedicated entry in the Wiktionary,
it's listed as 'Mispelling of compatibility'. Fix it.
Signed-off-by: Laurent Pinchart laurent.pinch...@ideasonboard.com
---
arch/metag/include/asm/elf.h | 2 +-
If device has no DMA max_seg_size set, we assume that there is no limit
and it is safe to force it to use DMA_BIT_MASK(32) as max_seg_size to
let DMA-mapping API always create contiguous mappings in DMA address
space. This is essential for all devices, which use dma-contig
videobuf2 memory
On 06/01/2015 02:40 PM, Jan Kara wrote:
On Thu 28-05-15 16:24:02, Andrew Morton wrote:
On Wed, 13 May 2015 15:08:08 +0200 Jan Kara j...@suse.cz wrote:
Provide new function get_vaddr_frames(). This function maps virtual
addresses from given start and fills given array with page frame numbers
Hi,
On Friday 29 May 2015 08:34 PM, Felipe Balbi wrote:
Hi,
On Fri, May 29, 2015 at 05:04:38PM +0530, Kishon Vijay Abraham I wrote:
Hi Felipe,
On Wednesday 27 May 2015 12:09 AM, Felipe Balbi wrote:
On Tue, May 26, 2015 at 11:37:17AM -0700, Arun Ramamurthy wrote:
Hi
On 15-05-26 07:19 AM,
On 05/31/2015 07:56 PM, Adam Baker wrote:
On 29/05/15 22:05, Antti Palosaari wrote:
We need own I2C locking because of tuner I2C adapter/repeater.
Firmware command is executed using I2C send + reply message. Default
I2C adapter locking protects only single I2C operation, not whole
send + reply
Hi all,
On Mon, 01 Jun 2015 09:08:03 +0100 Jemma Denson jden...@gmail.com
wrote:
Yes, that might work, I hadn't though of just swapping them around -
thanks. It would however assume that the 0x PAT feed is requested
early on enough that it always sits within the bank of 32 and nothing
On Thu, May 28, 2015 at 04:41:17PM +0200, Valentin Vidic wrote:
I recently bought this card after seeing on the LinuxTV wiki
that it's supported since kernel v3.19, but now I can't get
it working properly with Debian. The modules load without
errors but scanning for channels or watching TV
On Thu 28-05-15 16:24:02, Andrew Morton wrote:
On Wed, 13 May 2015 15:08:08 +0200 Jan Kara j...@suse.cz wrote:
Provide new function get_vaddr_frames(). This function maps virtual
addresses from given start and fills given array with page frame numbers of
the corresponding pages. If given
On 06/01/2015 11:12 AM, Mauro Carvalho Chehab wrote:
FE_SET_PROPERTY/FE_GET_PROPERTY actually expects a struct dtv_properties
argument.
Signed-off-by: Mauro Carvalho Chehab mche...@osg.samsung.com
diff --git a/Documentation/DocBook/media/dvb/fe-get-property.xml
Em Sun, 31 May 2015 14:59:09 +0200
Hans Verkuil hverk...@xs4all.nl escreveu:
From: Hans Verkuil hans.verk...@cisco.com
Hi Mauro,
Here are three patches that fix typos and xmllint errors.
The first patch fixes typos, the second a large number of xmllint
errors and the last fixes a final
Hi Hans,
Thanks for the RFC.
On Mon, Jun 01, 2015 at 11:44:51AM +0200, Hans Verkuil wrote:
One of the things that is really irritating is the fact that drivers that
use contig-dma sometimes want to support USERPTR, allowing applications to
pass pointers to the driver that point to physically
Hi Antti,
On 01/06/15 07:14, Antti Palosaari wrote:
On 05/30/2015 09:10 PM, Jemma Denson wrote:
The flexcop bridge chip has two banks of hardware pid filters -
an initial 6, and on some chip revisions an additional bank of 32.
A bug is present on the initial 6 - when changing transponders
one
This set fixes the final compilation and sparse warnings (except for a few
remaining
sparse warnings for which I have no obvious solution).
It also improves timestamp handling in the davinci drivers.
Regards,
Hans
The following changes since commit
On Mon, Jun 1, 2015 at 12:09 PM, Geert Uytterhoeven
ge...@linux-m68k.org wrote:
JFYI, when comparing v4.1-rc6[1] to v4.1-rc5[3], the summaries are:
- build errors: +8/-52
+ /home/kisskb/slave/src/drivers/media/i2c/ov2659.c: error: 'struct
v4l2_subdev_fh' has no member named 'pad': =
The following changes since commit d511eb7d642aaf513fefeb05514dc6177c53c350:
[media] uvcvideo: Remove unneeded device disconnected flag
(2015-05-30 12:12:58 -0300)
are available in the git repository at:
git://linuxtv.org/anttip/media_tree.git silabs_pull
for you to fetch changes up to
One of the things that is really irritating is the fact that drivers that
use contig-dma sometimes want to support USERPTR, allowing applications to
pass pointers to the driver that point to physically contiguous memory that
was somehow obtained, and that userspace has no way of knowing whether
This has been on my TODO list for some time now: the control that enables the
video
loopback was part of the controls of the video output device instead of the
video
capture device. In practice this was quite annoying since you expect it at the
capture
side since that's where you want to make
On 06/01/2015 11:12 AM, Mauro Carvalho Chehab wrote:
The changeset dc9ef7d11207 change the open() ioctl documentation to
match the V4L2 open(). However, some cut-and-pasted stuff doesn't
match what actually happens at the DVB core.
So, fix the documentation entry to be more accurate with the
v2:
* si2168 declare functions as static
* i2157 set FE_SCALE_NOT_AVAILABLE if stats polling stopped due to IO error
Antti Palosaari (2):
si2168: Implement own I2C adapter locking
si2157: implement signal strength stats
drivers/media/dvb-frontends/si2168.c | 135
Implement DVBv5 signal strength stats. Returns dBm.
Signed-off-by: Antti Palosaari cr...@iki.fi
Tested-by: Adam Baker li...@baker-net.org.uk
---
drivers/media/tuners/si2157.c | 40 +-
drivers/media/tuners/si2157_priv.h | 1 +
2 files changed, 40
We need own I2C locking because of tuner I2C adapter/repeater.
Firmware command is executed using I2C send + reply message. Default
I2C adapter locking protects only single I2C operation, not whole
send + reply sequence as needed. Due to that, it was possible tuner
I2C message interrupts firmware
The changeset dc9ef7d11207 change the open() ioctl documentation to
match the V4L2 open(). However, some cut-and-pasted stuff doesn't
match what actually happens at the DVB core.
So, fix the documentation entry to be more accurate with the DVB
frontend open() specifics.
Signed-off-by: Mauro
FE_SET_PROPERTY/FE_GET_PROPERTY actually expects a struct dtv_properties
argument.
Signed-off-by: Mauro Carvalho Chehab mche...@osg.samsung.com
diff --git a/Documentation/DocBook/media/dvb/fe-get-property.xml
b/Documentation/DocBook/media/dvb/fe-get-property.xml
index 7d0bd78f5a24..53a170ed3bd1
Hi Hans,
On Mon, Jun 01, 2015 at 01:02:26PM +0200, Hans Verkuil wrote:
On 06/01/2015 12:44 PM, Sakari Ailus wrote:
Hi Hans,
Thanks for the RFC.
On Mon, Jun 01, 2015 at 11:44:51AM +0200, Hans Verkuil wrote:
One of the things that is really irritating is the fact that drivers that
Hi Hans,
On Monday 01 June 2015 11:44:51 Hans Verkuil wrote:
One of the things that is really irritating is the fact that drivers that
use contig-dma sometimes want to support USERPTR, allowing applications to
pass pointers to the driver that point to physically contiguous memory that
was
On 05/27/2015 09:24 AM, Takashi Iwai wrote:
At Fri, 8 May 2015 13:31:31 -0600,
Shuah Khan wrote:
Change ALSA driver to use media controller API to share tuner
with DVB and V4L2 drivers that control AU0828 media device.
Media device is created based on a newly added field value
in the
On 06/01/2015 11:44 AM, Hans Verkuil wrote:
One of the things that is really irritating is the fact that drivers that
use contig-dma sometimes want to support USERPTR, allowing applications to
pass pointers to the driver that point to physically contiguous memory that
was somehow obtained, and
On Mon, Jun 01, 2015 at 06:22:41PM +0530, Kishon Vijay Abraham I wrote:
Hi,
On Friday 29 May 2015 08:34 PM, Felipe Balbi wrote:
Hi,
On Fri, May 29, 2015 at 05:04:38PM +0530, Kishon Vijay Abraham I wrote:
Hi Felipe,
On Wednesday 27 May 2015 12:09 AM, Felipe Balbi wrote:
On Tue, May 26,
Since commit 1c6c69525b40 (genirq: Reject bogus threaded irq requests)
threaded IRQs without a primary handler need to be requested with
IRQF_ONESHOT, otherwise the request will fail.
So pass the IRQF_ONESHOT flag in this case.
The semantic patch that makes this change is available
in
On Sunday 31 May 2015 12:47:06 Tina Ruchandani wrote:
struct timeval uses a 32-bit seconds representation which will
overflow in the year 2038 and beyond. This patch replaces
the usage of struct timeval with ktime_t which is a 64-bit
timestamp and is year 2038 safe.
This patch is part of a
Hi Jacek,
On Mon, May 25, 2015 at 05:13:56PM +0200, Jacek Anaszewski wrote:
+On remove the v4l2_flash_release function has to be called, which takes one
+argument - struct v4l2_flash pointer returned previously by v4l2_flash_init.
You might want to add this function can be safely called with
Hi Jacek,
On Mon, May 25, 2015 at 05:13:58PM +0200, Jacek Anaszewski wrote:
Add support for V4L2 Flash sub-device to the max77693 LED Flash class
driver. The support allows for V4L2 Flash sub-device to take the control
of the LED Flash class device.
Signed-off-by: Jacek Anaszewski
Hi Jacek,
On Mon, May 25, 2015 at 05:13:57PM +0200, Jacek Anaszewski wrote:
This patch adds helper functions for registering/unregistering
LED Flash class devices as V4L2 sub-devices. The functions should
be called from the LED subsystem device driver. In case the
support for V4L2 Flash
Hi Sylwester,
On Mon, May 25, 2015 at 02:00:33PM +0200, Sylwester Nawrocki wrote:
Hi,
On 23/05/15 14:03, Sakari Ailus wrote:
On Thu, May 21, 2015 at 03:28:40PM +0200, Sylwester Nawrocki wrote:
flash-leds = flash_xx image_sensor_x, ...;
One more matter to consider: xenon flash
Hello Hans
On Mon, Jun 1, 2015 at 9:05 AM, Hans Verkuil hverk...@xs4all.nl wrote:
Currently the colors for the Y16 and Y16_BE pixelformats are in the range
0x-0xff00. So pure white (0x) is never created.
Improve this by using the same byte for both LSB and MSB so the full range
is
Hi Sakari,
Thank you for the patch. Please see below for one small comment.
On Monday 01 June 2015 01:24:39 Sakari Ailus wrote:
V4L2 async sub-devices are currently matched (OF case) based on the struct
device_node pointer in struct device. LED devices may have more than one
LED, and in that
Hello All,
I would like to ask for some comments about a plan to use user space
video codecs through the V4L interface. I am thinking of a situation
similar to the one described on the linuxtv.org wiki at
http://www.linuxtv.org/wiki/index.php/V4L2_Userspace_Library
The basic premise is to
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 Jun 2 04:00:20 CEST 2015
git branch: test
git hash: c1c3c85ddf60a6d97c122d57d385b4929fcec4b3
gcc
On Thu, 28 May 2015 18:49:05 -0300
Mauro Carvalho Chehab mche...@osg.samsung.com wrote:
+ paraIt should also be noticed that a media device may also have audio
+ components, like mixers, PCM capture, PCM playback, etc, with
+ are controlled via ALSA API./para
How about
A few minor corrections here.
jon
On Thu, 28 May 2015 18:49:18 -0300
Mauro Carvalho Chehab mche...@osg.samsung.com wrote:
Make the text clearer about what the properties API does.
Signed-off-by: Mauro Carvalho Chehab mche...@osg.samsung.com
diff --git
On Thu, 28 May 2015 18:49:03 -0300
Mauro Carvalho Chehab mche...@osg.samsung.com wrote:
This is the first series of patches that will improve the DVB
documentation.
I've done a *quick* pass over these and sent a few comments, but they are
all on the trivial-detail side of things. Looks good
On Thu, 28 May 2015 18:49:07 -0300
Mauro Carvalho Chehab mche...@osg.samsung.com wrote:
Currently, it is using 'role=tt', but this is not defined at
the DocBook 4.5 spec. The net result is that no emphasis happens.
So, replace them to bold emphasis.
Nit: I suspect the intent of the emphasis
On Thu, 28 May 2015 18:49:35 -0300
Mauro Carvalho Chehab mche...@osg.samsung.com wrote:
+Please notice that several statistics require the demodulator to be fully
+locked (e. g. with FE_HAS_LOCK bit set). See
s/notice/note/
jon
--
To unsubscribe from this list: send the line
48 matches
Mail list logo
