[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d351e221-ddd4-eb34-5bbe-08314d26a2e0@gmail.com>
Date: Fri, 28 Jan 2022 19:44:36 +0300
From: Sergei Shtylyov <sergei.shtylyov@...il.com>
To: Lee Jones <lee.jones@...aro.org>
Cc: Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
greybus-dev@...ts.linaro.org, linux-i2c@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-staging@...ts.linux.dev,
linux-usb@...r.kernel.org, netdev@...r.kernel.org,
"David S. Miller" <davem@...emloft.net>,
Alex Elder <elder@...nel.org>, Arnd Bergmann <arnd@...db.de>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Hans de Goede <hdegoede@...hat.com>,
Jakub Kicinski <kuba@...nel.org>,
Johan Hovold <johan@...nel.org>,
Rui Miguel Silva <rmfrfs@...il.com>,
Thomas Gleixner <tglx@...utronix.de>,
UNGLinuxDriver@...rochip.com, Wolfram Sang <wsa@...nel.org>,
Woojung Huh <woojung.huh@...rochip.com>
Subject: Re: [PATCH 4/7] mfd: hi6421-spmi-pmic: Use generic_handle_irq_safe().
On 1/28/22 4:33 PM, Lee Jones wrote:
>>> generic_handle_irq() is invoked from a regular interrupt service
>>> routing. This handler will become a forced-threaded handler on
>>
>> s/routing/routine/?
>>
>>> PREEMPT_RT and will be invoked with enabled interrupts. The
>>> generic_handle_irq() must be invoked with disabled interrupts in order
>>> to avoid deadlocks.
>>>
>>> Instead of manually disabling interrupts before invoking use
>>> generic_handle_irq() which can be invoked with enabled and disabled
>>> interrupts.
>>>
>>> Signed-off-by: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
>> [...]
>>
>> MBR, Sergey
>
> What does that mean?
Ah, you were asking about MBR! My best regards then. :-)
MBR, Sergey
Powered by blists - more mailing lists