staging/rdma/hfi1: Avoid using upstream component if it is not accessible
authorKaike Wan <kaike.wan@intel.com>
Fri, 26 Feb 2016 21:33:18 +0000 (13:33 -0800)
committerDoug Ledford <dledford@redhat.com>
Fri, 11 Mar 2016 01:45:46 +0000 (20:45 -0500)
commitbf400235f392eabf60c865c95da823727cb00def
tree24faafd6e639139752adb78b367cb8bae039aadc
parentaa0ad411e51763f95afdae11d6ee684915faecef
staging/rdma/hfi1: Avoid using upstream component if it is not accessible

When the hfi1 device is assigned to a VM (eg KVM), the hfi1 driver has
no access to the upstream component and therefore cannot use it to perform
some operations, such as secondary bus reset. As a result, the hfi1 driver
cannot perform the pcie Gen3 transition. Instead, those operation should
be done in the host environment, preferrably done during the Option ROM
initialization. Similarly, the hfi1 driver cannot support ASPM and tune
the pcie capability under this circumstance.

Reviewed-by: Mike Marciniszyn <mike.marciniszyn@intel.com>
Reviewed-by: Dennis Dalessandro <dennis.dalessandro@intel.com>
Signed-off-by: Kaike Wan <kaike.wan@intel.com>
Signed-off-by: Doug Ledford <dledford@redhat.com>
drivers/staging/rdma/hfi1/aspm.h
drivers/staging/rdma/hfi1/pcie.c