diff options
| author | Sudeep Holla <sudeep.holla@arm.com> | 2019-07-08 15:42:16 +0200 |
|---|---|---|
| committer | Sudeep Holla <sudeep.holla@arm.com> | 2019-08-12 13:23:01 +0200 |
| commit | 2bc06ffa0635e99cd4d88d6f6fe5bb4e4b9e50f1 (patch) | |
| tree | e6425ca7b776f7ceb74b7838bd37f802e1efb177 /drivers/of/unittest-data/overlay_0.dts | |
| parent | firmware: arm_scmi: Drop config flag in clk_ops->rate_set (diff) | |
| download | linux-2bc06ffa0635e99cd4d88d6f6fe5bb4e4b9e50f1.tar.xz linux-2bc06ffa0635e99cd4d88d6f6fe5bb4e4b9e50f1.zip | |
firmware: arm_scmi: Use asynchronous CLOCK_RATE_SET when possible
CLOCK_PROTOCOL_ATTRIBUTES provides attributes to indicate the maximum
number of pending asynchronous clock rate changes supported by the
platform. If it's non-zero, then we should be able to use asynchronous
clock rate set for any clocks until the maximum limit is reached.
Tracking the current count of pending asynchronous clock set rate
requests, we can decide if the incoming/new request for clock set rate
can be handled asynchronously or not until the maximum limit is
reached.
Cc: linux-clk@vger.kernel.org
Reviewed-by: Stephen Boyd <sboyd@kernel.org>
Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
Diffstat (limited to 'drivers/of/unittest-data/overlay_0.dts')
0 files changed, 0 insertions, 0 deletions