From: Marc Zyngier <marc.zyngier@arm.com>
To: Derek Basehore <dbasehore@chromium.org>, linux-kernel@vger.kernel.org
Cc: Soby.Mathew@arm.com, sudeep.holla@arm.com,
devicetree@vger.kernel.org, robh+dt@kernel.org,
mark.rutland@arm.com, linux-pm@vger.kernel.org,
rafael.j.wysocki@intel.com, tglx@linutronix.de,
briannorris@chromium.org
Subject: Re: [PATCH v5 3/4] DT/arm,gic-v3-its: add reset-on-suspend property
Date: Wed, 7 Feb 2018 09:21:59 +0000 [thread overview]
Message-ID: <b4c7bc62-6861-3851-513e-be8d7a440c91@arm.com> (raw)
In-Reply-To: <20180207014117.62611-4-dbasehore@chromium.org>
On 07/02/18 01:41, Derek Basehore wrote:
> This adds documentation for the new reset-on-suspend property. This
> property enables saving and restoring the ITS for when it loses state
> in system suspend.
>
> Signed-off-by: Derek Basehore <dbasehore@chromium.org>
> ---
> Documentation/devicetree/bindings/interrupt-controller/arm,gic-v3.txt | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/interrupt-controller/arm,gic-v3.txt b/Documentation/devicetree/bindings/interrupt-controller/arm,gic-v3.txt
> index 0a57f2f4167d..a470147d4f14 100644
> --- a/Documentation/devicetree/bindings/interrupt-controller/arm,gic-v3.txt
> +++ b/Documentation/devicetree/bindings/interrupt-controller/arm,gic-v3.txt
> @@ -78,6 +78,9 @@ 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.
> +- reset-on-suspend: Boolean property. Indicates that the ITS state is
> + reset on suspend. The state is then saved on suspend and restored on
> + resume.
By whom? It is important to be clear about the respective
responsibilities, as this forms a binding contract between firmware and OS.
Mark: Can you have a look at how to formulate this? I'm not sure we have
other instances of a non-architected behaviour involving FW
participation, aside from PSCI.
>
> The main GIC node must contain the appropriate #address-cells,
> #size-cells and ranges properties for the reg property of all ITS
>
Thanks,
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2018-02-07 9:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-07 1:41 [PATCH v5 0/5] GICv3 Save and Restore Derek Basehore
2018-02-07 1:41 ` [PATCH v5 1/4] cpu_pm: add syscore_suspend error handling Derek Basehore
2018-02-07 8:57 ` Marc Zyngier
2018-02-07 22:01 ` Brian Norris
2018-02-07 22:10 ` Marc Zyngier
2018-02-07 1:41 ` [PATCH v5 2/4] irqchip/gic-v3-its: add ability to save/restore ITS state Derek Basehore
2018-02-07 9:18 ` Marc Zyngier
2018-02-07 1:41 ` [PATCH v5 3/4] DT/arm,gic-v3-its: add reset-on-suspend property Derek Basehore
2018-02-07 9:21 ` Marc Zyngier [this message]
2018-02-08 2:59 ` dbasehore .
2018-02-07 1:41 ` [PATCH v5 4/4] irqchip/gic-v3-its: add ability to resend MAPC on resume Derek Basehore
2018-02-07 8:46 ` Marc Zyngier
2018-02-07 23:22 ` Brian Norris
2018-02-08 0:00 ` dbasehore .
2018-02-08 9:08 ` 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=b4c7bc62-6861-3851-513e-be8d7a440c91@arm.com \
--to=marc.zyngier@arm.com \
--cc=Soby.Mathew@arm.com \
--cc=briannorris@chromium.org \
--cc=dbasehore@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=rafael.j.wysocki@intel.com \
--cc=robh+dt@kernel.org \
--cc=sudeep.holla@arm.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