From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] Get kexec working on SMP omap variants
Date: Tue, 21 Jun 2016 00:52:41 -0700 [thread overview]
Message-ID: <1466495565-17480-1-git-send-email-tony@atomide.com> (raw)
Hi all,
Here are some patches to make kexec work for SMP omaps. To test
these you need to use the latest kexec-tools.git kexec with
Russell's recent patches in "[PATCH 0/2] Simple fix to the ARM
kexec tools implementation" thread fixed for 6x. Or else you
need to use appended DTB.
I've tested these so far on 4430 duovero, omap5-uevm, and
beagle-x15.
Regards,
Tony
Tony Lindgren (4):
ARM: OMAP4+: Initialize SAR RAM base early for proper CPU1 reset for
kexec
ARM: OMAP4+: Prevent CPU1 related hang with kexec
ARM: OMAP4+: Reset CPU1 properly for kexec
ARM: OMAP4+: Allow kexec on SMP variants
arch/arm/mach-omap2/Makefile | 4 +-
arch/arm/mach-omap2/common.h | 8 ++-
arch/arm/mach-omap2/io.c | 3 +
arch/arm/mach-omap2/omap-hotplug.c | 6 ++
arch/arm/mach-omap2/omap-mpuss-lowpower.c | 29 ++++++++--
arch/arm/mach-omap2/omap-smp.c | 96 ++++++++++++++++++++++---------
arch/arm/mach-omap2/omap4-common.c | 14 ++---
7 files changed, 118 insertions(+), 42 deletions(-)
--
2.8.1
next reply other threads:[~2016-06-21 7:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-21 7:52 Tony Lindgren [this message]
2016-06-21 7:52 ` [PATCH 1/4] ARM: OMAP4+: Initialize SAR RAM base early for proper CPU1 reset for kexec Tony Lindgren
2016-06-21 7:52 ` [PATCH 2/4] ARM: OMAP4+: Prevent CPU1 related hang with kexec Tony Lindgren
2016-06-24 7:40 ` Arnd Bergmann
2016-06-27 13:26 ` Tony Lindgren
2016-06-21 7:52 ` [PATCH 3/4] ARM: OMAP4+: Reset CPU1 properly for kexec Tony Lindgren
2016-06-21 7:52 ` [PATCH 4/4] ARM: OMAP4+: Allow kexec on SMP variants Tony Lindgren
2016-06-21 16:07 ` [PATCH 0/4] Get kexec working on SMP omap variants Santosh Shilimkar
2016-06-22 9:53 ` Tony Lindgren
2016-06-22 8:35 ` Keerthy
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=1466495565-17480-1-git-send-email-tony@atomide.com \
--to=tony@atomide.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).