diff options
authorArnd Bergmann <arnd@arndb.de>2017-12-21 16:17:59 +0100
committerArnd Bergmann <arnd@arndb.de>2017-12-21 16:17:59 +0100
commit6b0b1a6b07e2de9671b540717bd393313efaf3a0 (patch)
parentc6ff8d79268ddfb022e0855f1db0d54915ec7cf7 (diff)
parent90f0d2b344313a8a4c366ef60d0df33008d2be84 (diff)
Merge tag 'renesas-soc-for-v4.16' of ssh://gitolite.kernel.org/pub/scm/linux/kernel/git/horms/renesas into next/soc
Pull "Renesas ARM Based SoC Updates for v4.16" from Simon Horman: * Identify R-Car M3-W ES1.1 Geert Uytterhoeven says "The Product Register of R-Car M3-W ES1.1 incorrectly identifies the SoC revision as ES2.0. Add a workaround to fix this." It is my understanding that this is likely to be forwards-compatibile. * tag 'renesas-soc-for-v4.16' of ssh://gitolite.kernel.org/pub/scm/linux/kernel/git/horms/renesas: soc: renesas: Identify R-Car M3-W ES1.1
1 files changed, 3 insertions, 0 deletions
diff --git a/drivers/soc/renesas/renesas-soc.c b/drivers/soc/renesas/renesas-soc.c
index 9f4ee2567c72..926b7fd6db2d 100644
--- a/drivers/soc/renesas/renesas-soc.c
+++ b/drivers/soc/renesas/renesas-soc.c
@@ -250,6 +250,9 @@ static int __init renesas_soc_init(void)
if (chipid) {
product = readl(chipid);
+ /* R-Car M3-W ES1.1 incorrectly identifies as ES2.0 */
+ if ((product & 0x7fff) == 0x5210)
+ product ^= 0x11;
if (soc->id && ((product >> 8) & 0xff) != soc->id) {
pr_warn("SoC mismatch (product = 0x%x)\n", product);
return -ENODEV;

Privacy Policy