diff options
author | Miquel Raynal <miquel.raynal@bootlin.com> | 2019-06-27 14:52:43 +0200 |
---|---|---|
committer | Stephen Boyd <sboyd@kernel.org> | 2019-10-03 14:00:20 -0700 |
commit | e7ea59b6dc6ddb86dabf88c11cd6748da2313b37 (patch) | |
tree | b50339e4f31c4e1a2e58e3ee9a758cd9e0044881 /mm/slab_common.c | |
parent | 4d8fb4948472c976d0c6dcf3380f92332dd660c1 (diff) | |
download | linux-e7ea59b6dc6ddb86dabf88c11cd6748da2313b37.tar.gz linux-e7ea59b6dc6ddb86dabf88c11cd6748da2313b37.tar.bz2 linux-e7ea59b6dc6ddb86dabf88c11cd6748da2313b37.zip |
clk: mvebu: armada-37xx-periph: change suspend/resume time
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 registers 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.
The solution to support PCIe resume operation is to change the
"priority" of this clock driver PM callbacks to "_noirq()".
Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
Link: https://lkml.kernel.org/r/20190627125245.26788-3-miquel.raynal@bootlin.com
Signed-off-by: Stephen Boyd <sboyd@kernel.org>
Diffstat (limited to 'mm/slab_common.c')
0 files changed, 0 insertions, 0 deletions