diff options
author | Mario Limonciello <mario.limonciello@dell.com> | 2017-11-09 20:49:10 +0300 |
---|---|---|
committer | Darren Hart (VMware) <dvhart@infradead.org> | 2017-11-17 04:45:26 +0300 |
commit | 868b8d33f91e431b1961a35baa6b5022639067f3 (patch) | |
tree | a49852abaa758657c61145842cfd73094f0bd3e9 /drivers/s390/scsi/zfcp_ccw.c | |
parent | 8b9528a6d9a901b9f933231505fef5630e80ce5a (diff) | |
download | linux-868b8d33f91e431b1961a35baa6b5022639067f3.tar.xz |
platform/x86: dell-*wmi*: Relay failed initial probe to dependent drivers
dell-wmi and dell-smbios-wmi are dependent upon dell-wmi-descriptor
finishing probe successfully to probe themselves.
Currently if dell-wmi-descriptor fails probing in a non-recoverable way
(such as invalid header) dell-wmi and dell-smbios-wmi will continue to
try to redo probing due to deferred probing.
To solve this have the dependent drivers query the dell-wmi-descriptor
driver whether the descriptor has been determined valid. The possible
results are:
-ENODEV: Descriptor GUID missing from WMI bus
-EPROBE_DEFER: Descriptor not yet probed, dependent driver should wait
and use deferred probing
< 0: Descriptor probed, invalid. Dependent driver should return an
error.
0: Successful descriptor probe, dependent driver can continue
Successful descriptor probe still doesn't mean that the descriptor driver
is necessarily bound at the time of initialization of dependent driver.
Userspace can unbind the driver, so all methods used from driver
should still be verified to return success values otherwise deferred
probing be used.
Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
Reviewed-by: Pali Rohár <pali.rohar@gmail.com>
Signed-off-by: Darren Hart (VMware) <dvhart@infradead.org>
Diffstat (limited to 'drivers/s390/scsi/zfcp_ccw.c')
0 files changed, 0 insertions, 0 deletions