1562 lines · plain
1What: /sys/bus/*/drivers/ufshcd/*/auto_hibern82Date: March 20183Contact: linux-scsi@vger.kernel.org4Description:5 This file contains the auto-hibernate idle timer setting of a6 UFS host controller. A value of '0' means auto-hibernate is not7 enabled. Otherwise the value is the number of microseconds of8 idle time before the UFS host controller will autonomously put9 the link into hibernate state. That will save power at the10 expense of increased latency. Note that the hardware supports11 10-bit values with a power-of-ten multiplier which allows a12 maximum value of 102300000. Refer to the UFS Host Controller13 Interface specification for more details.14 15What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/device_type16What: /sys/bus/platform/devices/*.ufs/device_descriptor/device_type17Date: February 201818Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>19Description: This file shows the device type. This is one of the UFS20 device descriptor parameters. The full information about21 the descriptor could be found at UFS specifications 2.1.22 23 The file is read only.24 25What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/device_class26What: /sys/bus/platform/devices/*.ufs/device_descriptor/device_class27Date: February 201828Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>29Description: This file shows the device class. This is one of the UFS30 device descriptor parameters. The full information about31 the descriptor could be found at UFS specifications 2.1.32 33 The file is read only.34 35What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/device_sub_class36What: /sys/bus/platform/devices/*.ufs/device_descriptor/device_sub_class37Date: February 201838Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>39Description: This file shows the UFS storage subclass. This is one of40 the UFS device descriptor parameters. The full information41 about the descriptor could be found at UFS specifications 2.1.42 43 The file is read only.44 45What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/protocol46What: /sys/bus/platform/devices/*.ufs/device_descriptor/protocol47Date: February 201848Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>49Description: This file shows the protocol supported by an UFS device.50 This is one of the UFS device descriptor parameters.51 The full information about the descriptor could be found52 at UFS specifications 2.1.53 54 The file is read only.55 56What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/number_of_luns57What: /sys/bus/platform/devices/*.ufs/device_descriptor/number_of_luns58Date: February 201859Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>60Description: This file shows number of logical units. This is one of61 the UFS device descriptor parameters. The full information62 about the descriptor could be found at UFS specifications 2.1.63 64 The file is read only.65 66What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/number_of_wluns67What: /sys/bus/platform/devices/*.ufs/device_descriptor/number_of_wluns68Date: February 201869Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>70Description: This file shows number of well known logical units.71 This is one of the UFS device descriptor parameters.72 The full information about the descriptor could be found73 at UFS specifications 2.1.74 75 The file is read only.76 77What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/boot_enable78What: /sys/bus/platform/devices/*.ufs/device_descriptor/boot_enable79Date: February 201880Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>81Description: This file shows value that indicates whether the device is82 enabled for boot. This is one of the UFS device descriptor83 parameters. The full information about the descriptor could84 be found at UFS specifications 2.1.85 86 The file is read only.87 88What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/descriptor_access_enable89What: /sys/bus/platform/devices/*.ufs/device_descriptor/descriptor_access_enable90Date: February 201891Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>92Description: This file shows value that indicates whether the device93 descriptor could be read after partial initialization phase94 of the boot sequence. This is one of the UFS device descriptor95 parameters. The full information about the descriptor could96 be found at UFS specifications 2.1.97 98 The file is read only.99 100What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/initial_power_mode101What: /sys/bus/platform/devices/*.ufs/device_descriptor/initial_power_mode102Date: February 2018103Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>104Description: This file shows value that defines the power mode after105 device initialization or hardware reset. This is one of106 the UFS device descriptor parameters. The full information107 about the descriptor could be found at UFS specifications 2.1.108 109 The file is read only.110 111What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/high_priority_lun112What: /sys/bus/platform/devices/*.ufs/device_descriptor/high_priority_lun113Date: February 2018114Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>115Description: This file shows the high priority lun. This is one of116 the UFS device descriptor parameters. The full information117 about the descriptor could be found at UFS specifications 2.1.118 119 The file is read only.120 121What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/secure_removal_type122What: /sys/bus/platform/devices/*.ufs/device_descriptor/secure_removal_type123Date: February 2018124Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>125Description: This file shows the secure removal type. This is one of126 the UFS device descriptor parameters. The full information127 about the descriptor could be found at UFS specifications 2.1.128 129 The file is read only.130 131What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/support_security_lun132What: /sys/bus/platform/devices/*.ufs/device_descriptor/support_security_lun133Date: February 2018134Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>135Description: This file shows whether the security lun is supported.136 This is one of the UFS device descriptor parameters.137 The full information about the descriptor could be found138 at UFS specifications 2.1.139 140 The file is read only.141 142What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/bkops_termination_latency143What: /sys/bus/platform/devices/*.ufs/device_descriptor/bkops_termination_latency144Date: February 2018145Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>146Description: This file shows the background operations termination147 latency. This is one of the UFS device descriptor parameters.148 The full information about the descriptor could be found149 at UFS specifications 2.1.150 151 The file is read only.152 153What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/initial_active_icc_level154What: /sys/bus/platform/devices/*.ufs/device_descriptor/initial_active_icc_level155Date: February 2018156Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>157Description: This file shows the initial active ICC level. This is one158 of the UFS device descriptor parameters. The full information159 about the descriptor could be found at UFS specifications 2.1.160 161 The file is read only.162 163What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/specification_version164What: /sys/bus/platform/devices/*.ufs/device_descriptor/specification_version165Date: February 2018166Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>167Description: This file shows the specification version. This is one168 of the UFS device descriptor parameters. The full information169 about the descriptor could be found at UFS specifications 2.1.170 171 The file is read only.172 173What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/manufacturing_date174What: /sys/bus/platform/devices/*.ufs/device_descriptor/manufacturing_date175Date: February 2018176Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>177Description: This file shows the manufacturing date in BCD format.178 This is one of the UFS device descriptor parameters.179 The full information about the descriptor could be found180 at UFS specifications 2.1.181 182 The file is read only.183 184What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/manufacturer_id185What: /sys/bus/platform/devices/*.ufs/device_descriptor/manufacturer_id186Date: February 2018187Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>188Description: This file shows the manufacturer ID. This is one of the189 UFS device descriptor parameters. The full information about190 the descriptor could be found at UFS specifications 2.1.191 192 The file is read only.193 194What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/rtt_capability195What: /sys/bus/platform/devices/*.ufs/device_descriptor/rtt_capability196Date: February 2018197Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>198Description: This file shows the maximum number of outstanding RTTs199 supported by the device. This is one of the UFS device200 descriptor parameters. The full information about201 the descriptor could be found at UFS specifications 2.1.202 203 The file is read only.204 205What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/rtc_update206What: /sys/bus/platform/devices/*.ufs/device_descriptor/rtc_update207Date: February 2018208Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>209Description: This file shows the frequency and method of the realtime210 clock update. This is one of the UFS device descriptor211 parameters. The full information about the descriptor212 could be found at UFS specifications 2.1.213 214 The file is read only.215 216What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/ufs_features217What: /sys/bus/platform/devices/*.ufs/device_descriptor/ufs_features218Date: February 2018219Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>220Description: This file shows which features are supported by the device.221 This is one of the UFS device descriptor parameters.222 The full information about the descriptor could be223 found at UFS specifications 2.1.224 225 The file is read only.226 227What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/ffu_timeout228What: /sys/bus/platform/devices/*.ufs/device_descriptor/ffu_timeout229Date: February 2018230Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>231Description: This file shows the FFU timeout. This is one of the232 UFS device descriptor parameters. The full information233 about the descriptor could be found at UFS specifications 2.1.234 235 The file is read only.236 237What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/queue_depth238What: /sys/bus/platform/devices/*.ufs/device_descriptor/queue_depth239Date: February 2018240Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>241Description: This file shows the device queue depth. This is one of the242 UFS device descriptor parameters. The full information243 about the descriptor could be found at UFS specifications 2.1.244 245 The file is read only.246 247What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/device_version248What: /sys/bus/platform/devices/*.ufs/device_descriptor/device_version249Date: February 2018250Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>251Description: This file shows the device version. This is one of the252 UFS device descriptor parameters. The full information253 about the descriptor could be found at UFS specifications 2.1.254 255 The file is read only.256 257What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/number_of_secure_wpa258What: /sys/bus/platform/devices/*.ufs/device_descriptor/number_of_secure_wpa259Date: February 2018260Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>261Description: This file shows number of secure write protect areas262 supported by the device. This is one of the UFS device263 descriptor parameters. The full information about264 the descriptor could be found at UFS specifications 2.1.265 266 The file is read only.267 268What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/psa_max_data_size269What: /sys/bus/platform/devices/*.ufs/device_descriptor/psa_max_data_size270Date: February 2018271Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>272Description: This file shows the maximum amount of data that may be273 written during the pre-soldering phase of the PSA flow.274 This is one of the UFS device descriptor parameters.275 The full information about the descriptor could be found276 at UFS specifications 2.1.277 278 The file is read only.279 280What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/psa_state_timeout281What: /sys/bus/platform/devices/*.ufs/device_descriptor/psa_state_timeout282Date: February 2018283Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>284Description: This file shows the command maximum timeout for a change285 in PSA state. This is one of the UFS device descriptor286 parameters. The full information about the descriptor could287 be found at UFS specifications 2.1.288 289 The file is read only.290 291 292What: /sys/bus/platform/drivers/ufshcd/*/interconnect_descriptor/unipro_version293What: /sys/bus/platform/devices/*.ufs/interconnect_descriptor/unipro_version294Date: February 2018295Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>296Description: This file shows the MIPI UniPro version number in BCD format.297 This is one of the UFS interconnect descriptor parameters.298 The full information about the descriptor could be found at299 UFS specifications 2.1.300 301 The file is read only.302 303What: /sys/bus/platform/drivers/ufshcd/*/interconnect_descriptor/mphy_version304What: /sys/bus/platform/devices/*.ufs/interconnect_descriptor/mphy_version305Date: February 2018306Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>307Description: This file shows the MIPI M-PHY version number in BCD format.308 This is one of the UFS interconnect descriptor parameters.309 The full information about the descriptor could be found at310 UFS specifications 2.1.311 312 The file is read only.313 314 315What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/raw_device_capacity316What: /sys/bus/platform/devices/*.ufs/geometry_descriptor/raw_device_capacity317Date: February 2018318Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>319Description: This file shows the total memory quantity available to320 the user to configure the device logical units. This is one321 of the UFS geometry descriptor parameters. The full322 information about the descriptor could be found at323 UFS specifications 2.1.324 325 The file is read only.326 327What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/max_number_of_luns328What: /sys/bus/platform/devices/*.ufs/geometry_descriptor/max_number_of_luns329Date: February 2018330Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>331Description: This file shows the maximum number of logical units332 supported by the UFS device. This is one of the UFS333 geometry descriptor parameters. The full information about334 the descriptor could be found at UFS specifications 2.1.335 336 The file is read only.337 338What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/segment_size339What: /sys/bus/platform/devices/*.ufs/geometry_descriptor/segment_size340Date: February 2018341Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>342Description: This file shows the segment size. This is one of the UFS343 geometry descriptor parameters. The full information about344 the descriptor could be found at UFS specifications 2.1.345 346 The file is read only.347 348What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/allocation_unit_size349What: /sys/bus/platform/devices/*.ufs/geometry_descriptor/allocation_unit_size350Date: February 2018351Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>352Description: This file shows the allocation unit size. This is one of353 the UFS geometry descriptor parameters. The full information354 about the descriptor could be found at UFS specifications 2.1.355 356 The file is read only.357 358What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/min_addressable_block_size359What: /sys/bus/platform/devices/*.ufs/geometry_descriptor/min_addressable_block_size360Date: February 2018361Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>362Description: This file shows the minimum addressable block size. This363 is one of the UFS geometry descriptor parameters. The full364 information about the descriptor could be found at UFS365 specifications 2.1.366 367 The file is read only.368 369What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/optimal_read_block_size370What: /sys/bus/platform/devices/*.ufs/geometry_descriptor/optimal_read_block_size371Date: February 2018372Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>373Description: This file shows the optimal read block size. This is one374 of the UFS geometry descriptor parameters. The full375 information about the descriptor could be found at UFS376 specifications 2.1.377 378 The file is read only.379 380What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/optimal_write_block_size381What: /sys/bus/platform/devices/*.ufs/geometry_descriptor/optimal_write_block_size382Date: February 2018383Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>384Description: This file shows the optimal write block size. This is one385 of the UFS geometry descriptor parameters. The full386 information about the descriptor could be found at UFS387 specifications 2.1.388 389 The file is read only.390 391What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/max_in_buffer_size392What: /sys/bus/platform/devices/*.ufs/geometry_descriptor/max_in_buffer_size393Date: February 2018394Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>395Description: This file shows the maximum data-in buffer size. This396 is one of the UFS geometry descriptor parameters. The full397 information about the descriptor could be found at UFS398 specifications 2.1.399 400 The file is read only.401 402What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/max_out_buffer_size403What: /sys/bus/platform/devices/*.ufs/geometry_descriptor/max_out_buffer_size404Date: February 2018405Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>406Description: This file shows the maximum data-out buffer size. This407 is one of the UFS geometry descriptor parameters. The full408 information about the descriptor could be found at UFS409 specifications 2.1.410 411 The file is read only.412 413What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/rpmb_rw_size414What: /sys/bus/platform/devices/*.ufs/geometry_descriptor/rpmb_rw_size415Date: February 2018416Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>417Description: This file shows the maximum number of RPMB frames allowed418 in Security Protocol In/Out. This is one of the UFS geometry419 descriptor parameters. The full information about the420 descriptor could be found at UFS specifications 2.1.421 422 The file is read only.423 424What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/dyn_capacity_resource_policy425What: /sys/bus/platform/devices/*.ufs/geometry_descriptor/dyn_capacity_resource_policy426Date: February 2018427Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>428Description: This file shows the dynamic capacity resource policy. This429 is one of the UFS geometry descriptor parameters. The full430 information about the descriptor could be found at431 UFS specifications 2.1.432 433 The file is read only.434 435What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/data_ordering436What: /sys/bus/platform/devices/*.ufs/geometry_descriptor/data_ordering437Date: February 2018438Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>439Description: This file shows support for out-of-order data transfer.440 This is one of the UFS geometry descriptor parameters.441 The full information about the descriptor could be found at442 UFS specifications 2.1.443 444 The file is read only.445 446What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/max_number_of_contexts447What: /sys/bus/platform/devices/*.ufs/geometry_descriptor/max_number_of_contexts448Date: February 2018449Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>450Description: This file shows maximum available number of contexts which451 are supported by the device. This is one of the UFS geometry452 descriptor parameters. The full information about the453 descriptor could be found at UFS specifications 2.1.454 455 The file is read only.456 457What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/sys_data_tag_unit_size458What: /sys/bus/platform/devices/*.ufs/geometry_descriptor/sys_data_tag_unit_size459Date: February 2018460Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>461Description: This file shows system data tag unit size. This is one of462 the UFS geometry descriptor parameters. The full information463 about the descriptor could be found at UFS specifications 2.1.464 465 The file is read only.466 467What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/sys_data_tag_resource_size468What: /sys/bus/platform/devices/*.ufs/geometry_descriptor/sys_data_tag_resource_size469Date: February 2018470Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>471Description: This file shows maximum storage area size allocated by472 the device to handle system data by the tagging mechanism.473 This is one of the UFS geometry descriptor parameters.474 The full information about the descriptor could be found at475 UFS specifications 2.1.476 477 The file is read only.478 479What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/secure_removal_types480What: /sys/bus/platform/devices/*.ufs/geometry_descriptor/secure_removal_types481Date: February 2018482Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>483Description: This file shows supported secure removal types. This is484 one of the UFS geometry descriptor parameters. The full485 information about the descriptor could be found at486 UFS specifications 2.1.487 488 The file is read only.489 490What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/memory_types491What: /sys/bus/platform/devices/*.ufs/geometry_descriptor/memory_types492Date: February 2018493Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>494Description: This file shows supported memory types. This is one of495 the UFS geometry descriptor parameters. The full496 information about the descriptor could be found at497 UFS specifications 2.1.498 499 The file is read only.500 501What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/*_memory_max_alloc_units502What: /sys/bus/platform/devices/*.ufs/geometry_descriptor/*_memory_max_alloc_units503Date: February 2018504Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>505Description: This file shows the maximum number of allocation units for506 different memory types (system code, non persistent,507 enhanced type 1-4). This is one of the UFS geometry508 descriptor parameters. The full information about the509 descriptor could be found at UFS specifications 2.1.510 511 The file is read only.512 513What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/*_memory_capacity_adjustment_factor514What: /sys/bus/platform/devices/*.ufs/geometry_descriptor/*_memory_capacity_adjustment_factor515Date: February 2018516Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>517Description: This file shows the memory capacity adjustment factor for518 different memory types (system code, non persistent,519 enhanced type 1-4). This is one of the UFS geometry520 descriptor parameters. The full information about the521 descriptor could be found at UFS specifications 2.1.522 523 The file is read only.524 525 526What: /sys/bus/platform/drivers/ufshcd/*/health_descriptor/eol_info527What: /sys/bus/platform/devices/*.ufs/health_descriptor/eol_info528Date: February 2018529Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>530Description: This file shows preend of life information. This is one531 of the UFS health descriptor parameters. The full532 information about the descriptor could be found at533 UFS specifications 2.1.534 535 The file is read only.536 537What: /sys/bus/platform/drivers/ufshcd/*/health_descriptor/life_time_estimation_a538What: /sys/bus/platform/devices/*.ufs/health_descriptor/life_time_estimation_a539Date: February 2018540Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>541Description: This file shows indication of the device life time542 (method a). This is one of the UFS health descriptor543 parameters. The full information about the descriptor544 could be found at UFS specifications 2.1.545 546 The file is read only.547 548What: /sys/bus/platform/drivers/ufshcd/*/health_descriptor/life_time_estimation_b549What: /sys/bus/platform/devices/*.ufs/health_descriptor/life_time_estimation_b550Date: February 2018551Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>552Description: This file shows indication of the device life time553 (method b). This is one of the UFS health descriptor554 parameters. The full information about the descriptor555 could be found at UFS specifications 2.1.556 557 The file is read only.558 559 560What: /sys/bus/platform/drivers/ufshcd/*/power_descriptor/active_icc_levels_vcc*561What: /sys/bus/platform/devices/*.ufs/power_descriptor/active_icc_levels_vcc*562Date: February 2018563Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>564Description: This file shows maximum VCC, VCCQ and VCCQ2 value for565 active ICC levels from 0 to 15. This is one of the UFS566 power descriptor parameters. The full information about567 the descriptor could be found at UFS specifications 2.1.568 569 The file is read only.570 571 572What: /sys/bus/platform/drivers/ufshcd/*/string_descriptors/manufacturer_name573What: /sys/bus/platform/devices/*.ufs/string_descriptors/manufacturer_name574Date: February 2018575Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>576Description: This file contains a device manufacturer name string.577 The full information about the descriptor could be found at578 UFS specifications 2.1.579 580 The file is read only.581 582What: /sys/bus/platform/drivers/ufshcd/*/string_descriptors/product_name583What: /sys/bus/platform/devices/*.ufs/string_descriptors/product_name584Date: February 2018585Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>586Description: This file contains a product name string. The full information587 about the descriptor could be found at UFS specifications 2.1.588 589 The file is read only.590 591What: /sys/bus/platform/drivers/ufshcd/*/string_descriptors/oem_id592What: /sys/bus/platform/devices/*.ufs/string_descriptors/oem_id593Date: February 2018594Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>595Description: This file contains a OEM ID string. The full information596 about the descriptor could be found at UFS specifications 2.1.597 598 The file is read only.599 600What: /sys/bus/platform/drivers/ufshcd/*/string_descriptors/serial_number601What: /sys/bus/platform/devices/*.ufs/string_descriptors/serial_number602Date: February 2018603Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>604Description: This file contains a device serial number string. The full605 information about the descriptor could be found at606 UFS specifications 2.1.607 608 The file is read only.609 610What: /sys/bus/platform/drivers/ufshcd/*/string_descriptors/product_revision611What: /sys/bus/platform/devices/*.ufs/string_descriptors/product_revision612Date: February 2018613Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>614Description: This file contains a product revision string. The full615 information about the descriptor could be found at616 UFS specifications 2.1.617 618 The file is read only.619 620 621What: /sys/class/scsi_device/*/device/unit_descriptor/boot_lun_id622Date: February 2018623Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>624Description: This file shows boot LUN information. This is one of625 the UFS unit descriptor parameters. The full information626 about the descriptor could be found at UFS specifications 2.1.627 628 The file is read only.629 630What: /sys/class/scsi_device/*/device/unit_descriptor/lun_write_protect631Date: February 2018632Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>633Description: This file shows LUN write protection status. This is one of634 the UFS unit descriptor parameters. The full information635 about the descriptor could be found at UFS specifications 2.1.636 637 The file is read only.638 639What: /sys/class/scsi_device/*/device/unit_descriptor/lun_queue_depth640Date: February 2018641Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>642Description: This file shows LUN queue depth. This is one of the UFS643 unit descriptor parameters. The full information about644 the descriptor could be found at UFS specifications 2.1.645 646 The file is read only.647 648What: /sys/class/scsi_device/*/device/unit_descriptor/psa_sensitive649Date: February 2018650Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>651Description: This file shows PSA sensitivity. This is one of the UFS652 unit descriptor parameters. The full information about653 the descriptor could be found at UFS specifications 2.1.654 655 The file is read only.656 657What: /sys/class/scsi_device/*/device/unit_descriptor/lun_memory_type658Date: February 2018659Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>660Description: This file shows LUN memory type. This is one of the UFS661 unit descriptor parameters. The full information about662 the descriptor could be found at UFS specifications 2.1.663 664 The file is read only.665 666What: /sys/class/scsi_device/*/device/unit_descriptor/data_reliability667Date: February 2018668Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>669Description: This file defines the device behavior when a power failure670 occurs during a write operation. This is one of the UFS671 unit descriptor parameters. The full information about672 the descriptor could be found at UFS specifications 2.1.673 674 The file is read only.675 676What: /sys/class/scsi_device/*/device/unit_descriptor/logical_block_size677Date: February 2018678Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>679Description: This file shows the size of addressable logical blocks680 (calculated as an exponent with base 2). This is one of681 the UFS unit descriptor parameters. The full information about682 the descriptor could be found at UFS specifications 2.1.683 684 The file is read only.685 686What: /sys/class/scsi_device/*/device/unit_descriptor/logical_block_count687Date: February 2018688Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>689Description: This file shows total number of addressable logical blocks.690 This is one of the UFS unit descriptor parameters. The full691 information about the descriptor could be found at692 UFS specifications 2.1.693 694 The file is read only.695 696What: /sys/class/scsi_device/*/device/unit_descriptor/erase_block_size697Date: February 2018698Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>699Description: This file shows the erase block size. This is one of700 the UFS unit descriptor parameters. The full information701 about the descriptor could be found at UFS specifications 2.1.702 703 The file is read only.704 705What: /sys/class/scsi_device/*/device/unit_descriptor/provisioning_type706Date: February 2018707Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>708Description: This file shows the thin provisioning type. This is one of709 the UFS unit descriptor parameters. The full information710 about the descriptor could be found at UFS specifications 2.1.711 712 The file is read only.713 714What: /sys/class/scsi_device/*/device/unit_descriptor/physical_memory_resourse_count715Date: February 2018716Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>717Description: This file shows the total physical memory resources. This is718 one of the UFS unit descriptor parameters. The full information719 about the descriptor could be found at UFS specifications 2.1.720 721 The file is read only.722 723What: /sys/class/scsi_device/*/device/unit_descriptor/context_capabilities724Date: February 2018725Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>726Description: This file shows the context capabilities. This is one of727 the UFS unit descriptor parameters. The full information728 about the descriptor could be found at UFS specifications 2.1.729 730 The file is read only.731 732What: /sys/class/scsi_device/*/device/unit_descriptor/large_unit_granularity733Date: February 2018734Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>735Description: This file shows the granularity of the LUN. This is one of736 the UFS unit descriptor parameters. The full information737 about the descriptor could be found at UFS specifications 2.1.738 739 The file is read only.740 741 742What: /sys/bus/platform/drivers/ufshcd/*/flags/device_init743What: /sys/bus/platform/devices/*.ufs/flags/device_init744Date: February 2018745Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>746Description: This file shows the device init status. The full information747 about the flag could be found at UFS specifications 2.1.748 749 The file is read only.750 751What: /sys/bus/platform/drivers/ufshcd/*/flags/permanent_wpe752What: /sys/bus/platform/devices/*.ufs/flags/permanent_wpe753Date: February 2018754Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>755Description: This file shows whether permanent write protection is enabled.756 The full information about the flag could be found at757 UFS specifications 2.1.758 759 The file is read only.760 761What: /sys/bus/platform/drivers/ufshcd/*/flags/power_on_wpe762What: /sys/bus/platform/devices/*.ufs/flags/power_on_wpe763Date: February 2018764Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>765Description: This file shows whether write protection is enabled on all766 logical units configured as power on write protected. The767 full information about the flag could be found at768 UFS specifications 2.1.769 770 The file is read only.771 772What: /sys/bus/platform/drivers/ufshcd/*/flags/bkops_enable773What: /sys/bus/platform/devices/*.ufs/flags/bkops_enable774Date: February 2018775Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>776Description: This file shows whether the device background operations are777 enabled. The full information about the flag could be778 found at UFS specifications 2.1.779 780 The file is read only.781 782What: /sys/bus/platform/drivers/ufshcd/*/flags/life_span_mode_enable783What: /sys/bus/platform/devices/*.ufs/flags/life_span_mode_enable784Date: February 2018785Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>786Description: This file shows whether the device life span mode is enabled.787 The full information about the flag could be found at788 UFS specifications 2.1.789 790 The file is read only.791 792What: /sys/bus/platform/drivers/ufshcd/*/flags/phy_resource_removal793What: /sys/bus/platform/devices/*.ufs/flags/phy_resource_removal794Date: February 2018795Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>796Description: This file shows whether physical resource removal is enable.797 The full information about the flag could be found at798 UFS specifications 2.1.799 800 The file is read only.801 802What: /sys/bus/platform/drivers/ufshcd/*/flags/busy_rtc803What: /sys/bus/platform/devices/*.ufs/flags/busy_rtc804Date: February 2018805Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>806Description: This file shows whether the device is executing internal807 operation related to real time clock. The full information808 about the flag could be found at UFS specifications 2.1.809 810 The file is read only.811 812What: /sys/bus/platform/drivers/ufshcd/*/flags/disable_fw_update813What: /sys/bus/platform/devices/*.ufs/flags/disable_fw_update814Date: February 2018815Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>816Description: This file shows whether the device FW update is permanently817 disabled. The full information about the flag could be found818 at UFS specifications 2.1.819 820 The file is read only.821 822 823What: /sys/bus/platform/drivers/ufshcd/*/attributes/boot_lun_enabled824What: /sys/bus/platform/devices/*.ufs/attributes/boot_lun_enabled825Date: February 2018826Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>827Description: This file provides the boot lun enabled UFS device attribute.828 The full information about the attribute could be found at829 UFS specifications 2.1.830 831 The file is read only.832 833What: /sys/bus/platform/drivers/ufshcd/*/attributes/current_power_mode834What: /sys/bus/platform/devices/*.ufs/attributes/current_power_mode835Date: February 2018836Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>837Description: This file provides the current power mode UFS device attribute.838 The full information about the attribute could be found at839 UFS specifications 2.1.840 841 The file is read only.842 843What: /sys/bus/platform/drivers/ufshcd/*/attributes/active_icc_level844What: /sys/bus/platform/devices/*.ufs/attributes/active_icc_level845Date: February 2018846Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>847Description: This file provides the active icc level UFS device attribute.848 The full information about the attribute could be found at849 UFS specifications 2.1.850 851 The file is read only.852 853What: /sys/bus/platform/drivers/ufshcd/*/attributes/ooo_data_enabled854What: /sys/bus/platform/devices/*.ufs/attributes/ooo_data_enabled855Date: February 2018856Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>857Description: This file provides the out of order data transfer enabled UFS858 device attribute. The full information about the attribute859 could be found at UFS specifications 2.1.860 861 The file is read only.862 863What: /sys/bus/platform/drivers/ufshcd/*/attributes/bkops_status864What: /sys/bus/platform/devices/*.ufs/attributes/bkops_status865Date: February 2018866Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>867Description: This file provides the background operations status UFS device868 attribute. The full information about the attribute could869 be found at UFS specifications 2.1.870 871 The file is read only.872 873What: /sys/bus/platform/drivers/ufshcd/*/attributes/purge_status874What: /sys/bus/platform/devices/*.ufs/attributes/purge_status875Date: February 2018876Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>877Description: This file provides the purge operation status UFS device878 attribute. The full information about the attribute could879 be found at UFS specifications 2.1.880 881 The file is read only.882 883What: /sys/bus/platform/drivers/ufshcd/*/attributes/max_data_in_size884What: /sys/bus/platform/devices/*.ufs/attributes/max_data_in_size885Date: February 2018886Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>887Description: This file shows the maximum data size in a DATA IN888 UPIU. The full information about the attribute could889 be found at UFS specifications 2.1.890 891 The file is read only.892 893What: /sys/bus/platform/drivers/ufshcd/*/attributes/max_data_out_size894What: /sys/bus/platform/devices/*.ufs/attributes/max_data_out_size895Date: February 2018896Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>897Description: This file shows the maximum number of bytes that can be898 requested with a READY TO TRANSFER UPIU. The full information899 about the attribute could be found at UFS specifications 2.1.900 901 The file is read only.902 903What: /sys/bus/platform/drivers/ufshcd/*/attributes/reference_clock_frequency904What: /sys/bus/platform/devices/*.ufs/attributes/reference_clock_frequency905Date: February 2018906Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>907Description: This file provides the reference clock frequency UFS device908 attribute. The full information about the attribute could909 be found at UFS specifications 2.1.910 911 The file is read only.912 913What: /sys/bus/platform/drivers/ufshcd/*/attributes/configuration_descriptor_lock914What: /sys/bus/platform/devices/*.ufs/attributes/configuration_descriptor_lock915Date: February 2018916Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>917Description: This file shows whether the configuration descriptor is locked.918 The full information about the attribute could be found at919 UFS specifications 2.1. The file is read only.920 921What: /sys/bus/platform/drivers/ufshcd/*/attributes/max_number_of_rtt922What: /sys/bus/platform/devices/*.ufs/attributes/max_number_of_rtt923Date: May 2024924Contact: Avri Altman <avri.altman@wdc.com>925Description: This file provides the maximum current number of926 outstanding RTTs in device that is allowed. bMaxNumOfRTT is a927 read-write persistent attribute and is equal to two after device928 manufacturing. It shall not be set to a value greater than929 bDeviceRTTCap value, and it may be set only when the hw queues are930 empty.931 932 The file is read write.933 934What: /sys/bus/platform/drivers/ufshcd/*/attributes/exception_event_control935What: /sys/bus/platform/devices/*.ufs/attributes/exception_event_control936Date: February 2018937Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>938Description: This file provides the exception event control UFS device939 attribute. The full information about the attribute could940 be found at UFS specifications 2.1.941 942 The file is read only.943 944What: /sys/bus/platform/drivers/ufshcd/*/attributes/exception_event_status945What: /sys/bus/platform/devices/*.ufs/attributes/exception_event_status946Date: February 2018947Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>948Description: This file provides the exception event status UFS device949 attribute. The full information about the attribute could950 be found at UFS specifications 2.1.951 952 The file is read only.953 954What: /sys/bus/platform/drivers/ufshcd/*/attributes/ffu_status955What: /sys/bus/platform/devices/*.ufs/attributes/ffu_status956Date: February 2018957Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>958Description: This file provides the ffu status UFS device attribute.959 The full information about the attribute could be found at960 UFS specifications 2.1.961 962 The file is read only.963 964What: /sys/bus/platform/drivers/ufshcd/*/attributes/psa_state965What: /sys/bus/platform/devices/*.ufs/attributes/psa_state966Date: February 2018967Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>968Description: This file show the PSA feature status. The full information969 about the attribute could be found at UFS specifications 2.1.970 971 The file is read only.972 973What: /sys/bus/platform/drivers/ufshcd/*/attributes/psa_data_size974What: /sys/bus/platform/devices/*.ufs/attributes/psa_data_size975Date: February 2018976Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>977Description: This file shows the amount of data that the host plans to978 load to all logical units in pre-soldering state.979 The full information about the attribute could be found at980 UFS specifications 2.1.981 982 The file is read only.983 984 985What: /sys/class/scsi_device/*/device/dyn_cap_needed986Date: February 2018987Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>988Description: This file shows the amount of physical memory needed989 to be removed from the physical memory resources pool of990 the particular logical unit. The full information about991 the attribute could be found at UFS specifications 2.1.992 993 The file is read only.994 995 996What: /sys/bus/platform/drivers/ufshcd/*/rpm_lvl997What: /sys/bus/platform/devices/*.ufs/rpm_lvl998Date: September 2014999Contact: Can Guo <quic_cang@quicinc.com>1000Description: This entry could be used to set or show the UFS device1001 runtime power management level. The current driver1002 implementation supports 7 levels with next target states:1003 1004 == ====================================================1005 0 UFS device will stay active, UIC link will1006 stay active1007 1 UFS device will stay active, UIC link will1008 hibernate1009 2 UFS device will be moved to sleep, UIC link will1010 stay active1011 3 UFS device will be moved to sleep, UIC link will1012 hibernate1013 4 UFS device will be powered off, UIC link will1014 hibernate1015 5 UFS device will be powered off, UIC link will1016 be powered off1017 6 UFS device will be moved to deep sleep, UIC link1018 will be powered off. Note, deep sleep might not be1019 supported in which case this value will not be1020 accepted1021 == ====================================================1022 1023What: /sys/bus/platform/drivers/ufshcd/*/rpm_target_dev_state1024What: /sys/bus/platform/devices/*.ufs/rpm_target_dev_state1025Date: February 20181026Contact: Can Guo <quic_cang@quicinc.com>1027Description: This entry shows the target power mode of an UFS device1028 for the chosen runtime power management level.1029 1030 The file is read only.1031 1032What: /sys/bus/platform/drivers/ufshcd/*/rpm_target_link_state1033What: /sys/bus/platform/devices/*.ufs/rpm_target_link_state1034Date: February 20181035Contact: Can Guo <quic_cang@quicinc.com>1036Description: This entry shows the target state of an UFS UIC link1037 for the chosen runtime power management level.1038 1039 The file is read only.1040 1041What: /sys/bus/platform/drivers/ufshcd/*/spm_lvl1042What: /sys/bus/platform/devices/*.ufs/spm_lvl1043Date: September 20141044Contact: Can Guo <quic_cang@quicinc.com>1045Description: This entry could be used to set or show the UFS device1046 system power management level. The current driver1047 implementation supports 7 levels with next target states:1048 1049 == ====================================================1050 0 UFS device will stay active, UIC link will1051 stay active1052 1 UFS device will stay active, UIC link will1053 hibernate1054 2 UFS device will be moved to sleep, UIC link will1055 stay active1056 3 UFS device will be moved to sleep, UIC link will1057 hibernate1058 4 UFS device will be powered off, UIC link will1059 hibernate1060 5 UFS device will be powered off, UIC link will1061 be powered off1062 6 UFS device will be moved to deep sleep, UIC link1063 will be powered off. Note, deep sleep might not be1064 supported in which case this value will not be1065 accepted1066 == ====================================================1067 1068What: /sys/bus/platform/drivers/ufshcd/*/spm_target_dev_state1069What: /sys/bus/platform/devices/*.ufs/spm_target_dev_state1070Date: February 20181071Contact: Can Guo <quic_cang@quicinc.com>1072Description: This entry shows the target power mode of an UFS device1073 for the chosen system power management level.1074 1075 The file is read only.1076 1077What: /sys/bus/platform/drivers/ufshcd/*/spm_target_link_state1078What: /sys/bus/platform/devices/*.ufs/spm_target_link_state1079Date: February 20181080Contact: Can Guo <quic_cang@quicinc.com>1081Description: This entry shows the target state of an UFS UIC link1082 for the chosen system power management level.1083 1084 The file is read only.1085 1086What: /sys/bus/platform/drivers/ufshcd/*/monitor/monitor_enable1087What: /sys/bus/platform/devices/*.ufs/monitor/monitor_enable1088Date: January 20211089Contact: Can Guo <quic_cang@quicinc.com>1090Description: This file shows the status of performance monitor enablement1091 and it can be used to start/stop the monitor. When the monitor1092 is stopped, the performance data collected is also cleared.1093 1094What: /sys/bus/platform/drivers/ufshcd/*/monitor/monitor_chunk_size1095What: /sys/bus/platform/devices/*.ufs/monitor/monitor_chunk_size1096Date: January 20211097Contact: Can Guo <quic_cang@quicinc.com>1098Description: This file tells the monitor to focus on requests transferring1099 data of specific chunk size (in Bytes). 0 means any chunk size.1100 It can only be changed when monitor is disabled.1101 1102What: /sys/bus/platform/drivers/ufshcd/*/monitor/read_total_sectors1103What: /sys/bus/platform/devices/*.ufs/monitor/read_total_sectors1104Date: January 20211105Contact: Can Guo <quic_cang@quicinc.com>1106Description: This file shows how many sectors (in 512 Bytes) have been1107 sent from device to host after monitor gets started.1108 1109 The file is read only.1110 1111What: /sys/bus/platform/drivers/ufshcd/*/monitor/read_total_busy1112What: /sys/bus/platform/devices/*.ufs/monitor/read_total_busy1113Date: January 20211114Contact: Can Guo <quic_cang@quicinc.com>1115Description: This file shows how long (in micro seconds) has been spent1116 sending data from device to host after monitor gets started.1117 1118 The file is read only.1119 1120What: /sys/bus/platform/drivers/ufshcd/*/monitor/read_nr_requests1121What: /sys/bus/platform/devices/*.ufs/monitor/read_nr_requests1122Date: January 20211123Contact: Can Guo <quic_cang@quicinc.com>1124Description: This file shows how many read requests have been sent after1125 monitor gets started.1126 1127 The file is read only.1128 1129What: /sys/bus/platform/drivers/ufshcd/*/monitor/read_req_latency_max1130What: /sys/bus/platform/devices/*.ufs/monitor/read_req_latency_max1131Date: January 20211132Contact: Can Guo <quic_cang@quicinc.com>1133Description: This file shows the maximum latency (in micro seconds) of1134 read requests after monitor gets started.1135 1136 The file is read only.1137 1138What: /sys/bus/platform/drivers/ufshcd/*/monitor/read_req_latency_min1139What: /sys/bus/platform/devices/*.ufs/monitor/read_req_latency_min1140Date: January 20211141Contact: Can Guo <quic_cang@quicinc.com>1142Description: This file shows the minimum latency (in micro seconds) of1143 read requests after monitor gets started.1144 1145 The file is read only.1146 1147What: /sys/bus/platform/drivers/ufshcd/*/monitor/read_req_latency_avg1148What: /sys/bus/platform/devices/*.ufs/monitor/read_req_latency_avg1149Date: January 20211150Contact: Can Guo <quic_cang@quicinc.com>1151Description: This file shows the average latency (in micro seconds) of1152 read requests after monitor gets started.1153 1154 The file is read only.1155 1156What: /sys/bus/platform/drivers/ufshcd/*/monitor/read_req_latency_sum1157What: /sys/bus/platform/devices/*.ufs/monitor/read_req_latency_sum1158Date: January 20211159Contact: Can Guo <quic_cang@quicinc.com>1160Description: This file shows the total latency (in micro seconds) of1161 read requests sent after monitor gets started.1162 1163 The file is read only.1164 1165What: /sys/bus/platform/drivers/ufshcd/*/monitor/write_total_sectors1166What: /sys/bus/platform/devices/*.ufs/monitor/write_total_sectors1167Date: January 20211168Contact: Can Guo <quic_cang@quicinc.com>1169Description: This file shows how many sectors (in 512 Bytes) have been sent1170 from host to device after monitor gets started.1171 1172 The file is read only.1173 1174What: /sys/bus/platform/drivers/ufshcd/*/monitor/write_total_busy1175What: /sys/bus/platform/devices/*.ufs/monitor/write_total_busy1176Date: January 20211177Contact: Can Guo <quic_cang@quicinc.com>1178Description: This file shows how long (in micro seconds) has been spent1179 sending data from host to device after monitor gets started.1180 1181 The file is read only.1182 1183What: /sys/bus/platform/drivers/ufshcd/*/monitor/write_nr_requests1184What: /sys/bus/platform/devices/*.ufs/monitor/write_nr_requests1185Date: January 20211186Contact: Can Guo <quic_cang@quicinc.com>1187Description: This file shows how many write requests have been sent after1188 monitor gets started.1189 1190 The file is read only.1191 1192What: /sys/bus/platform/drivers/ufshcd/*/monitor/write_req_latency_max1193What: /sys/bus/platform/devices/*.ufs/monitor/write_req_latency_max1194Date: January 20211195Contact: Can Guo <quic_cang@quicinc.com>1196Description: This file shows the maximum latency (in micro seconds) of write1197 requests after monitor gets started.1198 1199 The file is read only.1200 1201What: /sys/bus/platform/drivers/ufshcd/*/monitor/write_req_latency_min1202What: /sys/bus/platform/devices/*.ufs/monitor/write_req_latency_min1203Date: January 20211204Contact: Can Guo <quic_cang@quicinc.com>1205Description: This file shows the minimum latency (in micro seconds) of write1206 requests after monitor gets started.1207 1208 The file is read only.1209 1210What: /sys/bus/platform/drivers/ufshcd/*/monitor/write_req_latency_avg1211What: /sys/bus/platform/devices/*.ufs/monitor/write_req_latency_avg1212Date: January 20211213Contact: Can Guo <quic_cang@quicinc.com>1214Description: This file shows the average latency (in micro seconds) of write1215 requests after monitor gets started.1216 1217 The file is read only.1218 1219What: /sys/bus/platform/drivers/ufshcd/*/monitor/write_req_latency_sum1220What: /sys/bus/platform/devices/*.ufs/monitor/write_req_latency_sum1221Date: January 20211222Contact: Can Guo <quic_cang@quicinc.com>1223Description: This file shows the total latency (in micro seconds) of write1224 requests after monitor gets started.1225 1226 The file is read only.1227 1228What: /sys/bus/platform/drivers/ufshcd/*/power_info/lane1229What: /sys/bus/platform/devices/*.ufs/power_info/lane1230Date: September 20231231Contact: Can Guo <quic_cang@quicinc.com>1232Description: This file shows how many lanes are enabled on the UFS link,1233 i.e., an output 2 means UFS link is operating with 2 lanes.1234 1235 The file is read only.1236 1237What: /sys/bus/platform/drivers/ufshcd/*/power_info/mode1238What: /sys/bus/platform/devices/*.ufs/power_info/mode1239Date: September 20231240Contact: Can Guo <quic_cang@quicinc.com>1241Description: This file shows the PA power mode of UFS.1242 1243 The file is read only.1244 1245What: /sys/bus/platform/drivers/ufshcd/*/power_info/rate1246What: /sys/bus/platform/devices/*.ufs/power_info/rate1247Date: September 20231248Contact: Can Guo <quic_cang@quicinc.com>1249Description: This file shows the speed rate of UFS link.1250 1251 The file is read only.1252 1253What: /sys/bus/platform/drivers/ufshcd/*/power_info/gear1254What: /sys/bus/platform/devices/*.ufs/power_info/gear1255Date: September 20231256Contact: Can Guo <quic_cang@quicinc.com>1257Description: This file shows the gear of UFS link.1258 1259 The file is read only.1260 1261What: /sys/bus/platform/drivers/ufshcd/*/power_info/dev_pm1262What: /sys/bus/platform/devices/*.ufs/power_info/dev_pm1263Date: September 20231264Contact: Can Guo <quic_cang@quicinc.com>1265Description: This file shows the UFS device power mode.1266 1267 The file is read only.1268 1269What: /sys/bus/platform/drivers/ufshcd/*/power_info/link_state1270What: /sys/bus/platform/devices/*.ufs/power_info/link_state1271Date: September 20231272Contact: Can Guo <quic_cang@quicinc.com>1273Description: This file shows the state of UFS link.1274 1275 The file is read only.1276 1277What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/wb_presv_us_en1278What: /sys/bus/platform/devices/*.ufs/device_descriptor/wb_presv_us_en1279Date: June 20201280Contact: Asutosh Das <quic_asutoshd@quicinc.com>1281Description: This entry shows if preserve user-space was configured1282 1283 The file is read only.1284 1285What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/wb_shared_alloc_units1286What: /sys/bus/platform/devices/*.ufs/device_descriptor/wb_shared_alloc_units1287Date: June 20201288Contact: Asutosh Das <quic_asutoshd@quicinc.com>1289Description: This entry shows the shared allocated units of WB buffer1290 1291 The file is read only.1292 1293What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/wb_type1294What: /sys/bus/platform/devices/*.ufs/device_descriptor/wb_type1295Date: June 20201296Contact: Asutosh Das <quic_asutoshd@quicinc.com>1297Description: This entry shows the configured WB type.1298 0x1 for shared buffer mode. 0x0 for dedicated buffer mode.1299 1300 The file is read only.1301 1302What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/wb_buff_cap_adj1303What: /sys/bus/platform/devices/*.ufs/geometry_descriptor/wb_buff_cap_adj1304Date: June 20201305Contact: Asutosh Das <quic_asutoshd@quicinc.com>1306Description: This entry shows the total user-space decrease in shared1307 buffer mode.1308 The value of this parameter is 3 for TLC NAND when SLC mode1309 is used as WriteBooster Buffer. 2 for MLC NAND.1310 1311 The file is read only.1312 1313What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/wb_max_alloc_units1314What: /sys/bus/platform/devices/*.ufs/geometry_descriptor/wb_max_alloc_units1315Date: June 20201316Contact: Asutosh Das <quic_asutoshd@quicinc.com>1317Description: This entry shows the Maximum total WriteBooster Buffer size1318 which is supported by the entire device.1319 1320 The file is read only.1321 1322What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/wb_max_wb_luns1323What: /sys/bus/platform/devices/*.ufs/geometry_descriptor/wb_max_wb_luns1324Date: June 20201325Contact: Asutosh Das <quic_asutoshd@quicinc.com>1326Description: This entry shows the maximum number of luns that can support1327 WriteBooster.1328 1329 The file is read only.1330 1331What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/wb_sup_red_type1332What: /sys/bus/platform/devices/*.ufs/geometry_descriptor/wb_sup_red_type1333Date: June 20201334Contact: Asutosh Das <quic_asutoshd@quicinc.com>1335Description: The supportability of user space reduction mode1336 and preserve user space mode.1337 00h: WriteBooster Buffer can be configured only in1338 user space reduction type.1339 01h: WriteBooster Buffer can be configured only in1340 preserve user space type.1341 02h: Device can be configured in either user space1342 reduction type or preserve user space type.1343 1344 The file is read only.1345 1346What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/wb_sup_wb_type1347What: /sys/bus/platform/devices/*.ufs/geometry_descriptor/wb_sup_wb_type1348Date: June 20201349Contact: Asutosh Das <quic_asutoshd@quicinc.com>1350Description: The supportability of WriteBooster Buffer type.1351 1352 === ==========================================================1353 00h LU based WriteBooster Buffer configuration1354 01h Single shared WriteBooster Buffer configuration1355 02h Supporting both LU based WriteBooster.1356 Buffer and Single shared WriteBooster Buffer configuration1357 === ==========================================================1358 1359 The file is read only.1360 1361What: /sys/bus/platform/drivers/ufshcd/*/flags/wb_enable1362What: /sys/bus/platform/devices/*.ufs/flags/wb_enable1363Date: June 20201364Contact: Asutosh Das <quic_asutoshd@quicinc.com>1365Description: This entry shows the status of WriteBooster.1366 1367 == ============================1368 0 WriteBooster is not enabled.1369 1 WriteBooster is enabled1370 == ============================1371 1372 The file is read only.1373 1374What: /sys/bus/platform/drivers/ufshcd/*/flags/wb_flush_en1375What: /sys/bus/platform/devices/*.ufs/flags/wb_flush_en1376Date: June 20201377Contact: Asutosh Das <quic_asutoshd@quicinc.com>1378Description: This entry shows if flush is enabled.1379 1380 == =================================1381 0 Flush operation is not performed.1382 1 Flush operation is performed.1383 == =================================1384 1385 The file is read only.1386 1387What: /sys/bus/platform/drivers/ufshcd/*/flags/wb_flush_during_h81388What: /sys/bus/platform/devices/*.ufs/flags/wb_flush_during_h81389Date: June 20201390Contact: Asutosh Das <quic_asutoshd@quicinc.com>1391Description: Flush WriteBooster Buffer during hibernate state.1392 1393 == =================================================1394 0 Device is not allowed to flush the1395 WriteBooster Buffer during link hibernate state.1396 1 Device is allowed to flush the1397 WriteBooster Buffer during link hibernate state.1398 == =================================================1399 1400 The file is read only.1401 1402What: /sys/bus/platform/drivers/ufshcd/*/attributes/wb_avail_buf1403What: /sys/bus/platform/devices/*.ufs/attributes/wb_avail_buf1404Date: June 20201405Contact: Asutosh Das <quic_asutoshd@quicinc.com>1406Description: This entry shows the amount of unused WriteBooster buffer1407 available.1408 1409 The file is read only.1410 1411What: /sys/bus/platform/drivers/ufshcd/*/attributes/wb_cur_buf1412What: /sys/bus/platform/devices/*.ufs/attributes/wb_cur_buf1413Date: June 20201414Contact: Asutosh Das <quic_asutoshd@quicinc.com>1415Description: This entry shows the amount of unused current buffer.1416 1417 The file is read only.1418 1419What: /sys/bus/platform/drivers/ufshcd/*/attributes/wb_flush_status1420What: /sys/bus/platform/devices/*.ufs/attributes/wb_flush_status1421Date: June 20201422Contact: Asutosh Das <quic_asutoshd@quicinc.com>1423Description: This entry shows the flush operation status.1424 1425 1426 === ======================================1427 00h idle1428 01h Flush operation in progress1429 02h Flush operation stopped prematurely.1430 03h Flush operation completed successfully1431 04h Flush operation general failure1432 === ======================================1433 1434 The file is read only.1435 1436What: /sys/bus/platform/drivers/ufshcd/*/attributes/wb_life_time_est1437What: /sys/bus/platform/devices/*.ufs/attributes/wb_life_time_est1438Date: June 20201439Contact: Asutosh Das <quic_asutoshd@quicinc.com>1440Description: This entry shows an indication of the WriteBooster Buffer1441 lifetime based on the amount of performed program/erase cycles1442 1443 === =============================================1444 01h 0% - 10% WriteBooster Buffer life time used1445 ...1446 0Ah 90% - 100% WriteBooster Buffer life time used1447 === =============================================1448 1449 The file is read only.1450 1451What: /sys/class/scsi_device/*/device/unit_descriptor/wb_buf_alloc_units1452Date: June 20201453Contact: Asutosh Das <quic_asutoshd@quicinc.com>1454Description: This entry shows the configured size of WriteBooster buffer.1455 0400h corresponds to 4GB.1456 1457 The file is read only.1458 1459What: /sys/bus/platform/drivers/ufshcd/*/wb_on1460What: /sys/bus/platform/devices/*.ufs/wb_on1461Date: January 20211462Contact: Bean Huo <beanhuo@micron.com>1463Description: This node is used to set or display whether UFS WriteBooster is1464 enabled. Echo 0 to this file to disable UFS WriteBooster or 1 to1465 enable it. The WriteBooster is enabled after power-on/reset,1466 however, it will be disabled/enable while CLK scaling down/up1467 (if the platform supports UFSHCD_CAP_CLK_SCALING). For a1468 platform that doesn't support UFSHCD_CAP_CLK_SCALING, we can1469 disable/enable WriteBooster through this sysfs node.1470 1471What: /sys/bus/platform/drivers/ufshcd/*/enable_wb_buf_flush1472What: /sys/bus/platform/devices/*.ufs/enable_wb_buf_flush1473Date: July 20221474Contact: Jinyoung Choi <j-young.choi@samsung.com>1475Description: This entry shows the status of WriteBooster buffer flushing1476 and it can be used to enable or disable the flushing.1477 If flushing is enabled, the device executes the flush1478 operation when the command queue is empty.1479 1480What: /sys/bus/platform/drivers/ufshcd/*/wb_flush_threshold1481What: /sys/bus/platform/devices/*.ufs/wb_flush_threshold1482Date: June 20231483Contact: Lu Hongfei <luhongfei@vivo.com>1484Description:1485 wb_flush_threshold represents the threshold for flushing WriteBooster buffer,1486 whose value expressed in unit of 10% granularity, such as '1' representing 10%,1487 '2' representing 20%, and so on.1488 If avail_wb_buff < wb_flush_threshold, it indicates that WriteBooster buffer needs to1489 be flushed, otherwise it is not necessary.1490 1491Contact: Daniil Lunev <dlunev@chromium.org>1492What: /sys/bus/platform/drivers/ufshcd/*/capabilities/1493What: /sys/bus/platform/devices/*.ufs/capabilities/1494Date: August 20221495Description: The group represents the effective capabilities of the1496 host-device pair. i.e. the capabilities which are enabled in the1497 driver for the specific host controller, supported by the host1498 controller and are supported and/or have compatible1499 configuration on the device side.1500 1501Contact: Daniil Lunev <dlunev@chromium.org>1502What: /sys/bus/platform/drivers/ufshcd/*/capabilities/clock_scaling1503What: /sys/bus/platform/devices/*.ufs/capabilities/clock_scaling1504Date: August 20221505Contact: Daniil Lunev <dlunev@chromium.org>1506Description: Indicates status of clock scaling.1507 1508 == ============================1509 0 Clock scaling is not supported.1510 1 Clock scaling is supported.1511 == ============================1512 1513 The file is read only.1514 1515What: /sys/bus/platform/drivers/ufshcd/*/capabilities/write_booster1516What: /sys/bus/platform/devices/*.ufs/capabilities/write_booster1517Date: August 20221518Contact: Daniil Lunev <dlunev@chromium.org>1519Description: Indicates status of Write Booster.1520 1521 == ============================1522 0 Write Booster can not be enabled.1523 1 Write Booster can be enabled.1524 == ============================1525 1526 The file is read only.1527 1528What: /sys/bus/platform/drivers/ufshcd/*/rtc_update_ms1529What: /sys/bus/platform/devices/*.ufs/rtc_update_ms1530Date: November 20231531Contact: Bean Huo <beanhuo@micron.com>1532Description:1533 rtc_update_ms indicates how often the host should synchronize or update the1534 UFS RTC. If set to 0, this will disable UFS RTC periodic update.1535 1536What: /sys/devices/platform/.../ufshci_capabilities/version1537Date: August 20241538Contact: Avri Altman <avri.altman@wdc.com>1539Description:1540 Host Capabilities register group: UFS version register.1541 Symbol - VER. This file shows the UFSHCD version.1542 Example: Version 3.12 would be represented as 0000_0312h.1543 The file is read only.1544 1545What: /sys/devices/platform/.../ufshci_capabilities/product_id1546Date: August 20241547Contact: Avri Altman <avri.altman@wdc.com>1548Description:1549 Host Capabilities register group: product ID register.1550 Symbol - HCPID. This file shows the UFSHCD product id.1551 The content of this register is vendor specific.1552 The file is read only.1553 1554What: /sys/devices/platform/.../ufshci_capabilities/man_id1555Date: August 20241556Contact: Avri Altman <avri.altman@wdc.com>1557Description:1558 Host Capabilities register group: manufacturer ID register.1559 Symbol - HCMID. This file shows the UFSHCD manufacturer id.1560 The Manufacturer ID is defined by JEDEC in JEDEC-JEP106.1561 The file is read only.1562