summaryrefslogtreecommitdiff
path: root/Kconfig
diff options
context:
space:
mode:
authorNiklas Schnelle <schnelle@linux.ibm.com>2021-03-26 15:58:48 +0300
committerHeiko Carstens <hca@linux.ibm.com>2021-04-12 13:46:42 +0300
commit61311e32892b008886478bdba4ce2a34f4d938f8 (patch)
treeb8e88fbcf8422e6347d0c33d6a83f755dc425f1d /Kconfig
parent14c87ba8123abe6b707d04e1711eef90653567f2 (diff)
downloadlinux-61311e32892b008886478bdba4ce2a34f4d938f8.tar.xz
s390/pci: narrow scope of zpci_configure_device()
Currently zpci_configure_device() can be called on a zPCI function in two completely different states. Either the underlying zPCI function has already been configured by the platform and we are only doing the scanning to get it usable by Linux drivers. Or the underlying function is in Standby and we first do an SCLP to get it configured. This makes zpci_configure_device() harder to reason about. Since calling zpci_configure_device() on a function in Standby only happens in enable_slot() simply pull out the SCLP call and setting of zdev->state and thus call zpci_configure_device() under the same circumstances as in the event handling code. Reviewed-by: Matthew Rosato <mjrosato@linux.ibm.com> Reviewed-by: Pierre Morel <pmorel@linux.ibm.com> Signed-off-by: Niklas Schnelle <schnelle@linux.ibm.com> Signed-off-by: Heiko Carstens <hca@linux.ibm.com>
Diffstat (limited to 'Kconfig')
0 files changed, 0 insertions, 0 deletions