All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kai-Heng Feng <kai.heng.feng@canonical.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linus.walleij@linaro.org, linux-gpio@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>,
	Borislav Petkov <bp@alien8.de>
Subject: Re: [PATCH] pinctrl: amd: don't load pinctrl-amd on Gigabyte AM4 boards
Date: Fri, 26 May 2017 18:18:51 +0800	[thread overview]
Message-ID: <CAAd53p75fbX7gJe9jkzkYVLTmn5SRq9AH5SBf6avhDYQNFOMyw@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1705261206180.1902@nanos>

On Fri, May 26, 2017 at 6:09 PM, Thomas Gleixner <tglx@linutronix.de> wrote:
> On Thu, 25 May 2017, Kai-Heng Feng wrote:
>
>> On Gigabyte AM4 boards, pinctrl-amd generates tons of irq, makes the
>> system not able to boot properly.
>>
>> Don't load the module until Gigabyte fixes the issue.
>
> NAK.
>
> That's the completely wrong approach. This crap will surface on a gazillion
> of other boards and will hit users faster than you can keep that DMI list
> up to date.

Yea. I'll try to understand your patch, and hopefully I can find
correct solutions next time.

>
> There is a proper solution to this problem:
>
> http://lkml.kernel.org/r/alpine.DEB.2.20.1705232307330.2409@nanos

Wow, this is great news for Gigabyte AM4 users!

Thanks for the patch, I'll build a custom Ubuntu kernel and get
feedback from users.

>
> Thanks,
>
>         tglx

      reply	other threads:[~2017-05-26 10:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-25  4:00 [PATCH] pinctrl: amd: don't load pinctrl-amd on Gigabyte AM4 boards Kai-Heng Feng
2017-05-26 10:09 ` Thomas Gleixner
2017-05-26 10:18   ` Kai-Heng Feng [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=CAAd53p75fbX7gJe9jkzkYVLTmn5SRq9AH5SBf6avhDYQNFOMyw@mail.gmail.com \
    --to=kai.heng.feng@canonical.com \
    --cc=bp@alien8.de \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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.