From: Brian Norris <briannorris@chromium.org>
To: Derek Basehore <dbasehore@chromium.org>
Cc: linux-kernel@vger.kernel.org, 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, marc.zyngier@arm.com
Subject: Re: [PATCH v6 3/3] irqchip/gic-v3-its: add ability to resend MAPC on resume
Date: Thu, 8 Feb 2018 10:02:04 -0800 [thread overview]
Message-ID: <20180208180203.GD106856@ban.mtv.corp.google.com> (raw)
In-Reply-To: <20180208023648.89124-4-dbasehore@chromium.org>
On Wed, Feb 07, 2018 at 06:36:48PM -0800, Derek Basehore wrote:
> This adds functionality to resend the MAPC command to an ITS node on
> resume. If the ITS is powered down during suspend and the collections
> are not backed by memory, the ITS will lose that state. This just sets
> up the known state for the collections after the ITS is restored.
>
> This is enabled via the reset-on-suspend flag in the DTS. It only runs
> for collections stored in the ITS itself.
>
> Signed-off-by: Derek Basehore <dbasehore@chromium.org>
> ---
> drivers/irqchip/irq-gic-v3-its.c | 86 +++++++++++++++++++++-----------------
> include/linux/irqchip/arm-gic-v3.h | 1 +
> 2 files changed, 49 insertions(+), 38 deletions(-)
For the very little it's worth:
Reviewed-by: Brian Norris <briannorris@chromium.org>
prev parent reply other threads:[~2018-02-08 18:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-08 2:36 [PATCH v6 0/3] GICv3 Save and Restore Derek Basehore
2018-02-08 2:36 ` [PATCH v6 1/3] irqchip/gic-v3-its: add ability to save/restore ITS state Derek Basehore
2018-02-08 17:55 ` Brian Norris
2018-02-08 2:36 ` [PATCH v6 2/3] DT/arm,gic-v3-its: add reset-on-suspend property Derek Basehore
2018-02-08 13:46 ` Mark Rutland
2018-02-08 2:36 ` [PATCH v6 3/3] irqchip/gic-v3-its: add ability to resend MAPC on resume Derek Basehore
2018-02-08 18:02 ` Brian Norris [this message]
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=20180208180203.GD106856@ban.mtv.corp.google.com \
--to=briannorris@chromium.org \
--cc=Soby.Mathew@arm.com \
--cc=dbasehore@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--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
all inboxes | Powered by JetHome®