All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andre Przywara <andre.przywara@linaro.org>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: julien.grall@linaro.org, xen-devel@lists.xen.org,
	patches@linaro.org, stefano.stabellini@eu.citrix.com
Subject: Re: [PATCH 1/4] arm: parse PSCI node from the host device-tree
Date: Thu, 28 Nov 2013 11:56:32 +0100	[thread overview]
Message-ID: <52972160.4080307@linaro.org> (raw)
In-Reply-To: <1385464352.23112.32.camel@kazak.uk.xensource.com>

On 11/26/2013 12:12 PM, Ian Campbell wrote:
> On Mon, 2013-11-25 at 13:02 +0100, Andre Przywara wrote:
>> +
>> +    if ( !dt_property_read_u32(psci, "cpu_on", &psci_host_cpu_on_nr) )
>> +    {
>> +        printk("/psci node is missing the \"cpu_on\" property\n");
>> +        return 4;
>> +    }
>
> http://www.spinics.net/lists/devicetree/msg05348.html updates the
> bindings for PSCI 0.2. I suppose Midway must only support 0.1?
>
> I'd be OK with only supporting 0.1 right now, but it would be useful to
> comment either in the code or in the commit message.
>
> (nb: I'm not sure of v4 was the final version of that series)

If I look at http://www.spinics.net/lists/devicetree/msg12293.html
I would keep it as it is - at least until the binding changes. Hopefully 
there will be a compatibility fallback if cpu_on should change to 
cpu_on-{32,64}. I will talk to Rob about this and will later send a fix 
if that is needed.
Midway provides an implementation conforming to PSCI 0.2, however the 
device tree binding is still the one from the current kernel git HEAD.

>
>> +
>> +    return 0;
>> +}
>> +
>>   /* Parse the device tree and build the logical map array containing
>>    * MPIDR values related to logical cpus
>>    * Code base on Linux arch/arm/kernel/devtree.c
>> @@ -107,6 +145,11 @@ void __init smp_init_cpus(void)
>>       bool_t bootcpu_valid = 0;
>>       int rc;
>>
>> +    if ( psci_host_init() == 0 )
>> +    {
>> +        printk(XENLOG_INFO "Using PSCI for SMP bringup\n");
>> +    }
>> +
>>       if ( (rc = arch_smp_init()) < 0 )
>
> arch_smp_init is empty on both platforms. arm32 has a comment "TODO:
> PSCI" ;-)
>
> I think we can nuke this function while we are here, since it's only
> purpose was as a PSCI placehoder.
>

But arch_smp_init() calls platform_smp_init(), which is not empty for 
the Exynos, VExpress and OMAP5 (it contains the native SMP bringup for 
these platforms).
So shall I skip the superfluous arch_smp_init() and call 
platform_smp_init() directly from smpboot.c?
Or keep it as it is and we clean it up later?

Thanks,
Andre.

  parent reply	other threads:[~2013-11-28 10:56 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-25 12:02 [PATCH 0/4] ARM: add PSCI host support Andre Przywara
2013-11-25 12:02 ` [PATCH 1/4] arm: parse PSCI node from the host device-tree Andre Przywara
2013-11-26 11:12   ` Ian Campbell
2013-11-26 11:25     ` Ian Campbell
2013-11-28 10:56     ` Andre Przywara [this message]
2013-11-25 12:02 ` [PATCH 2/4] arm: add a function to invoke the PSCI handler and use it Andre Przywara
2013-11-26 11:18   ` Ian Campbell
2013-11-28 10:59     ` Andre Przywara
2013-11-25 12:02 ` [PATCH 3/4] arm: dont give up on EAGAIN if PSCI is defined Andre Przywara
2013-11-26 11:20   ` Ian Campbell
2013-11-25 12:02 ` [PATCH 4/4] arm64: defer CPU initialization on ARM64 if PSCI is present Andre Przywara
2013-11-26 11:24   ` Ian Campbell
2013-11-25 13:00 ` [PATCH 0/4] ARM: add PSCI host support George Dunlap
2013-11-25 14:03   ` Ian Campbell
2013-11-25 14:21     ` Andre Przywara
2013-11-25 14:50       ` Ian Campbell
2013-11-25 15:03         ` Andre Przywara
2013-11-25 16:35     ` George Dunlap
2013-11-26 11:01       ` Ian Campbell
2013-11-26 11:05 ` Ian Campbell
2013-11-27 13:45   ` Andre Przywara
2013-11-27 14:28     ` Ian Campbell

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=52972160.4080307@linaro.org \
    --to=andre.przywara@linaro.org \
    --cc=Ian.Campbell@citrix.com \
    --cc=julien.grall@linaro.org \
    --cc=patches@linaro.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.