From: Thorsten Leemhuis <regressions@leemhuis.info>
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
Date: Wed, 8 Jun 2022 10:54:48 +0200 [thread overview]
Message-ID: <2725aaed-6c31-2cce-dcd2-55f2f1ed533c@leemhuis.info> (raw)
In-Reply-To: <CY1PR07MB27008E7B556EF9ABF609F85081A59@CY1PR07MB2700.namprd07.prod.outlook.com>
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.
next prev parent reply other threads:[~2022-06-08 8:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 15:56 [REGRESSION] gpio: omap: ensure irq is enabled before wakeup Eric Schikschneit
2022-06-07 10:07 ` Thorsten Leemhuis
2022-06-07 11:58 ` Eric Schikschneit
2022-06-08 8:54 ` Thorsten Leemhuis [this message]
2022-06-08 9:19 ` Russell King (Oracle)
2022-06-08 11:08 ` Russell King (Oracle)
2022-06-08 11:28 ` [REGRESSION] gpio: omap: ensure irq is enabled before wakeup #forregzbot Thorsten Leemhuis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2725aaed-6c31-2cce-dcd2-55f2f1ed533c@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=eric.schikschneit@novatechautomation.com \
--cc=grygorii.strashko@ti.com \
--cc=linus.walleij@linaro.org \
--cc=regressions@lists.linux.dev \
--cc=rmk+kernel@armlinux.org.uk \
--cc=stable@vger.kernel.org \
--cc=tony@atomide.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).