Re: [PATCH v4 1/9] dt-bindings: media: Add Renesas CEU bindings

On Fri, Jan 12, 2018 at 12:50:41AM +0200, Laurent Pinchart wrote: > Hi Jacopo, > > Thank you for the patch. > > On Tuesday, 9 January 2018 18:25:23 EET Jacopo Mondi wrote: > > Add bindings documentation for Renesas Capture Engine Unit (CEU). > > > > Signed-off-by: Jacopo Mondi > > Reviewed-by:

Re: [PATCH v2 09/22] mmc: tmio: use mmc_can_gpio_cd() instead of checking TMIO_MMC_USE_GPIO_CD

Hi Ulf, 2018-01-02 21:56 GMT+09:00 Wolfram Sang : > On Sat, Nov 25, 2017 at 01:24:44AM +0900, Masahiro Yamada wrote: >> To use a GPIO line for card detection, TMIO_MMC_USE_GPIO_CD is set >> by a legacy board (arch/sh/boards/mach-ecovec24). >> >> For DT platforms, the "cd-gpios" property is a legi

[PATCH] drm: rcar-du: Enable VSP compositor by default on Gen3

On Gen3 hardware the VSP compositor is required for display. Enable it by default in the kernel configuration. The option is kept user-configurable for testing purpose on Gen2 platforms. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/rcar-du/Kconfig | 3 ++- 1 file changed, 2 insertions(+),

Re: [PATCH 1/3] drm: rcar-du: lvds: refactor LVDS startup

Hi Sergei, Thank you for the patch. On Thursday, 11 January 2018 18:54:33 EET Sergei Shtylyov wrote: > After the recent correction of the R-Car gen3 LVDCR1 value, already similar > enough at their ends rcar_du_lvdsenc_start_gen{2|3}() started asking for a > merge and it's becoming actually neces

Re: [PATCH 3/3] drm: rcar-du: add R8A77970 support

Hi Sergei, Thank you for the patch. On Thursday, 11 January 2018 18:54:35 EET Sergei Shtylyov wrote: > Add support for the R-Car V3M (R8A77970) SoC to the DU driver (this SoC > has only 1 display port). Note that there are some differences with the > other R-Car gen3 SoCs in the LVDS encoder

[PATCH 05/10] ARM: dts: porter: Fix HDMI output routing

The HDMI encoder is connected to the RGB output of the DU, which is port@0, not port@1. Fix the incorrect DT description. Signed-off-by: Laurent Pinchart --- arch/arm/boot/dts/r8a7791-porter.dts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm/boot/dts/r8a7791-porter.

[PATCH 04/10] drm: rcar-du: Convert LVDS encoder code to bridge driver

The LVDS encoders used to be described in DT as part of the DU. They now have their own DT node, linked to the DU using the OF graph bindings. This allows moving internal LVDS encoder support to a separate driver modelled as a DRM bridge. Backward compatibility is retained as legacy DT is patched l

[PATCH 02/10] dt-bindings: display: renesas: Deprecate LVDS support in the DU bindings

The internal LVDS encoders now have their own DT bindings, representing them as part of the DU is deprecated. Signed-off-by: Laurent Pinchart --- .../devicetree/bindings/display/renesas,du.txt | 26 +- 1 file changed, 11 insertions(+), 15 deletions(-) diff --git a/Docume

[PATCH 03/10] drm: rcar-du: Fix legacy DT to create LVDS encoder nodes

The internal LVDS encoders now have their own DT bindings. Before switching the driver infrastructure to those new bindings, implement backward-compatibility through live DT patching. Patching is disabled and will be enabled along with support for the new DT bindings in the DU driver. Signed-off-

[PATCH 00/10] R-Car DU: Convert LVDS code to bridge driver

Hello, This patch series addresses a design mistake that dates back from the initial DU support. Support for the LVDS encoders, which are IP cores separate from the DU, was bundled in the DU driver. Worse, both the DU and LVDS were described through a single DT node. To fix the, patches 01/10 and

[PATCH 01/10] dt-bindings: display: renesas: Add R-Car LVDS encoder DT bindings

