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 7/8] DT/arm,gic-v3: add resend-mapc-on-resume property
Date: Fri, 12 Jan 2018 13:24:21 -0800 [thread overview]
Message-ID: <20180112212422.148625-8-dbasehore@chromium.org> (raw)
In-Reply-To: <20180112212422.148625-1-dbasehore@chromium.org>
This boolean property for the GIC-V3-ITS enables resending the MAP
COLLECTIONS commands when restoring the GIC on resume.
Change-Id: I03ab8689dace109851a4d2be3abf5fbafb090d27
Signed-off-by: Derek Basehore <dbasehore@chromium.org>
---
.../devicetree/bindings/interrupt-controller/arm,gic-v3.txt | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/Documentation/devicetree/bindings/interrupt-controller/arm,gic-v3.txt b/Documentation/devicetree/bindings/interrupt-controller/arm,gic-v3.txt
index 820556a8ffd2..1f0d691df9b3 100644
--- a/Documentation/devicetree/bindings/interrupt-controller/arm,gic-v3.txt
+++ b/Documentation/devicetree/bindings/interrupt-controller/arm,gic-v3.txt
@@ -82,6 +82,12 @@ These nodes must have the following properties:
Optional:
- socionext,synquacer-pre-its: (u32, u32) tuple describing the untranslated
address and size of the pre-ITS window.
+- resend-mapc-on-resume : Bool property. If the collections for the ITS
+ are stored in the ITS instead of external memory, the state will be
+ lost if the GIC loses power. Setting this enables the kernel to
+ reset the collections state on resume for this ITS node. The state
+ will only be reset if the save-suspend-state boolean is set for the
+ gic.
The main GIC node must contain the appropriate #address-cells,
#size-cells and ranges properties for the reg property of all ITS
@@ -129,6 +135,7 @@ Examples:
its: interrupt-controller@fee20000 {
compatible = "arm,gic-v3-its";
msi-controller;
+ resend-mapc-on-resume;
reg = <0x0 0xfee20000 0x0 0x20000>;
};
--
2.16.0.rc1.238.g530d649a79-goog
next prev parent 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 [PATCH 0/8] GICv3 Save and Restore Derek Basehore
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 ` Derek Basehore [this message]
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-8-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).