1SMARTPQI(4)                Linux Programmer's Manual               SMARTPQI(4)
2
3
4

NAME

6       smartpqi - Microsemi Smart Family SCSI driver
7

SYNOPSIS

9       modprobe smartpqi [disable_device_id_wildcards={0|1}]
10                         [disable_heartbeat={0|1}]
11                         [disable_ctrl_shutdown={0|1}]
12                         [lockup_action={none|reboot|panic}]
13                         [expose_ld_first={0|1}] [hide_vsep={0|1}]
14

DESCRIPTION

16       smartpqi is a SCSI driver for Microsemi Smart Family controllers.
17
18   Supported ioctl() operations
19       For  compatibility  with  applications  written  for  the  cciss(4) and
20       hpsa(4) drivers, many, but not all of the ioctl(2) operations supported
21       by the hpsa driver are also supported by the smartpqi driver.  The data
22       structures used by these operations are described in the  Linux  kernel
23       source file include/linux/cciss_ioctl.h.
24
25       CCISS_DEREGDISK, CCISS_REGNEWDISK, CCISS_REGNEWD
26              These  operations  all  do  exactly  the same thing, which is to
27              cause the driver to re-scan for new devices.  This does  exactly
28              the  same  thing as writing to the smartpqi-specific host rescan
29              attribute.
30
31       CCISS_GETPCIINFO
32              This operation Returns the PCI domain, bus, device and  function
33              and "board ID" (PCI subsystem ID).
34
35       CCISS_GETDRIVVER
36              This operation returns the driver version in four bytes, encoded
37              as:
38
39                  (major_version << 28) | (minor_version << 24) |
40                          (release << 16) | revision
41
42       CCISS_PASSTHRU
43              Allows BMIC and CISS commands to be passed through to  the  con‐
44              troller.
45
46   Boot options
47       disable_device_id_wildcards={0|1}
48              Disables  support for device ID wildcards.  The default value is
49              0.
50
51       disable_heartbeat={0|1}
52              Disables support for the  controller's  heartbeat  check.   This
53              parameter  is used for debugging purposes.  The default value is
54              0, leaving the controller's heartbeat check active.
55
56       disable_ctrl_shutdown={0|1}
57              Disables support for shutting down the controller in  the  event
58              of a controller lockup.  The default value is 0.
59
60       lockup_action={none|reboot|panic}
61              Specifies  the  action the driver takes when a controller lockup
62              is detected.  The default action is none.
63
64              parameter   action
65              ─────────────────────────────────────────────
66
67              none        take controller offline only
68              reboot      reboot the system
69              panic       panic the system
70
71       expose_ld_first={0|1}
72              This option enables support for exposing logical devices to  the
73              operating  system before physical devices.  The default value is
74              0.
75
76       hide_vsep={0|1}
77              This option enables disabling exposure of the virtual SEP to the
78              host.   This  is usually associated with direct attached drives.
79              The default value is 0.
80

FILES

