xref: /linux/Documentation/ABI/testing/sysfs-class-scsi_host (revision 0a65e125150c227314dcd561a202a84228398449)
13a7bda83SDave JiangWhat:		/sys/class/scsi_host/hostX/isci_id
23a7bda83SDave JiangDate:		June 2011
33a7bda83SDave JiangContact:	Dave Jiang <dave.jiang@intel.com>
43a7bda83SDave JiangDescription:
53a7bda83SDave Jiang		This file contains the enumerated host ID for the Intel
63a7bda83SDave Jiang		SCU controller. The Intel(R) C600 Series Chipset SATA/SAS
73a7bda83SDave Jiang		Storage Control Unit embeds up to two 4-port controllers in
83a7bda83SDave Jiang		a single PCI device.  The controllers are enumerated in order
93a7bda83SDave Jiang		which usually means the lowest number scsi_host corresponds
103a7bda83SDave Jiang		with the first controller, but this association is not
113a7bda83SDave Jiang		guaranteed.  The 'isci_id' attribute unambiguously identifies
123a7bda83SDave Jiang		the controller index: '0' for the first controller,
133a7bda83SDave Jiang		'1' for the second.
14da0697bdSScott Teel
15da0697bdSScott TeelWhat:		/sys/class/scsi_host/hostX/acciopath_status
16da0697bdSScott TeelDate:		November 2013
17da0697bdSScott TeelContact:	Stephen M. Cameron <scameron@beardog.cce.hp.com>
18da0697bdSScott TeelDescription:	This file contains the current status of the "SSD Smart Path"
19da0697bdSScott Teel		feature of HP Smart Array RAID controllers using the hpsa
20da0697bdSScott Teel		driver.  SSD Smart Path, when enabled permits the driver to
21da0697bdSScott Teel		send i/o requests directly to physical devices that are part
22da0697bdSScott Teel		of a logical drive, bypassing the controllers firmware RAID
23da0697bdSScott Teel		stack for a performance advantage when possible.  A value of
24da0697bdSScott Teel		'1' indicates the feature is enabled, and the controller may
25da0697bdSScott Teel		use the direct i/o path to physical devices.  A value of zero
26da0697bdSScott Teel		means the feature is disabled and the controller may not use
27da0697bdSScott Teel		the direct i/o path to physical devices.  This setting is
28da0697bdSScott Teel		controller wide, affecting all configured logical drives on the
29da0697bdSScott Teel		controller.  This file is readable and writable.
30*0a65e125SAishwarya Pant
31*0a65e125SAishwarya PantWhat:		/sys/class/scsi_host/hostX/link_power_management_policy
32*0a65e125SAishwarya PantDate:		Oct, 2007
33*0a65e125SAishwarya PantKernelVersion:	v2.6.24
34*0a65e125SAishwarya PantContact:	linux-ide@vger.kernel.org
35*0a65e125SAishwarya PantDescription:
36*0a65e125SAishwarya Pant		(RW) This parameter allows the user to read and set the link
37*0a65e125SAishwarya Pant		(interface) power management.
38*0a65e125SAishwarya Pant
39*0a65e125SAishwarya Pant		There are four possible options:
40*0a65e125SAishwarya Pant
41*0a65e125SAishwarya Pant		min_power: Tell the controller to try to make the link use the
42*0a65e125SAishwarya Pant		least possible power when possible. This may sacrifice some
43*0a65e125SAishwarya Pant		performance due to increased latency when coming out of lower
44*0a65e125SAishwarya Pant		power states.
45*0a65e125SAishwarya Pant
46*0a65e125SAishwarya Pant		max_performance: Generally, this means no power management.
47*0a65e125SAishwarya Pant		Tell the controller to have performance be a priority over power
48*0a65e125SAishwarya Pant		management.
49*0a65e125SAishwarya Pant
50*0a65e125SAishwarya Pant		medium_power: Tell the controller to enter a lower power state
51*0a65e125SAishwarya Pant		when possible, but do not enter the lowest power state, thus
52*0a65e125SAishwarya Pant		improving latency over min_power setting.
53*0a65e125SAishwarya Pant
54*0a65e125SAishwarya Pant		med_power_with_dipm: Identical to the existing medium_power
55*0a65e125SAishwarya Pant		setting except that it enables dipm (device initiated power
56*0a65e125SAishwarya Pant		management) on top, which makes it match the Windows IRST (Intel
57*0a65e125SAishwarya Pant		Rapid Storage Technology) driver settings. This setting is also
58*0a65e125SAishwarya Pant		close to min_power, except that:
59*0a65e125SAishwarya Pant		a) It does not use host-initiated slumber mode, but it does
60*0a65e125SAishwarya Pant		allow device-initiated slumber
61*0a65e125SAishwarya Pant		b) It does not enable low power device sleep mode (DevSlp).
62*0a65e125SAishwarya Pant
63*0a65e125SAishwarya PantWhat:		/sys/class/scsi_host/hostX/em_message
64*0a65e125SAishwarya PantWhat:		/sys/class/scsi_host/hostX/em_message_type
65*0a65e125SAishwarya PantDate:		Jun, 2008
66*0a65e125SAishwarya PantKernelVersion:	v2.6.27
67*0a65e125SAishwarya PantContact:	linux-ide@vger.kernel.org
68*0a65e125SAishwarya PantDescription:
69*0a65e125SAishwarya Pant		em_message: (RW) Enclosure management support. For the LED
70*0a65e125SAishwarya Pant		protocol, writes and reads correspond to the LED message format
71*0a65e125SAishwarya Pant		as defined in the AHCI spec.
72*0a65e125SAishwarya Pant
73*0a65e125SAishwarya Pant		The user must turn sw_activity (under /sys/block/*/device/) OFF
74*0a65e125SAishwarya Pant		it they wish to control the activity LED via the em_message
75*0a65e125SAishwarya Pant		file.
76*0a65e125SAishwarya Pant
77*0a65e125SAishwarya Pant		em_message_type: (RO) Displays the current enclosure management
78*0a65e125SAishwarya Pant		protocol that is being used by the driver (for eg. LED, SAF-TE,
79*0a65e125SAishwarya Pant		SES-2, SGPIO etc).
80*0a65e125SAishwarya Pant
81*0a65e125SAishwarya PantWhat:		/sys/class/scsi_host/hostX/ahci_port_cmd
82*0a65e125SAishwarya PantWhat:		/sys/class/scsi_host/hostX/ahci_host_caps
83*0a65e125SAishwarya PantWhat:		/sys/class/scsi_host/hostX/ahci_host_cap2
84*0a65e125SAishwarya PantDate:		Mar, 2010
85*0a65e125SAishwarya PantKernelVersion:	v2.6.35
86*0a65e125SAishwarya PantContact:	linux-ide@vger.kernel.org
87*0a65e125SAishwarya PantDescription:
88*0a65e125SAishwarya Pant		[to be documented]
89*0a65e125SAishwarya Pant
90*0a65e125SAishwarya PantWhat:		/sys/class/scsi_host/hostX/ahci_host_version
91*0a65e125SAishwarya PantDate:		Mar, 2010
92*0a65e125SAishwarya PantKernelVersion:	v2.6.35
93*0a65e125SAishwarya PantContact:	linux-ide@vger.kernel.org
94*0a65e125SAishwarya PantDescription:
95*0a65e125SAishwarya Pant		(RO) Display the version of the AHCI spec implemented by the
96*0a65e125SAishwarya Pant		host.
97*0a65e125SAishwarya Pant
98*0a65e125SAishwarya PantWhat:		/sys/class/scsi_host/hostX/em_buffer
99*0a65e125SAishwarya PantDate:		Apr, 2010
100*0a65e125SAishwarya PantKernelVersion:	v2.6.35
101*0a65e125SAishwarya PantContact:	linux-ide@vger.kernel.org
102*0a65e125SAishwarya PantDescription:
103*0a65e125SAishwarya Pant		(RW) Allows access to AHCI EM (enclosure management) buffer
104*0a65e125SAishwarya Pant		directly if the host supports EM.
105*0a65e125SAishwarya Pant
106*0a65e125SAishwarya Pant		For eg. the AHCI driver supports SGPIO EM messages but the
107*0a65e125SAishwarya Pant		SATA/AHCI specs do not define the SGPIO message format of the EM
108*0a65e125SAishwarya Pant		buffer. Different hardware(HW) vendors may have different
109*0a65e125SAishwarya Pant		definitions. With the em_buffer attribute, this issue can be
110*0a65e125SAishwarya Pant		solved by allowing HW vendors to provide userland drivers and
111*0a65e125SAishwarya Pant		tools for their SGPIO initiators.
112*0a65e125SAishwarya Pant
113*0a65e125SAishwarya PantWhat:		/sys/class/scsi_host/hostX/em_message_supported
114*0a65e125SAishwarya PantDate:		Oct, 2009
115*0a65e125SAishwarya PantKernelVersion:	v2.6.39
116*0a65e125SAishwarya PantContact:	linux-ide@vger.kernel.org
117*0a65e125SAishwarya PantDescription:
118*0a65e125SAishwarya Pant		(RO) Displays supported enclosure management message types.
119