From: Linus Walleij <linus.walleij@linaro.org>
To: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
Cc: linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
openbmc@lists.ozlabs.org, Tomer Maimon <tmaimon77@gmail.com>,
Joel Stanley <joel@jms.id.au>,
linux-kernel@vger.kernel.org,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Avi Fishman <avifishman70@gmail.com>,
Tali Perry <tali.perry1@gmail.com>,
Patrick Venture <venture@google.com>,
Nancy Yuen <yuenn@google.com>,
Benjamin Fair <benjaminfair@google.com>
Subject: Re: [PATCH v5 0/9] Nuvoton WPCM450 pinctrl and GPIO driver
Date: Sun, 30 Jan 2022 02:50:25 +0100 [thread overview]
Message-ID: <CACRpkdYEigGHkoGfBg15tFXadgpXUAjDOnw7ePXhmvHJqPEJXw@mail.gmail.com> (raw)
In-Reply-To: <20220129115228.2257310-1-j.neuschaefer@gmx.net>
On Sat, Jan 29, 2022 at 12:57 PM Jonathan Neuschäfer
<j.neuschaefer@gmx.net> wrote:
> This is version 5 of the WPCM450 pinctrl/GPIO driver patchset.
I haven't had time to look in detail but the kernel robot is complaining
about patch 5...
> I was originally just going to rebase the patchset on top of v5.17-rc1,
> but while testing, I found that the IRQ handling code violated locking
> rules, specifically that it used spin locks (which can sleep on RT kernels)
> in IRQ contexts. So I made a few changes to fix that, mainly switching
> to raw spin locks.
Which patches do you expect to be applied to the pin control tree?
Yours,
Linus Walleij
WARNING: multiple messages have this Message-ID (diff)
From: Linus Walleij <linus.walleij@linaro.org>
To: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
Cc: devicetree@vger.kernel.org, Tomer Maimon <tmaimon77@gmail.com>,
Avi Fishman <avifishman70@gmail.com>,
Patrick Venture <venture@google.com>,
openbmc@lists.ozlabs.org, linux-kernel@vger.kernel.org,
Tali Perry <tali.perry1@gmail.com>,
linux-gpio@vger.kernel.org,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Benjamin Fair <benjaminfair@google.com>
Subject: Re: [PATCH v5 0/9] Nuvoton WPCM450 pinctrl and GPIO driver
Date: Sun, 30 Jan 2022 02:50:25 +0100 [thread overview]
Message-ID: <CACRpkdYEigGHkoGfBg15tFXadgpXUAjDOnw7ePXhmvHJqPEJXw@mail.gmail.com> (raw)
In-Reply-To: <20220129115228.2257310-1-j.neuschaefer@gmx.net>
On Sat, Jan 29, 2022 at 12:57 PM Jonathan Neuschäfer
<j.neuschaefer@gmx.net> wrote:
> This is version 5 of the WPCM450 pinctrl/GPIO driver patchset.
I haven't had time to look in detail but the kernel robot is complaining
about patch 5...
> I was originally just going to rebase the patchset on top of v5.17-rc1,
> but while testing, I found that the IRQ handling code violated locking
> rules, specifically that it used spin locks (which can sleep on RT kernels)
> in IRQ contexts. So I made a few changes to fix that, mainly switching
> to raw spin locks.
Which patches do you expect to be applied to the pin control tree?
Yours,
Linus Walleij
next prev parent reply other threads:[~2022-01-30 1:50 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-29 11:52 [PATCH v5 0/9] Nuvoton WPCM450 pinctrl and GPIO driver Jonathan Neuschäfer
2022-01-29 11:52 ` Jonathan Neuschäfer
2022-01-29 11:52 ` [PATCH v5 1/9] dt-bindings: arm/npcm: Add binding for global control registers (GCR) Jonathan Neuschäfer
2022-01-29 11:52 ` Jonathan Neuschäfer
2022-01-29 11:52 ` [PATCH v5 2/9] MAINTAINERS: Match all of bindings/arm/npcm/ as part of NPCM architecture Jonathan Neuschäfer
2022-01-29 11:52 ` Jonathan Neuschäfer
2022-01-29 11:52 ` [PATCH v5 3/9] ARM: dts: wpcm450: Add global control registers (GCR) node Jonathan Neuschäfer
2022-01-29 11:52 ` Jonathan Neuschäfer
2022-01-29 11:52 ` [PATCH v5 4/9] dt-bindings: pinctrl: Add Nuvoton WPCM450 Jonathan Neuschäfer
2022-01-29 11:52 ` Jonathan Neuschäfer
2022-01-29 11:52 ` [PATCH v5 5/9] pinctrl: nuvoton: Add driver for WPCM450 Jonathan Neuschäfer
2022-01-29 11:52 ` Jonathan Neuschäfer
2022-01-29 13:48 ` kernel test robot
2022-01-29 13:48 ` kernel test robot
2022-01-29 13:48 ` kernel test robot
2022-01-29 14:09 ` kernel test robot
2022-01-29 14:09 ` kernel test robot
2022-01-29 14:09 ` kernel test robot
2022-01-30 18:47 ` Andy Shevchenko
2022-01-30 18:47 ` Andy Shevchenko
2022-01-30 18:47 ` Andy Shevchenko
2022-01-30 20:17 ` Jonathan Neuschäfer
2022-01-30 20:17 ` Jonathan Neuschäfer
2022-01-30 20:17 ` Jonathan Neuschäfer
2022-01-29 11:52 ` [PATCH v5 6/9] ARM: dts: wpcm450: Add pinctrl and GPIO nodes Jonathan Neuschäfer
2022-01-29 11:52 ` Jonathan Neuschäfer
2022-01-29 11:52 ` [PATCH v5 7/9] ARM: dts: wpcm450: Add pin functions Jonathan Neuschäfer
2022-01-29 11:52 ` Jonathan Neuschäfer
2022-01-29 11:52 ` [PATCH v5 8/9] ARM: dts: wpcm450-supermicro-x9sci-ln4f: Add GPIO LEDs and buttons Jonathan Neuschäfer
2022-01-29 11:52 ` Jonathan Neuschäfer
2022-01-29 11:52 ` [PATCH v5 9/9] ARM: dts: wpcm450: Add pinmux information to UART0 Jonathan Neuschäfer
2022-01-29 11:52 ` Jonathan Neuschäfer
2022-01-30 1:50 ` Linus Walleij [this message]
2022-01-30 1:50 ` [PATCH v5 0/9] Nuvoton WPCM450 pinctrl and GPIO driver Linus Walleij
2022-01-30 10:12 ` Jonathan Neuschäfer
2022-01-30 10:12 ` Jonathan Neuschäfer
2022-02-01 23:42 ` Joel Stanley
2022-02-01 23:42 ` Joel Stanley
2022-02-02 12:01 ` Jonathan Neuschäfer
2022-02-02 12:01 ` Jonathan Neuschäfer
2022-02-02 12:10 ` Andy Shevchenko
2022-02-02 12:10 ` Andy Shevchenko
2022-02-02 12:40 ` Jonathan Neuschäfer
2022-02-02 12:40 ` Jonathan Neuschäfer
2022-02-12 8:40 ` Jonathan Neuschäfer
2022-02-12 8:40 ` Jonathan Neuschäfer
2022-02-15 5:56 ` Joel Stanley
2022-02-15 5:56 ` Joel Stanley
2022-02-15 17:19 ` Jonathan Neuschäfer
2022-02-15 17:19 ` Jonathan Neuschäfer
2022-03-15 0:17 ` Linus Walleij
2022-03-15 0:17 ` Linus Walleij
2022-03-15 1:13 ` Joel Stanley
2022-03-15 1:13 ` Joel Stanley
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=CACRpkdYEigGHkoGfBg15tFXadgpXUAjDOnw7ePXhmvHJqPEJXw@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=andy.shevchenko@gmail.com \
--cc=avifishman70@gmail.com \
--cc=benjaminfair@google.com \
--cc=devicetree@vger.kernel.org \
--cc=j.neuschaefer@gmx.net \
--cc=joel@jms.id.au \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=robh+dt@kernel.org \
--cc=tali.perry1@gmail.com \
--cc=tmaimon77@gmail.com \
--cc=venture@google.com \
--cc=yuenn@google.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.