On Fri, May 26, 2017 at 6:09 PM, Thomas Gleixner 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.
>
>
On Fri, May 26, 2017 at 6:09 PM, Thomas Gleixner 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
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
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
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.
BugLink: https://bugs.launchpad.net/bugs/1671360
Signed-off-by: Kai-Heng Feng
---
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.
BugLink: https://bugs.launchpad.net/bugs/1671360
Signed-off-by: Kai-Heng Feng
---
drivers/pinctrl/pinctrl-amd.c | 25
6 matches
Mail list logo