Hi Cédric, On Tue, Sep 22, 2026 at 09:39:12PM +0200, Cédric Bellegarde wrote: > When a sensor's fwnode references an ancillary lens or flash device > (e.g. via the "lens-focus" or "flash-leds" properties), > v4l2_async_create_ancillary_links() already creates a media controller > link between the two entities, but their runtime PM states remain > independent. > > This is a problem for devices such as VCM lens actuators, which are > typically spring-loaded: holding a position away from the spring's > rest point requires continuous power, and the position is not retained > once power is cut. If such an actuator is allowed to runtime-suspend > independently of the sensor, the lens can drift back to its rest > position during an otherwise active capture session. > > Add V4L2_SUBDEV_FL_PM_LINK to allow an ancillary subdevice to request > that its runtime PM state be linked to the associated sensor.
Interesting idea. The IPU bridge has created such a device link between the VCM and the sensor as on some ACPI systems the VCM is in fact relying on the power resources of the sensor. But to do this everywhere? VCMs traditionally have been powered through opening their sub-device node and that hasn't been exactly neat API-wise. It has been practical still, AFAIK, as in order to control the VCM, you have to have a sub-device node open. This change also does mean that if the sensor is powered, even for always-on use cases that generally consume very little power, the VCM is powered on as well. VCMs still typically consume very little power if the current is configured to zero. Maybe this won't be an issue? Backtracking from such a change wouldn't be simple, and might not be possible at all. There wouldn't be a need for a sub-device flag and this would be done for all VCMs based on the ancillary link. I wonder what others think. Cc Laurent and Hans as well. -- Kind regards, Sakari Ailus