82   Device nodes
83       Logical drives are accessed via the SCSI disk driver (sd), tape  drives
84       via  the  SCSI  tape  driver (st), and the RAID controller via the SCSI
85       generic driver (sg), with device nodes named  /dev/sd*,  /dev/st*,  and
86       /dev/sg*, respectively.
87
88   SmartPQI-specific host attribute files in /sys
89       /sys/class/scsi_host/host*/rescan
90              The host rescan attribute is a write-only attribute.  Writing to
91              this attribute will cause the driver to scan for  new,  changed,
92              or removed devices (e.g., hot-plugged tape drives, or newly con‐
93              figured or deleted logical drives) and notify the SCSI mid-layer
94              of any changes detected.  Usually this action is triggered auto‐
95              matically by configuration changes, so the user should not  nor‐
96              mally  have  to write to this file.  Doing so may be useful when
97              hot-plugging devices such as tape drives or entire storage boxes
98              containing pre-configured logical drives.
99
100       /sys/class/scsi_host/host*/version
101              The  host  version  attribute  is  a  read-only attribute.  This
102              attribute  contains  the  driver  version  and  the   controller
103              firmware version.
104
105              For example:
106
107                  $ cat /sys/class/scsi_host/host1/version
108                  driver: 1.1.2-126
109                  firmware: 1.29-112
110
111       /sys/class/scsi_host/host*/lockup_action
112              The  host  lockup_action  attribute  is  a read/write attribute.
113              This attribute will cause  the  driver  to  perform  a  specific
114              action  in  the unlikely event that a controller lockup has been
115              detected.   See  OPTIONS  above  for  an  explanation   of   the
116              lockup_action values.
117
118       /sys/class/scsi_host/host*/driver_version
119              The  driver_version attribute is read-only.  This attribute con‐
120              tains the smartpqi driver version.
121
122              For example:
123
124                  $ cat /sys/class/scsi_host/host1/driver_version
125                  1.1.2-126
126
127       /sys/class/scsi_host/host*/firmware_version
128              The firmware_version attribute  is  read-only.   This  attribute
129              contains the controller firmware version.
130
131              For example:
132
133                  $ cat /sys/class/scsi_host/host1/firmware_version
134                  1.29-112
135
136       /sys/class/scsi_host/host*/model
137              The  model  attribute is read-only.  This attribute contains the
138              product identification string of the controller.
139
140              For example:
141
142                  $ cat /sys/class/scsi_host/host1/model
143                  1100-16i
144
145       /sys/class/scsi_host/host*/serial_number
146              The serial_number attribute is read-only.  This  attribute  con‐
147              tains the unique identification number of the controller.
148
149              For example:
150
151                  $ cat /sys/class/scsi_host/host1/serial_number
152                  6A316373777
153
154       /sys/class/scsi_host/host*/vendor
155              The  vendor attribute is read-only.  This attribute contains the
156              vendor identification string of the controller.
157
158              For example:
159
160                  $ cat /sys/class/scsi_host/host1/vendor
161                  Adaptec
162
163   SmartPQI-specific disk attribute files in /sys
164       In the file specifications below, c stands for the number of the appro‐
165       priate SCSI controller, b is the bus number, t the target number, and l
166       is the logical unit number (LUN).
167
168       /sys/class/scsi_disk/c:b:t:l/device/raid_level
169              The raid_level attribute is read-only.  This attribute  contains
170              the RAID level of each logical drive.
171
172              For example:
173
174                  $ cat /sys/class/scsi_disk/4:0:0:0/device/raid_level
175                  RAID 0
176
177       /sys/class/scsi_disk/c:b:t:l/device/sas_address
178              The sas_address attribute is read-only.  This attribute contains
179              the unique identifier of the disk.
180
181              For example:
182
183                  $ cat /sys/class/scsi_disk/1:0:3:0/device/sas_address
184                  0x5001173d028543a2
185
186       /sys/class/scsi_disk/c:b:t:l/device/ssd_smart_path_enabled
187              The  ssd_smart_path_enabled  attribute   is   read-only.    This
188              attribute is for ioaccel-enabled volumes.  (Ioaccel is an alter‐
189              native driver submission path that allows the driver to send I/O
190              requests  directly  to  backend SCSI devices, bypassing the con‐
191              troller firmware.  This results in an increase  in  performance.
192              This  method  is used for HBA disks and for logical volumes com‐
193              prised of SSDs.)  Contains 1 if ioaccel is enabled for the  vol‐
194              ume and 0 otherwise.
195
196              For example:
197
198                  $ cat /sys/class/scsi_disk/1:0:3:0/device/ssd_smart_path_enabled
199                  0
200

VERSIONS

202       The smartpqi driver was added in Linux 4.9.
203

NOTES

205   Configuration
206       To  configure  a  Microsemi  Smart Family controller, refer to the User
207       Guide for the controller, which can be found by searching for the  spe‐
208       cific controller at ⟨https://storage.microsemi.com/⟩.
209

SEE ALSO

211       cciss(4), hpsa(4), sd(4), st(4)
212
213       Documentation/ABI/testing/sysfs-bus-pci-devices-cciss in the Linux ker‐
214       nel source tree.
215

COLOPHON

217       This page is part of release 5.07 of the Linux  man-pages  project.   A
218       description  of  the project, information about reporting bugs, and the
219       latest    version    of    this    page,    can     be     found     at
220       https://www.kernel.org/doc/man-pages/.
221
222
223
224Linux                             2019-10-10                       SMARTPQI(4)
Impressum