From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH v2 2/3] ARM: SoC: Add per SoC SMP and CPU hotplug operations
Date: Fri, 9 Sep 2011 17:06:39 +0200 [thread overview]
Message-ID: <201109091706.39621.arnd@arndb.de> (raw)
In-Reply-To: <4E6A28F8.4070606@ti.com>
On Friday 09 September 2011, Santosh wrote:
> Sorry for such a basic question but I don't understand the need
> of these wrappers.
> I am not upto speed on this topic but what is the motivation
> behind the soc_smp_ops(). All of above functions are CPU specific
> and not really soc specific though, I agree that every SOC,
> implements it's own version.
We have two separate problems to solve that we should not confuse:
1. Get multiple soc platforms to compile together in a single kernel
binary.
2. Share as much code as possible between similar soc platforms.
Marc's patch only addresses the first problem, and we need that
anyway if we want to get e.g. cortex-a9 based systems to be
supported in the same kernel as Qualcomm and Marvell CPU based
ones.
The other part is useful too, but it's easier to do after this one.
Arnd
next prev parent reply other threads:[~2011-09-09 15:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-09 14:46 [RFC PATCH v2 0/3] Per SoC descriptor Marc Zyngier
2011-09-09 14:46 ` [RFC PATCH v2 1/3] ARM: SoC: Introduce per " Marc Zyngier
2011-09-09 14:46 ` [RFC PATCH v2 2/3] ARM: SoC: Add per SoC SMP and CPU hotplug operations Marc Zyngier
2011-09-09 14:55 ` Santosh
2011-09-09 15:06 ` Arnd Bergmann [this message]
2011-09-09 17:06 ` Santosh
2011-09-09 15:13 ` Marc Zyngier
2011-09-09 17:07 ` Santosh
2011-09-09 18:17 ` Nicolas Pitre
2011-09-09 14:46 ` [RFC PATCH v2 3/3] ARM: SoC: convert VExpress/RealView to SoC descriptor Marc Zyngier
2011-09-09 14:56 ` Arnd Bergmann
2011-09-09 15:20 ` Marc Zyngier
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=201109091706.39621.arnd@arndb.de \
--to=arnd@arndb.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