From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/8] ARM: SCU: Add common routines for secondary CPUbootup
Date: Mon, 6 Dec 2010 12:58:02 +0530 [thread overview]
Message-ID: <a77f1800c9be01e7c81532a716b4e260@mail.gmail.com> (raw)
In-Reply-To: <20101204084815.GA20969@n2100.arm.linux.org.uk>
> -----Original Message-----
> From: linux-omap-owner at vger.kernel.org [mailto:linux-omap-
> owner at vger.kernel.org] On Behalf Of Russell King - ARM Linux
> Sent: Saturday, December 04, 2010 2:18 PM
> To: Tony Lindgren; Kukjin Kim; Srinidhi Kasagar; Jamie Iles; Anton
> Vorontsov; linux-kernel at vger.kernel.org; linux-samsung-
> soc at vger.kernel.org; Colin Cross; linux-tegra at vger.kernel.org; Uwe
Kleine-
> K?nig; linux-omap at vger.kernel.org; linux-arm-kernel at lists.infradead.org
> Subject: Re: [PATCH 1/8] ARM: SCU: Add common routines for secondary
> CPUbootup
>
> On Thu, Dec 02, 2010 at 06:01:50PM +0000, Russell King - ARM Linux
wrote:
> > On Thu, Dec 02, 2010 at 05:38:24PM +0000, Russell King - ARM Linux
> wrote:
> > > What if a platform, for what ever reason, wants to have 3 CPUs,
> > > numbered 0, 2, 3 ? That's the reason why the code which sets the
> > > possible and present maps isn't in the ARM core code - Eg, we don't
> > > know if a platform wants to keep CPU 1 in AMP mode to run some
> > > special software on it.
> > >
> > > I don't think it's worth it because I think trying to considate this
> > > is going to cripple the code structure in the future.
> >
> > I don't think this is particularly worth it either:
>
> As Catalin has pointed out:
>
>
http://lists.arm.linux.org.uk/lurker/message/20101202.162840.5465758c.en.h
> tml
>
> The SCU is part of the core, and if you consult the TRMs for the MPCore
> devices, it is actually different in ARM11 MPCore vs Cortex-A9 MPCore.
> Cortex-A15 doesn't have a MMIO addressable SCU at all.
>
> So, this is about as far as I want to go with stripping out the common
> code from the various platforms (this includes my previous SMP series):
>
>
http://lists.arm.linux.org.uk/lurker/message/20101203.200746.31424430.en.h
> tml
>
> This results in a net reduction of 242 LOC, as shown in the following
> diffstat:
>
> arch/arm/include/asm/hardirq.h | 18 ++
> arch/arm/include/asm/mach/irq.h | 2 +-
> arch/arm/include/asm/smp.h | 17 +-
> arch/arm/include/asm/smp_mpidr.h | 17 --
> arch/arm/kernel/entry-armv.S | 2 +-
> arch/arm/kernel/fiq.c | 5 +-
> arch/arm/kernel/head.S | 39 +++--
> arch/arm/kernel/irq.c | 23 ++-
> arch/arm/kernel/smp.c | 243
++++++++++++++++--------
> -----
> arch/arm/mach-msm/include/mach/smp.h | 4 +-
> arch/arm/mach-omap2/omap-hotplug.c | 14 +--
> arch/arm/mach-omap2/omap-smp.c | 66 ++------
> arch/arm/mach-realview/hotplug.c | 18 +--
> arch/arm/mach-realview/include/mach/smp.h | 5 +-
> arch/arm/mach-realview/platsmp.c | 95 +++---------
> arch/arm/mach-s5pv310/hotplug.c | 18 +--
> arch/arm/mach-s5pv310/include/mach/smp.h | 5 +-
> arch/arm/mach-s5pv310/platsmp.c | 46 +-----
> arch/arm/mach-tegra/hotplug.c | 18 +--
> arch/arm/mach-tegra/include/mach/smp.h | 12 +--
> arch/arm/mach-tegra/platsmp.c | 33 +---
> arch/arm/mach-ux500/hotplug.c | 18 +--
> arch/arm/mach-ux500/include/mach/smp.h | 5 +-
> arch/arm/mach-ux500/platsmp.c | 57 ++-----
> arch/arm/mach-vexpress/include/mach/smp.h | 5 +-
> arch/arm/mach-vexpress/platsmp.c | 54 ++-----
> arch/arm/plat-omap/include/plat/smp.h | 5 +-
> 27 files changed, 301 insertions(+), 543 deletions(-)
>
> Can someone also explain why OMAP uses different file naming from
everyone
> else? It's annoying as (eg) arch/arm/*/platsmp.c for editing the
platform
> SMP support files gets everyone except OMAP.
Nothing specific Russell?.
Its just to keep in sync with the way other files are named
under omap directories. We could rename this if it helps.
Regards,
Ssantosh
next prev parent reply other threads:[~2010-12-06 7:28 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-30 17:16 [PATCH v4 0/8] SMP support for CNS3xxx + some SMP SCU cleanups Anton Vorontsov
2010-11-30 17:16 ` [PATCH 1/8] ARM: SCU: Add common routines for secondary CPU bootup Anton Vorontsov
2010-11-30 22:24 ` Russell King - ARM Linux
2010-11-30 23:32 ` Russell King - ARM Linux
2010-12-01 0:25 ` Russell King - ARM Linux
2010-12-02 15:19 ` Catalin Marinas
2010-12-02 15:24 ` Russell King - ARM Linux
2010-12-02 16:28 ` Catalin Marinas
2010-12-02 17:38 ` Russell King - ARM Linux
2010-12-02 17:55 ` Catalin Marinas
2010-12-02 18:01 ` Russell King - ARM Linux
2010-12-04 8:48 ` Russell King - ARM Linux
2010-12-06 7:28 ` Santosh Shilimkar [this message]
2010-12-01 6:21 ` Srinidhi Kasagar
2010-11-30 17:17 ` [PATCH 2/8] ARM: cns3xxx: Add support for SMP Anton Vorontsov
2010-11-30 18:14 ` Russell King - ARM Linux
2010-11-30 17:17 ` [PATCH 3/8] ARM: VExpress: Switch to generic SCU routines Anton Vorontsov
2010-11-30 23:27 ` Russell King - ARM Linux
2010-11-30 17:17 ` [PATCH 4/8] ARM: RealView: " Anton Vorontsov
2010-11-30 17:17 ` [PATCH 5/8] ARM: S5PV310: " Anton Vorontsov
2010-11-30 17:17 ` [PATCH 6/8] ARM: ux500: " Anton Vorontsov
2010-11-30 17:17 ` [PATCH 7/8] ARM: tegra: " Anton Vorontsov
2010-11-30 17:17 ` [PATCH 8/8] ARM: OMAP2: " Anton Vorontsov
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=a77f1800c9be01e7c81532a716b4e260@mail.gmail.com \
--to=santosh.shilimkar@ti.com \
--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).