[Ksummit-discuss] [TECH TOPIC] PM dependencies

[Laurent Pinchart]

Hello,

On modern systems many PM dependencies don't follow the Linux kernel device 
model based on parent-child relationships from a control bus point of view. 
For instance a GPU will need the IOMMU that services its memory requests to be 
powered on to perform DMA operations.

Ad-hoc solutions with subsystem-specific or even driver-specific APIs have 
been implemented (see omap_iommu_save_ctx and omap_iommu_restore_ctx in 
include/linux/omap-iommu.h for instance, that push the burden of saving and 
restoring the IOMMU registers to bus master drivers), but they make automatic 
handling of hardware resources difficult. In the IOMMU case again, the goal is 
to hide IOMMU handling inside the DMA mapping API and make its usage 
completely transparent to bus master drivers in most of the cases. An IOMMU-
specific API to explicitly control IOMMU power from the bus master driver 
would make that goal impossible to reach.

The problem is not limited to IOMMUs. We have similar dependencies at 
suspend/resume time with camera interfaces for instance, where two completely 
unrelated device in the Linux device hierarchy (a camera interface platform 
device in the SoC and an I2C camera sensor) need to be suspended and resumed 
in a controlled order. I'm sure many more use cases exist.

Whether we can (partly) reuse existing infrastructure for this is not clear. 
I'd like to gather use cases, to first find out exactly how widespread the 
need is, and whether we can come up with a common solution or we are really 
faced with different classes of similarly looking but distinct issues.

Tomasz Figa (CC'ed) has recently expressed interest for this topic, if he's 
still interested I'd like to nominate him.

-- 
Regards,

Laurent Pinchart