[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180420145521.GB30433@ziepe.ca>
Date: Fri, 20 Apr 2018 08:55:21 -0600
From: Jason Gunthorpe <jgg@...pe.ca>
To: "Deucher, Alexander" <Alexander.Deucher@....com>
Cc: Bjorn Helgaas <helgaas@...nel.org>,
Sinan Kaya <okaya@...eaurora.org>,
Bjorn Helgaas <bhelgaas@...gle.com>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
"sulrich@...eaurora.org" <sulrich@...eaurora.org>,
"timur@...eaurora.org" <timur@...eaurora.org>,
"linux-arm-msm@...r.kernel.org" <linux-arm-msm@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
Mike Marciniszyn <mike.marciniszyn@...el.com>,
Dennis Dalessandro <dennis.dalessandro@...el.com>,
Doug Ledford <dledford@...hat.com>,
"open list:HFI1 DRIVER" <linux-rdma@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/2] IB/hfi1: Try slot reset before secondary bus reset
On Thu, Apr 19, 2018 at 10:11:27PM +0000, Deucher, Alexander wrote:
> My understanding was that some platfoms only bring up the link in
> gen 1 mode for compatibility reasons. TBH, I'm not that familiar
> with how the links come up on different platforms.
Then the platform firmware or platform's linux PCI root complex driver
should perform speed negotiation.
Something like that shouldn't be a driver problem to solve.
The driver should only be involved if it has to alter the device (eg
new device firmware or something)..
Jason
Powered by blists - more mailing lists