summaryrefslogtreecommitdiffstats
path: root/arch/arm/mach-orion5x/kurobox_pro-setup.c
diff options
context:
space:
mode:
authorLennert Buytenhek <buytenh@wantstofly.org>2008-06-26 17:12:50 +0200
committerNicolas Pitre <nico@cam.org>2008-06-30 16:04:44 -0400
commitda01bba3cb8814b17d809e09c301e1dad86fec87 (patch)
tree0605379dac7ae8b9de458b2d46230c839b319c34 /arch/arm/mach-orion5x/kurobox_pro-setup.c
parent1338760329c586e0141831099e15f5c336dd9c1d (diff)
downloadblackbird-op-linux-da01bba3cb8814b17d809e09c301e1dad86fec87.tar.gz
blackbird-op-linux-da01bba3cb8814b17d809e09c301e1dad86fec87.zip
[ARM] Orion: make PCI handling code deal with Cardbus slots
The Cardbus connector does not have an IDSEL signal, and Cardbus cards are always the intended target of configuration transactions on their local PCI bus. This means that if the Orion's PCI bus signals are hooked up to a Cardbus slot, the same set of PCI functions will will appear 31 times, for each of the PCI device IDs 1-31 (ID 0 is the host bridge). This patch adds a function to the Orion PCI handling code that board support code can call to enable Cardbus mode. When Cardbus mode is enabled, configuration transactions on the PCI local bus are only allowed to PCI IDs 0 (host bridge) and 1 (cardbus device). Signed-off-by: Lennert Buytenhek <buytenh@marvell.com>
Diffstat (limited to 'arch/arm/mach-orion5x/kurobox_pro-setup.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud