diff options
| author | Maxime Ripard <[email protected]> | 2022-08-16 11:25:10 +0000 |
|---|---|---|
| committer | Stephen Boyd <[email protected]> | 2022-09-15 16:30:34 +0000 |
| commit | bde8870cd8c3a3913ddbc19f8422a21828e14d99 (patch) | |
| tree | 0f05db773dab6a4d60746cb3aaf6ac36f3ceb7e5 /tools/perf/util/scripting-engines/trace-event-perl.c | |
| parent | clk: Mention that .recalc_rate can return 0 on error (diff) | |
| download | kernel-bde8870cd8c3a3913ddbc19f8422a21828e14d99.tar.gz kernel-bde8870cd8c3a3913ddbc19f8422a21828e14d99.zip | |
clk: Clarify clk_get_rate() expectations
As shown by a number of clock users already, clk_get_rate() can be
called whether or not the clock is enabled.
Similarly, a number of clock drivers will return a rate of 0 whenever
the rate cannot be figured out.
Since it was a bit ambiguous before, let's make it clear in the
clk_get_rate() documentation.
Signed-off-by: Maxime Ripard <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Tested-by: Linux Kernel Functional Testing <[email protected]>
Tested-by: Naresh Kamboju <[email protected]>
Signed-off-by: Stephen Boyd <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-perl.c')
0 files changed, 0 insertions, 0 deletions
