From: Stephen Boyd <sboyd@kernel.org> To: Mark Rutland <mark.rutland@arm.com>, Michael Turquette <mturquette@baylibre.com>, Miquel Raynal <miquel.raynal@bootlin.com>, Rob Herring <robh+dt@kernel.org> Cc: linux-clk@vger.kernel.org, devicetree@vger.kernel.org, Thomas Petazzoni <thomas.petazzoni@bootlin.com>, Antoine Tenart <antoine.tenart@bootlin.com>, Gregory Clement <gregory.clement@bootlin.com>, Maxime Chevallier <maxime.chevallier@bootlin.com>, Nadav Haklai <nadavh@marvell.com> Subject: Re: [PATCH 2/4] clk: mvebu: armada-37xx-periph: change suspend/resume time Date: Thu, 29 Nov 2018 16:37:58 -0800 [thread overview] Message-ID: <154353827849.88331.12767996548874447262@swboyd.mtv.corp.google.com> (raw) In-Reply-To: <20181123094444.27956-3-miquel.raynal@bootlin.com> Quoting Miquel Raynal (2018-11-23 01:44:41) > Armada 3700 PCIe IP relies on the PCIe clock managed by this > driver. For reasons related to the PCI core's organization when > suspending/resuming, PCI host controller drivers must reconfigure > their register at suspend_noirq()/resume_noirq() which happens after > suspend()/suspend_late() and before resume_early()/resume(). > > Device link support in the clock framework enforce that the clock > driver's resume() callback will be called before the PCIe > driver's. But, any resume_noirq() callback will be called before all > the registered resume() callbacks. I thought any device driver that provides something to another device driver will implicitly be probed before the driver that consumes said resources. And we actually reorder the dpm list on probe defer so that the order of devices is correct. Is it more that we want to parallelize suspend/resume of the PCIe chip so we need to have device links so that we know the dependency of the PCIe driver on the clock driver? > > The solution to support PCIe resume operation is to change the > "priority" of this clock driver PM callbacks to "_noirq()". This seems sad that the PM core can't "priority boost" any suspend/resume callbacks of a device that doesn't have noirq callbacks when a device that depends on it from the device link perspective does have noirq callbacks. And why does the PCIe device need to use noirq callbacks in general? I'm just saying this seems like a more fundamental problem with ordering of provider and consumer suspend/resume functions that isn't being solved in this patch. In fact, it's quite the opposite, this is working around the problem.
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Boyd <sboyd@kernel.org> To: Mark Rutland <mark.rutland@arm.com>, Michael Turquette <mturquette@baylibre.com>, Miquel Raynal <miquel.raynal@bootlin.com>, Rob Herring <robh+dt@kernel.org> Cc: linux-clk@vger.kernel.org, devicetree@vger.kernel.org, Thomas Petazzoni <thomas.petazzoni@bootlin.com>, Antoine Tenart <antoine.tenart@bootlin.com>, Gregory Clement <gregory.clement@bootlin.com>, Maxime Chevallier <maxime.chevallier@bootlin.com>, Nadav Haklai <nadavh@marvell.com>, Miquel Raynal <miquel.raynal@bootlin.com> Subject: Re: [PATCH 2/4] clk: mvebu: armada-37xx-periph: change suspend/resume time Date: Thu, 29 Nov 2018 16:37:58 -0800 [thread overview] Message-ID: <154353827849.88331.12767996548874447262@swboyd.mtv.corp.google.com> (raw) In-Reply-To: <20181123094444.27956-3-miquel.raynal@bootlin.com> Quoting Miquel Raynal (2018-11-23 01:44:41) > Armada 3700 PCIe IP relies on the PCIe clock managed by this > driver. For reasons related to the PCI core's organization when > suspending/resuming, PCI host controller drivers must reconfigure > their register at suspend_noirq()/resume_noirq() which happens after > suspend()/suspend_late() and before resume_early()/resume(). > > Device link support in the clock framework enforce that the clock > driver's resume() callback will be called before the PCIe > driver's. But, any resume_noirq() callback will be called before all > the registered resume() callbacks. I thought any device driver that provides something to another device driver will implicitly be probed before the driver that consumes said resources. And we actually reorder the dpm list on probe defer so that the order of devices is correct. Is it more that we want to parallelize suspend/resume of the PCIe chip so we need to have device links so that we know the dependency of the PCIe driver on the clock driver? > > The solution to support PCIe resume operation is to change the > "priority" of this clock driver PM callbacks to "_noirq()". This seems sad that the PM core can't "priority boost" any suspend/resume callbacks of a device that doesn't have noirq callbacks when a device that depends on it from the device link perspective does have noirq callbacks. And why does the PCIe device need to use noirq callbacks in general? I'm just saying this seems like a more fundamental problem with ordering of provider and consumer suspend/resume functions that isn't being solved in this patch. In fact, it's quite the opposite, this is working around the problem.
next prev parent reply other threads:[~2018-11-30 0:37 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-11-23 9:44 [PATCH 0/4] Prepare Armada 3700 PCIe suspend to RAM support Miquel Raynal 2018-11-23 9:44 ` [PATCH 1/4] clk: mvebu: armada-37xx-periph: add PCIe gated clock Miquel Raynal 2018-11-23 9:44 ` [PATCH 2/4] clk: mvebu: armada-37xx-periph: change suspend/resume time Miquel Raynal 2018-11-30 0:37 ` Stephen Boyd [this message] 2018-11-30 0:37 ` Stephen Boyd 2018-11-30 10:58 ` Miquel Raynal 2018-12-12 21:59 ` Bjorn Helgaas 2019-01-11 13:44 ` Miquel Raynal 2018-11-23 9:44 ` [PATCH 3/4] dt-bindings: clk: armada3700: fix typo in SoC name Miquel Raynal 2018-12-11 21:35 ` Rob Herring 2018-12-11 21:35 ` Rob Herring 2018-11-23 9:44 ` [PATCH 4/4] dt-bindings: clk: armada3700: document the PCIe clock Miquel Raynal 2018-12-11 21:36 ` Rob Herring 2018-12-11 21:36 ` Rob Herring 2019-02-25 15:05 ` [PATCH 0/4] Prepare Armada 3700 PCIe suspend to RAM support Miquel Raynal
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=154353827849.88331.12767996548874447262@swboyd.mtv.corp.google.com \ --to=sboyd@kernel.org \ --cc=antoine.tenart@bootlin.com \ --cc=devicetree@vger.kernel.org \ --cc=gregory.clement@bootlin.com \ --cc=linux-clk@vger.kernel.org \ --cc=mark.rutland@arm.com \ --cc=maxime.chevallier@bootlin.com \ --cc=miquel.raynal@bootlin.com \ --cc=mturquette@baylibre.com \ --cc=nadavh@marvell.com \ --cc=robh+dt@kernel.org \ --cc=thomas.petazzoni@bootlin.com \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.