From: Thomas Gleixner <tglx@linutronix.de>
To: Borislav Petkov <bp@alien8.de>
Cc: "Shah, Nehal-bakulchandra" <Nehal-bakulchandra.Shah@amd.com>,
LKML <linux-kernel@vger.kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"Xue, Ken" <Ken.Xue@amd.com>,
"S-k, Shyam-sundar" <Shyam-sundar.S-k@amd.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] pinctrl/amd: Use regular interrupt instead of chained
Date: Tue, 20 Jun 2017 11:22:05 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1706201120190.1869@nanos> (raw)
In-Reply-To: <20170619161323.pjdrh6l33pqix32x@pd.tnic>
On Mon, 19 Jun 2017, Borislav Petkov wrote:
> On Fri, May 26, 2017 at 09:33:10AM +0000, Shah, Nehal-bakulchandra wrote:
> > Hi Thomas,
> >
> > Thanks for the prompt reply. Agree on points.
> >
> > we will validate at our end and shall provide the update.
>
> Any news on the issue? Resolution?
>
> I still have a user reporting "irq 7: nobody cared (try booting with the
> "irqpoll" option)" pointing to amd_gpio_irq_handler(), even with Thomas'
> patch.
>
> See https://bugzilla.suse.com/show_bug.cgi?id=1034261
>
> So something's still not completely fine yet.
Well, that's kinda expected.
If the interrupt _IS_ screaming because the hardware is buggered, then the
nobody cared thing will detect it and switch it off. That's all what we can
do, aside of not loading the driver at all.
But that's way better than silently locking up the box forever.
Thanks
tglx
next prev parent reply other threads:[~2017-06-20 9:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.DEB.2.20.1705232307330.2409@nanos>
[not found] ` <BLUPR12MB07212D4797B68DB06C3A6D40A0FC0@BLUPR12MB0721.namprd12.prod.outlook.com>
2017-05-26 6:48 ` [PATCH] pinctrl/amd: Use regular interrupt instead of chained Thomas Gleixner
2017-05-26 9:33 ` Shah, Nehal-bakulchandra
2017-05-26 9:57 ` Borislav Petkov
2017-06-19 16:13 ` Borislav Petkov
2017-06-20 9:22 ` Thomas Gleixner [this message]
2017-06-20 9:29 ` Borislav Petkov
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=alpine.DEB.2.20.1706201120190.1869@nanos \
--to=tglx@linutronix.de \
--cc=Ken.Xue@amd.com \
--cc=Nehal-bakulchandra.Shah@amd.com \
--cc=Shyam-sundar.S-k@amd.com \
--cc=bp@alien8.de \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.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