[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20190630040828.GB1263@builder>
Date: Sat, 29 Jun 2019 21:08:28 -0700
From: Bjorn Andersson <bjorn.andersson@...aro.org>
To: Fabien Dessenne <fabien.dessenne@...com>
Cc: Ohad Ben-Cohen <ohad@...ery.com>, Jonathan Corbet <corbet@....net>,
linux-remoteproc@...r.kernel.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org,
Benjamin Gaignard <benjamin.gaignard@...com>,
Alexandre Torgue <alexandre.torgue@...com>
Subject: Re: [PATCH 0/2] hwspinlock: add the 'in_atomic' API
On Thu 07 Mar 07:58 PST 2019, 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.
>
Applied
Thanks,
Bjorn
> 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(-)
>
> --
> 2.7.4
>
Powered by blists - more mailing lists