iommu/arm-smmu: Add runtime pm/sleep support
Get series with b4
b4 am [email protected]Versions newest first
- v3 Latest0 of 5 patches 0 repliesNew
Patches in v3 No applies recorded yet
None of the 5 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/5] iommu/arm-smmu: Add runtime pm/sleep support
Quoted 16 lines · Will Deacon
Quoted 15 lines · Rob Clark
Quoted 13 lines · Will Deacon
Quoted 5 lines · Sricharan R
This series provides the support for turning on the arm-smmu's clocks/power domains using runtime pm. This is done using the recently introduced device links patches, which lets the symmu's runtime to follow the master's runtime pm, so the smmu remains powered only when the masters use it.
Do you have any numbers for the power savings you achieve with this? How often do we actually manage to stop the SMMU clocks on an SoC with a handful of masters?
In other words, is this too coarse-grained to be useful, or is it common that all the devices upstream of the SMMU are suspended?
Quoted 6 lines
Quoted 2 lines
well, if you think about a phone/tablet with a command mode panel, pretty much all devices will be suspended most of the time ;-)
Well, that's really what I was asking about. I assumed that periodic modem/radio transactions would keep the SMMU clocked, so would like to get a rough idea of the power savings achieved with this coarse-grained approach.
Sometimes we distribute SMMUs to each IP block in the system and let each one of those live in their own clock + power domain. In these cases, the SMMU can be powered down along with the only IP block that uses it. Furthermore, sometimes we put the IP block and the SMMU inside the same power domain to really tie the two together, so we definitely have cases where all devices (device?) upstream of the SMMU are suspended. And in the case of multimedia, it could be very often that something like the camera app isn't open and thus the SMMU dedicated for the camera can be powered down.
Other times we have two SMMUs in the system where one is dedicated to GPU and the other is "everything else". Even in these cases, we can suspend the GPU one when the GPU is inactive because it's the only consumer. The other SMMU might not be as fine grained, but I think we still power it down quite often because the consumers are mostly multimedia devices that aren't active when the display is off.
Signature · 2 lines
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project