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