From: lorenzo.pieralisi@arm.com (Lorenzo Pieralisi)
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 12:03:28 +0100 [thread overview]
Message-ID: <20150410110328.GC25921@red-moon> (raw)
In-Reply-To: <1428601031-5366-1-git-send-email-galak@codeaurora.org>
On Thu, Apr 09, 2015 at 06:37:06PM +0100, Kumar Gala wrote:
> 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.
Why ? Do not tell me you were not aware of those standard methods,
because I can't believe you.
If there were additional features to add to spin-table and PSCI,
you were, you are and you will always be welcome to debate them.
There is no justification for this patchset, honestly.
Lorenzo
next prev parent reply other threads:[~2015-04-10 11:03 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-09 17:37 [RFC PATCH 0/5] Add smp booting support for Qualcomm ARMv8 SoCs Kumar Gala
2015-04-09 17:37 ` [RFC PATCH 1/5] firmware: qcom: scm: Split out 32-bit specific SCM code Kumar Gala
2015-04-09 17:37 ` [RFC PATCH 2/5] firmware: qcom: scm: Add support for ARM64 SoCs Kumar Gala
2015-04-09 17:37 ` [RFC PATCH 3/5] arm64: introduce CPU_OF_TABLES for cpu ops selection Kumar Gala
2015-04-09 21:17 ` Arnd Bergmann
2015-04-14 15:52 ` Mark Rutland
2015-04-10 10:28 ` Lorenzo Pieralisi
2015-04-09 17:37 ` [RFC PATCH 4/5] arm64: smp: move the pen to a header file Kumar Gala
2015-04-09 21:17 ` Arnd Bergmann
2015-04-14 19:41 ` Kumar Gala
2015-04-14 15:59 ` Mark Rutland
2015-04-14 19:40 ` Kumar Gala
2015-04-09 17:37 ` [RFC PATCH 5/5] arm64: qcom: add cpu operations Kumar Gala
2015-04-09 21:19 ` Arnd Bergmann
2015-04-10 10:08 ` Catalin Marinas
2015-04-10 10:39 ` Lorenzo Pieralisi
2015-04-14 16:29 ` Mark Rutland
2015-04-14 20:51 ` Arnd Bergmann
2015-04-15 14:46 ` Catalin Marinas
2015-04-14 22:52 ` Al Stone
2015-04-15 9:04 ` Mark Rutland
2015-04-15 14:53 ` Catalin Marinas
2015-04-15 16:29 ` Al Stone
2015-04-10 10:05 ` [RFC PATCH 0/5] Add smp booting support for Qualcomm ARMv8 SoCs 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 [this message]
2015-04-10 15:25 ` Kumar Gala
2015-04-10 16:07 ` Lorenzo Pieralisi
-- strict thread matches above, loose matches on Subject: below --
2015-04-10 20:43 Kumar Gala
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=20150410110328.GC25921@red-moon \
--to=lorenzo.pieralisi@arm.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).