[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <171701811794.1918821.5154506293707584272.b4-ty@kernel.org>
Date: Wed, 29 May 2024 14:28:48 -0700
From: Bjorn Andersson <andersson@...nel.org>
To: 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>,
Konrad Dybcio <konrad.dybcio@...aro.org>,
Chris Lew <quic_clew@...cinc.com>
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: (subset) [PATCH v3 0/4] Add support for hwspinlock bust
On Wed, 29 May 2024 11:09:54 -0700, Chris Lew wrote:
> hwspinlocks can be acquired by many devices on the SoC. If any of these
> devices go into a bad state before the device releases the hwspinlock,
> then that hwspinlock may end up in an unusable state.
>
> In the case of smem, each remoteproc takes a hwspinlock before trying to
> allocate an smem item. If the remoteproc were to suddenly crash without
> releasing this, it would be impossible for other remoteprocs to allocate
> any smem items.
>
> [...]
Applied, thanks!
[3/4] soc: qcom: smem: Add qcom_smem_bust_hwspin_lock_by_host()
commit: 2e3f0d693875db698891ffe89a18121bda5b95b8
[4/4] remoteproc: qcom_q6v5_pas: Add hwspinlock bust on stop
commit: 568b13b65078e2b557ccf47674a354cecd1db641
Best regards,
--
Bjorn Andersson <andersson@...nel.org>
Powered by blists - more mailing lists