RE: [PATCH] arm64: dts: renesas: salvator-common: add dr_mode property for USB2.0 channel 0

Hi Simon-san, > From: Yoshihiro Shimoda, Sent: Thursday, October 12, 2017 6:24 PM > > Since Salvator-X[S] have a USB2.0 dual-role channel (CN9), this patch > adds dr_mode property for USB2.0 channel 0 (EHCI/OHCI and HS-USB) > as "otg". > > Signed-off-by: Yoshihiro Shimoda

[PATCH v6 00/10] rockchip: kevin: Enable edp display

Make edp display works on chromebook kevin(at least for boot animation). Also solve some issues i meet during the bringup. Changes in v6: Don't change order of rockchip_drm_psr_register(). Changes in v5: Call the destroy hook in the error handling path like in unbind(). Call the destroy hook

[PATCH v6 09/10] drm/bridge/synopsys: dw-hdmi: Do not use device's drvdata

Let plat drivers own the drvdata, so that they could cleanup resources in their unbind(). Signed-off-by: Jeffy Chen Reviewed-by: Neil Armstrong --- Changes in v6: None Changes in v5: None drivers/gpu/drm/bridge/synopsys/dw-hdmi.c | 43

Re: [PATCH 1/2] mmc: renesas_sdhi: fix swiotlb buffer is full

On Tue, Oct 17, 2017 at 10:02:50AM +0200, Geert Uytterhoeven wrote: > Hi Shimoda-san, > > CC iommu > > On Tue, Oct 17, 2017 at 9:30 AM, Yoshihiro Shimoda > wrote: > > Since the commit de3ee99b097d ("mmc: Delete bounce buffer handling") > > deletes the bounce

RE: [PATCH] i2c: riic: remove clock and frequency restrictions

On Wednesday, October 18, 2017 1, Wolfram Sang wrote: > > + brl -= t->scl_fall_ns / (10/rate); > > + brh -= t->scl_rise_ns / (10/rate); > > However you solve the precision issue, please take care about the "space > around operators" rule afterwards. checkpatch should help you

Re: [PATCH] i2c: riic: remove clock and frequency restrictions

> + brl -= t->scl_fall_ns / (10/rate); > + brh -= t->scl_rise_ns / (10/rate); However you solve the precision issue, please take care about the "space around operators" rule afterwards. checkpatch should help you there. signature.asc Description: PGP signature

Re: [PATCH v5 8/9] drm/bridge/synopsys: dw-hdmi: Do not use device's drvdata

On 18/10/2017 14:09, Jeffy Chen wrote: > Let plat drivers own the drvdata, so that they could cleanup resources > in their unbind(). > > Signed-off-by: Jeffy Chen > --- > > Changes in v5: None > > drivers/gpu/drm/bridge/synopsys/dw-hdmi.c | 43 >

RE: [PATCH] i2c: riic: remove clock and frequency restrictions

Hi Geert, On Wednesday, October 18, 2017 1, Geert Uytterhoeven wrote: > >> > + /* > >> > +* Remove clock ticks for rise and fall times. Convert ns to > >> clock > >> > +* ticks. > >> > +*/ > >> > + brl -= t->scl_fall_ns / (10/rate); > >> > + brh

Re: [PATCH] i2c: riic: remove clock and frequency restrictions

Hi Chris, On Wed, Oct 18, 2017 at 5:10 PM, Chris Brandt wrote: > On Wednesday, October 18, 2017 1, Geert Uytterhoeven wrote: >> > + /* >> > +* Remove clock ticks for rise and fall times. Convert ns to >> clock >> > +* ticks. >> > +*/ >> > +

RE: [PATCH] i2c: riic: remove clock and frequency restrictions

Hi Geert, Thank you for your review. On Wednesday, October 18, 2017 1, Geert Uytterhoeven wrote: > > + /* > > +* Remove clock ticks for rise and fall times. Convert ns to > clock > > +* ticks. > > +*/ > > + brl -= t->scl_fall_ns / (10/rate); > > +

Re: [PATCH] i2c: riic: remove clock and frequency restrictions

