From: Alex Elder <elder@linaro.org>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: Matt Porter <mporter@linaro.org>,
Christian Daudt <bcm@fixthebug.org>,
Russell King <linux@arm.linux.org.uk>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
sboyd@codeaurora.org, bcm-kernel-feedback-list@broadcom.com,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v3 RESEND 2/5] ARM: add SMP support for Broadcom mobile SoCs
Date: Thu, 15 May 2014 13:17:00 -0500 [thread overview]
Message-ID: <5375049C.40104@linaro.org> (raw)
In-Reply-To: <CAGVrzca20+3kmJjyGv8Pr-qNNV4n0hhADL6GWvcYVDUL4q28Hg@mail.gmail.com>
On 05/15/2014 01:03 PM, Florian Fainelli wrote:
> Hi Alex,
>
> 2014-05-15 10:58 GMT-07:00 Alex Elder <elder@linaro.org>:
>> This patch adds SMP support for BCM281XX and BCM21664 family SoCs.
>>
>> This feature is controlled with a distinct config option such that a
>> SMP-enabled multi-v7 binary can be configured to run these SoCs in
>> uniprocessor mode. Since this SMP functionality is used for
>> multiple Broadcom mobile chip families the config option is called
>> ARCH_BCM_MOBILE_SMP (for lack of a better name).
>>
>> On SoCs of this type, the secondary core is not held in reset on
>> power-on. Instead it loops in a ROM-based holding pen. To release
>> it, one must write into a special register a jump address whose
>> low-order bits have been replaced with a secondary core's id, then
>> trigger an event with SEV. On receipt of an event, the ROM code
>> will examine the register's contents, and if the low-order bits
>> match its cpu id, it will clear them and write the value back to the
>> register just prior to jumping to the address specified.
>>
>> The location of the special register is defined in the device tree
>> using a "secondary-boot-reg" property in a node whose "enable-method"
>> matches.
>>
>> Derived from code originally provided by Ray Jui <rjui@broadcom.com>
>>
>> Signed-off-by: Alex Elder <elder@linaro.org>
>> ---
>> arch/arm/mach-bcm/Kconfig | 18 +++-
>> arch/arm/mach-bcm/Makefile | 3 +
>> arch/arm/mach-bcm/platsmp.c | 201 ++++++++++++++++++++++++++++++++++++++++++++
>
> Could we make that name a little bit more specific to the mobile SoCs?
Sure. I thought about that but naming stuff here has been a sort
of ongoing struggle... "Kona" made some sense, in some cases,
but it's not perfect. Simlar with "mobile."
I'll propose "kona_smp.c". OK with you? Unless I get a better
suggestion I'll plan to go with that next time around.
Thanks.
-Alex
> There are other BCM SoCs either currently supported in this directory
> (BCM5310X), or making their way to be supported (brcmstb, bcm63xx),
> and those share nothing with the Mobile SoC SMP code.
>
> Maybe we should create another level directory within mach-bcm...
>
next prev parent reply other threads:[~2014-05-15 18:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 17:58 [PATCH v3 RESEND 0/5] ARM: SMP: support Broadcom mobile SoCs Alex Elder
2014-05-15 17:58 ` [PATCH v3 RESEND 1/5] devicetree: bindings: document Broadcom CPU enable method Alex Elder
2014-05-15 17:58 ` [PATCH v3 RESEND 2/5] ARM: add SMP support for Broadcom mobile SoCs Alex Elder
[not found] ` <1400176691-26058-3-git-send-email-elder-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2014-05-15 18:03 ` Florian Fainelli
2014-05-15 18:17 ` Alex Elder [this message]
[not found] ` <5375049C.40104-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2014-05-15 19:19 ` Matt Porter
[not found] ` <CAGVrzca20+3kmJjyGv8Pr-qNNV4n0hhADL6GWvcYVDUL4q28Hg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-05-15 18:26 ` Matt Porter
2014-05-15 18:31 ` Florian Fainelli
2014-05-15 17:58 ` [PATCH v3 RESEND 3/5] ARM: configs: enable SMP in bcm_defconfig Alex Elder
2014-05-15 17:58 ` [PATCH v3 RESEND 4/5] ARM: dts: enable SMP support for bcm28155 Alex Elder
2014-05-15 17:58 ` [PATCH v3 RESEND 5/5] ARM: dts: enable SMP support for bcm21664 Alex Elder
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=5375049C.40104@linaro.org \
--to=elder@linaro.org \
--cc=arnd@arndb.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bcm@fixthebug.org \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mporter@linaro.org \
--cc=sboyd@codeaurora.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).