From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] soc: renesas: Identify R-Car M3-W ES1.1
Date: Wed, 1 Nov 2017 09:42:38 +0100 [thread overview]
Message-ID: <20171101084237.atr25lujcqctwhjj@verge.net.au> (raw)
In-Reply-To: <1509384599-28953-3-git-send-email-geert+renesas@glider.be>
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.
next parent reply other threads:[~2017-11-01 8:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1509384599-28953-1-git-send-email-geert+renesas@glider.be>
[not found] ` <1509384599-28953-3-git-send-email-geert+renesas@glider.be>
2017-11-01 8:42 ` Simon Horman [this message]
2017-11-10 9:26 ` [PATCH 2/3] soc: renesas: Identify R-Car M3-W ES1.1 Simon Horman
[not found] ` <1509384599-28953-2-git-send-email-geert+renesas@glider.be>
2017-11-01 21:49 ` [PATCH 1/3] ARM: shmobile: Document Renesas M3-W-based Salvator-XS board DT bindings Rob Herring
2017-11-02 7:58 ` Simon Horman
[not found] ` <1509384599-28953-4-git-send-email-geert+renesas@glider.be>
2017-11-10 9:30 ` [PATCH 3/3] arm64: dts: renesas: Add support for Salvator-XS with R-Car M3-W Simon Horman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171101084237.atr25lujcqctwhjj@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox