Re: [PATCH v2] clk: renesas: mstp: Support 8-bit registers for r7s72100

Hi Stephen, On Tue, Dec 20, 2016 at 11:55 PM, Stephen Boyd wrote: > On 12/19, Geert Uytterhoeven wrote: >> On Thu, Dec 15, 2016 at 6:00 PM, Chris Brandt >> wrote: >> > The RZ/A1 is different than the other Renesas SOCs because the MSTP >> >

Re: [PATCH v2] clk: renesas: mstp: Support 8-bit registers for r7s72100

On 12/19, Geert Uytterhoeven wrote: > Hi Chris, Mike, Stephen, > > On Thu, Dec 15, 2016 at 6:00 PM, Chris Brandt > wrote: > > The RZ/A1 is different than the other Renesas SOCs because the MSTP > > registers are 8-bit instead of 32-bit and if you try writing values as

[PATCH v2 pci/next] PCI: rcar: Add compatible string for r8a7796

From: Harunobu Kurokawa This patch adds support for r8a7796. Signed-off-by: Harunobu Kurokawa Signed-off-by: Yoshihiro Kaneko Reviewed-by: Geert Uytterhoeven --- This patch is

Re: [PATCH v2 16/29] drm: bridge: dw-hdmi: Detect PHY type at runtime

Hi Laurent, On 20-12-2016 13:11, Laurent Pinchart wrote: > Hi Jose, > > On Tuesday 20 Dec 2016 11:39:21 Jose Abreu wrote: >> On 20-12-2016 01:33, Laurent Pinchart wrote: >>> Detect the PHY type and use it to handle the PHY type-specific SVSRET >>> signal. >>> >>> Signed-off-by: Laurent Pinchart

Re: [PATCH v2 17/29] drm: bridge: dw-hdmi: Refactor PHY power handling

Hi Russell, Thank you for the review. On Tuesday 20 Dec 2016 11:45:53 Russell King - ARM Linux wrote: > On Tue, Dec 20, 2016 at 03:33:48AM +0200, Laurent Pinchart wrote: > > Instead of spreading version-dependent PHY power handling code around, > > group it in two functions to power the PHY on

Re: [PATCH v2 04/13] drm: Add data mirror bus flag

On 2016-12-20 14:21, Laurent Pinchart wrote: > Hi Stefan, > > Thank you for the review. > > On Tuesday 20 Dec 2016 14:01:46 Stefan Agner wrote: >> On 2016-12-18 21:31, Laurent Pinchart wrote: >> > Hi Stefan and Thierry, >> > >> > As the author and suggester of the other bus flags, could you

Re: [PATCH v2 04/13] drm: Add data mirror bus flag

Hi Stefan, Thank you for the review. On Tuesday 20 Dec 2016 14:01:46 Stefan Agner wrote: > On 2016-12-18 21:31, Laurent Pinchart wrote: > > Hi Stefan and Thierry, > > > > As the author and suggester of the other bus flags, could you please > > review this patch ? > > It looks to me like an

Re: [PATCH v2 16/29] drm: bridge: dw-hdmi: Detect PHY type at runtime

Hi Jose, On Tuesday 20 Dec 2016 11:39:21 Jose Abreu wrote: > On 20-12-2016 01:33, Laurent Pinchart wrote: > > Detect the PHY type and use it to handle the PHY type-specific SVSRET > > signal. > > > > Signed-off-by: Laurent Pinchart > > > > --- > > > >

Re: [PATCH v2 04/13] drm: Add data mirror bus flag

Hi Laurent, On 2016-12-18 21:31, Laurent Pinchart wrote: > Hi Stefan and Thierry, > > As the author and suggester of the other bus flags, could you please review > this patch ? It looks to me like an appropriate use case for the flag. One remark below: > > On Saturday 19 Nov 2016 05:28:04

Re: [PATCH v2 17/29] drm: bridge: dw-hdmi: Refactor PHY power handling

Hi Russell, On 20-12-2016 11:45, Russell King - ARM Linux wrote: > On Tue, Dec 20, 2016 at 03:33:48AM +0200, Laurent Pinchart wrote: >> Instead of spreading version-dependent PHY power handling code around, >> group it in two functions to power the PHY on and off and use them >> through the

Re: [PATCH v2 17/29] drm: bridge: dw-hdmi: Refactor PHY power handling

On Tue, Dec 20, 2016 at 03:33:48AM +0200, Laurent Pinchart wrote: > Instead of spreading version-dependent PHY power handling code around, > group it in two functions to power the PHY on and off and use them > through the driver. > > Powering off the PHY at the beginning of the setup phase is

Applied "spi: sh-msiof: Do not use C++ style comment" to the spi tree

The patch spi: sh-msiof: Do not use C++ style comment has been applied to the spi tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus

Re: [PATCH v2 16/29] drm: bridge: dw-hdmi: Detect PHY type at runtime

Hi Laurent, On 20-12-2016 01:33, Laurent Pinchart wrote: > Detect the PHY type and use it to handle the PHY type-specific SVSRET > signal. > > Signed-off-by: Laurent Pinchart > --- > drivers/gpu/drm/bridge/dw-hdmi.c | 68 >

Re: [PATCH v2 15/29] drm: bridge: dw-hdmi: Handle overflow workaround based on device version

Hi Laurent, On 20-12-2016 01:33, Laurent Pinchart wrote: > Use the device version queried at runtime instead of the device type > provided through platform data to handle the overflow workaround. This > will make support of other SoCs integrating the same HDMI TX controller > version easier. > >

Re: [PATCH renesas/devel 1/4] arm64: dts: r8a7796: Use R-Car Gen 3 fallback binding for msiof nodes

On Tue, Dec 20, 2016 at 11:44:14AM +0100, Geert Uytterhoeven wrote: > On Tue, Dec 20, 2016 at 11:42 AM, Geert Uytterhoeven > wrote: > > On Tue, Dec 20, 2016 at 11:32 AM, Simon Horman > > wrote: > >> Use recently added R-Car Gen 3 fallback binding

Re: [PATCH renesas/devel 0/4] ARM, arm64: dts: Use R-Car fallback bindings for msiof nodes

On Tue, Dec 20, 2016 at 11:32:35AM +0100, Simon Horman wrote: > Hi, > > this short series makes use of newly added R-Car fallback bindings in msiof > nodes of the DTs for SoCs where the drivers in question are already used. > > This should have no run-time effect at this time as the current

Re: [PATCH v2 14/29] drm: bridge: dw-hdmi: Detect AHB audio DMA using correct register

Hi Laurent, On 20-12-2016 01:33, Laurent Pinchart wrote: > Bit 0 in CONFIG1_ID tells whether the IP core uses an AHB slave > interface for control. The correct way to identify AHB audio DMA support > is through bit 1 in CONFIG3_ID. > > Signed-off-by: Laurent Pinchart

Re: [PATCH v2 13/29] drm: bridge: dw-hdmi: Reject invalid product IDs

Hi Laurent, On 20-12-2016 01:33, Laurent Pinchart wrote: > The DWC HDMI TX can be recognized by the two product identification > registers. If the registers don't read as expect the IP will be very > different than what the driver has been designed for, or will be > misconfigured in a way that

Re: [PATCH resend] arm64: dts: r8a7796: salvator-x: Update memory node to 4 GiB map

On Thu, Dec 15, 2016 at 04:31:29PM +0100, Geert Uytterhoeven wrote: > From: Takeshi Kihara > > This patch updates memory region: > > - After changes, the new map of the Salvator-X board on R8A7796 SoC > Bank0: 2GiB RAM : 0x4800 -> 0x000bfff >

Re: [PATCH v2 renesas/devel 00/13] ARM, arm64: dts: Use R-Car fallback bindings for i2c/iic nodes

On Tue, Dec 13, 2016 at 12:45:46PM +0100, Simon Horman wrote: > Hi, > > this short series makes use of newly added R-Car fallback bindings in i2c > and iic nodes of the DTs for SoCs where the drivers in question are already > used. > > This should have no run-time effect at this time as the

Re: [PATCH renesas/devel 4/4] ARM: dts: r8a7790: Use R-Car Gen 2 fallback binding for msiof nodes

On Tue, Dec 20, 2016 at 11:32 AM, Simon Horman wrote: > Use recently added R-Car Gen 2 fallback binding for msiof nodes in > DT for r8a7790 SoC. > > This has no run-time effect for the current driver as the initialisation > sequence is the same for the SoC-specific

Re: [PATCH renesas/devel 1/4] arm64: dts: r8a7796: Use R-Car Gen 3 fallback binding for msiof nodes

