From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marek Behun Date: Fri, 10 May 2019 13:44:01 +0200 Subject: [U-Boot] [PATCH 1/1] pci: pci_mvebu: ignore the local device In-Reply-To: References: <20190510025611.4296-1-marek.behun@nic.cz> Message-ID: <20190510134401.03701045@nic.cz> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: u-boot@lists.denx.de On Fri, 10 May 2019 10:15:25 +0200 Stefan Roese wrote: > On 10.05.19 04:56, Marek Beh=C3=BAn wrote: > > The local device (host "bridge"?) on pci_mvebu controller reports > > PCI_CLASS_MEMORY_OTHER in the class register. > >=20 > > This does not work in U-Boot, because U-Boot then tries to autoconfigure > > this device in pci_auto.c. This causes the real connected PCIe device > > not to work (in U-Boot nor in Linux). =20 >=20 > What exactly does not work or is the issue here with the current > implementation in Linux? I'm asking, since we have not noticed any > issues here? >=20 ath10k firmware fails to load for network device. SATA device timeouts on a PCIe SATA expander. As if some PCIe I/O did not work. The devices are still enumerated and recognized by Linux, but simply won't work. Nor in U-Boot.