Lines Matching +full:full +full:- +full:size
3 Contact: linux-scsi@vger.kernel.org
5 This file contains the auto-hibernate idle timer setting of a
6 UFS host controller. A value of '0' means auto-hibernate is not
11 10-bit values with a power-of-ten multiplier which allows a
19 device descriptor parameters. The full information about
28 device descriptor parameters. The full information about
37 the UFS device descriptor parameters. The full information
47 The full information about the descriptor could be found
56 the UFS device descriptor parameters. The full information
66 The full information about the descriptor could be found
76 parameters. The full information about the descriptor could
87 parameters. The full information about the descriptor could
97 the UFS device descriptor parameters. The full information
106 the UFS device descriptor parameters. The full information
115 the UFS device descriptor parameters. The full information
125 The full information about the descriptor could be found
135 The full information about the descriptor could be found
144 of the UFS device descriptor parameters. The full information
153 of the UFS device descriptor parameters. The full information
163 The full information about the descriptor could be found
172 UFS device descriptor parameters. The full information about
182 descriptor parameters. The full information about
192 parameters. The full information about the descriptor
202 The full information about the descriptor could be
211 UFS device descriptor parameters. The full information
220 UFS device descriptor parameters. The full information
229 UFS device descriptor parameters. The full information
239 descriptor parameters. The full information about
248 written during the pre-soldering phase of the PSA flow.
250 The full information about the descriptor could be found
260 parameters. The full information about the descriptor could
271 The full information about the descriptor could be found at
279 Description: This file shows the MIPI M-PHY version number in BCD format.
281 The full information about the descriptor could be found at
292 of the UFS geometry descriptor parameters. The full
303 geometry descriptor parameters. The full information about
311 Description: This file shows the segment size. This is one of the UFS
312 geometry descriptor parameters. The full information about
320 Description: This file shows the allocation unit size. This is one of
321 the UFS geometry descriptor parameters. The full information
329 Description: This file shows the minimum addressable block size. This
330 is one of the UFS geometry descriptor parameters. The full
339 Description: This file shows the optimal read block size. This is one
340 of the UFS geometry descriptor parameters. The full
349 Description: This file shows the optimal write block size. This is one
350 of the UFS geometry descriptor parameters. The full
359 Description: This file shows the maximum data-in buffer size. This
360 is one of the UFS geometry descriptor parameters. The full
369 Description: This file shows the maximum data-out buffer size. This
370 is one of the UFS geometry descriptor parameters. The full
381 descriptor parameters. The full information about the
390 is one of the UFS geometry descriptor parameters. The full
399 Description: This file shows support for out-of-order data transfer.
401 The full information about the descriptor could be found at
411 descriptor parameters. The full information about the
419 Description: This file shows system data tag unit size. This is one of
420 the UFS geometry descriptor parameters. The full information
428 Description: This file shows maximum storage area size allocated by
431 The full information about the descriptor could be found at
440 one of the UFS geometry descriptor parameters. The full
450 the UFS geometry descriptor parameters. The full
461 enhanced type 1-4). This is one of the UFS geometry
462 descriptor parameters. The full information about the
472 enhanced type 1-4). This is one of the UFS geometry
473 descriptor parameters. The full information about the
483 of the UFS health descriptor parameters. The full
494 parameters. The full information about the descriptor
504 parameters. The full information about the descriptor
515 power descriptor parameters. The full information about
525 The full information about the descriptor could be found at
533 Description: This file contains a product name string. The full information
541 Description: This file contains a OEM ID string. The full information
549 Description: This file contains a device serial number string. The full
558 Description: This file contains a product revision string. The full
569 the UFS unit descriptor parameters. The full information
578 the UFS unit descriptor parameters. The full information
587 unit descriptor parameters. The full information about
596 unit descriptor parameters. The full information about
605 unit descriptor parameters. The full information about
615 unit descriptor parameters. The full information about
623 Description: This file shows the size of addressable logical blocks
625 the UFS unit descriptor parameters. The full information about
634 This is one of the UFS unit descriptor parameters. The full
643 Description: This file shows the erase block size. This is one of
644 the UFS unit descriptor parameters. The full information
653 the UFS unit descriptor parameters. The full information
662 one of the UFS unit descriptor parameters. The full information
671 the UFS unit descriptor parameters. The full information
680 the UFS unit descriptor parameters. The full information
689 Description: This file shows the device init status. The full information
698 The full information about the flag could be found at
708 full information about the flag could be found at
717 enabled. The full information about the flag could be
726 The full information about the flag could be found at
735 The full information about the flag could be found at
744 operation related to real time clock. The full information
753 disabled. The full information about the flag could be found
763 The full information about the attribute could be found at
772 The full information about the attribute could be found at
781 The full information about the attribute could be found at
790 device attribute. The full information about the attribute
799 attribute. The full information about the attribute could
808 attribute. The full information about the attribute could
816 Description: This file shows the maximum data size in a DATA IN
817 UPIU. The full information about the attribute could
826 requested with a READY TO TRANSFER UPIU. The full information
835 attribute. The full information about the attribute could
844 The full information about the attribute could be found at
851 outstanding RTTs in device that is allowed. The full
861 attribute. The full information about the attribute could
870 attribute. The full information about the attribute could
879 The full information about the attribute could be found at
887 Description: This file show the PSA feature status. The full information
896 load to all logical units in pre-soldering state.
897 The full information about the attribute could be found at
908 the particular logical unit. The full information about
1009 data of specific chunk size (in Bytes). 0 means any chunk size.
1127 Description: This entry shows if preserve user-space was configured
1149 Description: This entry shows the total user-space decrease in shared
1159 Description: This entry shows the Maximum total WriteBooster Buffer size
1276 01h 0% - 10% WriteBooster Buffer life time used
1278 0Ah 90% - 100% WriteBooster Buffer life time used
1286 Description: This entry shows the configured size of WriteBooster buffer.
1296 enable it. The WriteBooster is enabled after power-on/reset,
1306 The full information about the descriptor can be found in the UFS
1326 HPB Region size = 512B * 2^bHPBRegionSize
1345 logical block size:
1346 HPB Sub-Region size = 512B x 2^bHPBSubRegionSize
1401 recommendations for activating sub-regions and/or inactivating region.
1408 Description: This entry shows the number of active sub-regions recommended by
1425 activating sub-regions recommended by response UPIUs.
1439 Description: This entry shows the maximum HPB data size for using a single HPB
1469 "to-be-activated" list. Since we reset the read counter upon
1478 We use entries_per_srgn - the amount of blocks in a subregion as
1479 our bucket size. This applies because HPB1.0 only handles
1480 single-block reads. Once the bucket size is crossed, we trigger
1481 a normalization work - not only to avoid overflow, but mainly
1486 an active region has exhausted its reads - inactivate it.
1493 happening when the max-active-regions limit has been crossed.
1512 time - read_timeout_ms. If read_timeout_ms has expired, and the
1516 region if it is clean - see read_timeout_expiries.
1522 just re-wind its timer for another spin. Do that as long as it