Re: [PATCH v3 2/3] arm64: dts: renesas: draak: Describe CVBS input

2018-05-20 Thread kbuild test robot
Hi Jacopo, I love your patch! Yet something to improve: [auto build test ERROR on linuxtv-media/master] [cannot apply to renesas/next v4.17-rc6] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH v2] v4l: vsp1: Fix vsp1_regs.h license header

2018-05-20 Thread Nobuhiro Iwamatsu
Hi, 2018-05-20 16:24 GMT+09:00 Laurent Pinchart : > All source files of the vsp1 driver are licensed under the GPLv2+ except > for vsp1_regs.h which is licensed under GPLv2. This is caused by a bad > copy that dates back from the initial version of the

Re: [PATCH 0/3] sh_eth: fix typos/grammar

2018-05-20 Thread David Miller
From: Sergei Shtylyov Date: Sat, 19 May 2018 23:57:50 +0300 > Here's a set of 3 patches against DaveM's 'net-next.git' repo plus the > R8A77980 > support patches posted earlier. They fix the comments typos/grammar and > another > typo in the EESR bit...

Re: [Qemu-devel] [PATCH v3 RESEND 3/3] nvram: at24c: use standard error reporting

2018-05-20 Thread Peter Maydell
On 20 May 2018 at 08:00, Wolfram Sang wrote: > Replace the ERR macro with error_report() because fprintf is deprecated. > This also fixes the prefix printed out twice. > > Reviewed-by: Philippe Mathieu-Daudé > Signed-off-by: Wolfram Sang

Re: [PATCH 1/2] vsp-lib: Capture the kernel log messages in test log files

2018-05-20 Thread Niklas Söderlund
Hi Laurent, Thanks for your patch. On 2018-05-19 23:34:25 +0300, Laurent Pinchart wrote: > It can be useful to capture kernel log messages in test log files for > diagnostic purpose. Add a simple mechanism to do so by capturing the > full kernel log at the end of the test. The kernel log is

[PATCH v4 0/3] thermal: add support for r8a77995

2018-05-20 Thread Yoshihiro Kaneko
This series adds thermal support for r8a77995. R-Car D3 (r8a77995) have a thermal sensor module which is similar to Gen2. Therefore this series adds r8a77995 support to rcar_thermal driver not rcar_gen3_thermal driver. This series is based on the next branch of Zhang Rui's linux tree. v4

[PATCH v4 1/3] thermal: rcar_thermal: add r8a77995 support

2018-05-20 Thread Yoshihiro Kaneko
Add support for R-Car D3 (r8a77995) thermal sensor. Signed-off-by: Yoshihiro Kaneko Tested-by: Ulrich Hecht --- drivers/thermal/rcar_thermal.c | 158 - 1 file changed, 126 insertions(+), 32

[PATCH v4 3/3] arm64: dts: renesas: r8a77995: add thermal device support

2018-05-20 Thread Yoshihiro Kaneko
Signed-off-by: Yoshihiro Kaneko Reviewed-by: Geert Uytterhoeven --- arch/arm64/boot/dts/renesas/r8a77995.dtsi | 31 +++ 1 file changed, 31 insertions(+) diff --git a/arch/arm64/boot/dts/renesas/r8a77995.dtsi

[PATCH v4 2/3] dt-bindings: thermal: rcar-thermal: add R8A77995 support

2018-05-20 Thread Yoshihiro Kaneko
Signed-off-by: Yoshihiro Kaneko Reviewed-by: Geert Uytterhoeven --- Documentation/devicetree/bindings/thermal/rcar-thermal.txt | 7 +-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git

Re: [PATCH 5/5] arm64: dts: renesas: r8a77995-draak: add X12 input dot clock

2018-05-20 Thread Laurent Pinchart
Hi Ulrich, Thank you for the patch. On Wednesday, 16 May 2018 11:38:22 EEST Simon Horman wrote: > On Tue, May 15, 2018 at 02:20:40PM +0200, Ulrich Hecht wrote: > > 74.25 Mhz oscillator X12 is connected to DU_DOTCLKIN0. > > > > Signed-off-by: Ulrich Hecht

Re: [PATCH 4/5] arm64: dts: renesas: r8a77995-draak: add HDMI output

2018-05-20 Thread Laurent Pinchart
Hi Ulrich, Thank you for the patch. On Tuesday, 15 May 2018 15:20:39 EEST Ulrich Hecht wrote: > Adds LVDS decoder, HDMI encoder and connector for Draak boards. > > Signed-off-by: Ulrich Hecht Reviewed-by: Laurent Pinchart >

Re: [PATCH 3/5] arm64: dts: renesas: r8a77995: Add LVDS support

2018-05-20 Thread Laurent Pinchart
Hi Ulrich, Thank you for the patch. On Tuesday, 15 May 2018 15:20:38 EEST Ulrich Hecht wrote: > From: Kieran Bingham > > The r8a77995 D3 platform has 2 LVDS channels connected to the DU. > > Signed-off-by: Kieran Bingham

Re: [PATCH 2/5] drm: rcar-du: lvds: Add R8A77995 support

