[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YUpXXjpM4kwH0pTC@robh.at.kernel.org>
Date: Tue, 21 Sep 2021 17:06:22 -0500
From: Rob Herring <robh@...nel.org>
To: Sibi Sankar <sibis@...eaurora.org>
Cc: rjw@...ysocki.net, sidgup@...eaurora.org, ohad@...ery.com,
agross@...nel.org, linux-kernel@...r.kernel.org,
bjorn.andersson@...aro.org, mathieu.poirier@...aro.org,
mka@...omium.org, swboyd@...omium.org, devicetree@...r.kernel.org,
dianders@...omium.org, robh+dt@...nel.org,
linux-remoteproc@...r.kernel.org, rishabhb@...eaurora.org,
linux-arm-msm@...r.kernel.org, ulf.hansson@...aro.org
Subject: Re: [PATCH v7 02/13] dt-bindings: remoteproc: qcom: pas: Add QMP
property
On Thu, 16 Sep 2021 19:29:19 +0530, Sibi Sankar wrote:
> The load state power-domain, used by the co-processors to notify the
> Always on Subsystem (AOSS) that a particular co-processor is up/down,
> suffers from the side-effect of changing states during suspend/resume.
> However the co-processors enter low-power modes independent to that of
> the application processor and their states are expected to remain
> unaltered across system suspend/resume cycles. To achieve this behavior
> let's drop the load state power-domain and replace them with the qmp
> property for all SoCs supporting low power mode signalling.
>
> Due to the current broken load state implementation, we can afford the
> binding breakage that ensues and the remoteproc functionality will remain
> the same when using newer kernels with older dtbs.
>
> Signed-off-by: Sibi Sankar <sibis@...eaurora.org>
> Reviewed-by: Stephen Boyd <swboyd@...omium.org>
> ---
>
> v7:
> * Set "qcom,qmp" property to false for unsupported devices. [Rob]
>
> .../devicetree/bindings/remoteproc/qcom,adsp.yaml | 54 ++++++++++------------
> 1 file changed, 24 insertions(+), 30 deletions(-)
>
Reviewed-by: Rob Herring <robh@...nel.org>
Powered by blists - more mailing lists