linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Derek Basehore <dbasehore@chromium.org>
To: linux-kernel@vger.kernel.org
Cc: linux-pm@vger.kernel.org, rafael.j.wysocki@intel.com,
	tglx@linutronix.de, briannorris@chromium.org,
	marc.zyngier@arm.com, Derek Basehore <dbasehore@chromium.org>
Subject: [PATCH 0/8] GICv3 Save and Restore
Date: Fri, 12 Jan 2018 13:24:14 -0800	[thread overview]
Message-ID: <20180112212422.148625-1-dbasehore@chromium.org> (raw)

This patch set adds saving and restoring the GIC on v3
implementations through a devicetree flag.

The new CPU_PM state was the cleanest way to synchronize the save and
restore (that I figured out) with other PM operations since this isn't
going into any PSCI implementations (at least not in
ARM-Trusted-Firmware).

I've verified these patches on a Rockchip RK3399 platform (some
devicetree changes needed). This included turning off the power rail
for the GIC during suspend.

Derek Basehore (8):
  cpu_pm: add syscore_suspend error handling
  lib/iomap_copy: add __ioread64_copy()
  cpu_pm: Add SYSTEM_PM state
  irqchip/gic-v3: add ability to save/restore GIC/ITS state
  DT/arm,gic-v3: add save-suspend-state property
  irqchip/gic-v3-its: add ability to resend MAPC on resume
  DT/arm,gic-v3: add resend-mapc-on-resume property
  irqchip/gic-v3: add power down/up sequence

 .../bindings/interrupt-controller/arm,gic-v3.txt   |  43 +++
 drivers/irqchip/irq-gic-v3-its.c                   | 136 +++++--
 drivers/irqchip/irq-gic-v3.c                       | 391 ++++++++++++++++++++-
 include/linux/cpu_pm.h                             |  14 +
 include/linux/io.h                                 |   1 +
 include/linux/irqchip/arm-gic-v3.h                 |  26 ++
 kernel/cpu_pm.c                                    |  75 ++--
 lib/iomap_copy.c                                   |  26 ++
 8 files changed, 640 insertions(+), 72 deletions(-)

-- 
2.16.0.rc1.238.g530d649a79-goog

             reply	other threads:[~2018-01-12 21:24 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-12 21:24 Derek Basehore [this message]
2018-01-12 21:24 ` [PATCH 1/8] cpu_pm: add syscore_suspend error handling Derek Basehore
2018-01-12 22:07   ` Brian Norris
2018-01-12 21:24 ` [PATCH 2/8] lib/iomap_copy: add __ioread64_copy() Derek Basehore
2018-01-12 21:24 ` [PATCH 3/8] cpu_pm: Add SYSTEM_PM state Derek Basehore
2018-01-12 21:24 ` [PATCH 4/8] irqchip/gic-v3: add ability to save/restore GIC/ITS state Derek Basehore
2018-01-13 18:10   ` Marc Zyngier
2018-01-18 23:33     ` Brian Norris
2018-01-19  9:22       ` Marc Zyngier
2018-01-19 22:58         ` dbasehore .
2018-01-12 21:24 ` [PATCH 5/8] DT/arm,gic-v3: add save-suspend-state property Derek Basehore
2018-01-14 10:48   ` Marc Zyngier
2018-01-12 21:24 ` [PATCH 6/8] irqchip/gic-v3-its: add ability to resend MAPC on resume Derek Basehore
2018-01-14 10:56   ` Marc Zyngier
2018-01-25 23:07     ` dbasehore .
2018-01-12 21:24 ` [PATCH 7/8] DT/arm,gic-v3: add resend-mapc-on-resume property Derek Basehore
2018-01-12 21:24 ` [PATCH 8/8] irqchip/gic-v3: add power down/up sequence Derek Basehore
2018-01-14 11:04   ` Marc Zyngier

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=20180112212422.148625-1-dbasehore@chromium.org \
    --to=dbasehore@chromium.org \
    --cc=briannorris@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=marc.zyngier@arm.com \
    --cc=rafael.j.wysocki@intel.com \
    --cc=tglx@linutronix.de \
    /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).