aboutsummaryrefslogtreecommitdiffstats
path: root/net/8021q
diff options
context:
space:
mode:
authorBenjamin Herrenschmidt <benh@kernel.crashing.org>2011-04-11 11:37:07 +1000
committerBenjamin Herrenschmidt <benh@kernel.crashing.org>2011-06-08 09:08:17 +1000
commit98d9f30c820d509145757e6ecbc36013aa02f7bc (patch)
treedd5da915d991352ced56ed849612029339f64198 /net/8021q
parent1fa7b6a29c61358cc2ca6f64cef4aa0e1a7ca74c (diff)
downloadkernel_goldelico_gta04-98d9f30c820d509145757e6ecbc36013aa02f7bc.zip
kernel_goldelico_gta04-98d9f30c820d509145757e6ecbc36013aa02f7bc.tar.gz
kernel_goldelico_gta04-98d9f30c820d509145757e6ecbc36013aa02f7bc.tar.bz2
pci/of: Match PCI devices to OF nodes dynamically
powerpc has two different ways of matching PCI devices to their corresponding OF node (if any) for historical reasons. The ppc64 one does a scan looking for matching bus/dev/fn, while the ppc32 one does a scan looking only for matching dev/fn on each level in order to be agnostic to busses being renumbered (which Linux does on some platforms). This removes both and instead moves the matching code to the PCI core itself. It's the most logical place to do it: when a pci_dev is created, we know the parent and thus can do a single level scan for the matching device_node (if any). The benefit is that all archs now get the matching for free. There's one hook the arch might want to provide to match a PHB bus to its device node. A default weak implementation is provided that looks for the parent device device node, but it's not entirely reliable on powerpc for various reasons so powerpc provides its own. Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org> Acked-by: Michal Simek <monstr@monstr.eu> Acked-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Diffstat (limited to 'net/8021q')
0 files changed, 0 insertions, 0 deletions