[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <41036bca-1266-70e9-6485-b718c9741c3f@st.com>
Date: Mon, 13 May 2019 09:10:34 +0000
From: Fabien DESSENNE <fabien.dessenne@...com>
To: Ohad Ben-Cohen <ohad@...ery.com>,
Bjorn Andersson <bjorn.andersson@...aro.org>,
Jonathan Corbet <corbet@....net>,
"linux-remoteproc@...r.kernel.org" <linux-remoteproc@...r.kernel.org>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
CC: Benjamin GAIGNARD <benjamin.gaignard@...com>,
Alexandre TORGUE <alexandre.torgue@...com>,
Fabien DESSENNE <fabien.dessenne@...com>
Subject: Re: [PATCH 0/2] hwspinlock: add the 'in_atomic' API
Hi
Gentle reminder
Fabien
On 07/03/2019 4:58 PM, Fabien Dessenne wrote:
> In its current implementation, the hwspinlock framework relies on jiffies
> to handle the timeout of the hwspin_lock_timeout_xxx() API.
> In an atomic context (or more precisely when irq are disabled) jiffies does not
> increase, which prevents the timeout to reach its target value (infinite loop).
>
> Note that there is already an hwspinlock user that runs in atomic context
> (drivers/irqchip/irq-stm32-exti.c) and that has to handle by itself the
> timeout.
>
> The first patch of the series completes the Documentation (the 'raw' API
> is not documented), and the second patch provides with the 'in_atomic' API.
>
> Fabien Dessenne (2):
> hwspinlock: document the hwspinlock 'raw' API
> hwspinlock: add the 'in_atomic' API
>
> Documentation/hwspinlock.txt | 81 ++++++++++++++++++++++++++++++++++++
> drivers/hwspinlock/hwspinlock_core.c | 43 +++++++++++++------
> include/linux/hwspinlock.h | 61 +++++++++++++++++++++++++--
> 3 files changed, 169 insertions(+), 16 deletions(-)
>
Powered by blists - more mailing lists