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

Simon Horman horms at verge.net.au
Fri Nov 10 01:26:50 PST 2017


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 at 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.



More information about the linux-arm-kernel mailing list