On 5/21/2024 10:38 AM, Konrad Dybcio wrote:
On 5/17/24 00:58, Chris Lew wrote:
From: Richard Maina
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 inc
On 5/17/24 00:58, Chris Lew wrote:
From: Richard Maina
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 remote
On 5/17/2024 12:21 AM, Mukesh Ojha wrote:
On 5/17/2024 4:28 AM, Chris Lew wrote:
From: Richard Maina
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 i
On 5/17/2024 2:08 AM, Bryan O'Donoghue wrote:
On 17/05/2024 00:58, Chris Lew wrote:
From: Richard Maina
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
On 17/05/2024 00:58, Chris Lew wrote:
From: Richard Maina
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 remote
On 5/17/2024 4:28 AM, Chris Lew wrote:
From: Richard Maina
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 re
On 5/17/2024 4:28 AM, Chris Lew wrote:
From: Richard Maina
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 re
From: Richard Maina
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 remote
