Re: [PATCH] pinctrl: cherryview: Trigger hwirq0 for interrupt-lines without a mapping

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

On 1/16/22 02:01, Linus Walleij wrote:
> On Tue, Jan 4, 2022 at 10:31 PM Andy Shevchenko
> <andriy.shevchenko@xxxxxxxxxxxxxxx> wrote:
> 
>> On Tue, Jan 04, 2022 at 05:42:38PM +0100, Hans de Goede wrote:
>>> Commit bdfbef2d29dc ("pinctrl: cherryview: Don't use selection 0 to mark
>>> an interrupt line as unused") made the code properly differentiate
>>> between unset vs (hwirq) 0 entries in the GPIO-controller interrupt-line
>>> to GPIO pinnumber/hwirq mapping.
>>>
>>> This is causing some boards to not boot. This commit restores the old
>>> behavior of triggering hwirq 0 when receiving an interrupt on an
>>> interrupt-line for which there is no mapping.
>>
>> Acked-by: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
>>
>> Linus, can you apply this directly for v5.16 release?
> 
> Unfortunately I am a bit snowed under by backlog but I have now
> applied it for fixes for v5.17.

Thank you.

> Should I now also tag it for stable?

The troublesome commit this fixes / worksaround is only in Torvald's
current master, not in the v5.16 tag, so there is no need for this to
go stable.

Regards,

Hans




[Index of Archives]     [Linux SPI]     [Linux Kernel]     [Linux ARM (vger)]     [Linux ARM MSM]     [Linux Omap]     [Linux Arm]     [Linux Tegra]     [Fedora ARM]     [Linux for Samsung SOC]     [eCos]     [Linux Fastboot]     [Gcc Help]     [Git]     [DCCP]     [IETF Announce]     [Security]     [Linux MIPS]     [Yosemite Campsites]

  Powered by Linux