Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1625044

[Query] Enabling parent device clock from resume_noirq

From Kishon Vijay Abraham I <kishon@ti.com>
Newsgroups linux.kernel
Subject [Query] Enabling parent device clock from resume_noirq
Date 2017-04-18 08:10 +0200
Message-ID <txuuS-2Go-7@gated-at.bofh.it> (permalink)
Organization linux.* mail to news gateway

Show all headers | View raw


Hi,

resume_noirq callbacks are used in PCIe core to restore PCI state (this
accesses PCI module). So the clocks of PCI module has to be enabled before
resume_noirq.

The clocks for the PCI module in DRA7xx is provided by PIPE3 PHY device which
in turn gets it's clock from OCP2SCP device. During resume_noirq callbacks,
pm_runtime is disabled, so pm_runtime_get_sync is ineffective. However
pm_runtime can be enabled using pm_runtime_force_resume. Now the problem is
adding pm_runtime_force_resume() in resume_noirq callback of pci-dra7xx driver
will enable only the pm_runtime of PCI device but not PIPE3 PHY or OCP2SCP.
Adding pm_runtime_force_resume() in resume_noirq callback of PIPE3 PHY driver
or OCP2SCP driver will not help if the resume_noirq callbacks in PIP3PHY driver
and OCP2SCP driver are invoked after the resume_noirq of pci-dra7xx driver.

How to enable the pm_runtime of parent devices in resume_noirq callback? Does
existing pm_runtime framework has support for that?

Thanks
Kishon

Back to linux.kernel | Previous | NextNext in thread | Find similar | Unroll thread


Thread

[Query] Enabling parent device clock from resume_noirq Kishon Vijay Abraham I <kishon@ti.com> - 2017-04-18 08:10 +0200
  Re: [Query] Enabling parent device clock from resume_noirq Grygorii Strashko <grygorii.strashko@ti.com> - 2017-04-18 22:10 +0200
    Re: [Query] Enabling parent device clock from resume_noirq Kishon Vijay Abraham I <kishon@ti.com> - 2017-04-19 13:20 +0200

csiph-web