[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <410989D2-7358-4285-8B1B-D6EA5403D313@linaro.org>
Date: Mon, 19 Aug 2024 08:09:30 +0700
From: Dmitry Baryshkov <dmitry.baryshkov@...aro.org>
To: Bjorn Andersson <quic_bjorande@...cinc.com>,
Sebastian Reichel <sre@...nel.org>, Bjorn Andersson <andersson@...nel.org>,
Konrad Dybcio <konrad.dybcio@...aro.org>,
Heikki Krogerus <heikki.krogerus@...ux.intel.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Neil Armstrong <neil.armstrong@...aro.org>
CC: Johan Hovold <johan+linaro@...nel.org>, Chris Lew <quic_clew@...cinc.com>,
Stephen Boyd <swboyd@...omium.org>, Amit Pundir <amit.pundir@...aro.org>,
linux-arm-msm@...r.kernel.org, linux-pm@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-usb@...r.kernel.org,
stable@...r.kernel.org
Subject: Re: [PATCH 3/3] soc: qcom: pmic_glink: Actually communicate with remote goes down
On 19 August 2024 06:17:39 GMT+07:00, Bjorn Andersson <quic_bjorande@...cinc.com> wrote:
>When the pmic_glink state is UP and we either receive a protection-
>domain (PD) notifcation indicating that the PD is going down, or that
>the whole remoteproc is going down, it's expected that the pmic_glink
>client instances are notified that their function has gone DOWN.
>
>This is not what the code does, which results in the client state either
>not updating, or being wrong in many cases. So let's fix the conditions.
>
>Fixes: 58ef4ece1e41 ("soc: qcom: pmic_glink: Introduce base PMIC GLINK driver")
>Cc: stable@...r.kernel.org
>Signed-off-by: Bjorn Andersson <quic_bjorande@...cinc.com>
>---
> drivers/soc/qcom/pmic_glink.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@...aro.org>
Powered by blists - more mailing lists