From: Greg KH <gregkh@linuxfoundation.org>
To: Linux regressions mailing list <regressions@lists.linux.dev>
Cc: "Basavaraj Natikar" <Basavaraj.Natikar@amd.com>,
"Shyam Sundar S K" <Shyam-sundar.S-k@amd.com>,
"Linus Walleij" <linus.walleij@linaro.org>,
upstream@semihalf.com, rad@semihalf.com, mattedavis@google.com,
stable@vger.kernel.org, "Sasha Levin" <sashal@kernel.org>,
"Gong, Richard" <richard.gong@amd.com>,
"Mario Limonciello" <mario.limonciello@amd.com>,
"Kornel Dulęba" <korneld@chromium.org>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pinctrl: amd: Disable and mask interrupts on resume
Date: Tue, 11 Apr 2023 15:15:55 +0200 [thread overview]
Message-ID: <2023041152-desktop-breeze-0a89@gregkh> (raw)
In-Reply-To: <37178398-497c-900b-361a-34b1b77517aa@leemhuis.info>
On Tue, Apr 11, 2023 at 02:50:40PM +0200, Linux regression tracking (Thorsten Leemhuis) wrote:
>
>
> On 10.04.23 17:29, Gong, Richard wrote:
> > On 4/10/2023 12:03 AM, Mario Limonciello wrote:
> >> On 3/20/23 04:32, Kornel Dulęba wrote:
> >>
> >>> This fixes a similar problem to the one observed in:
> >>> commit 4e5a04be88fe ("pinctrl: amd: disable and mask interrupts on
> >>> probe").
> >>>
> >>> On some systems, during suspend/resume cycle firmware leaves
> >>> an interrupt enabled on a pin that is not used by the kernel.
> >>> This confuses the AMD pinctrl driver and causes spurious interrupts.
> >>>
> >>> The driver already has logic to detect if a pin is used by the kernel.
> >>> Leverage it to re-initialize interrupt fields of a pin only if it's not
> >>> used by us.
> >>>
> >>> Signed-off-by: Kornel Dulęba <korneld@chromium.org>
> >>> ---
> >>> drivers/pinctrl/pinctrl-amd.c | 36 +++++++++++++++++++----------------
> >>> 1 file changed, 20 insertions(+), 16 deletions(-)
> >>>
> >>> diff --git a/drivers/pinctrl/pinctrl-amd.c
> >>> b/drivers/pinctrl/pinctrl-amd.c
> >>> index 9236a132c7ba..609821b756c2 100644
> >>> --- a/drivers/pinctrl/pinctrl-amd.c
> >>> +++ b/drivers/pinctrl/pinctrl-amd.c
> >>> @@ -872,32 +872,34 @@ static const struct pinconf_ops amd_pinconf_ops
> >>> = {
> >>> .pin_config_group_set = amd_pinconf_group_set,
> >>> };
> >>> -static void amd_gpio_irq_init(struct amd_gpio *gpio_dev)
> >>> +static void amd_gpio_irq_init_pin(struct amd_gpio *gpio_dev, int pin)
> >>> {
> >>> - struct pinctrl_desc *desc = gpio_dev->pctrl->desc;
> >>> + const struct pin_desc *pd;
> >>> unsigned long flags;
> >>> u32 pin_reg, mask;
> >>> - int i;
> >>> mask = BIT(WAKE_CNTRL_OFF_S0I3) | BIT(WAKE_CNTRL_OFF_S3) |
> >>> BIT(INTERRUPT_MASK_OFF) | BIT(INTERRUPT_ENABLE_OFF) |
> >>> BIT(WAKE_CNTRL_OFF_S4);
> >>> - for (i = 0; i < desc->npins; i++) {
> >>> - int pin = desc->pins[i].number;
> >>> - const struct pin_desc *pd = pin_desc_get(gpio_dev->pctrl, pin);
> >>> -
> >>> - if (!pd)
> >>> - continue;
> >>> + pd = pin_desc_get(gpio_dev->pctrl, pin);
> >>> + if (!pd)
> >>> + return;
> >>> - raw_spin_lock_irqsave(&gpio_dev->lock, flags);
> >>> + raw_spin_lock_irqsave(&gpio_dev->lock, flags);
> >>> + pin_reg = readl(gpio_dev->base + pin * 4);
> >>> + pin_reg &= ~mask;
> >>> + writel(pin_reg, gpio_dev->base + pin * 4);
> >>> + raw_spin_unlock_irqrestore(&gpio_dev->lock, flags);
> >>> +}
> >>> - pin_reg = readl(gpio_dev->base + i * 4);
> >>> - pin_reg &= ~mask;
> >>> - writel(pin_reg, gpio_dev->base + i * 4);
> >>> +static void amd_gpio_irq_init(struct amd_gpio *gpio_dev)
> >>> +{
> >>> + struct pinctrl_desc *desc = gpio_dev->pctrl->desc;
> >>> + int i;
> >>> - raw_spin_unlock_irqrestore(&gpio_dev->lock, flags);
> >>> - }
> >>> + for (i = 0; i < desc->npins; i++)
> >>> + amd_gpio_irq_init_pin(gpio_dev, i);
> >>> }
> >>> #ifdef CONFIG_PM_SLEEP
> >>> @@ -950,8 +952,10 @@ static int amd_gpio_resume(struct device *dev)
> >>> for (i = 0; i < desc->npins; i++) {
> >>> int pin = desc->pins[i].number;
> >>> - if (!amd_gpio_should_save(gpio_dev, pin))
> >>> + if (!amd_gpio_should_save(gpio_dev, pin)) {
> >>> + amd_gpio_irq_init_pin(gpio_dev, pin);
> >>> continue;
> >>> + }
> >>> raw_spin_lock_irqsave(&gpio_dev->lock, flags);
> >>> gpio_dev->saved_regs[i] |= readl(gpio_dev->base + pin * 4)
> >>> & PIN_IRQ_PENDING;
> >>
> >> Hello Kornel,
> >>
> >> I've found that this commit which was included in 6.3-rc5 is causing a
> >> regression waking up from lid on a Lenovo Z13.
> > observed "unable to wake from power button" on AMD based Dell platform.
>
> This sounds like something that we want to fix quickly.
>
> > Reverting "pinctrl: amd: Disable and mask interrupts on resume" on the
> > top of 6.3-rc6 does fix the issue.
> >>
> >> Reverting it on top of 6.3-rc6 resolves the problem.
> >>
> >> I've collected what I can into this bug report:
> >>
> >> https://bugzilla.kernel.org/show_bug.cgi?id=217315
> >>
> >> Linus Walleij,
> >>
> >> It looks like this was CC to stable. If we can't get a quick solution
> >> we might want to pull this from stable.
> >
> > this commit landed into 6.1.23 as well
> >
> > d9c63daa576b2 pinctrl: amd: Disable and mask interrupts on resume
>
> It made it back up to 5.10.y afaics.
>
> The culprit has no fixes tag, which makes me wonder: should we quickly
> (e.g. today) revert this in mainline to get back to the previous state,
> so that Greg can pick up the revert for the next stable releases he
> apparently currently prepares?
>
> Greg, is there another way to make you quickly fix this in the stable
> trees? One option obviously would be "revert this now in stable, reapply
> it later together with a fix ". But I'm under the impression that this
> is too much of a hassle and thus something you only do in dire situations?
I would like to see this reverted in Linus's tree first please.
thanks,
greg k-h
prev parent reply other threads:[~2023-04-11 13:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 9:32 [PATCH] pinctrl: amd: Disable and mask interrupts on resume Kornel Dulęba
2023-03-20 10:05 ` Linus Walleij
2023-03-20 11:07 ` Kornel Dulęba
2023-03-28 13:20 ` Linus Walleij
2023-04-10 5:03 ` Mario Limonciello
2023-04-10 15:29 ` Gong, Richard
2023-04-10 16:17 ` Kornel Dulęba
2023-04-10 16:32 ` Kornel Dulęba
2023-04-11 1:29 ` Mario Limonciello
2023-04-11 12:50 ` Linux regression tracking (Thorsten Leemhuis)
2023-04-11 13:09 ` Kornel Dulęba
2023-04-11 13:29 ` Linux regression tracking (Thorsten Leemhuis)
2023-04-11 13:35 ` Kornel Dulęba
2023-04-11 13:43 ` Linux regression tracking (Thorsten Leemhuis)
2023-04-11 20:44 ` Linus Walleij
2023-04-12 10:47 ` Linux regression tracking (Thorsten Leemhuis)
2023-04-11 13:15 ` Greg KH [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=2023041152-desktop-breeze-0a89@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Basavaraj.Natikar@amd.com \
--cc=Shyam-sundar.S-k@amd.com \
--cc=korneld@chromium.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=mattedavis@google.com \
--cc=rad@semihalf.com \
--cc=regressions@lists.linux.dev \
--cc=richard.gong@amd.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=upstream@semihalf.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.