[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMRc=Mf91eMF7D6CRtA8-HQ7pdtP343WUGhLG4qti_9zJF4ELQ@mail.gmail.com>
Date: Mon, 2 May 2022 13:18:49 +0200
From: Bartosz Golaszewski <brgl@...ev.pl>
To: Piyush Malgujar <pmalgujar@...vell.com>
Cc: "open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
devicetree <devicetree@...r.kernel.org>,
Linus Walleij <linus.walleij@...aro.org>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Robert Richter <rric@...nel.org>, cchavva@...vell.com,
wsadowski@...vell.com
Subject: Re: [PATCH 1/5] gpio: thunderx: avoid potential deadlock
On Wed, Apr 27, 2022 at 4:46 PM Piyush Malgujar <pmalgujar@...vell.com> wrote:
>
> Using irqsave/irqrestore locking variants to avoid any deadlock.
>
I see you'll be resending this anyway so would you mind providing an
example of a deadlock that is possible with no-irqsave variants?
Thanks.
Bart
> Signed-off-by: Piyush Malgujar <pmalgujar@...vell.com>
> ---
Powered by blists - more mailing lists