On 10/09/2024 13:06, Laurent Pinchart wrote:
Unrelated, but I am wrong the driver core calls pm_request_idle() on
the just probed device ? Does this mean drivers doesn't have to do
that by themseleves ? (it's not a big deal, as request_idle() doesn't
change the usage counter)
Seems like that. This could be omitted from drivers then.
Is that guaranteed, or is it an implementation detail that could change
at any time ?
The runtime_pm.rst says:
It may be desirable to suspend the device once ->probe() has finished.
Therefore the driver core uses the asynchronous pm_request_idle() to submit a
request to execute the subsystem-level idle callback for the device at that
time. A driver that makes use of the runtime autosuspend feature may want to
update the last busy mark before returning from ->probe().
But I can't find any mention of the dependencies (parent, suppliers)
being powered up automatically for probe.
Tomi
