[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180430213826.GA6046@wunner.de>
Date: Mon, 30 Apr 2018 23:38:26 +0200
From: Lukas Wunner <lukas@...ner.de>
To: Sinan Kaya <okaya@...eaurora.org>
Cc: Bjorn Helgaas <helgaas@...nel.org>,
Paul Menzel <pmenzel+linux-pci@...gen.mpg.de>,
Dave Young <dyoung@...hat.com>, linux-pci@...r.kernel.org,
kexec@...ts.infradead.org, linux-kernel@...r.kernel.org,
Eric Biederman <ebiederm@...ssion.com>,
Bjorn Helgaas <bhelgaas@...gle.com>,
Vivek Goyal <vgoyal@...hat.com>
Subject: Re: pciehp 0000:00:1c.0:pcie004: Timeout on hotplug command 0x1038
(issued 65284 msec ago)
On Mon, Apr 30, 2018 at 05:27:32PM -0400, Sinan Kaya wrote:
> On 4/30/2018 5:17 PM, Bjorn Helgaas wrote:
> How about remove() only if MSI is disabled? Most root port interrupts
> are MSI based anyhow.
I think the code is perfectly fine as it is and doesn't need to nor
should be modified. We should just add a quirk for this particular
chipset that it doesn't support Command Completed interrupts (if that's
what's broken). In the case of Thunderbolt controllers, the first few
had the NoCompl bit set incorrectly in config space and Intel hardware
engineers confirmed the error. These or similar oddities may occur
with more chipsets, so I propose moving existing quirks to a
separate file, thereby avoiding that they clutter generic code.
The blinkenlights feature added with commit 576243b3f9ea is a similar
quirk that could be moved to a separate pciehp_quirks.c file.
Thanks,
Lukas
Powered by blists - more mailing lists