From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S971063AbdEZKJY (ORCPT ); Fri, 26 May 2017 06:09:24 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:40723 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1761857AbdEZKJX (ORCPT ); Fri, 26 May 2017 06:09:23 -0400 Date: Fri, 26 May 2017 12:09:20 +0200 (CEST) From: Thomas Gleixner To: Kai-Heng Feng cc: linus.walleij@linaro.org, linux-gpio@vger.kernel.org, LKML , Borislav Petkov Subject: Re: [PATCH] pinctrl: amd: don't load pinctrl-amd on Gigabyte AM4 boards In-Reply-To: <20170525040006.22654-1-kai.heng.feng@canonical.com> Message-ID: References: <20170525040006.22654-1-kai.heng.feng@canonical.com> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. There is a proper solution to this problem: http://lkml.kernel.org/r/alpine.DEB.2.20.1705232307330.2409@nanos Thanks, tglx