Ulf Hansson <ulf.hansson@xxxxxxxxxx> writes: > Changes in v3: > -Rework the entire intermediate step which was suggested in v2. > That means solving the race condition, but also cope with PM domains > that are initialized in powered off state. > > Changes in v2: > -Added some acks. > -Updated commit messages. > -Included a wider audience of the patchset. V1 was lacking SoC > maintainers. > > Here are link to the first patchset, were some discussion started. > http://marc.info/?l=linux-pm&m=141208104729597&w=2 > > There may be more than one device in a PM domain which then will be > probed at different points in time. > > Depending on timing and runtime PM support, in for the device related > driver/subsystem, a PM domain may be advised to power off after a > successful probe sequence. > > A general requirement for a device within a PM domain, is that the > PM domain must stay powered during the probe sequence. To cope with > such requirement, let's add two new APIs, dev_pm_domain_get|put(). > > These APIs are intended to be invoked from subsystem-level code and the > calls between get/put needs to be balanced. > > dev_pm_domain_get(), tells the PM domain that it needs to increase a > usage count and to keep supplying power. dev_pm_domain_put(), does the > opposite. I'm confused. Why arent' pm_runtime_get*() and pm_runtime_put*() working? What's not explained here (or what I'm not understanding) is why a PM domain is powering off if it has active devices. Kevin -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
 |