From: Pierluigi Passaro <pierluigi.p@variscite.com>
To: Wolfram Sang <wsa@kernel.org>,
Alexander Stein <alexander.stein@ew.tq-group.com>
Cc: Alifer Willians de Moraes <alifer.m@variscite.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Eran Matityahu <eran.m@variscite.com>,
"festevam@gmail.com" <festevam@gmail.com>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
"linux-imx@nxp.com" <linux-imx@nxp.com>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"linux@rempel-privat.de" <linux@rempel-privat.de>,
"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
gaopan <b54642@freescale.com>, Fugang Duan <B38611@freescale.com>,
Vipul Kumar <vipul_kumar@mentor.com>
Subject: Re: [PATCH] i2c: imx: add irqf_no_suspend
Date: Mon, 20 Jun 2022 13:29:30 +0000 [thread overview]
Message-ID: <AM6PR08MB4376A823A9B433B68D9F8423FFB09@AM6PR08MB4376.eurprd08.prod.outlook.com> (raw)
Hi All,
> Hi everyone,
> > > The i2c irq is masked when pcie starts a i2c transfer process
> > > during noirq suspend stage. As a result, i2c transfer fails.
> > > To solve the problem, IRQF_NO_SUSPEND is added to i2c bus.
> > >
> > > Signed-off-by: Gao Pan <b54642@freescale.com>
> > > Signed-off-by: Fugang Duan <B38611@freescale.com>
> > > Signed-off-by: Vipul Kumar <vipul_kumar@mentor.com>
> The SoB from Alifer Moraes is missing, too.
> > > goto rpm_disable;
> > >
> > > /* Request IRQ */
> > > - ret = request_threaded_irq(irq, i2c_imx_isr, NULL, IRQF_SHARED,
> > > + ret = request_threaded_irq(irq, i2c_imx_isr, NULL,
> > > + IRQF_SHARED | IRQF_NO_SUSPEND,
> > > pdev->name, i2c_imx);
> > > if (ret) {
> > > dev_err(&pdev->dev, "can't claim irq %d\n", irq);
> >
> >
> > I stumbled across Documentation/power/suspend-and-interrupts.rst which states:
> > > For this reason, using IRQF_NO_SUSPEND and IRQF_SHARED at the
> > > same time should be avoided.
> > Given this IMHO at least a comment should be inserted why this is fine. I dont
> > have a full picture about the situation, but to me it seems there is a
> > reference missing, or why/how does some PCIe start some I2C transfer when the
> > controller is suspended already? Do I miss something?
This patch has been introduced to fix the following behavior.
HW conditions
- Variscite DART-MX8M on DT8MCustomBoard v2.x or higher.
- The PCIe connector uses a reset pin coming from a GPIO expander connected to the I2C bus.
SW behavior
- Upon wake-up, the PCIe try toggling the reset pins, but the GPIO expander / I2C bus are still suspended, leading to a PCIe wake-up failure.
From our investigation, we can't identify a way to postpone PCIe wake-up after I2C wake-up.
This patch is still present in latest NXP kernel 5.15, but please let me know if you think this should be approached / fixed in a different way.
Thanks
Regards
Pier
> Thank you for this comment, Alexander. I second you, this needs
> explanation.
> Happy hacking,
> Wolfram
next reply other threads:[~2022-06-20 14:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 13:29 Pierluigi Passaro [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-03-07 14:36 [PATCH] i2c: imx: add irqf_no_suspend Alifer Moraes
2022-03-11 9:01 ` Oleksij Rempel
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=AM6PR08MB4376A823A9B433B68D9F8423FFB09@AM6PR08MB4376.eurprd08.prod.outlook.com \
--to=pierluigi.p@variscite.com \
--cc=B38611@freescale.com \
--cc=alexander.stein@ew.tq-group.com \
--cc=alifer.m@variscite.com \
--cc=b54642@freescale.com \
--cc=eran.m@variscite.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rempel-privat.de \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=vipul_kumar@mentor.com \
--cc=wsa@kernel.org \
/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).