2018-05-20 Thread Laurent Pinchart
Hi Ulrich, Thank you for the patch. On Tuesday, 15 May 2018 15:20:37 EEST Ulrich Hecht wrote: > Add support for the R-Car D3 (R8A77995) SoC to the LVDS encoder driver. > > Signed-off-by: Ulrich Hecht > --- > drivers/gpu/drm/rcar-du/rcar_lvds.c | 6 ++ > 1

Re: [PATCH 0/5] R-Car D3 LVDS/HDMI support

2018-05-20 Thread Laurent Pinchart
Hi Ulrich, On Tuesday, 15 May 2018 15:20:35 EEST Ulrich Hecht wrote: > Hi! > > This adds D3 support to the DU and LVDS drivers, not including LVDS PLL > support. > > It also adds LVDS encoders to the D3 device tree, and LVDS decoder, HDMI > encoder and HDMI output connector to the Draak device

Re: [PATCH 1/5] drm: rcar-du: Add r8a77995 device support

2018-05-20 Thread Laurent Pinchart
Hi Ulrich, Thank you for the patch. On Tuesday, 15 May 2018 15:20:36 EEST Ulrich Hecht wrote: > From: Koji Matsuoka > > Add support for the R-Car D3 (R8A77995) SoC to the R-Car DU driver. > > Signed-off-by: Koji Matsuoka >

[PATCH v2] v4l: vsp1: Fix vsp1_regs.h license header

2018-05-20 Thread Laurent Pinchart
All source files of the vsp1 driver are licensed under the GPLv2+ except for vsp1_regs.h which is licensed under GPLv2. This is caused by a bad copy that dates back from the initial version of the driver. Fix it. Cc: Nobuhiro Iwamatsu Acked-by: Kieran Bingham

Re: [PATCH 1/2] i2c: mux: demux-pinctrl: use proper parent device for demux adapter

2018-05-20 Thread Peter Rosin
On 2018-05-20 08:45, Wolfram Sang wrote: > On Sat, May 19, 2018 at 11:40:04PM +0200, Peter Rosin wrote: >> On 2018-04-30 13:55, Wolfram Sang wrote: >>> Due to a typo, the wrong parent device was assigned to the newly created >>> demuxing adapter device. It got connected to the demuxing platform

Re: [PATCH v6 9/9] v4l: vsp1: Reduce display list body size

2018-05-20 Thread Laurent Pinchart
Hi Kieran, On Wednesday, 28 February 2018 22:52:43 EEST Kieran Bingham wrote: > The display list originally allocated a body of 256 entries to store all > of the register lists required for each frame. > > This has now been separated into fragments for constant stream setup, and > runtime

[PATCH v3 RESEND 0/3] nvram: at24c: fix problems related to "rom-size"

2018-05-20 Thread Wolfram Sang
I used this driver as a template for a custom one. While hacking on my own, I noticed some problems in this driver, too. This series fixes the first set of them, related to the "rom-size" parameter. It fixes a segfault. I think the first patch is clearly suitable for stable. I think the second

[PATCH v3 RESEND 1/3] nvram: at24c: prevent segfault by checking "rom-size"

2018-05-20 Thread Wolfram Sang
The value for "rom-size" is used as a divisor, so it must not be 0 or it will segfault. A size of 0 wouldn't make sense anyhow. Reviewed-by: Philippe Mathieu-Daudé Signed-off-by: Wolfram Sang --- hw/nvram/eeprom_at24c.c | 5 + 1 file

[PATCH v3 RESEND 3/3] nvram: at24c: use standard error reporting

2018-05-20 Thread Wolfram Sang
Replace the ERR macro with error_report() because fprintf is deprecated. This also fixes the prefix printed out twice. Reviewed-by: Philippe Mathieu-Daudé Signed-off-by: Wolfram Sang --- hw/nvram/eeprom_at24c.c | 17 ++--- 1 file

[PATCH v3 RESEND 2/3] nvram: at24c: use a sane default for "rom-size"

2018-05-20 Thread Wolfram Sang
0 as "rom-size" will lead to an error message. Let's use the size of a small 24c01 which has 128 byte. Reviewed-by: Philippe Mathieu-Daudé Signed-off-by: Wolfram Sang --- hw/nvram/eeprom_at24c.c | 5 - 1 file changed, 4 insertions(+), 1

Re: [PATCH 2/2] i2c: mux: demux-pinctrl: add symlinks to the demux device in sysfs

2018-05-20 Thread Wolfram Sang
> > + sysfs_create_link(>cur_adap.dev.kobj, >dev->kobj, > > + "demux_device"); > > + sysfs_create_link(>dev->kobj, >cur_adap.dev.kobj, > > + "channel-0"); > > + > > From sysfs.h: > int __must_check sysfs_create_link(...); Darn, right... Will

Re: [PATCH 1/2] i2c: mux: demux-pinctrl: use proper parent device for demux adapter

2018-05-20 Thread Wolfram Sang
On Sat, May 19, 2018 at 11:40:04PM +0200, Peter Rosin wrote: > On 2018-04-30 13:55, Wolfram Sang wrote: > > Due to a typo, the wrong parent device was assigned to the newly created > > demuxing adapter device. It got connected to the demuxing platform > > device but not to the selected parent I2C