Hi Chris, On Wed, Oct 18, 2017 at 4:04 PM, Chris Brandt wrote: > Remove the restriction that the parent clock has to be a specific frequency > and also allow any speed to be supported. > > Signed-off-by: Chris Brandt Thanks for your patch! >

[PATCH] i2c: riic: remove clock and frequency restrictions

Remove the restriction that the parent clock has to be a specific frequency and also allow any speed to be supported. Signed-off-by: Chris Brandt --- Tested on the RZ/A1H RSK board with the following DT: { pinctrl-names = "default"; pinctrl-0 = <_pins>;

RE: [PATCH 2/2] ARM: dts: iwg20d-q7-dbcm-ca: Add HDMI video output

Hi Laurent, > On Wednesday, 18 October 2017 12:33:47 EEST Biju Das wrote: > > From: Fabrizio Castro > > > > Although there is a HDMI connector on the q7 carrier board it is not > > connected to the RZ/G1M SoC. One must use the HDMI connector on the > > camera

Re: [PATCH 2/2] ARM: dts: iwg20d-q7-dbcm-ca: Add HDMI video output

Hi Laurent, On Wed, Oct 18, 2017 at 2:16 PM, Laurent Pinchart wrote: > On Wednesday, 18 October 2017 12:33:47 EEST Biju Das wrote: >> From: Fabrizio Castro >> >> Although there is a HDMI connector on the q7 carrier board it is

Re: [PATCH 1/2] ARM: dts: r8a7743: Add DU support

Hi Biju, Thank you for the patch. On Wednesday, 18 October 2017 12:33:46 EEST Biju Das wrote: > From: Fabrizio Castro > > Signed-off-by: Fabrizio Castro > Reviewed-by: Biju Das Reviewed-by: Laurent

Re: [PATCH 2/2] ARM: dts: iwg20d-q7-dbcm-ca: Add HDMI video output

Hi Biju, Thank you for the patch. On Wednesday, 18 October 2017 12:33:47 EEST Biju Das wrote: > From: Fabrizio Castro > > Although there is a HDMI connector on the q7 carrier board it is not > connected to the RZ/G1M SoC. One must use the HDMI connector on the >

[PATCH v5 8/9] drm/bridge/synopsys: dw-hdmi: Do not use device's drvdata

Let plat drivers own the drvdata, so that they could cleanup resources in their unbind(). Signed-off-by: Jeffy Chen --- Changes in v5: None drivers/gpu/drm/bridge/synopsys/dw-hdmi.c | 43 ++--- drivers/gpu/drm/imx/dw_hdmi-imx.c |

Re: [PATCH v6 0/4] phy: rcar-gen3-usb2: add support for r8a77995

On Thursday 12 October 2017 12:04 PM, Yoshihiro Shimoda wrote: > This patch set is based on the latest phy.git / next branch > (the commit id = 415060b21f318e009d865b4bcbf8f220ebc36964) > > After this patch set is applied, a usb 2.0 host node that is combined > with usb 2.0 peripheral needs

[PATCH v2] of_mdio: Fix broken PHY IRQ in case of probe deferral

If an Ethernet PHY is initialized before the interrupt controller it is connected to, a message like the following is printed: irq: no irq domain found for /interrupt-controller@e61c ! However, the actual error is ignored, leading to a non-functional (POLL) PHY interrupt later:

Re: [PATCH RESEND] phy: rcar-gen2: Add r8a7743/5 support

On Monday 09 October 2017 03:52 PM, Biju Das wrote: > Add USB PHY support for r8a7743/5 SoC. Renesas RZ/G1[ME] (R8A7743/5) > USB PHY is identical to the R-Car Gen2 family. > > Signed-off-by: Biju Das > Acked-by: Simon Horman > Acked-by: Rob

Re: [PATCH/RFC 4/5] regulator: bd9571mwv: Add support for backup mode

Hi Mark, On Wed, Oct 18, 2017 at 1:24 PM, Mark Brown wrote: > On Wed, Oct 18, 2017 at 01:19:08PM +0200, Geert Uytterhoeven wrote: >> On Wed, Oct 18, 2017 at 1:02 PM, Mark Brown wrote: >> > On Tue, Oct 10, 2017 at 05:26:17PM +0200, Geert Uytterhoeven

Re: [PATCH/RFC 4/5] regulator: bd9571mwv: Add support for backup mode

On Wed, Oct 18, 2017 at 01:19:08PM +0200, Geert Uytterhoeven wrote: > On Wed, Oct 18, 2017 at 1:02 PM, Mark Brown wrote: > > On Tue, Oct 10, 2017 at 05:26:17PM +0200, Geert Uytterhoeven wrote: > >> Backup mode is not enabled automatically, as e.g. on Renesas > >>

Re: [PATCH/RFC 4/5] regulator: bd9571mwv: Add support for backup mode

Hi Mark, On Wed, Oct 18, 2017 at 1:02 PM, Mark Brown wrote: > On Tue, Oct 10, 2017 at 05:26:17PM +0200, Geert Uytterhoeven wrote: >> Backup mode is not enabled automatically, as e.g. on Renesas >> Salvator-X(S) boards enabling backup mode changes the role of the ACC >> switch

Re: [PATCH/RFC 4/5] regulator: bd9571mwv: Add support for backup mode

On Tue, Oct 10, 2017 at 05:26:17PM +0200, Geert Uytterhoeven wrote: > Backup mode is not enabled automatically, as e.g. on Renesas > Salvator-X(S) boards enabling backup mode changes the role of the ACC > switch from a power switch to a wake-up switch. Hence enabling it > prevents the board from

[PATCH 2/2] ARM: dts: iwg20d-q7-dbcm-ca: Add HDMI video output

From: Fabrizio Castro Although there is a HDMI connector on the q7 carrier board it is not connected to the RZ/G1M SoC. One must use the HDMI connector on the camera daughter board. This patch adds support for this connector. Signed-off-by: Fabrizio Castro

[PATCH 0/2] Add HDMI support

Hello, This series aims to add HDMI support for iWave RZ/G1M (R8A7743) board. This series has been tested against renesas-dev tag 20171018-v4.14-rc5. This patch dependency on below patches [1] dt-bindings: display: rcar-du: Document R8A774[35]DU https://patchwork.kernel.org/patch/10005091

[PATCH 1/2] ARM: dts: r8a7743: Add DU support

From: Fabrizio Castro Signed-off-by: Fabrizio Castro Reviewed-by: Biju Das --- arch/arm/boot/dts/r8a7743.dtsi | 30 ++ 1 file changed, 30 insertions(+) diff --git

Re: [PATCH 7/7] ARM: dts: r8a7794: Use R-Car Gen2 Ether fallback compat string

On Wed, Oct 18, 2017 at 9:27 AM, Simon Horman wrote: > Use newly added R-Car Gen2 Ether fallback compat string > in the DT of the r8a7794 SoC. > > This should have no run-time effect as the driver matches against > the per-SoC compat string before considering the

Re: [PATCH 3/7] ARM: dts: r8a7778: Use R-Car Gen1 Ether fallback compat string

On Wed, Oct 18, 2017 at 9:27 AM, Simon Horman wrote: > Use newly added R-Car Gen1 Ether fallback compat string > in the DT of the r8a7778 SoC. > > This should have no run-time effect as the driver matches against > the per-SoC compat string before considering the

Re: [PATCH 5/7] ARM: dts: r8a7791: Use R-Car Gen2 Ether fallback compat string

On Wed, Oct 18, 2017 at 9:27 AM, Simon Horman wrote: > Use newly added R-Car Gen2 Ether fallback compat string > in the DT of the r8a7791 SoC. > > This should have no run-time effect as the driver matches against > the per-SoC compat string before considering the

Re: [PATCH 6/7] ARM: dts: r8a7793: Use R-Car Gen2 Ether fallback compat string

On Wed, Oct 18, 2017 at 9:27 AM, Simon Horman wrote: > Use newly added R-Car Gen2 Ether fallback compat string > in the DT of the r8a7793 SoC. > > This should have no run-time effect as the driver matches against > the per-SoC compat string before considering the

Re: [PATCH 2/7] ARM: dts: r8a7745: Use R-Car Gen2 Ether fallback compat string

On Wed, Oct 18, 2017 at 9:27 AM, Simon Horman wrote: > Use newly added R-Car Gen2 Ether fallback compat string > in the DT of the r8a7745 SoC. > > This should have no run-time effect as the driver matches against > the per-SoC compat string before considering the

Re: [PATCH 1/7] ARM: dts: r8a7743: Use R-Car Gen2 Ether fallback compat string

On Wed, Oct 18, 2017 at 9:27 AM, Simon Horman wrote: > Use newly added R-Car Gen2 Ether fallback compat string > in the DT of the r8a7743 SoC. > > This should have no run-time effect as the driver matches against > the per-SoC compat string before considering the

Re: [PATCH 4/7] ARM: dts: r8a7790: Use R-Car Gen2 Ether fallback compat string

On Wed, Oct 18, 2017 at 9:27 AM, Simon Horman wrote: > Use newly added R-Car Gen2 Ether fallback compat string > in the DT of the r8a7790 SoC. > > This should have no run-time effect as the driver matches against > the per-SoC compat string before considering the

[PATCH 4/7] ARM: dts: r8a7790: Use R-Car Gen2 Ether fallback compat string

Use newly added R-Car Gen2 Ether fallback compat string in the DT of the r8a7790 SoC. This should have no run-time effect as the driver matches against the per-SoC compat string before considering the fallback compat string. Signed-off-by: Simon Horman ---

[PATCH 2/7] ARM: dts: r8a7745: Use R-Car Gen2 Ether fallback compat string

Use newly added R-Car Gen2 Ether fallback compat string in the DT of the r8a7745 SoC. This should have no run-time effect as the driver matches against the per-SoC compat string before considering the fallback compat string. Signed-off-by: Simon Horman ---

[PATCH 0/7] ARM: dts: renesas: Use R-Car SDHI Gen[12] fallback compat strings

Use recently posted R-Car Gen 1 and 2 Ether fallback compat strings in the DT of Renesas ARM based SoCs. Based on renesas-devel-20171018-v4.14-rc5 Has a binding documentation but no run-time dependency on "[PATCH net-next 0/3] net: sh_eth: add R-Car Gen[12] fallback compatibility strings&qu

[PATCH 1/7] ARM: dts: r8a7743: Use R-Car Gen2 Ether fallback compat string

Use newly added R-Car Gen2 Ether fallback compat string in the DT of the r8a7743 SoC. This should have no run-time effect as the driver matches against the per-SoC compat string before considering the fallback compat string. Signed-off-by: Simon Horman ---

[PATCH 7/7] ARM: dts: r8a7794: Use R-Car Gen2 Ether fallback compat string

Use newly added R-Car Gen2 Ether fallback compat string in the DT of the r8a7794 SoC. This should have no run-time effect as the driver matches against the per-SoC compat string before considering the fallback compat string. Signed-off-by: Simon Horman ---

[PATCH 5/7] ARM: dts: r8a7791: Use R-Car Gen2 Ether fallback compat string

Use newly added R-Car Gen2 Ether fallback compat string in the DT of the r8a7791 SoC. This should have no run-time effect as the driver matches against the per-SoC compat string before considering the fallback compat string. Signed-off-by: Simon Horman ---

[PATCH 6/7] ARM: dts: r8a7793: Use R-Car Gen2 Ether fallback compat string

Use newly added R-Car Gen2 Ether fallback compat string in the DT of the r8a7793 SoC. This should have no run-time effect as the driver matches against the per-SoC compat string before considering the fallback compat string. Signed-off-by: Simon Horman ---

[PATCH 3/7] ARM: dts: r8a7778: Use R-Car Gen1 Ether fallback compat string

Use newly added R-Car Gen1 Ether fallback compat string in the DT of the r8a7778 SoC. This should have no run-time effect as the driver matches against the per-SoC compat string before considering the fallback compat string. Signed-off-by: Simon Horman ---

Re: [PATCH v4 3/3] mmc: renesas_sdhi: implement R-Car Gen[123] fallback compatibility strings

On Wed, Oct 18, 2017 at 09:00:23AM +0200, Simon Horman wrote: > Implement fallback compatibility strings for R-Car Gen 1, 2 and 3. > > In the case of Renesas R-Car hardware we know that there are generations of > SoCs, f.e. Gen 1 and 2. But beyond that its not clear what the relationship >

Re: [PATCH v4 2/3] dt-bindings: mmc: renesas_sdhi: add R-Car Gen[123] fallback compatibility strings

On Wed, Oct 18, 2017 at 09:00:22AM +0200, Simon Horman wrote: > Add fallback compatibility strings for R-Car Gen 1, 2 and 3. > > In the case of Renesas R-Car hardware we know that there are generations of > SoCs, f.e. Gen 1 and 2. But beyond that its not clear what the relationship > between IP

Re: [PATCH v4 1/3] dt-bindings: mmc: renesas_sdhi: provide example in bindings documentation

On Wed, Oct 18, 2017 at 09:00:21AM +0200, Simon Horman wrote: > Provide an example of the usage of the DT bindings for TMIO > in their documentation. The example given is for the r8a7790 (R-Car H2). > > Signed-off-by: Simon Horman > Reviewed-by: Geert Uytterhoeven

[PATCH net-next v2 2/3] net: sh_eth: rename name structures as rcar_gen[12]_*

Rename structures describing R-Car SoCs as rcar_gen[12]_* rather than r8a77[79]x_*. This seems a little easier on the eyes. And will make things slightly cleaner in a follow-up patch that adds fallback-compatibility strings for these SoCs. Note that R-Car Gen2 and RZ/G1 have many compatible IP

[PATCH net-next v2 3/3] net: sh_eth: implement R-Car Gen[12] fallback compatibility strings

Implement fallback compatibility strings for R-Car Gen 1 and 2. In the case of Renesas R-Car hardware we know that there are generations of SoCs, f.e. Gen 1 and 2. But beyond that its not clear what the relationship between IP blocks might be. For example, I believe that r8a7790 is older than

[PATCH net-next v2 1/3] dt-bindings: net: sh_eth: add R-Car Gen[12] fallback compatibility strings

Add fallback compatibility strings for R-Car Gen 1 and 2. In the case of Renesas R-Car hardware we know that there are generations of SoCs, f.e. Gen 1 and 2. But beyond that its not clear what the relationship between IP blocks might be. For example, I believe that r8a7790 is older than r8a7791

[PATCH net-next v2 0/3] net: sh_eth: add R-Car Gen[12] fallback compatibility strings

Add fallback compatibility strings for R-Car Gen 1 and 2. In the case of Renesas R-Car hardware we know that there are generations of SoCs, f.e. Gen 1 and 2. But beyond that its not clear what the relationship between IP blocks might be. For example, I believe that r8a7790 is older than r8a7791

[PATCH v4 1/3] dt-bindings: mmc: renesas_sdhi: provide example in bindings documentation

Provide an example of the usage of the DT bindings for TMIO in their documentation. The example given is for the r8a7790 (R-Car H2). Signed-off-by: Simon Horman Reviewed-by: Geert Uytterhoeven --- v3 * Updated example to newer upstream DTS

[PATCH v4 3/3] mmc: renesas_sdhi: implement R-Car Gen[123] fallback compatibility strings

Implement fallback compatibility strings for R-Car Gen 1, 2 and 3. In the case of Renesas R-Car hardware we know that there are generations of SoCs, f.e. Gen 1 and 2. But beyond that its not clear what the relationship between IP blocks might be. For example, I believe that r8a7790 is older than

Re: [PATCH net-next 0/3] net: sh_eth: add R-Car Gen[12] fallback compatibility strings

On Tue, Oct 17, 2017 at 09:47:44AM +0200, Simon Horman wrote: > Add fallback compatibility strings for R-Car Gen 1 and 2. > > In the case of Renesas R-Car hardware we know that there are generations of > SoCs, f.e. Gen 1 and 2. But beyond that its not clear what the relationship > between IP