[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <722c57dc-98cf-4ec8-93c5-aef55e6084c7@linaro.org>
Date: Tue, 21 May 2024 19:38:03 +0200
From: Konrad Dybcio <konrad.dybcio@...aro.org>
To: Chris Lew <quic_clew@...cinc.com>, Bjorn Andersson
<andersson@...nel.org>, Baolin Wang <baolin.wang@...ux.alibaba.com>,
Peter Zijlstra <peterz@...radead.org>, Ingo Molnar <mingo@...hat.com>,
Will Deacon <will@...nel.org>, Waiman Long <longman@...hat.com>,
Boqun Feng <boqun.feng@...il.com>, Jonathan Corbet <corbet@....net>,
Mathieu Poirier <mathieu.poirier@...aro.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
<conor+dt@...nel.org>,
Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>
Cc: linux-remoteproc@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-doc@...r.kernel.org, linux-arm-msm@...r.kernel.org,
devicetree@...r.kernel.org, Richard Maina <quic_rmaina@...cinc.com>
Subject: Re: [PATCH 6/7] remoteproc: qcom_q6v5_pas: Add hwspinlock bust on
stop
On 5/17/24 00:58, Chris Lew wrote:
> From: Richard Maina <quic_rmaina@...cinc.com>
>
> When remoteproc goes down unexpectedly this results in a state where any
> acquired hwspinlocks will remain locked possibly resulting in deadlock.
> In order to ensure all locks are freed we include a call to
> hwspin_lock_bust() during remoteproc shutdown.
>
> For qcom_q6v5_pas remoteprocs, each remoteproc has an assigned id that
> is used to take the hwspinlock. Remoteproc should use this id to try and
> bust the lock on remoteproc stop.
>
> This edge case only occurs with q6v5_pas watchdog crashes. The error
> fatal case has handling to clear the hwspinlock before the error fatal
> interrupt is triggered.
>
> Signed-off-by: Richard Maina <quic_rmaina@...cinc.com>
> Signed-off-by: Chris Lew <quic_clew@...cinc.com>
> ---
> drivers/remoteproc/qcom_q6v5_pas.c | 28 ++++++++++++++++++++++++++++
> 1 file changed, 28 insertions(+)
>
> diff --git a/drivers/remoteproc/qcom_q6v5_pas.c b/drivers/remoteproc/qcom_q6v5_pas.c
> index 54d8005d40a3..57178fcb9aa3 100644
> --- a/drivers/remoteproc/qcom_q6v5_pas.c
> +++ b/drivers/remoteproc/qcom_q6v5_pas.c
> @@ -10,6 +10,7 @@
> #include <linux/clk.h>
> #include <linux/delay.h>
> #include <linux/firmware.h>
> +#include <linux/hwspinlock.h>
> #include <linux/interrupt.h>
> #include <linux/kernel.h>
> #include <linux/module.h>
> @@ -52,6 +53,7 @@ struct adsp_data {
> const char *ssr_name;
> const char *sysmon_name;
> int ssctl_id;
> + int hwlock_id;
>
> int region_assign_idx;
> int region_assign_count;
> @@ -84,6 +86,9 @@ struct qcom_adsp {
> bool decrypt_shutdown;
> const char *info_name;
>
> + struct hwspinlock *hwlock;
> + int hwlock_id;
IIRC, this is the same one that is passed in the DT.
Can we get it dynamically from there?
Konrad
Powered by blists - more mailing lists