Re: [PATCH v6 04/21] arm64: boot protocol documentation update for GICv3

[Mark Rutland <mark.rutland@arm.com>]

Hi Marc,

On Mon, Jun 30, 2014 at 04:01:33PM +0100, Marc Zyngier wrote:
> Linux has some requirements that must be satisfied in order to boot
> on a system built with a GICv3.
> 
> Acked-by: Christoffer Dall <christoffer.dall@linaro.org>
> Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>

FWIW:

Acked-by: Mark Rutland <mark.rutland@arm.com>

Mark.

> ---
>  Documentation/arm64/booting.txt | 8 ++++++++
>  1 file changed, 8 insertions(+)
> 
> diff --git a/Documentation/arm64/booting.txt b/Documentation/arm64/booting.txt
> index 37fc4f6..da1d4bf 100644
> --- a/Documentation/arm64/booting.txt
> +++ b/Documentation/arm64/booting.txt
> @@ -141,6 +141,14 @@ Before jumping into the kernel, the following conditions must be met:
>    the kernel image will be entered must be initialised by software at a
>    higher exception level to prevent execution in an UNKNOWN state.
>  
> +  For systems with a GICv3 interrupt controller:
> +  - If EL3 is present:
> +    ICC_SRE_EL3.Enable (bit 3) must be initialiased to 0b1.
> +    ICC_SRE_EL3.SRE (bit 0) must be initialised to 0b1.
> +  - If the kernel is entered at EL1:
> +    ICC.SRE_EL2.Enable (bit 3) must be initialised to 0b1
> +    ICC_SRE_EL2.SRE (bit 0) must be initialised to 0b1.
> +
>  The requirements described above for CPU mode, caches, MMUs, architected
>  timers, coherency and system registers apply to all CPUs.  All CPUs must
>  enter the kernel in the same exception level.
> -- 
> 2.0.0
>