summaryrefslogtreecommitdiff
path: root/drivers/clk/qcom/gdsc.c
diff options
context:
space:
mode:
authorMaxime Ripard <maxime@cerno.tech>2022-10-26 16:46:59 +0300
committerStephen Boyd <sboyd@kernel.org>2022-12-08 00:54:09 +0300
commit49e62e0d96baf7236615e4ec2878d8db229de9c2 (patch)
tree875f2ea0c077b1d71105c8e61a17d8cd6d1b9286 /drivers/clk/qcom/gdsc.c
parentef13f8b64728c4b4d28639bbcf30fe1314b18482 (diff)
downloadlinux-49e62e0d96baf7236615e4ec2878d8db229de9c2.tar.xz
clk: Add trace events for rate requests
It is currently fairly difficult to follow what clk_rate_request are issued, and how they have been modified once done. Indeed, there's multiple paths that can be taken, some functions are recursive and will just forward the request to its parent, etc. Adding a lot of debug prints is just not very convenient, so let's add trace events for the clock requests, one before they are submitted and one after they are returned. That way we can simply toggle the tracing on without modifying the kernel code and without affecting performances or the kernel logs too much. Reviewed-by: Steven Rostedt (Google) <rostedt@goodmis.org> Signed-off-by: Maxime Ripard <maxime@cerno.tech> Link: https://lore.kernel.org/r/20221018-clk-rate-request-tracing-v2-2-5170b363c413@cerno.tech Signed-off-by: Stephen Boyd <sboyd@kernel.org>
Diffstat (limited to 'drivers/clk/qcom/gdsc.c')
0 files changed, 0 insertions, 0 deletions