[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 11 Dec 2013 16:21:09 -0800
From: Yinghai Lu <yinghai@...nel.org>
To: Andreas Noever <andreas.noever@...il.com>
Cc: "linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: How to reserve pci bus numbers for hotplug?
On Wed, Dec 11, 2013 at 3:37 PM, Andreas Noever
<andreas.noever@...il.com> wrote:
> If I could get Linux to assign enough resources (bus numbers for now)
> then I could drop the acpi_osi parameter and make thunderbolt work
> after suspend... So, is there an easy way to fix this? (Quirks,
> reconfiguring bus number assignments from a platform driver, ...?)
please check if busn_alloc at
git://git.kernel.org/pub/scm/linux/kernel/git/yinghai/linux-yinghai.git
for-pci-busn-alloc-3.14
could help.
resources: Split out __allocate_resource()
resources: Add resource_shrink_parents_top()
resources: Add probe_resource()
resources: Replace registered resource in tree.
PCI: Add pci_bus_extend/shrink_top()
PCI: Probe safe range that we can use for unassigned bridge.
PCI: Add pci_bus_replace_busn_res()
PCI: Allocate bus range instead of use max blindly
PCI: Strict checking of valid range for bridge
PCI: Kill pci_fixup_parent_subordinate_busnr()
PCI: Seperate child bus scanning to two passes overall
pcmcia: Remove workaround for fixing pci parent bus subordinate
PCI, pciehp: Remove not needed bus number range checking
PCI: More strict checking of valid range for bridge
PCI: Don't shrink too much for hotplug bridge
expand_bus_for_sriov
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists