All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bin Meng <bmeng.cn@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/3] drivers: pci: Fix Host bridge bus number issue
Date: Sat, 23 Nov 2019 20:54:42 +0800	[thread overview]
Message-ID: <CAEUhbmXKWZR3XKfryPgxb_ctKZL6uKcP902f_TYdua6LC264yQ@mail.gmail.com> (raw)
In-Reply-To: <20191122222323.28898-2-vladimir.olovyannikov@broadcom.com>

Hi Vladimir,

On Sat, Nov 23, 2019 at 6:23 AM Vladimir Olovyannikov
<vladimir.olovyannikov@broadcom.com> wrote:
>
> From: Srinath Mannam <srinath.mannam@broadcom.com>
>
> 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 <srinath.mannam@broadcom.com>
> Signed-off-by: Vladimir Olovyannikov <vladimir.olovyannikov@broadcom.com>
> ---
>  drivers/pci/pci-uclass.c | 8 +++++---
>  drivers/pci/pci_auto.c   | 6 +++++-
>  2 files changed, 10 insertions(+), 4 deletions(-)
>

Regards,
Bin

  reply	other threads:[~2019-11-23 12:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-22 22:23 [U-Boot] [PATCH 0/3] Introduce APIs for multi PCIe host controller platforms Vladimir Olovyannikov
2019-11-22 22:23 ` [U-Boot] [PATCH 1/3] drivers: pci: Fix Host bridge bus number issue Vladimir Olovyannikov
2019-11-23 12:54   ` Bin Meng [this message]
2019-11-22 22:23 ` [U-Boot] [PATCH 2/3] drivers: core: uclass: Get next device fail with driver probe fail Vladimir Olovyannikov
2019-11-23 12:54   ` Bin Meng
2019-11-22 22:23 ` [U-Boot] [PATCH 3/3] drivers: pci: pci-uclass: Get PCI dma regions support Vladimir Olovyannikov
2019-11-23 12:54   ` Bin Meng

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAEUhbmXKWZR3XKfryPgxb_ctKZL6uKcP902f_TYdua6LC264yQ@mail.gmail.com \
    --to=bmeng.cn@gmail.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.