diff options
| author | Yinghai Lu <yinghai@kernel.org> | 2011-05-12 17:11:37 -0700 |
|---|---|---|
| committer | Jesse Barnes <jbarnes@virtuousgeek.org> | 2011-05-21 12:17:11 -0700 |
| commit | da7822e5ad71ec9b745b412639f1e5e0ba795a20 (patch) | |
| tree | 605722e2c2b32fd6450bc91718ac7b4240fcba6c /drivers/pci/pci-sysfs.c | |
| parent | f8fcfd775523347afe460dc3a0f45d0479e784a2 (diff) | |
| download | kernel_samsung_smdk4412-da7822e5ad71ec9b745b412639f1e5e0ba795a20.zip kernel_samsung_smdk4412-da7822e5ad71ec9b745b412639f1e5e0ba795a20.tar.gz kernel_samsung_smdk4412-da7822e5ad71ec9b745b412639f1e5e0ba795a20.tar.bz2 | |
PCI: update bridge resources to get more big ranges when allocating space (again)
With Ram's fixes, this should be safe to do again. So let's give it
another try.
BIOS separates IO ranges between several IOHs, and on some slots, BIOS
assigns resources to a bridge, but stops assigning resources to the
device under that bridge, because the device needs a big resource.
So:
1. allocate resources and record the failed device resources
2. clear the BIOS assigned resources of the parent bridge of failing device
3. go back and call pci assign unassigned
4. if it still fails, go up the tree, clear more bridges. and try again
Now Ram's allocate requested resource already got into mainline. could
put this one again.
Reviewed-by: Ram Pai <linuxram@us.ibm.com>
Signed-off-by: Yinghai Lu <yinghai@kernel.org>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Diffstat (limited to 'drivers/pci/pci-sysfs.c')
0 files changed, 0 insertions, 0 deletions