aboutsummaryrefslogtreecommitdiffstats
path: root/tools/perf/scripts/python/event_analyzing_sample.py
diff options
context:
space:
mode:
authorJerome Brunet <[email protected]>2018-06-19 13:40:51 +0000
committerMichael Turquette <[email protected]>2018-06-19 17:03:38 +0000
commit9461f7b33d11cbbf5ce79c3c03d0da9d42dfce92 (patch)
tree5a595804ecd64012231e6304739ff7205ce80f27 /tools/perf/scripts/python/event_analyzing_sample.py
parentLinux 4.18-rc1 (diff)
downloadkernel-9461f7b33d11cbbf5ce79c3c03d0da9d42dfce92.tar.gz
kernel-9461f7b33d11cbbf5ce79c3c03d0da9d42dfce92.zip
clk: fix CLK_SET_RATE_GATE with clock rate protection
CLK_SET_RATE_GATE should prevent any operation which may result in a rate change or glitch while the clock is prepared/enabled. IOW, the following sequence is not allowed anymore with CLK_SET_RATE_GATE: * clk_get() * clk_prepare_enable() * clk_get_rate() * clk_set_rate() At the moment this is enforced on the leaf clock of the operation, not along the tree. This problematic because, if a PLL has the CLK_RATE_GATE, it won't be enforced if the clk_set_rate() is called on its child clocks. Using clock rate protection, we can now enforce CLK_SET_RATE_GATE along the clock tree Acked-by: Linus Walleij <[email protected]> Tested-by: Quentin Schulz <[email protected]> Tested-by: Maxime Ripard <[email protected]> Signed-off-by: Jerome Brunet <[email protected]> Signed-off-by: Michael Turquette <[email protected]> Link: lkml.kernel.org/r/[email protected]
Diffstat (limited to 'tools/perf/scripts/python/event_analyzing_sample.py')
0 files changed, 0 insertions, 0 deletions