diff options
| author | Mauro Carvalho Chehab <[email protected]> | 2021-04-23 17:19:21 +0200 |
|---|---|---|
| committer | Mauro Carvalho Chehab <[email protected]> | 2021-05-10 11:36:34 +0200 |
| commit | c44eac5b72e23c31eefc0e10a71d9650036b8341 (patch) | |
| tree | a9a7c97e61a28cd2e257993808139d83ea1a66b6 /tools/perf/scripts/python/flamegraph.py | |
| parent | 9c298f82d8392f799a0595f50076afa1d91e9092 (diff) | |
media: sti/bdisp: fix pm_runtime_get_sync() usage count
The pm_runtime_get_sync() internally increments the
dev->power.usage_count without decrementing it, even on errors.
The bdisp_start_streaming() doesn't take it into account, which
would unbalance PM usage counter at bdisp_stop_streaming().
The logic at bdisp_probe() is correct, but the best is to use
the same call along the driver.
So, replace it by the new pm_runtime_resume_and_get(), introduced by:
commit dd8088d5a896 ("PM: runtime: Add pm_runtime_resume_and_get to deal with usage counter")
in order to properly decrement the usage counter, avoiding
a potential PM usage counter leak.
Reviewed-by: Jonathan Cameron <[email protected]>
Signed-off-by: Mauro Carvalho Chehab <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/flamegraph.py')
0 files changed, 0 insertions, 0 deletions