Hi,
Sorry to be late. In this weekday, I have little time for this thread
because working for alsa-lib[1]. Besides, I'm not full-time developer
for this kind of work. In short, I use my limited private time for this
discussion.
On Jun 15 2016 17:06, Richard Cochran wrote:
> On Wed, Jun 15, 2016 a
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: Sat Jun 18 04:00:25 CEST 2016
git branch: test
git hash: 59f0bc11848f8f3242bc1fefae670e745929cd7b
gcc versi
On 06/15/2016 01:48 AM, Jacek Anaszewski wrote:
> Hi Andrew,
>
> Thanks for the patch.
>
> Please address the issue [1] raised by test bot and resubmit.
>
> Thanks,
> Jacek Anaszewski
>
> [1] https://lkml.org/lkml/2016/6/13/1091
>
It looks like some systems use 'gpio_led_register_device' to m
Hello,
On Saturday 18 Jun 2016 00:11:49 Pavel Machek wrote:
> Hi!
>
> >> I also don't think the FOCUS_ABSOLUTE controls is a really good one for
> >> the voice coil lens current. I expect more voice coil lens controls
> >> (linear vs. PWM mode, ringing compensation...) to be needed so I think
> >
Hi!
> >I also don't think the FOCUS_ABSOLUTE controls is a really good one for
> >the voice coil lens current. I expect more voice coil lens controls
> >(linear vs. PWM mode, ringing compensation...) to be needed so I think
> >it's worth a new class.
Well, I do agree that that the new class is fi
Hi!
> -
> +
> +
> + Voice Coil Control Reference
> +
> + The Voice Coil class controls are used to control voice
> + coil lens devices. These are very simple devices that consist of
> + a voice coil, a spring and a lens. The current applied on a
"on the"?
> + voice c
Hi Pavel,
On Mon, Jun 13, 2016 at 09:17:53PM +0200, Pavel Machek wrote:
> On Sun 2016-06-12 14:22:53, Sakari Ailus wrote:
> > Hi Pavel,
> >
> > On Sun, Jun 12, 2016 at 10:48:11AM +0200, Pavel Machek wrote:
> > > Hi!
> > >
> > > > > >Add userspace API definitions.
> > > > > >
> > > > > >Signed-of
Hi Pavel,
On Sun, Jun 12, 2016 at 09:54:17AM +0200, Pavel Machek wrote:
> Hi!
>
> > > >@@ -974,4 +975,9 @@ enum v4l2_detect_md_mode {
> > > > #define V4L2_CID_DETECT_MD_THRESHOLD_GRID
> > > > (V4L2_CID_DETECT_CLASS_BASE + 3)
> > > > #define V4L2_CID_DETECT_MD_REGION_GRID
> > > >
C libraries with 64-bit time_t use an incompatible format for
struct omap3isp_stat_data. This changes the kernel code to
support either version, by moving over the normal handling
to the 64-bit variant, and adding compatiblity code to handle
the old binary format with the existing ioctl command cod
The dvb demuxer code uses a 'struct timespec' to pass a timeout
as absolute time. This will cause problems on 32-bit architectures
in 2038 when time_t overflows, and it is racy with a concurrent
settimeofday() call.
This patch changes the code to use ktime_get() instead, using
the monotonic time b
On 06/16/2016 04:33 AM, Lars-Peter Clausen wrote:
On 06/15/2016 12:49 AM, Steve Longerbeam wrote:
This driver is based on adv7180.c from Freescale imx_3.10.17_1.0.0_beta
branch, modified heavily for code cleanup and converted from int-device
to subdev.
We already have a driver for the adv7180
On 06/16/2016 09:13 AM, Ian Arkver wrote:
For me this fails when I try to enable both video muxes (mx6dl, though
mx6q should be the same).
I get a sysfs duplicate name failure for 34.videomux. I realise
passing the GPR13 register offset and a bitfield mask as a tuple in
the reg value of the o
On 06/17/2016 08:18 AM, Gary Bisson wrote:
Steve, All,
On Thu, Jun 16, 2016 at 10:32:31AM +0200, Gary Bisson wrote:
Steve, All,
On Tue, Jun 14, 2016 at 03:49:15PM -0700, Steve Longerbeam wrote:
Defines the host video capture device node and an OV5642 camera sensor
node on i2c2. The host cap
On 06/17/2016 08:18 AM, Gary Bisson wrote:
Steve, All,
On Thu, Jun 16, 2016 at 10:32:31AM +0200, Gary Bisson wrote:
Steve, All,
On Tue, Jun 14, 2016 at 03:49:15PM -0700, Steve Longerbeam wrote:
Defines the host video capture device node and an OV5642 camera sensor
node on i2c2. The host cap
The callback function dma_buf_describe() returns an int not void so the
function pointer cast in dma_buf_show() is wrong. dma_buf_describe() can
also fail when acquiring the mutex gets interrupted so always returning
0 in dma_buf_show() is wrong, too.
Fix both issues by casting the function pointe
A copy paste error created that format with the same one-line
description as Y8I and Y12I, whereas Z16 is quite different from them
both.
Signed-off-by: Guennadi Liakhovetski
---
Documentation/DocBook/media/v4l/pixfmt-z16.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Do
On 06/17/2016 12:10 AM, Hans Verkuil wrote:
On 06/16/2016 07:02 PM, Steve Longerbeam wrote:
On 06/16/2016 02:49 AM, Jack Mitchell wrote:
On 16/06/16 02:37, Steve Longerbeam wrote:
Hi Jack,
On 06/15/2016 03:43 AM, Jack Mitchell wrote:
Trying to use a user pointer rather than mmap also fail
Hi!
> First, I re-did pipeline setup in python, it seems slightly less hacky
> then in shell.
>
> I tried to modify fcam-dev to work with the new interface, but was not
> successful so far. I can post patches if someone is interested
> (mplayer works for me, but that's not too suitable for taking
Hi!
First, I re-did pipeline setup in python, it seems slightly less hacky
then in shell.
I tried to modify fcam-dev to work with the new interface, but was not
successful so far. I can post patches if someone is interested
(mplayer works for me, but that's not too suitable for taking photos).
I
On 05/05/2016 01:06 AM, Sakari Ailus wrote:
> Instead of checking for a strict size for the IOCTL arguments, place
> minimum and maximum limits.
>
> As an additional bonus, IOCTL handlers will be able to check whether the
> caller actually set (using the argument size) the field vs. assigning it
>
On 17/06/16 16:18, Gary Bisson wrote:
Steve, All,
On Thu, Jun 16, 2016 at 10:32:31AM +0200, Gary Bisson wrote:
Steve, All,
On Tue, Jun 14, 2016 at 03:49:15PM -0700, Steve Longerbeam wrote:
Defines the host video capture device node and an OV5642 camera sensor
node on i2c2. The host capture
On Fri, Jun 17, 2016 at 9:31 AM, Pekka Paalanen wrote:
> On Fri, 17 Jun 2016 08:26:04 -0400
> Rob Clark wrote:
>
>> On Fri, Jun 17, 2016 at 3:59 AM, Pekka Paalanen wrote:
>> > On Thu, 16 Jun 2016 10:40:51 -0400
>> > Rob Clark wrote:
>> >
>> >> So, if we wanted to extend this to support the four
Steve, All,
On Thu, Jun 16, 2016 at 10:32:31AM +0200, Gary Bisson wrote:
> Steve, All,
>
> On Tue, Jun 14, 2016 at 03:49:15PM -0700, Steve Longerbeam wrote:
> > Defines the host video capture device node and an OV5642 camera sensor
> > node on i2c2. The host capture device connects to the OV5642
Hi Mauro,
Thank you for the review.
On Friday 17 Jun 2016 08:07:23 Mauro Carvalho Chehab wrote:
> Em Tue, 26 Apr 2016 00:36:30 +0300
>
> Laurent Pinchart escreveu:
> > On some platforms the VSP performs memory accesses through an FCP. When
> > that's the case get a reference to the FCP from the
This is a series of patches to add output of raw touch diagnostic data via V4L2
to the Atmel maXTouch and Synaptics RMI4 drivers.
It's a rewrite of the previous implementation which output via debugfs: it now
uses a V4L2 device in a similar way to the sur40 driver.
We have a utility which can rea
Register a video device to output T37 diagnostic data.
Signed-off-by: Nick Dyer
---
drivers/input/touchscreen/Kconfig| 6 +-
drivers/input/touchscreen/atmel_mxt_ts.c | 244 +++
2 files changed, 248 insertions(+), 2 deletions(-)
diff --git a/drivers/input/to
Function 54 implements access to various RMI4 diagnostic features.
This patch adds support for retrieving this data. It registers a V4L2
device to output the data to user space.
Signed-off-by: Nick Dyer
---
drivers/input/rmi4/Kconfig | 11 +
drivers/input/rmi4/Makefile | 1 +
driver
The touchscreen may have a margin where not all the matrix is used. Read
the parameters from T9 and T100 and take account of the difference.
Note: this does not read the XORIGIN/YORIGIN fields so it assumes that
the touchscreen starts at (0,0)
Signed-off-by: Nick Dyer
---
drivers/input/touchscr
The mXT1386 family of chips have a different architecture which splits
the diagnostic data into 3 columns.
Signed-off-by: Nick Dyer
---
drivers/input/touchscreen/atmel_mxt_ts.c | 31 ---
1 file changed, 28 insertions(+), 3 deletions(-)
diff --git a/drivers/input/touc
Some touch controllers send out raw touch data in a similar way to a
greyscale frame grabber. Add a new device type for these devices.
Use a new device prefix v4l-touch for these devices, to stop generic
capture software from treating them as webcams.
Signed-off-by: Nick Dyer
---
drivers/input/
Invert the diagnostic data to match the orientation of the input device.
Signed-off-by: Nick Dyer
---
drivers/input/touchscreen/atmel_mxt_ts.c | 26 +-
1 file changed, 21 insertions(+), 5 deletions(-)
diff --git a/drivers/input/touchscreen/atmel_mxt_ts.c
b/drivers/input
There are different datatypes available from a maXTouch chip. Add
support to retrieve reference data as well.
Signed-off-by: Nick Dyer
---
drivers/input/touchscreen/atmel_mxt_ts.c | 58
1 file changed, 51 insertions(+), 7 deletions(-)
diff --git a/drivers/input/
This will be used for output of raw touch delta data. This format is
used by Atmel maXTouch (atmel_mxt_ts) and also Synaptics RMI4.
Signed-off-by: Nick Dyer
---
Documentation/DocBook/media/v4l/pixfmt-ys16.xml | 79 +
Documentation/DocBook/media/v4l/pixfmt.xml | 1 +
Atmel maXTouch devices have a T37 object which can be used to read raw
touch deltas from the device. This consists of an array of 16-bit
integers, one for each node on the touchscreen matrix.
Signed-off-by: Nick Dyer
---
drivers/input/touchscreen/Kconfig| 6 ++
drivers/input/touchscree
On 06/17/2016 12:08 AM, Sakari Ailus wrote:
> Hi Shuah,
>
> On Fri, Jun 10, 2016 at 11:37:23AM -0600, Shuah Khan wrote:
>> Media devnode open/ioctl could be in progress when media device unregister
>> is initiated. System calls and ioctls check media device registered status
>> at the beginning, h
On Fri, 17 Jun 2016 08:26:04 -0400
Rob Clark wrote:
> On Fri, Jun 17, 2016 at 3:59 AM, Pekka Paalanen wrote:
> > On Thu, 16 Jun 2016 10:40:51 -0400
> > Rob Clark wrote:
> >
> >> So, if we wanted to extend this to support the fourcc-modifiers that
> >> we have on the kernel side for compressed
On 2016/06/17 14:53, Sakari Ailus wrote:
> On Wed, Jun 15, 2016 at 10:15:07PM +0200, Max Kellermann wrote:
> > media_gobj_destroy() may be called twice on one instance - once by
> > media_device_unregister() and again by dvb_media_device_free(). The
>
> Is that something that should really happe
Hi Max,
On Wed, Jun 15, 2016 at 10:15:07PM +0200, Max Kellermann wrote:
> media_gobj_destroy() may be called twice on one instance - once by
> media_device_unregister() and again by dvb_media_device_free(). The
Is that something that should really happen, and why? The same object should
not be u
On Fri, Jun 17, 2016 at 3:59 AM, Pekka Paalanen wrote:
> On Thu, 16 Jun 2016 10:40:51 -0400
> Rob Clark wrote:
>
>> So, if we wanted to extend this to support the fourcc-modifiers that
>> we have on the kernel side for compressed/tiled/etc formats, what
>> would be the right approach?
>>
>> A new
Em Fri, 17 Jun 2016 13:09:10 +0200
Hans Verkuil escreveu:
> On 06/17/2016 11:50 AM, Mauro Carvalho Chehab wrote:
> +
> +CEC_MODE_MONITOR
> +0xe0
> +Put the file descriptor into monitor mode. Can only
> be used in combination
On 06/17/2016 11:50 AM, Mauro Carvalho Chehab wrote:
+
+ CEC_MODE_MONITOR
+ 0xe0
+ Put the file descriptor into monitor mode. Can only be used
in combination
+ with CEC_MODE_NO_INITIATOR, otherwise &EINVAL;
will be
+ returned. I
Em Tue, 26 Apr 2016 00:36:30 +0300
Laurent Pinchart escreveu:
> On some platforms the VSP performs memory accesses through an FCP. When
> that's the case get a reference to the FCP from the VSP DT node and
> enable/disable it at runtime as needed.
>
> Signed-off-by: Laurent Pinchart
> ---
> ..
Em Fri, 17 Jun 2016 10:06:31 +0200
Hans Verkuil escreveu:
> On 06/16/2016 11:22 PM, Mauro Carvalho Chehab wrote:
> > Em Fri, 29 Apr 2016 15:52:25 +0200
> > Hans Verkuil escreveu:
> >
> >> From: Hans Verkuil
> >>
> >> Add CEC support to the adv7842 driver.
> >>
> >> Signed-off-by: Hans Verkui
* Hans Verkuil [160617 00:07]:
> Hi Janusz,
>
> On 06/16/2016 07:21 PM, Janusz Krzysztofik wrote:
> > As requested by media subsystem maintainers, here is an attempt to
> > convert the omap1_camera driver to the vb2 framework. Also, conversion
> > to the dmaengine framework, long awaited by ARM
Em Fri, 17 Jun 2016 10:03:13 +0200
Hans Verkuil escreveu:
> On 06/16/2016 11:17 PM, Mauro Carvalho Chehab wrote:
> > Em Fri, 29 Apr 2016 15:52:24 +0200
> > Hans Verkuil escreveu:
> >
> >> From: Hans Verkuil
> >>
> >> Add CEC support to the adv7604 driver.
> >>
> >> Signed-off-by: Hans Verkui
Em Fri, 17 Jun 2016 09:58:53 +0200
Hans Verkuil escreveu:
> On 06/16/2016 11:09 PM, Mauro Carvalho Chehab wrote:
> > Em Fri, 29 Apr 2016 15:52:23 +0200
> > Hans Verkuil escreveu:
> >
> >> From: Hans Verkuil
> >>
> >> Add DocBook documentation for the CEC API.
> >
> > Please always send th
Add driver for the Image Sensor Controller. It manages
incoming data from a parallel based CMOS/CCD sensor.
It has an internal image processor, also integrates a
triple channel direct memory access controller master
interface.
Signed-off-by: Songjun Wu
---
Changes in v5:
- Modify the macro defin
The Image Sensor Controller driver includes two parts.
1) Driver code to implement the ISC function.
2) Device tree binding documentation, it describes how
to add the ISC in device tree.
Changes in v5:
- Modify the macro definition and the related code.
- Add clock names.
Changes in v4:
- Modi
Em Fri, 17 Jun 2016 09:22:05 +0200
Hans Verkuil escreveu:
> On 06/16/2016 10:12 PM, Mauro Carvalho Chehab wrote:
> > Em Fri, 29 Apr 2016 15:52:22 +0200
> > Hans Verkuil escreveu:
> >
> >> From: Hans Verkuil
> >>
> >> Document the new HDMI CEC framework.
> >
> > As we'll be moving document
Em Fri, 17 Jun 2016 09:18:32 +0200
Hans Verkuil escreveu:
> Hi Mauro,
>
> From the daily build:
>
> apps: WARNINGS
> dvb-sat.c:188:14: warning: unused variable 's' [-Wunused-variable]
>
> The fix is easy of course (delete static char s[1024];), but it is a bit
> surprising and I just
> want t
On 06/16/2016 11:22 PM, Mauro Carvalho Chehab wrote:
> Em Fri, 29 Apr 2016 15:52:25 +0200
> Hans Verkuil escreveu:
>
>> From: Hans Verkuil
>>
>> Add CEC support to the adv7842 driver.
>>
>> Signed-off-by: Hans Verkuil
>
> Won't review patches 10-13, as the same reviews I made for patch 9
> ver
On 06/16/2016 11:17 PM, Mauro Carvalho Chehab wrote:
> Em Fri, 29 Apr 2016 15:52:24 +0200
> Hans Verkuil escreveu:
>
>> From: Hans Verkuil
>>
>> Add CEC support to the adv7604 driver.
>>
>> Signed-off-by: Hans Verkuil
>> [k.deb...@samsung.com: Merged changes from CEC Updates commit by Hans
>>
On Thu, 16 Jun 2016 10:40:51 -0400
Rob Clark wrote:
> So, if we wanted to extend this to support the fourcc-modifiers that
> we have on the kernel side for compressed/tiled/etc formats, what
> would be the right approach?
>
> A new version of the existing extension or a new
> EGL_EXT_image_dma_b
On 06/16/2016 11:09 PM, Mauro Carvalho Chehab wrote:
> Em Fri, 29 Apr 2016 15:52:23 +0200
> Hans Verkuil escreveu:
>
>> From: Hans Verkuil
>>
>> Add DocBook documentation for the CEC API.
>
> Please always send the documentation patch *before* the code,
> in order to make easier to do the code
On 06/16/2016 10:12 PM, Mauro Carvalho Chehab wrote:
> Em Fri, 29 Apr 2016 15:52:22 +0200
> Hans Verkuil escreveu:
>
>> From: Hans Verkuil
>>
>> Document the new HDMI CEC framework.
>
> As we'll be moving documentation to Sphinx/Rst, it would be good if
> you could make it work fine with sphinx
Hi Mauro,
>From the daily build:
apps: WARNINGS
dvb-sat.c:188:14: warning: unused variable 's' [-Wunused-variable]
The fix is easy of course (delete static char s[1024];), but it is a bit
surprising and I just
want to make sure there isn't something else going on.
Regards,
Hans
--
To
On 06/16/2016 11:40 PM, Javier Martinez Canillas wrote:
> The driver doesn't set the device in the struct v4l2_capability bus_info
> field so v4l2-compliance reports the following error for VIDIOC_QUERYCAP:
>
> Required ioctls:
> fail: v4l2-compliance.cpp(537): missing bus_info pre
On 06/16/2016 11:40 PM, Javier Martinez Canillas wrote:
> According to the V4L2 documentation the driver and card fields should be
> used to identify the driver and the device but the gsc-m2m driver fills
> those field using the platform device name, which in turn is the name of
> the device DT nod
On 06/16/2016 11:40 PM, Javier Martinez Canillas wrote:
> The driver fills in both the struct v4l2_capability driver and card fields
> the same values, that is the driver's name plus the information if the dev
> is a decoder or an encoder.
>
> But the driver field has a fixed length of 16 bytes so
On 06/16/2016 11:40 PM, Javier Martinez Canillas wrote:
> The driver doesn't set the struct v4l2_capability cap_info field so the
> v4l2-compliance tool reports the following errors for VIDIOC_QUERYCAP:
>
> Required ioctls:
> VIDIOC_QUERYCAP returned 0 (Success)
> f
On 06/16/2016 11:40 PM, Javier Martinez Canillas wrote:
> According to the V4L2 documentation the driver and card fields should be
> used to identify the driver and the device but the s5p-mfc driver fills
> those field using the platform device name, which in turn is the name of
> the device DT nod
On 06/16/2016 11:40 PM, Javier Martinez Canillas wrote:
> The driver doesn't set the struct v4l2_capability bus_info field so the
> v4l2-compliance tool reports the following errors for VIDIOC_QUERYCAP:
>
> Required ioctls:
> VIDIOC_QUERYCAP returned 0 (Success)
> f
On 06/16/2016 07:02 PM, Steve Longerbeam wrote:
> On 06/16/2016 02:49 AM, Jack Mitchell wrote:
>>
>> On 16/06/16 02:37, Steve Longerbeam wrote:
>>> Hi Jack,
>>>
>>> On 06/15/2016 03:43 AM, Jack Mitchell wrote:
Trying to use a user pointer rather than mmap also fails and causes a
ke
Hi Janusz,
On 06/16/2016 07:21 PM, Janusz Krzysztofik wrote:
> As requested by media subsystem maintainers, here is an attempt to
> convert the omap1_camera driver to the vb2 framework. Also, conversion
> to the dmaengine framework, long awaited by ARM/OMAP maintainers, is
> done.
>
> Next, I'
64 matches
Mail list logo
