[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdYEigGHkoGfBg15tFXadgpXUAjDOnw7ePXhmvHJqPEJXw@mail.gmail.com>
Date: Sun, 30 Jan 2022 02:50:25 +0100
From: Linus Walleij <linus.walleij@...aro.org>
To: Jonathan Neuschäfer <j.neuschaefer@....net>
Cc: linux-gpio@...r.kernel.org, devicetree@...r.kernel.org,
Rob Herring <robh+dt@...nel.org>, openbmc@...ts.ozlabs.org,
Tomer Maimon <tmaimon77@...il.com>,
Joel Stanley <joel@....id.au>, linux-kernel@...r.kernel.org,
Andy Shevchenko <andy.shevchenko@...il.com>,
Avi Fishman <avifishman70@...il.com>,
Tali Perry <tali.perry1@...il.com>,
Patrick Venture <venture@...gle.com>,
Nancy Yuen <yuenn@...gle.com>,
Benjamin Fair <benjaminfair@...gle.com>
Subject: Re: [PATCH v5 0/9] Nuvoton WPCM450 pinctrl and GPIO driver
On Sat, Jan 29, 2022 at 12:57 PM Jonathan Neuschäfer
<j.neuschaefer@....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
Powered by blists - more mailing lists