linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: chander.kashyap@linaro.org (Chander Kashyap)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 09/10] ARM: Exynos: add secondary CPU boot base location for Exynos5420
Date: Mon, 17 Jun 2013 16:30:34 +0530	[thread overview]
Message-ID: <1371466836-4111-10-git-send-email-chander.kashyap@linaro.org> (raw)
In-Reply-To: <1371466836-4111-1-git-send-email-chander.kashyap@linaro.org>

The location at which the boot address is specified for secondary CPUs of
Exynos5420 is SYSRAM base + 4. Update the cpu_boot_reg function accordingly.

Signed-off-by: Chander Kashyap <chander.kashyap@linaro.org>
---
 arch/arm/mach-exynos/platsmp.c |    2 ++
 1 file changed, 2 insertions(+)

diff --git a/arch/arm/mach-exynos/platsmp.c b/arch/arm/mach-exynos/platsmp.c
index 85ea4ca..7b4c03e 100644
--- a/arch/arm/mach-exynos/platsmp.c
+++ b/arch/arm/mach-exynos/platsmp.c
@@ -50,6 +50,8 @@ static inline void __iomem *cpu_boot_reg(int cpu)
 	boot_reg = cpu_boot_reg_base();
 	if (soc_is_exynos4412())
 		boot_reg += 4*cpu;
+	else if (soc_is_exynos5420())
+		boot_reg += 4;
 	return boot_reg;
 }
 
-- 
1.7.9.5

  parent reply	other threads:[~2013-06-17 11:00 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-17 11:00 [PATCH v3 00/10] ARM: Exynos: Add Exynos5420 SoC support Chander Kashyap
2013-06-17 11:00 ` [PATCH v3 01/10] ARM: dts: fork out common Exynos5 nodes Chander Kashyap
2013-06-17 11:38   ` Kukjin Kim
2013-06-18  4:24     ` Chander Kashyap
2013-06-17 11:00 ` [PATCH v3 02/10] ARM: dts: list the CPU nodes for Exynos5250 Chander Kashyap
2013-06-17 11:00 ` [PATCH v3 03/10] ARM: Exynos: Add support for Exynos5420 SoC Chander Kashyap
2013-06-17 11:00 ` [PATCH v3 04/10] serial: samsung: select Exynos specific driver data if ARCH_EXYNOS is defined Chander Kashyap
2013-06-17 11:45   ` Kukjin Kim
2013-06-18 10:31   ` Kukjin Kim
2013-06-18 15:19     ` 'Greg Kroah-Hartman'
2013-06-17 11:00 ` [PATCH v3 05/10] ARM: Exynos: use four additional chipid bits to identify Exynos family Chander Kashyap
2013-06-17 11:00 ` [PATCH v3 06/10] clk: exynos5420: register clocks using common clock framework Chander Kashyap
2013-06-17 11:49   ` Kukjin Kim
2013-06-17 12:27   ` Arnd Bergmann
2013-06-18  4:09     ` Chander Kashyap
2013-06-18 14:01       ` Arnd Bergmann
2013-06-18 14:26         ` Tomasz Figa
2013-06-18 17:13           ` Arnd Bergmann
2013-06-17 11:00 ` [PATCH v3 07/10] ARM: dts: Add initial device tree support for Exynos5420 Chander Kashyap
2013-06-17 11:44   ` Tomasz Figa
2013-06-18  4:21     ` Chander Kashyap
2013-06-18  7:36       ` Tomasz Figa
2013-06-17 11:00 ` [PATCH v3 08/10] clocksource: exynos_mct: use (request/free)_irq calls for local timer registration Chander Kashyap
2013-06-17 11:53   ` Kukjin Kim
2013-06-18  4:11     ` Chander Kashyap
2013-06-17 11:00 ` Chander Kashyap [this message]
2013-06-17 11:00 ` [PATCH v3 10/10] ARM: Exynos: extend soft-reset support for Exynos5420 Chander Kashyap
2013-06-17 12:21   ` Arnd Bergmann
2013-06-18  4:10     ` Chander Kashyap
2013-06-17 11:45 ` [PATCH v3 00/10] ARM: Exynos: Add Exynos5420 SoC support Tomasz Figa
2013-06-17 11:56 ` Kukjin Kim
2013-06-18  4:28   ` Chander Kashyap

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=1371466836-4111-10-git-send-email-chander.kashyap@linaro.org \
    --to=chander.kashyap@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).