Re: [RFC] ARM: shmobile: allow non-SMP builds again

> Wasn't this fixed by > > Commit: 869ec056fa8450184423c8076e0a342db127795c Ooops, yes. Sorry, overlooked this new 'if' after rebasing from rc1 to rd/master :( signature.asc Description: PGP signature

[RFC] ARM: shmobile: allow non-SMP builds again

platform_can_secondary_boot() is only available for SMP, so guard the smp_init function with some ifdeffery to allow building without SMP. Signed-off-by: Wolfram Sang --- This is the easiest solution, but I wonder if it is the proper one? It might make sense to

[PATCH 1/2] ARM: shmobile: r8a7790: only use smp_init when SMP is selected

We use the helper function which populates the smp_init pointer only in case of SMP. Signed-off-by: Wolfram Sang --- arch/arm/mach-shmobile/setup-r8a7790.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 2/2] ARM: shmobile: r8a7791: only use smp_init when SMP is selected

We use the helper function which populates the smp_init pointer only in case of SMP. Signed-off-by: Wolfram Sang --- arch/arm/mach-shmobile/setup-r8a7791.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH] i2c: mux: demux-pinctrl: properly roll back when adding adapter fails

We also need to revert the dynamic OF change, so we get a consistent state again. Otherwise, we might have two devices enabled e.g. after pinctrl setup fails. Signed-off-by: Wolfram Sang --- drivers/i2c/muxes/i2c-demux-pinctrl.c | 4 +++- 1 file changed, 3

[PATCH/PROTO 7/9 option 2] spi: sh-msiof: Configure MSIOF parent clock

Change the clock rate in spi_master.setup() to accomodate the desired maximum clock rate for the device being set up: - Change the clock rate if the msiofX (and thus mso) clock rate is too high. Failure to do so is considered an error. - Try to change the clock rate if the msiofX (and

[PATCH/PROTO 4/9 common] arm64: dts: salvator-x: Add dummy MSIOF SPI slave devices

Declares three SPI slave devices on three different MSIOF instances: - high-speed (30 MHz), - medium-speed (1 MHz), - low-speed (20 kHz). The maximum frequencies are chosen such that the optimal parent clock frequency for the high-speed device is outside of the allowed range for the

[PATCH/PROTO 9/9 option 3] spi: sh-msiof: Configure MSIOF parent clock

Change the clock rate in spi_master.setup() to accomodate the desired maximum clock rate for the device being set up. Use clk-fixed on a fake clock behaving like the internal MSIOF divider. Setting the rate of the fake clock will make clk-fixed find an optimal rate for the mso clock, with an

[PATCH/PROTO 0/9] R-Car H3 MSIOF Parent Clock Control Prototype

Hi all, On R-Car H3, the various MSIOF instances (used for SPI) have a common parent clock. This mso clock is a programmable "DIV6" clock (divider 1 - 64). Its rate lies in the range 12.5 to 800 MHz, or 6.25 to 400 MHz (depending on the main crystal). After boot up, the default

[PATCH/PROTO 8/9 option 3] clk: divider: Add hack to support dummy clocks

Allow registering dummy divider clocks that do not operate on an actual hardware register (reg = NULL), for testing clock algorithms. Not-Signed-off-by: Geert Uytterhoeven --- Not intended for upstream merge. --- drivers/clk/clk-divider.c| 33

[PATCH/PROTO 2/9 common] spi: sh-msiof: Print max and transfer frequency

Not-Signed-off-by: Geert Uytterhoeven --- Not intended for upstream merge. --- drivers/spi/spi-sh-msiof.c | 17 + 1 file changed, 17 insertions(+) diff --git a/drivers/spi/spi-sh-msiof.c b/drivers/spi/spi-sh-msiof.c index

[PATCH/PROTO 6/9 option 2/3] spi: sh-msiof: Add clock notifier to enforce valid parent clock

Use clock notifiers to avoid changing the clock rate to an out-of-range setting for already configured devices. This will allow dynamic configuration of the MSIOF parent clock. Not-Signed-off-by: Geert Uytterhoeven --- Not intended for upstream merge. ---

[PATCH/PROTO 5/9 option 1] arm64: dts: salvator-x: Configure MSIOF parent clock

Add assigned-clocks and assigned-clock-rates DT properties to the cpg device node, to configure the MSIOF parent clock for 20 MHz. Not-Signed-off-by: Geert Uytterhoeven --- Not intended for upstream merge. Note that these properties could also be added to an individual

[PATCH/PROTO 1/9 common] spi: sh-msiof: Add support for R-Car H3

Add support for MSIOF in r8a7795 (R-Car H3). Not-Signed-off-by: Geert Uytterhoeven --- Not intended for upstream merge. R-Car H3 ES1.0 has a hardware bug preventing MSIOF from being used with real SPI devices. However, this does not affect the generation of clock

[PATCH/PROTO 3/9 common] arm64: dts: r8a7795: Add all MSIOF nodes

Add the device nodes for all MSIOF SPI controllers, incl. clocks, clock domain, and dma properties. Not-Signed-off-by: Geert Uytterhoeven --- Not intended for upstream merge. R-Car H3 ES1.0 has a hardware bug preventing MSIOF from being used with real SPI devices.

RE: Question about dma-ranges property for PCI host controllers

Hi Arnd, On 11 August 2016 16:09 Arnd Bergmann wrote: > On Thursday, August 11, 2016 3:00:42 PM CEST Phil Edworthy wrote: > > Hi, > > > > A few PCI host controllers use the "dma-ranges" property to specify the > > mapping from PCI bus addresses to physical addresses. > > > > In the case of R-Car

[PATCH] pinctrl: sh-pfc: r8a7795: Add DU support

Only the DU parallel RGB output signals are included, HDMI and TCON pins will be added in separate groups. Signed-off-by: Laurent Pinchart --- drivers/pinctrl/sh-pfc/pfc-r8a7795.c | 100 +++ 1 file changed, 100

Re: [PATCH v2 4/4] arm64: dts: renesas: salvator-x: Enable DU

Hi Geert, On Thursday 11 Aug 2016 18:37:03 Laurent Pinchart wrote: > On Thursday 11 Aug 2016 11:17:17 Geert Uytterhoeven wrote: > > On Tue, Aug 9, 2016 at 2:29 PM, Laurent Pinchart wrote: > > > Only the VGA output is supported for now. > > > > > > Signed-off-by: Laurent Pinchart > > >

[PATCH] arm64: dts: renesas: salvator-x: Configure pins for the DU RGB output

Signed-off-by: Laurent Pinchart --- arch/arm64/boot/dts/renesas/r8a7795-salvator-x.dts | 7 +++ 1 file changed, 7 insertions(+) This patch depends on "[PATCH] pinctrl: sh-pfc: r8a7795: Add DU support" posted a few minutes ago to the