162306a36Sopenharmony_ciWhat: /sys/class/scsi_host/hostX/isci_id 262306a36Sopenharmony_ciDate: June 2011 362306a36Sopenharmony_ciContact: Dave Jiang <dave.jiang@intel.com> 462306a36Sopenharmony_ciDescription: 562306a36Sopenharmony_ci This file contains the enumerated host ID for the Intel 662306a36Sopenharmony_ci SCU controller. The Intel(R) C600 Series Chipset SATA/SAS 762306a36Sopenharmony_ci Storage Control Unit embeds up to two 4-port controllers in 862306a36Sopenharmony_ci a single PCI device. The controllers are enumerated in order 962306a36Sopenharmony_ci which usually means the lowest number scsi_host corresponds 1062306a36Sopenharmony_ci with the first controller, but this association is not 1162306a36Sopenharmony_ci guaranteed. The 'isci_id' attribute unambiguously identifies 1262306a36Sopenharmony_ci the controller index: '0' for the first controller, 1362306a36Sopenharmony_ci '1' for the second. 1462306a36Sopenharmony_ci 1562306a36Sopenharmony_ciWhat: /sys/class/scsi_host/hostX/acciopath_status 1662306a36Sopenharmony_ciDate: November 2013 1762306a36Sopenharmony_ciContact: Stephen M. Cameron <scameron@beardog.cce.hp.com> 1862306a36Sopenharmony_ciDescription: This file contains the current status of the "SSD Smart Path" 1962306a36Sopenharmony_ci feature of HP Smart Array RAID controllers using the hpsa 2062306a36Sopenharmony_ci driver. SSD Smart Path, when enabled permits the driver to 2162306a36Sopenharmony_ci send i/o requests directly to physical devices that are part 2262306a36Sopenharmony_ci of a logical drive, bypassing the controllers firmware RAID 2362306a36Sopenharmony_ci stack for a performance advantage when possible. A value of 2462306a36Sopenharmony_ci '1' indicates the feature is enabled, and the controller may 2562306a36Sopenharmony_ci use the direct i/o path to physical devices. A value of zero 2662306a36Sopenharmony_ci means the feature is disabled and the controller may not use 2762306a36Sopenharmony_ci the direct i/o path to physical devices. This setting is 2862306a36Sopenharmony_ci controller wide, affecting all configured logical drives on the 2962306a36Sopenharmony_ci controller. This file is readable and writable. 3062306a36Sopenharmony_ci 3162306a36Sopenharmony_ciWhat: /sys/class/scsi_host/hostX/link_power_management_policy 3262306a36Sopenharmony_ciDate: Oct, 2007 3362306a36Sopenharmony_ciKernelVersion: v2.6.24 3462306a36Sopenharmony_ciContact: linux-ide@vger.kernel.org 3562306a36Sopenharmony_ciDescription: 3662306a36Sopenharmony_ci (RW) This parameter allows the user to read and set the link 3762306a36Sopenharmony_ci (interface) power management. 3862306a36Sopenharmony_ci 3962306a36Sopenharmony_ci There are four possible options: 4062306a36Sopenharmony_ci 4162306a36Sopenharmony_ci min_power: Tell the controller to try to make the link use the 4262306a36Sopenharmony_ci least possible power when possible. This may sacrifice some 4362306a36Sopenharmony_ci performance due to increased latency when coming out of lower 4462306a36Sopenharmony_ci power states. 4562306a36Sopenharmony_ci 4662306a36Sopenharmony_ci max_performance: Generally, this means no power management. 4762306a36Sopenharmony_ci Tell the controller to have performance be a priority over power 4862306a36Sopenharmony_ci management. 4962306a36Sopenharmony_ci 5062306a36Sopenharmony_ci medium_power: Tell the controller to enter a lower power state 5162306a36Sopenharmony_ci when possible, but do not enter the lowest power state, thus 5262306a36Sopenharmony_ci improving latency over min_power setting. 5362306a36Sopenharmony_ci 5462306a36Sopenharmony_ci med_power_with_dipm: Identical to the existing medium_power 5562306a36Sopenharmony_ci setting except that it enables dipm (device initiated power 5662306a36Sopenharmony_ci management) on top, which makes it match the Windows IRST (Intel 5762306a36Sopenharmony_ci Rapid Storage Technology) driver settings. This setting is also 5862306a36Sopenharmony_ci close to min_power, except that: 5962306a36Sopenharmony_ci 6062306a36Sopenharmony_ci a) It does not use host-initiated slumber mode, but it does 6162306a36Sopenharmony_ci allow device-initiated slumber 6262306a36Sopenharmony_ci b) It does not enable low power device sleep mode (DevSlp). 6362306a36Sopenharmony_ci 6462306a36Sopenharmony_ciWhat: /sys/class/scsi_host/hostX/em_message 6562306a36Sopenharmony_ciWhat: /sys/class/scsi_host/hostX/em_message_type 6662306a36Sopenharmony_ciDate: Jun, 2008 6762306a36Sopenharmony_ciKernelVersion: v2.6.27 6862306a36Sopenharmony_ciContact: linux-ide@vger.kernel.org 6962306a36Sopenharmony_ciDescription: 7062306a36Sopenharmony_ci em_message: (RW) Enclosure management support. For the LED 7162306a36Sopenharmony_ci protocol, writes and reads correspond to the LED message format 7262306a36Sopenharmony_ci as defined in the AHCI spec. 7362306a36Sopenharmony_ci 7462306a36Sopenharmony_ci The user must turn sw_activity (under `/sys/block/*/device/`) 7562306a36Sopenharmony_ci OFF it they wish to control the activity LED via the em_message 7662306a36Sopenharmony_ci file. 7762306a36Sopenharmony_ci 7862306a36Sopenharmony_ci em_message_type: (RO) Displays the current enclosure management 7962306a36Sopenharmony_ci protocol that is being used by the driver (for eg. LED, SAF-TE, 8062306a36Sopenharmony_ci SES-2, SGPIO etc). 8162306a36Sopenharmony_ci 8262306a36Sopenharmony_ciWhat: /sys/class/scsi_host/hostX/ahci_port_cmd 8362306a36Sopenharmony_ciWhat: /sys/class/scsi_host/hostX/ahci_host_caps 8462306a36Sopenharmony_ciWhat: /sys/class/scsi_host/hostX/ahci_host_cap2 8562306a36Sopenharmony_ciDate: Mar, 2010 8662306a36Sopenharmony_ciKernelVersion: v2.6.35 8762306a36Sopenharmony_ciContact: linux-ide@vger.kernel.org 8862306a36Sopenharmony_ciDescription: 8962306a36Sopenharmony_ci [to be documented] 9062306a36Sopenharmony_ci 9162306a36Sopenharmony_ciWhat: /sys/class/scsi_host/hostX/ahci_host_version 9262306a36Sopenharmony_ciDate: Mar, 2010 9362306a36Sopenharmony_ciKernelVersion: v2.6.35 9462306a36Sopenharmony_ciContact: linux-ide@vger.kernel.org 9562306a36Sopenharmony_ciDescription: 9662306a36Sopenharmony_ci (RO) Display the version of the AHCI spec implemented by the 9762306a36Sopenharmony_ci host. 9862306a36Sopenharmony_ci 9962306a36Sopenharmony_ciWhat: /sys/class/scsi_host/hostX/em_buffer 10062306a36Sopenharmony_ciDate: Apr, 2010 10162306a36Sopenharmony_ciKernelVersion: v2.6.35 10262306a36Sopenharmony_ciContact: linux-ide@vger.kernel.org 10362306a36Sopenharmony_ciDescription: 10462306a36Sopenharmony_ci (RW) Allows access to AHCI EM (enclosure management) buffer 10562306a36Sopenharmony_ci directly if the host supports EM. 10662306a36Sopenharmony_ci 10762306a36Sopenharmony_ci For eg. the AHCI driver supports SGPIO EM messages but the 10862306a36Sopenharmony_ci SATA/AHCI specs do not define the SGPIO message format of the EM 10962306a36Sopenharmony_ci buffer. Different hardware(HW) vendors may have different 11062306a36Sopenharmony_ci definitions. With the em_buffer attribute, this issue can be 11162306a36Sopenharmony_ci solved by allowing HW vendors to provide userland drivers and 11262306a36Sopenharmony_ci tools for their SGPIO initiators. 11362306a36Sopenharmony_ci 11462306a36Sopenharmony_ciWhat: /sys/class/scsi_host/hostX/em_message_supported 11562306a36Sopenharmony_ciDate: Oct, 2009 11662306a36Sopenharmony_ciKernelVersion: v2.6.39 11762306a36Sopenharmony_ciContact: linux-ide@vger.kernel.org 11862306a36Sopenharmony_ciDescription: 11962306a36Sopenharmony_ci (RO) Displays supported enclosure management message types. 120