On Tue, Dec 20, 2016 at 11:42 AM, Geert Uytterhoeven wrote: > On Tue, Dec 20, 2016 at 11:32 AM, Simon Horman > wrote: >> Use recently added R-Car Gen 3 fallback binding for msiof nodes in >> DT for r8a7796 SoC. >> >> This has no run-time effect

Re: [PATCH renesas/devel 3/4] ARM: dts: r8a7792: Use R-Car Gen 2 fallback binding for msiof nodes

On Tue, Dec 20, 2016 at 11:32 AM, Simon Horman wrote: > Use recently added R-Car Gen 2 fallback binding for msiof nodes in > DT for r8a7792 SoC. > > This has no run-time effect for the current driver as the initialisation > sequence is the same for the SoC-specific

Re: [PATCH renesas/devel 2/4] ARM: dts: r8a7791: Use R-Car Gen 2 fallback binding for msiof nodes

On Tue, Dec 20, 2016 at 11:32 AM, Simon Horman wrote: > Use recently added R-Car Gen 2 fallback binding for msiof nodes in > DT for r8a7791 SoC. > > This has no run-time effect for the current driver as the initialisation > sequence is the same for the SoC-specific

Re: [PATCH renesas/devel 1/4] arm64: dts: r8a7796: Use R-Car Gen 3 fallback binding for msiof nodes

On Tue, Dec 20, 2016 at 11:32 AM, Simon Horman wrote: > Use recently added R-Car Gen 3 fallback binding for msiof nodes in > DT for r8a7796 SoC. > > This has no run-time effect for the current driver as the initialisation > sequence is the same for the SoC-specific

[PATCH renesas/devel 3/4] ARM: dts: r8a7792: Use R-Car Gen 2 fallback binding for msiof nodes

Use recently added R-Car Gen 2 fallback binding for msiof nodes in DT for r8a7792 SoC. This has no run-time effect for the current driver as the initialisation sequence is the same for the SoC-specific binding for r8a7792 and the fallback binding for R-Car Gen 2. Signed-off-by: Simon Horman

[PATCH renesas/devel 4/4] ARM: dts: r8a7790: Use R-Car Gen 2 fallback binding for msiof nodes

Use recently added R-Car Gen 2 fallback binding for msiof nodes in DT for r8a7790 SoC. This has no run-time effect for the current driver as the initialisation sequence is the same for the SoC-specific binding for r8a7790 and the fallback binding for R-Car Gen 2. Signed-off-by: Simon Horman

[PATCH renesas/devel 2/4] ARM: dts: r8a7791: Use R-Car Gen 2 fallback binding for msiof nodes

Use recently added R-Car Gen 2 fallback binding for msiof nodes in DT for r8a7791 SoC. This has no run-time effect for the current driver as the initialisation sequence is the same for the SoC-specific binding for r8a7791 and the fallback binding for R-Car Gen 2. Signed-off-by: Simon Horman

[PATCH renesas/devel 0/4] ARM, arm64: dts: Use R-Car fallback bindings for msiof nodes

Hi, this short series makes use of newly added R-Car fallback bindings in msiof nodes of the DTs for SoCs where the drivers in question are already used. This should have no run-time effect at this time as the current driver implementations use the same initialisation sequences for SoC-specific

[PATCH renesas/devel 1/4] arm64: dts: r8a7796: Use R-Car Gen 3 fallback binding for msiof nodes

Use recently added R-Car Gen 3 fallback binding for msiof nodes in DT for r8a7796 SoC. This has no run-time effect for the current driver as the initialisation sequence is the same for the SoC-specific binding for r8a7796 and the fallback binding for R-Car Gen 3. Signed-off-by: Simon Horman

Re: [PATCH spi/for-next] spi: sh-msiof: Add R-Car Gen 2 and 3 fallback bindings

On Wed, Dec 14, 2016 at 05:38:11PM +, Mark Brown wrote: > On Mon, Dec 12, 2016 at 10:49:35AM +0100, Simon Horman wrote: > > > + { .compatible = "renesas,sh-msiof",.data = _data }, // > > Deprecated > > C++ style comment here, please send a followup fixing this. Thanks, done.

[PATCH spi/for-next] sip: sh-msiof: Do not use C++ style comment

4286db8456f4 ("spi: sh-msiof: Add R-Car Gen 2 and 3 fallback bindings") added a C++ style comment. This is not in keeping with the style used for comments elsewhere in this fine. Update it accordingly. Signed-off-by: Simon Horman --- drivers/spi/spi-sh-msiof.c | 2 +-