Messages in this thread | | | From | Sudeep Holla <> | Subject | Re: [PATCH] firmware: arm_scmi: Set clock latency to U32_MAX if it is not supported | Date | Tue, 3 May 2022 09:04:45 +0100 |
| |
On Thu, 28 Apr 2022 13:29:13 +0100, Sudeep Holla wrote: > As per the spec, the clock_enable_delay is the worst case latency > incurred by the platform to enable the clock. The value of 0 indicates > that the platform doesn't support the same and must be considered as > maximum latency for practical purposes. > > Currently the value of 0 is assigned as is and is propogated to the clock > framework which can assume that the clock can support atomic enable operation. > > [...]
Applied to sudeep.holla/linux (for-next/scmi), thanks!
[1/1] firmware: arm_scmi: Set clock latency to U32_MAX if it is not supported https://git.kernel.org/sudeep.holla/c/7ad6b6ccba
-- Regards, Sudeep
| |