From: Julien Grall <julien.grall@linaro.org>
To: Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>,
stefano.stabellini@eu.citrix.com, ian.campbell@citrix.com
Cc: xen-devel@lists.xen.org
Subject: Re: [V2 3/3] amd/seattle: Initial revision of AMD Seattle support
Date: Thu, 02 Oct 2014 22:44:32 +0100 [thread overview]
Message-ID: <542DC740.8070805@linaro.org> (raw)
In-Reply-To: <542DB775.3030306@amd.com>
On 02/10/2014 21:37, Suravee Suthikulpanit wrote:
>
>
> On 10/02/2014 02:04 PM, Suravee Suthikulpanit wrote:
>>>> +#include <asm/psci.h>
>>>> +
>>>> +static const char * const seattle_dt_compat[] __initconst =
>>>> +{
>>>> + "amd,seattle",
>>>> + NULL
>>>> +};
>>>> +
>>>> +/* Seattle firmware only implements PSCI handler for
>>>> + * system off and system reset at this point.
>>>> + * This is temporary until full PSCI-0.2 is supported.
>>>> + * Then, these function will be removed.
>>>> + */
>>>> +static noinline void seattle_smc_psci(register_t func_id)
>>>> +{
>>>> + asm volatile(
>>>> + "smc #0"
>>>> + : "+r" (func_id)
>>>> + :);
>>>> +}
>>>
>>> We already have multiple implementation of smc in different place. Can
>>> we provide a common function rather than adding another one?
>>
>> The only place I found this is in the arch/arm/psci.c, which is used
>> mainly for the PSCI stuff. I can declare that one as non-static, and use
>> it here in the seattle.c.
>>
>> Suravee
>
> Julien,
>
> Actually, think about this again, I would rather keep this independent
> from the other PSCI patch series, which might not make it into 4.5. It
> is small enough and probably not too terrible to keep this.
There is also one in xen/arch/arm/platforms/exynos.c (exynos_smc).
Moving this patch could be part of this series and I don't think it
would be a showstopper for accepting it in 4.5.
Ian, any though?
Regards,
--
Julien Grall
next prev parent reply other threads:[~2014-10-02 21:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-01 19:51 [V2 0/3] Introduce AMD Seattle platform support suravee.suthikulpanit
2014-10-01 19:51 ` [V2 1/3] gicv2: Add compatibility id for gic-400 suravee.suthikulpanit
2014-10-01 19:51 ` [V2 2/3] amd/seattle: Add early printk message for the platform suravee.suthikulpanit
2014-10-02 15:52 ` Julien Grall
2014-10-02 18:40 ` Suravee Suthikulpanit
2014-10-01 19:51 ` [V2 3/3] amd/seattle: Initial revision of AMD Seattle support suravee.suthikulpanit
2014-10-02 10:41 ` Julien Grall
2014-10-02 19:04 ` Suravee Suthikulpanit
2014-10-02 20:37 ` Suravee Suthikulpanit
2014-10-02 21:26 ` Ian Campbell
2014-10-02 21:44 ` Julien Grall [this message]
2014-10-02 12:59 ` [V2 0/3] Introduce AMD Seattle platform support Ian Campbell
2014-10-02 15:10 ` Konrad Rzeszutek Wilk
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=542DC740.8070805@linaro.org \
--to=julien.grall@linaro.org \
--cc=Suravee.Suthikulpanit@amd.com \
--cc=ian.campbell@citrix.com \
--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.