public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: York Sun <york.sun@nxp.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 07/11] ARMv7: PSCI: add PSCI v1.0 functions skeleton
Date: Fri, 27 May 2016 10:25:37 -0700	[thread overview]
Message-ID: <57488311.3050702@nxp.com> (raw)
In-Reply-To: <CABxX_wOGqMT8SB6dG-wOodfaC3a3RvCrZW1waUN5WY0z3iC-gQ@mail.gmail.com>

On 05/19/2016 01:23 AM, Hongbo Zhang wrote:
> On Wed, May 18, 2016 at 6:39 PM, Andre Przywara <andre.przywara@arm.com> wrote:
>> Hi,
>>
>> On 18/05/16 10:10, macro.wave.z at gmail.com wrote:
>>> From: Hongbo Zhang <hongbo.zhang@nxp.com>
>>>

<snip>

>> ...
>>
>>>  static int fdt_psci(void *fdt)
>>>  {
>>>  #ifdef CONFIG_ARMV7_PSCI
>>> @@ -67,22 +96,16 @@ static int fdt_psci(void *fdt)
>>>                       return nodeoff;
>>>       }
>>>
>>> -     tmp = fdt_setprop_string(fdt, nodeoff, "compatible", "arm,psci");
>>> -     if (tmp)
>>> -             return tmp;
>>>       tmp = fdt_setprop_string(fdt, nodeoff, "method", "smc");
>>>       if (tmp)
>>>               return tmp;
>>> -     tmp = fdt_setprop_u32(fdt, nodeoff, "cpu_suspend", PSCI_FN_CPU_SUSPEND);
>>> -     if (tmp)
>>> -             return tmp;
>>> -     tmp = fdt_setprop_u32(fdt, nodeoff, "cpu_off", PSCI_FN_CPU_OFF);
>>> -     if (tmp)
>>> -             return tmp;
>>> -     tmp = fdt_setprop_u32(fdt, nodeoff, "cpu_on", PSCI_FN_CPU_ON);
>>
>> We keep those function ID specifiers in the node for compatibility
>> reasons. For PSCI 0.2 and higher they are ignored, but older OSes can
>> just use them as before.
>>
> 
> Yes, good suggestion, thanks.

Hongbo,

I see you are in agreement. Are you going to respin this patch, or keep it as is?

York

  reply	other threads:[~2016-05-27 17:25 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-18  9:10 [U-Boot] [PATCH v3 00/11] ARMv7: PSCI: add PSCI v1.0 support macro.wave.z at gmail.com
2016-05-18  9:10 ` [U-Boot] [PATCH v3 01/11] ARM: PSCI: change PSCI function IDs base and offsets macro.wave.z at gmail.com
2016-05-18  9:19   ` Chen-Yu Tsai
2016-05-19  8:40     ` Hongbo Zhang
2016-05-19  8:42       ` Chen-Yu Tsai
2016-05-18 10:07   ` Andre Przywara
2016-05-19  8:45     ` Hongbo Zhang
2016-05-19  9:07       ` Andre Przywara
2016-05-20 11:26         ` Hongbo Zhang
2016-05-23 15:54   ` Mark Rutland
2016-05-24  6:21     ` Hongbo Zhang
2016-05-18  9:10 ` [U-Boot] [PATCH v3 02/11] ARM: PSCI: change PSCI related macros definition style macro.wave.z at gmail.com
2016-05-18  9:10 ` [U-Boot] [PATCH v3 03/11] ARMv7: PSCI: update function psci_get_cpu_stack_top macro.wave.z at gmail.com
2016-05-18  9:10 ` [U-Boot] [PATCH v3 04/11] ARMv7: PSCI: update the place of saving target PC macro.wave.z at gmail.com
2016-05-18  9:10 ` [U-Boot] [PATCH v3 05/11] ARMv7: PSCI: add codes to save context ID for CPU_ON macro.wave.z at gmail.com
2016-05-18  9:10 ` [U-Boot] [PATCH v3 06/11] ARMv7: PSCI: factor out reusable psci_cpu_on_common macro.wave.z at gmail.com
2016-05-18  9:10 ` [U-Boot] [PATCH v3 07/11] ARMv7: PSCI: add PSCI v1.0 functions skeleton macro.wave.z at gmail.com
2016-05-18 10:39   ` Andre Przywara
2016-05-19  8:23     ` Hongbo Zhang
2016-05-27 17:25       ` York Sun [this message]
2016-05-30  2:11         ` Hongbo Zhang
2016-05-18  9:10 ` [U-Boot] [PATCH v3 08/11] ARMv7: PSCI: ls102xa: check target CPU ID before further operations macro.wave.z at gmail.com
2016-05-18  9:23   ` Chen-Yu Tsai
2016-05-19  7:13     ` Hongbo Zhang
2016-05-18  9:10 ` [U-Boot] [PATCH v3 09/11] ARMv7: PSCI: ls102xa: check ALREADY_ON or ON_PENDING for CPU_ON macro.wave.z at gmail.com
2016-05-18  9:10 ` [U-Boot] [PATCH v3 10/11] ARMv7: PSCI: ls102xa: add more PSCI v1.0 functions implemention macro.wave.z at gmail.com
2016-05-18  9:10 ` [U-Boot] [PATCH v3 11/11] ARMv7: PSCI: ls102xa: move secure text section into OCRAM macro.wave.z at gmail.com

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=57488311.3050702@nxp.com \
    --to=york.sun@nxp.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