linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: juri.lelli@arm.com (Juri Lelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6 4/8] arm64: parse cpu capacity-dmips-mhz from DT
Date: Tue, 9 Aug 2016 10:42:38 +0100	[thread overview]
Message-ID: <20160809094238.GA23236@e106622-lin> (raw)
In-Reply-To: <1468932048-31635-5-git-send-email-juri.lelli@arm.com>

Hi,

this patch needs the fix below, since platforms can boot without a
cpu-map.

On 19/07/16 13:40, Juri Lelli wrote:
[...]
> @@ -185,6 +328,8 @@ static int __init parse_dt_topology(void)
>  	if (ret != 0)
>  		goto out_map;
>  
> +	normalize_cpu_capacity();
> +
>  	/*
>  	 * Check that all cores are in the topology; the SMP code will
>  	 * only mark cores described in the DT as possible.
> -- 

--->8---
 arch/arm64/kernel/topology.c | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/arch/arm64/kernel/topology.c b/arch/arm64/kernel/topology.c
index 56bbd6d41daf..288f511a5f29 100644
--- a/arch/arm64/kernel/topology.c
+++ b/arch/arm64/kernel/topology.c
@@ -394,8 +394,10 @@ static int __init parse_dt_topology(void)
 	 * cluster with restricted subnodes.
 	 */
 	map = of_get_child_by_name(cn, "cpu-map");
-	if (!map)
+	if (!map) {
+		cap_parsing_failed = true;
 		goto out;
+	}
 
 	ret = parse_cluster(map, 0);
 	if (ret != 0)
-- 
2.7.0

  reply	other threads:[~2016-08-09  9:42 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-19 12:40 [PATCH v6 0/8] CPUs capacity information for heterogeneous systems Juri Lelli
2016-07-19 12:40 ` [PATCH v6 1/8] Documentation: arm: define DT cpu capacity-dmips-mhz bindings Juri Lelli
2016-07-20 18:56   ` Rob Herring
2016-07-21 11:43     ` Juri Lelli
2016-08-16  9:02   ` Vincent Guittot
2016-08-30 16:11     ` Juri Lelli
2016-07-19 12:40 ` [PATCH v6 2/8] arm: parse cpu capacity-dmips-mhz from DT Juri Lelli
2016-08-16  8:20   ` Vincent Guittot
2016-08-30 16:28     ` Juri Lelli
2016-08-31  8:14       ` Vincent Guittot
2016-08-31 17:08         ` Juri Lelli
2016-09-01  8:22           ` Vincent Guittot
2016-09-01  8:50             ` Juri Lelli
2016-07-19 12:40 ` [PATCH v6 3/8] arm, dts: add TC2 cpu capacity-dmips-mhz information Juri Lelli
2016-08-10 15:33   ` Sudeep Holla
2016-08-10 15:43     ` Juri Lelli
2016-08-10 15:52       ` Sudeep Holla
2016-08-10 16:06         ` Juri Lelli
2016-07-19 12:40 ` [PATCH v6 4/8] arm64: parse cpu capacity-dmips-mhz from DT Juri Lelli
2016-08-09  9:42   ` Juri Lelli [this message]
2016-07-19 12:40 ` [PATCH v6 5/8] arm64, dts: add Juno cpu capacity-dmips-mhz information Juri Lelli
2016-08-10 15:38   ` Sudeep Holla
2016-07-19 12:40 ` [PATCH v6 6/8] arm64, dts: add Juno r2 " Juri Lelli
2016-08-10 15:41   ` Sudeep Holla
2016-07-19 12:40 ` [PATCH v6 7/8] arm: add sysfs cpu_capacity attribute Juri Lelli
2016-07-19 12:40 ` [PATCH v6 8/8] arm64: " Juri Lelli
2016-08-08 16:49 ` [PATCH v6 0/8] CPUs capacity information for heterogeneous systems Peter Zijlstra
2016-08-09 10:08   ` Juri Lelli
2016-08-10 10:53 ` Juri Lelli

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=20160809094238.GA23236@e106622-lin \
    --to=juri.lelli@arm.com \
    --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;
as well as URLs for NNTP newsgroup(s).