Re: [REGRESSION] gpio: omap: ensure irq is enabled before wakeup

[Thorsten Leemhuis <regressions@leemhuis.info>]

On 07.06.22 13:58, Eric Schikschneit wrote:
> I am limited by the availability of the preempt-rt kernels that are 
> available on the yocto project. The newest kernel I see listed is 
> 5.15.44 on: https://git.yoctoproject.org/linux-yocto/

Well, it's up to Russel if that is enough for him, as he authored
c859e0d479b3 ("gpio: omap: ensure irq is enabled before wakeup") and
thus should look into this regression.

Ciao, Thorsten

> From: Thorsten Leemhuis <regressions@leemhuis.info>
> Sent: Tuesday, June 7, 2022 5:07 AM
> To: Eric Schikschneit <eric.schikschneit@novatechautomation.com>; stable@vger.kernel.org <stable@vger.kernel.org>
> Cc: regressions@lists.linux.dev <regressions@lists.linux.dev>; rmk+kernel@armlinux.org.uk <rmk+kernel@armlinux.org.uk>; grygorii.strashko@ti.com <grygorii.strashko@ti.com>; tony@atomide.com <tony@atomide.com>; linus.walleij@linaro.org <linus.walleij@linaro.org>
> Subject: Re: [REGRESSION] gpio: omap: ensure irq is enabled before wakeup 
>  
> Hi, this is your Linux kernel regression tracker.
> 
> On 01.06.22 17:56, Eric Schikschneit wrote:
>> Summary: OMAP patch causes SPI bus transaction failure on TI CPU 
>> Commit: c859e0d479b3b4f6132fc12637c51e01492f31f6 Kernel version:
>> 5.10.87
>>
>> The detailed description:
>>
>> I know this is a old commit at this point,
> 
> That shouldn't be a problem at all, but it raises one question that
> would be good to get answered: does this problem still occur with the
> latest code? This issue for example might have been fixed in between,
> but maybe the fix was to complex to get backported or something like
> that. Hence it would be ideal if you could quickly give 5.19-rc1 a shot;
> 5.18.y is not ideal, but will do as well.
> 
>> but we have observed a
>> regression caused by this commit. It causes improper toggle during a
>> SPI transaction with a microcontroller. The CPU in use is Texas
>> Instruments AM3352BZCZA80. The microcontroller in use is a PIC based
>> micro. I have logic capture images available to show the signal
>> difference that is causing confusion on the SPI bus.
> 
> Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
> 
> P.S.: As the Linux kernel's regression tracker I deal with a lot of
> reports and sometimes miss something important when writing mails like
> this. If that's the case here, don't hesitate to tell me in a public
> reply, it's in everyone's interest to set the public record straight.