summaryrefslogtreecommitdiff
path: root/net/Kconfig
diff options
context:
space:
mode:
authorJon Hunter <jonathanh@nvidia.com>2015-07-31 12:20:00 +0300
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2015-08-01 00:34:12 +0300
commit311fa6adf92c5110057daa439fdaff012864aa2b (patch)
tree3dabf647f606f7444c410d6441eafb840d7699d2 /net/Kconfig
parent885fb909dc17f9240ab3e3420f7f135ae82be01f (diff)
downloadlinux-311fa6adf92c5110057daa439fdaff012864aa2b.tar.xz
PM / Domains: Return -EPROBE_DEFER if we fail to init or turn-on domain
When a device is probed, the function dev_pm_domain_attach() is called to see if there is a power-domain that is associated with the device and needs to be turned on. If dev_pm_domain_attach() does not return -EPROBE_DEFER then the device will be probed. For devices using genpd, dev_pm_domain_attach() will call genpd_dev_pm_attach(). If genpd_dev_pm_attach() does not find a power domain associated with the device then it returns an error code not equal to -EPROBE_DEFER to allow the device to be probed. However, if genpd_dev_pm_attach() does find a power-domain that is associated with the device, then it does not return -EPROBE_DEFER on failure and hence the device will still be probed. Furthermore, genpd_dev_pm_attach() does not check the error code returned by pm_genpd_poweron() to see if the power-domain was turned on successfully. Fix this by checking the return code from pm_genpd_poweron() and returning -EPROBE_DEFER from genpd_dev_pm_attach on failure, if there is a power-domain associated with the device. Signed-off-by: Jon Hunter <jonathanh@nvidia.com> Acked-by: Ulf Hansson <ulf.hansson@linaro.org> Acked-by: Kevin Hilman <khilman@linaro.org> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'net/Kconfig')
0 files changed, 0 insertions, 0 deletions