From: Ben Dooks <ben.dooks-4yDnlxn2s6sWdaTGBSpHTA@public.gmane.org>
To: linux-kernel-81qHHgoATdFT9dQujB1mzip2UmYkHbXO@public.gmane.org,
"open list:OPEN FIRMWARE AND..."
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Lorenzon Pieralisi
<lorenzo.pieralisi-5wv7dgnIgG8@public.gmane.org>,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [Linux-kernel] [PATCH] ARM: kernel: respect device tree status of cpu nodes
Date: Thu, 06 Mar 2014 10:00:10 +0000 [thread overview]
Message-ID: <5318472A.5060700@codethink.co.uk> (raw)
In-Reply-To: <53178A03.3090004-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
On 05/03/14 20:33, Stephen Boyd wrote:
> +Lorenzo
>
> On 02/24/14 03:22, Jürg Billeter wrote:
>> Skip 'disabled' cpu nodes when building the cpu logical map. This avoids
>> booting cpus that have been disabled in the device tree.
>>
>> Signed-off-by: Jürg Billeter <j@bitron.ch>
>> Reviewed-by: Ben Dooks <ben.dooks-4yDnlxn2s6sWdaTGBSpHTA@public.gmane.org>
>> ---
>> arch/arm/kernel/devtree.c | 4 ++++
>> 1 file changed, 4 insertions(+)
>>
>> diff --git a/arch/arm/kernel/devtree.c b/arch/arm/kernel/devtree.c
>> index 739c3df..9aed299 100644
>> --- a/arch/arm/kernel/devtree.c
>> +++ b/arch/arm/kernel/devtree.c
>> @@ -95,6 +95,10 @@ void __init arm_dt_init_cpu_maps(void)
>> if (of_node_cmp(cpu->type, "cpu"))
>> continue;
>>
>> + /* Check if CPU is enabled */
>> + if (!of_device_is_available(cpu))
>> + continue;
>> +
>> pr_debug(" * %s...\n", cpu->full_name);
>> /*
>> * A device tree containing CPU nodes with missing "reg"
>
> This doesn't follow the ePAPR spec. According to ePAPR status="disabled"
> in a cpu node means "the cpu is in a quiescent state" and one can enable
> it by using the "enable-method". At the least, we should document this
> in bindings/arm/cpus.txt if we can all agree that we want this
> definition of disabled.
My view was that disabled should be the same as for the device case
as it makes sense that way.
We have a position where we want to use the .dtsi files but not all
cpus are available to the Linux. If we cannot use disabled then we
need some other method to say this cpu node is not available, so
please do not try and bring it online (saves boot time waiting for
CPU nodes that cannot online)
--
Ben Dooks http://www.codethink.co.uk/
Senior Engineer Codethink - Providing Genius
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-03-06 10:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-24 11:22 [PATCH] ARM: kernel: respect device tree status of cpu nodes Jürg Billeter
2014-03-05 20:33 ` Stephen Boyd
[not found] ` <53178A03.3090004-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2014-03-06 10:00 ` Ben Dooks [this message]
[not found] ` <5318472A.5060700-4yDnlxn2s6sWdaTGBSpHTA@public.gmane.org>
2014-03-06 16:51 ` [Linux-kernel] " Lorenzo Pieralisi
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=5318472A.5060700@codethink.co.uk \
--to=ben.dooks-4ydnlxn2s6swdatgbsphta@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-81qHHgoATdFT9dQujB1mzip2UmYkHbXO@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lorenzo.pieralisi-5wv7dgnIgG8@public.gmane.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).