From: Radu Rendec <radu@rendec.net>
To: Ju Nan <junan76@163.com>,
tglx@kernel.org, mcoquelin.stm32@gmail.com,
alexandre.torgue@foss.st.com
Cc: linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] irqchip/stm32mp-exti: fix the unit of the hwspinlock timeout
Date: Sat, 15 Aug 2026 10:19:26 -0400 [thread overview]
Message-ID: <ffa83b72ad30bebe1ebcab30b04703e9d7c935ce.camel@rendec.net> (raw)
In-Reply-To: <0748a117106e6ae41ae5361ba053af3e96feed40.camel@rendec.net>
On Sat, 2026-08-15 at 10:08 -0400, Radu Rendec wrote:
> On Wed, 2026-08-05 at 11:21 +0800, Ju Nan wrote:
> > HWSPNLCK_TIMEOUT is passed to hwspin_lock_timeout_in_atomic(), whose
> > timeout argument is in milliseconds, not microseconds:
> >
> > atomic_delay += HWSPINLOCK_RETRY_DELAY_US;
> > if (atomic_delay > to * 1000)
> > return -ETIMEDOUT;
> >
> > So stm32mp_exti_set_type() asks for a 1 second timeout where the comment
> > next to the macro says it wants 1 millisecond. The semaphore is polled
> > with udelay() from a section that holds chip_data->rlock, a
> > raw_spinlock_t, so preemption stays disabled for the whole wait on every
> > configuration, PREEMPT_RT included.
> >
> > The hwspinlock core documents this explicitly:
> >
> > If the mode is HWLOCK_IN_ATOMIC (called from an atomic context) the
> > timeout is handled with busy-waiting delays, hence shall not exceed
> > few msecs.
> >
> > Pass the value the comment always described. The core retries every
> > HWSPINLOCK_RETRY_DELAY_US (100 us), so the semaphore is still polled ten
> > times before giving up, which is far longer than any plausible hold time
> > on the coprocessor side. A timeout is reported with pr_err() and fails
> > the trigger type configuration, so shortening it degrades gracefully.
> >
> > Signed-off-by: Ju Nan <junan76@163.com>
> > ---
> > drivers/irqchip/irq-stm32mp-exti.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/irqchip/irq-stm32mp-exti.c b/drivers/irqchip/irq-stm32mp-exti.c
> > index a24f4f1a4..f5f0109bf 100644
> > --- a/drivers/irqchip/irq-stm32mp-exti.c
> > +++ b/drivers/irqchip/irq-stm32mp-exti.c
> > @@ -23,7 +23,7 @@
> >
> > #define IRQS_PER_BANK 32
> >
> > -#define HWSPNLCK_TIMEOUT 1000 /* usec */
> > +#define HWSPNLCK_TIMEOUT 1 /* msec */
> >
> > #define EXTI_EnCIDCFGR(n) (0x180 + (n) * 4)
> > #define EXTI_HWCFGR1 0x3f0
>
> Reviewed-by: Radu Rendec <radu@rendec.net>
Oops! Hit the "send" button too soon. The patch is OK, so the r-b tag
stays. But it also needs this:
Fixes: 5257169ade8c ("irqchip/stm32-exti: Use the hwspin_lock_timeout_in_atomic() API")
next prev parent reply other threads:[~2026-08-15 14:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-05 3:21 [PATCH] irqchip/stm32mp-exti: fix the unit of the hwspinlock timeout Ju Nan
2026-08-15 14:08 ` Radu Rendec
2026-08-15 14:19 ` Radu Rendec [this message]
2026-08-16 14:20 ` [PATCH v2] " Ju Nan
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=ffa83b72ad30bebe1ebcab30b04703e9d7c935ce.camel@rendec.net \
--to=radu@rendec.net \
--cc=alexandre.torgue@foss.st.com \
--cc=junan76@163.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=tglx@kernel.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox