From: Suravee Suthikulanit <suravee.suthikulpanit@amd.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: "julien.grall@linaro.org" <julien.grall@linaro.org>,
"ian.campbell@citrix.com" <ian.campbell@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH 4/4] amd/seattle: Initial revision of AMD Seattle support
Date: Wed, 1 Oct 2014 14:21:55 -0500 [thread overview]
Message-ID: <542C5453.7040004@amd.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1410011107160.17038@kaball.uk.xensource.com>
On 10/1/2014 5:10 AM, Stefano Stabellini wrote:
> On Wed, 1 Oct 2014, suravee.suthikulpanit@amd.com wrote:
>> From: Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>
>>
>> This patch add inital (minimal) platform support for AMD Seattle,
>> which mainly just define the matching ID, and specify system_off,
>> and sytem_reset mechanism.
>>
>> Initially, the firmware only support a subset of PSCI-0.2 functions,
>> system-off and sytem-reset. The boot protocol is still using spin-table.
>
> In that case, aren't you missing
>
> cpu_up = cpu_up_send_sgi
>
> ?
>
> Or are you just going to assume that the firmware is going to be updated
> to support full PSCI 0.2?
I thought the platform_cpu_up() is only called from the
arch/arm/arm32/smpboot.c. Is it also used for ARM64?
And yes, the firmware will support full PSCI-0.2 eventually.
Thanks,
Suravee
next prev parent reply other threads:[~2014-10-01 19:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-01 8:07 [PATCH 0/4] Introduce AMD Seattle platform support suravee.suthikulpanit
2014-10-01 8:07 ` [PATCH 1/4] gicv2: Add compatibility id for gic-400 suravee.suthikulpanit
2014-10-01 9:54 ` Stefano Stabellini
2014-10-01 14:41 ` Julien Grall
2014-10-01 8:07 ` [PATCH 2/4] amd/seattle: Add early printk message for the platform suravee.suthikulpanit
2014-10-01 9:55 ` Stefano Stabellini
2014-10-01 14:43 ` Julien Grall
2014-10-01 8:07 ` [PATCH 3/4] xen/arm: Add PSCI system_off and system_reset support suravee.suthikulpanit
2014-10-01 10:07 ` Stefano Stabellini
2014-10-01 10:26 ` Ian Campbell
2014-10-01 14:15 ` Suravee Suthikulpanit
2014-10-01 14:46 ` Ian Campbell
2014-10-01 17:58 ` Suravee Suthikulanit
2014-10-02 8:28 ` Ian Campbell
2014-10-01 14:04 ` Ian Campbell
2014-10-01 8:07 ` [PATCH 4/4] amd/seattle: Initial revision of AMD Seattle support suravee.suthikulpanit
2014-10-01 10:10 ` Stefano Stabellini
2014-10-01 19:21 ` Suravee Suthikulanit [this message]
2014-10-02 9:10 ` Stefano Stabellini
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=542C5453.7040004@amd.com \
--to=suravee.suthikulpanit@amd.com \
--cc=ian.campbell@citrix.com \
--cc=julien.grall@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 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).