summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python
diff options
context:
space:
mode:
authorStephan Gerhold <stephan.gerhold@kernkonzept.com>2022-07-06 16:41:29 +0300
committerBjorn Andersson <andersson@kernel.org>2022-09-14 06:07:25 +0300
commit2cb8a39b6781ea23accd1fa93b3ad000d0948aec (patch)
treeab1cf0bf231f01c96f543c8b99aabb4f2d91959c /tools/perf/scripts/python
parentbf37a05744ebc6a488e3cfd3ec6d502d626740cc (diff)
downloadlinux-2cb8a39b6781ea23accd1fa93b3ad000d0948aec.tar.xz
clk: qcom: reset: Allow specifying custom reset delay
The amount of time required between asserting and deasserting the reset signal can vary depending on the involved hardware component. Sometimes 1 us might not be enough and a larger delay is necessary to conform to the specifications. Usually this is worked around in the consuming drivers, by replacing reset_control_reset() with a sequence of reset_control_assert(), waiting for a custom delay, followed by reset_control_deassert(). However, in some cases the driver making use of the reset is generic and can be used with different reset controllers. In this case the reset time requirement is better handled directly by the reset controller driver. Make this possible by adding an "udelay" field to the qcom_reset_map that allows setting a different reset delay (in microseconds). Signed-off-by: Stephan Gerhold <stephan.gerhold@kernkonzept.com> Signed-off-by: Bjorn Andersson <andersson@kernel.org> Link: https://lore.kernel.org/r/20220706134132.3623415-4-stephan.gerhold@kernkonzept.com
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions