From: Borislav Petkov <bp@alien8.de>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
Coiby Xu <coiby.xu@gmail.com>, Ken Xue <Ken.Xue@amd.com>,
Nehal Shah <Nehal-bakulchandra.Shah@amd.com>,
Shyam Sundar S K <Shyam-sundar.S-k@amd.com>,
Daniel Drake <drake@endlessm.com>,
vectorflaredesigns@gmail.com,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
Hans de Goede <hdegoede@redhat.com>
Subject: Re: [Bug 212379] AMD GPIO chip IRQs stops working (ELN4690, WCOM51C7, BMA250E)
Date: Thu, 29 Apr 2021 16:58:20 +0200 [thread overview]
Message-ID: <YIrJjDggcPs5cRmA@zn.tnic> (raw)
In-Reply-To: <CACRpkdbT-GD=45ViysGpNSXWN+i9QA9=J8zgtPDkxCRyLKxm3g@mail.gmail.com>
On Thu, Apr 29, 2021 at 04:31:18PM +0200, Linus Walleij wrote:
> I have no clue, someone with deeper understanding of AMDs bridges
> and stuff need to look at this. Since it dies after a while I would
> suspect power management by the BIOS. (Off the top of my head.)
> SInce I guess these systems use BIOS ACPI for all PM.
>
> If someone from AMD could pick up this bug, that would be great.
Thanks for looking. I have it on a good authority that something like
that is happening now.
:-)
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
prev parent reply other threads:[~2021-04-29 14:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-212379-6385@https.bugzilla.kernel.org/>
[not found] ` <bug-212379-6385-VMOjMpWM97@https.bugzilla.kernel.org/>
2021-04-26 22:04 ` [Bug 212379] AMD GPIO chip IRQs stops working (ELN4690, WCOM51C7, BMA250E) Borislav Petkov
2021-04-27 14:10 ` Andy Shevchenko
2021-04-27 14:25 ` Andy Shevchenko
2021-04-27 23:42 ` Daniel Drake
2021-04-29 14:31 ` Linus Walleij
2021-04-29 14:58 ` Borislav Petkov [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=YIrJjDggcPs5cRmA@zn.tnic \
--to=bp@alien8.de \
--cc=Ken.Xue@amd.com \
--cc=Nehal-bakulchandra.Shah@amd.com \
--cc=Shyam-sundar.S-k@amd.com \
--cc=andy.shevchenko@gmail.com \
--cc=coiby.xu@gmail.com \
--cc=drake@endlessm.com \
--cc=hdegoede@redhat.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vectorflaredesigns@gmail.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