PM / Domains: Fix race conditions during boot
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v3 Latest posting 2/20 of 9 patches 0 repliesNew
- v3 posting 1/20 of 9 patches 0 repliesSuperseded
Patches in v3 posting 2/2 No applies recorded yet
None of the 9 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v3 yet.
Cover letter [PATCH v3 0/9] PM / Domains: Fix race conditions during boot
Quoted 14 lines · Kevin Hilman
Quoted 4 lines · Mark Brown
Quoted 1 line · Kevin Hilman
I'm confused. Why arent' pm_runtime_get*() and pm_runtime_put*() working?
Quoted 8 lines
Quoted 2 lines
What's not explained here (or what I'm not understanding) is why a PM domain is powering off if it has active devices.
The issue AIUI is what happens during system boot - if one device in a domain probes and marks itself runtime idle then that will trigger domain powerdown even if there is another device in the domain that hasn't yet been probed. This can cause undesirable glitches (or worse) during boot depending on what's getting powered down.
Quoted 5 lines
I'm not quite seeing how this series fixes that problem.
Looking at platform devices in PATCH 4/9, the new
_get()and_put()are still happening around ->probe(), so if a platform device runtime suspends after probe, don't we still have a PM domain that can turn off?
Yeah, I haven't actually reviewed the series so I don't know if it does
the above but that was my understanding of the intention.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20141030/54f67faa/attachment-0001.sig>