From: Eric Schikschneit <eric.schikschneit@novatechautomation.com>
To: "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: [REGRESSION] gpio: omap: ensure irq is enabled before wakeup
Date: Wed, 1 Jun 2022 15:56:51 +0000 [thread overview]
Message-ID: <CY1PR07MB2700E81609B0967127D0773381DF9@CY1PR07MB2700.namprd07.prod.outlook.com> (raw)
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.
..............................................
Eric Schikschneit
Embedded Linux Engineer
NovaTech, LLC
13555 W. 107th Street
Lenexa, KS 66215
(913) 451-1880 (main)
(913) 742-XXXX (direct)
Eric.Schikschneit@novatechweb.com
next reply other threads:[~2022-06-01 15:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 15:56 Eric Schikschneit [this message]
2022-06-07 10:07 ` [REGRESSION] gpio: omap: ensure irq is enabled before wakeup 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 ` [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=CY1PR07MB2700E81609B0967127D0773381DF9@CY1PR07MB2700.namprd07.prod.outlook.com \
--to=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).