diff options
author | 2025-01-23 19:56:36 +0000 | |
---|---|---|
committer | 2025-03-11 13:23:24 +0000 | |
commit | 0a679336dc171db06d84679ae9180e5cda42166c (patch) | |
tree | 6d7ceeb8414daa5d41d62271a72e46d1359f8f57 /scripts/generate_rust_analyzer.py | |
parent | Linux 6.14-rc3 (diff) | |
download | linux-rng-0a679336dc171db06d84679ae9180e5cda42166c.tar.xz linux-rng-0a679336dc171db06d84679ae9180e5cda42166c.zip |
iommu/arm-smmu: Set rpm auto_suspend once during probe
The current code calls arm_smmu_rpm_use_autosuspend() during device
attach, which seems unusual as it sets the autosuspend delay and the
'use_autosuspend' flag for the smmu device. These parameters can be
simply set once during the smmu probe and in order to avoid bouncing
rpm states, we can simply mark_last_busy() during a client dev attach
as discussed in [1].
Move the handling of arm_smmu_rpm_use_autosuspend() to the SMMU probe
and modify the arm_smmu_rpm_put() function to mark_last_busy() before
calling __pm_runtime_put_autosuspend(). Additionally,
s/pm_runtime_put_autosuspend/__pm_runtime_put_autosuspend/ to help with
the refactor of the pm_runtime_put_autosuspend() API [2].
Link: https://lore.kernel.org/r/20241023164835.GF29251@willie-the-truck [1]
Link: https://git.kernel.org/linus/b7d46644e554 [2]
Signed-off-by: Pranjal Shrivastava <praan@google.com>
Link: https://lore.kernel.org/r/20250123195636.4182099-1-praan@google.com
Signed-off-by: Will Deacon <will@kernel.org>
Diffstat (limited to 'scripts/generate_rust_analyzer.py')
0 files changed, 0 insertions, 0 deletions