From: galak@codeaurora.org (Kumar Gala)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 0/5] Add smp booting support for Qualcomm ARMv8 SoCs
Date: Fri, 10 Apr 2015 15:43:21 -0500 [thread overview]
Message-ID: <1428698605-13166-1-git-send-email-galak@codeaurora.org> (raw)
This patch set adds support for SMP boot on the MSM8x16 family of Qualcomm SoCs.
To support SMP on the MSM8x16 SoCs we need to add ARMv8/64-bit SCM interfaces to
setup the boot/release addresses for the secondary CPUs. In addition we need
a uniquie set of cpu ops. I'm aware the desired methods for booting secondary
CPUs is either via spintable or PSCI. However, these SoCs are shipping with a
firmware that does not support those methods.
v2:
* Dropped introduction and use of CPU_METHOD_OF_DECLARE
* Moved qcom cpu ops from drivers/soc/qcom to arch/arm64/kernel
* Renamed msm to qcom in cpu ops code, minor cleans (remove dead defines/code)
- k
--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
next reply other threads:[~2015-04-10 20:43 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 20:43 Kumar Gala [this message]
2015-04-10 20:43 ` [RFC PATCH v2 1/4] firmware: qcom: scm: Split out 32-bit specific SCM code Kumar Gala
2015-04-10 20:43 ` [RFC PATCH v2 2/4] firmware: qcom: scm: Add support for ARM64 SoCs Kumar Gala
2015-04-10 20:43 ` [RFC PATCH v3 3/4] arm64: smp: move the pen to a header file Kumar Gala
2015-04-10 20:43 ` [RFC PATCH v2 4/4] arm64: qcom: add cpu operations Kumar Gala
2015-04-10 20:57 ` Arnd Bergmann
-- strict thread matches above, loose matches on Subject: below --
2015-04-09 17:37 [RFC PATCH 0/5] Add smp booting support for Qualcomm ARMv8 SoCs Kumar Gala
2015-04-10 10:05 ` Catalin Marinas
2015-04-10 15:24 ` Kumar Gala
2015-04-10 16:10 ` Catalin Marinas
2015-04-10 19:06 ` Kumar Gala
2015-04-13 9:41 ` Catalin Marinas
2015-04-14 14:21 ` Kumar Gala
2015-04-14 14:44 ` Kumar Gala
2015-04-14 15:45 ` Mark Rutland
2015-04-14 22:32 ` Lorenzo Pieralisi
2015-04-15 16:17 ` Lina Iyer
2015-04-15 17:35 ` Lorenzo Pieralisi
2015-04-15 14:27 ` Catalin Marinas
2015-04-14 16:36 ` Mark Rutland
2015-04-14 19:49 ` Kumar Gala
2015-04-14 21:17 ` Catalin Marinas
2015-04-14 21:48 ` Rob Clark
2015-04-15 13:34 ` Catalin Marinas
2015-04-15 15:01 ` Rob Clark
2015-04-16 15:21 ` Catalin Marinas
2015-04-16 17:17 ` Rob Clark
2015-04-16 21:39 ` Catalin Marinas
2015-04-16 22:03 ` Matt Sealey
2015-04-10 11:03 ` Lorenzo Pieralisi
2015-04-10 15:25 ` Kumar Gala
2015-04-10 16:07 ` Lorenzo Pieralisi
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=1428698605-13166-1-git-send-email-galak@codeaurora.org \
--to=galak@codeaurora.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 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).