From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bin Meng Date: Sat, 23 Nov 2019 20:54:42 +0800 Subject: [U-Boot] [PATCH 1/3] drivers: pci: Fix Host bridge bus number issue In-Reply-To: <20191122222323.28898-2-vladimir.olovyannikov@broadcom.com> References: <20191122222323.28898-1-vladimir.olovyannikov@broadcom.com> <20191122222323.28898-2-vladimir.olovyannikov@broadcom.com> Message-ID: List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Hi Vladimir, On Sat, Nov 23, 2019 at 6:23 AM Vladimir Olovyannikov wrote: > > From: Srinath Mannam > > Add changes to fix bus number of host bridge is set with device > sequence number issue. > All devices are managed using device sequence number. For PCIe, > devices enabled in DTS are added under PCIE_CLASS with consecutive > device sequence numbers to scan all pcie devices in sequence using > device sequence number. If a device is a bridge then it will enumerate > all endpoints in that bridge, and give sequence numbers in that order. > However, the parent device is a root bridge. > The solution is all bus numbers are device sequence number minus > root bridge sequence number. This way, every root bridge and its > downstream EPs bus numbers start from 0. > So root bridges are different hierarchy of bus numbers. Could you please give an example for better understanding? > > Signed-off-by: Srinath Mannam > Signed-off-by: Vladimir Olovyannikov > --- > drivers/pci/pci-uclass.c | 8 +++++--- > drivers/pci/pci_auto.c | 6 +++++- > 2 files changed, 10 insertions(+), 4 deletions(-) > Regards, Bin