Subject: [PATCH v2 Resend 1/2] ARM: EXYNOS: Update secondary boot addr for secure mode

From: [email-masked] (Tushar Behera)
Date: Wed, 25 Jun 2014 16:17:57 +0530

On 05/31/2014 12:17 AM, Tomasz Figa wrote:
> On 30.05.2014 20:42, Kukjin Kim wrote:
>> On 05/31/14 03:19, Andreas F?rber wrote:
>>> Am 28.05.2014 06:13, schrieb Sachin Kamat:
>>>> Almost all Exynos-series of SoCs that run in secure mode don't need
>>>> additional offset for every CPU, with Exynos4412 being the only
>>>> exception.
>>>>
>>>> Tested on Origen-Quad (Exynos4412) and Arndale-Octa (Exynos5420).
>>>>
>>>> While at it, fix the coding style (space around *).
>>>>
>>>> Signed-off-by: Sachin Kamat<[email-masked]>
>>>> Signed-off-by: Tushar Behera<[email-masked]>
>>>> ---
>>>>   arch/arm/mach-exynos/firmware.c |    9 +++++++--
>>>>   1 file changed, 7 insertions(+), 2 deletions(-)
>>>
>>> Fixes ODROID-XU (Exynos5410) as well - thought it had been a prereq to
>>> applying the 5410 patches...
>>>
>>> Tested-by: Andreas F?rber<[email-masked]>
>>>
>> Andreas, thanks for your test :-)
>>
>> Sachin, How about exynos4210, 5250, 5260 and 5440?...
>> I need to check again, honestly I don't remember all of Exynos SoCs'
>> different things ;-) Then will apply into fixes for 3.16.
> 
> Exynos4210 doesn't use secure firmware, at least on any board supported
> in mainline. Not sure about those Exynos5 models, but the only boards
> supported in mainline with firmware node in DT are based on Exynos4412
> or Exynos5410.
> 
> Best regards,
> Tomasz
> 

Kukjin,

Would you please pick this patch as a fix for 3.16?

-- 
Tushar Behera