€•›@Œsphinx.addnodes”Œdocument”“”)”}”(Œ rawsource”Œ”Œchildren”]”(Œ translations”Œ LanguagesNode”“”)”}”(hhh]”(hŒ pending_xref”“”)”}”(hhh]”Œdocutils.nodes”ŒText”“”ŒChinese (Simplified)”…””}”Œparent”hsbaŒ attributes”}”(Œids”]”Œclasses”]”Œnames”]”Œdupnames”]”Œbackrefs”]”Œ refdomain”Œstd”Œreftype”Œdoc”Œ reftarget”Œ!/translations/zh_CN/scsi/smartpqi”Œmodname”NŒ classname”NŒ refexplicit”ˆuŒtagname”hhh ubh)”}”(hhh]”hŒChinese (Traditional)”…””}”hh2sbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ!/translations/zh_TW/scsi/smartpqi”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒItalian”…””}”hhFsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ!/translations/it_IT/scsi/smartpqi”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒJapanese”…””}”hhZsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ!/translations/ja_JP/scsi/smartpqi”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒKorean”…””}”hhnsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ!/translations/ko_KR/scsi/smartpqi”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒSpanish”…””}”hh‚sbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ!/translations/sp_SP/scsi/smartpqi”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubeh}”(h]”h ]”h"]”h$]”h&]”Œcurrent_language”ŒEnglish”uh1h hhŒ _document”hŒsource”NŒline”NubhŒcomment”“”)”}”(hŒ SPDX-License-Identifier: GPL-2.0”h]”hŒ SPDX-License-Identifier: GPL-2.0”…””}”hh£sbah}”(h]”h ]”h"]”h$]”h&]”Œ xml:space”Œpreserve”uh1h¡hhhžhhŸŒ;/var/lib/git/docbuild/linux/Documentation/scsi/smartpqi.rst”h KubhŒsection”“”)”}”(hhh]”(hŒtitle”“”)”}”(hŒ.SMARTPQI - Microchip Smart Storage SCSI driver”h]”hŒ.SMARTPQI - Microchip Smart Storage SCSI driver”…””}”(hh»hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hh¶hžhhŸh³h KubhŒ paragraph”“”)”}”(hXThis file describes the smartpqi SCSI driver for Microchip (http://www.microchip.com) PQI controllers. The smartpqi driver is the next generation SCSI driver for Microchip Corp. The smartpqi driver is the first SCSI driver to implement the PQI queuing model.”h]”(hŒFor more information on the PQI Queuing Interface, please see:”h]”hŒ>For more information on the PQI Queuing Interface, please see:”…””}”(hj hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Khh¶hžhubhŒ bullet_list”“”)”}”(hhh]”(hŒ list_item”“”)”}”(hŒhttp://www.t10.org/drafts.htm”h]”hÊ)”}”(hj!h]”hÔ)”}”(hj!h]”hŒhttp://www.t10.org/drafts.htm”…””}”(hj&hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”j!uh1hÓhj#ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Khjubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjhžhhŸh³h Nubj)”}”(hŒ&http://www.t10.org/members/w_pqi2.htm ”h]”hÊ)”}”(hŒ%http://www.t10.org/members/w_pqi2.htm”h]”hÔ)”}”(hjFh]”hŒ%http://www.t10.org/members/w_pqi2.htm”…””}”(hjHhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”jFuh1hÓhjDubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Khj@ubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjhžhhŸh³h Nubeh}”(h]”h ]”h"]”h$]”h&]”Œbullet”Œ-”uh1jhŸh³h Khh¶hžhubhµ)”}”(hhh]”(hº)”}”(hŒSupported devices”h]”hŒSupported devices”…””}”(hjmhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjjhžhhŸh³h KubhÊ)”}”(hŒA”h]”hŒA”…””}”(hj{hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Khjjhžhubeh}”(h]”Œsupported-devices”ah ]”h"]”Œsupported devices”ah$]”h&]”uh1h´hh¶hžhhŸh³h Kubhµ)”}”(hhh]”(hº)”}”(hŒ!smartpqi specific entries in /sys”h]”hŒ!smartpqi specific entries in /sys”…””}”(hj”hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hj‘hžhhŸh³h Kubhµ)”}”(hhh]”(hº)”}”(hŒsmartpqi host attributes”h]”hŒsmartpqi host attributes”…””}”(hj¥hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hj¢hžhhŸh³h K!ubhŒ block_quote”“”)”}”(hXÕ- /sys/class/scsi_host/host*/rescan - /sys/class/scsi_host/host*/driver_version The host rescan attribute is a write only attribute. Writing to this attribute will trigger the driver to scan for new, changed, or removed devices and notify the SCSI mid-layer of any changes detected. The version attribute is read-only and will return the driver version and the controller firmware version. For example:: driver: 0.9.13-370 firmware: 0.01-522 ”h]”(j)”}”(hhh]”(j)”}”(hŒ!/sys/class/scsi_host/host*/rescan”h]”hÊ)”}”(hj¾h]”hŒ!/sys/class/scsi_host/host*/rescan”…””}”(hjÀhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K"hj¼ubah}”(h]”h ]”h"]”h$]”h&]”uh1jhj¹ubj)”}”(hŒ*/sys/class/scsi_host/host*/driver_version ”h]”hÊ)”}”(hŒ)/sys/class/scsi_host/host*/driver_version”h]”hŒ)/sys/class/scsi_host/host*/driver_version”…””}”(hj×hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K#hjÓubah}”(h]”h ]”h"]”h$]”h&]”uh1jhj¹ubeh}”(h]”h ]”h"]”h$]”h&]”jhjiuh1jhŸh³h K"hjµubhÊ)”}”(hŒÊThe host rescan attribute is a write only attribute. Writing to this attribute will trigger the driver to scan for new, changed, or removed devices and notify the SCSI mid-layer of any changes detected.”h]”hŒÊThe host rescan attribute is a write only attribute. Writing to this attribute will trigger the driver to scan for new, changed, or removed devices and notify the SCSI mid-layer of any changes detected.”…””}”(hjñhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K%hjµubhÊ)”}”(hŒxThe version attribute is read-only and will return the driver version and the controller firmware version. For example::”h]”hŒwThe version attribute is read-only and will return the driver version and the controller firmware version. For example:”…””}”(hjÿhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K)hjµubhŒ literal_block”“”)”}”(hŒ%driver: 0.9.13-370 firmware: 0.01-522”h]”hŒ%driver: 0.9.13-370 firmware: 0.01-522”…””}”hjsbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1j hŸh³h K-hjµubeh}”(h]”h ]”h"]”h$]”h&]”uh1j³hŸh³h K"hj¢hžhubeh}”(h]”Œsmartpqi-host-attributes”ah ]”h"]”Œsmartpqi host attributes”ah$]”h&]”uh1h´hj‘hžhhŸh³h K!ubhµ)”}”(hhh]”(hº)”}”(hŒsmartpqi sas device attributes”h]”hŒsmartpqi sas device attributes”…””}”(hj.hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hj+hžhhŸh³h K1ubj´)”}”(hXHBA devices are added to the SAS transport layer. These attributes are automatically added by the SAS transport layer. /sys/class/sas_device/end_device-X:X/sas_address /sys/class/sas_device/end_device-X:X/enclosure_identifier /sys/class/sas_device/end_device-X:X/scsi_target_id ”h]”(hÊ)”}”(hŒvHBA devices are added to the SAS transport layer. These attributes are automatically added by the SAS transport layer.”h]”hŒvHBA devices are added to the SAS transport layer. These attributes are automatically added by the SAS transport layer.”…””}”(hj@hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K2hj<ubhÊ)”}”(hŒž/sys/class/sas_device/end_device-X:X/sas_address /sys/class/sas_device/end_device-X:X/enclosure_identifier /sys/class/sas_device/end_device-X:X/scsi_target_id”h]”hŒž/sys/class/sas_device/end_device-X:X/sas_address /sys/class/sas_device/end_device-X:X/enclosure_identifier /sys/class/sas_device/end_device-X:X/scsi_target_id”…””}”(hjNhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K5hj<ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j³hŸh³h K2hj+hžhubeh}”(h]”Œsmartpqi-sas-device-attributes”ah ]”h"]”Œsmartpqi sas device attributes”ah$]”h&]”uh1h´hj‘hžhhŸh³h K1ubeh}”(h]”Œ smartpqi-specific-entries-in-sys”ah ]”h"]”Œ!smartpqi specific entries in /sys”ah$]”h&]”uh1h´hh¶hžhhŸh³h Kubhµ)”}”(hhh]”(hº)”}”(hŒsmartpqi specific ioctls”h]”hŒsmartpqi specific ioctls”…””}”(hjuhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjrhžhhŸh³h K:ubj´)”}”(hX:For compatibility with applications written for the cciss protocol. CCISS_DEREGDISK, CCISS_REGNEWDISK, CCISS_REGNEWD The above three ioctls all do exactly the same thing, which is to cause the driver to rescan for new devices. This does exactly the same thing as writing to the smartpqi specific host "rescan" attribute. CCISS_GETPCIINFO Returns PCI domain, bus, device and function and "board ID" (PCI subsystem ID). CCISS_GETDRIVVER Returns driver version in three bytes encoded as:: (DRIVER_MAJOR << 28) | (DRIVER_MINOR << 24) | (DRIVER_RELEASE << 16) | DRIVER_REVISION; CCISS_PASSTHRU Allows "BMIC" and "CISS" commands to be passed through to the Smart Storage Array. These are used extensively by the SSA Array Configuration Utility, SNMP storage agents, etc.”h]”(hÊ)”}”(hŒCFor compatibility with applications written for the cciss protocol.”h]”hŒCFor compatibility with applications written for the cciss protocol.”…””}”(hj‡hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K