linux-renesas-soc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ulrich Hecht <uli+renesas@fpond.eu>
To: linux-renesas-soc@vger.kernel.org
Cc: horms@verge.net.au, geert@linux-m68k.org,
	khiem.nguyen.xt@renesas.com, dien.pham.ry@renesas.com,
	takeshi.kihara.df@renesas.com,
	Ulrich Hecht <uli+renesas@fpond.eu>
Subject: [PATCH v2 5/5] arm64: dts: r8a7796-m3ulcb: Disable cpuidle support for CA53 cores
Date: Fri, 18 Jan 2019 11:47:54 +0100	[thread overview]
Message-ID: <1547808474-19427-6-git-send-email-uli+renesas@fpond.eu> (raw)
In-Reply-To: <1547808474-19427-1-git-send-email-uli+renesas@fpond.eu>

From: Takeshi Kihara <takeshi.kihara.df@renesas.com>

The revision of the R8A7796 SoC on the M3ULCB board is ES1.0. This revision
can not use cpuidle for CA53 cores.

Therefore, this patch disables cpuidle support for CA53 cores.

Signed-off-by: Takeshi Kihara <takeshi.kihara.df@renesas.com>
Signed-off-by: Ulrich Hecht <uli+renesas@fpond.eu>
---
 arch/arm64/boot/dts/renesas/r8a7796-m3ulcb.dts | 22 ++++++++++++++++++++++
 1 file changed, 22 insertions(+)

diff --git a/arch/arm64/boot/dts/renesas/r8a7796-m3ulcb.dts b/arch/arm64/boot/dts/renesas/r8a7796-m3ulcb.dts
index 9e4594c..cf96675 100644
--- a/arch/arm64/boot/dts/renesas/r8a7796-m3ulcb.dts
+++ b/arch/arm64/boot/dts/renesas/r8a7796-m3ulcb.dts
@@ -14,6 +14,12 @@
 	model = "Renesas M3ULCB board based on r8a7796";
 	compatible = "renesas,m3ulcb", "renesas,r8a7796";
 
+	cpus {
+		idle-states {
+			/delete-node/ cpu-sleep-1;
+		};
+	};
+
 	memory@48000000 {
 		device_type = "memory";
 		/* first 128MB is reserved for secure area. */
@@ -26,6 +32,22 @@
 	};
 };
 
+&a53_0 {
+	/delete-property/ cpu-idle-states;
+};
+
+&a53_1 {
+	/delete-property/ cpu-idle-states;
+};
+
+&a53_2 {
+	/delete-property/ cpu-idle-states;
+};
+
+&a53_3 {
+	/delete-property/ cpu-idle-states;
+};
+
 &du {
 	clocks = <&cpg CPG_MOD 724>,
 		 <&cpg CPG_MOD 723>,
-- 
2.7.4


  parent reply	other threads:[~2019-01-18 10:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-18 10:47 [PATCH v2 0/5] H3/M3-W cpuidle support Ulrich Hecht
2019-01-18 10:47 ` [PATCH v2 1/5] arm64: dts: r8a7795: Add cpuidle support for CA57 cores Ulrich Hecht
2019-08-28 11:47   ` Geert Uytterhoeven
2019-01-18 10:47 ` [PATCH v2 2/5] arm64: dts: r8a7795: Add cpuidle support for CA53 cores Ulrich Hecht
     [not found]   ` <20190726091325.GA13111@vmlxhi-102.adit-jv.com>
2019-07-26  9:47     ` Eugeniu Rosca
2019-07-29  7:44       ` Geert Uytterhoeven
2019-07-29 11:32         ` Lorenzo Pieralisi
2019-07-29 21:55           ` Eugeniu Rosca
2019-08-28 11:48   ` Geert Uytterhoeven
2019-01-18 10:47 ` [PATCH v2 3/5] arm64: dts: r8a7796: Add cpuidle support for CA57 cores Ulrich Hecht
2019-08-28 11:48   ` Geert Uytterhoeven
2019-01-18 10:47 ` [PATCH v2 4/5] arm64: dts: r8a7796: Add cpuidle support for CA53 cores Ulrich Hecht
2019-08-28 11:48   ` Geert Uytterhoeven
2019-01-18 10:47 ` Ulrich Hecht [this message]
2019-08-28 12:04 ` [PATCH v2 0/5] H3/M3-W cpuidle support Geert Uytterhoeven
2019-09-03 12:10   ` Geert Uytterhoeven

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=1547808474-19427-6-git-send-email-uli+renesas@fpond.eu \
    --to=uli+renesas@fpond.eu \
    --cc=dien.pham.ry@renesas.com \
    --cc=geert@linux-m68k.org \
    --cc=horms@verge.net.au \
    --cc=khiem.nguyen.xt@renesas.com \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=takeshi.kihara.df@renesas.com \
    /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;
as well as URLs for NNTP newsgroup(s).