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 1/3] irqchip/gic-v3-its: add ability to save/restore ITS state
Date: Thu, 8 Feb 2018 09:55:12 -0800 [thread overview]
Message-ID: <20180208175511.GC106856@ban.mtv.corp.google.com> (raw)
In-Reply-To: <20180208023648.89124-2-dbasehore@chromium.org>
Hi Derek,
On Wed, Feb 07, 2018 at 06:36:46PM -0800, Derek Basehore wrote:
> Some platforms power off GIC logic in suspend, so we need to
> save/restore state. The distributor and redistributor registers need
> to be handled in platform code due to access permissions on those
> registers, but the ITS registers can be restored in the kernel.
>
> Signed-off-by: Derek Basehore <dbasehore@chromium.org>
> ---
> drivers/irqchip/irq-gic-v3-its.c | 103 +++++++++++++++++++++++++++++++++++++++
> 1 file changed, 103 insertions(+)
>
> diff --git a/drivers/irqchip/irq-gic-v3-its.c b/drivers/irqchip/irq-gic-v3-its.c
> index 06f025fd5726..35ad48f51dfa 100644
> --- a/drivers/irqchip/irq-gic-v3-its.c
> +++ b/drivers/irqchip/irq-gic-v3-its.c
> @@ -33,6 +33,7 @@
> #include <linux/of_platform.h>
> #include <linux/percpu.h>
> #include <linux/slab.h>
> +#include <linux/syscore_ops.h>
>
> #include <linux/irqchip.h>
> #include <linux/irqchip/arm-gic-v3.h>
> @@ -46,6 +47,7 @@
> #define ITS_FLAGS_CMDQ_NEEDS_FLUSHING (1ULL << 0)
> #define ITS_FLAGS_WORKAROUND_CAVIUM_22375 (1ULL << 1)
> #define ITS_FLAGS_WORKAROUND_CAVIUM_23144 (1ULL << 2)
> +#define ITS_FLAGS_SAVE_SUSPEND_STATE (1ULL << 3)
>
> #define RDIST_FLAGS_PROPBASE_NEEDS_FLUSHING (1 << 0)
>
> @@ -101,6 +103,8 @@ struct its_node {
> struct its_collection *collections;
> struct fwnode_handle *fwnode_handle;
> u64 (*get_msi_base)(struct its_device *its_dev);
> + u64 cbaser_save;
> + u32 ctlr_save;
> struct list_head its_device_list;
> u64 flags;
> unsigned long list_nr;
> @@ -3042,6 +3046,100 @@ static void its_enable_quirks(struct its_node *its)
> gic_enable_quirks(iidr, its_quirks, its);
> }
>
> +static int its_save_disable(void)
> +{
> + struct its_node *its;
> + int err = 0;
> +
> + spin_lock(&its_lock);
> + list_for_each_entry(its, &its_nodes, entry) {
> + void __iomem *base;
> +
> + if (!(its->flags & ITS_FLAGS_SAVE_SUSPEND_STATE))
> + continue;
> +
> + base = its->base;
> + its->ctlr_save = readl_relaxed(base + GITS_CTLR);
> + err = its_force_quiescent(base);
> + if (err) {
> + pr_err("ITS failed to quiesce\n");
Isn't this a case where it was suggested to print the PA? Also, printing
the error code never hurts. Like:
pr_err("ITS@%pa: failed to quiesce: %d\n",
&its->phys_base, err);
> + writel_relaxed(its->ctlr_save, base + GITS_CTLR);
> + goto err;
> + }
> +
> + its->cbaser_save = gits_read_cbaser(base + GITS_CBASER);
> + }
> +
> +err:
> + if (err) {
> + list_for_each_entry_continue_reverse(its, &its_nodes, entry) {
> + void __iomem *base;
> +
> + if (!(its->flags & ITS_FLAGS_SAVE_SUSPEND_STATE))
> + continue;
> +
> + base = its->base;
> + writel_relaxed(its->ctlr_save, base + GITS_CTLR);
> + }
> + }
> + spin_unlock(&its_lock);
> +
> + return err;
> +}
> +
> +static void its_restore_enable(void)
> +{
> + struct its_node *its;
> +
> + spin_lock(&its_lock);
> + list_for_each_entry(its, &its_nodes, entry) {
> + void __iomem *base;
> + int i;
> +
> + if (!(its->flags & ITS_FLAGS_SAVE_SUSPEND_STATE))
> + continue;
> +
> + base = its->base;
> +
> + /*
> + * Make sure that the ITS is disabled. If it fails to quiesce,
> + * don't restore it since writing to CBASER or BASER<n>
> + * registers is undefined according to the GIC v3 ITS
> + * Specification.
> + */
> + if (its_force_quiescent(base)) {
> + pr_err("ITS(%p): failed to quiesce on resume\n", base);
I think Marc was requesting the PA, not the VA. The VA isn't really very
useful. Also, might as well log with similar style to the existing logs
(ITS@xxx), and log the error code:
pr_err("ITS@%pa: failed to quiesce on resume: %d\n",
&its->phys_base, ret);
Brian
> + continue;
> + }
> +
> + gits_write_cbaser(its->cbaser_save, base + GITS_CBASER);
> +
> + /*
> + * Writing CBASER resets CREADR to 0, so make CWRITER and
> + * cmd_write line up with it.
> + */
> + its->cmd_write = its->cmd_base;
> + gits_write_cwriter(0, base + GITS_CWRITER);
> +
> + /* Restore GITS_BASER from the value cache. */
> + for (i = 0; i < GITS_BASER_NR_REGS; i++) {
> + struct its_baser *baser = &its->tables[i];
> +
> + if (!(baser->val & GITS_BASER_VALID))
> + continue;
> +
> + its_write_baser(its, baser, baser->val);
> + }
> + writel_relaxed(its->ctlr_save, base + GITS_CTLR);
> + }
> + spin_unlock(&its_lock);
> +}
> +
> +static struct syscore_ops its_syscore_ops = {
> + .suspend = its_save_disable,
> + .resume = its_restore_enable,
> +};
> +
> static int its_init_domain(struct fwnode_handle *handle, struct its_node *its)
> {
> struct irq_domain *inner_domain;
> @@ -3261,6 +3359,9 @@ static int __init its_probe_one(struct resource *res,
> ctlr |= GITS_CTLR_ImDe;
> writel_relaxed(ctlr, its->base + GITS_CTLR);
>
> + if (fwnode_property_present(handle, "reset-on-suspend"))
> + its->flags |= ITS_FLAGS_SAVE_SUSPEND_STATE;
> +
> err = its_init_domain(handle, its);
> if (err)
> goto out_free_tables;
> @@ -3515,5 +3616,7 @@ int __init its_init(struct fwnode_handle *handle, struct rdists *rdists,
> }
> }
>
> + register_syscore_ops(&its_syscore_ops);
> +
> return 0;
> }
> --
> 2.16.0.rc1.238.g530d649a79-goog
>
next prev parent reply other threads:[~2018-02-08 17:55 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 [this message]
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
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=20180208175511.GC106856@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®