On Tue, Jun 03 2014 at 10:41:51 am BST, "tiger...@via-alliance.com"
wrote:
> Hi, Marc:
>>My understanding is that if you're using the Trusted Firmware, then you
>>have an implementation of PSCI, and that's what you must use to bring
>>the CPUs into u-boot. U-Boot will be running non-secure anyway
Hi, Marc:
>My understanding is that if you're using the Trusted Firmware, then you
>have an implementation of PSCI, and that's what you must use to bring
>the CPUs into u-boot. U-Boot will be running non-secure anyway, so it
>requires the firmware to perform S to NS transition on its behalf.
Do you
On Tue, Jun 03 2014 at 3:16:19 am BST, "tiger...@via-alliance.com"
wrote:
> Hi， Marc:
>>In short, if you're setting GICD_SGIR[24] to 1, you're sending SGI0 to
>>all CPUs but yourself. This seems to match the name of the function,
>>doesn't it?
> I described my understanding based on 2014.07-RC2
Hi， Marc:
>In short, if you're setting GICD_SGIR[24] to 1, you're sending SGI0 to
>all CPUs but yourself. This seems to match the name of the function,
>doesn't it?
I described my understanding based on 2014.07-RC2 u-boot source code:
(For ARMv8 cores)
1. smp_kick_all_cpus() will send SGI0 to all o
Hi Liu,
On 30/05/14 03:25, tiger...@via-alliance.com wrote:
> Hi, Marc:
> I am studying ARMv8's u-boot code with FVP model.
> In do_nonsec_virt_switch() function in bootm.c :
> It will call smp_kick_all_cpus() function :
> It seems it would set GICD_SGIR[24] = 1, forward the interrupt to all
> CPU
Hi, Marc:
I am studying ARMv8's u-boot code with FVP model.
In do_nonsec_virt_switch() function in bootm.c :
It will call smp_kick_all_cpus() function :
It seems it would set GICD_SGIR[24] = 1, forward the interrupt to all
CPU interfaces except tha tof the processor that requested the
interrupt.
S
6 matches
Mail list logo
