Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1625044
| Path | csiph.com!1.us.feeder.erje.net!feeder.erje.net!2.eu.feeder.erje.net!feeds.phibee-telecom.net!news.panservice.it!bofh.it!news.nic.it!robomod |
|---|---|
| From | Kishon Vijay Abraham I <kishon@ti.com> |
| Newsgroups | linux.kernel |
| Subject | [Query] Enabling parent device clock from resume_noirq |
| Date | Tue, 18 Apr 2017 08:10:02 +0200 |
| Message-ID | <txuuS-2Go-7@gated-at.bofh.it> (permalink) |
| Dkim-Signature | v=1; a=rsa-sha256; c=relaxed/simple; d=ti.com; s=ti-com-17Q1; t=1492495645; bh=aItzzXcqMDomVu9WUpwLefQ5FI2Pk1+cdgeVGmXNfdI=; h=From:Subject:To:Date; b=nWbB4PXwT/BIAkyJhy0WiuN+lkCxYYG7DhvtIKvD5Gr6/VJRidU+3gvsxIPiSADu3 cMMfbmPOm7hbQZivLUYa9sXh4jswK7f5TQcJf2IsutVlrNZCRzX4df3wHgC3Gxv+RA JmkwjGr7UkPe6xhGkx+Vp6kpXAtbSw2aoELRsKQ8= |
| User-Agent | Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0 |
| MIME-Version | 1.0 |
| Content-Type | text/plain; charset="utf-8" |
| Content-Transfer-Encoding | 7bit |
| Sender | robomod@news.nic.it |
| List-ID | <linux-kernel.vger.kernel.org> |
| X-Mailing-List | linux-kernel@vger.kernel.org |
| Approved | robomod@news.nic.it |
| Lines | 21 |
| Organization | linux.* mail to news gateway |
| X-Original-Date | Tue, 18 Apr 2017 11:37:20 +0530 |
| X-Original-Message-ID | <62cd5ee0-3f0c-5e65-5f64-0c91a2a6f1e6@ti.com> |
| X-Original-Sender | linux-kernel-owner@vger.kernel.org |
| Xref | csiph.com linux.kernel:1625044 |
Show key headers only | 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 | Next — Next in thread | Find similar | Unroll 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