All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kukjin Kim <kgene.kim@samsung.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Sachin Kamat <sachin.kamat@linaro.org>,
	linux-samsung-soc@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, kgene.kim@samsung.com,
	tushar.behera@linaro.org, tomasz.figa@gmail.com
Subject: Re: [PATCH v2 Resend 1/2] ARM: EXYNOS: Update secondary boot addr for secure mode
Date: Sat, 31 May 2014 03:42:49 +0900	[thread overview]
Message-ID: <5388D129.6000706@samsung.com> (raw)
In-Reply-To: <5388CBB9.1050003@suse.de>

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<sachin.kamat@linaro.org>
>> Signed-off-by: Tushar Behera<tushar.behera@linaro.org>
>> ---
>>   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<afaerber@suse.de>
>
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.

Thanks,
Kukjin

WARNING: multiple messages have this Message-ID (diff)
From: kgene.kim@samsung.com (Kukjin Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 Resend 1/2] ARM: EXYNOS: Update secondary boot addr for secure mode
Date: Sat, 31 May 2014 03:42:49 +0900	[thread overview]
Message-ID: <5388D129.6000706@samsung.com> (raw)
In-Reply-To: <5388CBB9.1050003@suse.de>

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<sachin.kamat@linaro.org>
>> Signed-off-by: Tushar Behera<tushar.behera@linaro.org>
>> ---
>>   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<afaerber@suse.de>
>
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.

Thanks,
Kukjin

  reply	other threads:[~2014-05-30 18:42 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-28  4:13 [PATCH v2 Resend 1/2] ARM: EXYNOS: Update secondary boot addr for secure mode Sachin Kamat
2014-05-28  4:13 ` Sachin Kamat
2014-05-28  4:13 ` [PATCH v2 Resend 2/2] ARM: dts: Add secure firmware support for Arndale-octa Sachin Kamat
2014-05-28  4:13   ` Sachin Kamat
2014-05-30 18:20   ` Kukjin Kim
2014-05-30 18:20     ` Kukjin Kim
2014-05-30 18:19 ` [PATCH v2 Resend 1/2] ARM: EXYNOS: Update secondary boot addr for secure mode Andreas Färber
2014-05-30 18:19   ` Andreas Färber
2014-05-30 18:42   ` Kukjin Kim [this message]
2014-05-30 18:42     ` Kukjin Kim
2014-05-30 18:47     ` Tomasz Figa
2014-05-30 18:47       ` Tomasz Figa
2014-06-25 10:47       ` Tushar Behera
2014-06-25 10:47         ` Tushar Behera
2014-06-13 16:25     ` Sachin Kamat
2014-06-13 16:25       ` Sachin Kamat
2014-06-23  4:33   ` Sachin Kamat
2014-06-23  4:33     ` Sachin Kamat
2014-06-25 11:43     ` Kukjin Kim
2014-06-25 11:43       ` Kukjin Kim
2014-06-25 11:54       ` Andreas Färber
2014-06-25 11:54         ` Andreas Färber
2014-07-05 14:53       ` Sachin Kamat
2014-07-05 14:53         ` Sachin Kamat

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=5388D129.6000706@samsung.com \
    --to=kgene.kim@samsung.com \
    --cc=afaerber@suse.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=sachin.kamat@linaro.org \
    --cc=tomasz.figa@gmail.com \
    --cc=tushar.behera@linaro.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.