diff options
| author | Gavin Shan <shangw@linux.vnet.ibm.com> | 2013-11-04 16:32:47 +0800 |
|---|---|---|
| committer | Benjamin Herrenschmidt <benh@kernel.crashing.org> | 2013-11-06 14:13:52 +1100 |
| commit | 36954dc78d8a1dcd4780cf4bd0fc6292791821b9 (patch) | |
| tree | 896bea4d43edad65577bd4e061fa846bd57df786 /drivers/usb/host/Kconfig | |
| parent | 631ad691b5818291d89af9be607d2fe40be0886e (diff) | |
| download | kernel-common-36954dc78d8a1dcd4780cf4bd0fc6292791821b9.tar.gz kernel-common-36954dc78d8a1dcd4780cf4bd0fc6292791821b9.tar.bz2 kernel-common-36954dc78d8a1dcd4780cf4bd0fc6292791821b9.zip | |
powerpc/powernv: Reserve the correct PE number
We're assigning PE numbers after the completion of PCI probe. During
the PCI probe, we had PE#0 as the super container to encompass all
PCI devices. However, that's inappropriate since PELTM has ascending
order of priority on search on P7IOC. So we need PE#127 takes the
role that PE#0 has previously. For PHB3, we still have PE#0 as the
reserved PE.
The patch supposes that the underly firmware has built the RID to
PE# mapping after resetting IODA tables: all PELTM entries except
last one has invalid mapping on P7IOC, but all RTEs have binding
to PE#0. The reserved PE# is being exported by firmware by device
tree.
Signed-off-by: Gavin Shan <shangw@linux.vnet.ibm.com>
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Diffstat (limited to 'drivers/usb/host/Kconfig')
0 files changed, 0 insertions, 0 deletions