Re: [PATCH 02/14] dt-bindings: arm: don't embed SoC name into the ULCB boards' compatible

2018-08-08 Thread Eugeniu Rosca
Hello Geert, Laurent, Morimoto-san, On Tue, Aug 07, 2018 at 10:30:14AM +0200, Geert Uytterhoeven wrote: > Hi Laurent, > > On Tue, Aug 7, 2018 at 10:21 AM Laurent Pinchart > wrote: > > On Tuesday, 7 August 2018 11:18:11 EEST Kuninori Morimoto wrote: > > > > Yeah, it is true "so far". I think ther

RE: [PATCH/RFC 0/4] sh-sci : Do not derive regshift from regsize

2018-08-08 Thread Chris Brandt
Hi Geert, Just FYI... On Wednesday, August 08, 2018, Geert Uytterhoeven wrote: > 4. Drop "renesas,scif" from the compatible value in the (not yet > submitted) r7s9210.dtsi (this may have to be clarified in the DT > bindings, although they already say "renesas,scif" is only meant for >

Re: [PATCH V2 4/5] PCI: rcar: Support runtime PM, link state L1 handling

2018-08-08 Thread Marek Vasut
On 07/25/2018 11:08 PM, Marek Vasut wrote: > On 06/13/2018 07:25 PM, Bjorn Helgaas wrote: >> On Wed, Jun 13, 2018 at 04:52:52PM +0100, Lorenzo Pieralisi wrote: >>> On Wed, Jun 13, 2018 at 08:53:08AM -0500, Bjorn Helgaas wrote: On Wed, Jun 13, 2018 at 01:54:51AM +0200, Marek Vasut wrote: >

RE: Fix RCAR-V3H SoC wrong IPSR9/10 registers

2018-08-08 Thread Adnan Ali
Hi Thanks for your review. I'm using link from elinux may be I need to send It to someone who's maintaining this branch. I have issues sending patch from cooperate domain via send-email. This file is called drivers/pinctrl/sh-pfc/pfc-r8a77980.c in upstream Linux. >>> Thanks > }, >

Re: Fix RCAR-V3H SoC wrong IPSR9/10 registers

2018-08-08 Thread Geert Uytterhoeven
Hi Adnan, On Wed, Aug 8, 2018 at 1:39 PM Adnan Ali wrote: > Please review this patch. Thanks for your patch! But please don't send patches as attachments. It makes review more difficult. > From 468b28ae35eb0b64db13e3d7d013abaf3734ae32 Mon Sep 17 00:00:00 2001 > From: Adnan Ali > Date: Wed, 8

RE: [PATCH/RFC 0/4] sh-sci : Do not derive regshift from regsize

2018-08-08 Thread Chris Brandt
Hi Geert, On Wednesday, August 08, 2018, Geert Uytterhoeven wrote: > Suggestions for actions: > 1. Revert commit 7acece71a517cad8 ("serial: sh-sci: Remove > SCIx_RZ_SCIFA_REGTYPE"), as this is a dependency for step 2, > 2. Revert commit 2d4dd0da45401c7a ("serial: sh-sci: Allow for compres

Re: [PATCH/RFC 4/4] sh-sci: Derive regshift value from DT compatible value

2018-08-08 Thread Geert Uytterhoeven
Hi Chris, On Wed, Aug 8, 2018 at 12:39 PM Chris Brandt wrote: > On Wednesday, August 08, 2018, Geert Uytterhoeven wrote: > > BTW, I guess earlycon also works on RZ/A2 with current tty-next or > > latest renesas-drivers? > > I was using your RFC patches on top of the current renesas-drivers. I me

Re: [PATCH/RFC 0/4] sh-sci : Do not derive regshift from regsize

2018-08-08 Thread Geert Uytterhoeven
On Mon, Aug 6, 2018 at 4:08 PM Geert Uytterhoeven wrote: > This RFC patch series was sparked by noticing that commit 2d4dd0da45401c7a > ("serial: sh-sci: Allow for compressed SCIF address") broke earlycon > support on most Renesas ARM SoCs using SCIF ports, and by the fragility of > deriving regsh

RE: [PATCH/RFC 4/4] sh-sci: Derive regshift value from DT compatible value

2018-08-08 Thread Chris Brandt
Hi Geert, On Wednesday, August 08, 2018, Geert Uytterhoeven wrote: > BTW, I guess earlycon also works on RZ/A2 with current tty-next or > latest renesas-drivers? I was using your RFC patches on top of the current renesas-drivers. Chris

Re: [PATCH/RFC 4/4] sh-sci: Derive regshift value from DT compatible value

2018-08-08 Thread Geert Uytterhoeven
Hi Chris, On Wed, Aug 8, 2018 at 2:16 AM Chris Brandt wrote: > On Tuesday, August 07, 2018, Geert Uytterhoeven wrote: > > > I see that you added this: > > > > > > OF_EARLYCON_DECLARE(scif, "renesas,scif-r7s9210", > > rza2_early_console_setup); > > > > > > and "renesas,scif-r7s9210" matches what

[PATCH 1/2] i2c: rcar: refactor private flags

2018-08-08 Thread Wolfram Sang
Use BIT macro to avoid shift-31-problem, indent a little more and use GENMASK to make it easier to add new flags. Signed-off-by: Wolfram Sang --- drivers/i2c/busses/i2c-rcar.c | 7 --- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/drivers/i2c/busses/i2c-rcar.c b/drivers/i2c/b

[PATCH 2/2] i2c: rcar: implement STOP and REP_START according to docs

2018-08-08 Thread Wolfram Sang
When doing a REP_START after a read message, the driver used to trigger a STOP first which would then be overwritten by REP_START. This was the only stable method found when doing the last refactoring. However, this was not in accordance with the documentation. After research from our BSP team and

[PATCH 0/2] i2c: rcar: implement STOP and REP_START according to docs

2018-08-08 Thread Wolfram Sang
Details are in the patch descriptions. Thanks to Yamasaki-san, Shimoda-san, and all other people involved. Wolfram Sang (2): i2c: rcar: refactor private flags i2c: rcar: implement STOP and REP_START according to docs drivers/i2c/busses/i2c-rcar.c | 39 +++