From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 4/6] arm/imx6q: add smp and cpu hotplug support
Date: Mon, 26 Sep 2011 13:06:34 +0200 [thread overview]
Message-ID: <20110926110634.GR31404@pengutronix.de> (raw)
In-Reply-To: <1317021651-17359-5-git-send-email-shawn.guo@linaro.org>
On Mon, Sep 26, 2011 at 03:20:49PM +0800, Shawn Guo wrote:
> It adds smp and cpu hotplug support for imx6q.
>
> Signed-off-by: Shawn Guo <shawn.guo@linaro.org>
> ---
> arch/arm/mach-imx/Kconfig | 1 +
> arch/arm/mach-imx/Makefile | 4 ++
> arch/arm/mach-imx/head-v7.S | 71 ++++++++++++++++++++++++++
> arch/arm/mach-imx/hotplug.c | 44 ++++++++++++++++
> arch/arm/mach-imx/localtimer.c | 35 +++++++++++++
> arch/arm/mach-imx/platsmp.c | 85 +++++++++++++++++++++++++++++++
> arch/arm/plat-mxc/include/mach/common.h | 5 ++
> 7 files changed, 245 insertions(+), 0 deletions(-)
> create mode 100644 arch/arm/mach-imx/head-v7.S
> create mode 100644 arch/arm/mach-imx/hotplug.c
> create mode 100644 arch/arm/mach-imx/localtimer.c
> create mode 100644 arch/arm/mach-imx/platsmp.c
>
> diff --git a/arch/arm/mach-imx/Kconfig b/arch/arm/mach-imx/Kconfig
> index af73b3e..6ec758d 100644
> --- a/arch/arm/mach-imx/Kconfig
> +++ b/arch/arm/mach-imx/Kconfig
> @@ -623,6 +623,7 @@ config SOC_IMX6Q
> bool "i.MX6 Quad support"
> select ARM_GIC
> select CPU_V7
> + select HAVE_ARM_SCU
> select HAVE_IMX_GPC
> select HAVE_IMX_MMDC
> select HAVE_IMX_SRC
> diff --git a/arch/arm/mach-imx/Makefile b/arch/arm/mach-imx/Makefile
> index 8c21fda..d46b2e7 100644
> --- a/arch/arm/mach-imx/Makefile
> +++ b/arch/arm/mach-imx/Makefile
> @@ -66,4 +66,8 @@ obj-$(CONFIG_DEBUG_LL) += lluart.o
> obj-$(CONFIG_HAVE_IMX_GPC) += gpc.o
> obj-$(CONFIG_HAVE_IMX_MMDC) += mmdc.o
> obj-$(CONFIG_HAVE_IMX_SRC) += src.o
> +obj-$(CONFIG_CPU_V7) += head-v7.o
Can we have a
AFLAGS_head-v7.o :=-Wa,-march=armv7-a
here?
Then you only have to adjust some Kconfig variables and can compile
i.MX3 and i.MX6 together. I just gave it a test and it works on i.MX3, I
don't have a i.MX6 platform to test on though.
The following patch could be a starting point. I merged the imx-features
branch into it so it probably won't apply cleanly on your series.
8<----------------------------------------
next prev parent reply other threads:[~2011-09-26 11:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-26 7:20 [PATCH v3 0/6] add initial imx6q support Shawn Guo
2011-09-26 7:20 ` [PATCH v3 1/6] arm/imx6q: add device tree source Shawn Guo
2011-09-26 7:20 ` [PATCH v3 2/6] arm/imx6q: add core definitions and low-level debug uart Shawn Guo
2011-09-26 7:20 ` [PATCH v3 3/6] arm/imx6q: add core drivers clock, gpc, mmdc and src Shawn Guo
2011-09-26 7:20 ` [PATCH v3 4/6] arm/imx6q: add smp and cpu hotplug support Shawn Guo
2011-09-26 11:06 ` Sascha Hauer [this message]
2011-09-26 11:47 ` Russell King - ARM Linux
2011-09-26 13:34 ` Shawn Guo
2011-09-27 13:44 ` Shawn Guo
2011-09-27 15:15 ` Shawn Guo
2011-09-28 6:29 ` Sascha Hauer
2011-09-28 8:57 ` Shawn Guo
2011-09-28 7:43 ` Shawn Guo
2011-09-26 7:20 ` [PATCH v3 5/6] arm/imx6q: add device tree machine support Shawn Guo
2011-09-26 7:20 ` [PATCH v3 6/6] arm/imx6q: add suspend/resume support Shawn Guo
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=20110926110634.GR31404@pengutronix.de \
--to=s.hauer@pengutronix.de \
--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).