public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] ARM: PSCI 0.1 vs 0.2
Date: Mon, 10 Nov 2014 14:35:40 +0100	[thread overview]
Message-ID: <5460BF2C.3020703@siemens.com> (raw)
In-Reply-To: <ea996f930d30434597ae88bb91c581e3@BY1PR0301MB1303.namprd03.prod.outlook.com>

On 2014-11-10 14:29, bhupesh.sharma at freescale.com wrote:
> Hi, 
> 
>> -----Original Message-----
>> From: u-boot-bounces at lists.denx.de [mailto:u-boot-bounces at lists.denx.de]
>> On Behalf Of Jan Kiszka
>> Sent: Monday, November 10, 2014 6:56 PM
>> To: Marc Zyngier
>> Cc: u-boot at lists.denx.de
>> Subject: Re: [U-Boot] ARM: PSCI 0.1 vs 0.2
>>
>> On 2014-11-10 14:08, Marc Zyngier wrote:
>>> On 10/11/14 12:51, Jan Kiszka wrote:
>>>> Hi Marc,
>>>>
>>>> what is the motivation to expose a PSCI 0.1 interface in U-boot,
>>>> instead of 0.2? Support for preexisting users of 0.1? The kernel
>>>> seems to be happy with both, and I'm now wondering if we should
>>>> actually add the legacy version to Jailhouse as well (I hope we can
>> avoid this).
>>>
>>> The initial rational was simple: at the time this code was written,
>>> the
>>> 0.2 spec still in review, and nobody was implementing it. Supporting
>>> 0.1 was the only viable use-case.
>>>
>>>> Still studying the logic: Is it possible to provide both interfaces,
>>>> and would it make sense?
>>>
>>> Supporting both is very easy. Just output the 0.2 function numbers
>>> that actually make sense for 0.1 and have both compatible strings.
>>
>> Ah, cool - parameters and return values of, say, CPU_ON/OFF are
>> compatible across both versions?
>>
>> Jan
>>
>> --
> 
> We did send out some ARMv8 PSCI v0.2 u-boot patches, which can be seen here:
> 
> http://permalink.gmane.org/gmane.comp.boot-loaders.u-boot/194210

Nice. I guess that could be reused for ARMv7 as well, at least
conceptually. You are using C for some PSCI functions, specifically for
cache flushing? Need to dig deeper...

Jan

-- 
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux

  reply	other threads:[~2014-11-10 13:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-10 12:51 [U-Boot] ARM: PSCI 0.1 vs 0.2 Jan Kiszka
2014-11-10 13:08 ` Marc Zyngier
2014-11-10 13:25   ` Jan Kiszka
2014-11-10 13:29     ` bhupesh.sharma at freescale.com
2014-11-10 13:35       ` Jan Kiszka [this message]
2014-11-10 13:36     ` Marc Zyngier
2014-11-28  8:52       ` Jan Kiszka
2014-11-28 10:05         ` Marc Zyngier
2014-11-28 10:24           ` Jan Kiszka

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=5460BF2C.3020703@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=u-boot@lists.denx.de \
    /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