LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Fabien Dessenne <fabien.dessenne@st.com>
Cc: Ohad Ben-Cohen <ohad@wizery.com>,
Jonathan Corbet <corbet@lwn.net>,
linux-remoteproc@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
Benjamin Gaignard <benjamin.gaignard@st.com>,
Alexandre Torgue <alexandre.torgue@st.com>
Subject: Re: [PATCH 0/2] hwspinlock: add the 'in_atomic' API
Date: Sat, 29 Jun 2019 21:08:28 -0700 [thread overview]
Message-ID: <20190630040828.GB1263@builder> (raw)
In-Reply-To: <1551974303-24542-1-git-send-email-fabien.dessenne@st.com>
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
>
prev parent reply other threads:[~2019-06-30 4:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-07 15:58 Fabien Dessenne
2019-03-07 15:58 ` [PATCH 1/2] hwspinlock: document the hwspinlock 'raw' API Fabien Dessenne
2019-03-07 15:58 ` [PATCH 2/2] hwspinlock: add the 'in_atomic' API Fabien Dessenne
2019-05-13 9:10 ` [PATCH 0/2] " Fabien DESSENNE
2019-06-30 4:08 ` Bjorn Andersson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190630040828.GB1263@builder \
--to=bjorn.andersson@linaro.org \
--cc=alexandre.torgue@st.com \
--cc=benjamin.gaignard@st.com \
--cc=corbet@lwn.net \
--cc=fabien.dessenne@st.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=ohad@wizery.com \
--subject='Re: [PATCH 0/2] hwspinlock: add the '\''in_atomic'\'' API' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).