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: Thu Jun 2 04:00:27 CEST 2016
git branch: test
git hash: de42e7655d504ceeda53e009b8860ba4bd007ab5
gcc versi
On Wed 2016-06-01 18:24:39, Sakari Ailus wrote:
> Hi Pavel,
> > Well, it does not use any dt properties. So there's not really much to
> > discuss with dt people...
> >
> > Maybe "ad5820" needs to go to list of simple i2c drivers somewhere,
> > but...
>
> It's an I2C device and it does use a reg
On Wed, Jun 01, 2016 at 05:39:44PM +0100, Nick Dyer wrote:
> This is a series of patches to add diagnostic data support to the Atmel
> maXTouch driver. 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.
>
> T
On Wed, Jun 01, 2016 at 05:39:48PM +0100, Nick Dyer wrote:
> Register a video device to output T37 diagnostic data.
>
> Signed-off-by: Nick Dyer
> ---
> drivers/input/touchscreen/Kconfig| 2 +
> drivers/input/touchscreen/atmel_mxt_ts.c | 247
> +++
> 2 file
On Wed, Jun 01, 2016 at 05:39:51PM +0100, Nick Dyer wrote:
> 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 | 29 ++---
> 1 file cha
Hi Nick,
On Wed, Jun 01, 2016 at 05:39:45PM +0100, Nick Dyer wrote:
> 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
>
This is a series of patches to add diagnostic data support to the Atmel
maXTouch driver. 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.
There are significant performance advantages to putting this code into th
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
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 +
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/
Register a video device to output T37 diagnostic data.
Signed-off-by: Nick Dyer
---
drivers/input/touchscreen/Kconfig| 2 +
drivers/input/touchscreen/atmel_mxt_ts.c | 247 +++
2 files changed, 249 insertions(+)
diff --git a/drivers/input/touchscreen/Kconfig
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/atmel_mxt_ts.c | 152
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 | 29 ++---
1 file changed, 26 insertions(+), 3 deletions(-)
diff --git a/drivers/input/touchs
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/
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
On 27/05/2016 13:54, Hans Verkuil wrote:
> Hi Nick,
Thanks for the useful review. Most of it is straightforward and I've
updated it in a new version of these patches which I will post now.
I think the open question is whether you're happy with the
V4L2_PIX_FMT_YS16 or whether I need to rename it.
Hello all,
The purpose of this RFC is to define SDI timings structure and potentially the
associated API in the V4L2 API.
** Context **
Currently, V4L2 API has a structure to define CEA-861 / VESA timings. If these
timings are common in monitor and general market, in the industry or television
Hi Pavel,
On Tue, May 31, 2016 at 11:34:37PM +0200, Pavel Machek wrote:
> On Wed 2016-06-01 00:22:22, Sakari Ailus wrote:
> > Hi Pavel,
> >
> > On Fri, May 27, 2016 at 10:51:40PM +0200, Pavel Machek wrote:
> > >
> > > This adds support for AD5820 autofocus coil, found for example in
> > > Nokia
On Fri, May 27, 2016 at 06:38:49PM +0300, Todor Tomov wrote:
> Add the document for ov5645 device tree binding.
>
> Signed-off-by: Todor Tomov
> ---
> .../devicetree/bindings/media/i2c/ov5645.txt | 50
> ++
> 1 file changed, 50 insertions(+)
> create mode 100644 Docum
Patrick Keshishian improved the explanation of the protocol when porting
the driver to OpenBSD. Given it's a reverse engineering one and there's
no documetnation it might be helpful to whoever hacks on the driver.
Signed-off-by: Patrick Keshishian
Signed-off-by: Lubomir Rintel
---
drivers/media
OpenBSD would like to reuse some code but consider the licensing not
clear enough. Let's clarify it a bit so that it suits their conventions:
1.) Keep the "extra text" away from the copyright statement and the
rights grant.
2.) Add the warranty disclaimer -- it should not be legally required,
nev
Applied for 4.8, thanks!
Antti
On 04/06/2016 01:23 AM, Alessandro Radicati wrote:
This patch will modify the af9035 driver to use the register address
fields of the I2C read command for the combined write/read transaction
case. Without this change, the firmware issues just a I2C read transacti
Applied for 4.8, thanks!
Antti
On 05/12/2016 01:47 PM, Alessandro Radicati wrote:
The MXL5007T tuner will lock-up on some devices after an I2C
read transaction. This patch works around this issue by inhibiting such
operations and emulating a 0x00 response. The workaround is only applied to
US
23 matches
Mail list logo