diff options
| author | Sudeep Holla <[email protected]> | 2022-04-28 13:29:13 +0100 |
|---|---|---|
| committer | Sudeep Holla <[email protected]> | 2022-04-28 18:22:52 +0100 |
| commit | 7ad6b6ccbafc1faa04ca9d26635bdd5e3e240a69 (patch) | |
| tree | 7679b54b5f5252d8e9f61f69223df2c9341620a4 /tools/perf/scripts/python/exported-sql-viewer.py | |
| parent | b260fccaebdc2c838e62aaef24fedf497f181d10 (diff) | |
firmware: arm_scmi: Set clock latency to U32_MAX if it is not supported
As per the spec, the clock_enable_delay is the worst case latency
incurred by the platform to enable the clock. The value of 0 indicates
that the platform doesn't support the same and must be considered as
maximum latency for practical purposes.
Currently the value of 0 is assigned as is and is propogated to the clock
framework which can assume that the clock can support atomic enable operation.
Link: https://lore.kernel.org/r/[email protected]
Fixes: 18f295b758b2 ("firmware: arm_scmi: Add support for clock_enable_latency")
Signed-off-by: Sudeep Holla <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/exported-sql-viewer.py')
0 files changed, 0 insertions, 0 deletions