Re: [PATCH] Documentation: ARM: EXYNOS: Update bootloader interface on Exynos542x

2015-10-23 Thread Kukjin Kim
On 10/23/15 13:19, Krzysztof Kozlowski wrote:
> Update the documentation about:
> 1. Usage of PMU_SPARE2 register.
>Bootloaders on Exynos542x-based boards often use the register
>PMU_SPARE2 (0x908) in the same way as on Exynos3250: as a indicator
>the secondary CPU was booted on. The bootloader will set this value
>to non-zero, after sucessfull power up of secondary CPU. In the same
>time this booted CPU will stuck (spin) waiting for software reset.
> 2. Exynos542x entry address for secondary CPU boot up after system
>suspend (with MCPM enabled and in non-secure mode).
> 
> See arch/arm/mach-exynos/mcpm-exynos.c for source code.
> 
> Signed-off-by: Krzysztof Kozlowski 
> ---
>  Documentation/arm/Samsung/Bootloader-interface.txt | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/Documentation/arm/Samsung/Bootloader-interface.txt 
> b/Documentation/arm/Samsung/Bootloader-interface.txt
> index df8d4fb85939..ed494ac0beb2 100644
> --- a/Documentation/arm/Samsung/Bootloader-interface.txt
> +++ b/Documentation/arm/Samsung/Bootloader-interface.txt
> @@ -19,7 +19,7 @@ executing kernel.
>  Address:  sysram_ns_base_addr
>  OffsetValuePurpose
>  =
> -0x08  exynos_cpu_resume_ns System suspend
> +0x08  exynos_cpu_resume_ns, mcpm_entry_point   System suspend
>  0x0c  0x0bad (Magic cookie)System suspend
>  0x1c  exynos4_secondary_startupSecondary CPU boot
>  0x1c + 4*cpu  exynos4_secondary_startup (Exynos4412)   Secondary CPU boot
> @@ -56,7 +56,8 @@ OffsetValue
> Purpose
>  Address:  pmu_base_addr
>  OffsetValue   Purpose
>  =
> -0x0908Non-zero (only Exynos3250)  Secondary CPU boot up indicator
> +0x0908Non-zeroSecondary CPU boot up indicator
> +  on Exynos3250 and Exynos542x
>  
>  
>  4. Glossary

Applied, thanks.

- Kukjin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


[PATCH] Documentation: ARM: EXYNOS: Update bootloader interface on Exynos542x

2015-10-22 Thread Krzysztof Kozlowski
Update the documentation about:
1. Usage of PMU_SPARE2 register.
   Bootloaders on Exynos542x-based boards often use the register
   PMU_SPARE2 (0x908) in the same way as on Exynos3250: as a indicator
   the secondary CPU was booted on. The bootloader will set this value
   to non-zero, after sucessfull power up of secondary CPU. In the same
   time this booted CPU will stuck (spin) waiting for software reset.
2. Exynos542x entry address for secondary CPU boot up after system
   suspend (with MCPM enabled and in non-secure mode).

See arch/arm/mach-exynos/mcpm-exynos.c for source code.

Signed-off-by: Krzysztof Kozlowski 
---
 Documentation/arm/Samsung/Bootloader-interface.txt | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/Documentation/arm/Samsung/Bootloader-interface.txt 
b/Documentation/arm/Samsung/Bootloader-interface.txt
index df8d4fb85939..ed494ac0beb2 100644
--- a/Documentation/arm/Samsung/Bootloader-interface.txt
+++ b/Documentation/arm/Samsung/Bootloader-interface.txt
@@ -19,7 +19,7 @@ executing kernel.
 Address:  sysram_ns_base_addr
 OffsetValuePurpose
 =
-0x08  exynos_cpu_resume_ns System suspend
+0x08  exynos_cpu_resume_ns, mcpm_entry_point   System suspend
 0x0c  0x0bad (Magic cookie)System suspend
 0x1c  exynos4_secondary_startupSecondary CPU boot
 0x1c + 4*cpu  exynos4_secondary_startup (Exynos4412)   Secondary CPU boot
@@ -56,7 +56,8 @@ OffsetValue
Purpose
 Address:  pmu_base_addr
 OffsetValue   Purpose
 =
-0x0908Non-zero (only Exynos3250)  Secondary CPU boot up indicator
+0x0908Non-zeroSecondary CPU boot up indicator
+  on Exynos3250 and Exynos542x
 
 
 4. Glossary
-- 
1.9.1

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/