regressions.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <regressions@leemhuis.info>
To: "regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: [REGRESSION] gpio: omap: ensure irq is enabled before wakeup #forregzbot
Date: Wed, 8 Jun 2022 13:28:59 +0200	[thread overview]
Message-ID: <ff1e3d4b-c69e-1dcf-fc37-bbd8cd35b605@leemhuis.info> (raw)
In-Reply-To: <CY1PR07MB2700E81609B0967127D0773381DF9@CY1PR07MB2700.namprd07.prod.outlook.com>

[TLDR: I'm adding this regression report to the list of tracked
regressions; all text from me you find below is based on a few templates
paragraphs you might have encountered already already in similar form.]

TWIMC: this mail is primarily send for documentation purposes and for
regzbot, my Linux kernel regression tracking bot. These mails usually
contain '#forregzbot' in the subject, to make them easy to spot and filter.

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, 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.
> 

To be sure below issue doesn't fall through the cracks unnoticed, I'm
adding it to regzbot, my Linux kernel regression tracking bot:

#regzbot ^introduced c859e0d479b3b4f6132fc12637c51e01492f31f6
#regzbot title gpio: improper toggle during a SPI transaction with a
microcontroller
#regzbot ignore-activity
#regzbot back-burner: author of the commit can't help anymore

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.

      parent reply	other threads:[~2022-06-08 11:29 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
2022-06-08  9:19       ` Russell King (Oracle)
2022-06-08 11:08         ` Russell King (Oracle)
2022-06-08 11:28 ` Thorsten Leemhuis [this message]

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=ff1e3d4b-c69e-1dcf-fc37-bbd8cd35b605@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    /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).