diff options
| author | Chaitra P B <[email protected]> | 2018-04-24 05:28:41 -0400 |
|---|---|---|
| committer | Martin K. Petersen <[email protected]> | 2018-05-08 00:39:49 -0400 |
| commit | c1a6c5ac4278d406c112cc2f038e6e506feadff9 (patch) | |
| tree | 4bbd8b6fa1b89ca29b05369db062b131ac309018 /tools/perf/scripts/python | |
| parent | 65928d1f4130a48732034c2f31b2b0790694537f (diff) | |
scsi: mpt3sas: For NVME device, issue a protocol level reset
1) Manufacturing Page 11 contains parameters to control internal
firmware behavior. Based on AddlFlags2 field FW/Driver behaviour can
be changed, (flag tm_custom_handling is used for this)
a) For PCIe device, protocol level reset should be used if flag
tm_custom_handling is 0. Since Abort Task Set, LUN reset and Target
reset will result in a protocol level reset. Drivers should issue
only one type of this reset, if that fails then it should escalate to
a controller reset (diag reset/OCR).
b) If the driver has control over the TM reset timeout value, then
driver should use the value exposed in PCIe Device Page 2 for pcie
device (field ControllerResetTO).
Signed-off-by: Chaitra P B <[email protected]>
Signed-off-by: Suganath Prabu S <[email protected]>
Signed-off-by: Martin K. Petersen <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions