18c2ecf20Sopenharmony_ciWhat:		/sys/class/scsi_host/hostX/isci_id
28c2ecf20Sopenharmony_ciDate:		June 2011
38c2ecf20Sopenharmony_ciContact:	Dave Jiang <dave.jiang@intel.com>
48c2ecf20Sopenharmony_ciDescription:
58c2ecf20Sopenharmony_ci		This file contains the enumerated host ID for the Intel
68c2ecf20Sopenharmony_ci		SCU controller. The Intel(R) C600 Series Chipset SATA/SAS
78c2ecf20Sopenharmony_ci		Storage Control Unit embeds up to two 4-port controllers in
88c2ecf20Sopenharmony_ci		a single PCI device.  The controllers are enumerated in order
98c2ecf20Sopenharmony_ci		which usually means the lowest number scsi_host corresponds
108c2ecf20Sopenharmony_ci		with the first controller, but this association is not
118c2ecf20Sopenharmony_ci		guaranteed.  The 'isci_id' attribute unambiguously identifies
128c2ecf20Sopenharmony_ci		the controller index: '0' for the first controller,
138c2ecf20Sopenharmony_ci		'1' for the second.
148c2ecf20Sopenharmony_ci
158c2ecf20Sopenharmony_ciWhat:		/sys/class/scsi_host/hostX/acciopath_status
168c2ecf20Sopenharmony_ciDate:		November 2013
178c2ecf20Sopenharmony_ciContact:	Stephen M. Cameron <scameron@beardog.cce.hp.com>
188c2ecf20Sopenharmony_ciDescription:	This file contains the current status of the "SSD Smart Path"
198c2ecf20Sopenharmony_ci		feature of HP Smart Array RAID controllers using the hpsa
208c2ecf20Sopenharmony_ci		driver.  SSD Smart Path, when enabled permits the driver to
218c2ecf20Sopenharmony_ci		send i/o requests directly to physical devices that are part
228c2ecf20Sopenharmony_ci		of a logical drive, bypassing the controllers firmware RAID
238c2ecf20Sopenharmony_ci		stack for a performance advantage when possible.  A value of
248c2ecf20Sopenharmony_ci		'1' indicates the feature is enabled, and the controller may
258c2ecf20Sopenharmony_ci		use the direct i/o path to physical devices.  A value of zero
268c2ecf20Sopenharmony_ci		means the feature is disabled and the controller may not use
278c2ecf20Sopenharmony_ci		the direct i/o path to physical devices.  This setting is
288c2ecf20Sopenharmony_ci		controller wide, affecting all configured logical drives on the
298c2ecf20Sopenharmony_ci		controller.  This file is readable and writable.
308c2ecf20Sopenharmony_ci
318c2ecf20Sopenharmony_ciWhat:		/sys/class/scsi_host/hostX/link_power_management_policy
328c2ecf20Sopenharmony_ciDate:		Oct, 2007
338c2ecf20Sopenharmony_ciKernelVersion:	v2.6.24
348c2ecf20Sopenharmony_ciContact:	linux-ide@vger.kernel.org
358c2ecf20Sopenharmony_ciDescription:
368c2ecf20Sopenharmony_ci		(RW) This parameter allows the user to read and set the link
378c2ecf20Sopenharmony_ci		(interface) power management.
388c2ecf20Sopenharmony_ci
398c2ecf20Sopenharmony_ci		There are four possible options:
408c2ecf20Sopenharmony_ci
418c2ecf20Sopenharmony_ci		min_power: Tell the controller to try to make the link use the
428c2ecf20Sopenharmony_ci		least possible power when possible. This may sacrifice some
438c2ecf20Sopenharmony_ci		performance due to increased latency when coming out of lower
448c2ecf20Sopenharmony_ci		power states.
458c2ecf20Sopenharmony_ci
468c2ecf20Sopenharmony_ci		max_performance: Generally, this means no power management.
478c2ecf20Sopenharmony_ci		Tell the controller to have performance be a priority over power
488c2ecf20Sopenharmony_ci		management.
498c2ecf20Sopenharmony_ci
508c2ecf20Sopenharmony_ci		medium_power: Tell the controller to enter a lower power state
518c2ecf20Sopenharmony_ci		when possible, but do not enter the lowest power state, thus
528c2ecf20Sopenharmony_ci		improving latency over min_power setting.
538c2ecf20Sopenharmony_ci
548c2ecf20Sopenharmony_ci		med_power_with_dipm: Identical to the existing medium_power
558c2ecf20Sopenharmony_ci		setting except that it enables dipm (device initiated power
568c2ecf20Sopenharmony_ci		management) on top, which makes it match the Windows IRST (Intel
578c2ecf20Sopenharmony_ci		Rapid Storage Technology) driver settings. This setting is also
588c2ecf20Sopenharmony_ci		close to min_power, except that:
598c2ecf20Sopenharmony_ci
608c2ecf20Sopenharmony_ci		a) It does not use host-initiated slumber mode, but it does
618c2ecf20Sopenharmony_ci		   allow device-initiated slumber
628c2ecf20Sopenharmony_ci		b) It does not enable low power device sleep mode (DevSlp).
638c2ecf20Sopenharmony_ci
648c2ecf20Sopenharmony_ciWhat:		/sys/class/scsi_host/hostX/em_message
658c2ecf20Sopenharmony_ciWhat:		/sys/class/scsi_host/hostX/em_message_type
668c2ecf20Sopenharmony_ciDate:		Jun, 2008
678c2ecf20Sopenharmony_ciKernelVersion:	v2.6.27
688c2ecf20Sopenharmony_ciContact:	linux-ide@vger.kernel.org
698c2ecf20Sopenharmony_ciDescription:
708c2ecf20Sopenharmony_ci		em_message: (RW) Enclosure management support. For the LED
718c2ecf20Sopenharmony_ci		protocol, writes and reads correspond to the LED message format
728c2ecf20Sopenharmony_ci		as defined in the AHCI spec.
738c2ecf20Sopenharmony_ci
748c2ecf20Sopenharmony_ci		The user must turn sw_activity (under `/sys/block/*/device/`)
758c2ecf20Sopenharmony_ci		OFF it they wish to control the activity LED via the em_message
768c2ecf20Sopenharmony_ci		file.
778c2ecf20Sopenharmony_ci
788c2ecf20Sopenharmony_ci		em_message_type: (RO) Displays the current enclosure management
798c2ecf20Sopenharmony_ci		protocol that is being used by the driver (for eg. LED, SAF-TE,
808c2ecf20Sopenharmony_ci		SES-2, SGPIO etc).
818c2ecf20Sopenharmony_ci
828c2ecf20Sopenharmony_ciWhat:		/sys/class/scsi_host/hostX/ahci_port_cmd
838c2ecf20Sopenharmony_ciWhat:		/sys/class/scsi_host/hostX/ahci_host_caps
848c2ecf20Sopenharmony_ciWhat:		/sys/class/scsi_host/hostX/ahci_host_cap2
858c2ecf20Sopenharmony_ciDate:		Mar, 2010
868c2ecf20Sopenharmony_ciKernelVersion:	v2.6.35
878c2ecf20Sopenharmony_ciContact:	linux-ide@vger.kernel.org
888c2ecf20Sopenharmony_ciDescription:
898c2ecf20Sopenharmony_ci		[to be documented]
908c2ecf20Sopenharmony_ci
918c2ecf20Sopenharmony_ciWhat:		/sys/class/scsi_host/hostX/ahci_host_version
928c2ecf20Sopenharmony_ciDate:		Mar, 2010
938c2ecf20Sopenharmony_ciKernelVersion:	v2.6.35
948c2ecf20Sopenharmony_ciContact:	linux-ide@vger.kernel.org
958c2ecf20Sopenharmony_ciDescription:
968c2ecf20Sopenharmony_ci		(RO) Display the version of the AHCI spec implemented by the
978c2ecf20Sopenharmony_ci		host.
988c2ecf20Sopenharmony_ci
998c2ecf20Sopenharmony_ciWhat:		/sys/class/scsi_host/hostX/em_buffer
1008c2ecf20Sopenharmony_ciDate:		Apr, 2010
1018c2ecf20Sopenharmony_ciKernelVersion:	v2.6.35
1028c2ecf20Sopenharmony_ciContact:	linux-ide@vger.kernel.org
1038c2ecf20Sopenharmony_ciDescription:
1048c2ecf20Sopenharmony_ci		(RW) Allows access to AHCI EM (enclosure management) buffer
1058c2ecf20Sopenharmony_ci		directly if the host supports EM.
1068c2ecf20Sopenharmony_ci
1078c2ecf20Sopenharmony_ci		For eg. the AHCI driver supports SGPIO EM messages but the
1088c2ecf20Sopenharmony_ci		SATA/AHCI specs do not define the SGPIO message format of the EM
1098c2ecf20Sopenharmony_ci		buffer. Different hardware(HW) vendors may have different
1108c2ecf20Sopenharmony_ci		definitions. With the em_buffer attribute, this issue can be
1118c2ecf20Sopenharmony_ci		solved by allowing HW vendors to provide userland drivers and
1128c2ecf20Sopenharmony_ci		tools for their SGPIO initiators.
1138c2ecf20Sopenharmony_ci
1148c2ecf20Sopenharmony_ciWhat:		/sys/class/scsi_host/hostX/em_message_supported
1158c2ecf20Sopenharmony_ciDate:		Oct, 2009
1168c2ecf20Sopenharmony_ciKernelVersion:	v2.6.39
1178c2ecf20Sopenharmony_ciContact:	linux-ide@vger.kernel.org
1188c2ecf20Sopenharmony_ciDescription:
1198c2ecf20Sopenharmony_ci		(RO) Displays supported enclosure management message types.
120