From: elder@ieee.org (Alex Elder)
To: linux-arm-kernel@lists.infradead.org
Subject: [ARM ATTEND] common ARM SMP initialization
Date: Wed, 26 Mar 2014 16:39:21 -0500 [thread overview]
Message-ID: <53334909.7050406@ieee.org> (raw)
I'd like to attend the ARM mini-summit on April 28th.
I've been working on adding SMP support for a Broadcom SoC
and have found a very large amount of duplication of code
involved in starting up secondary ARM cores.
I'm working on a patch series that creates a consolidated
set of routines for multiple platforms to use. Several
of these are going to be very easy; but there may need to
be a few (fairly small) tweaks to support more platforms
generically.
My goal is to define a set of CPU "enable-method" property
values that will allow a machine to leverage generic code
by specifying a few values in the machine's device tree.
There are two of these defined for arm64, and I'm trying
to follow the "spin-table" method there to make them as
consistent as possible.
I'll be posting some patches on this soon, but I'd like
to discuss this general topic at the summit, to make
sure I can hear from others any special requirements
or restrictions I need to know about. I'd also like
to make sure I can get these proposed changes well
tested; in most cases I don't have access to the
affected hardware.
-Alex
reply other threads:[~2014-03-26 21:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=53334909.7050406@ieee.org \
--to=elder@ieee.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 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.