1What: /sys/bus/*/drivers/ufshcd/*/auto_hibern8 2Date: March 2018 3Contact: linux-scsi@vger.kernel.org 4Description: 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 7 enabled. Otherwise the value is the number of microseconds of 8 idle time before the UFS host controller will autonomously put 9 the link into hibernate state. That will save power at the 10 expense of increased latency. Note that the hardware supports 11 10-bit values with a power-of-ten multiplier which allows a 12 maximum value of 102300000. Refer to the UFS Host Controller 13 Interface specification for more details. 14 15What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/device_type 16Date: February 2018 17Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 18Description: This file shows the device type. This is one of the UFS 19 device descriptor parameters. The full information about 20 the descriptor could be found at UFS specifications 2.1. 21 The file is read only. 22 23What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/device_class 24Date: February 2018 25Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 26Description: This file shows the device class. This is one of the UFS 27 device descriptor parameters. The full information about 28 the descriptor could be found at UFS specifications 2.1. 29 The file is read only. 30 31What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/device_sub_class 32Date: February 2018 33Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 34Description: This file shows the UFS storage subclass. This is one of 35 the UFS device descriptor parameters. The full information 36 about the descriptor could be found at UFS specifications 2.1. 37 The file is read only. 38 39What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/protocol 40Date: February 2018 41Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 42Description: This file shows the protocol supported by an UFS device. 43 This is one of the UFS device descriptor parameters. 44 The full information about the descriptor could be found 45 at UFS specifications 2.1. 46 The file is read only. 47 48What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/number_of_luns 49Date: February 2018 50Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 51Description: This file shows number of logical units. This is one of 52 the UFS device descriptor parameters. The full information 53 about the descriptor could be found at UFS specifications 2.1. 54 The file is read only. 55 56What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/number_of_wluns 57Date: February 2018 58Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 59Description: This file shows number of well known logical units. 60 This is one of the UFS device descriptor parameters. 61 The full information about the descriptor could be found 62 at UFS specifications 2.1. 63 The file is read only. 64 65What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/boot_enable 66Date: February 2018 67Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 68Description: This file shows value that indicates whether the device is 69 enabled for boot. This is one of the UFS device descriptor 70 parameters. The full information about the descriptor could 71 be found at UFS specifications 2.1. 72 The file is read only. 73 74What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/descriptor_access_enable 75Date: February 2018 76Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 77Description: This file shows value that indicates whether the device 78 descriptor could be read after partial initialization phase 79 of the boot sequence. This is one of the UFS device descriptor 80 parameters. The full information about the descriptor could 81 be found at UFS specifications 2.1. 82 The file is read only. 83 84What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/initial_power_mode 85Date: February 2018 86Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 87Description: This file shows value that defines the power mode after 88 device initialization or hardware reset. This is one of 89 the UFS device descriptor parameters. The full information 90 about the descriptor could be found at UFS specifications 2.1. 91 The file is read only. 92 93What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/high_priority_lun 94Date: February 2018 95Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 96Description: This file shows the high priority lun. This is one of 97 the UFS device descriptor parameters. The full information 98 about the descriptor could be found at UFS specifications 2.1. 99 The file is read only. 100 101What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/secure_removal_type 102Date: February 2018 103Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 104Description: This file shows the secure removal type. This is one of 105 the UFS device descriptor parameters. The full information 106 about the descriptor could be found at UFS specifications 2.1. 107 The file is read only. 108 109What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/support_security_lun 110Date: February 2018 111Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 112Description: This file shows whether the security lun is supported. 113 This is one of the UFS device descriptor parameters. 114 The full information about the descriptor could be found 115 at UFS specifications 2.1. 116 The file is read only. 117 118What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/bkops_termination_latency 119Date: February 2018 120Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 121Description: This file shows the background operations termination 122 latency. This is one of the UFS device descriptor parameters. 123 The full information about the descriptor could be found 124 at UFS specifications 2.1. 125 The file is read only. 126 127What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/initial_active_icc_level 128Date: February 2018 129Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 130Description: This file shows the initial active ICC level. This is one 131 of the UFS device descriptor parameters. The full information 132 about the descriptor could be found at UFS specifications 2.1. 133 The file is read only. 134 135What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/specification_version 136Date: February 2018 137Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 138Description: This file shows the specification version. This is one 139 of the UFS device descriptor parameters. The full information 140 about the descriptor could be found at UFS specifications 2.1. 141 The file is read only. 142 143What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/manufacturing_date 144Date: February 2018 145Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 146Description: This file shows the manufacturing date in BCD format. 147 This is one of the UFS device descriptor parameters. 148 The full information about the descriptor could be found 149 at UFS specifications 2.1. 150 The file is read only. 151 152What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/manufacturer_id 153Date: February 2018 154Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 155Description: This file shows the manufacturee ID. This is one of the 156 UFS device descriptor parameters. The full information about 157 the descriptor could be found at UFS specifications 2.1. 158 The file is read only. 159 160What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/rtt_capability 161Date: February 2018 162Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 163Description: This file shows the maximum number of outstanding RTTs 164 supported by the device. This is one of the UFS device 165 descriptor parameters. The full information about 166 the descriptor could be found at UFS specifications 2.1. 167 The file is read only. 168 169What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/rtc_update 170Date: February 2018 171Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 172Description: This file shows the frequency and method of the realtime 173 clock update. This is one of the UFS device descriptor 174 parameters. The full information about the descriptor 175 could be found at UFS specifications 2.1. 176 The file is read only. 177 178What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/ufs_features 179Date: February 2018 180Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 181Description: This file shows which features are supported by the device. 182 This is one of the UFS device descriptor parameters. 183 The full information about the descriptor could be 184 found at UFS specifications 2.1. 185 The file is read only. 186 187What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/ffu_timeout 188Date: February 2018 189Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 190Description: This file shows the FFU timeout. This is one of the 191 UFS device descriptor parameters. The full information 192 about the descriptor could be found at UFS specifications 2.1. 193 The file is read only. 194 195What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/queue_depth 196Date: February 2018 197Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 198Description: This file shows the device queue depth. This is one of the 199 UFS device descriptor parameters. The full information 200 about the descriptor could be found at UFS specifications 2.1. 201 The file is read only. 202 203What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/device_version 204Date: February 2018 205Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 206Description: This file shows the device version. This is one of the 207 UFS device descriptor parameters. The full information 208 about the descriptor could be found at UFS specifications 2.1. 209 The file is read only. 210 211What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/number_of_secure_wpa 212Date: February 2018 213Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 214Description: This file shows number of secure write protect areas 215 supported by the device. This is one of the UFS device 216 descriptor parameters. The full information about 217 the descriptor could be found at UFS specifications 2.1. 218 The file is read only. 219 220What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/psa_max_data_size 221Date: February 2018 222Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 223Description: This file shows the maximum amount of data that may be 224 written during the pre-soldering phase of the PSA flow. 225 This is one of the UFS device descriptor parameters. 226 The full information about the descriptor could be found 227 at UFS specifications 2.1. 228 The file is read only. 229 230What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/psa_state_timeout 231Date: February 2018 232Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 233Description: This file shows the command maximum timeout for a change 234 in PSA state. This is one of the UFS device descriptor 235 parameters. The full information about the descriptor could 236 be found at UFS specifications 2.1. 237 The file is read only. 238 239 240What: /sys/bus/platform/drivers/ufshcd/*/interconnect_descriptor/unipro_version 241Date: February 2018 242Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 243Description: This file shows the MIPI UniPro version number in BCD format. 244 This is one of the UFS interconnect descriptor parameters. 245 The full information about the descriptor could be found at 246 UFS specifications 2.1. 247 The file is read only. 248 249What: /sys/bus/platform/drivers/ufshcd/*/interconnect_descriptor/mphy_version 250Date: February 2018 251Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 252Description: This file shows the MIPI M-PHY version number in BCD format. 253 This is one of the UFS interconnect descriptor parameters. 254 The full information about the descriptor could be found at 255 UFS specifications 2.1. 256 The file is read only. 257 258 259What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/raw_device_capacity 260Date: February 2018 261Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 262Description: This file shows the total memory quantity available to 263 the user to configure the device logical units. This is one 264 of the UFS geometry descriptor parameters. The full 265 information about the descriptor could be found at 266 UFS specifications 2.1. 267 The file is read only. 268 269What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/max_number_of_luns 270Date: February 2018 271Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 272Description: This file shows the maximum number of logical units 273 supported by the UFS device. This is one of the UFS 274 geometry descriptor parameters. The full information about 275 the descriptor could be found at UFS specifications 2.1. 276 The file is read only. 277 278What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/segment_size 279Date: February 2018 280Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 281Description: This file shows the segment size. This is one of the UFS 282 geometry descriptor parameters. The full information about 283 the descriptor could be found at UFS specifications 2.1. 284 The file is read only. 285 286What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/allocation_unit_size 287Date: February 2018 288Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 289Description: This file shows the allocation unit size. This is one of 290 the UFS geometry descriptor parameters. The full information 291 about the descriptor could be found at UFS specifications 2.1. 292 The file is read only. 293 294What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/min_addressable_block_size 295Date: February 2018 296Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 297Description: This file shows the minimum addressable block size. This 298 is one of the UFS geometry descriptor parameters. The full 299 information about the descriptor could be found at UFS 300 specifications 2.1. 301 The file is read only. 302 303What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/optimal_read_block_size 304Date: February 2018 305Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 306Description: This file shows the optimal read block size. This is one 307 of the UFS geometry descriptor parameters. The full 308 information about the descriptor could be found at UFS 309 specifications 2.1. 310 The file is read only. 311 312What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/optimal_write_block_size 313Date: February 2018 314Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 315Description: This file shows the optimal write block size. This is one 316 of the UFS geometry descriptor parameters. The full 317 information about the descriptor could be found at UFS 318 specifications 2.1. 319 The file is read only. 320 321What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/max_in_buffer_size 322Date: February 2018 323Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 324Description: This file shows the maximum data-in buffer size. This 325 is one of the UFS geometry descriptor parameters. The full 326 information about the descriptor could be found at UFS 327 specifications 2.1. 328 The file is read only. 329 330What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/max_out_buffer_size 331Date: February 2018 332Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 333Description: This file shows the maximum data-out buffer size. This 334 is one of the UFS geometry descriptor parameters. The full 335 information about the descriptor could be found at UFS 336 specifications 2.1. 337 The file is read only. 338 339What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/rpmb_rw_size 340Date: February 2018 341Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 342Description: This file shows the maximum number of RPMB frames allowed 343 in Security Protocol In/Out. This is one of the UFS geometry 344 descriptor parameters. The full information about the 345 descriptor could be found at UFS specifications 2.1. 346 The file is read only. 347 348What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/dyn_capacity_resource_policy 349Date: February 2018 350Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 351Description: This file shows the dynamic capacity resource policy. This 352 is one of the UFS geometry descriptor parameters. The full 353 information about the descriptor could be found at 354 UFS specifications 2.1. 355 The file is read only. 356 357What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/data_ordering 358Date: February 2018 359Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 360Description: This file shows support for out-of-order data transfer. 361 This is one of the UFS geometry descriptor parameters. 362 The full information about the descriptor could be found at 363 UFS specifications 2.1. 364 The file is read only. 365 366What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/max_number_of_contexts 367Date: February 2018 368Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 369Description: This file shows maximum available number of contexts which 370 are supported by the device. This is one of the UFS geometry 371 descriptor parameters. The full information about the 372 descriptor could be found at UFS specifications 2.1. 373 The file is read only. 374 375What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/sys_data_tag_unit_size 376Date: February 2018 377Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 378Description: This file shows system data tag unit size. This is one of 379 the UFS geometry descriptor parameters. The full information 380 about the descriptor could be found at UFS specifications 2.1. 381 The file is read only. 382 383What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/sys_data_tag_resource_size 384Date: February 2018 385Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 386Description: This file shows maximum storage area size allocated by 387 the device to handle system data by the tagging mechanism. 388 This is one of the UFS geometry descriptor parameters. 389 The full information about the descriptor could be found at 390 UFS specifications 2.1. 391 The file is read only. 392 393What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/secure_removal_types 394Date: February 2018 395Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 396Description: This file shows supported secure removal types. This is 397 one of the UFS geometry descriptor parameters. The full 398 information about the descriptor could be found at 399 UFS specifications 2.1. 400 The file is read only. 401 402What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/memory_types 403Date: February 2018 404Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 405Description: This file shows supported memory types. This is one of 406 the UFS geometry descriptor parameters. The full 407 information about the descriptor could be found at 408 UFS specifications 2.1. 409 The file is read only. 410 411What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/*_memory_max_alloc_units 412Date: February 2018 413Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 414Description: This file shows the maximum number of allocation units for 415 different memory types (system code, non persistent, 416 enhanced type 1-4). This is one of the UFS geometry 417 descriptor parameters. The full information about the 418 descriptor could be found at UFS specifications 2.1. 419 The file is read only. 420 421What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/*_memory_capacity_adjustment_factor 422Date: February 2018 423Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 424Description: This file shows the memory capacity adjustment factor for 425 different memory types (system code, non persistent, 426 enhanced type 1-4). This is one of the UFS geometry 427 descriptor parameters. The full information about the 428 descriptor could be found at UFS specifications 2.1. 429 The file is read only. 430 431 432What: /sys/bus/platform/drivers/ufshcd/*/health_descriptor/eol_info 433Date: February 2018 434Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 435Description: This file shows preend of life information. This is one 436 of the UFS health descriptor parameters. The full 437 information about the descriptor could be found at 438 UFS specifications 2.1. 439 The file is read only. 440 441What: /sys/bus/platform/drivers/ufshcd/*/health_descriptor/life_time_estimation_a 442Date: February 2018 443Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 444Description: This file shows indication of the device life time 445 (method a). This is one of the UFS health descriptor 446 parameters. The full information about the descriptor 447 could be found at UFS specifications 2.1. 448 The file is read only. 449 450What: /sys/bus/platform/drivers/ufshcd/*/health_descriptor/life_time_estimation_b 451Date: February 2018 452Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 453Description: This file shows indication of the device life time 454 (method b). This is one of the UFS health descriptor 455 parameters. The full information about the descriptor 456 could be found at UFS specifications 2.1. 457 The file is read only. 458 459 460What: /sys/bus/platform/drivers/ufshcd/*/power_descriptor/active_icc_levels_vcc* 461Date: February 2018 462Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 463Description: This file shows maximum VCC, VCCQ and VCCQ2 value for 464 active ICC levels from 0 to 15. This is one of the UFS 465 power descriptor parameters. The full information about 466 the descriptor could be found at UFS specifications 2.1. 467 The file is read only. 468 469 470What: /sys/bus/platform/drivers/ufshcd/*/string_descriptors/manufacturer_name 471Date: February 2018 472Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 473Description: This file contains a device manufactureer name string. 474 The full information about the descriptor could be found at 475 UFS specifications 2.1. 476 The file is read only. 477 478What: /sys/bus/platform/drivers/ufshcd/*/string_descriptors/product_name 479Date: February 2018 480Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 481Description: This file contains a product name string. The full information 482 about the descriptor could be found at UFS specifications 2.1. 483 The file is read only. 484 485What: /sys/bus/platform/drivers/ufshcd/*/string_descriptors/oem_id 486Date: February 2018 487Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 488Description: This file contains a OEM ID string. The full information 489 about the descriptor could be found at UFS specifications 2.1. 490 The file is read only. 491 492What: /sys/bus/platform/drivers/ufshcd/*/string_descriptors/serial_number 493Date: February 2018 494Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 495Description: This file contains a device serial number string. The full 496 information about the descriptor could be found at 497 UFS specifications 2.1. 498 The file is read only. 499 500What: /sys/bus/platform/drivers/ufshcd/*/string_descriptors/product_revision 501Date: February 2018 502Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 503Description: This file contains a product revision string. The full 504 information about the descriptor could be found at 505 UFS specifications 2.1. 506 The file is read only. 507 508 509What: /sys/class/scsi_device/*/device/unit_descriptor/boot_lun_id 510Date: February 2018 511Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 512Description: This file shows boot LUN information. This is one of 513 the UFS unit descriptor parameters. The full information 514 about the descriptor could be found at UFS specifications 2.1. 515 The file is read only. 516 517What: /sys/class/scsi_device/*/device/unit_descriptor/lun_write_protect 518Date: February 2018 519Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 520Description: This file shows LUN write protection status. This is one of 521 the UFS unit descriptor parameters. The full information 522 about the descriptor could be found at UFS specifications 2.1. 523 The file is read only. 524 525What: /sys/class/scsi_device/*/device/unit_descriptor/lun_queue_depth 526Date: February 2018 527Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 528Description: This file shows LUN queue depth. This is one of the UFS 529 unit descriptor parameters. The full information about 530 the descriptor could be found at UFS specifications 2.1. 531 The file is read only. 532 533What: /sys/class/scsi_device/*/device/unit_descriptor/psa_sensitive 534Date: February 2018 535Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 536Description: This file shows PSA sensitivity. This is one of the UFS 537 unit descriptor parameters. The full information about 538 the descriptor could be found at UFS specifications 2.1. 539 The file is read only. 540 541What: /sys/class/scsi_device/*/device/unit_descriptor/lun_memory_type 542Date: February 2018 543Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 544Description: This file shows LUN memory type. This is one of the UFS 545 unit descriptor parameters. The full information about 546 the descriptor could be found at UFS specifications 2.1. 547 The file is read only. 548 549What: /sys/class/scsi_device/*/device/unit_descriptor/data_reliability 550Date: February 2018 551Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 552Description: This file defines the device behavior when a power failure 553 occurs during a write operation. This is one of the UFS 554 unit descriptor parameters. The full information about 555 the descriptor could be found at UFS specifications 2.1. 556 The file is read only. 557 558What: /sys/class/scsi_device/*/device/unit_descriptor/logical_block_size 559Date: February 2018 560Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 561Description: This file shows the size of addressable logical blocks 562 (calculated as an exponent with base 2). This is one of 563 the UFS unit descriptor parameters. The full information about 564 the descriptor could be found at UFS specifications 2.1. 565 The file is read only. 566 567What: /sys/class/scsi_device/*/device/unit_descriptor/logical_block_count 568Date: February 2018 569Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 570Description: This file shows total number of addressable logical blocks. 571 This is one of the UFS unit descriptor parameters. The full 572 information about the descriptor could be found at 573 UFS specifications 2.1. 574 The file is read only. 575 576What: /sys/class/scsi_device/*/device/unit_descriptor/erase_block_size 577Date: February 2018 578Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 579Description: This file shows the erase block size. This is one of 580 the UFS unit descriptor parameters. The full information 581 about the descriptor could be found at UFS specifications 2.1. 582 The file is read only. 583 584What: /sys/class/scsi_device/*/device/unit_descriptor/provisioning_type 585Date: February 2018 586Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 587Description: This file shows the thin provisioning type. This is one of 588 the UFS unit descriptor parameters. The full information 589 about the descriptor could be found at UFS specifications 2.1. 590 The file is read only. 591 592What: /sys/class/scsi_device/*/device/unit_descriptor/physical_memory_resourse_count 593Date: February 2018 594Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 595Description: This file shows the total physical memory resources. This is 596 one of the UFS unit descriptor parameters. The full information 597 about the descriptor could be found at UFS specifications 2.1. 598 The file is read only. 599 600What: /sys/class/scsi_device/*/device/unit_descriptor/context_capabilities 601Date: February 2018 602Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 603Description: This file shows the context capabilities. This is one of 604 the UFS unit descriptor parameters. The full information 605 about the descriptor could be found at UFS specifications 2.1. 606 The file is read only. 607 608What: /sys/class/scsi_device/*/device/unit_descriptor/large_unit_granularity 609Date: February 2018 610Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 611Description: This file shows the granularity of the LUN. This is one of 612 the UFS unit descriptor parameters. The full information 613 about the descriptor could be found at UFS specifications 2.1. 614 The file is read only. 615 616 617What: /sys/bus/platform/drivers/ufshcd/*/flags/device_init 618Date: February 2018 619Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 620Description: This file shows the device init status. The full information 621 about the flag could be found at UFS specifications 2.1. 622 The file is read only. 623 624What: /sys/bus/platform/drivers/ufshcd/*/flags/permanent_wpe 625Date: February 2018 626Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 627Description: This file shows whether permanent write protection is enabled. 628 The full information about the flag could be found at 629 UFS specifications 2.1. 630 The file is read only. 631 632What: /sys/bus/platform/drivers/ufshcd/*/flags/power_on_wpe 633Date: February 2018 634Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 635Description: This file shows whether write protection is enabled on all 636 logical units configured as power on write protected. The 637 full information about the flag could be found at 638 UFS specifications 2.1. 639 The file is read only. 640 641What: /sys/bus/platform/drivers/ufshcd/*/flags/bkops_enable 642Date: February 2018 643Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 644Description: This file shows whether the device background operations are 645 enabled. The full information about the flag could be 646 found at UFS specifications 2.1. 647 The file is read only. 648 649What: /sys/bus/platform/drivers/ufshcd/*/flags/life_span_mode_enable 650Date: February 2018 651Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 652Description: This file shows whether the device life span mode is enabled. 653 The full information about the flag could be found at 654 UFS specifications 2.1. 655 The file is read only. 656 657What: /sys/bus/platform/drivers/ufshcd/*/flags/phy_resource_removal 658Date: February 2018 659Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 660Description: This file shows whether physical resource removal is enable. 661 The full information about the flag could be found at 662 UFS specifications 2.1. 663 The file is read only. 664 665What: /sys/bus/platform/drivers/ufshcd/*/flags/busy_rtc 666Date: February 2018 667Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 668Description: This file shows whether the device is executing internal 669 operation related to real time clock. The full information 670 about the flag could be found at UFS specifications 2.1. 671 The file is read only. 672 673What: /sys/bus/platform/drivers/ufshcd/*/flags/disable_fw_update 674Date: February 2018 675Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 676Description: This file shows whether the device FW update is permanently 677 disabled. The full information about the flag could be found 678 at UFS specifications 2.1. 679 The file is read only. 680 681 682What: /sys/bus/platform/drivers/ufshcd/*/attributes/boot_lun_enabled 683Date: February 2018 684Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 685Description: This file provides the boot lun enabled UFS device attribute. 686 The full information about the attribute could be found at 687 UFS specifications 2.1. 688 The file is read only. 689 690What: /sys/bus/platform/drivers/ufshcd/*/attributes/current_power_mode 691Date: February 2018 692Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 693Description: This file provides the current power mode UFS device attribute. 694 The full information about the attribute could be found at 695 UFS specifications 2.1. 696 The file is read only. 697 698What: /sys/bus/platform/drivers/ufshcd/*/attributes/active_icc_level 699Date: February 2018 700Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 701Description: This file provides the active icc level UFS device attribute. 702 The full information about the attribute could be found at 703 UFS specifications 2.1. 704 The file is read only. 705 706What: /sys/bus/platform/drivers/ufshcd/*/attributes/ooo_data_enabled 707Date: February 2018 708Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 709Description: This file provides the out of order data transfer enabled UFS 710 device attribute. The full information about the attribute 711 could be found at UFS specifications 2.1. 712 The file is read only. 713 714What: /sys/bus/platform/drivers/ufshcd/*/attributes/bkops_status 715Date: February 2018 716Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 717Description: This file provides the background operations status UFS device 718 attribute. The full information about the attribute could 719 be found at UFS specifications 2.1. 720 The file is read only. 721 722What: /sys/bus/platform/drivers/ufshcd/*/attributes/purge_status 723Date: February 2018 724Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 725Description: This file provides the purge operation status UFS device 726 attribute. The full information about the attribute could 727 be found at UFS specifications 2.1. 728 The file is read only. 729 730What: /sys/bus/platform/drivers/ufshcd/*/attributes/max_data_in_size 731Date: February 2018 732Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 733Description: This file shows the maximum data size in a DATA IN 734 UPIU. The full information about the attribute could 735 be found at UFS specifications 2.1. 736 The file is read only. 737 738What: /sys/bus/platform/drivers/ufshcd/*/attributes/max_data_out_size 739Date: February 2018 740Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 741Description: This file shows the maximum number of bytes that can be 742 requested with a READY TO TRANSFER UPIU. The full information 743 about the attribute could be found at UFS specifications 2.1. 744 The file is read only. 745 746What: /sys/bus/platform/drivers/ufshcd/*/attributes/reference_clock_frequency 747Date: February 2018 748Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 749Description: This file provides the reference clock frequency UFS device 750 attribute. The full information about the attribute could 751 be found at UFS specifications 2.1. 752 The file is read only. 753 754What: /sys/bus/platform/drivers/ufshcd/*/attributes/configuration_descriptor_lock 755Date: February 2018 756Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 757Description: This file shows whether the configuration descriptor is locked. 758 The full information about the attribute could be found at 759 UFS specifications 2.1. The file is read only. 760 761What: /sys/bus/platform/drivers/ufshcd/*/attributes/max_number_of_rtt 762Date: February 2018 763Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 764Description: This file provides the maximum current number of 765 outstanding RTTs in device that is allowed. The full 766 information about the attribute could be found at 767 UFS specifications 2.1. 768 The file is read only. 769 770What: /sys/bus/platform/drivers/ufshcd/*/attributes/exception_event_control 771Date: February 2018 772Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 773Description: This file provides the exception event control UFS device 774 attribute. The full information about the attribute could 775 be found at UFS specifications 2.1. 776 The file is read only. 777 778What: /sys/bus/platform/drivers/ufshcd/*/attributes/exception_event_status 779Date: February 2018 780Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 781Description: This file provides the exception event status UFS device 782 attribute. The full information about the attribute could 783 be found at UFS specifications 2.1. 784 The file is read only. 785 786What: /sys/bus/platform/drivers/ufshcd/*/attributes/ffu_status 787Date: February 2018 788Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 789Description: This file provides the ffu status UFS device attribute. 790 The full information about the attribute could be found at 791 UFS specifications 2.1. 792 The file is read only. 793 794What: /sys/bus/platform/drivers/ufshcd/*/attributes/psa_state 795Date: February 2018 796Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 797Description: This file show the PSA feature status. The full information 798 about the attribute could be found at UFS specifications 2.1. 799 The file is read only. 800 801What: /sys/bus/platform/drivers/ufshcd/*/attributes/psa_data_size 802Date: February 2018 803Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 804Description: This file shows the amount of data that the host plans to 805 load to all logical units in pre-soldering state. 806 The full information about the attribute could be found at 807 UFS specifications 2.1. 808 The file is read only. 809 810 811What: /sys/class/scsi_device/*/device/dyn_cap_needed 812Date: February 2018 813Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> 814Description: This file shows the The amount of physical memory needed 815 to be removed from the physical memory resources pool of 816 the particular logical unit. The full information about 817 the attribute could be found at UFS specifications 2.1. 818 The file is read only. 819 820 821What: /sys/bus/platform/drivers/ufshcd/*/rpm_lvl 822Date: September 2014 823Contact: Subhash Jadavani <subhashj@codeaurora.org> 824Description: This entry could be used to set or show the UFS device 825 runtime power management level. The current driver 826 implementation supports 6 levels with next target states: 827 0 - an UFS device will stay active, an UIC link will 828 stay active 829 1 - an UFS device will stay active, an UIC link will 830 hibernate 831 2 - an UFS device will moved to sleep, an UIC link will 832 stay active 833 3 - an UFS device will moved to sleep, an UIC link will 834 hibernate 835 4 - an UFS device will be powered off, an UIC link will 836 hibernate 837 5 - an UFS device will be powered off, an UIC link will 838 be powered off 839 840What: /sys/bus/platform/drivers/ufshcd/*/rpm_target_dev_state 841Date: February 2018 842Contact: Subhash Jadavani <subhashj@codeaurora.org> 843Description: This entry shows the target power mode of an UFS device 844 for the chosen runtime power management level. 845 The file is read only. 846 847What: /sys/bus/platform/drivers/ufshcd/*/rpm_target_link_state 848Date: February 2018 849Contact: Subhash Jadavani <subhashj@codeaurora.org> 850Description: This entry shows the target state of an UFS UIC link 851 for the chosen runtime power management level. 852 The file is read only. 853 854What: /sys/bus/platform/drivers/ufshcd/*/spm_lvl 855Date: September 2014 856Contact: Subhash Jadavani <subhashj@codeaurora.org> 857Description: This entry could be used to set or show the UFS device 858 system power management level. The current driver 859 implementation supports 6 levels with next target states: 860 0 - an UFS device will stay active, an UIC link will 861 stay active 862 1 - an UFS device will stay active, an UIC link will 863 hibernate 864 2 - an UFS device will moved to sleep, an UIC link will 865 stay active 866 3 - an UFS device will moved to sleep, an UIC link will 867 hibernate 868 4 - an UFS device will be powered off, an UIC link will 869 hibernate 870 5 - an UFS device will be powered off, an UIC link will 871 be powered off 872 873What: /sys/bus/platform/drivers/ufshcd/*/spm_target_dev_state 874Date: February 2018 875Contact: Subhash Jadavani <subhashj@codeaurora.org> 876Description: This entry shows the target power mode of an UFS device 877 for the chosen system power management level. 878 The file is read only. 879 880What: /sys/bus/platform/drivers/ufshcd/*/spm_target_link_state 881Date: February 2018 882Contact: Subhash Jadavani <subhashj@codeaurora.org> 883Description: This entry shows the target state of an UFS UIC link 884 for the chosen system power management level. 885 The file is read only. 886 887What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/wb_presv_us_en 888Date: June 2020 889Contact: Asutosh Das <asutoshd@codeaurora.org> 890Description: This entry shows if preserve user-space was configured 891 The file is read only. 892 893What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/wb_shared_alloc_units 894Date: June 2020 895Contact: Asutosh Das <asutoshd@codeaurora.org> 896Description: This entry shows the shared allocated units of WB buffer 897 The file is read only. 898 899What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/wb_type 900Date: June 2020 901Contact: Asutosh Das <asutoshd@codeaurora.org> 902Description: This entry shows the configured WB type. 903 0x1 for shared buffer mode. 0x0 for dedicated buffer mode. 904 The file is read only. 905 906What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/wb_buff_cap_adj 907Date: June 2020 908Contact: Asutosh Das <asutoshd@codeaurora.org> 909Description: This entry shows the total user-space decrease in shared 910 buffer mode. 911 The value of this parameter is 3 for TLC NAND when SLC mode 912 is used as WriteBooster Buffer. 2 for MLC NAND. 913 The file is read only. 914 915What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/wb_max_alloc_units 916Date: June 2020 917Contact: Asutosh Das <asutoshd@codeaurora.org> 918Description: This entry shows the Maximum total WriteBooster Buffer size 919 which is supported by the entire device. 920 The file is read only. 921 922What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/wb_max_wb_luns 923Date: June 2020 924Contact: Asutosh Das <asutoshd@codeaurora.org> 925Description: This entry shows the maximum number of luns that can support 926 WriteBooster. 927 The file is read only. 928 929What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/wb_sup_red_type 930Date: June 2020 931Contact: Asutosh Das <asutoshd@codeaurora.org> 932Description: The supportability of user space reduction mode 933 and preserve user space mode. 934 00h: WriteBooster Buffer can be configured only in 935 user space reduction type. 936 01h: WriteBooster Buffer can be configured only in 937 preserve user space type. 938 02h: Device can be configured in either user space 939 reduction type or preserve user space type. 940 The file is read only. 941 942What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/wb_sup_wb_type 943Date: June 2020 944Contact: Asutosh Das <asutoshd@codeaurora.org> 945Description: The supportability of WriteBooster Buffer type. 946 00h: LU based WriteBooster Buffer configuration 947 01h: Single shared WriteBooster Buffer 948 configuration 949 02h: Supporting both LU based WriteBooster 950 Buffer and Single shared WriteBooster Buffer 951 configuration 952 The file is read only. 953 954What: /sys/bus/platform/drivers/ufshcd/*/flags/wb_enable 955Date: June 2020 956Contact: Asutosh Das <asutoshd@codeaurora.org> 957Description: This entry shows the status of WriteBooster. 958 0: WriteBooster is not enabled. 959 1: WriteBooster is enabled 960 The file is read only. 961 962What: /sys/bus/platform/drivers/ufshcd/*/flags/wb_flush_en 963Date: June 2020 964Contact: Asutosh Das <asutoshd@codeaurora.org> 965Description: This entry shows if flush is enabled. 966 0: Flush operation is not performed. 967 1: Flush operation is performed. 968 The file is read only. 969 970What: /sys/bus/platform/drivers/ufshcd/*/flags/wb_flush_during_h8 971Date: June 2020 972Contact: Asutosh Das <asutoshd@codeaurora.org> 973Description: Flush WriteBooster Buffer during hibernate state. 974 0: Device is not allowed to flush the 975 WriteBooster Buffer during link hibernate 976 state. 977 1: Device is allowed to flush the 978 WriteBooster Buffer during link hibernate 979 state 980 The file is read only. 981 982What: /sys/bus/platform/drivers/ufshcd/*/attributes/wb_avail_buf 983Date: June 2020 984Contact: Asutosh Das <asutoshd@codeaurora.org> 985Description: This entry shows the amount of unused WriteBooster buffer 986 available. 987 The file is read only. 988 989What: /sys/bus/platform/drivers/ufshcd/*/attributes/wb_cur_buf 990Date: June 2020 991Contact: Asutosh Das <asutoshd@codeaurora.org> 992Description: This entry shows the amount of unused current buffer. 993 The file is read only. 994 995What: /sys/bus/platform/drivers/ufshcd/*/attributes/wb_flush_status 996Date: June 2020 997Contact: Asutosh Das <asutoshd@codeaurora.org> 998Description: This entry shows the flush operation status. 999 00h: idle 1000 01h: Flush operation in progress 1001 02h: Flush operation stopped prematurely. 1002 03h: Flush operation completed successfully 1003 04h: Flush operation general failure 1004 The file is read only. 1005 1006What: /sys/bus/platform/drivers/ufshcd/*/attributes/wb_life_time_est 1007Date: June 2020 1008Contact: Asutosh Das <asutoshd@codeaurora.org> 1009Description: This entry shows an indication of the WriteBooster Buffer 1010 lifetime based on the amount of performed program/erase cycles 1011 01h: 0% - 10% WriteBooster Buffer life time used 1012 ... 1013 0Ah: 90% - 100% WriteBooster Buffer life time used 1014 The file is read only. 1015 1016What: /sys/class/scsi_device/*/device/unit_descriptor/wb_buf_alloc_units 1017Date: June 2020 1018Contact: Asutosh Das <asutoshd@codeaurora.org> 1019Description: This entry shows the configured size of WriteBooster buffer. 1020 0400h corresponds to 4GB. 1021 The file is read only. 1022