Loading .mailmap +1 −0 Original line number Original line Diff line number Diff line Loading @@ -246,6 +246,7 @@ John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> John Stultz <johnstul@us.ibm.com> John Stultz <johnstul@us.ibm.com> <jon.toppins+linux@gmail.com> <jtoppins@cumulusnetworks.com> <jon.toppins+linux@gmail.com> <jtoppins@cumulusnetworks.com> <jon.toppins+linux@gmail.com> <jtoppins@redhat.com> <jon.toppins+linux@gmail.com> <jtoppins@redhat.com> Jonas Gorski <jonas.gorski@gmail.com> <jogo@openwrt.org> Jordan Crouse <jordan@cosmicpenguin.net> <jcrouse@codeaurora.org> Jordan Crouse <jordan@cosmicpenguin.net> <jcrouse@codeaurora.org> <josh@joshtriplett.org> <josh@freedesktop.org> <josh@joshtriplett.org> <josh@freedesktop.org> <josh@joshtriplett.org> <josh@kernel.org> <josh@joshtriplett.org> <josh@kernel.org> Loading Documentation/ABI/testing/sysfs-driver-ufs +38 −38 Original line number Original line Diff line number Diff line Loading @@ -994,7 +994,7 @@ Description: This file shows the amount of physical memory needed What: /sys/bus/platform/drivers/ufshcd/*/rpm_lvl What: /sys/bus/platform/drivers/ufshcd/*/rpm_lvl What: /sys/bus/platform/devices/*.ufs/rpm_lvl What: /sys/bus/platform/devices/*.ufs/rpm_lvl Date: September 2014 Date: September 2014 Contact: Subhash Jadavani <subhashj@codeaurora.org> Contact: Can Guo <quic_cang@quicinc.com> Description: This entry could be used to set or show the UFS device Description: This entry could be used to set or show the UFS device runtime power management level. The current driver runtime power management level. The current driver implementation supports 7 levels with next target states: implementation supports 7 levels with next target states: Loading @@ -1021,7 +1021,7 @@ Description: This entry could be used to set or show the UFS device What: /sys/bus/platform/drivers/ufshcd/*/rpm_target_dev_state What: /sys/bus/platform/drivers/ufshcd/*/rpm_target_dev_state What: /sys/bus/platform/devices/*.ufs/rpm_target_dev_state What: /sys/bus/platform/devices/*.ufs/rpm_target_dev_state Date: February 2018 Date: February 2018 Contact: Subhash Jadavani <subhashj@codeaurora.org> Contact: Can Guo <quic_cang@quicinc.com> Description: This entry shows the target power mode of an UFS device Description: This entry shows the target power mode of an UFS device for the chosen runtime power management level. for the chosen runtime power management level. Loading @@ -1030,7 +1030,7 @@ Description: This entry shows the target power mode of an UFS device What: /sys/bus/platform/drivers/ufshcd/*/rpm_target_link_state What: /sys/bus/platform/drivers/ufshcd/*/rpm_target_link_state What: /sys/bus/platform/devices/*.ufs/rpm_target_link_state What: /sys/bus/platform/devices/*.ufs/rpm_target_link_state Date: February 2018 Date: February 2018 Contact: Subhash Jadavani <subhashj@codeaurora.org> Contact: Can Guo <quic_cang@quicinc.com> Description: This entry shows the target state of an UFS UIC link Description: This entry shows the target state of an UFS UIC link for the chosen runtime power management level. for the chosen runtime power management level. Loading @@ -1039,7 +1039,7 @@ Description: This entry shows the target state of an UFS UIC link What: /sys/bus/platform/drivers/ufshcd/*/spm_lvl What: /sys/bus/platform/drivers/ufshcd/*/spm_lvl What: /sys/bus/platform/devices/*.ufs/spm_lvl What: /sys/bus/platform/devices/*.ufs/spm_lvl Date: September 2014 Date: September 2014 Contact: Subhash Jadavani <subhashj@codeaurora.org> Contact: Can Guo <quic_cang@quicinc.com> Description: This entry could be used to set or show the UFS device Description: This entry could be used to set or show the UFS device system power management level. The current driver system power management level. The current driver implementation supports 7 levels with next target states: implementation supports 7 levels with next target states: Loading @@ -1066,7 +1066,7 @@ Description: This entry could be used to set or show the UFS device What: /sys/bus/platform/drivers/ufshcd/*/spm_target_dev_state What: /sys/bus/platform/drivers/ufshcd/*/spm_target_dev_state What: /sys/bus/platform/devices/*.ufs/spm_target_dev_state What: /sys/bus/platform/devices/*.ufs/spm_target_dev_state Date: February 2018 Date: February 2018 Contact: Subhash Jadavani <subhashj@codeaurora.org> Contact: Can Guo <quic_cang@quicinc.com> Description: This entry shows the target power mode of an UFS device Description: This entry shows the target power mode of an UFS device for the chosen system power management level. for the chosen system power management level. Loading @@ -1075,7 +1075,7 @@ Description: This entry shows the target power mode of an UFS device What: /sys/bus/platform/drivers/ufshcd/*/spm_target_link_state What: /sys/bus/platform/drivers/ufshcd/*/spm_target_link_state What: /sys/bus/platform/devices/*.ufs/spm_target_link_state What: /sys/bus/platform/devices/*.ufs/spm_target_link_state Date: February 2018 Date: February 2018 Contact: Subhash Jadavani <subhashj@codeaurora.org> Contact: Can Guo <quic_cang@quicinc.com> Description: This entry shows the target state of an UFS UIC link Description: This entry shows the target state of an UFS UIC link for the chosen system power management level. for the chosen system power management level. Loading @@ -1084,7 +1084,7 @@ Description: This entry shows the target state of an UFS UIC link What: /sys/bus/platform/drivers/ufshcd/*/monitor/monitor_enable What: /sys/bus/platform/drivers/ufshcd/*/monitor/monitor_enable What: /sys/bus/platform/devices/*.ufs/monitor/monitor_enable What: /sys/bus/platform/devices/*.ufs/monitor/monitor_enable Date: January 2021 Date: January 2021 Contact: Can Guo <cang@codeaurora.org> Contact: Can Guo <quic_cang@quicinc.com> Description: This file shows the status of performance monitor enablement Description: This file shows the status of performance monitor enablement and it can be used to start/stop the monitor. When the monitor and it can be used to start/stop the monitor. When the monitor is stopped, the performance data collected is also cleared. is stopped, the performance data collected is also cleared. Loading @@ -1092,7 +1092,7 @@ Description: This file shows the status of performance monitor enablement What: /sys/bus/platform/drivers/ufshcd/*/monitor/monitor_chunk_size What: /sys/bus/platform/drivers/ufshcd/*/monitor/monitor_chunk_size What: /sys/bus/platform/devices/*.ufs/monitor/monitor_chunk_size What: /sys/bus/platform/devices/*.ufs/monitor/monitor_chunk_size Date: January 2021 Date: January 2021 Contact: Can Guo <cang@codeaurora.org> Contact: Can Guo <quic_cang@quicinc.com> Description: This file tells the monitor to focus on requests transferring Description: This file tells the monitor to focus on requests transferring data of specific chunk size (in Bytes). 0 means any chunk size. data of specific chunk size (in Bytes). 0 means any chunk size. It can only be changed when monitor is disabled. It can only be changed when monitor is disabled. Loading @@ -1100,7 +1100,7 @@ Description: This file tells the monitor to focus on requests transferring What: /sys/bus/platform/drivers/ufshcd/*/monitor/read_total_sectors What: /sys/bus/platform/drivers/ufshcd/*/monitor/read_total_sectors What: /sys/bus/platform/devices/*.ufs/monitor/read_total_sectors What: /sys/bus/platform/devices/*.ufs/monitor/read_total_sectors Date: January 2021 Date: January 2021 Contact: Can Guo <cang@codeaurora.org> Contact: Can Guo <quic_cang@quicinc.com> Description: This file shows how many sectors (in 512 Bytes) have been Description: This file shows how many sectors (in 512 Bytes) have been sent from device to host after monitor gets started. sent from device to host after monitor gets started. Loading @@ -1109,7 +1109,7 @@ Description: This file shows how many sectors (in 512 Bytes) have been What: /sys/bus/platform/drivers/ufshcd/*/monitor/read_total_busy What: /sys/bus/platform/drivers/ufshcd/*/monitor/read_total_busy What: /sys/bus/platform/devices/*.ufs/monitor/read_total_busy What: /sys/bus/platform/devices/*.ufs/monitor/read_total_busy Date: January 2021 Date: January 2021 Contact: Can Guo <cang@codeaurora.org> Contact: Can Guo <quic_cang@quicinc.com> Description: This file shows how long (in micro seconds) has been spent Description: This file shows how long (in micro seconds) has been spent sending data from device to host after monitor gets started. sending data from device to host after monitor gets started. Loading @@ -1118,7 +1118,7 @@ Description: This file shows how long (in micro seconds) has been spent What: /sys/bus/platform/drivers/ufshcd/*/monitor/read_nr_requests What: /sys/bus/platform/drivers/ufshcd/*/monitor/read_nr_requests What: /sys/bus/platform/devices/*.ufs/monitor/read_nr_requests What: /sys/bus/platform/devices/*.ufs/monitor/read_nr_requests Date: January 2021 Date: January 2021 Contact: Can Guo <cang@codeaurora.org> Contact: Can Guo <quic_cang@quicinc.com> Description: This file shows how many read requests have been sent after Description: This file shows how many read requests have been sent after monitor gets started. monitor gets started. Loading @@ -1127,7 +1127,7 @@ Description: This file shows how many read requests have been sent after What: /sys/bus/platform/drivers/ufshcd/*/monitor/read_req_latency_max What: /sys/bus/platform/drivers/ufshcd/*/monitor/read_req_latency_max What: /sys/bus/platform/devices/*.ufs/monitor/read_req_latency_max What: /sys/bus/platform/devices/*.ufs/monitor/read_req_latency_max Date: January 2021 Date: January 2021 Contact: Can Guo <cang@codeaurora.org> Contact: Can Guo <quic_cang@quicinc.com> Description: This file shows the maximum latency (in micro seconds) of Description: This file shows the maximum latency (in micro seconds) of read requests after monitor gets started. read requests after monitor gets started. Loading @@ -1136,7 +1136,7 @@ Description: This file shows the maximum latency (in micro seconds) of What: /sys/bus/platform/drivers/ufshcd/*/monitor/read_req_latency_min What: /sys/bus/platform/drivers/ufshcd/*/monitor/read_req_latency_min What: /sys/bus/platform/devices/*.ufs/monitor/read_req_latency_min What: /sys/bus/platform/devices/*.ufs/monitor/read_req_latency_min Date: January 2021 Date: January 2021 Contact: Can Guo <cang@codeaurora.org> Contact: Can Guo <quic_cang@quicinc.com> Description: This file shows the minimum latency (in micro seconds) of Description: This file shows the minimum latency (in micro seconds) of read requests after monitor gets started. read requests after monitor gets started. Loading @@ -1145,7 +1145,7 @@ Description: This file shows the minimum latency (in micro seconds) of What: /sys/bus/platform/drivers/ufshcd/*/monitor/read_req_latency_avg What: /sys/bus/platform/drivers/ufshcd/*/monitor/read_req_latency_avg What: /sys/bus/platform/devices/*.ufs/monitor/read_req_latency_avg What: /sys/bus/platform/devices/*.ufs/monitor/read_req_latency_avg Date: January 2021 Date: January 2021 Contact: Can Guo <cang@codeaurora.org> Contact: Can Guo <quic_cang@quicinc.com> Description: This file shows the average latency (in micro seconds) of Description: This file shows the average latency (in micro seconds) of read requests after monitor gets started. read requests after monitor gets started. Loading @@ -1154,7 +1154,7 @@ Description: This file shows the average latency (in micro seconds) of What: /sys/bus/platform/drivers/ufshcd/*/monitor/read_req_latency_sum What: /sys/bus/platform/drivers/ufshcd/*/monitor/read_req_latency_sum What: /sys/bus/platform/devices/*.ufs/monitor/read_req_latency_sum What: /sys/bus/platform/devices/*.ufs/monitor/read_req_latency_sum Date: January 2021 Date: January 2021 Contact: Can Guo <cang@codeaurora.org> Contact: Can Guo <quic_cang@quicinc.com> Description: This file shows the total latency (in micro seconds) of Description: This file shows the total latency (in micro seconds) of read requests sent after monitor gets started. read requests sent after monitor gets started. Loading @@ -1163,7 +1163,7 @@ Description: This file shows the total latency (in micro seconds) of What: /sys/bus/platform/drivers/ufshcd/*/monitor/write_total_sectors What: /sys/bus/platform/drivers/ufshcd/*/monitor/write_total_sectors What: /sys/bus/platform/devices/*.ufs/monitor/write_total_sectors What: /sys/bus/platform/devices/*.ufs/monitor/write_total_sectors Date: January 2021 Date: January 2021 Contact: Can Guo <cang@codeaurora.org> Contact: Can Guo <quic_cang@quicinc.com> Description: This file shows how many sectors (in 512 Bytes) have been sent Description: This file shows how many sectors (in 512 Bytes) have been sent from host to device after monitor gets started. from host to device after monitor gets started. Loading @@ -1172,7 +1172,7 @@ Description: This file shows how many sectors (in 512 Bytes) have been sent What: /sys/bus/platform/drivers/ufshcd/*/monitor/write_total_busy What: /sys/bus/platform/drivers/ufshcd/*/monitor/write_total_busy What: /sys/bus/platform/devices/*.ufs/monitor/write_total_busy What: /sys/bus/platform/devices/*.ufs/monitor/write_total_busy Date: January 2021 Date: January 2021 Contact: Can Guo <cang@codeaurora.org> Contact: Can Guo <quic_cang@quicinc.com> Description: This file shows how long (in micro seconds) has been spent Description: This file shows how long (in micro seconds) has been spent sending data from host to device after monitor gets started. sending data from host to device after monitor gets started. Loading @@ -1181,7 +1181,7 @@ Description: This file shows how long (in micro seconds) has been spent What: /sys/bus/platform/drivers/ufshcd/*/monitor/write_nr_requests What: /sys/bus/platform/drivers/ufshcd/*/monitor/write_nr_requests What: /sys/bus/platform/devices/*.ufs/monitor/write_nr_requests What: /sys/bus/platform/devices/*.ufs/monitor/write_nr_requests Date: January 2021 Date: January 2021 Contact: Can Guo <cang@codeaurora.org> Contact: Can Guo <quic_cang@quicinc.com> Description: This file shows how many write requests have been sent after Description: This file shows how many write requests have been sent after monitor gets started. monitor gets started. Loading @@ -1190,7 +1190,7 @@ Description: This file shows how many write requests have been sent after What: /sys/bus/platform/drivers/ufshcd/*/monitor/write_req_latency_max What: /sys/bus/platform/drivers/ufshcd/*/monitor/write_req_latency_max What: /sys/bus/platform/devices/*.ufs/monitor/write_req_latency_max What: /sys/bus/platform/devices/*.ufs/monitor/write_req_latency_max Date: January 2021 Date: January 2021 Contact: Can Guo <cang@codeaurora.org> Contact: Can Guo <quic_cang@quicinc.com> Description: This file shows the maximum latency (in micro seconds) of write Description: This file shows the maximum latency (in micro seconds) of write requests after monitor gets started. requests after monitor gets started. Loading @@ -1199,7 +1199,7 @@ Description: This file shows the maximum latency (in micro seconds) of write What: /sys/bus/platform/drivers/ufshcd/*/monitor/write_req_latency_min What: /sys/bus/platform/drivers/ufshcd/*/monitor/write_req_latency_min What: /sys/bus/platform/devices/*.ufs/monitor/write_req_latency_min What: /sys/bus/platform/devices/*.ufs/monitor/write_req_latency_min Date: January 2021 Date: January 2021 Contact: Can Guo <cang@codeaurora.org> Contact: Can Guo <quic_cang@quicinc.com> Description: This file shows the minimum latency (in micro seconds) of write Description: This file shows the minimum latency (in micro seconds) of write requests after monitor gets started. requests after monitor gets started. Loading @@ -1208,7 +1208,7 @@ Description: This file shows the minimum latency (in micro seconds) of write What: /sys/bus/platform/drivers/ufshcd/*/monitor/write_req_latency_avg What: /sys/bus/platform/drivers/ufshcd/*/monitor/write_req_latency_avg What: /sys/bus/platform/devices/*.ufs/monitor/write_req_latency_avg What: /sys/bus/platform/devices/*.ufs/monitor/write_req_latency_avg Date: January 2021 Date: January 2021 Contact: Can Guo <cang@codeaurora.org> Contact: Can Guo <quic_cang@quicinc.com> Description: This file shows the average latency (in micro seconds) of write Description: This file shows the average latency (in micro seconds) of write requests after monitor gets started. requests after monitor gets started. Loading @@ -1217,7 +1217,7 @@ Description: This file shows the average latency (in micro seconds) of write What: /sys/bus/platform/drivers/ufshcd/*/monitor/write_req_latency_sum What: /sys/bus/platform/drivers/ufshcd/*/monitor/write_req_latency_sum What: /sys/bus/platform/devices/*.ufs/monitor/write_req_latency_sum What: /sys/bus/platform/devices/*.ufs/monitor/write_req_latency_sum Date: January 2021 Date: January 2021 Contact: Can Guo <cang@codeaurora.org> Contact: Can Guo <quic_cang@quicinc.com> Description: This file shows the total latency (in micro seconds) of write Description: This file shows the total latency (in micro seconds) of write requests after monitor gets started. requests after monitor gets started. Loading @@ -1226,7 +1226,7 @@ Description: This file shows the total latency (in micro seconds) of write What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/wb_presv_us_en What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/wb_presv_us_en What: /sys/bus/platform/devices/*.ufs/device_descriptor/wb_presv_us_en What: /sys/bus/platform/devices/*.ufs/device_descriptor/wb_presv_us_en Date: June 2020 Date: June 2020 Contact: Asutosh Das <asutoshd@codeaurora.org> Contact: Asutosh Das <quic_asutoshd@quicinc.com> Description: This entry shows if preserve user-space was configured Description: This entry shows if preserve user-space was configured The file is read only. The file is read only. Loading @@ -1234,7 +1234,7 @@ Description: This entry shows if preserve user-space was configured What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/wb_shared_alloc_units What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/wb_shared_alloc_units What: /sys/bus/platform/devices/*.ufs/device_descriptor/wb_shared_alloc_units What: /sys/bus/platform/devices/*.ufs/device_descriptor/wb_shared_alloc_units Date: June 2020 Date: June 2020 Contact: Asutosh Das <asutoshd@codeaurora.org> Contact: Asutosh Das <quic_asutoshd@quicinc.com> Description: This entry shows the shared allocated units of WB buffer Description: This entry shows the shared allocated units of WB buffer The file is read only. The file is read only. Loading @@ -1242,7 +1242,7 @@ Description: This entry shows the shared allocated units of WB buffer What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/wb_type What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/wb_type What: /sys/bus/platform/devices/*.ufs/device_descriptor/wb_type What: /sys/bus/platform/devices/*.ufs/device_descriptor/wb_type Date: June 2020 Date: June 2020 Contact: Asutosh Das <asutoshd@codeaurora.org> Contact: Asutosh Das <quic_asutoshd@quicinc.com> Description: This entry shows the configured WB type. Description: This entry shows the configured WB type. 0x1 for shared buffer mode. 0x0 for dedicated buffer mode. 0x1 for shared buffer mode. 0x0 for dedicated buffer mode. Loading @@ -1251,7 +1251,7 @@ Description: This entry shows the configured WB type. What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/wb_buff_cap_adj What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/wb_buff_cap_adj What: /sys/bus/platform/devices/*.ufs/geometry_descriptor/wb_buff_cap_adj What: /sys/bus/platform/devices/*.ufs/geometry_descriptor/wb_buff_cap_adj Date: June 2020 Date: June 2020 Contact: Asutosh Das <asutoshd@codeaurora.org> Contact: Asutosh Das <quic_asutoshd@quicinc.com> Description: This entry shows the total user-space decrease in shared Description: This entry shows the total user-space decrease in shared buffer mode. buffer mode. The value of this parameter is 3 for TLC NAND when SLC mode The value of this parameter is 3 for TLC NAND when SLC mode Loading @@ -1262,7 +1262,7 @@ Description: This entry shows the total user-space decrease in shared What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/wb_max_alloc_units What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/wb_max_alloc_units What: /sys/bus/platform/devices/*.ufs/geometry_descriptor/wb_max_alloc_units What: /sys/bus/platform/devices/*.ufs/geometry_descriptor/wb_max_alloc_units Date: June 2020 Date: June 2020 Contact: Asutosh Das <asutoshd@codeaurora.org> Contact: Asutosh Das <quic_asutoshd@quicinc.com> Description: This entry shows the Maximum total WriteBooster Buffer size Description: This entry shows the Maximum total WriteBooster Buffer size which is supported by the entire device. which is supported by the entire device. Loading @@ -1271,7 +1271,7 @@ Description: This entry shows the Maximum total WriteBooster Buffer size What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/wb_max_wb_luns What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/wb_max_wb_luns What: /sys/bus/platform/devices/*.ufs/geometry_descriptor/wb_max_wb_luns What: /sys/bus/platform/devices/*.ufs/geometry_descriptor/wb_max_wb_luns Date: June 2020 Date: June 2020 Contact: Asutosh Das <asutoshd@codeaurora.org> Contact: Asutosh Das <quic_asutoshd@quicinc.com> Description: This entry shows the maximum number of luns that can support Description: This entry shows the maximum number of luns that can support WriteBooster. WriteBooster. Loading @@ -1280,7 +1280,7 @@ Description: This entry shows the maximum number of luns that can support What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/wb_sup_red_type What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/wb_sup_red_type What: /sys/bus/platform/devices/*.ufs/geometry_descriptor/wb_sup_red_type What: /sys/bus/platform/devices/*.ufs/geometry_descriptor/wb_sup_red_type Date: June 2020 Date: June 2020 Contact: Asutosh Das <asutoshd@codeaurora.org> Contact: Asutosh Das <quic_asutoshd@quicinc.com> Description: The supportability of user space reduction mode Description: The supportability of user space reduction mode and preserve user space mode. and preserve user space mode. 00h: WriteBooster Buffer can be configured only in 00h: WriteBooster Buffer can be configured only in Loading @@ -1295,7 +1295,7 @@ Description: The supportability of user space reduction mode What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/wb_sup_wb_type What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/wb_sup_wb_type What: /sys/bus/platform/devices/*.ufs/geometry_descriptor/wb_sup_wb_type What: /sys/bus/platform/devices/*.ufs/geometry_descriptor/wb_sup_wb_type Date: June 2020 Date: June 2020 Contact: Asutosh Das <asutoshd@codeaurora.org> Contact: Asutosh Das <quic_asutoshd@quicinc.com> Description: The supportability of WriteBooster Buffer type. Description: The supportability of WriteBooster Buffer type. === ========================================================== === ========================================================== Loading @@ -1310,7 +1310,7 @@ Description: The supportability of WriteBooster Buffer type. What: /sys/bus/platform/drivers/ufshcd/*/flags/wb_enable What: /sys/bus/platform/drivers/ufshcd/*/flags/wb_enable What: /sys/bus/platform/devices/*.ufs/flags/wb_enable What: /sys/bus/platform/devices/*.ufs/flags/wb_enable Date: June 2020 Date: June 2020 Contact: Asutosh Das <asutoshd@codeaurora.org> Contact: Asutosh Das <quic_asutoshd@quicinc.com> Description: This entry shows the status of WriteBooster. Description: This entry shows the status of WriteBooster. == ============================ == ============================ Loading @@ -1323,7 +1323,7 @@ Description: This entry shows the status of WriteBooster. What: /sys/bus/platform/drivers/ufshcd/*/flags/wb_flush_en What: /sys/bus/platform/drivers/ufshcd/*/flags/wb_flush_en What: /sys/bus/platform/devices/*.ufs/flags/wb_flush_en What: /sys/bus/platform/devices/*.ufs/flags/wb_flush_en Date: June 2020 Date: June 2020 Contact: Asutosh Das <asutoshd@codeaurora.org> Contact: Asutosh Das <quic_asutoshd@quicinc.com> Description: This entry shows if flush is enabled. Description: This entry shows if flush is enabled. == ================================= == ================================= Loading @@ -1336,7 +1336,7 @@ Description: This entry shows if flush is enabled. What: /sys/bus/platform/drivers/ufshcd/*/flags/wb_flush_during_h8 What: /sys/bus/platform/drivers/ufshcd/*/flags/wb_flush_during_h8 What: /sys/bus/platform/devices/*.ufs/flags/wb_flush_during_h8 What: /sys/bus/platform/devices/*.ufs/flags/wb_flush_during_h8 Date: June 2020 Date: June 2020 Contact: Asutosh Das <asutoshd@codeaurora.org> Contact: Asutosh Das <quic_asutoshd@quicinc.com> Description: Flush WriteBooster Buffer during hibernate state. Description: Flush WriteBooster Buffer during hibernate state. == ================================================= == ================================================= Loading @@ -1351,7 +1351,7 @@ Description: Flush WriteBooster Buffer during hibernate state. What: /sys/bus/platform/drivers/ufshcd/*/attributes/wb_avail_buf What: /sys/bus/platform/drivers/ufshcd/*/attributes/wb_avail_buf What: /sys/bus/platform/devices/*.ufs/attributes/wb_avail_buf What: /sys/bus/platform/devices/*.ufs/attributes/wb_avail_buf Date: June 2020 Date: June 2020 Contact: Asutosh Das <asutoshd@codeaurora.org> Contact: Asutosh Das <quic_asutoshd@quicinc.com> Description: This entry shows the amount of unused WriteBooster buffer Description: This entry shows the amount of unused WriteBooster buffer available. available. Loading @@ -1360,7 +1360,7 @@ Description: This entry shows the amount of unused WriteBooster buffer What: /sys/bus/platform/drivers/ufshcd/*/attributes/wb_cur_buf What: /sys/bus/platform/drivers/ufshcd/*/attributes/wb_cur_buf What: /sys/bus/platform/devices/*.ufs/attributes/wb_cur_buf What: /sys/bus/platform/devices/*.ufs/attributes/wb_cur_buf Date: June 2020 Date: June 2020 Contact: Asutosh Das <asutoshd@codeaurora.org> Contact: Asutosh Das <quic_asutoshd@quicinc.com> Description: This entry shows the amount of unused current buffer. Description: This entry shows the amount of unused current buffer. The file is read only. The file is read only. Loading @@ -1368,7 +1368,7 @@ Description: This entry shows the amount of unused current buffer. What: /sys/bus/platform/drivers/ufshcd/*/attributes/wb_flush_status What: /sys/bus/platform/drivers/ufshcd/*/attributes/wb_flush_status What: /sys/bus/platform/devices/*.ufs/attributes/wb_flush_status What: /sys/bus/platform/devices/*.ufs/attributes/wb_flush_status Date: June 2020 Date: June 2020 Contact: Asutosh Das <asutoshd@codeaurora.org> Contact: Asutosh Das <quic_asutoshd@quicinc.com> Description: This entry shows the flush operation status. Description: This entry shows the flush operation status. Loading @@ -1385,7 +1385,7 @@ Description: This entry shows the flush operation status. What: /sys/bus/platform/drivers/ufshcd/*/attributes/wb_life_time_est What: /sys/bus/platform/drivers/ufshcd/*/attributes/wb_life_time_est What: /sys/bus/platform/devices/*.ufs/attributes/wb_life_time_est What: /sys/bus/platform/devices/*.ufs/attributes/wb_life_time_est Date: June 2020 Date: June 2020 Contact: Asutosh Das <asutoshd@codeaurora.org> Contact: Asutosh Das <quic_asutoshd@quicinc.com> Description: This entry shows an indication of the WriteBooster Buffer Description: This entry shows an indication of the WriteBooster Buffer lifetime based on the amount of performed program/erase cycles lifetime based on the amount of performed program/erase cycles Loading @@ -1399,7 +1399,7 @@ Description: This entry shows an indication of the WriteBooster Buffer What: /sys/class/scsi_device/*/device/unit_descriptor/wb_buf_alloc_units What: /sys/class/scsi_device/*/device/unit_descriptor/wb_buf_alloc_units Date: June 2020 Date: June 2020 Contact: Asutosh Das <asutoshd@codeaurora.org> Contact: Asutosh Das <quic_asutoshd@quicinc.com> Description: This entry shows the configured size of WriteBooster buffer. Description: This entry shows the configured size of WriteBooster buffer. 0400h corresponds to 4GB. 0400h corresponds to 4GB. Loading Documentation/devicetree/bindings/watchdog/loongson,ls1x-wdt.yaml 0 → 100644 +42 −0 Original line number Original line Diff line number Diff line # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) %YAML 1.2 --- $id: http://devicetree.org/schemas/watchdog/loongson,ls1x-wdt.yaml# $schema: http://devicetree.org/meta-schemas/core.yaml# title: Loongson-1 Watchdog Timer maintainers: - Keguang Zhang <keguang.zhang@gmail.com> allOf: - $ref: watchdog.yaml# properties: compatible: enum: - loongson,ls1b-wdt - loongson,ls1c-wdt reg: maxItems: 1 clocks: maxItems: 1 required: - compatible - reg - clocks unevaluatedProperties: false examples: - | #include <dt-bindings/clock/loongson,ls1x-clk.h> watchdog: watchdog@1fe5c060 { compatible = "loongson,ls1b-wdt"; reg = <0x1fe5c060 0xc>; clocks = <&clkc LS1X_CLKID_APB>; }; Documentation/process/maintainer-netdev.rst +1 −1 Original line number Original line Diff line number Diff line Loading @@ -98,7 +98,7 @@ If you aren't subscribed to netdev and/or are simply unsure if repository link above for any new networking-related commits. You may repository link above for any new networking-related commits. You may also check the following website for the current status: also check the following website for the current status: http://vger.kernel.org/~davem/net-next.html https://patchwork.hopto.org/net-next.html The ``net`` tree continues to collect fixes for the vX.Y content, and is The ``net`` tree continues to collect fixes for the vX.Y content, and is fed back to Linus at regular (~weekly) intervals. Meaning that the fed back to Linus at regular (~weekly) intervals. Meaning that the Loading Documentation/riscv/hwprobe.rst +1 −1 Original line number Original line Diff line number Diff line Loading @@ -49,7 +49,7 @@ The following keys are defined: privileged ISA, with the following known exceptions (more exceptions may be privileged ISA, with the following known exceptions (more exceptions may be added, but only if it can be demonstrated that the user ABI is not broken): added, but only if it can be demonstrated that the user ABI is not broken): * The :fence.i: instruction cannot be directly executed by userspace * The ``fence.i`` instruction cannot be directly executed by userspace programs (it may still be executed in userspace via a programs (it may still be executed in userspace via a kernel-controlled mechanism such as the vDSO). kernel-controlled mechanism such as the vDSO). Loading Loading
.mailmap +1 −0 Original line number Original line Diff line number Diff line Loading @@ -246,6 +246,7 @@ John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> John Stultz <johnstul@us.ibm.com> John Stultz <johnstul@us.ibm.com> <jon.toppins+linux@gmail.com> <jtoppins@cumulusnetworks.com> <jon.toppins+linux@gmail.com> <jtoppins@cumulusnetworks.com> <jon.toppins+linux@gmail.com> <jtoppins@redhat.com> <jon.toppins+linux@gmail.com> <jtoppins@redhat.com> Jonas Gorski <jonas.gorski@gmail.com> <jogo@openwrt.org> Jordan Crouse <jordan@cosmicpenguin.net> <jcrouse@codeaurora.org> Jordan Crouse <jordan@cosmicpenguin.net> <jcrouse@codeaurora.org> <josh@joshtriplett.org> <josh@freedesktop.org> <josh@joshtriplett.org> <josh@freedesktop.org> <josh@joshtriplett.org> <josh@kernel.org> <josh@joshtriplett.org> <josh@kernel.org> Loading
Documentation/ABI/testing/sysfs-driver-ufs +38 −38 Original line number Original line Diff line number Diff line Loading @@ -994,7 +994,7 @@ Description: This file shows the amount of physical memory needed What: /sys/bus/platform/drivers/ufshcd/*/rpm_lvl What: /sys/bus/platform/drivers/ufshcd/*/rpm_lvl What: /sys/bus/platform/devices/*.ufs/rpm_lvl What: /sys/bus/platform/devices/*.ufs/rpm_lvl Date: September 2014 Date: September 2014 Contact: Subhash Jadavani <subhashj@codeaurora.org> Contact: Can Guo <quic_cang@quicinc.com> Description: This entry could be used to set or show the UFS device Description: This entry could be used to set or show the UFS device runtime power management level. The current driver runtime power management level. The current driver implementation supports 7 levels with next target states: implementation supports 7 levels with next target states: Loading @@ -1021,7 +1021,7 @@ Description: This entry could be used to set or show the UFS device What: /sys/bus/platform/drivers/ufshcd/*/rpm_target_dev_state What: /sys/bus/platform/drivers/ufshcd/*/rpm_target_dev_state What: /sys/bus/platform/devices/*.ufs/rpm_target_dev_state What: /sys/bus/platform/devices/*.ufs/rpm_target_dev_state Date: February 2018 Date: February 2018 Contact: Subhash Jadavani <subhashj@codeaurora.org> Contact: Can Guo <quic_cang@quicinc.com> Description: This entry shows the target power mode of an UFS device Description: This entry shows the target power mode of an UFS device for the chosen runtime power management level. for the chosen runtime power management level. Loading @@ -1030,7 +1030,7 @@ Description: This entry shows the target power mode of an UFS device What: /sys/bus/platform/drivers/ufshcd/*/rpm_target_link_state What: /sys/bus/platform/drivers/ufshcd/*/rpm_target_link_state What: /sys/bus/platform/devices/*.ufs/rpm_target_link_state What: /sys/bus/platform/devices/*.ufs/rpm_target_link_state Date: February 2018 Date: February 2018 Contact: Subhash Jadavani <subhashj@codeaurora.org> Contact: Can Guo <quic_cang@quicinc.com> Description: This entry shows the target state of an UFS UIC link Description: This entry shows the target state of an UFS UIC link for the chosen runtime power management level. for the chosen runtime power management level. Loading @@ -1039,7 +1039,7 @@ Description: This entry shows the target state of an UFS UIC link What: /sys/bus/platform/drivers/ufshcd/*/spm_lvl What: /sys/bus/platform/drivers/ufshcd/*/spm_lvl What: /sys/bus/platform/devices/*.ufs/spm_lvl What: /sys/bus/platform/devices/*.ufs/spm_lvl Date: September 2014 Date: September 2014 Contact: Subhash Jadavani <subhashj@codeaurora.org> Contact: Can Guo <quic_cang@quicinc.com> Description: This entry could be used to set or show the UFS device Description: This entry could be used to set or show the UFS device system power management level. The current driver system power management level. The current driver implementation supports 7 levels with next target states: implementation supports 7 levels with next target states: Loading @@ -1066,7 +1066,7 @@ Description: This entry could be used to set or show the UFS device What: /sys/bus/platform/drivers/ufshcd/*/spm_target_dev_state What: /sys/bus/platform/drivers/ufshcd/*/spm_target_dev_state What: /sys/bus/platform/devices/*.ufs/spm_target_dev_state What: /sys/bus/platform/devices/*.ufs/spm_target_dev_state Date: February 2018 Date: February 2018 Contact: Subhash Jadavani <subhashj@codeaurora.org> Contact: Can Guo <quic_cang@quicinc.com> Description: This entry shows the target power mode of an UFS device Description: This entry shows the target power mode of an UFS device for the chosen system power management level. for the chosen system power management level. Loading @@ -1075,7 +1075,7 @@ Description: This entry shows the target power mode of an UFS device What: /sys/bus/platform/drivers/ufshcd/*/spm_target_link_state What: /sys/bus/platform/drivers/ufshcd/*/spm_target_link_state What: /sys/bus/platform/devices/*.ufs/spm_target_link_state What: /sys/bus/platform/devices/*.ufs/spm_target_link_state Date: February 2018 Date: February 2018 Contact: Subhash Jadavani <subhashj@codeaurora.org> Contact: Can Guo <quic_cang@quicinc.com> Description: This entry shows the target state of an UFS UIC link Description: This entry shows the target state of an UFS UIC link for the chosen system power management level. for the chosen system power management level. Loading @@ -1084,7 +1084,7 @@ Description: This entry shows the target state of an UFS UIC link What: /sys/bus/platform/drivers/ufshcd/*/monitor/monitor_enable What: /sys/bus/platform/drivers/ufshcd/*/monitor/monitor_enable What: /sys/bus/platform/devices/*.ufs/monitor/monitor_enable What: /sys/bus/platform/devices/*.ufs/monitor/monitor_enable Date: January 2021 Date: January 2021 Contact: Can Guo <cang@codeaurora.org> Contact: Can Guo <quic_cang@quicinc.com> Description: This file shows the status of performance monitor enablement Description: This file shows the status of performance monitor enablement and it can be used to start/stop the monitor. When the monitor and it can be used to start/stop the monitor. When the monitor is stopped, the performance data collected is also cleared. is stopped, the performance data collected is also cleared. Loading @@ -1092,7 +1092,7 @@ Description: This file shows the status of performance monitor enablement What: /sys/bus/platform/drivers/ufshcd/*/monitor/monitor_chunk_size What: /sys/bus/platform/drivers/ufshcd/*/monitor/monitor_chunk_size What: /sys/bus/platform/devices/*.ufs/monitor/monitor_chunk_size What: /sys/bus/platform/devices/*.ufs/monitor/monitor_chunk_size Date: January 2021 Date: January 2021 Contact: Can Guo <cang@codeaurora.org> Contact: Can Guo <quic_cang@quicinc.com> Description: This file tells the monitor to focus on requests transferring Description: This file tells the monitor to focus on requests transferring data of specific chunk size (in Bytes). 0 means any chunk size. data of specific chunk size (in Bytes). 0 means any chunk size. It can only be changed when monitor is disabled. It can only be changed when monitor is disabled. Loading @@ -1100,7 +1100,7 @@ Description: This file tells the monitor to focus on requests transferring What: /sys/bus/platform/drivers/ufshcd/*/monitor/read_total_sectors What: /sys/bus/platform/drivers/ufshcd/*/monitor/read_total_sectors What: /sys/bus/platform/devices/*.ufs/monitor/read_total_sectors What: /sys/bus/platform/devices/*.ufs/monitor/read_total_sectors Date: January 2021 Date: January 2021 Contact: Can Guo <cang@codeaurora.org> Contact: Can Guo <quic_cang@quicinc.com> Description: This file shows how many sectors (in 512 Bytes) have been Description: This file shows how many sectors (in 512 Bytes) have been sent from device to host after monitor gets started. sent from device to host after monitor gets started. Loading @@ -1109,7 +1109,7 @@ Description: This file shows how many sectors (in 512 Bytes) have been What: /sys/bus/platform/drivers/ufshcd/*/monitor/read_total_busy What: /sys/bus/platform/drivers/ufshcd/*/monitor/read_total_busy What: /sys/bus/platform/devices/*.ufs/monitor/read_total_busy What: /sys/bus/platform/devices/*.ufs/monitor/read_total_busy Date: January 2021 Date: January 2021 Contact: Can Guo <cang@codeaurora.org> Contact: Can Guo <quic_cang@quicinc.com> Description: This file shows how long (in micro seconds) has been spent Description: This file shows how long (in micro seconds) has been spent sending data from device to host after monitor gets started. sending data from device to host after monitor gets started. Loading @@ -1118,7 +1118,7 @@ Description: This file shows how long (in micro seconds) has been spent What: /sys/bus/platform/drivers/ufshcd/*/monitor/read_nr_requests What: /sys/bus/platform/drivers/ufshcd/*/monitor/read_nr_requests What: /sys/bus/platform/devices/*.ufs/monitor/read_nr_requests What: /sys/bus/platform/devices/*.ufs/monitor/read_nr_requests Date: January 2021 Date: January 2021 Contact: Can Guo <cang@codeaurora.org> Contact: Can Guo <quic_cang@quicinc.com> Description: This file shows how many read requests have been sent after Description: This file shows how many read requests have been sent after monitor gets started. monitor gets started. Loading @@ -1127,7 +1127,7 @@ Description: This file shows how many read requests have been sent after What: /sys/bus/platform/drivers/ufshcd/*/monitor/read_req_latency_max What: /sys/bus/platform/drivers/ufshcd/*/monitor/read_req_latency_max What: /sys/bus/platform/devices/*.ufs/monitor/read_req_latency_max What: /sys/bus/platform/devices/*.ufs/monitor/read_req_latency_max Date: January 2021 Date: January 2021 Contact: Can Guo <cang@codeaurora.org> Contact: Can Guo <quic_cang@quicinc.com> Description: This file shows the maximum latency (in micro seconds) of Description: This file shows the maximum latency (in micro seconds) of read requests after monitor gets started. read requests after monitor gets started. Loading @@ -1136,7 +1136,7 @@ Description: This file shows the maximum latency (in micro seconds) of What: /sys/bus/platform/drivers/ufshcd/*/monitor/read_req_latency_min What: /sys/bus/platform/drivers/ufshcd/*/monitor/read_req_latency_min What: /sys/bus/platform/devices/*.ufs/monitor/read_req_latency_min What: /sys/bus/platform/devices/*.ufs/monitor/read_req_latency_min Date: January 2021 Date: January 2021 Contact: Can Guo <cang@codeaurora.org> Contact: Can Guo <quic_cang@quicinc.com> Description: This file shows the minimum latency (in micro seconds) of Description: This file shows the minimum latency (in micro seconds) of read requests after monitor gets started. read requests after monitor gets started. Loading @@ -1145,7 +1145,7 @@ Description: This file shows the minimum latency (in micro seconds) of What: /sys/bus/platform/drivers/ufshcd/*/monitor/read_req_latency_avg What: /sys/bus/platform/drivers/ufshcd/*/monitor/read_req_latency_avg What: /sys/bus/platform/devices/*.ufs/monitor/read_req_latency_avg What: /sys/bus/platform/devices/*.ufs/monitor/read_req_latency_avg Date: January 2021 Date: January 2021 Contact: Can Guo <cang@codeaurora.org> Contact: Can Guo <quic_cang@quicinc.com> Description: This file shows the average latency (in micro seconds) of Description: This file shows the average latency (in micro seconds) of read requests after monitor gets started. read requests after monitor gets started. Loading @@ -1154,7 +1154,7 @@ Description: This file shows the average latency (in micro seconds) of What: /sys/bus/platform/drivers/ufshcd/*/monitor/read_req_latency_sum What: /sys/bus/platform/drivers/ufshcd/*/monitor/read_req_latency_sum What: /sys/bus/platform/devices/*.ufs/monitor/read_req_latency_sum What: /sys/bus/platform/devices/*.ufs/monitor/read_req_latency_sum Date: January 2021 Date: January 2021 Contact: Can Guo <cang@codeaurora.org> Contact: Can Guo <quic_cang@quicinc.com> Description: This file shows the total latency (in micro seconds) of Description: This file shows the total latency (in micro seconds) of read requests sent after monitor gets started. read requests sent after monitor gets started. Loading @@ -1163,7 +1163,7 @@ Description: This file shows the total latency (in micro seconds) of What: /sys/bus/platform/drivers/ufshcd/*/monitor/write_total_sectors What: /sys/bus/platform/drivers/ufshcd/*/monitor/write_total_sectors What: /sys/bus/platform/devices/*.ufs/monitor/write_total_sectors What: /sys/bus/platform/devices/*.ufs/monitor/write_total_sectors Date: January 2021 Date: January 2021 Contact: Can Guo <cang@codeaurora.org> Contact: Can Guo <quic_cang@quicinc.com> Description: This file shows how many sectors (in 512 Bytes) have been sent Description: This file shows how many sectors (in 512 Bytes) have been sent from host to device after monitor gets started. from host to device after monitor gets started. Loading @@ -1172,7 +1172,7 @@ Description: This file shows how many sectors (in 512 Bytes) have been sent What: /sys/bus/platform/drivers/ufshcd/*/monitor/write_total_busy What: /sys/bus/platform/drivers/ufshcd/*/monitor/write_total_busy What: /sys/bus/platform/devices/*.ufs/monitor/write_total_busy What: /sys/bus/platform/devices/*.ufs/monitor/write_total_busy Date: January 2021 Date: January 2021 Contact: Can Guo <cang@codeaurora.org> Contact: Can Guo <quic_cang@quicinc.com> Description: This file shows how long (in micro seconds) has been spent Description: This file shows how long (in micro seconds) has been spent sending data from host to device after monitor gets started. sending data from host to device after monitor gets started. Loading @@ -1181,7 +1181,7 @@ Description: This file shows how long (in micro seconds) has been spent What: /sys/bus/platform/drivers/ufshcd/*/monitor/write_nr_requests What: /sys/bus/platform/drivers/ufshcd/*/monitor/write_nr_requests What: /sys/bus/platform/devices/*.ufs/monitor/write_nr_requests What: /sys/bus/platform/devices/*.ufs/monitor/write_nr_requests Date: January 2021 Date: January 2021 Contact: Can Guo <cang@codeaurora.org> Contact: Can Guo <quic_cang@quicinc.com> Description: This file shows how many write requests have been sent after Description: This file shows how many write requests have been sent after monitor gets started. monitor gets started. Loading @@ -1190,7 +1190,7 @@ Description: This file shows how many write requests have been sent after What: /sys/bus/platform/drivers/ufshcd/*/monitor/write_req_latency_max What: /sys/bus/platform/drivers/ufshcd/*/monitor/write_req_latency_max What: /sys/bus/platform/devices/*.ufs/monitor/write_req_latency_max What: /sys/bus/platform/devices/*.ufs/monitor/write_req_latency_max Date: January 2021 Date: January 2021 Contact: Can Guo <cang@codeaurora.org> Contact: Can Guo <quic_cang@quicinc.com> Description: This file shows the maximum latency (in micro seconds) of write Description: This file shows the maximum latency (in micro seconds) of write requests after monitor gets started. requests after monitor gets started. Loading @@ -1199,7 +1199,7 @@ Description: This file shows the maximum latency (in micro seconds) of write What: /sys/bus/platform/drivers/ufshcd/*/monitor/write_req_latency_min What: /sys/bus/platform/drivers/ufshcd/*/monitor/write_req_latency_min What: /sys/bus/platform/devices/*.ufs/monitor/write_req_latency_min What: /sys/bus/platform/devices/*.ufs/monitor/write_req_latency_min Date: January 2021 Date: January 2021 Contact: Can Guo <cang@codeaurora.org> Contact: Can Guo <quic_cang@quicinc.com> Description: This file shows the minimum latency (in micro seconds) of write Description: This file shows the minimum latency (in micro seconds) of write requests after monitor gets started. requests after monitor gets started. Loading @@ -1208,7 +1208,7 @@ Description: This file shows the minimum latency (in micro seconds) of write What: /sys/bus/platform/drivers/ufshcd/*/monitor/write_req_latency_avg What: /sys/bus/platform/drivers/ufshcd/*/monitor/write_req_latency_avg What: /sys/bus/platform/devices/*.ufs/monitor/write_req_latency_avg What: /sys/bus/platform/devices/*.ufs/monitor/write_req_latency_avg Date: January 2021 Date: January 2021 Contact: Can Guo <cang@codeaurora.org> Contact: Can Guo <quic_cang@quicinc.com> Description: This file shows the average latency (in micro seconds) of write Description: This file shows the average latency (in micro seconds) of write requests after monitor gets started. requests after monitor gets started. Loading @@ -1217,7 +1217,7 @@ Description: This file shows the average latency (in micro seconds) of write What: /sys/bus/platform/drivers/ufshcd/*/monitor/write_req_latency_sum What: /sys/bus/platform/drivers/ufshcd/*/monitor/write_req_latency_sum What: /sys/bus/platform/devices/*.ufs/monitor/write_req_latency_sum What: /sys/bus/platform/devices/*.ufs/monitor/write_req_latency_sum Date: January 2021 Date: January 2021 Contact: Can Guo <cang@codeaurora.org> Contact: Can Guo <quic_cang@quicinc.com> Description: This file shows the total latency (in micro seconds) of write Description: This file shows the total latency (in micro seconds) of write requests after monitor gets started. requests after monitor gets started. Loading @@ -1226,7 +1226,7 @@ Description: This file shows the total latency (in micro seconds) of write What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/wb_presv_us_en What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/wb_presv_us_en What: /sys/bus/platform/devices/*.ufs/device_descriptor/wb_presv_us_en What: /sys/bus/platform/devices/*.ufs/device_descriptor/wb_presv_us_en Date: June 2020 Date: June 2020 Contact: Asutosh Das <asutoshd@codeaurora.org> Contact: Asutosh Das <quic_asutoshd@quicinc.com> Description: This entry shows if preserve user-space was configured Description: This entry shows if preserve user-space was configured The file is read only. The file is read only. Loading @@ -1234,7 +1234,7 @@ Description: This entry shows if preserve user-space was configured What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/wb_shared_alloc_units What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/wb_shared_alloc_units What: /sys/bus/platform/devices/*.ufs/device_descriptor/wb_shared_alloc_units What: /sys/bus/platform/devices/*.ufs/device_descriptor/wb_shared_alloc_units Date: June 2020 Date: June 2020 Contact: Asutosh Das <asutoshd@codeaurora.org> Contact: Asutosh Das <quic_asutoshd@quicinc.com> Description: This entry shows the shared allocated units of WB buffer Description: This entry shows the shared allocated units of WB buffer The file is read only. The file is read only. Loading @@ -1242,7 +1242,7 @@ Description: This entry shows the shared allocated units of WB buffer What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/wb_type What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/wb_type What: /sys/bus/platform/devices/*.ufs/device_descriptor/wb_type What: /sys/bus/platform/devices/*.ufs/device_descriptor/wb_type Date: June 2020 Date: June 2020 Contact: Asutosh Das <asutoshd@codeaurora.org> Contact: Asutosh Das <quic_asutoshd@quicinc.com> Description: This entry shows the configured WB type. Description: This entry shows the configured WB type. 0x1 for shared buffer mode. 0x0 for dedicated buffer mode. 0x1 for shared buffer mode. 0x0 for dedicated buffer mode. Loading @@ -1251,7 +1251,7 @@ Description: This entry shows the configured WB type. What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/wb_buff_cap_adj What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/wb_buff_cap_adj What: /sys/bus/platform/devices/*.ufs/geometry_descriptor/wb_buff_cap_adj What: /sys/bus/platform/devices/*.ufs/geometry_descriptor/wb_buff_cap_adj Date: June 2020 Date: June 2020 Contact: Asutosh Das <asutoshd@codeaurora.org> Contact: Asutosh Das <quic_asutoshd@quicinc.com> Description: This entry shows the total user-space decrease in shared Description: This entry shows the total user-space decrease in shared buffer mode. buffer mode. The value of this parameter is 3 for TLC NAND when SLC mode The value of this parameter is 3 for TLC NAND when SLC mode Loading @@ -1262,7 +1262,7 @@ Description: This entry shows the total user-space decrease in shared What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/wb_max_alloc_units What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/wb_max_alloc_units What: /sys/bus/platform/devices/*.ufs/geometry_descriptor/wb_max_alloc_units What: /sys/bus/platform/devices/*.ufs/geometry_descriptor/wb_max_alloc_units Date: June 2020 Date: June 2020 Contact: Asutosh Das <asutoshd@codeaurora.org> Contact: Asutosh Das <quic_asutoshd@quicinc.com> Description: This entry shows the Maximum total WriteBooster Buffer size Description: This entry shows the Maximum total WriteBooster Buffer size which is supported by the entire device. which is supported by the entire device. Loading @@ -1271,7 +1271,7 @@ Description: This entry shows the Maximum total WriteBooster Buffer size What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/wb_max_wb_luns What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/wb_max_wb_luns What: /sys/bus/platform/devices/*.ufs/geometry_descriptor/wb_max_wb_luns What: /sys/bus/platform/devices/*.ufs/geometry_descriptor/wb_max_wb_luns Date: June 2020 Date: June 2020 Contact: Asutosh Das <asutoshd@codeaurora.org> Contact: Asutosh Das <quic_asutoshd@quicinc.com> Description: This entry shows the maximum number of luns that can support Description: This entry shows the maximum number of luns that can support WriteBooster. WriteBooster. Loading @@ -1280,7 +1280,7 @@ Description: This entry shows the maximum number of luns that can support What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/wb_sup_red_type What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/wb_sup_red_type What: /sys/bus/platform/devices/*.ufs/geometry_descriptor/wb_sup_red_type What: /sys/bus/platform/devices/*.ufs/geometry_descriptor/wb_sup_red_type Date: June 2020 Date: June 2020 Contact: Asutosh Das <asutoshd@codeaurora.org> Contact: Asutosh Das <quic_asutoshd@quicinc.com> Description: The supportability of user space reduction mode Description: The supportability of user space reduction mode and preserve user space mode. and preserve user space mode. 00h: WriteBooster Buffer can be configured only in 00h: WriteBooster Buffer can be configured only in Loading @@ -1295,7 +1295,7 @@ Description: The supportability of user space reduction mode What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/wb_sup_wb_type What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/wb_sup_wb_type What: /sys/bus/platform/devices/*.ufs/geometry_descriptor/wb_sup_wb_type What: /sys/bus/platform/devices/*.ufs/geometry_descriptor/wb_sup_wb_type Date: June 2020 Date: June 2020 Contact: Asutosh Das <asutoshd@codeaurora.org> Contact: Asutosh Das <quic_asutoshd@quicinc.com> Description: The supportability of WriteBooster Buffer type. Description: The supportability of WriteBooster Buffer type. === ========================================================== === ========================================================== Loading @@ -1310,7 +1310,7 @@ Description: The supportability of WriteBooster Buffer type. What: /sys/bus/platform/drivers/ufshcd/*/flags/wb_enable What: /sys/bus/platform/drivers/ufshcd/*/flags/wb_enable What: /sys/bus/platform/devices/*.ufs/flags/wb_enable What: /sys/bus/platform/devices/*.ufs/flags/wb_enable Date: June 2020 Date: June 2020 Contact: Asutosh Das <asutoshd@codeaurora.org> Contact: Asutosh Das <quic_asutoshd@quicinc.com> Description: This entry shows the status of WriteBooster. Description: This entry shows the status of WriteBooster. == ============================ == ============================ Loading @@ -1323,7 +1323,7 @@ Description: This entry shows the status of WriteBooster. What: /sys/bus/platform/drivers/ufshcd/*/flags/wb_flush_en What: /sys/bus/platform/drivers/ufshcd/*/flags/wb_flush_en What: /sys/bus/platform/devices/*.ufs/flags/wb_flush_en What: /sys/bus/platform/devices/*.ufs/flags/wb_flush_en Date: June 2020 Date: June 2020 Contact: Asutosh Das <asutoshd@codeaurora.org> Contact: Asutosh Das <quic_asutoshd@quicinc.com> Description: This entry shows if flush is enabled. Description: This entry shows if flush is enabled. == ================================= == ================================= Loading @@ -1336,7 +1336,7 @@ Description: This entry shows if flush is enabled. What: /sys/bus/platform/drivers/ufshcd/*/flags/wb_flush_during_h8 What: /sys/bus/platform/drivers/ufshcd/*/flags/wb_flush_during_h8 What: /sys/bus/platform/devices/*.ufs/flags/wb_flush_during_h8 What: /sys/bus/platform/devices/*.ufs/flags/wb_flush_during_h8 Date: June 2020 Date: June 2020 Contact: Asutosh Das <asutoshd@codeaurora.org> Contact: Asutosh Das <quic_asutoshd@quicinc.com> Description: Flush WriteBooster Buffer during hibernate state. Description: Flush WriteBooster Buffer during hibernate state. == ================================================= == ================================================= Loading @@ -1351,7 +1351,7 @@ Description: Flush WriteBooster Buffer during hibernate state. What: /sys/bus/platform/drivers/ufshcd/*/attributes/wb_avail_buf What: /sys/bus/platform/drivers/ufshcd/*/attributes/wb_avail_buf What: /sys/bus/platform/devices/*.ufs/attributes/wb_avail_buf What: /sys/bus/platform/devices/*.ufs/attributes/wb_avail_buf Date: June 2020 Date: June 2020 Contact: Asutosh Das <asutoshd@codeaurora.org> Contact: Asutosh Das <quic_asutoshd@quicinc.com> Description: This entry shows the amount of unused WriteBooster buffer Description: This entry shows the amount of unused WriteBooster buffer available. available. Loading @@ -1360,7 +1360,7 @@ Description: This entry shows the amount of unused WriteBooster buffer What: /sys/bus/platform/drivers/ufshcd/*/attributes/wb_cur_buf What: /sys/bus/platform/drivers/ufshcd/*/attributes/wb_cur_buf What: /sys/bus/platform/devices/*.ufs/attributes/wb_cur_buf What: /sys/bus/platform/devices/*.ufs/attributes/wb_cur_buf Date: June 2020 Date: June 2020 Contact: Asutosh Das <asutoshd@codeaurora.org> Contact: Asutosh Das <quic_asutoshd@quicinc.com> Description: This entry shows the amount of unused current buffer. Description: This entry shows the amount of unused current buffer. The file is read only. The file is read only. Loading @@ -1368,7 +1368,7 @@ Description: This entry shows the amount of unused current buffer. What: /sys/bus/platform/drivers/ufshcd/*/attributes/wb_flush_status What: /sys/bus/platform/drivers/ufshcd/*/attributes/wb_flush_status What: /sys/bus/platform/devices/*.ufs/attributes/wb_flush_status What: /sys/bus/platform/devices/*.ufs/attributes/wb_flush_status Date: June 2020 Date: June 2020 Contact: Asutosh Das <asutoshd@codeaurora.org> Contact: Asutosh Das <quic_asutoshd@quicinc.com> Description: This entry shows the flush operation status. Description: This entry shows the flush operation status. Loading @@ -1385,7 +1385,7 @@ Description: This entry shows the flush operation status. What: /sys/bus/platform/drivers/ufshcd/*/attributes/wb_life_time_est What: /sys/bus/platform/drivers/ufshcd/*/attributes/wb_life_time_est What: /sys/bus/platform/devices/*.ufs/attributes/wb_life_time_est What: /sys/bus/platform/devices/*.ufs/attributes/wb_life_time_est Date: June 2020 Date: June 2020 Contact: Asutosh Das <asutoshd@codeaurora.org> Contact: Asutosh Das <quic_asutoshd@quicinc.com> Description: This entry shows an indication of the WriteBooster Buffer Description: This entry shows an indication of the WriteBooster Buffer lifetime based on the amount of performed program/erase cycles lifetime based on the amount of performed program/erase cycles Loading @@ -1399,7 +1399,7 @@ Description: This entry shows an indication of the WriteBooster Buffer What: /sys/class/scsi_device/*/device/unit_descriptor/wb_buf_alloc_units What: /sys/class/scsi_device/*/device/unit_descriptor/wb_buf_alloc_units Date: June 2020 Date: June 2020 Contact: Asutosh Das <asutoshd@codeaurora.org> Contact: Asutosh Das <quic_asutoshd@quicinc.com> Description: This entry shows the configured size of WriteBooster buffer. Description: This entry shows the configured size of WriteBooster buffer. 0400h corresponds to 4GB. 0400h corresponds to 4GB. Loading
Documentation/devicetree/bindings/watchdog/loongson,ls1x-wdt.yaml 0 → 100644 +42 −0 Original line number Original line Diff line number Diff line # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) %YAML 1.2 --- $id: http://devicetree.org/schemas/watchdog/loongson,ls1x-wdt.yaml# $schema: http://devicetree.org/meta-schemas/core.yaml# title: Loongson-1 Watchdog Timer maintainers: - Keguang Zhang <keguang.zhang@gmail.com> allOf: - $ref: watchdog.yaml# properties: compatible: enum: - loongson,ls1b-wdt - loongson,ls1c-wdt reg: maxItems: 1 clocks: maxItems: 1 required: - compatible - reg - clocks unevaluatedProperties: false examples: - | #include <dt-bindings/clock/loongson,ls1x-clk.h> watchdog: watchdog@1fe5c060 { compatible = "loongson,ls1b-wdt"; reg = <0x1fe5c060 0xc>; clocks = <&clkc LS1X_CLKID_APB>; };
Documentation/process/maintainer-netdev.rst +1 −1 Original line number Original line Diff line number Diff line Loading @@ -98,7 +98,7 @@ If you aren't subscribed to netdev and/or are simply unsure if repository link above for any new networking-related commits. You may repository link above for any new networking-related commits. You may also check the following website for the current status: also check the following website for the current status: http://vger.kernel.org/~davem/net-next.html https://patchwork.hopto.org/net-next.html The ``net`` tree continues to collect fixes for the vX.Y content, and is The ``net`` tree continues to collect fixes for the vX.Y content, and is fed back to Linus at regular (~weekly) intervals. Meaning that the fed back to Linus at regular (~weekly) intervals. Meaning that the Loading
Documentation/riscv/hwprobe.rst +1 −1 Original line number Original line Diff line number Diff line Loading @@ -49,7 +49,7 @@ The following keys are defined: privileged ISA, with the following known exceptions (more exceptions may be privileged ISA, with the following known exceptions (more exceptions may be added, but only if it can be demonstrated that the user ABI is not broken): added, but only if it can be demonstrated that the user ABI is not broken): * The :fence.i: instruction cannot be directly executed by userspace * The ``fence.i`` instruction cannot be directly executed by userspace programs (it may still be executed in userspace via a programs (it may still be executed in userspace via a kernel-controlled mechanism such as the vDSO). kernel-controlled mechanism such as the vDSO). Loading