Commit fa82cabb authored by Damien Le Moal's avatar Damien Le Moal
Browse files

doc: admin-guide: Update libata kernel parameters 



Cleanup the text text describing the libata.force boot parameter and
update the list of the values to include all supported horkage and link
flag that can be forced.

Signed-off-by: default avatarDamien Le Moal <damien.lemoal@opensource.wdc.com>
Reviewed-by: default avatarHannes Reinecke <hare@suse.de>
parent 2c33bbda

Documentation/admin-guide/kernel-parameters.txt

+55 −16
Original line number Diff line number Diff line
@@ -2622,14 +2622,14 @@ 
			when set.

			Format: <int>



	libata.force=	[LIBATA] Force configurations.  The format is comma-

			separated list of "[ID:]VAL" where ID is

			PORT[.DEVICE].  PORT and DEVICE are decimal numbers

			matching port, link or device.  Basically, it matches

			the ATA ID string printed on console by libata.  If

			the whole ID part is omitted, the last PORT and DEVICE

			values are used.  If ID hasn't been specified yet, the

			configuration applies to all ports, links and devices.

	libata.force=	[LIBATA] Force configurations.  The format is a comma-

			separated list of "[ID:]VAL" where ID is PORT[.DEVICE].

			PORT and DEVICE are decimal numbers matching port, link

			or device.  Basically, it matches the ATA ID string

			printed on console by libata.  If the whole ID part is

			omitted, the last PORT and DEVICE values are used.  If

			ID hasn't been specified yet, the configuration applies

			to all ports, links and devices.



			If only DEVICE is omitted, the parameter applies to

			the port and all links and devices behind it.  DEVICE
@@ -2639,7 +2639,7 @@ 
			host link and device attached to it.



			The VAL specifies the configuration to force.  As long

			as there's no ambiguity shortcut notation is allowed.

			as there is no ambiguity, shortcut notation is allowed.

			For example, both 1.5 and 1.5G would work for 1.5Gbps.

			The following configurations can be forced.
@@ -2652,19 +2652,58 @@ 
			  udma[/][16,25,33,44,66,100,133] notation is also

			  allowed.



			* nohrst, nosrst, norst: suppress hard, soft and both

			  resets.



			* rstonce: only attempt one reset during hot-unplug

			  link recovery.



			* [no]dbdelay: Enable or disable the extra 200ms delay

			  before debouncing a link PHY and device presence

			  detection.



			* [no]ncq: Turn on or off NCQ.



			* [no]ncqtrim: Turn off queued DSM TRIM.

			* [no]ncqtrim: Enable or disable queued DSM TRIM.



			* [no]ncqati: Enable or disable NCQ trim on ATI chipset.



			* [no]trim: Enable or disable (unqueued) TRIM.



			* trim_zero: Indicate that TRIM command zeroes data.



			* max_trim_128m: Set 128M maximum trim size limit.



			* [no]dma: Turn on or off DMA transfers.



			* atapi_dmadir: Enable ATAPI DMADIR bridge support.



			* atapi_mod16_dma: Enable the use of ATAPI DMA for

			  commands that are not a multiple of 16 bytes.



			* [no]dmalog: Enable or disable the use of the

			  READ LOG DMA EXT command to access logs.



			* [no]iddevlog: Enable or disable access to the

			  identify device data log.



			* [no]logdir: Enable or disable access to the general

			  purpose log directory.



			* max_sec_128: Set transfer size limit to 128 sectors.



			* max_sec_1024: Set or clear transfer size limit to

			  1024 sectors.



			* nohrst, nosrst, norst: suppress hard, soft

			  and both resets.

			* max_sec_lba48: Set or clear transfer size limit to

			  65535 sectors.



			* rstonce: only attempt one reset during

			  hot-unplug link recovery

			* [no]lpm: Enable or disable link power management.



			* dump_id: dump IDENTIFY data.

			* [no]setxfer: Indicate if transfer speed mode setting

			  should be skipped.



			* atapi_dmadir: Enable ATAPI DMADIR bridge support

			* dump_id: Dump IDENTIFY data.



			* disable: Disable this device.