[PATCH 2/3] soc: renesas: Identify R-Car M3-W ES1.1

[PATCH 2/3] soc: renesas: Identify R-Car M3-W ES1.1

[Simon Horman]

On Mon, Oct 30, 2017 at 06:29:58PM +0100, Geert Uytterhoeven wrote:
> The Product Register of R-Car M3-W ES1.1 incorrectly identifies the SoC
> revision as ES2.0.  Add a workaround to fix this.
> 
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> Is it already known how future revisions will be identified?

I'd like there to be some sort of conclusion to that discussion before
applying that patch (I seem to recall we discussed it some time ago
but I don't recall the outcome). The reason that I am being cautious here
is that it potentially has implications for old-kernel/new-SoC compatibility
which may be hard to fix later.

I am happy to apply the other patches in the series if you think that is
worthwhile.

[PATCH 2/3] soc: renesas: Identify R-Car M3-W ES1.1

[Simon Horman]

On Wed, Nov 01, 2017 at 09:42:38AM +0100, Simon Horman wrote:
> On Mon, Oct 30, 2017 at 06:29:58PM +0100, Geert Uytterhoeven wrote:
> > The Product Register of R-Car M3-W ES1.1 incorrectly identifies the SoC
> > revision as ES2.0.  Add a workaround to fix this.
> > 
> > Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> > ---
> > Is it already known how future revisions will be identified?
> 
> I'd like there to be some sort of conclusion to that discussion before
> applying that patch (I seem to recall we discussed it some time ago
> but I don't recall the outcome). The reason that I am being cautious here
> is that it potentially has implications for old-kernel/new-SoC compatibility
> which may be hard to fix later.
> 
> I am happy to apply the other patches in the series if you think that is
> worthwhile.

After some discussion off-list I am now satisfied that the approach you
have taken - to special case as identifying ES1.1 as what would otherwise
be identified ES2.0 - is not likely to cause problems with future SoC
releases.

I have applied this patch for v4.16.

[PATCH 1/3] ARM: shmobile: Document Renesas M3-W-based Salvator-XS board DT bindings

[Rob Herring]

On Mon, Oct 30, 2017 at 06:29:57PM +0100, Geert Uytterhoeven wrote:
> The Renesas Salvator-XS (Salvator-X 2nd version) development board can
> be equipped with either an R-Car H3 ES2.0 or M3-W ES1.x SiP, which are
> pin-compatible.
> 
> Document board part number and compatible values for the version with
> R-Car M3-W.
> 
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
>  Documentation/devicetree/bindings/arm/shmobile.txt | 2 ++
>  1 file changed, 2 insertions(+)

Acked-by: Rob Herring <robh@kernel.org>

[PATCH 1/3] ARM: shmobile: Document Renesas M3-W-based Salvator-XS board DT bindings

[Simon Horman]

On Wed, Nov 01, 2017 at 04:49:04PM -0500, Rob Herring wrote:
> On Mon, Oct 30, 2017 at 06:29:57PM +0100, Geert Uytterhoeven wrote:
> > The Renesas Salvator-XS (Salvator-X 2nd version) development board can
> > be equipped with either an R-Car H3 ES2.0 or M3-W ES1.x SiP, which are
> > pin-compatible.
> > 
> > Document board part number and compatible values for the version with
> > R-Car M3-W.
> > 
> > Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> > ---
> >  Documentation/devicetree/bindings/arm/shmobile.txt | 2 ++
> >  1 file changed, 2 insertions(+)
> 
> Acked-by: Rob Herring <robh@kernel.org>

Thanks, applied.

[PATCH 3/3] arm64: dts: renesas: Add support for Salvator-XS with R-Car M3-W

[Simon Horman]

On Mon, Oct 30, 2017 at 06:29:59PM +0100, Geert Uytterhoeven wrote:
> Add initial support for the Renesas Salvator-XS (Salvator-X 2nd version)
> development board equipped with an R-Car M3-W SiP.
> 
> Based on work for the Salvator-X and -XS boards with M3-W resp. H3 SiPs.
> 
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>

Thanks, applied for v4.16.