The Renesas R-Car Gen2 and Gen3 SoCs have internal LVDS encoders. Add corresponding device tree bindings. Signed-off-by: Laurent Pinchart --- .../bindings/display/bridge/renesas,lvds.txt | 54 ++ MAINTAINERS| 1 + 2 files changed

[PATCH 09/10] arm64: dts: renesas: r8a7795: Convert to new LVDS DT bindings

The internal LVDS encoder now has DT bindings separate from the DU. Port the device tree over to the new model. Signed-off-by: Laurent Pinchart --- .../boot/dts/renesas/r8a7795-es1-salvator-x.dts| 3 +- arch/arm64/boot/dts/renesas/r8a7795-h3ulcb.dts | 3 +- arch/arm64/boot/dts/renesas/

[PATCH 08/10] ARM: dts: r8a7793: Convert to new LVDS DT bindings

The internal LVDS encoder now has DT bindings separate from the DU. Port the device tree over to the new model. Signed-off-by: Laurent Pinchart --- arch/arm/boot/dts/r8a7793-gose.dts | 10 +++--- arch/arm/boot/dts/r8a7793.dtsi | 35 +-- 2 files changed, 36

[PATCH 10/10] arm64: dts: renesas: r8a7796: Convert to new LVDS DT bindings

The internal LVDS encoder now has DT bindings separate from the DU. Port the device tree over to the new model. Signed-off-by: Laurent Pinchart --- arch/arm64/boot/dts/renesas/r8a7796-m3ulcb.dts | 3 +- arch/arm64/boot/dts/renesas/r8a7796-salvator-x.dts | 3 +- arch/arm64/boot/dts/renesas/

[PATCH 06/10] ARM: dts: r8a7790: Convert to new LVDS DT bindings

The internal LVDS encoder now has DT bindings separate from the DU. Port the device tree over to the new model. Signed-off-by: Laurent Pinchart --- arch/arm/boot/dts/r8a7790-lager.dts | 22 ++--- arch/arm/boot/dts/r8a7790.dtsi | 61 - 2 files chan

[PATCH 07/10] ARM: dts: r8a7791: Convert to new LVDS DT bindings

The internal LVDS encoder now has DT bindings separate from the DU. Port the device tree over to the new model. Signed-off-by: Laurent Pinchart --- arch/arm/boot/dts/r8a7791-koelsch.dts | 10 -- arch/arm/boot/dts/r8a7791-porter.dts | 16 +--- arch/arm/boot/dts/r8a7791.dtsi

Re: [PATCH] drm: rcar-du: lvds: fix LVDCR1 for R-Car gen3

Hi Sergei, On Thursday, 21 December 2017 22:23:30 EET Sergei Shtylyov wrote: > The LVDCR1 register for the R-Car gen3 SoCs was documented as having the > layout different from the gen2 SoCs in the early R-Car gen3 manuals but > since v0.52 the LVDCR1 layout is described as being the same as on th

Re: [PATCH v4 3/9] v4l: platform: Add Renesas CEU driver

On Tuesday, 9 January 2018 18:25:25 EET Jacopo Mondi wrote: > Add driver for Renesas Capture Engine Unit (CEU). > > The CEU interface supports capturing 'data' (YUV422) and 'images' > (NV[12|21|16|61]). > > This driver aims to replace the soc_camera-based sh_mobile_ceu one. > > Tested with ov767

Re: [PATCH v4 1/9] dt-bindings: media: Add Renesas CEU bindings

Hi Jacopo, Thank you for the patch. On Tuesday, 9 January 2018 18:25:23 EET Jacopo Mondi wrote: > Add bindings documentation for Renesas Capture Engine Unit (CEU). > > Signed-off-by: Jacopo Mondi Reviewed-by: Laurent Pinchart > --- > .../devicetree/bindings/media/renesas,ceu.txt | 81 >

Re: [PATCH v4 1/9] dt-bindings: media: Add Renesas CEU bindings

On Tue, Jan 09, 2018 at 05:25:23PM +0100, Jacopo Mondi wrote: > Add bindings documentation for Renesas Capture Engine Unit (CEU). > > Signed-off-by: Jacopo Mondi > --- > .../devicetree/bindings/media/renesas,ceu.txt | 81 > ++ > 1 file changed, 81 insertions(+) > creat

