From: Deng-Cheng Zhu <dczhu@mips.com>
To: bhelgaas@google.com, jbarnes@virtuousgeek.org,
ralf@linux-mips.org, monstr@monstr.eu, benh@kernel.crashing.org,
paulus@samba.org, davem@davemloft.net, tglx@linutronix.de,
mingo@redhat.com, hpa@zytor.com, x86@kernel.org
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mips@linux-mips.org, eyal@mips.com, zenon@mips.com,
dczhu@mips.com, dengcheng.zhu@gmail.com
Subject: [RESEND PATCH v3 0/2] Pass resources to pci_create_bus() and fix MIPS PCI resources
Date: Thu, 1 Sep 2011 10:48:27 +0800 [thread overview]
Message-ID: <1314845309-3277-1-git-send-email-dczhu@mips.com> (raw)
Message-ID: <20110901024827.E074QgE7qCw7TDhGVR5KmKx1OLJpojI4sWdH9lKx0JQ@z> (raw)
(Resending the patch set to include more arch maintainers.)
Change the pci_create_bus() interface to pass in available resources to get them
settled down early. This is to avoid possible resource conflicts while doing
pci_scan_slot() in pci_scan_child_bus(). Note that pcibios_fixup_bus() can get
rid of such conflicts, but it's done AFTER scanning slots.
In addition, MIPS PCI resources are now fixed using this new interface.
-- Changes --
v3 - v2:
o Do not do fixups for root buses in pcibios_fixup_bus().
o Skip bus creation when bus resources cannot be allocated.
o PCI domain/bus numbers added to the error info in controller_resources().
v2 - v1:
o Merge [PATCH 1/3] to [PATCH 3/3], so now 2 patches in total.
o Add more info to patch description.
o Fix arch breaks in default resource setup discovered by Bjorn Helgaas.
Deng-Cheng Zhu (2):
PCI: Pass available resources into pci_create_bus()
MIPS: PCI: Pass controller's resources to pci_create_bus() in
pcibios_scanbus()
arch/microblaze/pci/pci-common.c | 3 +-
arch/mips/pci/pci.c | 61 +++++++++++++++++++++++++++++++++-----
arch/powerpc/kernel/pci-common.c | 3 +-
arch/sparc/kernel/pci.c | 3 +-
arch/x86/pci/acpi.c | 2 +-
drivers/pci/probe.c | 15 +++++++--
include/linux/pci.h | 3 +-
7 files changed, 73 insertions(+), 17 deletions(-)
next reply other threads:[~2011-09-01 2:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-01 2:48 Deng-Cheng Zhu [this message]
2011-09-01 2:48 ` [RESEND PATCH v3 0/2] Pass resources to pci_create_bus() and fix MIPS PCI resources Deng-Cheng Zhu
2011-09-01 2:48 ` [RESEND PATCH v3 1/2] PCI: Pass available resources into pci_create_bus() Deng-Cheng Zhu
2011-09-01 2:48 ` Deng-Cheng Zhu
2011-09-01 2:48 ` [RESEND PATCH v3 2/2] MIPS: PCI: Pass controller's resources to pci_create_bus() in pcibios_scanbus() Deng-Cheng Zhu
2011-09-01 2:48 ` Deng-Cheng Zhu
2011-10-07 21:50 ` [RESEND PATCH v3 0/2] Pass resources to pci_create_bus() and fix MIPS PCI resources Bjorn Helgaas
2011-10-10 21:04 ` Bjorn Helgaas
2011-10-10 23:49 ` Zhu, DengCheng
2011-10-11 7:48 ` Benjamin Herrenschmidt
2011-10-11 16:15 ` Bjorn Helgaas
2011-11-02 21:14 ` Jesse Barnes
2011-11-02 21:37 ` Bjorn Helgaas
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=1314845309-3277-1-git-send-email-dczhu@mips.com \
--to=dczhu@mips.com \
--cc=benh@kernel.crashing.org \
--cc=bhelgaas@google.com \
--cc=davem@davemloft.net \
--cc=dengcheng.zhu@gmail.com \
--cc=eyal@mips.com \
--cc=hpa@zytor.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-pci@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=monstr@monstr.eu \
--cc=paulus@samba.org \
--cc=ralf@linux-mips.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=zenon@mips.com \
/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.