From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Cosmin-Gabriel Tanislav <cosmin-gabriel.tanislav.xa@renesas.com>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Linus Walleij <linusw@kernel.org>,
Clark Williams <clrkwllms@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Bartosz Golaszewski <brgl@kernel.org>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-rt-devel@lists.linux.dev" <linux-rt-devel@lists.linux.dev>
Subject: Re: RE: [PATCH] pinctrl: renesas: rzt2h: fix invalid wait context
Date: Wed, 4 Feb 2026 21:00:34 +0100 [thread overview]
Message-ID: <20260204200034.b1UsoMT9@linutronix.de> (raw)
In-Reply-To: <TYRPR01MB156191EEA4542FC6DC6BA9A488598A@TYRPR01MB15619.jpnprd01.prod.outlook.com>
On 2026-02-04 19:53:36 [+0000], Cosmin-Gabriel Tanislav wrote:
> > From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> > Sent: Wednesday, February 4, 2026 9:14 PM
> >
> > On 2026-02-04 20:04:48 [+0200], Cosmin Tanislav wrote:
> > > The following invalid wait context BUG is observed when running with
> > > CONFIG_PROVE_LOCKING enabled.
> > >
> > > This seems to stem from the fact that __setup_irq() takes a
> > > raw_spinlock_t, while we take a spinlock_t inside gpiod_get_direction().
> >
> > From the backtrace yes. It is more that the irqchip used interrupt chip
> > needs to be able to mask interrupts in hardirq context which it needs a
> > raw_spinlock_t.
> >
>
> Would you like me to reword the commit message? I only analyzed why it
> happens, I didn't investigate why it needs to happen. :D
It did explain. It would make sense to include the reasoning and not
symptoms.
Sebastian
prev parent reply other threads:[~2026-02-04 20:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 18:04 [PATCH] pinctrl: renesas: rzt2h: fix invalid wait context Cosmin Tanislav
2026-02-04 19:14 ` Sebastian Andrzej Siewior
2026-02-04 19:53 ` Cosmin-Gabriel Tanislav
2026-02-04 20:00 ` Sebastian Andrzej Siewior [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=20260204200034.b1UsoMT9@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=brgl@kernel.org \
--cc=clrkwllms@kernel.org \
--cc=cosmin-gabriel.tanislav.xa@renesas.com \
--cc=geert+renesas@glider.be \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=rostedt@goodmis.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