Re: [PATCH v4 2/3] dt-bindings: usb: renesas_usbhs: Add support for RZ/A1

On Mon, Jan 08, 2018 at 07:30:54AM -0500, Chris Brandt wrote: > Document support for RZ/A1 SoCs > > Signed-off-by: Chris Brandt > Reviewed-by: Geert Uytterhoeven > --- > v4: > * Re-added "renesas,usbhs-r7s72100" > v3: > * Removed "renesas,usbhs-r7s72100" > v2: > * Added Reviewed-by > --- > D

[PATCH] ARM: dts: iwg22m: Enable cmt0

This patch enables cmt0 support from within the iwg22m SoM dtsi. Signed-off-by: Fabrizio Castro Reviewed-by: Biju Das --- arch/arm/boot/dts/r8a7745-iwg22m.dtsi | 4 1 file changed, 4 insertions(+) diff --git a/arch/arm/boot/dts/r8a7745-iwg22m.dtsi b/arch/arm/boot/dts/r8a7745-iwg22m.dtsi

[PATCH] ARM: dts: iwg20m: Enable cmt0

This patch enables cmt0 support from within the iwg20m SoM dtsi. Signed-off-by: Fabrizio Castro Reviewed-by: Biju Das --- arch/arm/boot/dts/r8a7743-iwg20m.dtsi | 4 1 file changed, 4 insertions(+) diff --git a/arch/arm/boot/dts/r8a7743-iwg20m.dtsi b/arch/arm/boot/dts/r8a7743-iwg20m.dtsi

Re: [PATCH] net: phy: Fix phy_modify() semantic difference fallout

On 01/11/2018 07:48 AM, David Miller wrote: > From: Geert Uytterhoeven > Date: Tue, 9 Jan 2018 12:11:21 +0100 > >> In case of success, the return values of (__)phy_write() and >> (__)phy_modify() are not compatible: (__)phy_write() returns 0, while >> (__)phy_modify() returns the old PHY registe

Re: [PATCH v2] PM / runtime: Rework pm_runtime_force_suspend/resume()

On Thu, Jan 11, 2018 at 1:32 PM, Ulf Hansson wrote: [cut] >>> >>> The point is, we can go for this solution, but is it good enough? >> >> I would like to treat it as a step away from what is there today, >> retaining some of the existing functionality. >> >> From a quick look at the existing use

Re: [PATCH] net: phy: Fix phy_modify() semantic difference fallout

> Sorry, the phy_restore_page() semantics are driving me crazy. > Let's revert. I will try to take a look today. Andrew

[PATCH 2/3] drm: rcar-du: add model field to struct rcar_du_device_info

In order to add the R-Car V3M (R8A77970) support to the DU driver we'd need to keep track not only of the SoC generation but also of the exact model (for the LVDS encoder support). Therefore add the 'model' field to the 'struct rcar_du_device_info' and initialize it accordingly for the alrea

[PATCH 1/3] drm: rcar-du: lvds: refactor LVDS startup

After the recent correction of the R-Car gen3 LVDCR1 value, already similar enough at their ends rcar_du_lvdsenc_start_gen{2|3}() started asking for a merge and it's becoming actually necessary with the addition the R-Car V3M (R8A77970) support -- this gen3 SoC has gen2-like LVDPLLCR layout. BT

[PATCH 3/3] drm: rcar-du: add R8A77970 support

Add support for the R-Car V3M (R8A77970) SoC to the DU driver (this SoC has only 1 display port). Note that there are some differences with the other R-Car gen3 SoCs in the LVDS encoder part, e.g. LVDPLLCR has the same layout as on the R-Car gen2 SoCs... Signed-off-by: Sergei Shtylyov ---

[PATCH 0/3] Add R-Car V3M (R8A77970) support to the DU driver

Hello! Here's the set of 3 patches against the 'drm-next' branch of David Airlie's 'linux.git' repo plus the patch fixing LVDCR1 for R-Car gen3 posted recently. The main purpose of these patches is to add the R-Car V3M (R8A77970) support to the DU driver, we have to do some refactoring first to ac

Re: [PATCH] net: phy: Fix phy_modify() semantic difference fallout

On Thu, Jan 11, 2018 at 05:00:03PM +0100, Geert Uytterhoeven wrote: > On Thu, Jan 11, 2018 at 4:54 PM, Geert Uytterhoeven > wrote: > > On Thu, Jan 11, 2018 at 4:53 PM, Russell King - ARM Linux > > wrote: > >> On Thu, Jan 11, 2018 at 10:48:35AM -0500, David Miller wrote: > >>> From: Geert Uytterho

Re: [PATCH] net: phy: Fix phy_modify() semantic difference fallout

On Thu, Jan 11, 2018 at 4:54 PM, Geert Uytterhoeven wrote: > On Thu, Jan 11, 2018 at 4:53 PM, Russell King - ARM Linux > wrote: >> On Thu, Jan 11, 2018 at 10:48:35AM -0500, David Miller wrote: >>> From: Geert Uytterhoeven >>> Date: Tue, 9 Jan 2018 12:11:21 +0100 >>> >>> > In case of success, th

Re: [PATCH] net: phy: Fix phy_modify() semantic difference fallout

On Thu, Jan 11, 2018 at 4:53 PM, Russell King - ARM Linux wrote: > On Thu, Jan 11, 2018 at 10:48:35AM -0500, David Miller wrote: >> From: Geert Uytterhoeven >> Date: Tue, 9 Jan 2018 12:11:21 +0100 >> >> > In case of success, the return values of (__)phy_write() and >> > (__)phy_modify() are not

Re: [PATCH] net: phy: Fix phy_modify() semantic difference fallout

On Thu, Jan 11, 2018 at 10:48:35AM -0500, David Miller wrote: > From: Geert Uytterhoeven > Date: Tue, 9 Jan 2018 12:11:21 +0100 > > > In case of success, the return values of (__)phy_write() and > > (__)phy_modify() are not compatible: (__)phy_write() returns 0, while > > (__)phy_modify() return

Re: [PATCH] ARM: dts: lager: Add CEC clock for HDMI transmitter

On Tue, Jan 09, 2018 at 05:49:04PM +0100, Niklas Söderlund wrote: > The adv7511 on the Lager board has a 12 MHz fixed clock > for the CEC block. Specify this in the dts to enable CEC support. > > Based on a similar patch for Koelsch by Hans Verkuil. > > Signed-off-by: Niklas Söderlund > Tested-b

Re: [PATCH] net: phy: Fix phy_modify() semantic difference fallout

From: Geert Uytterhoeven Date: Tue, 9 Jan 2018 12:11:21 +0100 > In case of success, the return values of (__)phy_write() and > (__)phy_modify() are not compatible: (__)phy_write() returns 0, while > (__)phy_modify() returns the old PHY register value. > > Apparently this change was catered for

Re: [PATCH v2] PM / runtime: Rework pm_runtime_force_suspend/resume()

[...] >>> Index: linux-pm/drivers/base/power/domain.c >>> === >>> --- linux-pm.orig/drivers/base/power/domain.c >>> +++ linux-pm/drivers/base/power/domain.c >>> @@ -1048,8 +1048,9 @@ static int genpd_finish_suspend(struct d >>>

Re: [PATCH] gpio: Add missing open drain/source handling to gpiod_set_value_cansleep()

On úterý 9. ledna 2018 19:08:21 CET, Geert Uytterhoeven wrote: Since commit f11a04464ae57e8d ("i2c: gpio: Enable working over slow can_sleep GPIOs"), probing the i2c RTC connected to an i2c-gpio bus on r8a7740/armadillo fails with: rtc-s35390a 0-0030: error resetting chip rtc-s35390a: pr

[PATCH/RFC] usb: host: xhci-plat and rcar: reinitialize the xhci when the mode changes

This patch adds extcon notifier to reinitialize the xhci when the mode of R-Car USB 3.0 controller changes from peripheral to host. Otherwise, the host controller cannot detect Super Speed after changed the mode because the PORTSC.PLS for usb3.0 will be set to Disabled. TODO in this RFC version: