From: "Pali Rohár" <pali@kernel.org>
To: "Bin Meng" <bmeng.cn@gmail.com>, "Simon Glass" <sjg@chromium.org>,
"Stefan Roese" <sr@denx.de>, "Marek Behún" <kabel@kernel.org>
Cc: u-boot@lists.denx.de
Subject: [PATCH 1/4] pci: Fix setting controller's last_busno
Date: Mon, 17 Jan 2022 16:38:37 +0100 [thread overview]
Message-ID: <20220117153840.31173-2-pali@kernel.org> (raw)
In-Reply-To: <20220117153840.31173-1-pali@kernel.org>
Initially it is set to dev_seq but update to the last bus number is
missing. Fix it.
Signed-off-by: Pali Rohár <pali@kernel.org>
---
drivers/pci/pci-uclass.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/pci/pci-uclass.c b/drivers/pci/pci-uclass.c
index 8c4d75bdb685..374b22601818 100644
--- a/drivers/pci/pci-uclass.c
+++ b/drivers/pci/pci-uclass.c
@@ -562,6 +562,8 @@ int pci_auto_config_devices(struct udevice *bus)
if (pplat->class == (PCI_CLASS_DISPLAY_VGA << 8))
set_vga_bridge_bits(dev);
}
+ if (hose->last_busno < sub_bus)
+ hose->last_busno = sub_bus;
debug("%s: done\n", __func__);
return log_msg_ret("sub", sub_bus);
--
2.20.1
next prev parent reply other threads:[~2022-01-17 15:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 15:38 [PATCH 0/4] pci: Extend 'pci' and 'pci regions' commands Pali Rohár
2022-01-17 15:38 ` Pali Rohár [this message]
2022-01-25 15:49 ` [PATCH 1/4] pci: Fix setting controller's last_busno Stefan Roese
2022-01-29 18:48 ` Tom Rini
2022-01-17 15:38 ` [PATCH 2/4] pci: Extend 'pci regions' command with bus number Pali Rohár
2022-01-25 15:53 ` Stefan Roese
2022-01-25 16:50 ` Pali Rohár
2022-01-26 15:43 ` Stefan Roese
2022-01-29 18:48 ` Tom Rini
2022-01-17 15:38 ` [PATCH 3/4] pci: Add checks for valid cmdline arguments Pali Rohár
2022-01-25 15:53 ` Stefan Roese
2022-01-29 18:48 ` Tom Rini
2022-01-17 15:38 ` [PATCH 4/4] pci: Extend 'pci' command with bus option '*' Pali Rohár
2022-01-25 15:53 ` Stefan Roese
2022-01-29 18:48 ` Tom Rini
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=20220117153840.31173-2-pali@kernel.org \
--to=pali@kernel.org \
--cc=bmeng.cn@gmail.com \
--cc=kabel@kernel.org \
--cc=sjg@chromium.org \
--cc=sr@denx.de \
--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.