forked from Minki/linux
a470a51cd6
In-order to handle this 'MPI2_EVENT_ACTIVE_CABLE_EXCEPTION' event, driver need to follow below steps, 1. Unmask the 'MPI2_EVENT_ACTIVE_CABLE_EXCEPTION' event, so that FW can notify this event to host driver. 2. After receiving this event, add this event to AEN event queue, for notifying this event to applications. 3. Then Print below message in kernel logs if the event data's reason code is zero, "Currently an active cable with ReceptacleID <ID_Value> cannot be powered and devices connected to this active cable will not be seen. This active cable requires <PowerValue_in_mW> of power" This event is only for Intruder/Cutlass HBAs. Signed-off-by: Chaitra P B <chaitra.basappa@broadcom.com> Reviewed-by: Tomas Henzl <thenzl@redhat.com> Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com> |
||
---|---|---|
.. | ||
mpi | ||
Kconfig | ||
Makefile | ||
mpt3sas_base.c | ||
mpt3sas_base.h | ||
mpt3sas_config.c | ||
mpt3sas_ctl.c | ||
mpt3sas_ctl.h | ||
mpt3sas_debug.h | ||
mpt3sas_scsih.c | ||
mpt3sas_transport.c | ||
mpt3sas_trigger_diag.c | ||
mpt3sas_trigger_diag.h | ||
mpt3sas_warpdrive.c |