Re: [PATCH v3] clk: qcom: gdsc: Remove direct runtime PM calls

From: Stephen Boyd
Date: Fri Nov 04 2022 - 15:19:25 EST

Next message: kernel test robot: "arch/arm64/kvm/hyp/nvhe/stacktrace.c:15:1: sparse: sparse: symbol '__pcpu_scope_kvm_stacktrace_info' was not declared. Should it be static?"
Previous message: Stephen Boyd: "Re: [PATCH v2] dt-bindings: clock: qcom,sdm845-lpasscc: convert to dtschema"
In reply to: Johan Hovold: "Re: [PATCH v3] clk: qcom: gdsc: Remove direct runtime PM calls"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Quoting Stephen Boyd (2022-11-03 11:30:30)
> We shouldn't be calling runtime PM APIs from within the genpd
> enable/disable path for a couple reasons.
>
> First, this causes an AA lockdep splat[1] because genpd can call into
> genpd code again while holding the genpd lock.
>
> WARNING: possible recursive locking detected
> 5.19.0-rc2-lockdep+ #7 Not tainted

Applied to clk-fixes

Next message: kernel test robot: "arch/arm64/kvm/hyp/nvhe/stacktrace.c:15:1: sparse: sparse: symbol '__pcpu_scope_kvm_stacktrace_info' was not declared. Should it be static?"
Previous message: Stephen Boyd: "Re: [PATCH v2] dt-bindings: clock: qcom,sdm845-lpasscc: convert to dtschema"
In reply to: Johan Hovold: "Re: [PATCH v3] clk: qcom: gdsc: Remove direct runtime PM calls"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]