In current UFS task abort hook, namely ufshcd_abort(), if one task is
aborted successfully, clk_gating.active_reqs held by this task is not
decreased, which makes clk_gating.active_reqs stay above zero forever,
thus clock gating would never happen. Instead of releasing resources of
one task "manual
Hi Markus,
On 2020-08-07 17:33, Markus Elfring wrote:
… To fix it, …
I propose to replace this wording by the tag “Fixes”.
… "mannually", …
Please avoid a typo:
… "manually", …
Regards,
Markus
Thanks, will fix these in next version.
Regards,
Can Guo.
In current UFS task abort hook, namely ufshcd_abort(), if a task is
aborted successfully, clock scaling busy time statistics is not updated
and, most important, clk_gating.active_reqs is not decreased, which makes
clk_gating.active_reqs stay above zero forever, thus clock gating would
never happen.
3 matches
Mail list logo