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: Sun Dec 17 05:00:15 CET 2017
media-tree git hash:45267fed3e55845c5b4b279162b273040ae4f587
media_build
From: Alexandru Gheorghe
The VSP2 found in R-Car Gen3 SoCs supports changing the alpha value of
source pixels that match a color key. Add support for this feature for
display pipelines through the API exposed to the DU driver.
The colorkey key value is expressed
Now that KMS has standard color keying properties, instantiate them for
all the non-primary planes. This replaces the custom colorkey field in
the driver plane state structure. The custom colorkey property is kept
to ensure backward-compatibility, but now implemented as an alias for
the standard
Hello,
This patch series is an attempt at implementing standard properties for color
keying support in the KMS API.
Before designing the API proposal I've analyzed the KMS drivers that support
color keying in the upstream kernel. Part of the explanation below was
initially posted in a reply to
Gen3 hardware supports color keying with replacement of the pixel value.
Implement it using the standard KMS colorkey properties.
Signed-off-by: Laurent Pinchart
---
drivers/gpu/drm/rcar-du/rcar_du_vsp.c | 16
1 file changed, 16
Color keying is the action of replacing pixels matching a given color
(or range of colors) with transparent pixels in an overlay when
performing blitting. Depending on the hardware capabilities, the
matching pixel can either become fully transparent, or gain a
programmable alpha value.
Color
Hi Tim,
On Thu, Nov 9, 2017 at 4:45 PM, Tim Harvey wrote:
> +static int tda1997x_set_power(struct tda1997x_state *state, bool on)
> +{
> + int ret = 0;
> +
> + if (on) {
> + ret = regulator_bulk_enable(TDA1997X_NUM_SUPPLIES,
> +
>From 8ca5f86d480f397f32626250cebab5b63eb79034 Mon Sep 17 00:00:00 2001
From: Kieran Kunhya
Date: Sat, 16 Dec 2017 18:40:22 +
Subject: [PATCH] libdvbv5: Add libudev to pkg-config file
Signed-off-by: Kieran Kunhya
---
lib/libdvbv5/libdvbv5.pc.in | 2 +-
1
On Sat, Dec 16, 2017 at 11:44:13AM +0100, Hans Verkuil wrote:
> Mention the maximum voltages of the CEC and HPD lines. Since in the example
> these lines are connected to a Raspberry Pi and the Rpi GPIO lines are 3.3V
> it is a good idea to warn against directly connecting the HPD to the Raspberry
gOn Sat, Dec 16, 2017 at 03:49:11AM +0100, Philipp Rossak wrote:
> This patch updates documentation for Device-Tree bindings for sunxi IR
> controller and adds the new requiered property for the base clock frequency.
>
> Signed-off-by: Philipp Rossak
> ---
>
Tim,
On Sat, Dec 16, 2017 at 7:00 PM, Tim Harvey wrote:
> Cc: Rob Herring
> Acked-by: Sakari Ailus
> Signed-off-by: Tim Harvey
> --- /dev/null
> +++ b/include/dt-bindings/media/tda1997x.h
> @@ -0,0
This is a v4l2 subdev driver supporting the TDA1997x HDMI video receiver.
I've tested this on a Gateworks GW54xx/GW551x with an IMX6Q/IMX6DL which
uses the TDA19971 with 16bits connected to the IMX6 CSI. For this
configuration I've tested both 16bit YUV422 and 8bit BT656 parallel video
bus modes.
From: Hans Verkuil
Add the v4l2_hdmi_colorimetry() function so we have a single function
that determines the colorspace, YCbCr encoding, quantization range and
transfer function from the InfoFrame data.
Signed-off-by: Hans Verkuil
Signed-off-by: Tim
Signed-off-by: Tim Harvey
---
MAINTAINERS | 8
1 file changed, 8 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index aa71ab52f..502bc97 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -13244,6 +13244,14 @@ T: git git://linuxtv.org/mkrufky/tuners.git
S:
The GW54xx has a front-panel microHDMI connector routed to a TDA19971
which is connected the the IPU CSI when using IMX6Q.
Signed-off-by: Tim Harvey
---
v5:
- remove leading 0 from unit address
- add newline between property list and child node
v4: no changes
v3: no
Signed-off-by: Tim Harvey
---
v5:
- add missing audmux config
---
arch/arm/boot/dts/imx6qdl-gw551x.dtsi | 138 ++
1 file changed, 138 insertions(+)
diff --git a/arch/arm/boot/dts/imx6qdl-gw551x.dtsi
b/arch/arm/boot/dts/imx6qdl-gw551x.dtsi
Add support for the TDA1997x HDMI receivers.
Cc: Hans Verkuil
Signed-off-by: Tim Harvey
---
v5:
- uppercase string constants
- use v4l2_hdmi_rx_coloriemtry to fill format
- fix V4L2_CID_DV_RX_RGB_RANGE
- fix interlaced mode format
v4:
- move
Cc: Rob Herring
Acked-by: Sakari Ailus
Signed-off-by: Tim Harvey
---
v5:
- added Sakari's ack
v4:
- move include/dt-bindings/media/tda1997x.h to bindings patch
- clarify port node details
v3:
- fix typo
v2:
- add
Hey Mauro,
Thanks for your fast feedback!
I will rework the driver like you suggested it.
Does somebody have any concerns about the Devicetree property
(base-clk-frequency = < frequency >;)?
Regards,
Philipp
On 16.12.2017 10:18, Mauro Carvalho Chehab wrote:
Em Sat, 16 Dec 2017 03:49:10
I will do what I can. Kind of surprising to have something like this
happen now after so many years of stability. There must have been some
kind of environmental change that set this up.
-Mike
On Sat, 16 Dec 2017, Hans Verkuil wrote:
> Hi Mike,
>
> Can you take a look?
>
> Regards,
>
Dear all,
I am trying to get the cameras in a Lenovo IdeaPad Miix 320 (Atom
x5-Z8350 BayTrail) to work. The front camera is an ov2680. With kernel
4.14.4 and 4.15rc3 I see the following dmesg output:
[ 21.469907] ov2680: module is from the staging directory, the quality
is unknown, you have
My wife and I have awarded you with a donation of $ 1,000,000.00, respond with
your details for claims.
Best Regards,
Friedrich And Annand Mayrhofer.
Em Sat, 16 Dec 2017 19:53:55 +0800
Jia-Ju Bai escreveu:
> Hi,
>
> On 2017/12/15 22:51, Fabien DESSENNE wrote:
> > Hi
> >
> > On 12/12/17 14:47, Jia-Ju Bai wrote:
> >> The driver may sleep under a spinlock.
> >> The function call path is:
> >> bdisp_device_run (acquire
Em Thu, 14 Dec 2017 22:55:02 +0100
Ralph Metzler escreveu:
> Hello Dan Carpenter,
>
> Dan Carpenter writes:
> > Hello Ralph Metzler,
> >
> > The patch 126f1e618870: "drx: add initial drx-d driver" from Mar 12,
> > 2011, leads to the following static checker warning:
>
This commit adds a new property DTV_SCRAMBLING_SEQUENCE_INDEX.
This 18 bit field, when present, carries the index of the DVB-S2 physical
layer scrambling sequence as defined in clause 5.5.4 of EN 302 307.
There is no explicit signalling method to convey scrambling sequence index
to the receiver.
A new property DTV_SCRAMBLING_SEQUENCE_INDEX introduced to control
the gold sequence that several demods support.
Also the DVB API was increased in order userspace to be aware of the
changes.
The stv090x driver was changed to make use of the new property.
Those commits based on discussion
This commit uses the new property scrambling_sequence_index
to control PLS.
By default we are using the gold sequence 0 and only gold sequences
expected on the new property.
Please note that all services use PLS, just most with the default
sequence 0 and many demods only support gold 0.
I'm really sorry. This warning showed up in my new warnings pile and I
didn't look at the date. :/ Sorry for the noise.
regards,
dan carpenter
Hi,
On 2017/12/15 22:51, Fabien DESSENNE wrote:
Hi
On 12/12/17 14:47, Jia-Ju Bai wrote:
The driver may sleep under a spinlock.
The function call path is:
bdisp_device_run (acquire the spinlock)
bdisp_hw_reset
msleep --> may sleep
To fix it, msleep is replaced with mdelay.
May I
The driver may sleep under a spinlock.
The function call path is:
bdisp_device_run (acquire the spinlock)
bdisp_hw_reset
msleep --> may sleep
To fix it, readl_poll_timeout_atomic is used to replace msleep.
This bug is found by my static analysis tool(DSAC) and
checked by my code review.
Em Sat, 16 Dec 2017 14:49:41 +1100
Vincent McIntyre escreveu:
> On Fri, Dec 15, 2017 at 11:41:13PM +1100, Vincent McIntyre wrote:
> >
> > ...
> >
> > $ make allyesconfig
> > make -C /home/me/git/clones/media_build/v4l allyesconfig
> > make[1]: Entering directory
My wife and I have awarded you with a donation of $ 1,000,000.00, respond with
your details for claims.
Best Regards,
Friedrich And Annand Mayrhofer.
Mention the maximum voltages of the CEC and HPD lines. Since in the example
these lines are connected to a Raspberry Pi and the Rpi GPIO lines are 3.3V
it is a good idea to warn against directly connecting the HPD to the Raspberry
Pi's GPIO line.
Signed-off-by: Hans Verkuil
Hi Vincent,
A lot of code has been merged this week and more is in the pipeline for next
week.
I'd rather wait until that's in before looking at build failures.
Regards,
Hans
On 16/12/17 04:49, Vincent McIntyre wrote:
> On Fri, Dec 15, 2017 at 11:41:13PM +1100, Vincent McIntyre wrote:
Hi Mike,
Can you take a look?
Regards,
Hans
On 16/12/17 00:02, Oleksandr Ostrenko wrote:
> Dear all,
>
> Unplugging the TV tuner (WinTV HVR-1900) from USB port causes a NULL pointer
> dereference in pvr2_v4l2_internal_check:
>
> [ 2128.129776] usb 1-1: USB disconnect, device number
Em Sat, 16 Dec 2017 03:49:10 +0100
Philipp Rossak escreveu:
Hi Phillip,
This is not a full review of this patchset. I just want to point you
that you should keep supporting existing DT files.
> This patch updates the sunxi-ir driver to set the ir base clock from
>
36 matches
Mail list logo