* Ivaylo Dimitrov [160622 12:25]:
> ir-rx51 is a driver for Nokia N900 IR transmitter. The current series
> fixes the remaining problems in the driver:
Thanks for updating these.
Trierry, care to ack the PWM patch?
Mauro, do you want me to set up an immutable
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 23 04:00:28 CEST 2016
git branch: test
git hash: 59f0bc11848f8f3242bc1fefae670e745929cd7b
gcc
It is not quite clear what does mutex_lock(>lock) defend against.
If there is a chance that some other code can try to lock the mutex during
probe(),
then
mutex_unlock(>lock);
kfree(dev);
looks suspicious, because when that code get control form mutex_lock(dev->lock)
the dev could be
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
Some touch controllers send out touch data in a similar way to a
greyscale frame grabber.
Use a new device prefix v4l-touch for these devices, to stop generic
capture software from treating them as webcams.
Add formats:
- V4L2_TCH_FMT_DELTA_TD16 for signed 16-bit touch deltas
-
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
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
---
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 ++
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
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(-)
Signed-off-by: Nick Dyer
---
drivers/input/touchscreen/sur40.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/input/touchscreen/sur40.c
b/drivers/input/touchscreen/sur40.c
index 880c40b..841e045 100644
---
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 +
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
On 22/06/2016 21:38, Florian Echtler wrote:
> On Wed, 22 Jun 2016, Nick Dyer wrote:
>
>> On 22/06/2016 12:48, Florian Echtler wrote:
>>> On 20.06.2016 14:00, Hans Verkuil wrote:
On 06/17/2016 04:16 PM, Nick Dyer wrote:
>
> Use a new device prefix v4l-touch for these devices, to stop
On Wed, 22 Jun 2016, Nick Dyer wrote:
On 22/06/2016 12:48, Florian Echtler wrote:
On 20.06.2016 14:00, Hans Verkuil wrote:
On 06/17/2016 04:16 PM, Nick Dyer wrote:
Use a new device prefix v4l-touch for these devices, to stop generic
capture software from treating them as webcams.
Come to
Hi Thomas,
I made some more investigation and figured out that you have a DVB-T2
mux at 642 MHz in Berlin, and can also see that your w_scan actually
locks on that DVB-T2 mux as you wrote. Sorry, I did not read properly
what you were saying in the beginning.
Then it should be just a question of
Convert driver to use PWM framework instead of calling dmtimer functions
directly for PWM timer. Remove paragraph about writing to the Free Software
Foundation's mailing address while at it.
Signed-off-by: Ivaylo Dimitrov
---
The ir-rx51 driver for n900 has been disabled since the multiarch
changes as plat include directory no longer is SoC specific.
Let's fix it with minimal changes to pass the dmtimer calls in
pdata. Then the following changes can be done while things can
be tested to be working for each change:
1.
ir-rx51 is a driver for Nokia N900 IR transmitter. The current series
fixes the remaining problems in the driver:
- replace GP timer 9 with PWM framework usage
- replace pulse width timer dmtimer usage with hrtimer
- add DT support to the driver
- add driver to the board DTS
Patch 2 is
With the upcoming removal of legacy boot, lets add support to one of the
last N900 drivers remaining without it. As the driver still uses omap
dmtimer, add auxdata as well.
Signed-off-by: Ivaylo Dimitrov
Acked-by: Rob Herring
---
OMAP GP timers can have different input clocks that allow different PWM
frequencies. However, there is no other way of setting the clock source but
through clocks or clock-names properties of the timer itself. This limits
PWM functionality to only the frequencies allowed by the particular clock
Drop dmtimer usage for pulse timer in favor of hrtimer. That allows
removing PWM dmitimer platform data usage.
Signed-off-by: Ivaylo Dimitrov
---
arch/arm/mach-omap2/board-rx51-peripherals.c | 4 -
arch/arm/mach-omap2/pdata-quirks.c | 3 -
Hi Thomas,
Ok, the correct firmwares are there:
[ 101.423697] si2168 11-0064: found a 'Silicon Labs Si2168-B40'
[ 101.428693] si2168 11-0064: downloading firmware from file
'dvb-demod-si2168-b40-01.fw'
[ 101.657999] si2168 11-0064: firmware version: 4.0.11
[ 101.661225] si2157 12-0060: found
On 2016-06-22 15:57, Hurda wrote:
kernel: si2168 8-0064: found a 'Silicon Labs Si2168-B40'
kernel: si2168 8-0064: downloading firmware from file
'dvb-demod-si2168-b40-01.fw'
kernel: si2168 8-0064: firmware version: 4.0.19
Distribution is Arch. Kernel version is 4.6.2.
IIRC you have to use
Hi Niklas,
Thank you for the patch.
On Wednesday 22 Jun 2016 02:19:24 Niklas Söderlund wrote:
> This is done in preparation to move s_stream from v4l2_subdev_video_ops
> to v4l2_subdev_pad_ops. Only wpf implements s_stream so it will no
> longer be possible to share the v4l2_subdev_pad_ops once
Hello,
On Tuesday 24 May 2016 19:26:32 Sakari Ailus wrote:
> On Tue, May 24, 2016 at 05:36:42PM +0200, Hans Verkuil wrote:
> > On 05/24/2016 05:28 PM, Sakari Ailus wrote:
> > > Hi Hans,
> > >
> > >> Should it be mentioned here that changing the video format might change
> > >> the buffersize? In
Hi Hans,
Thank you for the review.
On Monday 23 May 2016 12:09:16 Hans Verkuil wrote:
> On 05/12/2016 02:18 AM, Laurent Pinchart wrote:
> > The metadata buffer type is used to transfer metadata between userspace
> > and kernelspace through a V4L2 buffers queue. It comes with a new
> > metadata
kernel: si2168 8-0064: found a 'Silicon Labs Si2168-B40'
kernel: si2168 8-0064: downloading firmware from file
'dvb-demod-si2168-b40-01.fw'
kernel: si2168 8-0064: firmware version: 4.0.19
Distribution is Arch. Kernel version is 4.6.2.
IIRC you have to use firmware-version 4.0.11 in
On 6/21/16 12:40 PM, Richard Cochran wrote:
On Tue, Jun 21, 2016 at 10:45:18AM -0700, Pierre-Louis Bossart wrote:
You can experiment with the 'dma' and 'link' timestamps today on any
HDaudio-based device. Like I said the synchronized part has not been
upstreamed yet (delays + dependency on
Hello,
I bought a TechnoTrend TT-budget CT2-4500 [1,2] DVB-C card and connected
it to my cable, using no CI. A TV connected on the same cable is
working, but the card is not.
I have installed the driver package from openelec [3,4] which includes
all firmware (Version 1 and 2) mentioned in [5]
On 22/06/2016 12:48, Florian Echtler wrote:
> On 20.06.2016 14:00, Hans Verkuil wrote:
>> On 06/17/2016 04:16 PM, Nick Dyer wrote:
>>> 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
Hi!
> > I think libv4l itself has algorithms to control at least some of these. It
> > relies on the image data so the CPU time consumption will be high.
> >
> > AFAIR Laurent has also worked on implementing some algorithms that use the
> > histogram and some of the statistics. Add him to cc
On 20.06.2016 14:00, Hans Verkuil wrote:
> On 06/17/2016 04:16 PM, Nick Dyer wrote:
>> 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
The part can be reset by a low pulse on the RESET pin (i.e. a hardware
reset) with a minimum width of 5 ms. It is recommended to wait 5 ms
after the low pulse before an I2C write is performed to the part.
For safety reasons, the delays will be between 5 and 10 ms.
The RESET pin can be tied high,
Hi!
I tried to capture 1.2Mpix images, then scale them down to 800x600
using hardware... and results were kernel dying.
[12552.400146] [] (isp_video_start_streaming) from
[] (vb2_start_streaming+0x5c/0x154)
[12552.400146] [] (vb2_start_streaming) from []
(vb2_core_streamon+0x104/0x160)
Hi Pavel,
On Tue, Jun 21, 2016 at 08:05:49PM +0200, Pavel Machek wrote:
> 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.
36 matches
Mail list logo