arm64: qcom: msm8998-oneplus-common: Drop unussed NFC suspend pinctrl

arm64: qcom: msm8998-oneplus-common: Enable NFC
module: demote ELF structure error message to pr_debug
2021-11-09 14:45:47 +02:00 · 2021-11-01 06:13:48 +02:00 · 2021-11-01 06:13:48 +02:00 · 2021-11-01 06:13:48 +02:00 · 2021-11-01 06:13:47 +02:00 · 2021-11-01 06:13:47 +02:00
40569 changed files with 1500491 additions and 5200299 deletions
--- a/.clang-format
+++ b/.clang-format
@ -1,6 +1,6 @@
 # SPDX-License-Identifier: GPL-2.0
 #
-# clang-format configuration file. Intended for clang-format >= 11.
+# clang-format configuration file. Intended for clang-format >= 4.
 #
 # For more information, see:
 #
@ -13,7 +13,7 @@ AccessModifierOffset: -4
 AlignAfterOpenBracket: Align
 AlignConsecutiveAssignments: false
 AlignConsecutiveDeclarations: false
-AlignEscapedNewlines: Left
+#AlignEscapedNewlines: Left # Unknown to clang-format-4.0
 AlignOperands: true
 AlignTrailingComments: false
 AllowAllParametersOfDeclarationOnNextLine: false
@ -37,24 +37,24 @@ BraceWrapping:
  AfterObjCDeclaration: false
  AfterStruct: false
  AfterUnion: false
-  AfterExternBlock: false
+  #AfterExternBlock: false # Unknown to clang-format-5.0
  BeforeCatch: false
  BeforeElse: false
  IndentBraces: false
-  SplitEmptyFunction: true
+  #SplitEmptyFunction: true # Unknown to clang-format-4.0
-  SplitEmptyRecord: true
+  #SplitEmptyRecord: true # Unknown to clang-format-4.0
-  SplitEmptyNamespace: true
+  #SplitEmptyNamespace: true # Unknown to clang-format-4.0
 BreakBeforeBinaryOperators: None
 BreakBeforeBraces: Custom
-BreakBeforeInheritanceComma: false
+#BreakBeforeInheritanceComma: false # Unknown to clang-format-4.0
 BreakBeforeTernaryOperators: false
 BreakConstructorInitializersBeforeComma: false
-BreakConstructorInitializers: BeforeComma
+#BreakConstructorInitializers: BeforeComma # Unknown to clang-format-4.0
 BreakAfterJavaFieldAnnotations: false
 BreakStringLiterals: false
 ColumnLimit: 80
 CommentPragmas: '^ IWYU pragma:'
-CompactNamespaces: false
+#CompactNamespaces: false # Unknown to clang-format-4.0
 ConstructorInitializerAllOnOneLineOrOnePerLine: false
 ConstructorInitializerIndentWidth: 8
 ContinuationIndentWidth: 8
@ -62,56 +62,39 @@ Cpp11BracedListStyle: false
 DerivePointerAlignment: false
 DisableFormat: false
 ExperimentalAutoDetectBinPacking: false
-FixNamespaceComments: false
+#FixNamespaceComments: false # Unknown to clang-format-4.0
 # Taken from:
-#   git grep -h '^#define [^[:space:]]*for_each[^[:space:]]*(' include/ tools/ \
+#   git grep -h '^#define [^[:space:]]*for_each[^[:space:]]*(' include/ \
 #   | sed "s,^#define \([^[:space:]]*for_each[^[:space:]]*\)(.*$,  - '\1'," \
-#   | LC_ALL=C sort -u
+#   | sort | uniq
 ForEachMacros:
  - '__ata_qc_for_each'
  - '__bio_for_each_bvec'
  - '__bio_for_each_segment'
  - '__evlist__for_each_entry'
  - '__evlist__for_each_entry_continue'
  - '__evlist__for_each_entry_from'
  - '__evlist__for_each_entry_reverse'
  - '__evlist__for_each_entry_safe'
  - '__for_each_mem_range'
  - '__for_each_mem_range_rev'
  - '__for_each_thread'
  - '__hlist_for_each_rcu'
  - '__map__for_each_symbol_by_name'
  - '__perf_evlist__for_each_entry'
  - '__perf_evlist__for_each_entry_reverse'
  - '__perf_evlist__for_each_entry_safe'
  - '__rq_for_each_bio'
  - '__shost_for_each_device'
  - 'apei_estatus_for_each_section'
  - 'ata_for_each_dev'
  - 'ata_for_each_link'
  - '__ata_qc_for_each'
  - 'ata_qc_for_each'
  - 'ata_qc_for_each_raw'
  - 'ata_qc_for_each_with_internal'
  - 'ax25_for_each'
  - 'ax25_uid_for_each'
  - '__bio_for_each_bvec'
  - 'bio_for_each_bvec'
  - 'bio_for_each_bvec_all'
  - 'bio_for_each_folio_all'
  - 'bio_for_each_integrity_vec'
  - '__bio_for_each_segment'
  - 'bio_for_each_segment'
  - 'bio_for_each_segment_all'
  - 'bio_list_for_each'
  - 'bip_for_each_vec'
  - 'bitmap_for_each_clear_region'
  - 'bitmap_for_each_set_region'
  - 'blkg_for_each_descendant_post'
  - 'blkg_for_each_descendant_pre'
  - 'blk_queue_for_each_rl'
  - 'bond_for_each_slave'
  - 'bond_for_each_slave_rcu'
  - 'bpf__perf_for_each_map'
  - 'bpf__perf_for_each_map_named'
  - 'bpf_for_each_spilled_reg'
  - 'bpf_object__for_each_map'
  - 'bpf_object__for_each_program'
  - 'bpf_object__for_each_safe'
  - 'bpf_perf_object__for_each'
  - 'btree_for_each_safe128'
  - 'btree_for_each_safe32'
  - 'btree_for_each_safe64'
@ -119,7 +102,6 @@ ForEachMacros:
  - 'card_for_each_dev'
  - 'cgroup_taskset_for_each'
  - 'cgroup_taskset_for_each_leader'
  - 'cpufreq_for_each_efficient_entry_idx'
  - 'cpufreq_for_each_entry'
  - 'cpufreq_for_each_entry_idx'
  - 'cpufreq_for_each_valid_entry'
@ -127,22 +109,9 @@ ForEachMacros:
  - 'css_for_each_child'
  - 'css_for_each_descendant_post'
  - 'css_for_each_descendant_pre'
  - 'damon_for_each_region'
  - 'damon_for_each_region_safe'
  - 'damon_for_each_scheme'
  - 'damon_for_each_scheme_safe'
  - 'damon_for_each_target'
  - 'damon_for_each_target_safe'
  - 'data__for_each_file'
  - 'data__for_each_file_new'
  - 'data__for_each_file_start'
  - 'device_for_each_child_node'
  - 'displayid_iter_for_each'
  - 'dma_fence_array_for_each'
  - 'dma_fence_chain_for_each'
  - 'dma_fence_unwrap_for_each'
  - 'dma_resv_for_each_fence'
  - 'dma_resv_for_each_fence_unlocked'
  - 'do_for_each_ftrace_op'
  - 'drm_atomic_crtc_for_each_plane'
  - 'drm_atomic_crtc_state_for_each_plane'
@ -166,25 +135,6 @@ ForEachMacros:
  - 'drm_mm_for_each_node'
  - 'drm_mm_for_each_node_in_range'
  - 'drm_mm_for_each_node_safe'
  - 'dsa_switch_for_each_available_port'
  - 'dsa_switch_for_each_cpu_port'
  - 'dsa_switch_for_each_port'
  - 'dsa_switch_for_each_port_continue_reverse'
  - 'dsa_switch_for_each_port_safe'
  - 'dsa_switch_for_each_user_port'
  - 'dsa_tree_for_each_user_port'
  - 'dso__for_each_symbol'
  - 'dsos__for_each_with_build_id'
  - 'elf_hash_for_each_possible'
  - 'elf_section__for_each_rel'
  - 'elf_section__for_each_rela'
  - 'elf_symtab__for_each_symbol'
  - 'evlist__for_each_cpu'
  - 'evlist__for_each_entry'
  - 'evlist__for_each_entry_continue'
  - 'evlist__for_each_entry_from'
  - 'evlist__for_each_entry_reverse'
  - 'evlist__for_each_entry_safe'
  - 'flow_action_for_each'
  - 'for_each_acpi_dev_match'
  - 'for_each_active_dev_scope'
@ -192,11 +142,8 @@ ForEachMacros:
  - 'for_each_active_iommu'
  - 'for_each_aggr_pgid'
  - 'for_each_available_child_of_node'
  - 'for_each_bench'
  - 'for_each_bio'
  - 'for_each_board_func_rsrc'
  - 'for_each_btf_ext_rec'
  - 'for_each_btf_ext_sec'
  - 'for_each_bvec'
  - 'for_each_card_auxs'
  - 'for_each_card_auxs_safe'
@ -212,22 +159,17 @@ ForEachMacros:
  - 'for_each_child_of_node'
  - 'for_each_clear_bit'
  - 'for_each_clear_bit_from'
  - 'for_each_clear_bitrange'
  - 'for_each_clear_bitrange_from'
  - 'for_each_cmd'
  - 'for_each_cmsghdr'
  - 'for_each_collection'
  - 'for_each_comp_order'
  - 'for_each_compatible_node'
  - 'for_each_component_dais'
  - 'for_each_component_dais_safe'
  - 'for_each_comp_order'
  - 'for_each_console'
  - 'for_each_cpu'
  - 'for_each_cpu_and'
  - 'for_each_cpu_not'
  - 'for_each_cpu_wrap'
  - 'for_each_dapm_widgets'
  - 'for_each_dedup_cand'
  - 'for_each_dev_addr'
  - 'for_each_dev_scope'
  - 'for_each_dma_cap_mask'
@ -237,14 +179,13 @@ ForEachMacros:
  - 'for_each_dpcm_fe'
  - 'for_each_drhd_unit'
  - 'for_each_dss_dev'
  - 'for_each_dtpm_table'
  - 'for_each_efi_memory_desc'
  - 'for_each_efi_memory_desc_in_map'
  - 'for_each_element'
  - 'for_each_element_extid'
  - 'for_each_element_id'
  - 'for_each_endpoint_of_node'
  - 'for_each_event'
  - 'for_each_event_tps'
  - 'for_each_evictable_lru'
  - 'for_each_fib6_node_rt_rcu'
  - 'for_each_fib6_walker_rt'
@ -253,35 +194,31 @@ ForEachMacros:
  - 'for_each_free_mem_range'
  - 'for_each_free_mem_range_reverse'
  - 'for_each_func_rsrc'
  - 'for_each_group_evsel'
  - 'for_each_group_member'
  - 'for_each_hstate'
  - 'for_each_if'
  - 'for_each_inject_fn'
  - 'for_each_insn'
  - 'for_each_insn_prefix'
  - 'for_each_intid'
  - 'for_each_iommu'
  - 'for_each_ip_tunnel_rcu'
  - 'for_each_irq_nr'
  - 'for_each_lang'
  - 'for_each_link_codecs'
  - 'for_each_link_cpus'
  - 'for_each_link_platforms'
  - 'for_each_lru'
  - 'for_each_matching_node'
  - 'for_each_matching_node_and_match'
  - 'for_each_member'
  - 'for_each_memcg_cache_index'
  - 'for_each_mem_pfn_range'
  - '__for_each_mem_range'
  - 'for_each_mem_range'
  - '__for_each_mem_range_rev'
  - 'for_each_mem_range_rev'
  - 'for_each_mem_region'
  - 'for_each_member'
  - 'for_each_memory'
  - 'for_each_migratetype_order'
-  - 'for_each_missing_reg'
+  - 'for_each_msi_entry'
  - 'for_each_msi_entry_safe'
  - 'for_each_msi_vector'
  - 'for_each_net'
  - 'for_each_net_continue_reverse'
  - 'for_each_net_rcu'
  - 'for_each_netdev'
  - 'for_each_netdev_continue'
  - 'for_each_netdev_continue_rcu'
@ -291,13 +228,12 @@ ForEachMacros:
  - 'for_each_netdev_rcu'
  - 'for_each_netdev_reverse'
  - 'for_each_netdev_safe'
  - 'for_each_net_rcu'
  - 'for_each_new_connector_in_state'
  - 'for_each_new_crtc_in_state'
  - 'for_each_new_mst_mgr_in_state'
  - 'for_each_new_plane_in_state'
  - 'for_each_new_plane_in_state_reverse'
  - 'for_each_new_private_obj_in_state'
  - 'for_each_new_reg'
  - 'for_each_node'
  - 'for_each_node_by_name'
  - 'for_each_node_by_type'
@ -313,20 +249,20 @@ ForEachMacros:
  - 'for_each_old_connector_in_state'
  - 'for_each_old_crtc_in_state'
  - 'for_each_old_mst_mgr_in_state'
  - 'for_each_old_plane_in_state'
  - 'for_each_old_private_obj_in_state'
  - 'for_each_oldnew_connector_in_state'
  - 'for_each_oldnew_crtc_in_state'
  - 'for_each_oldnew_mst_mgr_in_state'
  - 'for_each_oldnew_plane_in_state'
  - 'for_each_oldnew_plane_in_state_reverse'
  - 'for_each_oldnew_private_obj_in_state'
  - 'for_each_old_plane_in_state'
  - 'for_each_old_private_obj_in_state'
  - 'for_each_online_cpu'
  - 'for_each_online_node'
  - 'for_each_online_pgdat'
  - 'for_each_path'
  - 'for_each_pci_bridge'
  - 'for_each_pci_dev'
  - 'for_each_pci_msi_entry'
  - 'for_each_pcm_streams'
  - 'for_each_physmem_range'
  - 'for_each_populated_zone'
@ -334,7 +270,6 @@ ForEachMacros:
  - 'for_each_present_cpu'
  - 'for_each_prime_number'
  - 'for_each_prime_number_from'
  - 'for_each_probe_cache_entry'
  - 'for_each_process'
  - 'for_each_process_thread'
  - 'for_each_prop_codec_conf'
@ -344,8 +279,6 @@ ForEachMacros:
  - 'for_each_prop_dlc_cpus'
  - 'for_each_prop_dlc_platforms'
  - 'for_each_property_of_node'
  - 'for_each_reg'
  - 'for_each_reg_filtered'
  - 'for_each_registered_fb'
  - 'for_each_requested_gpio'
  - 'for_each_requested_gpio_in_range'
@ -355,12 +288,8 @@ ForEachMacros:
  - 'for_each_rtd_components'
  - 'for_each_rtd_cpu_dais'
  - 'for_each_rtd_dais'
  - 'for_each_script'
  - 'for_each_sec'
  - 'for_each_set_bit'
  - 'for_each_set_bit_from'
  - 'for_each_set_bitrange'
  - 'for_each_set_bitrange_from'
  - 'for_each_set_clump8'
  - 'for_each_sg'
  - 'for_each_sg_dma_page'
@ -369,25 +298,18 @@ ForEachMacros:
  - 'for_each_sgtable_dma_sg'
  - 'for_each_sgtable_page'
  - 'for_each_sgtable_sg'
  - 'for_each_shell_test'
  - 'for_each_sibling_event'
  - 'for_each_subelement'
  - 'for_each_subelement_extid'
  - 'for_each_subelement_id'
-  - 'for_each_sublist'
+  - '__for_each_thread'
  - 'for_each_subsystem'
  - 'for_each_supported_activate_fn'
  - 'for_each_supported_inject_fn'
  - 'for_each_test'
  - 'for_each_thread'
  - 'for_each_token'
  - 'for_each_unicast_dest_pgid'
  - 'for_each_vsi'
  - 'for_each_wakeup_source'
  - 'for_each_zone'
  - 'for_each_zone_zonelist'
  - 'for_each_zone_zonelist_nodemask'
  - 'func_for_each_insn'
  - 'fwnode_for_each_available_child_node'
  - 'fwnode_for_each_child_node'
  - 'fwnode_graph_for_each_endpoint'
@ -401,13 +323,7 @@ ForEachMacros:
  - 'hash_for_each_possible_safe'
  - 'hash_for_each_rcu'
  - 'hash_for_each_safe'
  - 'hashmap__for_each_entry'
  - 'hashmap__for_each_entry_safe'
  - 'hashmap__for_each_key_entry'
  - 'hashmap__for_each_key_entry_safe'
  - 'hctx_for_each_ctx'
  - 'hists__for_each_format'
  - 'hists__for_each_sort_list'
  - 'hlist_bl_for_each_entry'
  - 'hlist_bl_for_each_entry_rcu'
  - 'hlist_bl_for_each_entry_safe'
@ -423,6 +339,7 @@ ForEachMacros:
  - 'hlist_for_each_entry_rcu_notrace'
  - 'hlist_for_each_entry_safe'
  - 'hlist_for_each_entry_srcu'
  - '__hlist_for_each_rcu'
  - 'hlist_for_each_safe'
  - 'hlist_nulls_for_each_entry'
  - 'hlist_nulls_for_each_entry_from'
@ -430,6 +347,9 @@ ForEachMacros:
  - 'hlist_nulls_for_each_entry_safe'
  - 'i3c_bus_for_each_i2cdev'
  - 'i3c_bus_for_each_i3cdev'
  - 'ide_host_for_each_port'
  - 'ide_port_for_each_dev'
  - 'ide_port_for_each_present_dev'
  - 'idr_for_each_entry'
  - 'idr_for_each_entry_continue'
  - 'idr_for_each_entry_continue_ul'
@ -437,12 +357,7 @@ ForEachMacros:
  - 'in_dev_for_each_ifa_rcu'
  - 'in_dev_for_each_ifa_rtnl'
  - 'inet_bind_bucket_for_each'
  - 'inet_lhash2_for_each_icsk'
  - 'inet_lhash2_for_each_icsk_continue'
  - 'inet_lhash2_for_each_icsk_rcu'
  - 'intlist__for_each_entry'
  - 'intlist__for_each_entry_safe'
  - 'kcore_copy__for_each_phdr'
  - 'key_for_each'
  - 'key_for_each_safe'
  - 'klp_for_each_func'
@ -453,9 +368,7 @@ ForEachMacros:
  - 'klp_for_each_object_static'
  - 'kunit_suite_for_each_test_case'
  - 'kvm_for_each_memslot'
  - 'kvm_for_each_memslot_in_gfn_range'
  - 'kvm_for_each_vcpu'
  - 'libbpf_nla_for_each_attr'
  - 'list_for_each'
  - 'list_for_each_codec'
  - 'list_for_each_codec_safe'
@ -475,7 +388,6 @@ ForEachMacros:
  - 'list_for_each_entry_safe_from'
  - 'list_for_each_entry_safe_reverse'
  - 'list_for_each_entry_srcu'
  - 'list_for_each_from'
  - 'list_for_each_prev'
  - 'list_for_each_prev_safe'
  - 'list_for_each_safe'
@ -483,18 +395,11 @@ ForEachMacros:
  - 'llist_for_each_entry'
  - 'llist_for_each_entry_safe'
  - 'llist_for_each_safe'
  - 'map__for_each_symbol'
  - 'map__for_each_symbol_by_name'
  - 'map_for_each_event'
  - 'map_for_each_metric'
  - 'maps__for_each_entry'
  - 'maps__for_each_entry_safe'
  - 'mci_for_each_dimm'
  - 'media_device_for_each_entity'
  - 'media_device_for_each_intf'
  - 'media_device_for_each_link'
  - 'media_device_for_each_pad'
  - 'msi_for_each_desc'
  - 'nanddev_io_for_each_page'
  - 'netdev_for_each_lower_dev'
  - 'netdev_for_each_lower_private'
@ -516,24 +421,9 @@ ForEachMacros:
  - 'of_property_for_each_string'
  - 'of_property_for_each_u32'
  - 'pci_bus_for_each_resource'
  - 'pci_doe_for_each_off'
  - 'pcl_for_each_chunk'
  - 'pcl_for_each_segment'
  - 'pcm_for_each_format'
  - 'perf_config_items__for_each_entry'
  - 'perf_config_sections__for_each_entry'
  - 'perf_config_set__for_each_entry'
  - 'perf_cpu_map__for_each_cpu'
  - 'perf_evlist__for_each_entry'
  - 'perf_evlist__for_each_entry_reverse'
  - 'perf_evlist__for_each_entry_safe'
  - 'perf_evlist__for_each_evsel'
  - 'perf_evlist__for_each_mmap'
  - 'perf_hpp_list__for_each_format'
  - 'perf_hpp_list__for_each_format_safe'
  - 'perf_hpp_list__for_each_sort_list'
  - 'perf_hpp_list__for_each_sort_list_safe'
  - 'perf_pmu__for_each_hybrid_pmu'
  - 'ping_portaddr_for_each_entry'
  - 'plist_for_each'
  - 'plist_for_each_continue'
@ -553,7 +443,6 @@ ForEachMacros:
  - 'rdma_for_each_block'
  - 'rdma_for_each_port'
  - 'rdma_umem_for_each_dma_block'
  - 'resort_rb__for_each_entry'
  - 'resource_list_for_each_entry'
  - 'resource_list_for_each_entry_safe'
  - 'rhl_for_each_entry_rcu'
@ -567,18 +456,15 @@ ForEachMacros:
  - 'rht_for_each_from'
  - 'rht_for_each_rcu'
  - 'rht_for_each_rcu_from'
  - '__rq_for_each_bio'
  - 'rq_for_each_bvec'
  - 'rq_for_each_segment'
  - 'rq_list_for_each'
  - 'rq_list_for_each_safe'
  - 'scsi_for_each_prot_sg'
  - 'scsi_for_each_sg'
  - 'sctp_for_each_hentry'
  - 'sctp_skb_for_each'
  - 'sec_for_each_insn'
  - 'sec_for_each_insn_continue'
  - 'sec_for_each_insn_from'
  - 'shdma_for_each_chan'
  - '__shost_for_each_device'
  - 'shost_for_each_device'
  - 'sk_for_each'
  - 'sk_for_each_bound'
@ -595,13 +481,7 @@ ForEachMacros:
  - 'snd_soc_dapm_widget_for_each_path_safe'
  - 'snd_soc_dapm_widget_for_each_sink_path'
  - 'snd_soc_dapm_widget_for_each_source_path'
  - 'strlist__for_each_entry'
  - 'strlist__for_each_entry_safe'
  - 'sym_for_each_insn'
  - 'sym_for_each_insn_continue_reverse'
  - 'symbols__for_each_entry'
  - 'tb_property_for_each'
  - 'tcf_act_for_each_action'
  - 'tcf_exts_for_each_action'
  - 'udp_portaddr_for_each_entry'
  - 'udp_portaddr_for_each_entry_rcu'
@ -625,17 +505,15 @@ ForEachMacros:
  - 'xbc_node_for_each_array_value'
  - 'xbc_node_for_each_child'
  - 'xbc_node_for_each_key_value'
  - 'xbc_node_for_each_subkey'
  - 'zorro_for_each_dev'
-IncludeBlocks: Preserve
+#IncludeBlocks: Preserve # Unknown to clang-format-5.0
 IncludeCategories:
  - Regex: '.*'
    Priority: 1
 IncludeIsMainRegex: '(Test)?$'
 IndentCaseLabels: false
-IndentGotoLabels: false
+#IndentPPDirectives: None # Unknown to clang-format-5.0
 IndentPPDirectives: None
 IndentWidth: 8
 IndentWrappedFunctionNames: false
 JavaScriptQuotes: Leave
@ -645,13 +523,13 @@ MacroBlockBegin: ''
 MacroBlockEnd: ''
 MaxEmptyLinesToKeep: 1
 NamespaceIndentation: None
-ObjCBinPackProtocolList: Auto
+#ObjCBinPackProtocolList: Auto # Unknown to clang-format-5.0
 ObjCBlockIndentWidth: 8
 ObjCSpaceAfterProperty: true
 ObjCSpaceBeforeProtocolList: true
 # Taken from git's rules
-PenaltyBreakAssignment: 10
+#PenaltyBreakAssignment: 10 # Unknown to clang-format-4.0
 PenaltyBreakBeforeFirstCallParameter: 30
 PenaltyBreakComment: 10
 PenaltyBreakFirstLessLess: 0
@ -662,14 +540,14 @@ PenaltyReturnTypeOnItsOwnLine: 60
 PointerAlignment: Right
 ReflowComments: false
 SortIncludes: false
-SortUsingDeclarations: false
+#SortUsingDeclarations: false # Unknown to clang-format-4.0
 SpaceAfterCStyleCast: false
 SpaceAfterTemplateKeyword: true
 SpaceBeforeAssignmentOperators: true
-SpaceBeforeCtorInitializerColon: true
+#SpaceBeforeCtorInitializerColon: true # Unknown to clang-format-5.0
-SpaceBeforeInheritanceColon: true
+#SpaceBeforeInheritanceColon: true # Unknown to clang-format-5.0
-SpaceBeforeParens: ControlStatementsExceptForEachMacros
+SpaceBeforeParens: ControlStatements
-SpaceBeforeRangeBasedForLoopColon: true
+#SpaceBeforeRangeBasedForLoopColon: true # Unknown to clang-format-5.0
 SpaceInEmptyParentheses: false
 SpacesBeforeTrailingComments: 1
 SpacesInAngles: false
--- a/.get_maintainer.ignore
+++ b/.get_maintainer.ignore
@ -1,4 +1,2 @@
 Alan Cox <alan@lxorguk.ukuu.org.uk>
 Alan Cox <root@hraefn.swansea.linux.org.uk>
 Christoph Hellwig <hch@lst.de>
 Marc Gonzalez <marc.w.gonzalez@free.fr>
--- a/.gitignore
+++ b/.gitignore
@ -37,8 +37,6 @@
 *.o
 *.o.*
 *.patch
 *.rmeta
 *.rsi
 *.s
 *.so
 *.so.dbg
@ -47,7 +45,6 @@
 *.symversions
 *.tab.[ch]
 *.tar
 *.usyms
 *.xz
 *.zst
 Module.symvers
@ -99,7 +96,6 @@ modules.order
 !.gitattributes
 !.gitignore
 !.mailmap
 !.rustfmt.toml
 #
 # Generated include files
@ -165,6 +161,3 @@ x509.genkey
 # Documentation toolchain
 sphinx_*/
 # Rust analyzer configuration
 /rust-project.json
--- a/.mailmap
+++ b/.mailmap
@ -10,14 +10,10 @@
 # Please keep this list dictionary sorted.
 #
 Aaron Durbin <adurbin@google.com>
 Abel Vesa <abelvesa@kernel.org> <abel.vesa@nxp.com>
 Abel Vesa <abelvesa@kernel.org> <abelvesa@gmail.com>
 Abhinav Kumar <quic_abhinavk@quicinc.com> <abhinavk@codeaurora.org>
 Adam Oldham <oldhamca@gmail.com>
 Adam Radford <aradford@gmail.com>
 Adriana Reus <adi.reus@gmail.com> <adriana.reus@intel.com>
 Adrian Bunk <bunk@stusta.de>
 Akhil P Oommen <quic_akhilpo@quicinc.com> <akhilpo@codeaurora.org>
 Alan Cox <alan@lxorguk.ukuu.org.uk>
 Alan Cox <root@hraefn.swansea.linux.org.uk>
 Aleksandar Markovic <aleksandar.markovic@mips.com> <aleksandar.markovic@imgtec.com>
@ -46,34 +42,20 @@ Andrew Vasquez <andrew.vasquez@qlogic.com>
 Andrey Konovalov <andreyknvl@gmail.com> <andreyknvl@google.com>
 Andrey Ryabinin <ryabinin.a.a@gmail.com> <a.ryabinin@samsung.com>
 Andrey Ryabinin <ryabinin.a.a@gmail.com> <aryabinin@virtuozzo.com>
 Andrzej Hajda <andrzej.hajda@intel.com> <a.hajda@samsung.com>
 André Almeida <andrealmeid@igalia.com> <andrealmeid@collabora.com>
 Andy Adamson <andros@citi.umich.edu>
 Antoine Tenart <atenart@kernel.org> <antoine.tenart@bootlin.com>
 Antoine Tenart <atenart@kernel.org> <antoine.tenart@free-electrons.com>
 Antonio Ospite <ao2@ao2.it> <ao2@amarulasolutions.com>
 Anup Patel <anup@brainfault.org> <anup.patel@wdc.com>
 Archit Taneja <archit@ti.com>
 Ard Biesheuvel <ardb@kernel.org> <ard.biesheuvel@linaro.org>
 Arnaud Patard <arnaud.patard@rtp-net.org>
 Arnd Bergmann <arnd@arndb.de>
 Atish Patra <atishp@atishpatra.org> <atish.patra@wdc.com>
 Axel Dyks <xl@xlsigned.net>
 Axel Lin <axel.lin@gmail.com>
 Baolin Wang <baolin.wang@linux.alibaba.com> <baolin.wang@linaro.org>
 Baolin Wang <baolin.wang@linux.alibaba.com> <baolin.wang@spreadtrum.com>
 Baolin Wang <baolin.wang@linux.alibaba.com> <baolin.wang@unisoc.com>
 Baolin Wang <baolin.wang@linux.alibaba.com> <baolin.wang7@gmail.com>
 Bart Van Assche <bvanassche@acm.org> <bart.vanassche@sandisk.com>
 Bart Van Assche <bvanassche@acm.org> <bart.vanassche@wdc.com>
 Ben Gardner <bgardner@wabtec.com>
 Ben M Cahill <ben.m.cahill@intel.com>
 Ben Widawsky <bwidawsk@kernel.org> <ben@bwidawsk.net>
 Ben Widawsky <bwidawsk@kernel.org> <ben.widawsky@intel.com>
 Ben Widawsky <bwidawsk@kernel.org> <benjamin.widawsky@intel.com>
 Bjorn Andersson <andersson@kernel.org> <bjorn@kryo.se>
 Bjorn Andersson <andersson@kernel.org> <bjorn.andersson@linaro.org>
 Bjorn Andersson <andersson@kernel.org> <bjorn.andersson@sonymobile.com>
 Björn Steinbrink <B.Steinbrink@gmx.de>
 Björn Töpel <bjorn@kernel.org> <bjorn.topel@gmail.com>
 Björn Töpel <bjorn@kernel.org> <bjorn.topel@intel.com>
@ -81,30 +63,18 @@ Boris Brezillon <bbrezillon@kernel.org> <b.brezillon.dev@gmail.com>
 Boris Brezillon <bbrezillon@kernel.org> <b.brezillon@overkiz.com>
 Boris Brezillon <bbrezillon@kernel.org> <boris.brezillon@bootlin.com>
 Boris Brezillon <bbrezillon@kernel.org> <boris.brezillon@free-electrons.com>
 Brendan Higgins <brendan.higgins@linux.dev> <brendanhiggins@google.com>
 Brian Avery <b.avery@hp.com>
 Brian King <brking@us.ibm.com>
 Brian Silverman <bsilver16384@gmail.com> <brian.silverman@bluerivertech.com>
 Cai Huoqing <cai.huoqing@linux.dev> <caihuoqing@baidu.com>
 Changbin Du <changbin.du@intel.com> <changbin.du@gmail.com>
 Changbin Du <changbin.du@intel.com> <changbin.du@intel.com>
 Chao Yu <chao@kernel.org> <chao2.yu@samsung.com>
 Chao Yu <chao@kernel.org> <yuchao0@huawei.com>
 Chris Chiu <chris.chiu@canonical.com> <chiu@endlessm.com>
 Chris Chiu <chris.chiu@canonical.com> <chiu@endlessos.org>
 Christian Borntraeger <borntraeger@linux.ibm.com> <borntraeger@de.ibm.com>
 Christian Borntraeger <borntraeger@linux.ibm.com> <cborntra@de.ibm.com>
 Christian Borntraeger <borntraeger@linux.ibm.com> <borntrae@de.ibm.com>
 Christian Brauner <brauner@kernel.org> <christian@brauner.io>
 Christian Brauner <brauner@kernel.org> <christian.brauner@canonical.com>
 Christian Brauner <brauner@kernel.org> <christian.brauner@ubuntu.com>
 Christian Marangi <ansuelsmth@gmail.com>
 Christophe Ricard <christophe.ricard@gmail.com>
 Christoph Hellwig <hch@lst.de>
 Colin Ian King <colin.i.king@gmail.com> <colin.king@canonical.com>
 Corey Minyard <minyard@acm.org>
 Damian Hobson-Garcia <dhobsong@igel.co.jp>
 Dan Carpenter <error27@gmail.com> <dan.carpenter@oracle.com>
 Daniel Borkmann <daniel@iogearbox.net> <danborkmann@googlemail.com>
 Daniel Borkmann <daniel@iogearbox.net> <danborkmann@iogearbox.net>
 Daniel Borkmann <daniel@iogearbox.net> <daniel.borkmann@tik.ee.ethz.ch>
@ -130,7 +100,6 @@ Douglas Gilbert <dougg@torque.net>
 Ed L. Cashin <ecashin@coraid.com>
 Erik Kaneda <erik.kaneda@intel.com> <erik.schmauss@intel.com>
 Evgeniy Polyakov <johnpol@2ka.mipt.ru>
 Ezequiel Garcia <ezequiel@vanguardiasur.com.ar> <ezequiel@collabora.com>
 Felipe W Damasio <felipewd@terra.com.br>
 Felix Kuhling <fxkuehl@gmx.de>
 Felix Moeller <felix@derklecks.de>
@ -138,14 +107,11 @@ Filipe Lautert <filipe@icewall.org>
 Finn Thain <fthain@linux-m68k.org> <fthain@telegraphics.com.au>
 Franck Bui-Huu <vagabon.xyz@gmail.com>
 Frank Rowand <frowand.list@gmail.com> <frank.rowand@am.sony.com>
 Frank Rowand <frowand.list@gmail.com> <frank.rowand@sony.com>
 Frank Rowand <frowand.list@gmail.com> <frank.rowand@sonymobile.com>
 Frank Rowand <frowand.list@gmail.com> <frowand@mvista.com>
 Frank Zago <fzago@systemfabricworks.com>
 Gao Xiang <xiang@kernel.org> <gaoxiang25@huawei.com>
 Gao Xiang <xiang@kernel.org> <hsiangkao@aol.com>
 Gao Xiang <xiang@kernel.org> <hsiangkao@linux.alibaba.com>
 Gao Xiang <xiang@kernel.org> <hsiangkao@redhat.com>
 Gerald Schaefer <gerald.schaefer@linux.ibm.com> <geraldsc@de.ibm.com>
 Gerald Schaefer <gerald.schaefer@linux.ibm.com> <gerald.schaefer@de.ibm.com>
 Gerald Schaefer <gerald.schaefer@linux.ibm.com> <geraldsc@linux.vnet.ibm.com>
@ -154,10 +120,6 @@ Greg Kroah-Hartman <gregkh@suse.de>
 Greg Kroah-Hartman <greg@kroah.com>
 Greg Kurz <groug@kaod.org> <gkurz@linux.vnet.ibm.com>
 Gregory CLEMENT <gregory.clement@bootlin.com> <gregory.clement@free-electrons.com>
 Guilherme G. Piccoli <kernel@gpiccoli.net> <gpiccoli@linux.vnet.ibm.com>
 Guilherme G. Piccoli <kernel@gpiccoli.net> <gpiccoli@canonical.com>
 Guo Ren <guoren@kernel.org> <guoren@linux.alibaba.com>
 Guo Ren <guoren@kernel.org> <ren_guo@c-sky.com>
 Gustavo Padovan <gustavo@las.ic.unicamp.br>
 Gustavo Padovan <padovan@profusion.mobi>
 Hanjun Guo <guohanjun@huawei.com> <hanjun.guo@linaro.org>
@ -184,7 +146,6 @@ Jan Glauber <jan.glauber@gmail.com> <jang@de.ibm.com>
 Jan Glauber <jan.glauber@gmail.com> <jang@linux.vnet.ibm.com>
 Jan Glauber <jan.glauber@gmail.com> <jglauber@cavium.com>
 Jarkko Sakkinen <jarkko@kernel.org> <jarkko.sakkinen@linux.intel.com>
 Jarkko Sakkinen <jarkko@kernel.org> <jarkko@profian.com>
 Jason Gunthorpe <jgg@ziepe.ca> <jgg@mellanox.com>
 Jason Gunthorpe <jgg@ziepe.ca> <jgg@nvidia.com>
 Jason Gunthorpe <jgg@ziepe.ca> <jgunthorpe@obsidianresearch.com>
@ -203,14 +164,11 @@ Jeff Layton <jlayton@kernel.org> <jlayton@redhat.com>
 Jens Axboe <axboe@suse.de>
 Jens Osterkamp <Jens.Osterkamp@de.ibm.com>
 Jernej Skrabec <jernej.skrabec@gmail.com> <jernej.skrabec@siol.net>
 Jessica Zhang <quic_jesszhan@quicinc.com> <jesszhan@codeaurora.org>
 Jiri Slaby <jirislaby@kernel.org> <jirislaby@gmail.com>
 Jiri Slaby <jirislaby@kernel.org> <jslaby@novell.com>
 Jiri Slaby <jirislaby@kernel.org> <jslaby@suse.com>
 Jiri Slaby <jirislaby@kernel.org> <jslaby@suse.cz>
 Jiri Slaby <jirislaby@kernel.org> <xslaby@fi.muni.cz>
 Jisheng Zhang <jszhang@kernel.org> <jszhang@marvell.com>
 Jisheng Zhang <jszhang@kernel.org> <Jisheng.Zhang@synaptics.com>
 Johan Hovold <johan@kernel.org> <jhovold@gmail.com>
 Johan Hovold <johan@kernel.org> <johan@hovoldconsulting.com>
 John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
@ -221,14 +179,10 @@ Jordan Crouse <jordan@cosmicpenguin.net> <jcrouse@codeaurora.org>
 <josh@joshtriplett.org> <josht@linux.vnet.ibm.com>
 <josh@joshtriplett.org> <josht@us.ibm.com>
 <josh@joshtriplett.org> <josht@vnet.ibm.com>
 Josh Poimboeuf <jpoimboe@kernel.org> <jpoimboe@redhat.com>
 Josh Poimboeuf <jpoimboe@kernel.org> <jpoimboe@us.ibm.com>
 Juha Yrjola <at solidboot.com>
 Juha Yrjola <juha.yrjola@nokia.com>
 Juha Yrjola <juha.yrjola@solidboot.com>
 Julien Thierry <julien.thierry.kdev@gmail.com> <julien.thierry@arm.com>
 Kalle Valo <kvalo@kernel.org> <kvalo@codeaurora.org>
 Kalyan Thota <quic_kalyant@quicinc.com> <kalyan_t@codeaurora.org>
 Kay Sievers <kay.sievers@vrfy.org>
 Kees Cook <keescook@chromium.org> <kees.cook@canonical.com>
 Kees Cook <keescook@chromium.org> <keescook@google.com>
@ -237,16 +191,12 @@ Kees Cook <keescook@chromium.org> <kees@ubuntu.com>
 Keith Busch <kbusch@kernel.org> <keith.busch@intel.com>
 Keith Busch <kbusch@kernel.org> <keith.busch@linux.intel.com>
 Kenneth W Chen <kenneth.w.chen@intel.com>
 Kirill Tkhai <tkhai@ya.ru> <ktkhai@virtuozzo.com>
 Konstantin Khlebnikov <koct9i@gmail.com> <khlebnikov@yandex-team.ru>
 Konstantin Khlebnikov <koct9i@gmail.com> <k.khlebnikov@samsung.com>
 Koushik <raghavendra.koushik@neterion.com>
 Krishna Manikandan <quic_mkrishn@quicinc.com> <mkrishn@codeaurora.org>
 Krzysztof Kozlowski <krzk@kernel.org> <k.kozlowski.k@gmail.com>
 Krzysztof Kozlowski <krzk@kernel.org> <k.kozlowski@samsung.com>
 Krzysztof Kozlowski <krzk@kernel.org> <krzysztof.kozlowski@canonical.com>
 Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
 Kuogee Hsieh <quic_khsieh@quicinc.com> <khsieh@codeaurora.org>
 Leonardo Bras <leobras.c@gmail.com> <leonardo@linux.ibm.com>
 Leonid I Ananiev <leonid.i.ananiev@intel.com>
 Leon Romanovsky <leon@kernel.org> <leon@leon.nu>
@ -258,8 +208,6 @@ Linus Lüssing <linus.luessing@c0d3.blue> <linus.luessing@web.de>
 <linux-hardening@vger.kernel.org> <kernel-hardening@lists.openwall.com>
 Li Yang <leoyang.li@nxp.com> <leoli@freescale.com>
 Li Yang <leoyang.li@nxp.com> <leo@zh-kernel.org>
 Lorenzo Pieralisi <lpieralisi@kernel.org> <lorenzo.pieralisi@arm.com>
 Luca Ceresoli <luca.ceresoli@bootlin.com> <luca@lucaceresoli.net>
 Lukasz Luba <lukasz.luba@arm.com> <l.luba@partner.samsung.com>
 Maciej W. Rozycki <macro@mips.com> <macro@imgtec.com>
 Maciej W. Rozycki <macro@orcam.me.uk> <macro@linux-mips.org>
@ -275,7 +223,6 @@ Mark Yao <markyao0591@gmail.com> <mark.yao@rock-chips.com>
 Martin Kepplinger <martink@posteo.de> <martin.kepplinger@ginzinger.com>
 Martin Kepplinger <martink@posteo.de> <martin.kepplinger@puri.sm>
 Martin Kepplinger <martink@posteo.de> <martin.kepplinger@theobroma-systems.com>
 Martyna Szapar-Mudlaw <martyna.szapar-mudlaw@linux.intel.com> <martyna.szapar-mudlaw@intel.com>
 Mathieu Othacehe <m.othacehe@gmail.com>
 Matthew Wilcox <willy@infradead.org> <matthew.r.wilcox@intel.com>
 Matthew Wilcox <willy@infradead.org> <matthew@wil.cx>
@ -320,7 +267,6 @@ Morten Welinder <welinder@troll.com>
 Mythri P K <mythripk@ti.com>
 Nadia Yvette Chambers <nyc@holomorphy.com> William Lee Irwin III <wli@holomorphy.com>
 Nathan Chancellor <nathan@kernel.org> <natechancellor@gmail.com>
 Neil Armstrong <neil.armstrong@linaro.org> <narmstrong@baylibre.com>
 Nguyen Anh Quynh <aquynh@gmail.com>
 Nicholas Piggin <npiggin@gmail.com> <npiggen@suse.de>
 Nicholas Piggin <npiggin@gmail.com> <npiggin@kernel.dk>
@ -332,13 +278,11 @@ Nicolas Pitre <nico@fluxnic.net> <nicolas.pitre@linaro.org>
 Nicolas Pitre <nico@fluxnic.net> <nico@linaro.org>
 Nicolas Saenz Julienne <nsaenz@kernel.org> <nsaenzjulienne@suse.de>
 Nicolas Saenz Julienne <nsaenz@kernel.org> <nsaenzjulienne@suse.com>
 Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se>
 Oleksij Rempel <linux@rempel-privat.de> <bug-track@fisher-privat.net>
 Oleksij Rempel <linux@rempel-privat.de> <external.Oleksij.Rempel@de.bosch.com>
 Oleksij Rempel <linux@rempel-privat.de> <fixed-term.Oleksij.Rempel@de.bosch.com>
 Oleksij Rempel <linux@rempel-privat.de> <o.rempel@pengutronix.de>
 Oleksij Rempel <linux@rempel-privat.de> <ore@pengutronix.de>
 Oliver Upton <oliver.upton@linux.dev> <oupton@google.com>
 Pali Rohár <pali@kernel.org> <pali.rohar@gmail.com>
 Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
 Patrick Mochel <mochel@digitalimplant.org>
@ -354,12 +298,10 @@ Peter Oruba <peter@oruba.de>
 Pratyush Anand <pratyush.anand@gmail.com> <pratyush.anand@st.com>
 Praveen BP <praveenbp@ti.com>
 Punit Agrawal <punitagrawal@gmail.com> <punit.agrawal@arm.com>
-Qais Yousef <qyousef@layalina.io> <qais.yousef@imgtec.com>
+Qais Yousef <qsyousef@gmail.com> <qais.yousef@imgtec.com>
 Qais Yousef <qyousef@layalina.io> <qais.yousef@arm.com>
 Quentin Monnet <quentin@isovalent.com> <quentin.monnet@netronome.com>
 Quentin Perret <qperret@qperret.net> <quentin.perret@arm.com>
 Rafael J. Wysocki <rjw@rjwysocki.net> <rjw@sisk.pl>
 Rajeev Nandan <quic_rajeevny@quicinc.com> <rajeevny@codeaurora.org>
 Rajesh Shah <rajesh.shah@intel.com>
 Ralf Baechle <ralf@linux-mips.org>
 Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
@ -368,16 +310,12 @@ Rémi Denis-Courmont <rdenis@simphalempin.com>
 Ricardo Ribalda <ribalda@kernel.org> <ricardo@ribalda.com>
 Ricardo Ribalda <ribalda@kernel.org> Ricardo Ribalda Delgado <ribalda@kernel.org>
 Ricardo Ribalda <ribalda@kernel.org> <ricardo.ribalda@gmail.com>
 Roman Gushchin <roman.gushchin@linux.dev> <guro@fb.com>
 Roman Gushchin <roman.gushchin@linux.dev> <guroan@gmail.com>
 Roman Gushchin <roman.gushchin@linux.dev> <klamm@yandex-team.ru>
 Ross Zwisler <zwisler@kernel.org> <ross.zwisler@linux.intel.com>
 Rudolf Marek <R.Marek@sh.cvut.cz>
 Rui Saraiva <rmps@joel.ist.utl.pt>
 Sachin P Sant <ssant@in.ibm.com>
 Sakari Ailus <sakari.ailus@linux.intel.com> <sakari.ailus@iki.fi>
 Sam Ravnborg <sam@mars.ravnborg.org>
 Sankeerth Billakanti <quic_sbillaka@quicinc.com> <sbillaka@codeaurora.org>
 Santosh Shilimkar <santosh.shilimkar@oracle.org>
 Santosh Shilimkar <ssantosh@kernel.org>
 Sarangdhar Joshi <spjoshi@codeaurora.org>
@ -388,7 +326,6 @@ Sean Nyekjaer <sean@geanix.com> <sean.nyekjaer@prevas.dk>
 Sebastian Reichel <sre@kernel.org> <sebastian.reichel@collabora.co.uk>
 Sebastian Reichel <sre@kernel.org> <sre@debian.org>
 Sedat Dilek <sedat.dilek@gmail.com> <sedat.dilek@credativ.de>
 Seth Forshee <sforshee@kernel.org> <seth.forshee@canonical.com>
 Shiraz Hashim <shiraz.linux.kernel@gmail.com> <shiraz.hashim@st.com>
 Shuah Khan <shuah@kernel.org> <shuahkhan@gmail.com>
 Shuah Khan <shuah@kernel.org> <shuah.khan@hp.com>
@ -422,11 +359,6 @@ Uwe Kleine-König <ukleinek@strlen.de>
 Uwe Kleine-König <ukl@pengutronix.de>
 Uwe Kleine-König <Uwe.Kleine-Koenig@digi.com>
 Valdis Kletnieks <Valdis.Kletnieks@vt.edu>
 Vasily Averin <vasily.averin@linux.dev> <vvs@virtuozzo.com>
 Vasily Averin <vasily.averin@linux.dev> <vvs@openvz.org>
 Vasily Averin <vasily.averin@linux.dev> <vvs@parallels.com>
 Vasily Averin <vasily.averin@linux.dev> <vvs@sw.ru>
 Valentin Schneider <vschneid@redhat.com> <valentin.schneider@arm.com>
 Vinod Koul <vkoul@kernel.org> <vinod.koul@intel.com>
 Vinod Koul <vkoul@kernel.org> <vinod.koul@linux.intel.com>
 Vinod Koul <vkoul@kernel.org> <vkoul@infradead.org>
--- a/.rustfmt.toml
+++ b/.rustfmt.toml
@ -1,12 +0,0 @@
 edition = "2021"
 newline_style = "Unix"
 # Unstable options that help catching some mistakes in formatting and that we may want to enable
 # when they become stable.
 #
 # They are kept here since they are useful to run from time to time.
 #format_code_in_doc_comments = true
 #reorder_impl_items = true
 #comment_width = 100
 #wrap_comments = true
 #normalize_comments = true
--- a/5768
+++ b/5768
--- a/19
+++ b/19
@ -315,11 +315,6 @@ S: Via Delle Palme, 9
 S: Terni 05100
 S: Italy
 N: Ohad Ben Cohen
 E: ohad@wizery.com
 D: Remote Processor (remoteproc) subsystem
 D: Remote Processor Messaging (rpmsg) subsystem
 N: Krzysztof Benedyczak
 E: golbi@mat.uni.torun.pl
 W: http://www.mat.uni.torun.pl/~golbi
@ -627,10 +622,6 @@ S: 48287 Sawleaf
 S: Fremont, California 94539
 S: USA
 N: Tomas Cech
 E: sleep_walker@suse.com
 D: arm/palm treo support
 N: Florent Chabaud
 E: florent.chabaud@polytechnique.org
 D: software suspend
@ -899,12 +890,6 @@ S: 3000 FORE Drive
 S: Warrendale, Pennsylvania 15086
 S: USA
 N: Ludovic Desroches
 E: ludovic.desroches@microchip.com
 D: Maintainer for ARM/Microchip (AT91) SoC support
 D: Author of ADC, pinctrl, XDMA and SDHCI drivers for this platform
 S: France
 N: Martin Devera
 E: devik@cdi.cz
 W: http://luxik.cdi.cz/~devik/qos/
@ -3495,10 +3480,6 @@ D: wd33c93 SCSI driver (linux-m68k)
 S: San Jose, California
 S: USA
 N: Joonyoung Shim
 E: y0922.shim@samsung.com
 D: Samsung Exynos DRM drivers
 N: Robert Siemer
 E: Robert.Siemer@gmx.de
 P: 2048/C99A4289 2F DC 17 2E 56 62 01 C8  3D F2 AC 09 F2 E5 DD EE
--- a/Documentation/ABI/obsolete/o2cb
+++ b/Documentation/ABI/obsolete/o2cb
@ -1,11 +0,0 @@
 What:		/sys/o2cb
 Date:		Dec 2005
 KernelVersion:	2.6.16
 Contact:	ocfs2-devel@oss.oracle.com
 Description:	Ocfs2-tools looks at 'interface-revision' for versioning
 		information. Each logmask/ file controls a set of debug prints
 		and can be written into with the strings "allow", "deny", or
 		"off". Reading the file returns the current state.
 		Was renamed to /sys/fs/u2cb/
 Users:		ocfs2-tools. It's sufficient to mail proposed changes to
 		ocfs2-devel@oss.oracle.com.
--- a/Documentation/ABI/obsolete/procfs-i8k
+++ b/Documentation/ABI/obsolete/procfs-i8k
@ -1,10 +0,0 @@
 What:		/proc/i8k
 Date:		November 2001
 KernelVersion:	2.4.14
 Contact:	Pali Rohár <pali@kernel.org>
 Description:	Legacy interface for getting/setting sensor information like
 		fan speed, temperature, serial number, hotkey status etc
 		on Dell Laptops.
 		Since the driver is now using the standard hwmon sysfs interface,
 		the procfs interface is deprecated.
 Users:		https://github.com/vitorafsr/i8kutils
--- a/Documentation/ABI/obsolete/sysfs-bus-iio
+++ b/Documentation/ABI/obsolete/sysfs-bus-iio
@ -6,7 +6,6 @@ Description:
 		Since Kernel 5.11, multiple buffers are supported.
 		so, it is better to use, instead:
 			/sys/bus/iio/devices/iio:deviceX/bufferY/length
 What:		/sys/bus/iio/devices/iio:deviceX/buffer/enable
@ -18,7 +17,6 @@ Description:
 		Since Kernel 5.11, multiple buffers are supported.
 		so, it is better to use, instead:
 			/sys/bus/iio/devices/iio:deviceX/bufferY/enable
 What:		/sys/bus/iio/devices/iio:deviceX/scan_elements
@ -167,7 +165,6 @@ Description:
 		Since Kernel 5.11, multiple buffers are supported.
 		so, it is better to use, instead:
 			/sys/bus/iio/devices/iio:deviceX/bufferY/watermark
 What:		/sys/bus/iio/devices/iio:deviceX/buffer/data_available
@ -182,5 +179,4 @@ Description:
 		Since Kernel 5.11, multiple buffers are supported.
 		so, it is better to use, instead:
 			/sys/bus/iio/devices/iio:deviceX/bufferY/data_available
--- a/Documentation/ABI/obsolete/sysfs-class-dax
+++ b/Documentation/ABI/obsolete/sysfs-class-dax
@ -0,0 +1,22 @@
 What:           /sys/class/dax/
 Date:           May, 2016
 KernelVersion:  v4.7
 Contact:        nvdimm@lists.linux.dev
 Description:	Device DAX is the device-centric analogue of Filesystem
 		DAX (CONFIG_FS_DAX).  It allows memory ranges to be
 		allocated and mapped without need of an intervening file
 		system.  Device DAX is strict, precise and predictable.
 		Specifically this interface:
 		1. Guarantees fault granularity with respect to a given
 		   page size (pte, pmd, or pud) set at configuration time.
 		2. Enforces deterministic behavior by being strict about
 		   what fault scenarios are supported.
 		The /sys/class/dax/ interface enumerates all the
 		device-dax instances in the system. The ABI is
 		deprecated and will be removed after 2020. It is
 		replaced with the DAX bus interface /sys/bus/dax/ where
 		device-dax instances can be found under
 		/sys/bus/dax/devices/
--- a/Documentation/ABI/removed/sysfs-mce
+++ b/Documentation/ABI/removed/sysfs-mce
@ -1,37 +0,0 @@
 What:		/sys/devices/system/machinecheck/machinecheckX/tolerant
 Contact:	Borislav Petkov <bp@suse.de>
 Date:		Dec, 2021
 Description:
 		Unused and obsolete after the advent of recoverable machine
 		checks (see last sentence below) and those are present since
 		2010 (Nehalem).
 		Original description:
 		The entries appear for each CPU, but they are truly shared
 		between all CPUs.
 		Tolerance level. When a machine check exception occurs for a
 		non corrected machine check the kernel can take different
 		actions.
 		Since machine check exceptions can happen any time it is
 		sometimes risky for the kernel to kill a process because it
 		defies normal kernel locking rules. The tolerance level
 		configures how hard the kernel tries to recover even at some
 		risk of	deadlock. Higher tolerant values trade potentially
 		better uptime with the risk of a crash or even corruption
 		(for tolerant >= 3).
 		==  ===========================================================
 		 0  always panic on uncorrected errors, log corrected errors
 		 1  panic or SIGBUS on uncorrected errors, log corrected errors
 		 2  SIGBUS or log uncorrected errors, log corrected errors
 		 3  never panic or SIGBUS, log all errors (for testing only)
 		==  ===========================================================
 		Default: 1
 		Note this only makes a difference if the CPU allows recovery
 		from a machine check exception. Current x86 CPUs generally
 		do not.
--- a/Documentation/ABI/stable/o2cb
+++ b/Documentation/ABI/stable/o2cb
@ -1,4 +1,4 @@
-What:		/sys/fs/o2cb/
+What:		/sys/fs/o2cb/ (was /sys/o2cb)
 Date:		Dec 2005
 KernelVersion:	2.6.16
 Contact:	ocfs2-devel@oss.oracle.com
--- a/Documentation/ABI/stable/sysfs-block
+++ b/Documentation/ABI/stable/sysfs-block
@ -1,734 +0,0 @@
 What:		/sys/block/<disk>/alignment_offset
 Date:		April 2009
 Contact:	Martin K. Petersen <martin.petersen@oracle.com>
 Description:
 		Storage devices may report a physical block size that is
 		bigger than the logical block size (for instance a drive
 		with 4KB physical sectors exposing 512-byte logical
 		blocks to the operating system).  This parameter
 		indicates how many bytes the beginning of the device is
 		offset from the disk's natural alignment.
 What:		/sys/block/<disk>/discard_alignment
 Date:		May 2011
 Contact:	Martin K. Petersen <martin.petersen@oracle.com>
 Description:
 		Devices that support discard functionality may
 		internally allocate space in units that are bigger than
 		the exported logical block size. The discard_alignment
 		parameter indicates how many bytes the beginning of the
 		device is offset from the internal allocation unit's
 		natural alignment.
 What:		/sys/block/<disk>/diskseq
 Date:		February 2021
 Contact:	Matteo Croce <mcroce@microsoft.com>
 Description:
 		The /sys/block/<disk>/diskseq files reports the disk
 		sequence number, which is a monotonically increasing
 		number assigned to every drive.
 		Some devices, like the loop device, refresh such number
 		every time the backing file is changed.
 		The value type is 64 bit unsigned.
 What:		/sys/block/<disk>/inflight
 Date:		October 2009
 Contact:	Jens Axboe <axboe@kernel.dk>, Nikanth Karthikesan <knikanth@suse.de>
 Description:
 		Reports the number of I/O requests currently in progress
 		(pending / in flight) in a device driver. This can be less
 		than the number of requests queued in the block device queue.
 		The report contains 2 fields: one for read requests
 		and one for write requests.
 		The value type is unsigned int.
 		Cf. Documentation/block/stat.rst which contains a single value for
 		requests in flight.
 		This is related to /sys/block/<disk>/queue/nr_requests
 		and for SCSI device also its queue_depth.
 What:		/sys/block/<disk>/integrity/device_is_integrity_capable
 Date:		July 2014
 Contact:	Martin K. Petersen <martin.petersen@oracle.com>
 Description:
 		Indicates whether a storage device is capable of storing
 		integrity metadata. Set if the device is T10 PI-capable.
 What:		/sys/block/<disk>/integrity/format
 Date:		June 2008
 Contact:	Martin K. Petersen <martin.petersen@oracle.com>
 Description:
 		Metadata format for integrity capable block device.
 		E.g. T10-DIF-TYPE1-CRC.
 What:		/sys/block/<disk>/integrity/protection_interval_bytes
 Date:		July 2015
 Contact:	Martin K. Petersen <martin.petersen@oracle.com>
 Description:
 		Describes the number of data bytes which are protected
 		by one integrity tuple. Typically the device's logical
 		block size.
 What:		/sys/block/<disk>/integrity/read_verify
 Date:		June 2008
 Contact:	Martin K. Petersen <martin.petersen@oracle.com>
 Description:
 		Indicates whether the block layer should verify the
 		integrity of read requests serviced by devices that
 		support sending integrity metadata.
 What:		/sys/block/<disk>/integrity/tag_size
 Date:		June 2008
 Contact:	Martin K. Petersen <martin.petersen@oracle.com>
 Description:
 		Number of bytes of integrity tag space available per
 		512 bytes of data.
 What:		/sys/block/<disk>/integrity/write_generate
 Date:		June 2008
 Contact:	Martin K. Petersen <martin.petersen@oracle.com>
 Description:
 		Indicates whether the block layer should automatically
 		generate checksums for write requests bound for
 		devices that support receiving integrity metadata.
 What:		/sys/block/<disk>/<partition>/alignment_offset
 Date:		April 2009
 Contact:	Martin K. Petersen <martin.petersen@oracle.com>
 Description:
 		Storage devices may report a physical block size that is
 		bigger than the logical block size (for instance a drive
 		with 4KB physical sectors exposing 512-byte logical
 		blocks to the operating system).  This parameter
 		indicates how many bytes the beginning of the partition
 		is offset from the disk's natural alignment.
 What:		/sys/block/<disk>/<partition>/discard_alignment
 Date:		May 2011
 Contact:	Martin K. Petersen <martin.petersen@oracle.com>
 Description:
 		Devices that support discard functionality may
 		internally allocate space in units that are bigger than
 		the exported logical block size. The discard_alignment
 		parameter indicates how many bytes the beginning of the
 		partition is offset from the internal allocation unit's
 		natural alignment.
 What:		/sys/block/<disk>/<partition>/stat
 Date:		February 2008
 Contact:	Jerome Marchand <jmarchan@redhat.com>
 Description:
 		The /sys/block/<disk>/<partition>/stat files display the
 		I/O statistics of partition <partition>. The format is the
 		same as the format of /sys/block/<disk>/stat.
 What:		/sys/block/<disk>/queue/add_random
 Date:		June 2010
 Contact:	linux-block@vger.kernel.org
 Description:
 		[RW] This file allows to turn off the disk entropy contribution.
 		Default value of this file is '1'(on).
 What:		/sys/block/<disk>/queue/chunk_sectors
 Date:		September 2016
 Contact:	Hannes Reinecke <hare@suse.com>
 Description:
 		[RO] chunk_sectors has different meaning depending on the type
 		of the disk. For a RAID device (dm-raid), chunk_sectors
 		indicates the size in 512B sectors of the RAID volume stripe
 		segment. For a zoned block device, either host-aware or
 		host-managed, chunk_sectors indicates the size in 512B sectors
 		of the zones of the device, with the eventual exception of the
 		last zone of the device which may be smaller.
 What:		/sys/block/<disk>/queue/crypto/
 Date:		February 2022
 Contact:	linux-block@vger.kernel.org
 Description:
 		The presence of this subdirectory of /sys/block/<disk>/queue/
 		indicates that the device supports inline encryption.  This
 		subdirectory contains files which describe the inline encryption
 		capabilities of the device.  For more information about inline
 		encryption, refer to Documentation/block/inline-encryption.rst.
 What:		/sys/block/<disk>/queue/crypto/max_dun_bits
 Date:		February 2022
 Contact:	linux-block@vger.kernel.org
 Description:
 		[RO] This file shows the maximum length, in bits, of data unit
 		numbers accepted by the device in inline encryption requests.
 What:		/sys/block/<disk>/queue/crypto/modes/<mode>
 Date:		February 2022
 Contact:	linux-block@vger.kernel.org
 Description:
 		[RO] For each crypto mode (i.e., encryption/decryption
 		algorithm) the device supports with inline encryption, a file
 		will exist at this location.  It will contain a hexadecimal
 		number that is a bitmask of the supported data unit sizes, in
 		bytes, for that crypto mode.
 		Currently, the crypto modes that may be supported are:
 		   * AES-256-XTS
 		   * AES-128-CBC-ESSIV
 		   * Adiantum
 		For example, if a device supports AES-256-XTS inline encryption
 		with data unit sizes of 512 and 4096 bytes, the file
 		/sys/block/<disk>/queue/crypto/modes/AES-256-XTS will exist and
 		will contain "0x1200".
 What:		/sys/block/<disk>/queue/crypto/num_keyslots
 Date:		February 2022
 Contact:	linux-block@vger.kernel.org
 Description:
 		[RO] This file shows the number of keyslots the device has for
 		use with inline encryption.
 What:		/sys/block/<disk>/queue/dax
 Date:		June 2016
 Contact:	linux-block@vger.kernel.org
 Description:
 		[RO] This file indicates whether the device supports Direct
 		Access (DAX), used by CPU-addressable storage to bypass the
 		pagecache.  It shows '1' if true, '0' if not.
 What:		/sys/block/<disk>/queue/discard_granularity
 Date:		May 2011
 Contact:	Martin K. Petersen <martin.petersen@oracle.com>
 Description:
 		[RO] Devices that support discard functionality may internally
 		allocate space using units that are bigger than the logical
 		block size. The discard_granularity parameter indicates the size
 		of the internal allocation unit in bytes if reported by the
 		device. Otherwise the discard_granularity will be set to match
 		the device's physical block size. A discard_granularity of 0
 		means that the device does not support discard functionality.
 What:		/sys/block/<disk>/queue/discard_max_bytes
 Date:		May 2011
 Contact:	Martin K. Petersen <martin.petersen@oracle.com>
 Description:
 		[RW] While discard_max_hw_bytes is the hardware limit for the
 		device, this setting is the software limit. Some devices exhibit
 		large latencies when large discards are issued, setting this
 		value lower will make Linux issue smaller discards and
 		potentially help reduce latencies induced by large discard
 		operations.
 What:		/sys/block/<disk>/queue/discard_max_hw_bytes
 Date:		July 2015
 Contact:	linux-block@vger.kernel.org
 Description:
 		[RO] Devices that support discard functionality may have
 		internal limits on the number of bytes that can be trimmed or
 		unmapped in a single operation.  The `discard_max_hw_bytes`
 		parameter is set by the device driver to the maximum number of
 		bytes that can be discarded in a single operation.  Discard
 		requests issued to the device must not exceed this limit.  A
 		`discard_max_hw_bytes` value of 0 means that the device does not
 		support discard functionality.
 What:		/sys/block/<disk>/queue/discard_zeroes_data
 Date:		May 2011
 Contact:	Martin K. Petersen <martin.petersen@oracle.com>
 Description:
 		[RO] Will always return 0.  Don't rely on any specific behavior
 		for discards, and don't read this file.
 What:		/sys/block/<disk>/queue/dma_alignment
 Date:		May 2022
 Contact:	linux-block@vger.kernel.org
 Description:
 		Reports the alignment that user space addresses must have to be
 		used for raw block device access with O_DIRECT and other driver
 		specific passthrough mechanisms.
 What:		/sys/block/<disk>/queue/fua
 Date:		May 2018
 Contact:	linux-block@vger.kernel.org
 Description:
 		[RO] Whether or not the block driver supports the FUA flag for
 		write requests.  FUA stands for Force Unit Access. If the FUA
 		flag is set that means that write requests must bypass the
 		volatile cache of the storage device.
 What:		/sys/block/<disk>/queue/hw_sector_size
 Date:		January 2008
 Contact:	linux-block@vger.kernel.org
 Description:
 		[RO] This is the hardware sector size of the device, in bytes.
 What:		/sys/block/<disk>/queue/independent_access_ranges/
 Date:		October 2021
 Contact:	linux-block@vger.kernel.org
 Description:
 		[RO] The presence of this sub-directory of the
 		/sys/block/xxx/queue/ directory indicates that the device is
 		capable of executing requests targeting different sector ranges
 		in parallel. For instance, single LUN multi-actuator hard-disks
 		will have an independent_access_ranges directory if the device
 		correctly advertizes the sector ranges of its actuators.
 		The independent_access_ranges directory contains one directory
 		per access range, with each range described using the sector
 		(RO) attribute file to indicate the first sector of the range
 		and the nr_sectors (RO) attribute file to indicate the total
 		number of sectors in the range starting from the first sector of
 		the range.  For example, a dual-actuator hard-disk will have the
 		following independent_access_ranges entries.::
 			$ tree /sys/block/<disk>/queue/independent_access_ranges/
 			/sys/block/<disk>/queue/independent_access_ranges/
 			|-- 0
 			|   |-- nr_sectors
 			|   `-- sector
 			`-- 1
 			    |-- nr_sectors
 			    `-- sector
 		The sector and nr_sectors attributes use 512B sector unit,
 		regardless of the actual block size of the device. Independent
 		access ranges do not overlap and include all sectors within the
 		device capacity. The access ranges are numbered in increasing
 		order of the range start sector, that is, the sector attribute
 		of range 0 always has the value 0.
 What:		/sys/block/<disk>/queue/io_poll
 Date:		November 2015
 Contact:	linux-block@vger.kernel.org
 Description:
 		[RW] When read, this file shows whether polling is enabled (1)
 		or disabled (0).  Writing '0' to this file will disable polling
 		for this device.  Writing any non-zero value will enable this
 		feature.
 What:		/sys/block/<disk>/queue/io_poll_delay
 Date:		November 2016
 Contact:	linux-block@vger.kernel.org
 Description:
 		[RW] If polling is enabled, this controls what kind of polling
 		will be performed. It defaults to -1, which is classic polling.
 		In this mode, the CPU will repeatedly ask for completions
 		without giving up any time.  If set to 0, a hybrid polling mode
 		is used, where the kernel will attempt to make an educated guess
 		at when the IO will complete. Based on this guess, the kernel
 		will put the process issuing IO to sleep for an amount of time,
 		before entering a classic poll loop. This mode might be a little
 		slower than pure classic polling, but it will be more efficient.
 		If set to a value larger than 0, the kernel will put the process
 		issuing IO to sleep for this amount of microseconds before
 		entering classic polling.
 What:		/sys/block/<disk>/queue/io_timeout
 Date:		November 2018
 Contact:	Weiping Zhang <zhangweiping@didiglobal.com>
 Description:
 		[RW] io_timeout is the request timeout in milliseconds. If a
 		request does not complete in this time then the block driver
 		timeout handler is invoked. That timeout handler can decide to
 		retry the request, to fail it or to start a device recovery
 		strategy.
 What:		/sys/block/<disk>/queue/iostats
 Date:		January 2009
 Contact:	linux-block@vger.kernel.org
 Description:
 		[RW] This file is used to control (on/off) the iostats
 		accounting of the disk.
 What:		/sys/block/<disk>/queue/logical_block_size
 Date:		May 2009
 Contact:	Martin K. Petersen <martin.petersen@oracle.com>
 Description:
 		[RO] This is the smallest unit the storage device can address.
 		It is typically 512 bytes.
 What:		/sys/block/<disk>/queue/max_active_zones
 Date:		July 2020
 Contact:	Niklas Cassel <niklas.cassel@wdc.com>
 Description:
 		[RO] For zoned block devices (zoned attribute indicating
 		"host-managed" or "host-aware"), the sum of zones belonging to
 		any of the zone states: EXPLICIT OPEN, IMPLICIT OPEN or CLOSED,
 		is limited by this value. If this value is 0, there is no limit.
 		If the host attempts to exceed this limit, the driver should
 		report this error with BLK_STS_ZONE_ACTIVE_RESOURCE, which user
 		space may see as the EOVERFLOW errno.
 What:		/sys/block/<disk>/queue/max_discard_segments
 Date:		February 2017
 Contact:	linux-block@vger.kernel.org
 Description:
 		[RO] The maximum number of DMA scatter/gather entries in a
 		discard request.
 What:		/sys/block/<disk>/queue/max_hw_sectors_kb
 Date:		September 2004
 Contact:	linux-block@vger.kernel.org
 Description:
 		[RO] This is the maximum number of kilobytes supported in a
 		single data transfer.
 What:		/sys/block/<disk>/queue/max_integrity_segments
 Date:		September 2010
 Contact:	linux-block@vger.kernel.org
 Description:
 		[RO] Maximum number of elements in a DMA scatter/gather list
 		with integrity data that will be submitted by the block layer
 		core to the associated block driver.
 What:		/sys/block/<disk>/queue/max_open_zones
 Date:		July 2020
 Contact:	Niklas Cassel <niklas.cassel@wdc.com>
 Description:
 		[RO] For zoned block devices (zoned attribute indicating
 		"host-managed" or "host-aware"), the sum of zones belonging to
 		any of the zone states: EXPLICIT OPEN or IMPLICIT OPEN, is
 		limited by this value. If this value is 0, there is no limit.
 What:		/sys/block/<disk>/queue/max_sectors_kb
 Date:		September 2004
 Contact:	linux-block@vger.kernel.org
 Description:
 		[RW] This is the maximum number of kilobytes that the block
 		layer will allow for a filesystem request. Must be smaller than
 		or equal to the maximum size allowed by the hardware.
 What:		/sys/block/<disk>/queue/max_segment_size
 Date:		March 2010
 Contact:	linux-block@vger.kernel.org
 Description:
 		[RO] Maximum size in bytes of a single element in a DMA
 		scatter/gather list.
 What:		/sys/block/<disk>/queue/max_segments
 Date:		March 2010
 Contact:	linux-block@vger.kernel.org
 Description:
 		[RO] Maximum number of elements in a DMA scatter/gather list
 		that is submitted to the associated block driver.
 What:		/sys/block/<disk>/queue/minimum_io_size
 Date:		April 2009
 Contact:	Martin K. Petersen <martin.petersen@oracle.com>
 Description:
 		[RO] Storage devices may report a granularity or preferred
 		minimum I/O size which is the smallest request the device can
 		perform without incurring a performance penalty.  For disk
 		drives this is often the physical block size.  For RAID arrays
 		it is often the stripe chunk size.  A properly aligned multiple
 		of minimum_io_size is the preferred request size for workloads
 		where a high number of I/O operations is desired.
 What:		/sys/block/<disk>/queue/nomerges
 Date:		January 2010
 Contact:	linux-block@vger.kernel.org
 Description:
 		[RW] Standard I/O elevator operations include attempts to merge
 		contiguous I/Os. For known random I/O loads these attempts will
 		always fail and result in extra cycles being spent in the
 		kernel. This allows one to turn off this behavior on one of two
 		ways: When set to 1, complex merge checks are disabled, but the
 		simple one-shot merges with the previous I/O request are
 		enabled. When set to 2, all merge tries are disabled. The
 		default value is 0 - which enables all types of merge tries.
 What:		/sys/block/<disk>/queue/nr_requests
 Date:		July 2003
 Contact:	linux-block@vger.kernel.org
 Description:
 		[RW] This controls how many requests may be allocated in the
 		block layer for read or write requests. Note that the total
 		allocated number may be twice this amount, since it applies only
 		to reads or writes (not the accumulated sum).
 		To avoid priority inversion through request starvation, a
 		request queue maintains a separate request pool per each cgroup
 		when CONFIG_BLK_CGROUP is enabled, and this parameter applies to
 		each such per-block-cgroup request pool.  IOW, if there are N
 		block cgroups, each request queue may have up to N request
 		pools, each independently regulated by nr_requests.
 What:		/sys/block/<disk>/queue/nr_zones
 Date:		November 2018
 Contact:	Damien Le Moal <damien.lemoal@wdc.com>
 Description:
 		[RO] nr_zones indicates the total number of zones of a zoned
 		block device ("host-aware" or "host-managed" zone model). For
 		regular block devices, the value is always 0.
 What:		/sys/block/<disk>/queue/optimal_io_size
 Date:		April 2009
 Contact:	Martin K. Petersen <martin.petersen@oracle.com>
 Description:
 		[RO] Storage devices may report an optimal I/O size, which is
 		the device's preferred unit for sustained I/O.  This is rarely
 		reported for disk drives.  For RAID arrays it is usually the
 		stripe width or the internal track size.  A properly aligned
 		multiple of optimal_io_size is the preferred request size for
 		workloads where sustained throughput is desired.  If no optimal
 		I/O size is reported this file contains 0.
 What:		/sys/block/<disk>/queue/physical_block_size
 Date:		May 2009
 Contact:	Martin K. Petersen <martin.petersen@oracle.com>
 Description:
 		[RO] This is the smallest unit a physical storage device can
 		write atomically.  It is usually the same as the logical block
 		size but may be bigger.  One example is SATA drives with 4KB
 		sectors that expose a 512-byte logical block size to the
 		operating system.  For stacked block devices the
 		physical_block_size variable contains the maximum
 		physical_block_size of the component devices.
 What:		/sys/block/<disk>/queue/read_ahead_kb
 Date:		May 2004
 Contact:	linux-block@vger.kernel.org
 Description:
 		[RW] Maximum number of kilobytes to read-ahead for filesystems
 		on this block device.
 What:		/sys/block/<disk>/queue/rotational
 Date:		January 2009
 Contact:	linux-block@vger.kernel.org
 Description:
 		[RW] This file is used to stat if the device is of rotational
 		type or non-rotational type.
 What:		/sys/block/<disk>/queue/rq_affinity
 Date:		September 2008
 Contact:	linux-block@vger.kernel.org
 Description:
 		[RW] If this option is '1', the block layer will migrate request
 		completions to the cpu "group" that originally submitted the
 		request. For some workloads this provides a significant
 		reduction in CPU cycles due to caching effects.
 		For storage configurations that need to maximize distribution of
 		completion processing setting this option to '2' forces the
 		completion to run on the requesting cpu (bypassing the "group"
 		aggregation logic).
 What:		/sys/block/<disk>/queue/scheduler
 Date:		October 2004
 Contact:	linux-block@vger.kernel.org
 Description:
 		[RW] When read, this file will display the current and available
 		IO schedulers for this block device. The currently active IO
 		scheduler will be enclosed in [] brackets. Writing an IO
 		scheduler name to this file will switch control of this block
 		device to that new IO scheduler. Note that writing an IO
 		scheduler name to this file will attempt to load that IO
 		scheduler module, if it isn't already present in the system.
 What:		/sys/block/<disk>/queue/stable_writes
 Date:		September 2020
 Contact:	linux-block@vger.kernel.org
 Description:
 		[RW] This file will contain '1' if memory must not be modified
 		while it is being used in a write request to this device.  When
 		this is the case and the kernel is performing writeback of a
 		page, the kernel will wait for writeback to complete before
 		allowing the page to be modified again, rather than allowing
 		immediate modification as is normally the case.  This
 		restriction arises when the device accesses the memory multiple
 		times where the same data must be seen every time -- for
 		example, once to calculate a checksum and once to actually write
 		the data.  If no such restriction exists, this file will contain
 		'0'.  This file is writable for testing purposes.
 What:		/sys/block/<disk>/queue/throttle_sample_time
 Date:		March 2017
 Contact:	linux-block@vger.kernel.org
 Description:
 		[RW] This is the time window that blk-throttle samples data, in
 		millisecond.  blk-throttle makes decision based on the
 		samplings. Lower time means cgroups have more smooth throughput,
 		but higher CPU overhead. This exists only when
 		CONFIG_BLK_DEV_THROTTLING_LOW is enabled.
 What:		/sys/block/<disk>/queue/virt_boundary_mask
 Date:		April 2021
 Contact:	linux-block@vger.kernel.org
 Description:
 		[RO] This file shows the I/O segment memory alignment mask for
 		the block device.  I/O requests to this device will be split
 		between segments wherever either the memory address of the end
 		of the previous segment or the memory address of the beginning
 		of the current segment is not aligned to virt_boundary_mask + 1
 		bytes.
 What:		/sys/block/<disk>/queue/wbt_lat_usec
 Date:		November 2016
 Contact:	linux-block@vger.kernel.org
 Description:
 		[RW] If the device is registered for writeback throttling, then
 		this file shows the target minimum read latency. If this latency
 		is exceeded in a given window of time (see wb_window_usec), then
 		the writeback throttling will start scaling back writes. Writing
 		a value of '0' to this file disables the feature. Writing a
 		value of '-1' to this file resets the value to the default
 		setting.
 What:		/sys/block/<disk>/queue/write_cache
 Date:		April 2016
 Contact:	linux-block@vger.kernel.org
 Description:
 		[RW] When read, this file will display whether the device has
 		write back caching enabled or not. It will return "write back"
 		for the former case, and "write through" for the latter. Writing
 		to this file can change the kernels view of the device, but it
 		doesn't alter the device state. This means that it might not be
 		safe to toggle the setting from "write back" to "write through",
 		since that will also eliminate cache flushes issued by the
 		kernel.
 What:		/sys/block/<disk>/queue/write_same_max_bytes
 Date:		January 2012
 Contact:	Martin K. Petersen <martin.petersen@oracle.com>
 Description:
 		[RO] Some devices support a write same operation in which a
 		single data block can be written to a range of several
 		contiguous blocks on storage. This can be used to wipe areas on
 		disk or to initialize drives in a RAID configuration.
 		write_same_max_bytes indicates how many bytes can be written in
 		a single write same command. If write_same_max_bytes is 0, write
 		same is not supported by the device.
 What:		/sys/block/<disk>/queue/write_zeroes_max_bytes
 Date:		November 2016
 Contact:	Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>
 Description:
 		[RO] Devices that support write zeroes operation in which a
 		single request can be issued to zero out the range of contiguous
 		blocks on storage without having any payload in the request.
 		This can be used to optimize writing zeroes to the devices.
 		write_zeroes_max_bytes indicates how many bytes can be written
 		in a single write zeroes command. If write_zeroes_max_bytes is
 		0, write zeroes is not supported by the device.
 What:		/sys/block/<disk>/queue/zone_append_max_bytes
 Date:		May 2020
 Contact:	linux-block@vger.kernel.org
 Description:
 		[RO] This is the maximum number of bytes that can be written to
 		a sequential zone of a zoned block device using a zone append
 		write operation (REQ_OP_ZONE_APPEND). This value is always 0 for
 		regular block devices.
 What:		/sys/block/<disk>/queue/zone_write_granularity
 Date:		January 2021
 Contact:	linux-block@vger.kernel.org
 Description:
 		[RO] This indicates the alignment constraint, in bytes, for
 		write operations in sequential zones of zoned block devices
 		(devices with a zoned attributed that reports "host-managed" or
 		"host-aware"). This value is always 0 for regular block devices.
 What:		/sys/block/<disk>/queue/zoned
 Date:		September 2016
 Contact:	Damien Le Moal <damien.lemoal@wdc.com>
 Description:
 		[RO] zoned indicates if the device is a zoned block device and
 		the zone model of the device if it is indeed zoned.  The
 		possible values indicated by zoned are "none" for regular block
 		devices and "host-aware" or "host-managed" for zoned block
 		devices. The characteristics of host-aware and host-managed
 		zoned block devices are described in the ZBC (Zoned Block
 		Commands) and ZAC (Zoned Device ATA Command Set) standards.
 		These standards also define the "drive-managed" zone model.
 		However, since drive-managed zoned block devices do not support
 		zone commands, they will be treated as regular block devices and
 		zoned will report "none".
 What:		/sys/block/<disk>/stat
 Date:		February 2008
 Contact:	Jerome Marchand <jmarchan@redhat.com>
 Description:
 		The /sys/block/<disk>/stat files displays the I/O
 		statistics of disk <disk>. They contain 11 fields:
 		==  ==============================================
 		 1  reads completed successfully
 		 2  reads merged
 		 3  sectors read
 		 4  time spent reading (ms)
 		 5  writes completed
 		 6  writes merged
 		 7  sectors written
 		 8  time spent writing (ms)
 		 9  I/Os currently in progress
 		10  time spent doing I/Os (ms)
 		11  weighted time spent doing I/Os (ms)
 		12  discards completed
 		13  discards merged
 		14  sectors discarded
 		15  time spent discarding (ms)
 		16  flush requests completed
 		17  time spent flushing (ms)
 		==  ==============================================
 		For more details refer Documentation/admin-guide/iostats.rst
--- a/Documentation/ABI/stable/sysfs-bus-mhi
+++ b/Documentation/ABI/stable/sysfs-bus-mhi
@ -19,13 +19,3 @@ Description:	The file holds the OEM PK Hash value of the endpoint device
 		read without having the device power on at least once, the file
 		will read all 0's.
 Users:		Any userspace application or clients interested in device info.
 What:           /sys/bus/mhi/devices/.../soc_reset
 Date:           April 2022
 KernelVersion:  5.19
 Contact:        mhi@lists.linux.dev
 Description:	Initiates a SoC reset on the MHI controller.  A SoC reset is
                a reset of last resort, and will require a complete re-init.
                This can be useful as a method of recovery if the device is
                non-responsive, or as a means of loading new firmware as a
                system administration task.
--- a/Documentation/ABI/stable/sysfs-class-infiniband
+++ b/Documentation/ABI/stable/sysfs-class-infiniband
@ -232,10 +232,10 @@ Description: 	The RoCE type of the associated GID resides at index <gid-index>.
 		or "RoCE v2" for RoCE v2 based GIDs.
-What:		/sys/class/infiniband_mad/umad<N>/ibdev
+What:		/sys/class/infiniband_mad/umadN/ibdev
-What:		/sys/class/infiniband_mad/umad<N>/port
+What:		/sys/class/infiniband_mad/umadN/port
-What:		/sys/class/infiniband_mad/issm<N>/ibdev
+What:		/sys/class/infiniband_mad/issmN/ibdev
-What:		/sys/class/infiniband_mad/issm<N>/port
+What:		/sys/class/infiniband_mad/issmN/port
 Date:		Apr, 2005
 KernelVersion:	v2.6.12
 Contact:	linux-rdma@vger.kernel.org
@ -261,8 +261,8 @@ Description:
 		userspace ABI compatibility of umad & issm devices.
-What:		/sys/class/infiniband_verbs/uverbs<N>/ibdev
+What:		/sys/class/infiniband_verbs/uverbsN/ibdev
-What:		/sys/class/infiniband_verbs/uverbs<N>/abi_version
+What:		/sys/class/infiniband_verbs/uverbsN/abi_version
 Date:		Sept, 2005
 KernelVersion:	v2.6.14
 Contact:	linux-rdma@vger.kernel.org
@ -471,7 +471,7 @@ Description:
 		=============== ======================================================
-What:		/sys/class/infiniband/qibX/ports/<N>/sl2vl/[0-15]
+What:		/sys/class/infiniband/qibX/ports/N/sl2vl/[0-15]
 Date:		May, 2010
 KernelVersion:	v2.6.35
 Contact:	linux-rdma@vger.kernel.org
@ -480,8 +480,8 @@ Description:
 		the Service Level (SL). Listing the SL files returns the Virtual
 		Lane (VL) as programmed by the SL.
-What:		/sys/class/infiniband/qibX/ports/<N>/CCMgtA/cc_settings_bin
+What:		/sys/class/infiniband/qibX/ports/N/CCMgtA/cc_settings_bin
-What:		/sys/class/infiniband/qibX/ports/<N>/CCMgtA/cc_table_bin
+What:		/sys/class/infiniband/qibX/ports/N/CCMgtA/cc_table_bin
 Date:		May, 2010
 KernelVersion:	v2.6.35
 Contact:	linux-rdma@vger.kernel.org
@ -499,11 +499,11 @@ Description:
 				delay.
 		=============== ================================================
-What:		/sys/class/infiniband/qibX/ports/<N>/linkstate/loopback
+What:		/sys/class/infiniband/qibX/ports/N/linkstate/loopback
-What:		/sys/class/infiniband/qibX/ports/<N>/linkstate/led_override
+What:		/sys/class/infiniband/qibX/ports/N/linkstate/led_override
-What:		/sys/class/infiniband/qibX/ports/<N>/linkstate/hrtbt_enable
+What:		/sys/class/infiniband/qibX/ports/N/linkstate/hrtbt_enable
-What:		/sys/class/infiniband/qibX/ports/<N>/linkstate/status
+What:		/sys/class/infiniband/qibX/ports/N/linkstate/status
-What:		/sys/class/infiniband/qibX/ports/<N>/linkstate/status_str
+What:		/sys/class/infiniband/qibX/ports/N/linkstate/status_str
 Date:		May, 2010
 KernelVersion:	v2.6.35
 Contact:	linux-rdma@vger.kernel.org
@ -523,16 +523,16 @@ Description:
 				"Fatal_Hardware_Error".
 		=============== ===============================================
-What:		/sys/class/infiniband/qibX/ports/<N>/diag_counters/rc_resends
+What:		/sys/class/infiniband/qibX/ports/N/diag_counters/rc_resends
-What:		/sys/class/infiniband/qibX/ports/<N>/diag_counters/seq_naks
+What:		/sys/class/infiniband/qibX/ports/N/diag_counters/seq_naks
-What:		/sys/class/infiniband/qibX/ports/<N>/diag_counters/rdma_seq
+What:		/sys/class/infiniband/qibX/ports/N/diag_counters/rdma_seq
-What:		/sys/class/infiniband/qibX/ports/<N>/diag_counters/rnr_naks
+What:		/sys/class/infiniband/qibX/ports/N/diag_counters/rnr_naks
-What:		/sys/class/infiniband/qibX/ports/<N>/diag_counters/other_naks
+What:		/sys/class/infiniband/qibX/ports/N/diag_counters/other_naks
-What:		/sys/class/infiniband/qibX/ports/<N>/diag_counters/rc_timeouts
+What:		/sys/class/infiniband/qibX/ports/N/diag_counters/rc_timeouts
-What:		/sys/class/infiniband/qibX/ports/<N>/diag_counters/look_pkts
+What:		/sys/class/infiniband/qibX/ports/N/diag_counters/look_pkts
-What:		/sys/class/infiniband/qibX/ports/<N>/diag_counters/pkt_drops
+What:		/sys/class/infiniband/qibX/ports/N/diag_counters/pkt_drops
-What:		/sys/class/infiniband/qibX/ports/<N>/diag_counters/dma_wait
+What:		/sys/class/infiniband/qibX/ports/N/diag_counters/dma_wait
-What:		/sys/class/infiniband/qibX/ports/<N>/diag_counters/unaligned
+What:		/sys/class/infiniband/qibX/ports/N/diag_counters/unaligned
 Date:		May, 2010
 KernelVersion:	v2.6.35
 Contact:	linux-rdma@vger.kernel.org
@ -650,9 +650,9 @@ Description:
 		=============== =============================================
-What:		/sys/class/infiniband/hfi1_X/ports/<N>/CCMgtA/cc_settings_bin
+What:		/sys/class/infiniband/hfi1_X/ports/N/CCMgtA/cc_settings_bin
-What:		/sys/class/infiniband/hfi1_X/ports/<N>/CCMgtA/cc_table_bin
+What:		/sys/class/infiniband/hfi1_X/ports/N/CCMgtA/cc_table_bin
-What:		/sys/class/infiniband/hfi1_X/ports/<N>/CCMgtA/cc_prescan
+What:		/sys/class/infiniband/hfi1_X/ports/N/CCMgtA/cc_prescan
 Date:		May, 2016
 KernelVersion:	v4.6
 Contact:	linux-rdma@vger.kernel.org
@ -675,9 +675,9 @@ Description:
 				disable.
 		=============== ================================================
-What:		/sys/class/infiniband/hfi1_X/ports/<N>/sc2vl/[0-31]
+What:		/sys/class/infiniband/hfi1_X/ports/N/sc2vl/[0-31]
-What:		/sys/class/infiniband/hfi1_X/ports/<N>/sl2sc/[0-31]
+What:		/sys/class/infiniband/hfi1_X/ports/N/sl2sc/[0-31]
-What:		/sys/class/infiniband/hfi1_X/ports/<N>/vl2mtu/[0-15]
+What:		/sys/class/infiniband/hfi1_X/ports/N/vl2mtu/[0-15]
 Date:		May, 2016
 KernelVersion:	v4.6
 Contact:	linux-rdma@vger.kernel.org
@ -691,8 +691,8 @@ Description:
 		=============== ===================================================
-What:		/sys/class/infiniband/hfi1_X/sdma_<N>/cpu_list
+What:		/sys/class/infiniband/hfi1_X/sdma_N/cpu_list
-What:		/sys/class/infiniband/hfi1_X/sdma_<N>/vl
+What:		/sys/class/infiniband/hfi1_X/sdma_N/vl
 Date:		Sept, 2016
 KernelVersion:	v4.8
 Contact:	linux-rdma@vger.kernel.org
--- a/Documentation/ABI/stable/sysfs-class-tpm
+++ b/Documentation/ABI/stable/sysfs-class-tpm
@ -195,7 +195,7 @@ Description:	The "tpm_version_major" property shows the TCG spec major version
 		  2
-What:		/sys/class/tpm/tpmX/pcr-<H>/<N>
+What:		/sys/class/tpm/tpmX/pcr-H/N
 Date:		March 2021
 KernelVersion:	5.12
 Contact:	linux-integrity@vger.kernel.org
--- a/Documentation/ABI/stable/sysfs-devices
+++ b/Documentation/ABI/stable/sysfs-devices
@ -23,10 +23,3 @@ Contact:	Device Tree mailing list <devicetree@vger.kernel.org>
 Description:
 		If CONFIG_OF is enabled, then this file is present. When
 		read, it returns full name of the device node.
 What:		/sys/devices/*/dev
 Date:		Jun 2006
 Contact:	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
 Description:
 		Major and minor numbers of the character device corresponding
 		to the device (in <major>:<minor> format).
--- a/Documentation/ABI/stable/sysfs-devices-node
+++ b/Documentation/ABI/stable/sysfs-devices-node
@ -176,9 +176,3 @@ Contact:	Keith Busch <keith.busch@intel.com>
 Description:
 		The cache write policy: 0 for write-back, 1 for write-through,
 		other or unknown.
 What:		/sys/devices/system/node/nodeX/x86/sgx_total_bytes
 Date:		November 2021
 Contact:	Jarkko Sakkinen <jarkko@kernel.org>
 Description:
 		The total amount of SGX physical memory in bytes.
--- a/Documentation/ABI/stable/sysfs-devices-system-cpu
+++ b/Documentation/ABI/stable/sysfs-devices-system-cpu
@ -42,12 +42,6 @@ Description:    the CPU core ID of cpuX. Typically it is the hardware platform's
                architecture and platform dependent.
 Values:         integer
 What:           /sys/devices/system/cpu/cpuX/topology/cluster_id
 Description:    the cluster ID of cpuX.  Typically it is the hardware platform's
                identifier (rather than the kernel's). The actual value is
                architecture and platform dependent.
 Values:         integer
 What:           /sys/devices/system/cpu/cpuX/topology/book_id
 Description:    the book ID of cpuX. Typically it is the hardware platform's
                identifier (rather than the kernel's). The actual value is
@ -86,24 +80,11 @@ What:           /sys/devices/system/cpu/cpuX/topology/die_cpus
 Description:    internal kernel map of CPUs within the same die.
 Values:         hexadecimal bitmask.
 What:           /sys/devices/system/cpu/cpuX/topology/ppin
 Description:    per-socket protected processor inventory number
 Values:         hexadecimal.
 What:           /sys/devices/system/cpu/cpuX/topology/die_cpus_list
 Description:    human-readable list of CPUs within the same die.
                The format is like 0-3, 8-11, 14,17.
 Values:         decimal list.
 What:           /sys/devices/system/cpu/cpuX/topology/cluster_cpus
 Description:    internal kernel map of CPUs within the same cluster.
 Values:         hexadecimal bitmask.
 What:           /sys/devices/system/cpu/cpuX/topology/cluster_cpus_list
 Description:    human-readable list of CPUs within the same cluster.
                The format is like 0-3, 8-11, 14,17.
 Values:         decimal list.
 What:           /sys/devices/system/cpu/cpuX/topology/book_siblings
 Description:    internal kernel map of cpuX's hardware threads within the same
                book_id. it's only used on s390.
--- a/Documentation/ABI/stable/sysfs-driver-dma-idxd
+++ b/Documentation/ABI/stable/sysfs-driver-dma-idxd
@ -41,14 +41,14 @@ KernelVersion:  5.6.0
 Contact:        dmaengine@vger.kernel.org
 Description:    The maximum number of groups can be created under this device.
-What:           /sys/bus/dsa/devices/dsa<m>/max_read_buffers
+What:           /sys/bus/dsa/devices/dsa<m>/max_tokens
-Date:           Dec 10, 2021
+Date:           Oct 25, 2019
-KernelVersion:  5.17.0
+KernelVersion:  5.6.0
 Contact:        dmaengine@vger.kernel.org
-Description:    The total number of read buffers supported by this device.
+Description:    The total number of bandwidth tokens supported by this device.
-		The read buffers represent resources within the DSA
+		The bandwidth tokens represent resources within the DSA
 		implementation, and these resources are allocated by engines to
-		support operations. See DSA spec v1.2 9.2.4 Total Read Buffers.
+		support operations.
 What:           /sys/bus/dsa/devices/dsa<m>/max_transfer_size
 Date:           Oct 25, 2019
@ -115,13 +115,13 @@ KernelVersion:  5.6.0
 Contact:        dmaengine@vger.kernel.org
 Description:    To indicate if this device is configurable or not.
-What:           /sys/bus/dsa/devices/dsa<m>/read_buffer_limit
+What:           /sys/bus/dsa/devices/dsa<m>/token_limit
-Date:           Dec 10, 2021
+Date:           Oct 25, 2019
-KernelVersion:  5.17.0
+KernelVersion:  5.6.0
 Contact:        dmaengine@vger.kernel.org
-Description:    The maximum number of read buffers that may be in use at
+Description:    The maximum number of bandwidth tokens that may be in use at
 		one time by operations that access low bandwidth memory in the
-		device. See DSA spec v1.2 9.2.8 GENCFG on Global Read Buffer Limit.
+		device.
 What:		/sys/bus/dsa/devices/dsa<m>/cmd_status
 Date:		Aug 28, 2020
@ -220,73 +220,8 @@ Contact:	dmaengine@vger.kernel.org
 Description:	Show the current number of entries in this WQ if WQ Occupancy
 		Support bit WQ capabilities is 1.
 What:		/sys/bus/dsa/devices/wq<m>.<n>/enqcmds_retries
 Date		Oct 29, 2021
 KernelVersion:	5.17.0
 Contact:	dmaengine@vger.kernel.org
 Description:	Indicate the number of retires for an enqcmds submission on a sharedwq.
 		A max value to set attribute is capped at 64.
 What:		/sys/bus/dsa/devices/wq<m>.<n>/op_config
 Date:		Sept 14, 2022
 KernelVersion:	6.0.0
 Contact:	dmaengine@vger.kernel.org
 Description:	Shows the operation capability bits displayed in bitmap format
 		presented by %*pb printk() output format specifier.
 		The attribute can be configured when the WQ is disabled in
 		order to configure the WQ to accept specific bits that
 		correlates to the operations allowed. It's visible only
 		on platforms that support the capability.
 What:           /sys/bus/dsa/devices/engine<m>.<n>/group_id
 Date:           Oct 25, 2019
 KernelVersion:  5.6.0
 Contact:        dmaengine@vger.kernel.org
 Description:    The group that this engine belongs to.
 What:		/sys/bus/dsa/devices/group<m>.<n>/use_read_buffer_limit
 Date:		Dec 10, 2021
 KernelVersion:	5.17.0
 Contact:	dmaengine@vger.kernel.org
 Description:	Enable the use of global read buffer limit for the group. See DSA
 		spec v1.2 9.2.18 GRPCFG Use Global Read Buffer Limit.
 What:		/sys/bus/dsa/devices/group<m>.<n>/read_buffers_allowed
 Date:		Dec 10, 2021
 KernelVersion:	5.17.0
 Contact:	dmaengine@vger.kernel.org
 Description:	Indicates max number of read buffers that may be in use at one time
 		by all engines in the group. See DSA spec v1.2 9.2.18 GRPCFG Read
 		Buffers Allowed.
 What:		/sys/bus/dsa/devices/group<m>.<n>/read_buffers_reserved
 Date:		Dec 10, 2021
 KernelVersion:	5.17.0
 Contact:	dmaengine@vger.kernel.org
 Description:	Indicates the number of Read Buffers reserved for the use of
 		engines in the group. See DSA spec v1.2 9.2.18 GRPCFG Read Buffers
 		Reserved.
 What:		/sys/bus/dsa/devices/group<m>.<n>/desc_progress_limit
 Date:		Sept 14, 2022
 KernelVersion:	6.0.0
 Contact:	dmaengine@vger.kernel.org
 Description:	Allows control of the number of work descriptors that can be
 		concurrently processed by an engine in the group as a fraction
 		of the Maximum Work Descriptors in Progress value specified in
 		the ENGCAP register. The acceptable values are 0 (default),
 		1 (1/2 of max value), 2 (1/4 of the max value), and 3 (1/8 of
 		the max value). It's visible only on platforms that support
 		the capability.
 What:		/sys/bus/dsa/devices/group<m>.<n>/batch_progress_limit
 Date:		Sept 14, 2022
 KernelVersion:	6.0.0
 Contact:	dmaengine@vger.kernel.org
 Description:	Allows control of the number of batch descriptors that can be
 		concurrently processed by an engine in the group as a fraction
 		of the Maximum Batch Descriptors in Progress value specified in
 		the ENGCAP register. The acceptable values are 0 (default),
 		1 (1/2 of max value), 2 (1/4 of the max value), and 3 (1/8 of
 		the max value). It's visible only on platforms that support
 		the capability.
--- a/Documentation/ABI/stable/sysfs-driver-firmware-zynqmp
+++ b/Documentation/ABI/stable/sysfs-driver-firmware-zynqmp
@ -113,144 +113,3 @@ Description:
 		    # echo 0 > /sys/devices/platform/firmware\:zynqmp-firmware/health_status
 Users:		Xilinx
 What:		/sys/devices/platform/firmware\:zynqmp-firmware/feature_config_id
 Date:		Feb 2022
 KernelVersion:	5.18
 Contact:	"Ronak Jain" <ronak.jain@xilinx.com>
 Description:
 		This sysfs interface allows user to configure features at
 		runtime. The user can enable or disable features running at
 		firmware as well as the user can configure the parameters of
 		the features at runtime. The supported features are over
 		temperature and external watchdog. Here, the external watchdog
 		is completely different than the /dev/watchdog as the external
 		watchdog is running on the firmware and it is used to monitor
 		the health of firmware not APU(Linux). Also, the external
 		watchdog is interfaced outside of the zynqmp soc.
 		The supported config ids are for the feature configuration is,
 		1. PM_FEATURE_OVERTEMP_STATUS = 1, the user can enable or
 		disable the over temperature feature.
 		2. PM_FEATURE_OVERTEMP_VALUE = 2, the user can configure the
 		over temperature limit in Degree Celsius.
 		3. PM_FEATURE_EXTWDT_STATUS = 3, the user can enable or disable
 		the external watchdog feature.
 		4. PM_FEATURE_EXTWDT_VALUE = 4, the user can configure the
 		external watchdog feature.
 		Usage:
 		Select over temperature config ID to enable/disable feature
 		# echo 1 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_id
 		Check over temperature config ID is selected or not
 		# cat /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_id
 		The expected result is 1.
 		Select over temperature config ID to configure OT limit
 		# echo 2 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_id
 		Check over temperature config ID is selected or not
 		# cat /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_id
 		The expected result is 2.
 		Select external watchdog config ID to enable/disable feature
 		# echo 3 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_id
 		Check external watchdog config ID is selected or not
 		# cat /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_id
 		The expected result is 3.
 		Select external watchdog config ID to configure time interval
 		# echo 4 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_id
 		Check external watchdog config ID is selected or not
 		# cat /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_id
 		The expected result is 4.
 Users:		Xilinx
 What:		/sys/devices/platform/firmware\:zynqmp-firmware/feature_config_value
 Date:		Feb 2022
 KernelVersion:	5.18
 Contact:	"Ronak Jain" <ronak.jain@xilinx.com>
 Description:
 		This sysfs interface allows to configure features at runtime.
 		The user can enable or disable features running at firmware.
 		Also, the user can configure the parameters of the features
 		at runtime. The supported features are over temperature and
 		external watchdog. Here, the external watchdog is completely
 		different than the /dev/watchdog as the external watchdog is
 		running on the firmware and it is used to monitor the health
 		of firmware not APU(Linux). Also, the external watchdog is
 		interfaced outside of the zynqmp soc.
 		By default the features are disabled in the firmware. The user
 		can enable features by querying appropriate config id of the
 		features.
 		The default limit for the over temperature is 90 Degree Celsius.
 		The default timer interval for the external watchdog is 570ms.
 		The supported config ids are for the feature configuration is,
 		1. PM_FEATURE_OVERTEMP_STATUS = 1, the user can enable or
 		disable the over temperature feature.
 		2. PM_FEATURE_OVERTEMP_VALUE = 2, the user can configure the
 		over temperature limit in Degree Celsius.
 		3. PM_FEATURE_EXTWDT_STATUS = 3, the user can enable or disable
 		the external watchdog feature.
 		4. PM_FEATURE_EXTWDT_VALUE = 4, the user can configure the
 		external watchdog feature.
 		Usage:
 		Enable over temperature feature
 		# echo 1 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_id
 		# echo 1 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_value
 		Check whether the over temperature feature is enabled or not
 		# cat /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_value
 		The expected result is 1.
 		Disable over temperature feature
 		# echo 1 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_id
 		# echo 0 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_value
 		Check whether the over temperature feature is disabled or not
 		# cat /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_value
 		The expected result is 0.
 		Configure over temperature limit to 50 Degree Celsius
 		# echo 2 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_id
 		# echo 50 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_value
 		Check whether the over temperature limit is configured or not
 		# cat /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_value
 		The expected result is 50.
 		Enable external watchdog feature
 		# echo 3 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_id
 		# echo 1 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_value
 		Check whether the external watchdog feature is enabled or not
 		# cat /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_value
 		The expected result is 1.
 		Disable external watchdog feature
 		# echo 3 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_id
 		# echo 0 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_value
 		Check whether the external watchdog feature is disabled or not
 		# cat /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_value
 		The expected result is 0.
 		Configure external watchdog timer interval to 500ms
 		# echo 4 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_id
 		# echo 500 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_value
 		Check whether the external watchdog timer interval is configured or not
 		# cat /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_value
 		The expected result is 500.
 Users:		Xilinx
--- a/Documentation/ABI/stable/sysfs-driver-mlxreg-io
+++ b/Documentation/ABI/stable/sysfs-driver-mlxreg-io
@ -1,7 +1,7 @@
 What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/asic_health
 Date:		June 2018
 KernelVersion:	4.19
-Contact:	Vadim Pasternak <vadimp@nvidia.com>
+Contact:	Vadim Pasternak <vadimpmellanox.com>
 Description:	This file shows ASIC health status. The possible values are:
 		0 - health failed, 2 - health OK, 3 - ASIC in booting state.
@ -11,7 +11,7 @@ What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/cpld1_version
 What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/cpld2_version
 Date:		June 2018
 KernelVersion:	4.19
-Contact:	Vadim Pasternak <vadimp@nvidia.com>
+Contact:	Vadim Pasternak <vadimpmellanox.com>
 Description:	These files show with which CPLD versions have been burned
 		on carrier and switch boards.
@ -20,7 +20,7 @@ Description:	These files show with which CPLD versions have been burned
 What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/fan_dir
 Date:		December 2018
 KernelVersion:	5.0
-Contact:	Vadim Pasternak <vadimp@nvidia.com>
+Contact:	Vadim Pasternak <vadimpmellanox.com>
 Description:	This file shows the system fans direction:
 		forward direction - relevant bit is set 0;
 		reversed direction - relevant bit is set 1.
@ -30,7 +30,7 @@ Description:	This file shows the system fans direction:
 What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/cpld3_version
 Date:		November 2018
 KernelVersion:	5.0
-Contact:	Vadim Pasternak <vadimp@nvidia.com>
+Contact:	Vadim Pasternak <vadimpmellanox.com>
 Description:	These files show with which CPLD versions have been burned
 		on LED or Gearbox board.
@ -39,7 +39,7 @@ Description:	These files show with which CPLD versions have been burned
 What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/jtag_enable
 Date:		November 2018
 KernelVersion:	5.0
-Contact:	Vadim Pasternak <vadimp@nvidia.com>
+Contact:	Vadim Pasternak <vadimpmellanox.com>
 Description:	These files enable and disable the access to the JTAG domain.
 		By default access to the JTAG domain is disabled.
@ -48,7 +48,7 @@ Description:	These files enable and disable the access to the JTAG domain.
 What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/select_iio
 Date:		June 2018
 KernelVersion:	4.19
-Contact:	Vadim Pasternak <vadimp@nvidia.com>
+Contact:	Vadim Pasternak <vadimpmellanox.com>
 Description:	This file allows iio devices selection.
 		Attribute select_iio can be written with 0 or with 1. It
@ -62,7 +62,7 @@ What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/psu1_on
 		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/pwr_down
 Date:		June 2018
 KernelVersion:	4.19
-Contact:	Vadim Pasternak <vadimp@nvidia.com>
+Contact:	Vadim Pasternak <vadimpmellanox.com>
 Description:	These files allow asserting system power cycling, switching
 		power supply units on and off and system's main power domain
 		shutdown.
@ -89,7 +89,7 @@ What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/reset_short_pb
 What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/reset_sw_reset
 Date:		June 2018
 KernelVersion:	4.19
-Contact:	Vadim Pasternak <vadimp@nvidia.com>
+Contact:	Vadim Pasternak <vadimpmellanox.com>
 Description:	These files show the system reset cause, as following: power
 		auxiliary outage or power refresh, ASIC thermal shutdown, halt,
 		hotswap, watchdog, firmware reset, long press power button,
@ -106,7 +106,7 @@ What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/reset_system
 What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/reset_voltmon_upgrade_fail
 Date:		November 2018
 KernelVersion:	5.0
-Contact:	Vadim Pasternak <vadimp@nvidia.com>
+Contact:	Vadim Pasternak <vadimpmellanox.com>
 Description:	These files show the system reset cause, as following: ComEx
 		power fail, reset from ComEx, system platform reset, reset
 		due to voltage monitor devices upgrade failure,
@ -119,7 +119,7 @@ Description:	These files show the system reset cause, as following: ComEx
 What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/cpld4_version
 Date:		November 2018
 KernelVersion:	5.0
-Contact:	Vadim Pasternak <vadimp@nvidia.com>
+Contact:	Vadim Pasternak <vadimpmellanox.com>
 Description:	These files show with which CPLD versions have been burned
 		on LED board.
@ -133,7 +133,7 @@ What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/reset_sff_wd
 What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/reset_swb_wd
 Date:		June 2019
 KernelVersion:	5.3
-Contact:	Vadim Pasternak <vadimp@nvidia.com>
+Contact:	Vadim Pasternak <vadimpmellanox.com>
 Description:	These files show the system reset cause, as following:
 		COMEX thermal shutdown; wathchdog power off or reset was derived
 		by one of the next components: COMEX, switch board or by Small Form
@ -148,7 +148,7 @@ What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/config1
 What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/config2
 Date:		January 2020
 KernelVersion:	5.6
-Contact:	Vadim Pasternak <vadimp@nvidia.com>
+Contact:	Vadim Pasternak <vadimpmellanox.com>
 Description:	These files show system static topology identification
 		like system's static I2C topology, number and type of FPGA
 		devices within the system and so on.
@ -161,7 +161,7 @@ What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/reset_soc
 What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/reset_sw_pwr_off
 Date:		January 2020
 KernelVersion:	5.6
-Contact:	Vadim Pasternak <vadimp@nvidia.com>
+Contact:	Vadim Pasternak <vadimpmellanox.com>
 Description:	These files show the system reset causes, as following: reset
 		due to AC power failure, reset invoked from software by
 		assertion reset signal through CPLD. reset caused by signal
@ -173,7 +173,7 @@ Description:	These files show the system reset causes, as following: reset
 What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/pcie_asic_reset_dis
 Date:		January 2020
 KernelVersion:	5.6
-Contact:	Vadim Pasternak <vadimp@nvidia.com>
+Contact:	Vadim Pasternak <vadimpmellanox.com>
 Description:	This file allows to retain ASIC up during PCIe root complex
 		reset, when attribute is set 1.
@ -182,7 +182,7 @@ Description:	This file allows to retain ASIC up during PCIe root complex
 What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/vpd_wp
 Date:		January 2020
 KernelVersion:	5.6
-Contact:	Vadim Pasternak <vadimp@nvidia.com>
+Contact:	Vadim Pasternak <vadimpmellanox.com>
 Description:	This file allows to overwrite system VPD hardware write
 		protection when attribute is set 1.
@ -191,7 +191,7 @@ Description:	This file allows to overwrite system VPD hardware write
 What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/voltreg_update_status
 Date:		January 2020
 KernelVersion:	5.6
-Contact:	Vadim Pasternak <vadimp@nvidia.com>
+Contact:	Vadim Pasternak <vadimpmellanox.com>
 Description:	This file exposes the configuration update status of burnable
 		voltage regulator devices. The status values are as following:
 		0 - OK; 1 - CRC failure; 2 = I2C failure; 3 - in progress.
@ -201,7 +201,7 @@ Description:	This file exposes the configuration update status of burnable
 What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/ufm_version
 Date:		January 2020
 KernelVersion:	5.6
-Contact:	Vadim Pasternak <vadimp@nvidia.com>
+Contact:	Vadim Pasternak <vadimpmellanox.com>
 Description:	This file exposes the firmware version of burnable voltage
 		regulator devices.
@ -217,328 +217,9 @@ What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/cpld3_version_min
 What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/cpld4_version_min
 Date:		July 2020
 KernelVersion:	5.9
-Contact:	Vadim Pasternak <vadimp@nvidia.com>
+Contact:	Vadim Pasternak <vadimpmellanox.com>
 Description:	These files show with which CPLD part numbers and minor
 		versions have been burned CPLD devices equipped on a
 		system.
 		The files are read only.
 What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/bios_active_image
 What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/bios_auth_fail
 What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/bios_upgrade_fail
 Date:		October 2021
 KernelVersion:	5.16
 Contact:	Vadim Pasternak <vadimp@nvidia.com>
 Description:	The files represent BIOS statuses:
 		bios_active_image: location of current active BIOS image:
 		0: Top, 1: Bottom.
 		The reported value should correspond to value expected by OS
 		in case of BIOS safe mode is 0. This bit is related to Intel
 		top-swap feature of DualBios on the same flash.
 		bios_auth_fail: BIOS upgrade is failed because provided BIOS
 		image is not signed correctly.
 		bios_upgrade_fail: BIOS upgrade is failed by some other
 		reason not because authentication. For example due to
 		physical SPI flash problem.
 		The files are read only.
 What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc1_enable
 What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc2_enable
 What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc3_enable
 What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc4_enable
 What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc5_enable
 What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc6_enable
 What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc7_enable
 What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc8_enable
 Date:		October 2021
 KernelVersion:	5.16
 Contact:	Vadim Pasternak <vadimp@nvidia.com>
 Description:	These files allow line cards enable state control.
 		Expected behavior:
 		When  lc{n}_enable is written 1, related line card is released
 		from the reset state, when 0 - is hold in reset state.
 		The files are read/write.
 What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc1_pwr
 What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc2_pwr
 What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc3_pwr
 What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc4_pwr
 What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc5_pwr
 What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc6_pwr
 What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc7_pwr
 What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc8_pwr
 Date:		October 2021
 KernelVersion:	5.16
 Contact:	Vadim Pasternak <vadimp@nvidia.com>
 Description:	These files switching line cards power on and off.
 		Expected behavior:
 		When  lc{n}_pwr is written 1, related line card is powered
 		on, when written 0 - powered off.
 		The files are read/write.
 What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc1_rst_mask
 What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc2_rst_mask
 What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc3_rst_mask
 What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc4_rst_mask
 What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc5_rst_mask
 What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc6_rst_mask
 What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc7_rst_mask
 What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc8_rst_mask
 Date:		October 2021
 KernelVersion:	5.16
 Contact:	Vadim Pasternak <vadimp@nvidia.com>
 Description:	These files clear line card reset bit enforced by ASIC, when it
 		sets it due to some abnormal ASIC behavior.
 		Expected behavior:
 		When lc{n}_rst_mask is written 1, related line card reset bit
 		is cleared, when written 0 - no effect.
 		The files are write only.
 What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/os_started
 Date:		October 2021
 KernelVersion:	5.16
 Contact:	Vadim Pasternak <vadimp@nvidia.com>
 Description:	This file, when written 1, indicates to programmable devices
 		that OS is taking control over it.
 		The file is read/write.
 What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/pm_mgmt_en
 Date:		October 2021
 KernelVersion:	5.16
 Contact:	Vadim Pasternak <vadimp@nvidia.com>
 Description:	This file assigns power management control ownership.
 		When power management control is provided by hardware, hardware
 		will automatically power off one or more line previously
 		powered line cards in case system power budget is getting
 		insufficient. It could be in case when some of power units lost
 		power good state.
 		When pm_mgmt_en is written 1, power management control by
 		software is enabled, 0 - power management control by hardware.
 		Note that for any setting of pm_mgmt_en attribute hardware will
 		not allow to power on any new line card in case system power
 		budget is insufficient.
 		Same in case software will try to power on several line cards
 		at once - hardware will power line cards while system has
 		enough power budget.
 		Default is 0.
 		The file is read/write.
 What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/psu3_on
 What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/psu4_on
 Date:		October 2021
 KernelVersion:	5.16
 Contact:	Vadim Pasternak <vadimp@nvidia.com>
 Description:	These files switching power supply units on and off.
 		Expected behavior:
 		When  psu3_on or psu4_on is written 1, related unit will be
 		disconnected from the power source, when written 0 - connected.
 		The files are write only.
 What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/shutdown_unlock
 Date:		October 2021
 KernelVersion:	5.16
 Contact:	Vadim Pasternak <vadimp@nvidia.com>
 Description:	This file allows to unlock ASIC after thermal shutdown event.
 		When system thermal shutdown is enforced by ASIC, ASIC is
 		getting locked and after system boot it will not be available.
 		Software can decide to unlock it by setting this attribute to
 		1 and then perform system power cycle by setting pwr_cycle
 		attribute to 1 (power cycle of main power domain).
 		Before setting shutdown_unlock to 1 it is recommended to
 		validate that system reboot cause is reset_asic_thermal or
 		reset_thermal_spc_or_pciesw.
 		In case shutdown_unlock is not set 1, the only way to release
 		ASIC from locking - is full system power cycle through the
 		external power distribution unit.
 		Default is 1.
 		The file is read/write.
 What:		/sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/cpld1_pn
 What:		/sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/cpld1_version
 What:		/sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/cpld1_version_min
 Date:		October 2021
 KernelVersion:	5.16
 Contact:	Vadim Pasternak <vadimp@nvidia.com>
 Description:	These files show with which CPLD major and minor versions
 		and part number has been burned CPLD device on line card.
 		The files are read only.
 What:		/sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/fpga1_pn
 What:		/sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/fpga1_version
 What:		/sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/fpga1_version_min
 Date:		October 2021
 KernelVersion:	5.16
 Contact:	Vadim Pasternak <vadimp@nvidia.com>
 Description:	These files show with which FPGA major and minor versions
 		and part number has been burned FPGA device on line card.
 		The files are read only.
 What:		/sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/vpd_wp
 Date:		October 2021
 KernelVersion:	5.16
 Contact:	Vadim Pasternak <vadimp@nvidia.com>
 Description:	This file allow to overwrite line card VPD hardware write
 		protection mode. When attribute is set 1 - write protection is
 		disabled, when 0 - enabled.
 		Default is 0.
 		If the system is in locked-down mode writing this file will not
 		be allowed.
 		The purpose if this file is to allow line card VPD burning
 		during production flow.
 		The file is read/write.
 What:		/sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/reset_aux_pwr_or_ref
 What:		/sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/reset_dc_dc_pwr_fail
 What:		/sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/reset_fpga_not_done
 What:		/sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/reset_from_chassis
 What:		/sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/reset_line_card
 What:		/sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/reset_pwr_off_from_chassis
 Date:		October 2021
 KernelVersion:	5.16
 Contact:	Vadim Pasternak <vadimp@nvidia.com>
 Description:	These files show the line reset cause, as following: power
 		auxiliary outage or power refresh, DC-to-DC power failure, FPGA reset
 		failed, line card reset failed, power off from chassis.
 		Value 1 in file means this is reset cause, 0 - otherwise. Only one of
 		the above causes could be 1 at the same time, representing only last
 		reset cause.
 		The files are read only.
 What:		/sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/cpld_upgrade_en
 What:		/sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/fpga_upgrade_en
 Date:		October 2021
 KernelVersion:	5.16
 Contact:	Vadim Pasternak <vadimp@nvidia.com>
 Description:	These files allow CPLD and FPGA burning. Value 1 in file means burning
 		is enabled, 0 - otherwise.
 		If the system is in locked-down mode writing these files will
 		not be allowed.
 		The purpose of these files to allow line card CPLD and FPGA
 		upgrade through the JTAG daisy-chain.
 		The files are read/write.
 What:		/sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/qsfp_pwr_en
 What:		/sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/pwr_en
 Date:		October 2021
 KernelVersion:	5.16
 Contact:	Vadim Pasternak <vadimp@nvidia.com>
 Description:	These files allow to power on/off all QSFP ports and whole line card.
 		The attributes are set 1 for power on, 0 - for power off.
 		The files are read/write.
 What:		/sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/agb_spi_burn_en
 What:		/sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/fpga_spi_burn_en
 Date:		October 2021
 KernelVersion:	5.16
 Contact:	Vadim Pasternak <vadimp@nvidia.com>
 Description:	These files allow gearboxes and FPGA SPI flash burning.
 		The attributes are set 1 to enable burning, 0 - to disable.
 		If the system is in locked-down mode writing these files will
 		not be allowed.
 		The purpose of these files to allow line card Gearboxes and FPGA
 		burning during production flow.
 		The file is read/write.
 What:		/sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/max_power
 What:		/sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/config
 Date:		October 2021
 KernelVersion:	5.16
 Contact:	Vadim Pasternak <vadimp@nvidia.com>
 Description:	These files provide the maximum powered required for line card
 		feeding and line card configuration Id.
 		The files are read only.
 What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/phy_reset
 Date:		May 2022
 KernelVersion:	5.19
 Contact:	Vadim Pasternak <vadimp@nvidia.com>
 Description:	This file allows to reset PHY 88E1548 when attribute is set 0
 		due to some abnormal PHY behavior.
 		Expected behavior:
 		When phy_reset is written 1, all PHY 88E1548 are released
 		from the reset state, when 0 - are hold in reset state.
 		The files are read/write.
 What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/mac_reset
 Date:		May 2022
 KernelVersion:	5.19
 Contact:	Vadim Pasternak <vadimp@nvidia.com>
 Description:	This file allows to reset ASIC MT52132 when attribute is set 0
 		due to some abnormal ASIC behavior.
 		Expected behavior:
 		When mac_reset is written 1, the ASIC MT52132 is released
 		from the reset state, when 0 - is hold in reset state.
 		The files are read/write.
 What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/qsfp_pwr_good
 Date:		May 2022
 KernelVersion:	5.19
 Contact:	Vadim Pasternak <vadimp@nvidia.com>
 Description:	This file shows QSFP ports power status. The value is set to 0
 		when one of any QSFP ports is plugged. The value is set to 1 when
 		there are no any QSFP ports are plugged.
 		The possible values are:
 		0 - Power good, 1 - Not power good.
 		The files are read only.
 What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/asic2_health
 Date:		July 2022
 KernelVersion:	5.20
 Contact:	Vadim Pasternak <vadimp@nvidia.com>
 Description:	This file shows 2-nd ASIC health status. The possible values are:
 		0 - health failed, 2 - health OK, 3 - ASIC in booting state.
 		The file is read only.
 What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/asic_reset
 What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/asic2_reset
 Date:		July 2022
 KernelVersion:	5.20
 Contact:	Vadim Pasternak <vadimp@nvidia.com>
 Description:	These files allow to each of ASICs by writing 1.
 		The files are write only.
 What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/comm_chnl_ready
 Date:		July 2022
 KernelVersion:	5.20
 Contact:	Vadim Pasternak <vadimp@nvidia.com>
 Description:	This file is used to indicate remote end (for example BMC) that system
 	        host CPU is ready for sending telemetry data to remote end.
 		For indication the file should be written 1.
 		The file is write only.
 What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/config3
 Date:		January 2020
 KernelVersion:	5.6
 Contact:	Vadim Pasternak <vadimp@nvidia.com>
 Description:	The file indicates COME module hardware configuration.
 		The value is pushed by hardware through GPIO pins.
 		The purpose is to expose some minor BOM changes for the same system SKU.
 		The file is read only.
--- a/Documentation/ABI/stable/sysfs-module
+++ b/Documentation/ABI/stable/sysfs-module
@ -1,7 +1,8 @@
-The /sys/module tree consists of the following structure:
+What:		/sys/module
 What:		/sys/module/<MODULENAME>
 Description:
 	The /sys/module tree consists of the following structure:
 	/sys/module/MODULENAME
 		The name of the module that is in the kernel.  This
 		module name will always show up if the module is loaded as a
 		dynamic module.  If it is built directly into the kernel, it
@ -11,8 +12,7 @@ Description:
 		Note: The conditions of creation in the built-in case are not
 		by design and may be removed in the future.
-What:		/sys/module/<MODULENAME>/parameters
+	/sys/module/MODULENAME/parameters
 Description:
 		This directory contains individual files that are each
 		individual parameters of the module that are able to be
 		changed at runtime.  See the individual module
@ -25,23 +25,10 @@ Description:
 		individual driver documentation for details as to the
 		stability of the different parameters.
-What:		/sys/module/<MODULENAME>/refcnt
+	/sys/module/MODULENAME/refcnt
 Description:
 		If the module is able to be unloaded from the kernel, this file
 		will contain the current reference count of the module.
 		Note: If the module is built into the kernel, or if the
 		CONFIG_MODULE_UNLOAD kernel configuration value is not enabled,
 		this file will not be present.
 What:		/sys/module/<MODULENAME>/srcversion
 Date:		Jun 2005
 Description:
 		If the module source has MODULE_VERSION, this file will contain
 		the checksum of the source code.
 What:		/sys/module/<MODULENAME>/version
 Date:		Jun 2005
 Description:
 		If the module source has MODULE_VERSION, this file will contain
 		the version of the source code.
--- a/Documentation/ABI/testing/configfs-usb-gadget-mass-storage
+++ b/Documentation/ABI/testing/configfs-usb-gadget-mass-storage
@ -19,7 +19,7 @@ KernelVersion:	3.13
 Description:
 		The attributes:
-		============	==============================================
+		===========	==============================================
 		file		The path to the backing file for the LUN.
 				Required if LUN is not marked as removable.
 		ro		Flag specifying access to the LUN shall be
@ -32,10 +32,4 @@ Description:
 				being a CD-ROM.
 		nofua		Flag specifying that FUA flag
 				in SCSI WRITE(10,12)
-		forced_eject	This write-only file is useful only when
+		===========	==============================================
 				the function is active. It causes the backing
 				file to be forcibly detached from the LUN,
 				regardless of whether the host has allowed it.
 				Any non-zero number of bytes written will
 				result in ejection.
 		============	==============================================
--- a/Documentation/ABI/testing/configfs-usb-gadget-uac1
+++ b/Documentation/ABI/testing/configfs-usb-gadget-uac1
@ -4,30 +4,23 @@ KernelVersion:	4.14
 Description:
 		The attributes:
-		=====================	=======================================
+		==========	===================================
-		c_chmask		capture channel mask
+		c_chmask	capture channel mask
-		c_srate			list of capture sampling rates (comma-separated)
+		c_srate		capture sampling rate
-		c_ssize			capture sample size (bytes)
+		c_ssize		capture sample size (bytes)
-		c_mute_present		capture mute control enable
+		c_mute_present	capture mute control enable
 		c_volume_present	capture volume control enable
-		c_volume_min		capture volume control min value
+		c_volume_min	capture volume control min value (in 1/256 dB)
-					(in 1/256 dB)
+		c_volume_max	capture volume control max value (in 1/256 dB)
-		c_volume_max		capture volume control max value
+		c_volume_res	capture volume control resolution (in 1/256 dB)
-					(in 1/256 dB)
+		p_chmask	playback channel mask
-		c_volume_res		capture volume control resolution
+		p_srate		playback sampling rate
-					(in 1/256 dB)
+		p_ssize		playback sample size (bytes)
-		p_chmask		playback channel mask
+		p_mute_present	playback mute control enable
 		p_srate			list of playback sampling rates (comma-separated)
 		p_ssize			playback sample size (bytes)
 		p_mute_present		playback mute control enable
 		p_volume_present	playback volume control enable
-		p_volume_min		playback volume control min value
+		p_volume_min	playback volume control min value (in 1/256 dB)
-					(in 1/256 dB)
+		p_volume_max	playback volume control max value (in 1/256 dB)
-		p_volume_max		playback volume control max value
+		p_volume_res	playback volume control resolution (in 1/256 dB)
-					(in 1/256 dB)
+		req_number	the number of pre-allocated request
-		p_volume_res		playback volume control resolution
+				for both capture and playback
-					(in 1/256 dB)
+		==========	===================================
 		req_number		the number of pre-allocated requests
 					for both capture and playback
 		function_name		name of the interface
 		=====================	=======================================
--- a/Documentation/ABI/testing/configfs-usb-gadget-uac2
+++ b/Documentation/ABI/testing/configfs-usb-gadget-uac2
@ -4,35 +4,23 @@ KernelVersion:	3.18
 Description:
 		The attributes:
-		=====================	=======================================
+		=========  ============================
-		c_chmask		capture channel mask
+		c_chmask   capture channel mask
-		c_srate			list of capture sampling rates (comma-separated)
+		c_srate    capture sampling rate
-		c_ssize			capture sample size (bytes)
+		c_ssize    capture sample size (bytes)
-		c_hs_bint		capture bInterval for HS/SS (1-4: fixed, 0: auto)
+		c_sync     capture synchronization type (async/adaptive)
-		c_sync			capture synchronization type
+		c_mute_present	capture mute control enable
 					(async/adaptive)
 		c_mute_present		capture mute control enable
 		c_volume_present	capture volume control enable
-		c_volume_min		capture volume control min value
+		c_volume_min	capture volume control min value (in 1/256 dB)
-					(in 1/256 dB)
+		c_volume_max	capture volume control max value (in 1/256 dB)
-		c_volume_max		capture volume control max value
+		c_volume_res	capture volume control resolution (in 1/256 dB)
-					(in 1/256 dB)
+		fb_max     maximum extra bandwidth in async mode
-		c_volume_res		capture volume control resolution
+		p_chmask   playback channel mask
-					(in 1/256 dB)
+		p_srate    playback sampling rate
-		fb_max			maximum extra bandwidth in async mode
+		p_ssize    playback sample size (bytes)
-		p_chmask		playback channel mask
+		p_mute_present	playback mute control enable
 		p_srate			list of playback sampling rates (comma-separated)
 		p_ssize			playback sample size (bytes)
 		p_hs_bint		playback bInterval for HS/SS (1-4: fixed, 0: auto)
 		p_mute_present		playback mute control enable
 		p_volume_present	playback volume control enable
-		p_volume_min		playback volume control min value
+		p_volume_min	playback volume control min value (in 1/256 dB)
-					(in 1/256 dB)
+		p_volume_max	playback volume control max value (in 1/256 dB)
-		p_volume_max		playback volume control max value
+		p_volume_res	playback volume control resolution (in 1/256 dB)
-					(in 1/256 dB)
+		=========  ============================
 		p_volume_res		playback volume control resolution
 					(in 1/256 dB)
 		req_number		the number of pre-allocated requests
 					for both capture and playback
 		function_name		name of the interface
 		=====================	=======================================
--- a/Documentation/ABI/testing/configfs-usb-gadget-uvc
+++ b/Documentation/ABI/testing/configfs-usb-gadget-uvc
@ -7,7 +7,6 @@ Description:	UVC function directory
 		streaming_maxburst	0..15 (ss only)
 		streaming_maxpacket	1..1023 (fs), 1..3072 (hs/ss)
 		streaming_interval	1..16
 		function_name		string [32]
 		===================	=============================
 What:		/config/usb-gadget/gadget/functions/uvc.name/control
--- a/Documentation/ABI/testing/debugfs-cros-ec
+++ b/Documentation/ABI/testing/debugfs-cros-ec
@ -54,25 +54,3 @@ Description:
 		this feature.
 		Output will be in the format: "0x%08x\n".
 What:		/sys/kernel/debug/<cros-ec-device>/suspend_timeout_ms
 Date:		August 2022
 KernelVersion:	6.1
 Description:
 		Some ECs have a feature where they will track transitions of
 		a hardware-controlled sleep line, such as Intel's SLP_S0 line,
 		in order to detect cases where a system failed to go into deep
 		sleep states. The suspend_timeout_ms file controls the amount of
 		time in milliseconds the EC will wait before declaring a sleep
 		timeout event and attempting to wake the system.
 		Supply 0 to use the default value coded into EC firmware. Supply
 		65535 (EC_HOST_SLEEP_TIMEOUT_INFINITE) to disable the EC sleep
 		failure detection mechanism. Values in between 0 and 65535
 		indicate the number of milliseconds the EC should wait after a
 		sleep transition before declaring a timeout. This includes both
 		the duration after a sleep command was received but before the
 		hardware line changed, as well as the duration between when the
 		hardware line changed and the kernel sent an EC resume command.
 		Output will be in the format: "%u\n".
--- a/Documentation/ABI/testing/debugfs-driver-habanalabs
+++ b/Documentation/ABI/testing/debugfs-driver-habanalabs
@ -12,7 +12,24 @@ What:           /sys/kernel/debug/habanalabs/hl<n>/clk_gate
 Date:           May 2020
 KernelVersion:  5.8
 Contact:        ogabbay@kernel.org
-Description:    This setting is now deprecated as clock gating is handled solely by the f/w
+Description:    Allow the root user to disable/enable in runtime the clock
                gating mechanism in Gaudi. Due to how Gaudi is built, the
                clock gating needs to be disabled in order to access the
                registers of the TPC and MME engines. This is sometimes needed
                during debug by the user and hence the user needs this option.
                The user can supply a bitmask value, each bit represents
                a different engine to disable/enable its clock gating feature.
                The bitmask is composed of 20 bits:
 		=======   ============
                0  -  7   DMA channels
                8  - 11   MME engines
                12 - 19   TPC engines
 		=======   ============
                The bit's location of a specific engine can be determined
                using (1 << GAUDI_ENGINE_ID_*). GAUDI_ENGINE_ID_* values
                are defined in uapi habanalabs.h file in enum gaudi_engine_id
 What:           /sys/kernel/debug/habanalabs/hl<n>/command_buffers
 Date:           Jan 2019
@ -101,15 +118,6 @@ Description:    Specify the size of the DMA transaction when using DMA to read
                When the write is finished, the user can read the "data_dma"
                blob
 What:           /sys/kernel/debug/habanalabs/hl<n>/dump_razwi_events
 Date:           Aug 2022
 KernelVersion:  5.20
 Contact:        fkassabri@habana.ai
 Description:    Dumps all razwi events to dmesg if exist.
                After reading the status register of an existing event
                the routine will clear the status register.
                Usage: cat dump_razwi_events
 What:           /sys/kernel/debug/habanalabs/hl<n>/dump_security_violations
 Date:           Jan 2021
 KernelVersion:  5.12
@ -130,16 +138,14 @@ Date:           Jan 2019
 KernelVersion:  5.1
 Contact:        ogabbay@kernel.org
 Description:    Sets I2C device address for I2C transaction that is generated
-                by the device's CPU, Not available when device is loaded with secured
+                by the device's CPU
                firmware
 What:           /sys/kernel/debug/habanalabs/hl<n>/i2c_bus
 Date:           Jan 2019
 KernelVersion:  5.1
 Contact:        ogabbay@kernel.org
 Description:    Sets I2C bus address for I2C transaction that is generated by
-                the device's CPU, Not available when device is loaded with secured
+                the device's CPU
                firmware
 What:           /sys/kernel/debug/habanalabs/hl<n>/i2c_data
 Date:           Jan 2019
@ -147,60 +153,32 @@ KernelVersion:  5.1
 Contact:        ogabbay@kernel.org
 Description:    Triggers an I2C transaction that is generated by the device's
                CPU. Writing to this file generates a write transaction while
-                reading from the file generates a read transaction, Not available
+                reading from the file generates a read transaction
                when device is loaded with secured firmware
 What:           /sys/kernel/debug/habanalabs/hl<n>/i2c_len
 Date:           Dec 2021
 KernelVersion:  5.17
 Contact:        obitton@habana.ai
 Description:    Sets I2C length in bytes for I2C transaction that is generated by
                the device's CPU, Not available when device is loaded with secured
                firmware
 What:           /sys/kernel/debug/habanalabs/hl<n>/i2c_reg
 Date:           Jan 2019
 KernelVersion:  5.1
 Contact:        ogabbay@kernel.org
 Description:    Sets I2C register id for I2C transaction that is generated by
-                the device's CPU, Not available when device is loaded with secured
+                the device's CPU
                firmware
 What:           /sys/kernel/debug/habanalabs/hl<n>/led0
 Date:           Jan 2019
 KernelVersion:  5.1
 Contact:        ogabbay@kernel.org
-Description:    Sets the state of the first S/W led on the device, Not available
+Description:    Sets the state of the first S/W led on the device
                when device is loaded with secured firmware
 What:           /sys/kernel/debug/habanalabs/hl<n>/led1
 Date:           Jan 2019
 KernelVersion:  5.1
 Contact:        ogabbay@kernel.org
-Description:    Sets the state of the second S/W led on the device, Not available
+Description:    Sets the state of the second S/W led on the device
                when device is loaded with secured firmware
 What:           /sys/kernel/debug/habanalabs/hl<n>/led2
 Date:           Jan 2019
 KernelVersion:  5.1
 Contact:        ogabbay@kernel.org
-Description:    Sets the state of the third S/W led on the device, Not available
+Description:    Sets the state of the third S/W led on the device
                when device is loaded with secured firmware
 What:           /sys/kernel/debug/habanalabs/hl<n>/memory_scrub
 Date:           May 2022
 KernelVersion:  5.19
 Contact:        dhirschfeld@habana.ai
 Description:    Allows the root user to scrub the dram memory. The scrubbing
                value can be set using the debugfs file memory_scrub_val.
 What:           /sys/kernel/debug/habanalabs/hl<n>/memory_scrub_val
 Date:           May 2022
 KernelVersion:  5.19
 Contact:        dhirschfeld@habana.ai
 Description:    The value to which the dram will be set to when the user
                scrubs the dram using 'memory_scrub' debugfs file and
                the scrubbing value when using module param 'memory_scrub'
 What:           /sys/kernel/debug/habanalabs/hl<n>/mmu
 Date:           Jan 2019
@ -222,30 +200,6 @@ Description:    Check and display page fault or access violation mmu errors for
                echo "0x200" > /sys/kernel/debug/habanalabs/hl0/mmu_error
                cat /sys/kernel/debug/habanalabs/hl0/mmu_error
 What:           /sys/kernel/debug/habanalabs/hl<n>/monitor_dump
 Date:           Mar 2022
 KernelVersion:  5.19
 Contact:        osharabi@habana.ai
 Description:    Allows the root user to dump monitors status from the device's
                protected config space.
                This property is a binary blob that contains the result of the
                monitors registers dump.
                This custom interface is needed (instead of using the generic
                Linux user-space PCI mapping) because this space is protected
                and cannot be accessed using PCI read.
                This interface doesn't support concurrency in the same device.
                Only supported on GAUDI.
 What:           /sys/kernel/debug/habanalabs/hl<n>/monitor_dump_trig
 Date:           Mar 2022
 KernelVersion:  5.19
 Contact:        osharabi@habana.ai
 Description:    Triggers dump of monitor data. The value to trigger the operation
                must be 1. Triggering the monitor dump operation initiates dump of
                current registers values of all monitors.
                When the write is finished, the user can read the "monitor_dump"
                blob
 What:           /sys/kernel/debug/habanalabs/hl<n>/set_power_state
 Date:           Jan 2019
 KernelVersion:  5.1
@ -278,13 +232,6 @@ KernelVersion:  5.6
 Contact:        ogabbay@kernel.org
 Description:    Sets the stop-on_error option for the device engines. Value of
                "0" is for disable, otherwise enable.
                Relevant only for GOYA and GAUDI.
 What:           /sys/kernel/debug/habanalabs/hl<n>/timeout_locked
 Date:           Sep 2021
 KernelVersion:  5.16
 Contact:        obitton@habana.ai
 Description:    Sets the command submission timeout value in seconds.
 What:           /sys/kernel/debug/habanalabs/hl<n>/userptr
 Date:           Jan 2019
@ -295,7 +242,7 @@ Description:    Displays a list with information about the currently user
                to DMA addresses
 What:           /sys/kernel/debug/habanalabs/hl<n>/userptr_lookup
-Date:           Oct 2021
+Date:           Aug 2021
 KernelVersion:  5.15
 Contact:        ogabbay@kernel.org
 Description:    Allows to search for specific user pointers (user virtual
--- a/Documentation/ABI/testing/debugfs-hisi-hpre
+++ b/Documentation/ABI/testing/debugfs-hisi-hpre
@ -1,164 +1,140 @@
-What:		/sys/kernel/debug/hisi_hpre/<bdf>/cluster[0-3]/regs
+What:           /sys/kernel/debug/hisi_hpre/<bdf>/cluster[0-3]/regs
-Date:		Sep 2019
+Date:           Sep 2019
-Contact:	linux-crypto@vger.kernel.org
+Contact:        linux-crypto@vger.kernel.org
-Description:	Dump debug registers from the HPRE cluster.
+Description:    Dump debug registers from the HPRE cluster.
 		Only available for PF.
-What:		/sys/kernel/debug/hisi_hpre/<bdf>/cluster[0-3]/cluster_ctrl
+What:           /sys/kernel/debug/hisi_hpre/<bdf>/cluster[0-3]/cluster_ctrl
-Date:		Sep 2019
+Date:           Sep 2019
-Contact:	linux-crypto@vger.kernel.org
+Contact:        linux-crypto@vger.kernel.org
-Description:	Write the HPRE core selection in the cluster into this file,
+Description:    Write the HPRE core selection in the cluster into this file,
 		and then we can read the debug information of the core.
 		Only available for PF.
-What:		/sys/kernel/debug/hisi_hpre/<bdf>/rdclr_en
+What:           /sys/kernel/debug/hisi_hpre/<bdf>/rdclr_en
-Date:		Sep 2019
+Date:           Sep 2019
-Contact:	linux-crypto@vger.kernel.org
+Contact:        linux-crypto@vger.kernel.org
-Description:	HPRE cores debug registers read clear control. 1 means enable
+Description:    HPRE cores debug registers read clear control. 1 means enable
 		register read clear, otherwise 0. Writing to this file has no
 		functional effect, only enable or disable counters clear after
 		reading of these registers.
 		Only available for PF.
-What:		/sys/kernel/debug/hisi_hpre/<bdf>/current_qm
+What:           /sys/kernel/debug/hisi_hpre/<bdf>/current_qm
-Date:		Sep 2019
+Date:           Sep 2019
-Contact:	linux-crypto@vger.kernel.org
+Contact:        linux-crypto@vger.kernel.org
-Description:	One HPRE controller has one PF and multiple VFs, each function
+Description:    One HPRE controller has one PF and multiple VFs, each function
 		has a QM. Select the QM which below qm refers to.
 		Only available for PF.
-What:		/sys/kernel/debug/hisi_hpre/<bdf>/alg_qos
+What:           /sys/kernel/debug/hisi_hpre/<bdf>/regs
-Date:		Jun 2021
+Date:           Sep 2019
-Contact:	linux-crypto@vger.kernel.org
+Contact:        linux-crypto@vger.kernel.org
-Description:	The <bdf> is related the function for PF and VF.
+Description:    Dump debug registers from the HPRE.
 		HPRE driver supports to configure each function's QoS, the driver
 		supports to write <bdf> value to alg_qos in the host. Such as
 		"echo <bdf> value > alg_qos". The qos value is 1~1000, means
 		1/1000~1000/1000 of total QoS. The driver reading alg_qos to
 		get related QoS in the host and VM, Such as "cat alg_qos".
 What:		/sys/kernel/debug/hisi_hpre/<bdf>/regs
 Date:		Sep 2019
 Contact:	linux-crypto@vger.kernel.org
 Description:	Dump debug registers from the HPRE.
 		Only available for PF.
-What:		/sys/kernel/debug/hisi_hpre/<bdf>/qm/regs
+What:           /sys/kernel/debug/hisi_hpre/<bdf>/qm/regs
-Date:		Sep 2019
+Date:           Sep 2019
-Contact:	linux-crypto@vger.kernel.org
+Contact:        linux-crypto@vger.kernel.org
-Description:	Dump debug registers from the QM.
+Description:    Dump debug registers from the QM.
 		Available for PF and VF in host. VF in guest currently only
 		has one debug register.
-What:		/sys/kernel/debug/hisi_hpre/<bdf>/qm/current_q
+What:           /sys/kernel/debug/hisi_hpre/<bdf>/qm/current_q
-Date:		Sep 2019
+Date:           Sep 2019
-Contact:	linux-crypto@vger.kernel.org
+Contact:        linux-crypto@vger.kernel.org
-Description:	One QM may contain multiple queues. Select specific queue to
+Description:    One QM may contain multiple queues. Select specific queue to
 		show its debug registers in above regs.
 		Only available for PF.
-What:		/sys/kernel/debug/hisi_hpre/<bdf>/qm/clear_enable
+What:           /sys/kernel/debug/hisi_hpre/<bdf>/qm/clear_enable
-Date:		Sep 2019
+Date:           Sep 2019
-Contact:	linux-crypto@vger.kernel.org
+Contact:        linux-crypto@vger.kernel.org
-Description:	QM debug registers(regs) read clear control. 1 means enable
+Description:    QM debug registers(regs) read clear control. 1 means enable
 		register read clear, otherwise 0.
 		Writing to this file has no functional effect, only enable or
 		disable counters clear after reading of these registers.
 		Only available for PF.
-What:		/sys/kernel/debug/hisi_hpre/<bdf>/qm/err_irq
+What:           /sys/kernel/debug/hisi_hpre/<bdf>/qm/err_irq
-Date:		Apr 2020
+Date:           Apr 2020
-Contact:	linux-crypto@vger.kernel.org
+Contact:        linux-crypto@vger.kernel.org
-Description:	Dump the number of invalid interrupts for
+Description:    Dump the number of invalid interrupts for
 		QM task completion.
 		Available for both PF and VF, and take no other effect on HPRE.
-What:		/sys/kernel/debug/hisi_hpre/<bdf>/qm/aeq_irq
+What:           /sys/kernel/debug/hisi_hpre/<bdf>/qm/aeq_irq
-Date:		Apr 2020
+Date:           Apr 2020
-Contact:	linux-crypto@vger.kernel.org
+Contact:        linux-crypto@vger.kernel.org
-Description:	Dump the number of QM async event queue interrupts.
+Description:    Dump the number of QM async event queue interrupts.
 		Available for both PF and VF, and take no other effect on HPRE.
-What:		/sys/kernel/debug/hisi_hpre/<bdf>/qm/abnormal_irq
+What:           /sys/kernel/debug/hisi_hpre/<bdf>/qm/abnormal_irq
-Date:		Apr 2020
+Date:           Apr 2020
-Contact:	linux-crypto@vger.kernel.org
+Contact:        linux-crypto@vger.kernel.org
-Description:	Dump the number of interrupts for QM abnormal event.
+Description:    Dump the number of interrupts for QM abnormal event.
 		Available for both PF and VF, and take no other effect on HPRE.
-What:		/sys/kernel/debug/hisi_hpre/<bdf>/qm/create_qp_err
+What:           /sys/kernel/debug/hisi_hpre/<bdf>/qm/create_qp_err
-Date:		Apr 2020
+Date:           Apr 2020
-Contact:	linux-crypto@vger.kernel.org
+Contact:        linux-crypto@vger.kernel.org
-Description:	Dump the number of queue allocation errors.
+Description:    Dump the number of queue allocation errors.
 		Available for both PF and VF, and take no other effect on HPRE.
-What:		/sys/kernel/debug/hisi_hpre/<bdf>/qm/mb_err
+What:           /sys/kernel/debug/hisi_hpre/<bdf>/qm/mb_err
-Date:		Apr 2020
+Date:           Apr 2020
-Contact:	linux-crypto@vger.kernel.org
+Contact:        linux-crypto@vger.kernel.org
-Description:	Dump the number of failed QM mailbox commands.
+Description:    Dump the number of failed QM mailbox commands.
 		Available for both PF and VF, and take no other effect on HPRE.
-What:		/sys/kernel/debug/hisi_hpre/<bdf>/qm/status
+What:           /sys/kernel/debug/hisi_hpre/<bdf>/qm/status
-Date:		Apr 2020
+Date:           Apr 2020
-Contact:	linux-crypto@vger.kernel.org
+Contact:        linux-crypto@vger.kernel.org
-Description:	Dump the status of the QM.
+Description:    Dump the status of the QM.
 		Four states: initiated, started, stopped and closed.
 		Available for both PF and VF, and take no other effect on HPRE.
-What:		/sys/kernel/debug/hisi_hpre/<bdf>/qm/diff_regs
+What:           /sys/kernel/debug/hisi_hpre/<bdf>/hpre_dfx/send_cnt
-Date:		Mar 2022
+Date:           Apr 2020
-Contact:	linux-crypto@vger.kernel.org
+Contact:        linux-crypto@vger.kernel.org
-Description:	QM debug registers(regs) read hardware register value. This
+Description:    Dump the total number of sent requests.
 		node is used to show the change of the qm register values. This
 		node can be help users to check the change of register values.
 What:		/sys/kernel/debug/hisi_hpre/<bdf>/hpre_dfx/diff_regs
 Date:		Mar 2022
 Contact:	linux-crypto@vger.kernel.org
 Description:	HPRE debug registers(regs) read hardware register value. This
 		node is used to show the change of the register values. This
 		node can be help users to check the change of register values.
 What:		/sys/kernel/debug/hisi_hpre/<bdf>/hpre_dfx/send_cnt
 Date:		Apr 2020
 Contact:	linux-crypto@vger.kernel.org
 Description:	Dump the total number of sent requests.
 		Available for both PF and VF, and take no other effect on HPRE.
-What:		/sys/kernel/debug/hisi_hpre/<bdf>/hpre_dfx/recv_cnt
+What:           /sys/kernel/debug/hisi_hpre/<bdf>/hpre_dfx/recv_cnt
-Date:		Apr 2020
+Date:           Apr 2020
-Contact:	linux-crypto@vger.kernel.org
+Contact:        linux-crypto@vger.kernel.org
-Description:	Dump the total number of received requests.
+Description:    Dump the total number of received requests.
 		Available for both PF and VF, and take no other effect on HPRE.
-What:		/sys/kernel/debug/hisi_hpre/<bdf>/hpre_dfx/send_busy_cnt
+What:           /sys/kernel/debug/hisi_hpre/<bdf>/hpre_dfx/send_busy_cnt
-Date:		Apr 2020
+Date:           Apr 2020
-Contact:	linux-crypto@vger.kernel.org
+Contact:        linux-crypto@vger.kernel.org
-Description:	Dump the total number of requests sent
+Description:    Dump the total number of requests sent
 		with returning busy.
 		Available for both PF and VF, and take no other effect on HPRE.
-What:		/sys/kernel/debug/hisi_hpre/<bdf>/hpre_dfx/send_fail_cnt
+What:           /sys/kernel/debug/hisi_hpre/<bdf>/hpre_dfx/send_fail_cnt
-Date:		Apr 2020
+Date:           Apr 2020
-Contact:	linux-crypto@vger.kernel.org
+Contact:        linux-crypto@vger.kernel.org
-Description:	Dump the total number of completed but error requests.
+Description:    Dump the total number of completed but error requests.
 		Available for both PF and VF, and take no other effect on HPRE.
-What:		/sys/kernel/debug/hisi_hpre/<bdf>/hpre_dfx/invalid_req_cnt
+What:           /sys/kernel/debug/hisi_hpre/<bdf>/hpre_dfx/invalid_req_cnt
-Date:		Apr 2020
+Date:           Apr 2020
-Contact:	linux-crypto@vger.kernel.org
+Contact:        linux-crypto@vger.kernel.org
-Description:	Dump the total number of invalid requests being received.
+Description:    Dump the total number of invalid requests being received.
 		Available for both PF and VF, and take no other effect on HPRE.
-What:		/sys/kernel/debug/hisi_hpre/<bdf>/hpre_dfx/overtime_thrhld
+What:           /sys/kernel/debug/hisi_hpre/<bdf>/hpre_dfx/overtime_thrhld
-Date:		Apr 2020
+Date:           Apr 2020
-Contact:	linux-crypto@vger.kernel.org
+Contact:        linux-crypto@vger.kernel.org
-Description:	Set the threshold time for counting the request which is
+Description:    Set the threshold time for counting the request which is
 		processed longer than the threshold.
 		0: disable(default), 1: 1 microsecond.
 		Available for both PF and VF, and take no other effect on HPRE.
-What:		/sys/kernel/debug/hisi_hpre/<bdf>/hpre_dfx/over_thrhld_cnt
+What:           /sys/kernel/debug/hisi_hpre/<bdf>/hpre_dfx/over_thrhld_cnt
-Date:		Apr 2020
+Date:           Apr 2020
-Contact:	linux-crypto@vger.kernel.org
+Contact:        linux-crypto@vger.kernel.org
-Description:	Dump the total number of time out requests.
+Description:    Dump the total number of time out requests.
 		Available for both PF and VF, and take no other effect on HPRE.
--- a/Documentation/ABI/testing/debugfs-hisi-sec
+++ b/Documentation/ABI/testing/debugfs-hisi-sec
@ -1,137 +1,113 @@
-What:		/sys/kernel/debug/hisi_sec2/<bdf>/clear_enable
+What:           /sys/kernel/debug/hisi_sec2/<bdf>/clear_enable
-Date:		Oct 2019
+Date:           Oct 2019
-Contact:	linux-crypto@vger.kernel.org
+Contact:        linux-crypto@vger.kernel.org
-Description:	Enabling/disabling of clear action after reading
+Description:    Enabling/disabling of clear action after reading
 		the SEC debug registers.
 		0: disable, 1: enable.
 		Only available for PF, and take no other effect on SEC.
-What:		/sys/kernel/debug/hisi_sec2/<bdf>/current_qm
+What:           /sys/kernel/debug/hisi_sec2/<bdf>/current_qm
-Date:		Oct 2019
+Date:           Oct 2019
-Contact:	linux-crypto@vger.kernel.org
+Contact:        linux-crypto@vger.kernel.org
-Description:	One SEC controller has one PF and multiple VFs, each function
+Description:    One SEC controller has one PF and multiple VFs, each function
 		has a QM. This file can be used to select the QM which below
 		qm refers to.
 		Only available for PF.
-What:		/sys/kernel/debug/hisi_sec2/<bdf>/alg_qos
+What:           /sys/kernel/debug/hisi_sec2/<bdf>/qm/qm_regs
-Date:		Jun 2021
+Date:           Oct 2019
-Contact:	linux-crypto@vger.kernel.org
+Contact:        linux-crypto@vger.kernel.org
-Description:	The <bdf> is related the function for PF and VF.
+Description:    Dump of QM related debug registers.
 		SEC driver supports to configure each function's QoS, the driver
 		supports to write <bdf> value to alg_qos in the host. Such as
 		"echo <bdf> value > alg_qos". The qos value is 1~1000, means
 		1/1000~1000/1000 of total QoS. The driver reading alg_qos to
 		get related QoS in the host and VM, Such as "cat alg_qos".
 What:		/sys/kernel/debug/hisi_sec2/<bdf>/qm/qm_regs
 Date:		Oct 2019
 Contact:	linux-crypto@vger.kernel.org
 Description:	Dump of QM related debug registers.
 		Available for PF and VF in host. VF in guest currently only
 		has one debug register.
-What:		/sys/kernel/debug/hisi_sec2/<bdf>/qm/current_q
+What:           /sys/kernel/debug/hisi_sec2/<bdf>/qm/current_q
-Date:		Oct 2019
+Date:           Oct 2019
-Contact:	linux-crypto@vger.kernel.org
+Contact:        linux-crypto@vger.kernel.org
-Description:	One QM of SEC may contain multiple queues. Select specific
+Description:    One QM of SEC may contain multiple queues. Select specific
 		queue to show its debug registers in above 'regs'.
 		Only available for PF.
-What:		/sys/kernel/debug/hisi_sec2/<bdf>/qm/clear_enable
+What:           /sys/kernel/debug/hisi_sec2/<bdf>/qm/clear_enable
-Date:		Oct 2019
+Date:           Oct 2019
-Contact:	linux-crypto@vger.kernel.org
+Contact:        linux-crypto@vger.kernel.org
-Description:	Enabling/disabling of clear action after reading
+Description:    Enabling/disabling of clear action after reading
 		the SEC's QM debug registers.
 		0: disable, 1: enable.
 		Only available for PF, and take no other effect on SEC.
-What:		/sys/kernel/debug/hisi_sec2/<bdf>/qm/err_irq
+What:           /sys/kernel/debug/hisi_sec2/<bdf>/qm/err_irq
-Date:		Apr 2020
+Date:           Apr 2020
-Contact:	linux-crypto@vger.kernel.org
+Contact:        linux-crypto@vger.kernel.org
-Description:	Dump the number of invalid interrupts for
+Description:    Dump the number of invalid interrupts for
 		QM task completion.
 		Available for both PF and VF, and take no other effect on SEC.
-What:		/sys/kernel/debug/hisi_sec2/<bdf>/qm/aeq_irq
+What:           /sys/kernel/debug/hisi_sec2/<bdf>/qm/aeq_irq
-Date:		Apr 2020
+Date:           Apr 2020
-Contact:	linux-crypto@vger.kernel.org
+Contact:        linux-crypto@vger.kernel.org
-Description:	Dump the number of QM async event queue interrupts.
+Description:    Dump the number of QM async event queue interrupts.
 		Available for both PF and VF, and take no other effect on SEC.
-What:		/sys/kernel/debug/hisi_sec2/<bdf>/qm/abnormal_irq
+What:           /sys/kernel/debug/hisi_sec2/<bdf>/qm/abnormal_irq
-Date:		Apr 2020
+Date:           Apr 2020
-Contact:	linux-crypto@vger.kernel.org
+Contact:        linux-crypto@vger.kernel.org
-Description:	Dump the number of interrupts for QM abnormal event.
+Description:    Dump the number of interrupts for QM abnormal event.
 		Available for both PF and VF, and take no other effect on SEC.
-What:		/sys/kernel/debug/hisi_sec2/<bdf>/qm/create_qp_err
+What:           /sys/kernel/debug/hisi_sec2/<bdf>/qm/create_qp_err
-Date:		Apr 2020
+Date:           Apr 2020
-Contact:	linux-crypto@vger.kernel.org
+Contact:        linux-crypto@vger.kernel.org
-Description:	Dump the number of queue allocation errors.
+Description:    Dump the number of queue allocation errors.
 		Available for both PF and VF, and take no other effect on SEC.
-What:		/sys/kernel/debug/hisi_sec2/<bdf>/qm/mb_err
+What:           /sys/kernel/debug/hisi_sec2/<bdf>/qm/mb_err
-Date:		Apr 2020
+Date:           Apr 2020
-Contact:	linux-crypto@vger.kernel.org
+Contact:        linux-crypto@vger.kernel.org
-Description:	Dump the number of failed QM mailbox commands.
+Description:    Dump the number of failed QM mailbox commands.
 		Available for both PF and VF, and take no other effect on SEC.
-What:		/sys/kernel/debug/hisi_sec2/<bdf>/qm/status
+What:           /sys/kernel/debug/hisi_sec2/<bdf>/qm/status
-Date:		Apr 2020
+Date:           Apr 2020
-Contact:	linux-crypto@vger.kernel.org
+Contact:        linux-crypto@vger.kernel.org
-Description:	Dump the status of the QM.
+Description:    Dump the status of the QM.
 		Four states: initiated, started, stopped and closed.
 		Available for both PF and VF, and take no other effect on SEC.
-What:		/sys/kernel/debug/hisi_sec2/<bdf>/qm/diff_regs
+What:           /sys/kernel/debug/hisi_sec2/<bdf>/sec_dfx/send_cnt
-Date:		Mar 2022
+Date:           Apr 2020
-Contact:	linux-crypto@vger.kernel.org
+Contact:        linux-crypto@vger.kernel.org
-Description:	QM debug registers(regs) read hardware register value. This
+Description:    Dump the total number of sent requests.
 		node is used to show the change of the qm register values. This
 		node can be help users to check the change of register values.
 What:		/sys/kernel/debug/hisi_sec2/<bdf>/sec_dfx/diff_regs
 Date:		Mar 2022
 Contact:	linux-crypto@vger.kernel.org
 Description:	SEC debug registers(regs) read hardware register value. This
 		node is used to show the change of the register values. This
 		node can be help users to check the change of register values.
 What:		/sys/kernel/debug/hisi_sec2/<bdf>/sec_dfx/send_cnt
 Date:		Apr 2020
 Contact:	linux-crypto@vger.kernel.org
 Description:	Dump the total number of sent requests.
 		Available for both PF and VF, and take no other effect on SEC.
-What:		/sys/kernel/debug/hisi_sec2/<bdf>/sec_dfx/recv_cnt
+What:           /sys/kernel/debug/hisi_sec2/<bdf>/sec_dfx/recv_cnt
-Date:		Apr 2020
+Date:           Apr 2020
-Contact:	linux-crypto@vger.kernel.org
+Contact:        linux-crypto@vger.kernel.org
-Description:	Dump the total number of received requests.
+Description:    Dump the total number of received requests.
 		Available for both PF and VF, and take no other effect on SEC.
-What:		/sys/kernel/debug/hisi_sec2/<bdf>/sec_dfx/send_busy_cnt
+What:           /sys/kernel/debug/hisi_sec2/<bdf>/sec_dfx/send_busy_cnt
-Date:		Apr 2020
+Date:           Apr 2020
-Contact:	linux-crypto@vger.kernel.org
+Contact:        linux-crypto@vger.kernel.org
-Description:	Dump the total number of requests sent with returning busy.
+Description:    Dump the total number of requests sent with returning busy.
 		Available for both PF and VF, and take no other effect on SEC.
-What:		/sys/kernel/debug/hisi_sec2/<bdf>/sec_dfx/err_bd_cnt
+What:           /sys/kernel/debug/hisi_sec2/<bdf>/sec_dfx/err_bd_cnt
-Date:		Apr 2020
+Date:           Apr 2020
-Contact:	linux-crypto@vger.kernel.org
+Contact:        linux-crypto@vger.kernel.org
-Description:	Dump the total number of BD type error requests
+Description:    Dump the total number of BD type error requests
 		to be received.
 		Available for both PF and VF, and take no other effect on SEC.
-What:		/sys/kernel/debug/hisi_sec2/<bdf>/sec_dfx/invalid_req_cnt
+What:           /sys/kernel/debug/hisi_sec2/<bdf>/sec_dfx/invalid_req_cnt
-Date:		Apr 2020
+Date:           Apr 2020
-Contact:	linux-crypto@vger.kernel.org
+Contact:        linux-crypto@vger.kernel.org
-Description:	Dump the total number of invalid requests being received.
+Description:    Dump the total number of invalid requests being received.
 		Available for both PF and VF, and take no other effect on SEC.
-What:		/sys/kernel/debug/hisi_sec2/<bdf>/sec_dfx/done_flag_cnt
+What:           /sys/kernel/debug/hisi_sec2/<bdf>/sec_dfx/done_flag_cnt
-Date:		Apr 2020
+Date:           Apr 2020
-Contact:	linux-crypto@vger.kernel.org
+Contact:        linux-crypto@vger.kernel.org
-Description:	Dump the total number of completed but marked error requests
+Description:    Dump the total number of completed but marked error requests
 		to be received.
 		Available for both PF and VF, and take no other effect on SEC.
--- a/Documentation/ABI/testing/debugfs-hisi-zip
+++ b/Documentation/ABI/testing/debugfs-hisi-zip
@ -1,138 +1,114 @@
-What:		/sys/kernel/debug/hisi_zip/<bdf>/comp_core[01]/regs
+What:           /sys/kernel/debug/hisi_zip/<bdf>/comp_core[01]/regs
-Date:		Nov 2018
+Date:           Nov 2018
-Contact:	linux-crypto@vger.kernel.org
+Contact:        linux-crypto@vger.kernel.org
-Description:	Dump of compression cores related debug registers.
+Description:    Dump of compression cores related debug registers.
 		Only available for PF.
-What:		/sys/kernel/debug/hisi_zip/<bdf>/decomp_core[0-5]/regs
+What:           /sys/kernel/debug/hisi_zip/<bdf>/decomp_core[0-5]/regs
-Date:		Nov 2018
+Date:           Nov 2018
-Contact:	linux-crypto@vger.kernel.org
+Contact:        linux-crypto@vger.kernel.org
-Description:	Dump of decompression cores related debug registers.
+Description:    Dump of decompression cores related debug registers.
 		Only available for PF.
-What:		/sys/kernel/debug/hisi_zip/<bdf>/clear_enable
+What:           /sys/kernel/debug/hisi_zip/<bdf>/clear_enable
-Date:		Nov 2018
+Date:           Nov 2018
-Contact:	linux-crypto@vger.kernel.org
+Contact:        linux-crypto@vger.kernel.org
-Description:	Compression/decompression core debug registers read clear
+Description:    Compression/decompression core debug registers read clear
 		control. 1 means enable register read clear, otherwise 0.
 		Writing to this file has no functional effect, only enable or
 		disable counters clear after reading of these registers.
 		Only available for PF.
-What:		/sys/kernel/debug/hisi_zip/<bdf>/current_qm
+What:           /sys/kernel/debug/hisi_zip/<bdf>/current_qm
-Date:		Nov 2018
+Date:           Nov 2018
-Contact:	linux-crypto@vger.kernel.org
+Contact:        linux-crypto@vger.kernel.org
-Description:	One ZIP controller has one PF and multiple VFs, each function
+Description:    One ZIP controller has one PF and multiple VFs, each function
 		has a QM. Select the QM which below qm refers to.
 		Only available for PF.
-What:		/sys/kernel/debug/hisi_zip/<bdf>/alg_qos
+What:           /sys/kernel/debug/hisi_zip/<bdf>/qm/regs
-Date:		Jun 2021
+Date:           Nov 2018
-Contact:	linux-crypto@vger.kernel.org
+Contact:        linux-crypto@vger.kernel.org
-Description:	The <bdf> is related the function for PF and VF.
+Description:    Dump of QM related debug registers.
 		ZIP driver supports to configure each function's QoS, the driver
 		supports to write <bdf> value to alg_qos in the host. Such as
 		"echo <bdf> value > alg_qos". The qos value is 1~1000, means
 		1/1000~1000/1000 of total QoS. The driver reading alg_qos to
 		get related QoS in the host and VM, Such as "cat alg_qos".
 What:		/sys/kernel/debug/hisi_zip/<bdf>/qm/regs
 Date:		Nov 2018
 Contact:	linux-crypto@vger.kernel.org
 Description:	Dump of QM related debug registers.
 		Available for PF and VF in host. VF in guest currently only
 		has one debug register.
-What:		/sys/kernel/debug/hisi_zip/<bdf>/qm/current_q
+What:           /sys/kernel/debug/hisi_zip/<bdf>/qm/current_q
-Date:		Nov 2018
+Date:           Nov 2018
-Contact:	linux-crypto@vger.kernel.org
+Contact:        linux-crypto@vger.kernel.org
-Description:	One QM may contain multiple queues. Select specific queue to
+Description:    One QM may contain multiple queues. Select specific queue to
 		show its debug registers in above regs.
 		Only available for PF.
-What:		/sys/kernel/debug/hisi_zip/<bdf>/qm/clear_enable
+What:           /sys/kernel/debug/hisi_zip/<bdf>/qm/clear_enable
-Date:		Nov 2018
+Date:           Nov 2018
-Contact:	linux-crypto@vger.kernel.org
+Contact:        linux-crypto@vger.kernel.org
-Description:	QM debug registers(regs) read clear control. 1 means enable
+Description:    QM debug registers(regs) read clear control. 1 means enable
 		register read clear, otherwise 0.
 		Writing to this file has no functional effect, only enable or
 		disable counters clear after reading of these registers.
 		Only available for PF.
-What:		/sys/kernel/debug/hisi_zip/<bdf>/qm/err_irq
+What:           /sys/kernel/debug/hisi_zip/<bdf>/qm/err_irq
-Date:		Apr 2020
+Date:           Apr 2020
-Contact:	linux-crypto@vger.kernel.org
+Contact:        linux-crypto@vger.kernel.org
-Description:	Dump the number of invalid interrupts for
+Description:    Dump the number of invalid interrupts for
 		QM task completion.
 		Available for both PF and VF, and take no other effect on ZIP.
-What:		/sys/kernel/debug/hisi_zip/<bdf>/qm/aeq_irq
+What:           /sys/kernel/debug/hisi_zip/<bdf>/qm/aeq_irq
-Date:		Apr 2020
+Date:           Apr 2020
-Contact:	linux-crypto@vger.kernel.org
+Contact:        linux-crypto@vger.kernel.org
-Description:	Dump the number of QM async event queue interrupts.
+Description:    Dump the number of QM async event queue interrupts.
 		Available for both PF and VF, and take no other effect on ZIP.
-What:		/sys/kernel/debug/hisi_zip/<bdf>/qm/abnormal_irq
+What:           /sys/kernel/debug/hisi_zip/<bdf>/qm/abnormal_irq
-Date:		Apr 2020
+Date:           Apr 2020
-Contact:	linux-crypto@vger.kernel.org
+Contact:        linux-crypto@vger.kernel.org
-Description:	Dump the number of interrupts for QM abnormal event.
+Description:    Dump the number of interrupts for QM abnormal event.
 		Available for both PF and VF, and take no other effect on ZIP.
-What:		/sys/kernel/debug/hisi_zip/<bdf>/qm/create_qp_err
+What:           /sys/kernel/debug/hisi_zip/<bdf>/qm/create_qp_err
-Date:		Apr 2020
+Date:           Apr 2020
-Contact:	linux-crypto@vger.kernel.org
+Contact:        linux-crypto@vger.kernel.org
-Description:	Dump the number of queue allocation errors.
+Description:    Dump the number of queue allocation errors.
 		Available for both PF and VF, and take no other effect on ZIP.
-What:		/sys/kernel/debug/hisi_zip/<bdf>/qm/mb_err
+What:           /sys/kernel/debug/hisi_zip/<bdf>/qm/mb_err
-Date:		Apr 2020
+Date:           Apr 2020
-Contact:	linux-crypto@vger.kernel.org
+Contact:        linux-crypto@vger.kernel.org
-Description:	Dump the number of failed QM mailbox commands.
+Description:    Dump the number of failed QM mailbox commands.
 		Available for both PF and VF, and take no other effect on ZIP.
-What:		/sys/kernel/debug/hisi_zip/<bdf>/qm/status
+What:           /sys/kernel/debug/hisi_zip/<bdf>/qm/status
-Date:		Apr 2020
+Date:           Apr 2020
-Contact:	linux-crypto@vger.kernel.org
+Contact:        linux-crypto@vger.kernel.org
-Description:	Dump the status of the QM.
+Description:    Dump the status of the QM.
 		Four states: initiated, started, stopped and closed.
 		Available for both PF and VF, and take no other effect on ZIP.
-What:		/sys/kernel/debug/hisi_zip/<bdf>/qm/diff_regs
+What:           /sys/kernel/debug/hisi_zip/<bdf>/zip_dfx/send_cnt
-Date:		Mar 2022
+Date:           Apr 2020
-Contact:	linux-crypto@vger.kernel.org
+Contact:        linux-crypto@vger.kernel.org
-Description:	QM debug registers(regs) read hardware register value. This
+Description:    Dump the total number of sent requests.
 		node is used to show the change of the qm registers value. This
 		node can be help users to check the change of register values.
 What:		/sys/kernel/debug/hisi_zip/<bdf>/zip_dfx/diff_regs
 Date:		Mar 2022
 Contact:	linux-crypto@vger.kernel.org
 Description:	ZIP debug registers(regs) read hardware register value. This
 		node is used to show the change of the registers value. this
 		node can be help users to check the change of register values.
 What:		/sys/kernel/debug/hisi_zip/<bdf>/zip_dfx/send_cnt
 Date:		Apr 2020
 Contact:	linux-crypto@vger.kernel.org
 Description:	Dump the total number of sent requests.
 		Available for both PF and VF, and take no other effect on ZIP.
-What:		/sys/kernel/debug/hisi_zip/<bdf>/zip_dfx/recv_cnt
+What:           /sys/kernel/debug/hisi_zip/<bdf>/zip_dfx/recv_cnt
-Date:		Apr 2020
+Date:           Apr 2020
-Contact:	linux-crypto@vger.kernel.org
+Contact:        linux-crypto@vger.kernel.org
-Description:	Dump the total number of received requests.
+Description:    Dump the total number of received requests.
 		Available for both PF and VF, and take no other effect on ZIP.
-What:		/sys/kernel/debug/hisi_zip/<bdf>/zip_dfx/send_busy_cnt
+What:           /sys/kernel/debug/hisi_zip/<bdf>/zip_dfx/send_busy_cnt
-Date:		Apr 2020
+Date:           Apr 2020
-Contact:	linux-crypto@vger.kernel.org
+Contact:        linux-crypto@vger.kernel.org
-Description:	Dump the total number of requests received
+Description:    Dump the total number of requests received
 		with returning busy.
 		Available for both PF and VF, and take no other effect on ZIP.
-What:		/sys/kernel/debug/hisi_zip/<bdf>/zip_dfx/err_bd_cnt
+What:           /sys/kernel/debug/hisi_zip/<bdf>/zip_dfx/err_bd_cnt
-Date:		Apr 2020
+Date:           Apr 2020
-Contact:	linux-crypto@vger.kernel.org
+Contact:        linux-crypto@vger.kernel.org
-Description:	Dump the total number of BD type error requests
+Description:    Dump the total number of BD type error requests
 		to be received.
 		Available for both PF and VF, and take no other effect on ZIP.
--- a/Documentation/ABI/testing/evm
+++ b/Documentation/ABI/testing/evm
@ -1,5 +1,4 @@
-What:		/sys/kernel/security/evm
+What:		security/evm
 What:		/sys/kernel/security/*/evm
 Date:		March 2011
 Contact:	Mimi Zohar <zohar@us.ibm.com>
 Description:
@ -94,7 +93,7 @@ Description:
 		core/ima-setup) have support for loading keys at boot
 		time.
-What:		/sys/kernel/security/*/evm/evm_xattrs
+What:		security/integrity/evm/evm_xattrs
 Date:		April 2018
 Contact:	Matthew Garrett <mjg59@google.com>
 Description:
--- a/Documentation/ABI/testing/ima_policy
+++ b/Documentation/ABI/testing/ima_policy
@ -1,4 +1,4 @@
-What:		/sys/kernel/security/*/ima/policy
+What:		security/ima/policy
 Date:		May 2008
 Contact:	Mimi Zohar <zohar@us.ibm.com>
 Description:
@ -22,14 +22,12 @@ Description:
 		  action: measure | dont_measure | appraise | dont_appraise |
 			  audit | hash | dont_hash
 		  condition:= base | lsm  [option]
-			base:	[[func=] [mask=] [fsmagic=] [fsuuid=] [fsname=]
+			base:	[[func=] [mask=] [fsmagic=] [fsuuid=] [uid=]
-				[uid=] [euid=] [gid=] [egid=]
+				[euid=] [fowner=] [fsname=]]
 				[fowner=] [fgroup=]]
 			lsm:	[[subj_user=] [subj_role=] [subj_type=]
 				 [obj_user=] [obj_role=] [obj_type=]]
-			option:	[digest_type=] [template=] [permit_directio]
+			option:	[[appraise_type=]] [template=] [permit_directio]
-				[appraise_type=] [appraise_flag=]
+				[appraise_flag=] [appraise_algos=] [keyrings=]
 				[appraise_algos=] [keyrings=]
 		  base:
 			func:= [BPRM_CHECK][MMAP_CHECK][CREDS_CHECK][FILE_CHECK][MODULE_CHECK]
 				[FIRMWARE_CHECK]
@ -42,27 +40,13 @@ Description:
 			fsuuid:= file system UUID (e.g 8bcbe394-4f13-4144-be8e-5aa9ea2ce2f6)
 			uid:= decimal value
 			euid:= decimal value
 			gid:= decimal value
 			egid:= decimal value
 			fowner:= decimal value
 			fgroup:= decimal value
 		  lsm:  are LSM specific
 		  option:
-			appraise_type:= [imasig] | [imasig|modsig] | [sigv3]
+			appraise_type:= [imasig] [imasig|modsig]
 			    where 'imasig' is the original or the signature
 				format v2.
 			    where 'modsig' is an appended signature,
 			    where 'sigv3' is the signature format v3. (Currently
 				limited to fsverity digest based signatures
 				stored in security.ima xattr. Requires
 				specifying "digest_type=verity" first.)
 			appraise_flag:= [check_blacklist]
 			Currently, blacklist check is only for files signed with appended
 			signature.
 			digest_type:= verity
 			    Require fs-verity's file digest instead of the
 			    regular IMA file hash.
 			keyrings:= list of keyrings
 			(eg, .builtin_trusted_keys|.ima). Only valid
 			when action is "measure" and func is KEY_CHECK.
@ -161,30 +145,3 @@ Description:
 		security.ima xattr of a file:
 			appraise func=SETXATTR_CHECK appraise_algos=sha256,sha384,sha512
 		Example of a 'measure' rule requiring fs-verity's digests
 		with indication of type of digest in the measurement list.
 			measure func=FILE_CHECK digest_type=verity \
 				template=ima-ngv2
 		Example of 'measure' and 'appraise' rules requiring fs-verity
 		signatures (format version 3) stored in security.ima xattr.
 		The 'measure' rule specifies the 'ima-sigv3' template option,
 		which includes the indication of type of digest and the file
 		signature in the measurement list.
 			measure func=BPRM_CHECK digest_type=verity \
 				template=ima-sigv3
 		The 'appraise' rule specifies the type and signature format
 		version (sigv3) required.
 			appraise func=BPRM_CHECK digest_type=verity \
 				appraise_type=sigv3
 		All of these policy rules could, for example, be constrained
 		either based on a filesystem's UUID (fsuuid) or based on LSM
 		labels.
--- a/Documentation/ABI/testing/procfs-smaps_rollup
+++ b/Documentation/ABI/testing/procfs-smaps_rollup
@ -22,7 +22,6 @@ Description:
 			MMUPageSize:           4 kB
 			Rss:		     884 kB
 			Pss:		     385 kB
 			Pss_Dirty:	      68 kB
 			Pss_Anon:	     301 kB
 			Pss_File:	      80 kB
 			Pss_Shmem:	       4 kB
--- a/Documentation/ABI/testing/pstore
+++ b/Documentation/ABI/testing/pstore
@ -1,5 +1,4 @@
-What:		/sys/fs/pstore/...
+What:		/sys/fs/pstore/... (or /dev/pstore/...)
 What:		/dev/pstore/...
 Date:		March 2011
 KernelVersion: 2.6.39
 Contact:	tony.luck@intel.com
--- a/Documentation/ABI/testing/securityfs-secrets-coco
+++ b/Documentation/ABI/testing/securityfs-secrets-coco
@ -1,51 +0,0 @@
 What:		security/secrets/coco
 Date:		February 2022
 Contact:	Dov Murik <dovmurik@linux.ibm.com>
 Description:
 		Exposes confidential computing (coco) EFI secrets to
 		userspace via securityfs.
 		EFI can declare memory area used by confidential computing
 		platforms (such as AMD SEV and SEV-ES) for secret injection by
 		the Guest Owner during VM's launch.  The secrets are encrypted
 		by the Guest Owner and decrypted inside the trusted enclave,
 		and therefore are not readable by the untrusted host.
 		The efi_secret module exposes the secrets to userspace.  Each
 		secret appears as a file under <securityfs>/secrets/coco,
 		where the filename is the GUID of the entry in the secrets
 		table.  This module is loaded automatically by the EFI driver
 		if the EFI secret area is populated.
 		Two operations are supported for the files: read and unlink.
 		Reading the file returns the content of secret entry.
 		Unlinking the file overwrites the secret data with zeroes and
 		removes the entry from the filesystem.  A secret cannot be read
 		after it has been unlinked.
 		For example, listing the available secrets::
 		  # modprobe efi_secret
 		  # ls -l /sys/kernel/security/secrets/coco
 		  -r--r----- 1 root root 0 Jun 28 11:54 736870e5-84f0-4973-92ec-06879ce3da0b
 		  -r--r----- 1 root root 0 Jun 28 11:54 83c83f7f-1356-4975-8b7e-d3a0b54312c6
 		  -r--r----- 1 root root 0 Jun 28 11:54 9553f55d-3da2-43ee-ab5d-ff17f78864d2
 		  -r--r----- 1 root root 0 Jun 28 11:54 e6f5a162-d67f-4750-a67c-5d065f2a9910
 		Reading the secret data by reading a file::
 		  # cat /sys/kernel/security/secrets/coco/e6f5a162-d67f-4750-a67c-5d065f2a9910
 		  the-content-of-the-secret-data
 		Wiping a secret by unlinking a file::
 		  # rm /sys/kernel/security/secrets/coco/e6f5a162-d67f-4750-a67c-5d065f2a9910
 		  # ls -l /sys/kernel/security/secrets/coco
 		  -r--r----- 1 root root 0 Jun 28 11:54 736870e5-84f0-4973-92ec-06879ce3da0b
 		  -r--r----- 1 root root 0 Jun 28 11:54 83c83f7f-1356-4975-8b7e-d3a0b54312c6
 		  -r--r----- 1 root root 0 Jun 28 11:54 9553f55d-3da2-43ee-ab5d-ff17f78864d2
 		Note: The binary format of the secrets table injected by the
 		Guest Owner is described in
 		drivers/virt/coco/efi_secret/efi_secret.c under "Structure of
 		the EFI secret area".
--- a/Documentation/ABI/testing/sysfs-amd-pmc
+++ b/Documentation/ABI/testing/sysfs-amd-pmc
@ -1,13 +0,0 @@
 What:		/sys/bus/platform/drivers/amd_pmc/*/smu_fw_version
 Date:		October 2022
 Contact:	Mario Limonciello <mario.limonciello@amd.com>
 Description:	Reading this file reports the version of the firmware loaded to
 		System Management Unit (SMU) contained in AMD CPUs and
 		APUs.
 What:		/sys/bus/platform/drivers/amd_pmc/*/smu_program
 Date:		October 2022
 Contact:	Mario Limonciello <mario.limonciello@amd.com>
 Description:	Reading this file reports the program corresponding to the SMU
 		firmware version.  The program field is used to disambiguate two
 		APU/CPU models that can share the same firmware binary.
--- a/Documentation/ABI/testing/sysfs-amd-pmf
+++ b/Documentation/ABI/testing/sysfs-amd-pmf
@ -1,13 +0,0 @@
 What:		/sys/devices/platform/*/cnqf_enable
 Date:		September 2022
 Contact:	Shyam Sundar S K <Shyam-sundar.S-k@amd.com>
 Description:	Reading this file tells if the AMD Platform Management(PMF)
 		Cool n Quiet Framework(CnQF) feature is enabled or not.
 		This feature is not enabled by default and gets only turned on
 		if OEM BIOS passes a "flag" to PMF ACPI function (index 11 or 12)
 		or in case the user writes "on".
 		To turn off CnQF user can write "off" to the sysfs node.
 		Note: Systems that support auto mode will not have this sysfs file
 		available.
--- a/Documentation/ABI/testing/sysfs-ata
+++ b/Documentation/ABI/testing/sysfs-ata
@ -1,4 +1,4 @@
-What:		/sys/class/ata_*
+What:		/sys/class/ata_...
 Description:
 		Provide a place in sysfs for storing the ATA topology of the
 		system. This allows retrieving various information about ATA
@ -107,14 +107,13 @@ Description:
 				described in ATA8 7.16 and 7.17. Only valid if
 				the device is not a PM.
-		pio_mode:	(RO) PIO transfer mode used by the device.
+		pio_mode:	(RO) Transfer modes supported by the device when
-				Mostly used by PATA devices.
+				in PIO mode. Mostly used by PATA device.
-		xfer_mode:	(RO) Current transfer mode. Mostly used by
+		xfer_mode:	(RO) Current transfer mode
 				PATA devices.
-		dma_mode:	(RO) DMA transfer mode used by the device.
+		dma_mode:	(RO) Transfer modes supported by the device when
-				Mostly used by PATA devices.
+				in DMA mode. Mostly used by PATA device.
 		class:		(RO) Device class. Can be "ata" for disk,
 				"atapi" for packet device, "pmp" for PM, or
--- a/Documentation/ABI/testing/sysfs-block
+++ b/Documentation/ABI/testing/sysfs-block
@ -0,0 +1,330 @@
 What:		/sys/block/<disk>/stat
 Date:		February 2008
 Contact:	Jerome Marchand <jmarchan@redhat.com>
 Description:
 		The /sys/block/<disk>/stat files displays the I/O
 		statistics of disk <disk>. They contain 11 fields:
 		==  ==============================================
 		 1  reads completed successfully
 		 2  reads merged
 		 3  sectors read
 		 4  time spent reading (ms)
 		 5  writes completed
 		 6  writes merged
 		 7  sectors written
 		 8  time spent writing (ms)
 		 9  I/Os currently in progress
 		10  time spent doing I/Os (ms)
 		11  weighted time spent doing I/Os (ms)
 		12  discards completed
 		13  discards merged
 		14  sectors discarded
 		15  time spent discarding (ms)
 		16  flush requests completed
 		17  time spent flushing (ms)
 		==  ==============================================
 		For more details refer Documentation/admin-guide/iostats.rst
 What:		/sys/block/<disk>/diskseq
 Date:		February 2021
 Contact:	Matteo Croce <mcroce@microsoft.com>
 Description:
 		The /sys/block/<disk>/diskseq files reports the disk
 		sequence number, which is a monotonically increasing
 		number assigned to every drive.
 		Some devices, like the loop device, refresh such number
 		every time the backing file is changed.
 		The value type is 64 bit unsigned.
 What:		/sys/block/<disk>/<part>/stat
 Date:		February 2008
 Contact:	Jerome Marchand <jmarchan@redhat.com>
 Description:
 		The /sys/block/<disk>/<part>/stat files display the
 		I/O statistics of partition <part>. The format is the
 		same as the above-written /sys/block/<disk>/stat
 		format.
 What:		/sys/block/<disk>/integrity/format
 Date:		June 2008
 Contact:	Martin K. Petersen <martin.petersen@oracle.com>
 Description:
 		Metadata format for integrity capable block device.
 		E.g. T10-DIF-TYPE1-CRC.
 What:		/sys/block/<disk>/integrity/read_verify
 Date:		June 2008
 Contact:	Martin K. Petersen <martin.petersen@oracle.com>
 Description:
 		Indicates whether the block layer should verify the
 		integrity of read requests serviced by devices that
 		support sending integrity metadata.
 What:		/sys/block/<disk>/integrity/tag_size
 Date:		June 2008
 Contact:	Martin K. Petersen <martin.petersen@oracle.com>
 Description:
 		Number of bytes of integrity tag space available per
 		512 bytes of data.
 What:		/sys/block/<disk>/integrity/device_is_integrity_capable
 Date:		July 2014
 Contact:	Martin K. Petersen <martin.petersen@oracle.com>
 Description:
 		Indicates whether a storage device is capable of storing
 		integrity metadata. Set if the device is T10 PI-capable.
 What:		/sys/block/<disk>/integrity/protection_interval_bytes
 Date:		July 2015
 Contact:	Martin K. Petersen <martin.petersen@oracle.com>
 Description:
 		Describes the number of data bytes which are protected
 		by one integrity tuple. Typically the device's logical
 		block size.
 What:		/sys/block/<disk>/integrity/write_generate
 Date:		June 2008
 Contact:	Martin K. Petersen <martin.petersen@oracle.com>
 Description:
 		Indicates whether the block layer should automatically
 		generate checksums for write requests bound for
 		devices that support receiving integrity metadata.
 What:		/sys/block/<disk>/alignment_offset
 Date:		April 2009
 Contact:	Martin K. Petersen <martin.petersen@oracle.com>
 Description:
 		Storage devices may report a physical block size that is
 		bigger than the logical block size (for instance a drive
 		with 4KB physical sectors exposing 512-byte logical
 		blocks to the operating system).  This parameter
 		indicates how many bytes the beginning of the device is
 		offset from the disk's natural alignment.
 What:		/sys/block/<disk>/<partition>/alignment_offset
 Date:		April 2009
 Contact:	Martin K. Petersen <martin.petersen@oracle.com>
 Description:
 		Storage devices may report a physical block size that is
 		bigger than the logical block size (for instance a drive
 		with 4KB physical sectors exposing 512-byte logical
 		blocks to the operating system).  This parameter
 		indicates how many bytes the beginning of the partition
 		is offset from the disk's natural alignment.
 What:		/sys/block/<disk>/queue/logical_block_size
 Date:		May 2009
 Contact:	Martin K. Petersen <martin.petersen@oracle.com>
 Description:
 		This is the smallest unit the storage device can
 		address.  It is typically 512 bytes.
 What:		/sys/block/<disk>/queue/physical_block_size
 Date:		May 2009
 Contact:	Martin K. Petersen <martin.petersen@oracle.com>
 Description:
 		This is the smallest unit a physical storage device can
 		write atomically.  It is usually the same as the logical
 		block size but may be bigger.  One example is SATA
 		drives with 4KB sectors that expose a 512-byte logical
 		block size to the operating system.  For stacked block
 		devices the physical_block_size variable contains the
 		maximum physical_block_size of the component devices.
 What:		/sys/block/<disk>/queue/minimum_io_size
 Date:		April 2009
 Contact:	Martin K. Petersen <martin.petersen@oracle.com>
 Description:
 		Storage devices may report a granularity or preferred
 		minimum I/O size which is the smallest request the
 		device can perform without incurring a performance
 		penalty.  For disk drives this is often the physical
 		block size.  For RAID arrays it is often the stripe
 		chunk size.  A properly aligned multiple of
 		minimum_io_size is the preferred request size for
 		workloads where a high number of I/O operations is
 		desired.
 What:		/sys/block/<disk>/queue/optimal_io_size
 Date:		April 2009
 Contact:	Martin K. Petersen <martin.petersen@oracle.com>
 Description:
 		Storage devices may report an optimal I/O size, which is
 		the device's preferred unit for sustained I/O.  This is
 		rarely reported for disk drives.  For RAID arrays it is
 		usually the stripe width or the internal track size.  A
 		properly aligned multiple of optimal_io_size is the
 		preferred request size for workloads where sustained
 		throughput is desired.  If no optimal I/O size is
 		reported this file contains 0.
 What:		/sys/block/<disk>/queue/nomerges
 Date:		January 2010
 Contact:
 Description:
 		Standard I/O elevator operations include attempts to
 		merge contiguous I/Os. For known random I/O loads these
 		attempts will always fail and result in extra cycles
 		being spent in the kernel. This allows one to turn off
 		this behavior on one of two ways: When set to 1, complex
 		merge checks are disabled, but the simple one-shot merges
 		with the previous I/O request are enabled. When set to 2,
 		all merge tries are disabled. The default value is 0 -
 		which enables all types of merge tries.
 What:		/sys/block/<disk>/discard_alignment
 Date:		May 2011
 Contact:	Martin K. Petersen <martin.petersen@oracle.com>
 Description:
 		Devices that support discard functionality may
 		internally allocate space in units that are bigger than
 		the exported logical block size. The discard_alignment
 		parameter indicates how many bytes the beginning of the
 		device is offset from the internal allocation unit's
 		natural alignment.
 What:		/sys/block/<disk>/<partition>/discard_alignment
 Date:		May 2011
 Contact:	Martin K. Petersen <martin.petersen@oracle.com>
 Description:
 		Devices that support discard functionality may
 		internally allocate space in units that are bigger than
 		the exported logical block size. The discard_alignment
 		parameter indicates how many bytes the beginning of the
 		partition is offset from the internal allocation unit's
 		natural alignment.
 What:		/sys/block/<disk>/queue/discard_granularity
 Date:		May 2011
 Contact:	Martin K. Petersen <martin.petersen@oracle.com>
 Description:
 		Devices that support discard functionality may
 		internally allocate space using units that are bigger
 		than the logical block size. The discard_granularity
 		parameter indicates the size of the internal allocation
 		unit in bytes if reported by the device. Otherwise the
 		discard_granularity will be set to match the device's
 		physical block size. A discard_granularity of 0 means
 		that the device does not support discard functionality.
 What:		/sys/block/<disk>/queue/discard_max_bytes
 Date:		May 2011
 Contact:	Martin K. Petersen <martin.petersen@oracle.com>
 Description:
 		Devices that support discard functionality may have
 		internal limits on the number of bytes that can be
 		trimmed or unmapped in a single operation. Some storage
 		protocols also have inherent limits on the number of
 		blocks that can be described in a single command. The
 		discard_max_bytes parameter is set by the device driver
 		to the maximum number of bytes that can be discarded in
 		a single operation. Discard requests issued to the
 		device must not exceed this limit. A discard_max_bytes
 		value of 0 means that the device does not support
 		discard functionality.
 What:		/sys/block/<disk>/queue/discard_zeroes_data
 Date:		May 2011
 Contact:	Martin K. Petersen <martin.petersen@oracle.com>
 Description:
 		Will always return 0.  Don't rely on any specific behavior
 		for discards, and don't read this file.
 What:		/sys/block/<disk>/queue/write_same_max_bytes
 Date:		January 2012
 Contact:	Martin K. Petersen <martin.petersen@oracle.com>
 Description:
 		Some devices support a write same operation in which a
 		single data block can be written to a range of several
 		contiguous blocks on storage. This can be used to wipe
 		areas on disk or to initialize drives in a RAID
 		configuration. write_same_max_bytes indicates how many
 		bytes can be written in a single write same command. If
 		write_same_max_bytes is 0, write same is not supported
 		by the device.
 What:		/sys/block/<disk>/queue/write_zeroes_max_bytes
 Date:		November 2016
 Contact:	Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>
 Description:
 		Devices that support write zeroes operation in which a
 		single request can be issued to zero out the range of
 		contiguous blocks on storage without having any payload
 		in the request. This can be used to optimize writing zeroes
 		to the devices. write_zeroes_max_bytes indicates how many
 		bytes can be written in a single write zeroes command. If
 		write_zeroes_max_bytes is 0, write zeroes is not supported
 		by the device.
 What:		/sys/block/<disk>/queue/zoned
 Date:		September 2016
 Contact:	Damien Le Moal <damien.lemoal@wdc.com>
 Description:
 		zoned indicates if the device is a zoned block device
 		and the zone model of the device if it is indeed zoned.
 		The possible values indicated by zoned are "none" for
 		regular block devices and "host-aware" or "host-managed"
 		for zoned block devices. The characteristics of
 		host-aware and host-managed zoned block devices are
 		described in the ZBC (Zoned Block Commands) and ZAC
 		(Zoned Device ATA Command Set) standards. These standards
 		also define the "drive-managed" zone model. However,
 		since drive-managed zoned block devices do not support
 		zone commands, they will be treated as regular block
 		devices and zoned will report "none".
 What:		/sys/block/<disk>/queue/nr_zones
 Date:		November 2018
 Contact:	Damien Le Moal <damien.lemoal@wdc.com>
 Description:
 		nr_zones indicates the total number of zones of a zoned block
 		device ("host-aware" or "host-managed" zone model). For regular
 		block devices, the value is always 0.
 What:		/sys/block/<disk>/queue/max_active_zones
 Date:		July 2020
 Contact:	Niklas Cassel <niklas.cassel@wdc.com>
 Description:
 		For zoned block devices (zoned attribute indicating
 		"host-managed" or "host-aware"), the sum of zones belonging to
 		any of the zone states: EXPLICIT OPEN, IMPLICIT OPEN or CLOSED,
 		is limited by this value. If this value is 0, there is no limit.
 What:		/sys/block/<disk>/queue/max_open_zones
 Date:		July 2020
 Contact:	Niklas Cassel <niklas.cassel@wdc.com>
 Description:
 		For zoned block devices (zoned attribute indicating
 		"host-managed" or "host-aware"), the sum of zones belonging to
 		any of the zone states: EXPLICIT OPEN or IMPLICIT OPEN,
 		is limited by this value. If this value is 0, there is no limit.
 What:		/sys/block/<disk>/queue/chunk_sectors
 Date:		September 2016
 Contact:	Hannes Reinecke <hare@suse.com>
 Description:
 		chunk_sectors has different meaning depending on the type
 		of the disk. For a RAID device (dm-raid), chunk_sectors
 		indicates the size in 512B sectors of the RAID volume
 		stripe segment. For a zoned block device, either
 		host-aware or host-managed, chunk_sectors indicates the
 		size in 512B sectors of the zones of the device, with
 		the eventual exception of the last zone of the device
 		which may be smaller.
 What:		/sys/block/<disk>/queue/io_timeout
 Date:		November 2018
 Contact:	Weiping Zhang <zhangweiping@didiglobal.com>
 Description:
 		io_timeout is the request timeout in milliseconds. If a request
 		does not complete in this time then the block driver timeout
 		handler is invoked. That timeout handler can decide to retry
 		the request, to fail it or to start a device recovery strategy.
--- a/Documentation/ABI/testing/sysfs-bus-bcma
+++ b/Documentation/ABI/testing/sysfs-bus-bcma
@ -3,7 +3,7 @@ Date:		May 2011
 KernelVersion:	3.0
 Contact:	Rafał Miłecki <zajec5@gmail.com>
 Description:
-		Each BCMA core has its manufacturer id. See
+		Each BCMA core has it's manufacturer id. See
 		include/linux/bcma/bcma.h for possible values.
 What:		/sys/bus/bcma/devices/.../id
--- a/Documentation/ABI/testing/sysfs-bus-coresight-devices-etm4x
+++ b/Documentation/ABI/testing/sysfs-bus-coresight-devices-etm4x
@ -516,11 +516,3 @@ Contact:	Mathieu Poirier <mathieu.poirier@linaro.org>
 Description:	(Read) Returns the number of special conditional P1 right-hand keys
 		that the trace unit can use (0x194).  The value is taken
 		directly from the HW.
 What:		/sys/bus/coresight/devices/etm<N>/ts_source
 Date:		October 2022
 KernelVersion:	6.1
 Contact:	Mathieu Poirier <mathieu.poirier@linaro.org> or Suzuki K Poulose <suzuki.poulose@arm.com>
 Description:	(Read) When FEAT_TRF is implemented, value of TRFCR_ELx.TS used for
 		trace session. Otherwise -1 indicates an unknown time source. Check
 		trcidr0.tssize to see if a global timestamp is available.
--- a/Documentation/ABI/testing/sysfs-bus-counter
+++ b/Documentation/ABI/testing/sysfs-bus-counter
@ -4,12 +4,6 @@ Contact:	linux-iio@vger.kernel.org
 Description:
 		Count data of Count Y represented as a string.
 What:		/sys/bus/counter/devices/counterX/countY/capture
 KernelVersion:	6.1
 Contact:	linux-iio@vger.kernel.org
 Description:
 		Historical capture of the Count Y count data.
 What:		/sys/bus/counter/devices/counterX/countY/ceiling
 KernelVersion:	5.2
 Contact:	linux-iio@vger.kernel.org
@ -209,37 +203,6 @@ Description:
 		both edges:
 			Any state transition.
 What:		/sys/bus/counter/devices/counterX/countY/num_overflows
 KernelVersion:	6.1
 Contact:	linux-iio@vger.kernel.org
 Description:
 		This attribute indicates the number of overflows of count Y.
 What:		/sys/bus/counter/devices/counterX/countY/capture_component_id
 What:		/sys/bus/counter/devices/counterX/countY/ceiling_component_id
 What:		/sys/bus/counter/devices/counterX/countY/floor_component_id
 What:		/sys/bus/counter/devices/counterX/countY/count_mode_component_id
 What:		/sys/bus/counter/devices/counterX/countY/direction_component_id
 What:		/sys/bus/counter/devices/counterX/countY/enable_component_id
 What:		/sys/bus/counter/devices/counterX/countY/error_noise_component_id
 What:		/sys/bus/counter/devices/counterX/countY/prescaler_component_id
 What:		/sys/bus/counter/devices/counterX/countY/preset_component_id
 What:		/sys/bus/counter/devices/counterX/countY/preset_enable_component_id
 What:		/sys/bus/counter/devices/counterX/countY/signalZ_action_component_id
 What:		/sys/bus/counter/devices/counterX/countY/num_overflows_component_id
 What:		/sys/bus/counter/devices/counterX/signalY/cable_fault_component_id
 What:		/sys/bus/counter/devices/counterX/signalY/cable_fault_enable_component_id
 What:		/sys/bus/counter/devices/counterX/signalY/filter_clock_prescaler_component_id
 What:		/sys/bus/counter/devices/counterX/signalY/index_polarity_component_id
 What:		/sys/bus/counter/devices/counterX/signalY/polarity_component_id
 What:		/sys/bus/counter/devices/counterX/signalY/synchronous_mode_component_id
 What:		/sys/bus/counter/devices/counterX/signalY/frequency_component_id
 KernelVersion:	5.16
 Contact:	linux-iio@vger.kernel.org
 Description:
 		Read-only attribute that indicates the component ID of the
 		respective extension or Synapse.
 What:		/sys/bus/counter/devices/counterX/countY/spike_filter_ns
 KernelVersion:	5.14
 Contact:	linux-iio@vger.kernel.org
@ -249,14 +212,6 @@ Description:
 		shorter or equal to configured value are ignored. Value 0 means
 		filter is disabled.
 What:		/sys/bus/counter/devices/counterX/events_queue_size
 KernelVersion:	5.16
 Contact:	linux-iio@vger.kernel.org
 Description:
 		Size of the Counter events queue in number of struct
 		counter_event data structures. The number of elements will be
 		rounded-up to a power of 2.
 What:		/sys/bus/counter/devices/counterX/name
 KernelVersion:	5.2
 Contact:	linux-iio@vger.kernel.org
@ -319,19 +274,6 @@ Description:
 		Discrete set of available values for the respective Signal Y
 		configuration are listed in this file.
 What:		/sys/bus/counter/devices/counterX/signalY/polarity
 KernelVersion:	6.1
 Contact:	linux-iio@vger.kernel.org
 Description:
 		Active level of Signal Y. The following polarity values are
 		available:
 		positive:
 			Signal high state considered active level (rising edge).
 		negative:
 			Signal low state considered active level (falling edge).
 What:		/sys/bus/counter/devices/counterX/signalY/name
 KernelVersion:	5.2
 Contact:	linux-iio@vger.kernel.org
@ -344,14 +286,7 @@ What:		/sys/bus/counter/devices/counterX/signalY/signal
 KernelVersion:	5.2
 Contact:	linux-iio@vger.kernel.org
 Description:
-		Signal level state of Signal Y. The following signal level
+		Signal data of Signal Y represented as a string.
 		states are available:
 		low:
 			Low level state.
 		high:
 			High level state.
 What:		/sys/bus/counter/devices/counterX/signalY/synchronous_mode
 KernelVersion:	5.2
@ -374,9 +309,3 @@ Description:
 			via index_polarity. The index function (as enabled via
 			preset_enable) is performed synchronously with the
 			quadrature clock on the active level of the index input.
 What:		/sys/bus/counter/devices/counterX/signalY/frequency
 KernelVersion:	6.1
 Contact:	linux-iio@vger.kernel.org
 Description:
 		Read-only attribute that indicates the signal Y frequency, in Hz.
--- a/Documentation/ABI/testing/sysfs-bus-cxl
+++ b/Documentation/ABI/testing/sysfs-bus-cxl
@ -1,13 +1,3 @@
 What:		/sys/bus/cxl/flush
 Date:		Januarry, 2022
 KernelVersion:	v5.18
 Contact:	linux-cxl@vger.kernel.org
 Description:
 		(WO) If userspace manually unbinds a port the kernel schedules
 		all descendant memdevs for unbind. Writing '1' to this attribute
 		flushes that work.
 What:		/sys/bus/cxl/devices/memX/firmware_version
 Date:		December, 2020
 KernelVersion:	v5.12
@ -17,7 +7,6 @@ Description:
 		Memory Device Output Payload in the CXL-2.0
 		specification.
 What:		/sys/bus/cxl/devices/memX/ram/size
 Date:		December, 2020
 KernelVersion:	v5.12
@ -27,7 +16,6 @@ Description:
 		identically named field in the Identify Memory Device Output
 		Payload in the CXL-2.0 specification.
 What:		/sys/bus/cxl/devices/memX/pmem/size
 Date:		December, 2020
 KernelVersion:	v5.12
@ -37,354 +25,105 @@ Description:
 		identically named field in the Identify Memory Device Output
 		Payload in the CXL-2.0 specification.
 What:		/sys/bus/cxl/devices/memX/serial
 Date:		January, 2022
 KernelVersion:	v5.18
 Contact:	linux-cxl@vger.kernel.org
 Description:
 		(RO) 64-bit serial number per the PCIe Device Serial Number
 		capability. Mandatory for CXL devices, see CXL 2.0 8.1.12.2
 		Memory Device PCIe Capabilities and Extended Capabilities.
 What:		/sys/bus/cxl/devices/memX/numa_node
 Date:		January, 2022
 KernelVersion:	v5.18
 Contact:	linux-cxl@vger.kernel.org
 Description:
 		(RO) If NUMA is enabled and the platform has affinitized the
 		host PCI device for this memory device, emit the CPU node
 		affinity for this device.
 What:		/sys/bus/cxl/devices/*/devtype
 Date:		June, 2021
 KernelVersion:	v5.14
 Contact:	linux-cxl@vger.kernel.org
 Description:
-		(RO) CXL device objects export the devtype attribute which
+		CXL device objects export the devtype attribute which mirrors
-		mirrors the same value communicated in the DEVTYPE environment
+		the same value communicated in the DEVTYPE environment variable
-		variable for uevents for devices on the "cxl" bus.
+		for uevents for devices on the "cxl" bus.
 What:		/sys/bus/cxl/devices/*/modalias
 Date:		December, 2021
 KernelVersion:	v5.18
 Contact:	linux-cxl@vger.kernel.org
 Description:
 		(RO) CXL device objects export the modalias attribute which
 		mirrors the same value communicated in the MODALIAS environment
 		variable for uevents for devices on the "cxl" bus.
 What:		/sys/bus/cxl/devices/portX/uport
 Date:		June, 2021
 KernelVersion:	v5.14
 Contact:	linux-cxl@vger.kernel.org
 Description:
-		(RO) CXL port objects are enumerated from either a platform
+		CXL port objects are enumerated from either a platform firmware
-		firmware device (ACPI0017 and ACPI0016) or PCIe switch upstream
+		device (ACPI0017 and ACPI0016) or PCIe switch upstream port with
-		port with CXL component registers. The 'uport' symlink connects
+		CXL component registers. The 'uport' symlink connects the CXL
-		the CXL portX object to the device that published the CXL port
+		portX object to the device that published the CXL port
 		capability.
 What:		/sys/bus/cxl/devices/portX/dportY
 Date:		June, 2021
 KernelVersion:	v5.14
 Contact:	linux-cxl@vger.kernel.org
 Description:
-		(RO) CXL port objects are enumerated from either a platform
+		CXL port objects are enumerated from either a platform firmware
-		firmware device (ACPI0017 and ACPI0016) or PCIe switch upstream
+		device (ACPI0017 and ACPI0016) or PCIe switch upstream port with
-		port with CXL component registers. The 'dportY' symlink
+		CXL component registers. The 'dportY' symlink identifies one or
-		identifies one or more downstream ports that the upstream port
+		more downstream ports that the upstream port may target in its
-		may target in its decode of CXL memory resources.  The 'Y'
+		decode of CXL memory resources.  The 'Y' integer reflects the
-		integer reflects the hardware port unique-id used in the
+		hardware port unique-id used in the hardware decoder target
-		hardware decoder target list.
+		list.
 What:		/sys/bus/cxl/devices/decoderX.Y
 Date:		June, 2021
 KernelVersion:	v5.14
 Contact:	linux-cxl@vger.kernel.org
 Description:
-		(RO) CXL decoder objects are enumerated from either a platform
+		CXL decoder objects are enumerated from either a platform
 		firmware description, or a CXL HDM decoder register set in a
 		PCIe device (see CXL 2.0 section 8.2.5.12 CXL HDM Decoder
 		Capability Structure). The 'X' in decoderX.Y represents the
 		cxl_port container of this decoder, and 'Y' represents the
 		instance id of a given decoder resource.
 What:		/sys/bus/cxl/devices/decoderX.Y/{start,size}
 Date:		June, 2021
 KernelVersion:	v5.14
 Contact:	linux-cxl@vger.kernel.org
 Description:
-		(RO) The 'start' and 'size' attributes together convey the
+		The 'start' and 'size' attributes together convey the physical
-		physical address base and number of bytes mapped in the
+		address base and number of bytes mapped in the decoder's decode
-		decoder's decode window. For decoders of devtype
+		window. For decoders of devtype "cxl_decoder_root" the address
-		"cxl_decoder_root" the address range is fixed. For decoders of
+		range is fixed. For decoders of devtype "cxl_decoder_switch" the
-		devtype "cxl_decoder_switch" the address is bounded by the
+		address is bounded by the decode range of the cxl_port ancestor
-		decode range of the cxl_port ancestor of the decoder's cxl_port,
+		of the decoder's cxl_port, and dynamically updates based on the
-		and dynamically updates based on the active memory regions in
+		active memory regions in that address space.
 		that address space.
 What:		/sys/bus/cxl/devices/decoderX.Y/locked
 Date:		June, 2021
 KernelVersion:	v5.14
 Contact:	linux-cxl@vger.kernel.org
 Description:
-		(RO) CXL HDM decoders have the capability to lock the
+		CXL HDM decoders have the capability to lock the configuration
-		configuration until the next device reset. For decoders of
+		until the next device reset. For decoders of devtype
-		devtype "cxl_decoder_root" there is no standard facility to
+		"cxl_decoder_root" there is no standard facility to unlock them.
-		unlock them.  For decoders of devtype "cxl_decoder_switch" a
+		For decoders of devtype "cxl_decoder_switch" a secondary bus
-		secondary bus reset, of the PCIe bridge that provides the bus
+		reset, of the PCIe bridge that provides the bus for this
-		for this decoders uport, unlocks / resets the decoder.
+		decoders uport, unlocks / resets the decoder.
 What:		/sys/bus/cxl/devices/decoderX.Y/target_list
 Date:		June, 2021
 KernelVersion:	v5.14
 Contact:	linux-cxl@vger.kernel.org
 Description:
-		(RO) Display a comma separated list of the current decoder
+		Display a comma separated list of the current decoder target
-		target configuration. The list is ordered by the current
+		configuration. The list is ordered by the current configured
-		configured interleave order of the decoder's dport instances.
+		interleave order of the decoder's dport instances. Each entry in
-		Each entry in the list is a dport id.
+		the list is a dport id.
 What:		/sys/bus/cxl/devices/decoderX.Y/cap_{pmem,ram,type2,type3}
 Date:		June, 2021
 KernelVersion:	v5.14
 Contact:	linux-cxl@vger.kernel.org
 Description:
-		(RO) When a CXL decoder is of devtype "cxl_decoder_root", it
+		When a CXL decoder is of devtype "cxl_decoder_root", it
 		represents a fixed memory window identified by platform
 		firmware. A fixed window may only support a subset of memory
 		types. The 'cap_*' attributes indicate whether persistent
 		memory, volatile memory, accelerator memory, and / or expander
 		memory may be mapped behind this decoder's memory window.
 What:		/sys/bus/cxl/devices/decoderX.Y/target_type
 Date:		June, 2021
 KernelVersion:	v5.14
 Contact:	linux-cxl@vger.kernel.org
 Description:
-		(RO) When a CXL decoder is of devtype "cxl_decoder_switch", it
+		When a CXL decoder is of devtype "cxl_decoder_switch", it can
-		can optionally decode either accelerator memory (type-2) or
+		optionally decode either accelerator memory (type-2) or expander
-		expander memory (type-3). The 'target_type' attribute indicates
+		memory (type-3). The 'target_type' attribute indicates the
-		the current setting which may dynamically change based on what
+		current setting which may dynamically change based on what
 		memory regions are activated in this decode hierarchy.
 What:		/sys/bus/cxl/devices/endpointX/CDAT
 Date:		July, 2022
 KernelVersion:	v5.20
 Contact:	linux-cxl@vger.kernel.org
 Description:
 		(RO) If this sysfs entry is not present no DOE mailbox was
 		found to support CDAT data.  If it is present and the length of
 		the data is 0 reading the CDAT data failed.  Otherwise the CDAT
 		data is reported.
 What:		/sys/bus/cxl/devices/decoderX.Y/mode
 Date:		May, 2022
 KernelVersion:	v5.20
 Contact:	linux-cxl@vger.kernel.org
 Description:
 		(RW) When a CXL decoder is of devtype "cxl_decoder_endpoint" it
 		translates from a host physical address range, to a device local
 		address range. Device-local address ranges are further split
 		into a 'ram' (volatile memory) range and 'pmem' (persistent
 		memory) range. The 'mode' attribute emits one of 'ram', 'pmem',
 		'mixed', or 'none'. The 'mixed' indication is for error cases
 		when a decoder straddles the volatile/persistent partition
 		boundary, and 'none' indicates the decoder is not actively
 		decoding, or no DPA allocation policy has been set.
 		'mode' can be written, when the decoder is in the 'disabled'
 		state, with either 'ram' or 'pmem' to set the boundaries for the
 		next allocation.
 What:		/sys/bus/cxl/devices/decoderX.Y/dpa_resource
 Date:		May, 2022
 KernelVersion:	v5.20
 Contact:	linux-cxl@vger.kernel.org
 Description:
 		(RO) When a CXL decoder is of devtype "cxl_decoder_endpoint",
 		and its 'dpa_size' attribute is non-zero, this attribute
 		indicates the device physical address (DPA) base address of the
 		allocation.
 What:		/sys/bus/cxl/devices/decoderX.Y/dpa_size
 Date:		May, 2022
 KernelVersion:	v5.20
 Contact:	linux-cxl@vger.kernel.org
 Description:
 		(RW) When a CXL decoder is of devtype "cxl_decoder_endpoint" it
 		translates from a host physical address range, to a device local
 		address range. The range, base address plus length in bytes, of
 		DPA allocated to this decoder is conveyed in these 2 attributes.
 		Allocations can be mutated as long as the decoder is in the
 		disabled state. A write to 'dpa_size' releases the previous DPA
 		allocation and then attempts to allocate from the free capacity
 		in the device partition referred to by 'decoderX.Y/mode'.
 		Allocate and free requests can only be performed on the highest
 		instance number disabled decoder with non-zero size. I.e.
 		allocations are enforced to occur in increasing 'decoderX.Y/id'
 		order and frees are enforced to occur in decreasing
 		'decoderX.Y/id' order.
 What:		/sys/bus/cxl/devices/decoderX.Y/interleave_ways
 Date:		May, 2022
 KernelVersion:	v5.20
 Contact:	linux-cxl@vger.kernel.org
 Description:
 		(RO) The number of targets across which this decoder's host
 		physical address (HPA) memory range is interleaved. The device
 		maps every Nth block of HPA (of size ==
 		'interleave_granularity') to consecutive DPA addresses. The
 		decoder's position in the interleave is determined by the
 		device's (endpoint or switch) switch ancestry. For root
 		decoders their interleave is specified by platform firmware and
 		they only specify a downstream target order for host bridges.
 What:		/sys/bus/cxl/devices/decoderX.Y/interleave_granularity
 Date:		May, 2022
 KernelVersion:	v5.20
 Contact:	linux-cxl@vger.kernel.org
 Description:
 		(RO) The number of consecutive bytes of host physical address
 		space this decoder claims at address N before the decode rotates
 		to the next target in the interleave at address N +
 		interleave_granularity (assuming N is aligned to
 		interleave_granularity).
 What:		/sys/bus/cxl/devices/decoderX.Y/create_pmem_region
 Date:		May, 2022
 KernelVersion:	v5.20
 Contact:	linux-cxl@vger.kernel.org
 Description:
 		(RW) Write a string in the form 'regionZ' to start the process
 		of defining a new persistent memory region (interleave-set)
 		within the decode range bounded by root decoder 'decoderX.Y'.
 		The value written must match the current value returned from
 		reading this attribute. An atomic compare exchange operation is
 		done on write to assign the requested id to a region and
 		allocate the region-id for the next creation attempt. EBUSY is
 		returned if the region name written does not match the current
 		cached value.
 What:		/sys/bus/cxl/devices/decoderX.Y/delete_region
 Date:		May, 2022
 KernelVersion:	v5.20
 Contact:	linux-cxl@vger.kernel.org
 Description:
 		(WO) Write a string in the form 'regionZ' to delete that region,
 		provided it is currently idle / not bound to a driver.
 What:		/sys/bus/cxl/devices/regionZ/uuid
 Date:		May, 2022
 KernelVersion:	v5.20
 Contact:	linux-cxl@vger.kernel.org
 Description:
 		(RW) Write a unique identifier for the region. This field must
 		be set for persistent regions and it must not conflict with the
 		UUID of another region.
 What:		/sys/bus/cxl/devices/regionZ/interleave_granularity
 Date:		May, 2022
 KernelVersion:	v5.20
 Contact:	linux-cxl@vger.kernel.org
 Description:
 		(RW) Set the number of consecutive bytes each device in the
 		interleave set will claim. The possible interleave granularity
 		values are determined by the CXL spec and the participating
 		devices.
 What:		/sys/bus/cxl/devices/regionZ/interleave_ways
 Date:		May, 2022
 KernelVersion:	v5.20
 Contact:	linux-cxl@vger.kernel.org
 Description:
 		(RW) Configures the number of devices participating in the
 		region is set by writing this value. Each device will provide
 		1/interleave_ways of storage for the region.
 What:		/sys/bus/cxl/devices/regionZ/size
 Date:		May, 2022
 KernelVersion:	v5.20
 Contact:	linux-cxl@vger.kernel.org
 Description:
 		(RW) System physical address space to be consumed by the region.
 		When written trigger the driver to allocate space out of the
 		parent root decoder's address space. When read the size of the
 		address space is reported and should match the span of the
 		region's resource attribute. Size shall be set after the
 		interleave configuration parameters. Once set it cannot be
 		changed, only freed by writing 0. The kernel makes no guarantees
 		that data is maintained over an address space freeing event, and
 		there is no guarantee that a free followed by an allocate
 		results in the same address being allocated.
 What:		/sys/bus/cxl/devices/regionZ/resource
 Date:		May, 2022
 KernelVersion:	v5.20
 Contact:	linux-cxl@vger.kernel.org
 Description:
 		(RO) A region is a contiguous partition of a CXL root decoder
 		address space. Region capacity is allocated by writing to the
 		size attribute, the resulting physical address space determined
 		by the driver is reflected here. It is therefore not useful to
 		read this before writing a value to the size attribute.
 What:		/sys/bus/cxl/devices/regionZ/target[0..N]
 Date:		May, 2022
 KernelVersion:	v5.20
 Contact:	linux-cxl@vger.kernel.org
 Description:
 		(RW) Write an endpoint decoder object name to 'targetX' where X
 		is the intended position of the endpoint device in the region
 		interleave and N is the 'interleave_ways' setting for the
 		region. ENXIO is returned if the write results in an impossible
 		to map decode scenario, like the endpoint is unreachable at that
 		position relative to the root decoder interleave. EBUSY is
 		returned if the position in the region is already occupied, or
 		if the region is not in a state to accept interleave
 		configuration changes. EINVAL is returned if the object name is
 		not an endpoint decoder. Once all positions have been
 		successfully written a final validation for decode conflicts is
 		performed before activating the region.
 What:		/sys/bus/cxl/devices/regionZ/commit
 Date:		May, 2022
 KernelVersion:	v5.20
 Contact:	linux-cxl@vger.kernel.org
 Description:
 		(RW) Write a boolean 'true' string value to this attribute to
 		trigger the region to transition from the software programmed
 		state to the actively decoding in hardware state. The commit
 		operation in addition to validating that the region is in proper
 		configured state, validates that the decoders are being
 		committed in spec mandated order (last committed decoder id +
 		1), and checks that the hardware accepts the commit request.
 		Reading this value indicates whether the region is committed or
 		not.
--- a/Documentation/ABI/testing/sysfs-bus-event_source-devices-caps
+++ b/Documentation/ABI/testing/sysfs-bus-event_source-devices-caps
@ -1,18 +0,0 @@
 What:		/sys/bus/event_source/devices/<dev>/caps
 Date:		May 2022
 KernelVersion:	5.19
 Contact:	Linux kernel mailing list <linux-kernel@vger.kernel.org>
 Description:
 		Attribute group to describe the capabilities exposed
 		for a particular pmu. Each attribute of this group can
 		expose information specific to a PMU, say pmu_name, so that
 		userspace can understand some of the feature which the
 		platform specific PMU supports.
 		One of the example available capability in supported platform
 		like Intel is pmu_name, which exposes underlying CPU name known
 		to the PMU driver.
 		Example output in powerpc:
 		grep . /sys/bus/event_source/devices/cpu/caps/*
 		/sys/bus/event_source/devices/cpu/caps/pmu_name:POWER9
--- a/Documentation/ABI/testing/sysfs-bus-fcoe
+++ b/Documentation/ABI/testing/sysfs-bus-fcoe
@ -31,7 +31,7 @@ Description:	'FCoE Controller' instances on the fcoe bus.
 		1) Write interface name to ctlr_create 2) Configure the FCoE
 		Controller (ctlr_X) 3) Enable the FCoE Controller to begin
 		discovery and login. The FCoE Controller is destroyed by
-		writing its name, i.e. ctlr_X to the ctlr_delete file.
+		writing it's name, i.e. ctlr_X to the ctlr_delete file.
 Attributes:
--- a/Documentation/ABI/testing/sysfs-bus-fsi-devices-sbefifo
+++ b/Documentation/ABI/testing/sysfs-bus-fsi-devices-sbefifo
@ -1,10 +0,0 @@
 What:		/sys/bus/fsi/devices/XX.XX.00:06/sbefifoX/timeout
 KernelVersion:	5.15
 Contact:	eajames@linux.ibm.com
 Description:
 		Indicates whether or not this SBE device has experienced a
 		timeout; i.e. the SBE did not respond within the time allotted
 		by the driver. A value of 1 indicates that a timeout has
 		ocurred and no transfers have completed since the timeout. A
 		value of 0 indicates that no timeout has ocurred, or if one
 		has, more recent transfers have completed successful.
--- a/Documentation/ABI/testing/sysfs-bus-iio
+++ b/Documentation/ABI/testing/sysfs-bus-iio
@ -79,11 +79,6 @@ Description:
 		* "accel-base"
 		* "accel-display"
 		For devices where an accelerometer is housed in the swivel camera subassembly
 		(for AR application), the following standardized label is used:
 		* "accel-camera"
 What:		/sys/bus/iio/devices/iio:deviceX/current_timestamp_clock
 KernelVersion:	4.5
 Contact:	linux-iio@vger.kernel.org
@ -107,9 +102,6 @@ Description:
 		relevant directories.  If it affects all of the above
 		then it is to be found in the base device directory.
 		The stm32-timer-trigger has the additional characteristic that
 		a sampling_frequency of 0 is defined to stop sampling.
 What:		/sys/bus/iio/devices/iio:deviceX/sampling_frequency_available
 What:		/sys/bus/iio/devices/iio:deviceX/in_intensity_sampling_frequency_available
 What:		/sys/bus/iio/devices/iio:deviceX/in_proximity_sampling_frequency_available
@ -196,7 +188,7 @@ Description:
 		Raw capacitance measurement from channel Y. Units after
 		application of scale and offset are nanofarads.
-What:		/sys/.../iio:deviceX/in_capacitanceY-capacitanceZ_raw
+What:		/sys/.../iio:deviceX/in_capacitanceY-in_capacitanceZ_raw
 KernelVersion:	3.2
 Contact:	linux-iio@vger.kernel.org
 Description:
@ -207,25 +199,6 @@ Description:
 		is required is a consistent labeling.  Units after application
 		of scale and offset are nanofarads.
 What:		/sys/.../iio:deviceX/in_capacitanceY-capacitanceZ_zeropoint
 KernelVersion:	6.1
 Contact:	linux-iio@vger.kernel.org
 Description:
 		For differential channels, this an offset that is applied
 		equally to both inputs. As the reading is of the difference
 		between the two inputs, this should not be applied to the _raw
 		reading by userspace (unlike _offset) and unlike calibbias
 		it does not affect the differential value measured because
 		the effect of _zeropoint cancels out across the two inputs
 		that make up the differential pair. It's purpose is to bring
 		the individual signals, before the differential is measured,
 		within the measurement range of the device. The naming is
 		chosen because if the separate inputs that make the
 		differential pair are drawn on a graph in their
 		_raw  units, this is the value that the zero point on the
 		measurement axis represents. It is expressed with the
 		same scaling as _raw.
 What:		/sys/bus/iio/devices/iio:deviceX/in_temp_raw
 What:		/sys/bus/iio/devices/iio:deviceX/in_tempX_raw
 What:		/sys/bus/iio/devices/iio:deviceX/in_temp_x_raw
@ -260,15 +233,6 @@ Description:
 		Has all of the equivalent parameters as per voltageY. Units
 		after application of scale and offset are m/s^2.
 What:		/sys/bus/iio/devices/iio:deviceX/in_accel_linear_x_raw
 What:		/sys/bus/iio/devices/iio:deviceX/in_accel_linear_y_raw
 What:		/sys/bus/iio/devices/iio:deviceX/in_accel_linear_z_raw
 KernelVersion:	6.1
 Contact:	linux-iio@vger.kernel.org
 Description:
 		As per in_accel_X_raw attributes, but minus the
 		acceleration due to gravity.
 What:		/sys/bus/iio/devices/iio:deviceX/in_gravity_x_raw
 What:		/sys/bus/iio/devices/iio:deviceX/in_gravity_y_raw
 What:		/sys/bus/iio/devices/iio:deviceX/in_gravity_z_raw
@ -465,7 +429,6 @@ What:		/sys/bus/iio/devices/iio:deviceX/in_angl_scale
 What:		/sys/bus/iio/devices/iio:deviceX/in_intensity_x_scale
 What:		/sys/bus/iio/devices/iio:deviceX/in_intensity_y_scale
 What:		/sys/bus/iio/devices/iio:deviceX/in_intensity_z_scale
 What:		/sys/bus/iio/devices/iio:deviceX/in_concentration_co2_scale
 KernelVersion:	2.6.35
 Contact:	linux-iio@vger.kernel.org
 Description:
@ -512,7 +475,6 @@ What:		/sys/bus/iio/devices/iio:deviceX/in_voltageY_i_calibscale
 What:		/sys/bus/iio/devices/iio:deviceX/in_voltageY_q_calibscale
 What:		/sys/bus/iio/devices/iio:deviceX/in_voltage_i_calibscale
 What:		/sys/bus/iio/devices/iio:deviceX/in_voltage_q_calibscale
 What:		/sys/bus/iio/devices/iio:deviceX/in_altvoltage_calibscale
 What:		/sys/bus/iio/devices/iio:deviceX/in_voltage_calibscale
 What:		/sys/bus/iio/devices/iio:deviceX/in_accel_x_calibscale
 What:		/sys/bus/iio/devices/iio:deviceX/in_accel_y_calibscale
@ -1250,32 +1212,6 @@ Description:
 		number or direction is not specified, applies to all channels of
 		this type.
 What:		/sys/.../iio:deviceX/events/in_accel_mag_referenced_en
 What:		/sys/.../iio:deviceX/events/in_accel_mag_referenced_rising_en
 What:		/sys/.../iio:deviceX/events/in_accel_mag_referenced_falling_en
 What:		/sys/.../iio:deviceX/events/in_accel_y_mag_referenced_en
 What:		/sys/.../iio:deviceX/events/in_accel_y_mag_referenced_rising_en
 What:		/sys/.../iio:deviceX/events/in_accel_y_mag_referenced_falling_en
 KernelVersion:	5.18
 Contact:	linux-iio@vger.kernel.org
 Description:
 		Similar to in_accel_mag[_y][_rising|_falling]_en, but the event
 		value is relative to a reference magnitude. The reference magnitude
 		includes the graviational acceleration.
 What:		/sys/.../iio:deviceX/events/in_accel_mag_referenced_value
 What:		/sys/.../iio:deviceX/events/in_accel_mag_referenced_rising_value
 What:		/sys/.../iio:deviceX/events/in_accel_mag_referenced_falling_value
 What:		/sys/.../iio:deviceX/events/in_accel_y_mag_referenced_value
 What:		/sys/.../iio:deviceX/events/in_accel_y_mag_referenced_rising_value
 What:		/sys/.../iio:deviceX/events/in_accel_y_mag_referenced_falling_value
 KernelVersion:	5.18
 Contact:	linux-iio@vger.kernel.org
 Description:
 		The value to which the reference magnitude of the channel is
 		compared. If the axis is not specified, it applies to all channels
 		of this type.
 What:		/sys/.../events/in_steps_change_en
 KernelVersion:	4.0
 Contact:	linux-iio@vger.kernel.org
@ -1315,10 +1251,6 @@ Description:
 		Actually start the buffer capture up.  Will start trigger
 		if first device and appropriate.
 		Note that it might be impossible to configure other attributes,
 		(e.g.: events, scale, sampling rate) if they impact the currently
 		active buffer capture session.
 What:		/sys/bus/iio/devices/iio:deviceX/bufferY
 KernelVersion:	5.11
 Contact:	linux-iio@vger.kernel.org
@ -2025,140 +1957,3 @@ Description:
 		Specify the percent for light sensor relative to the channel
 		absolute value that a data field should change before an event
 		is generated. Units are a percentage of the prior reading.
 What:		/sys/bus/iio/devices/iio:deviceX/calibration_auto_enable
 Date:		June 2020
 KernelVersion:	5.8
 Contact:	linux-iio@vger.kernel.org
 Description:
 		Some sensors have the ability to apply auto calibration at
 		runtime. For example, it may be necessary to compensate for
 		contaminant build-up in a measurement chamber or optical
 		element deterioration that would otherwise lead to sensor drift.
 		Writing 1 or 0 to this attribute will respectively activate or
 		deactivate this auto calibration function.
 		Upon reading, the current status is returned.
 What:		/sys/bus/iio/devices/iio:deviceX/calibration_forced_value
 Date:		June 2020
 KernelVersion:	5.8
 Contact:	linux-iio@vger.kernel.org
 Description:
 		Some sensors have the ability to apply a manual calibration using
 		a known measurement value, perhaps obtained from an external
 		reference device.
 		Writing a value to this function will force such a calibration
 		change. For the scd30 the value should be from the range
 		[400 1 2000].
 		Note for the scd30 that a valid value may only be obtained once
 		it is has been written. Until then any read back of this value
 		should be ignored. As for the scd4x an error will be returned
 		immediately if the manual calibration has failed.
 What:		/sys/bus/iio/devices/iio:deviceX/calibration_forced_value_available
 KernelVersion:  5.15
 Contact:        linux-iio@vger.kernel.org
 Description:
 		Available range for the forced calibration value, expressed as:
 		- a range specified as "[min step max]"
 What:		/sys/bus/iio/devices/iio:deviceX/in_voltageX_sampling_frequency
 What:		/sys/bus/iio/devices/iio:deviceX/in_powerY_sampling_frequency
 What:		/sys/bus/iio/devices/iio:deviceX/in_currentZ_sampling_frequency
 KernelVersion:	5.20
 Contact:	linux-iio@vger.kernel.org
 Description:
 		Some devices have separate controls of sampling frequency for
 		individual channels. If multiple channels are enabled in a scan,
 		then the sampling_frequency of the scan may be computed from the
 		per channel sampling frequencies.
 What:		/sys/.../events/in_accel_gesture_singletap_en
 What:		/sys/.../events/in_accel_gesture_doubletap_en
 KernelVersion:	6.1
 Contact:	linux-iio@vger.kernel.org
 Description:
 		Device generates an event on a single or double tap.
 What:		/sys/.../events/in_accel_gesture_singletap_value
 What:		/sys/.../events/in_accel_gesture_doubletap_value
 KernelVersion:	6.1
 Contact:	linux-iio@vger.kernel.org
 Description:
 		Specifies the threshold value that the device is comparing
 		against to generate the tap gesture event. The lower
 		threshold value increases the sensitivity of tap detection.
 		Units and the exact meaning of value are device-specific.
 What:		/sys/.../events/in_accel_gesture_tap_value_available
 KernelVersion:	6.1
 Contact:	linux-iio@vger.kernel.org
 Description:
 		Lists all available threshold values which can be used to
 		modify the sensitivity of the tap detection.
 What:		/sys/.../events/in_accel_gesture_singletap_reset_timeout
 What:		/sys/.../events/in_accel_gesture_doubletap_reset_timeout
 KernelVersion:	6.1
 Contact:	linux-iio@vger.kernel.org
 Description:
 		Specifies the timeout value in seconds for the tap detector
 		to not to look for another tap event after the event as
 		occurred. Basically the minimum quiet time between the two
 		single-tap's or two double-tap's.
 What:		/sys/.../events/in_accel_gesture_tap_reset_timeout_available
 KernelVersion:	6.1
 Contact:	linux-iio@vger.kernel.org
 Description:
 		Lists all available tap reset timeout values. Units in seconds.
 What:		/sys/.../events/in_accel_gesture_doubletap_tap2_min_delay
 KernelVersion:	6.1
 Contact:	linux-iio@vger.kernel.org
 Description:
 		Specifies the minimum quiet time in seconds between the two
 		taps of a double tap.
 What:		/sys/.../events/in_accel_gesture_doubletap_tap2_min_delay_available
 KernelVersion:	6.1
 Contact:	linux-iio@vger.kernel.org
 Description:
 		Lists all available delay values between two taps in the double
 		tap. Units in seconds.
 What:		/sys/.../events/in_accel_gesture_tap_maxtomin_time
 KernelVersion:	6.1
 Contact:	linux-iio@vger.kernel.org
 Description:
 		Specifies the maximum time difference allowed between upper
 		and lower peak of tap to consider it as the valid tap event.
 		Units in seconds.
 What:		/sys/.../events/in_accel_gesture_tap_maxtomin_time_available
 KernelVersion:	6.1
 Contact:	linux-iio@vger.kernel.org
 Description:
 		Lists all available time values between upper peak to lower
 		peak. Units in seconds.
 What:		/sys/bus/iio/devices/iio:deviceX/in_rot_yaw_raw
 What:		/sys/bus/iio/devices/iio:deviceX/in_rot_pitch_raw
 What:		/sys/bus/iio/devices/iio:deviceX/in_rot_roll_raw
 KernelVersion:	6.1
 Contact:	linux-iio@vger.kernel.org
 Description:
 		Raw (unscaled) euler angles readings. Units after
 		application of scale are deg.
 What:		/sys/bus/iio/devices/iio:deviceX/serialnumber
 KernelVersion:	6.1
 Contact:	linux-iio@vger.kernel.org
 Description:
 		An example format is 16-bytes, 2-digits-per-byte, HEX-string
 		representing the sensor unique ID number.
--- a/Documentation/ABI/testing/sysfs-bus-iio-adc-ad7280a
+++ b/Documentation/ABI/testing/sysfs-bus-iio-adc-ad7280a
@ -1,13 +0,0 @@
 What:		/sys/bus/iio/devices/iio:deviceX/in_voltageY-voltageZ_balance_switch_en
 KernelVersion:	5.14
 Contact:	linux-iio@vger.kernel.org
 Description:
 		Used to enable an output for balancing cells for time
 		controlled via in_voltage_Y-voltageZ_balance_switch_timer.
 What:		/sys/bus/iio/devices/iio:deviceX/in_voltageY-voltageZ_balance_switch_timer
 KernelVersion:	5.14
 Contact:	linux-iio@vger.kernel.org
 Description:
 		Time in seconds for which balance switch will be turned on.
 		Multiple of 71.5 seconds.
--- a/Documentation/ABI/testing/sysfs-bus-iio-bno055
+++ b/Documentation/ABI/testing/sysfs-bus-iio-bno055
@ -1,81 +0,0 @@
 What:		/sys/bus/iio/devices/iio:deviceX/in_accel_raw_range
 KernelVersion:	6.1
 Contact:	linux-iio@vger.kernel.org
 Description:
 		Raw (unscaled) range for acceleration readings. Unit after
 		application of scale is m/s^2. Note that this doesn't affects
 		the scale (which should be used when changing the maximum and
 		minimum readable value affects also the reading scaling factor).
 What:		/sys/bus/iio/devices/iio:deviceX/in_anglvel_raw_range
 KernelVersion:	6.1
 Contact:	linux-iio@vger.kernel.org
 Description:
 		Range for angular velocity readings in radians per second. Note
 		that this does not affects the scale (which should be used when
 		changing the maximum and minimum readable value affects also the
 		reading scaling factor).
 What:		/sys/bus/iio/devices/iio:deviceX/in_accel_raw_range_available
 KernelVersion:	6.1
 Contact:	linux-iio@vger.kernel.org
 Description:
 		List of allowed values for in_accel_raw_range attribute
 What:		/sys/bus/iio/devices/iio:deviceX/in_anglvel_raw_range_available
 KernelVersion:	6.1
 Contact:	linux-iio@vger.kernel.org
 Description:
 		List of allowed values for in_anglvel_raw_range attribute
 What:		/sys/bus/iio/devices/iio:deviceX/in_magn_calibration_fast_enable
 KernelVersion:	6.1
 Contact:	linux-iio@vger.kernel.org
 Description:
 		Can be 1 or 0. Enables/disables the "Fast Magnetometer
 		Calibration" HW function.
 What:		/sys/bus/iio/devices/iio:deviceX/fusion_enable
 KernelVersion:	6.1
 Contact:	linux-iio@vger.kernel.org
 Description:
 		Can be 1 or 0. Enables/disables the "sensor fusion" (a.k.a.
 		NDOF) HW function.
 What:		/sys/bus/iio/devices/iio:deviceX/calibration_data
 KernelVersion:	6.1
 Contact:	linux-iio@vger.kernel.org
 Description:
 		Reports the binary calibration data blob for the IMU sensors.
 What:		/sys/bus/iio/devices/iio:deviceX/in_accel_calibration_auto_status
 KernelVersion:	6.1
 Contact:	linux-iio@vger.kernel.org
 Description:
 		Reports the autocalibration status for the accelerometer sensor.
 		Can be 0 (calibration non even enabled) or 1 to 5 where the greater
 		the number, the better the calibration status.
 What:		/sys/bus/iio/devices/iio:deviceX/in_gyro_calibration_auto_status
 KernelVersion:	6.1
 Contact:	linux-iio@vger.kernel.org
 Description:
 		Reports the autocalibration status for the gyroscope sensor.
 		Can be 0 (calibration non even enabled) or 1 to 5 where the greater
 		the number, the better the calibration status.
 What:		/sys/bus/iio/devices/iio:deviceX/in_magn_calibration_auto_status
 KernelVersion:	6.1
 Contact:	linux-iio@vger.kernel.org
 Description:
 		Reports the autocalibration status for the magnetometer sensor.
 		Can be 0 (calibration non even enabled) or 1 to 5 where the greater
 		the number, the better the calibration status.
 What:		/sys/bus/iio/devices/iio:deviceX/sys_calibration_auto_status
 KernelVersion:	6.1
 Contact:	linux-iio@vger.kernel.org
 Description:
 		Reports the status for the IMU overall autocalibration.
 		Can be 0 (calibration non even enabled) or 1 to 5 where the greater
 		the number, the better the calibration status.
--- a/Documentation/ABI/testing/sysfs-bus-iio-cdc-ad7746
+++ b/Documentation/ABI/testing/sysfs-bus-iio-cdc-ad7746
@ -1,11 +0,0 @@
 What:		/sys/.../iio:deviceX/in_capacitableY_calibbias_calibration
 What:		/sys/.../iio:deviceX/in_capacitableY_calibscale_calibration
 KernelVersion:	6.1
 Contact:	linux-iio@vger.kernel.org
 Description:
 		Write 1 to trigger a calibration of the calibbias or
 		calibscale. For calibscale, a full scale capacitance should
 		be connected to the capacitance input and a
 		calibscale_calibration then started.  For calibbias see
 		the device datasheet section on "capacitive system offset
 		calibration".
--- a/Documentation/ABI/testing/sysfs-bus-iio-chemical-sunrise-co2
+++ b/Documentation/ABI/testing/sysfs-bus-iio-chemical-sunrise-co2
@ -1,38 +0,0 @@
 What:		/sys/bus/iio/devices/iio:deviceX/in_concentration_co2_calibration_factory
 Date:		August 2021
 KernelVersion:	5.16
 Contact:	Jacopo Mondi <jacopo@jmondi.org>
 Description:
 		Writing '1' triggers a 'Factory' calibration cycle.
 What:		/sys/bus/iio/devices/iio:deviceX/in_concentration_co2_calibration_background
 Date:		August 2021
 KernelVersion:	5.16
 Contact:	Jacopo Mondi <jacopo@jmondi.org>
 Description:
 		Writing '1' triggers a 'Background' calibration cycle.
 What:		/sys/bus/iio/devices/iio:deviceX/error_status_available
 Date:		August 2021
 KernelVersion:	5.16
 Contact:	Jacopo Mondi <jacopo@jmondi.org>
 Description:
 		Reading returns the list of possible chip error status.
 		Available options are:
 		- 'error_fatal': Analog front-end initialization error
 		- 'error_i2c': Read/write to non-existing register
 		- 'error_algorithm': Corrupted parameters
 		- 'error_calibration': Calibration has failed
 		- 'error_self_diagnostic': Internal interface failure
 		- 'error_out_of_range': Measured concentration out of scale
 		- 'error_memory': Error during memory operations
 		- 'error_no_measurement': Cleared at first measurement
 		- 'error_low_voltage': Sensor regulated voltage too low
 		- 'error_measurement_timeout': Unable to complete measurement
 What:		/sys/bus/iio/devices/iio:deviceX/error_status
 Date:		August 2021
 KernelVersion:	5.16
 Contact:	Jacopo Mondi <jacopo@jmondi.org>
 Description:
 		Reading returns the current chip error status.
--- a/Documentation/ABI/testing/sysfs-bus-iio-dac-ltc2688
+++ b/Documentation/ABI/testing/sysfs-bus-iio-dac-ltc2688
@ -1,86 +0,0 @@
 What:		/sys/bus/iio/devices/iio:deviceX/out_voltageY_dither_en
 KernelVersion:	5.18
 Contact:	linux-iio@vger.kernel.org
 Description:
 		Dither enable. Write 1 to enable dither or 0 to disable it. This is useful
 		for changing the dither parameters. They way it should be done is:
 		- disable dither operation;
 		- change dither parameters (eg: frequency, phase...);
 		- enabled dither operation
 What:		/sys/bus/iio/devices/iio:deviceX/out_voltageY_dither_raw
 KernelVersion:	5.18
 Contact:	linux-iio@vger.kernel.org
 Description:
 		This raw, unscaled value refers to the dither signal amplitude.
 		The same scale as in out_voltageY_raw applies. However, the
 		offset might be different as it's always 0 for this attribute.
 What:		/sys/bus/iio/devices/iio:deviceX/out_voltageY_dither_raw_available
 KernelVersion:	5.18
 Contact:	linux-iio@vger.kernel.org
 Description:
 		Available range for dither raw amplitude values.
 What:		/sys/bus/iio/devices/iio:deviceX/out_voltageY_dither_offset
 KernelVersion:	5.18
 Contact:	linux-iio@vger.kernel.org
 Description:
 		Offset applied to out_voltageY_dither_raw. Read only attribute
 		always set to 0.
 What:		/sys/bus/iio/devices/iio:deviceX/out_voltageY_dither_frequency
 KernelVersion:	5.18
 Contact:	linux-iio@vger.kernel.org
 Description:
 		Sets the dither signal frequency. Units are in Hz.
 What:		/sys/bus/iio/devices/iio:deviceX/out_voltageY_dither_frequency_available
 KernelVersion:	5.18
 Contact:	linux-iio@vger.kernel.org
 Description:
 		Returns the available values for the dither frequency.
 What:		/sys/bus/iio/devices/iio:deviceX/out_voltageY_dither_phase
 KernelVersion:	5.18
 Contact:	linux-iio@vger.kernel.org
 Description:
 		Sets the dither signal phase. Units are in Radians.
 What:		/sys/bus/iio/devices/iio:deviceX/out_voltageY_dither_phase_available
 KernelVersion:	5.18
 Contact:	linux-iio@vger.kernel.org
 Description:
 		Returns the available values for the dither phase.
 What:		/sys/bus/iio/devices/iio:deviceX/out_voltageY_toggle_en
 KernelVersion:	5.18
 Contact:	linux-iio@vger.kernel.org
 Description:
 		Toggle enable. Write 1 to enable toggle or 0 to disable it. This is
 		useful when one wants to change the DAC output codes. The way it should
 		be done is:
 		- disable toggle operation;
 		- change out_voltageY_raw0 and out_voltageY_raw1;
 		- enable toggle operation.
 What:		/sys/bus/iio/devices/iio:deviceX/out_voltageY_raw0
 What:		/sys/bus/iio/devices/iio:deviceX/out_voltageY_raw1
 KernelVersion:	5.18
 Contact:	linux-iio@vger.kernel.org
 Description:
 		It has the same meaning as out_voltageY_raw. This attribute is
 		specific to toggle enabled channels and refers to the DAC output
 		code in INPUT_A (_raw0) and INPUT_B (_raw1). The same scale and offset
 		as in out_voltageY_raw applies.
 What:		/sys/bus/iio/devices/iio:deviceX/out_voltageY_symbol
 KernelVersion:	5.18
 Contact:	linux-iio@vger.kernel.org
 Description:
 		Performs a SW toggle. This attribute is specific to toggle
 		enabled channels and allows to toggle between out_voltageY_raw0
 		and out_voltageY_raw1 through software. Writing 0 will select
 		out_voltageY_raw0 while 1 selects out_voltageY_raw1.
--- a/Documentation/ABI/testing/sysfs-bus-iio-filter-admv8818
+++ b/Documentation/ABI/testing/sysfs-bus-iio-filter-admv8818
@ -1,16 +0,0 @@
 What:		/sys/bus/iio/devices/iio:deviceX/filter_mode_available
 KernelVersion:
 Contact:	linux-iio@vger.kernel.org
 Description:
 		Reading this returns the valid values that can be written to the
 		on_altvoltage0_mode attribute:
 		- auto -> Adjust bandpass filter to track changes in input clock rate.
 		- manual -> disable/unregister the clock rate notifier / input clock tracking.
 What:		/sys/bus/iio/devices/iio:deviceX/filter_mode
 KernelVersion:
 Contact:	linux-iio@vger.kernel.org
 Description:
 		This attribute configures the filter mode.
 		Reading returns the actual mode.
--- a/Documentation/ABI/testing/sysfs-bus-iio-frequency-admv1013
+++ b/Documentation/ABI/testing/sysfs-bus-iio-frequency-admv1013
@ -1,38 +0,0 @@
 What:		/sys/bus/iio/devices/iio:deviceX/in_altvoltage0-1_i_calibphase
 KernelVersion:
 Contact:	linux-iio@vger.kernel.org
 Description:
 		Read/write unscaled value for the Local Oscillatior path quadrature I phase shift.
 What:		/sys/bus/iio/devices/iio:deviceX/in_altvoltage0-1_q_calibphase
 KernelVersion:
 Contact:	linux-iio@vger.kernel.org
 Description:
 		Read/write unscaled value for the Local Oscillatior path quadrature Q phase shift.
 What:		/sys/bus/iio/devices/iio:deviceX/in_altvoltage0_i_calibbias
 KernelVersion:
 Contact:	linux-iio@vger.kernel.org
 Description:
 		Read/write value for the Local Oscillatior Feedthrough Offset Calibration I Positive
 		side.
 What:		/sys/bus/iio/devices/iio:deviceX/in_altvoltage0_q_calibbias
 KernelVersion:
 Contact:	linux-iio@vger.kernel.org
 Description:
 		Read/write value for the Local Oscillatior Feedthrough Offset Calibration Q Positive side.
 What:		/sys/bus/iio/devices/iio:deviceX/in_altvoltage1_i_calibbias
 KernelVersion:
 Contact:	linux-iio@vger.kernel.org
 Description:
 		Read/write raw value for the Local Oscillatior Feedthrough Offset Calibration I Negative
 		side.
 What:		/sys/bus/iio/devices/iio:deviceX/in_altvoltage1_q_calibbias
 KernelVersion:
 Contact:	linux-iio@vger.kernel.org
 Description:
 		Read/write raw value for the Local Oscillatior Feedthrough Offset Calibration Q Negative
 		side.
--- a/Documentation/ABI/testing/sysfs-bus-iio-frequency-admv1014
+++ b/Documentation/ABI/testing/sysfs-bus-iio-frequency-admv1014
@ -1,23 +0,0 @@
 What:		/sys/bus/iio/devices/iio:deviceX/in_altvoltage0_i_calibscale_coarse
 KernelVersion: 5.18
 Contact:	linux-iio@vger.kernel.org
 Description:
 		Read/write value for the digital attenuator gain (IF_I) with coarse steps.
 What:		/sys/bus/iio/devices/iio:deviceX/in_altvoltage0_q_calibscale_coarse
 KernelVersion: 5.18
 Contact:	linux-iio@vger.kernel.org
 Description:
 		Read/write value for the digital attenuator gain (IF_Q) with coarse steps.
 What:		/sys/bus/iio/devices/iio:deviceX/in_altvoltage0_i_calibscale_fine
 KernelVersion: 5.18
 Contact:	linux-iio@vger.kernel.org
 Description:
 		Read/write value for the digital attenuator gain (IF_I) with fine steps.
 What:		/sys/bus/iio/devices/iio:deviceX/in_altvoltage0_q_calibscale_fine
 KernelVersion: 5.18
 Contact:	linux-iio@vger.kernel.org
 Description:
 		Read/write value for the digital attenuator gain (IF_Q) with fine steps.
--- a/Documentation/ABI/testing/sysfs-bus-iio-proximity
+++ b/Documentation/ABI/testing/sysfs-bus-iio-proximity
@ -18,7 +18,7 @@ Description:
 		on the signal from which time of flight measurements are
 		taken.
 		The appropriate values to take is dependent on both the
-		sensor and its operating environment:
+		sensor and it's operating environment:
 		* as3935 (0-31 range)
 		18 = indoors (default)
 		14 = outdoors
--- a/Documentation/ABI/testing/sysfs-bus-iio-scd30
+++ b/Documentation/ABI/testing/sysfs-bus-iio-scd30
@ -0,0 +1,34 @@
 What:		/sys/bus/iio/devices/iio:deviceX/calibration_auto_enable
 Date:		June 2020
 KernelVersion:	5.8
 Contact:	linux-iio@vger.kernel.org
 Description:
 		Contaminants build-up in the measurement chamber or optical
 		elements deterioration leads to sensor drift.
 		One can compensate for sensor drift by using automatic self
 		calibration procedure (asc).
 		Writing 1 or 0 to this attribute will respectively activate or
 		deactivate asc.
 		Upon reading current asc status is returned.
 What:		/sys/bus/iio/devices/iio:deviceX/calibration_forced_value
 Date:		June 2020
 KernelVersion:	5.8
 Contact:	linux-iio@vger.kernel.org
 Description:
 		Contaminants build-up in the measurement chamber or optical
 		elements deterioration leads to sensor drift.
 		One can compensate for sensor drift by using forced
 		recalibration (frc). This is useful in case there's known
 		co2 reference available nearby the sensor.
 		Picking value from the range [400 1 2000] and writing it to the
 		sensor will set frc.
 		Upon reading current frc value is returned. Note that after
 		power cycling default value (i.e 400) is returned even though
 		internally sensor had recalibrated itself.
--- a/Documentation/ABI/testing/sysfs-bus-iio-sx9324
+++ b/Documentation/ABI/testing/sysfs-bus-iio-sx9324
@ -1,29 +0,0 @@
 What:		/sys/bus/iio/devices/iio:deviceX/in_proximity<id>_setup
 Date:		November 2021
 KernelVersion:	5.17
 Contact:	Gwendal Grignou <gwendal@chromium.org>
 Description:
 		SX9324 has 3 inputs, CS0, CS1 and CS2. Hardware layout
 		defines if the input is
 		+ not connected (HZ),
 		+ grounded (GD),
 		+ connected to an antenna where it can act as a base
 		  (DS - data shield), or measured input (MI).
 		The sensor rotates measurement across 4 phases
 		(PH0, PH1, PH2, PH3), where the inputs are configured
 		and then measured.
 		By default,  during the first phase, [PH0], CS0 is measured,
 		while CS1 and CS2 are used as shields.
 		`cat in_proximity0_setup` returns "MI,DS,DS".
 		[PH1], CS1 is measured, CS0 and CS2 are shield:
 		`cat in_proximity1_setup` returns "DS,MI,DS".
 		[PH2], CS2 is measured, CS0 and CS1 are shield:
 		`cat in_proximity1_setup` returns "DS,DS,MI".
 		[PH3], CS1 and CS2 are measured (combo mode):
 		`cat in_proximity1_setup` returns "DS,MI,MI".
 		Note, these are the chip default. Hardware layout will most
 		likely dictate different output. The entry is read-only.
--- a/Documentation/ABI/testing/sysfs-bus-iio-temperature-max31856
+++ b/Documentation/ABI/testing/sysfs-bus-iio-temperature-max31856
@ -0,0 +1,31 @@
 What:		/sys/bus/iio/devices/iio:deviceX/fault_oc
 KernelVersion:	5.1
 Contact:	linux-iio@vger.kernel.org
 Description:
 		Open-circuit fault. The detection of open-circuit faults,
 		such as those caused by broken thermocouple wires.
 		Reading returns either '1' or '0'.
 		===  =======================================================
 		'1'  An open circuit such as broken thermocouple wires
 		     has been detected.
 		'0'  No open circuit or broken thermocouple wires are detected
 		===  =======================================================
 What:		/sys/bus/iio/devices/iio:deviceX/fault_ovuv
 KernelVersion:	5.1
 Contact:	linux-iio@vger.kernel.org
 Description:
 		Overvoltage or Undervoltage Input Fault. The internal circuitry
 		is protected from excessive voltages applied to the thermocouple
 		cables by integrated MOSFETs at the T+ and T- inputs, and the
 		BIAS output. These MOSFETs turn off when the input voltage is
 		negative or greater than VDD.
 		Reading returns either '1' or '0'.
 		===  =======================================================
 		'1'  The input voltage is negative or greater than VDD.
 		'0'  The input voltage is positive and less than VDD (normal
 		     state).
 		===  =======================================================
--- a/Documentation/ABI/testing/sysfs-bus-iio-thermocouple
+++ b/Documentation/ABI/testing/sysfs-bus-iio-thermocouple
@ -1,18 +0,0 @@
 What:		/sys/bus/iio/devices/iio:deviceX/fault_ovuv
 KernelVersion:	5.1
 Contact:	linux-iio@vger.kernel.org
 Description:
 		Overvoltage or Undervoltage Input Fault. The internal circuitry
 		is protected from excessive voltages applied to the thermocouple
 		cables. The device can also detect if such a condition occurs.
 		Reading returns '1' if input voltage is negative or greater
 		than VDD, otherwise '0'.
 What:		/sys/bus/iio/devices/iio:deviceX/fault_oc
 KernelVersion:	5.1
 Contact:	linux-iio@vger.kernel.org
 Description:
 		Open-circuit fault. The detection of open-circuit faults,
 		such as those caused by broken thermocouple wires.
 		Reading returns '1' if fault, '0' otherwise.
--- a/Documentation/ABI/testing/sysfs-bus-iio-timer-stm32
+++ b/Documentation/ABI/testing/sysfs-bus-iio-timer-stm32
@ -90,6 +90,14 @@ Description:
 		Reading returns the current master modes.
 		Writing set the master mode
 What:		/sys/bus/iio/devices/triggerX/sampling_frequency
 KernelVersion:	4.11
 Contact:	benjamin.gaignard@st.com
 Description:
 		Reading returns the current sampling frequency.
 		Writing an value different of 0 set and start sampling.
 		Writing 0 stop sampling.
 What:		/sys/bus/iio/devices/iio:deviceX/in_count0_preset
 KernelVersion:	4.12
 Contact:	benjamin.gaignard@st.com
--- a/Documentation/ABI/testing/sysfs-bus-iio-vf610
+++ b/Documentation/ABI/testing/sysfs-bus-iio-vf610
@ -1,4 +1,4 @@
-What:		/sys/bus/iio/devices/iio:deviceX/in_conversion_mode
+What:		/sys/bus/iio/devices/iio:deviceX/conversion_mode
 KernelVersion:	4.2
 Contact:	linux-iio@vger.kernel.org
 Description:
--- a/Documentation/ABI/testing/sysfs-bus-mdio
+++ b/Documentation/ABI/testing/sysfs-bus-mdio
@ -1,5 +1,4 @@
 What:          /sys/bus/mdio_bus/devices/.../statistics/
 What:          /sys/class/mdio_bus/.../statistics/
 Date:          January 2020
 KernelVersion: 5.6
 Contact:       netdev@vger.kernel.org
@ -8,7 +7,6 @@ Description:
 		MDIO bus address statistics.
 What:          /sys/bus/mdio_bus/devices/.../statistics/transfers
 What:          /sys/class/mdio_bus/.../transfers
 Date:          January 2020
 KernelVersion: 5.6
 Contact:       netdev@vger.kernel.org
@ -16,7 +14,6 @@ Description:
 		Total number of transfers for this MDIO bus.
 What:          /sys/bus/mdio_bus/devices/.../statistics/errors
 What:          /sys/class/mdio_bus/.../statistics/errors
 Date:          January 2020
 KernelVersion: 5.6
 Contact:       netdev@vger.kernel.org
@ -24,7 +21,6 @@ Description:
 		Total number of transfer errors for this MDIO bus.
 What:          /sys/bus/mdio_bus/devices/.../statistics/writes
 What:          /sys/class/mdio_bus/.../statistics/writes
 Date:          January 2020
 KernelVersion: 5.6
 Contact:       netdev@vger.kernel.org
@ -32,7 +28,6 @@ Description:
 		Total number of write transactions for this MDIO bus.
 What:          /sys/bus/mdio_bus/devices/.../statistics/reads
 What:          /sys/class/mdio_bus/.../statistics/reads
 Date:          January 2020
 KernelVersion: 5.6
 Contact:       netdev@vger.kernel.org
@ -40,7 +35,6 @@ Description:
 		Total number of read transactions for this MDIO bus.
 What:          /sys/bus/mdio_bus/devices/.../statistics/transfers_<addr>
 What:          /sys/class/mdio_bus/.../statistics/transfers_<addr>
 Date:          January 2020
 KernelVersion: 5.6
 Contact:       netdev@vger.kernel.org
@ -48,7 +42,6 @@ Description:
 		Total number of transfers for this MDIO bus address.
 What:          /sys/bus/mdio_bus/devices/.../statistics/errors_<addr>
 What:          /sys/class/mdio_bus/.../statistics/errors_<addr>
 Date:          January 2020
 KernelVersion: 5.6
 Contact:       netdev@vger.kernel.org
@ -56,7 +49,6 @@ Description:
 		Total number of transfer errors for this MDIO bus address.
 What:          /sys/bus/mdio_bus/devices/.../statistics/writes_<addr>
 What:          /sys/class/mdio_bus/.../statistics/writes_<addr>
 Date:          January 2020
 KernelVersion: 5.6
 Contact:       netdev@vger.kernel.org
@ -64,7 +56,6 @@ Description:
 		Total number of write transactions for this MDIO bus address.
 What:          /sys/bus/mdio_bus/devices/.../statistics/reads_<addr>
 What:          /sys/class/mdio_bus/.../statistics/reads_<addr>
 Date:          January 2020
 KernelVersion: 5.6
 Contact:       netdev@vger.kernel.org
--- a/Documentation/ABI/testing/sysfs-bus-nvdimm
+++ b/Documentation/ABI/testing/sysfs-bus-nvdimm
@ -6,38 +6,3 @@ Description:
 The libnvdimm sub-system implements a common sysfs interface for
 platform nvdimm resources. See Documentation/driver-api/nvdimm/.
 What:           /sys/bus/event_source/devices/nmemX/format
 Date:           February 2022
 KernelVersion:  5.18
 Contact:        Kajol Jain <kjain@linux.ibm.com>
 Description:	(RO) Attribute group to describe the magic bits
 		that go into perf_event_attr.config for a particular pmu.
 		(See ABI/testing/sysfs-bus-event_source-devices-format).
 		Each attribute under this group defines a bit range of the
 		perf_event_attr.config. Supported attribute is listed
 		below::
 		  event  = "config:0-4"  - event ID
 		For example::
 			ctl_res_cnt = "event=0x1"
 What:           /sys/bus/event_source/devices/nmemX/events
 Date:           February 2022
 KernelVersion:  5.18
 Contact:        Kajol Jain <kjain@linux.ibm.com>
 Description:	(RO) Attribute group to describe performance monitoring events
                for the nvdimm memory device. Each attribute in this group
                describes a single performance monitoring event supported by
                this nvdimm pmu.  The name of the file is the name of the event.
                (See ABI/testing/sysfs-bus-event_source-devices-events). A
                listing of the events supported by a given nvdimm provider type
                can be found in Documentation/driver-api/nvdimm/$provider.
 What:          /sys/bus/event_source/devices/nmemX/cpumask
 Date:          February 2022
 KernelVersion:  5.18
 Contact:        Kajol Jain <kjain@linux.ibm.com>
 Description:	(RO) This sysfs file exposes the cpumask which is designated to
 		to retrieve nvdimm pmu event counter data.
--- a/Documentation/ABI/testing/sysfs-bus-papr-pmem
+++ b/Documentation/ABI/testing/sysfs-bus-papr-pmem
@ -61,15 +61,3 @@ Description:
 		* "CchRHCnt" : Cache Read Hit Count
 		* "CchWHCnt" : Cache Write Hit Count
 		* "FastWCnt" : Fast Write Count
 What:		/sys/bus/nd/devices/nmemX/papr/health_bitmap_inject
 Date:		Jan, 2022
 KernelVersion:	v5.17
 Contact:	linuxppc-dev <linuxppc-dev@lists.ozlabs.org>, nvdimm@lists.linux.dev,
 Description:
 		(RO) Reports the health bitmap inject bitmap that is applied to
 		bitmap received from PowerVM via the H_SCM_HEALTH. This is used
 		to forcibly set specific bits returned from Hcall. These is then
 		used to simulate various health or shutdown states for an nvdimm
 		and are set by user-space tools like ndctl by issuing a PAPR DSM.
--- a/Documentation/ABI/testing/sysfs-bus-pci
+++ b/Documentation/ABI/testing/sysfs-bus-pci
@ -1,5 +1,4 @@
 What:		/sys/bus/pci/drivers/.../bind
 What:		/sys/devices/pciX/.../bind
 Date:		December 2003
 Contact:	linux-pci@vger.kernel.org
 Description:
@ -15,7 +14,6 @@ Description:
 		(Note: kernels before 2.6.28 may require echo -n).
 What:		/sys/bus/pci/drivers/.../unbind
 What:		/sys/devices/pciX/.../unbind
 Date:		December 2003
 Contact:	linux-pci@vger.kernel.org
 Description:
@ -31,7 +29,6 @@ Description:
 		(Note: kernels before 2.6.28 may require echo -n).
 What:		/sys/bus/pci/drivers/.../new_id
 What:		/sys/devices/pciX/.../new_id
 Date:		December 2003
 Contact:	linux-pci@vger.kernel.org
 Description:
@ -50,7 +47,6 @@ Description:
 		  # echo "8086 10f5" > /sys/bus/pci/drivers/foo/new_id
 What:		/sys/bus/pci/drivers/.../remove_id
 What:		/sys/devices/pciX/.../remove_id
 Date:		February 2009
 Contact:	Chris Wright <chrisw@sous-sol.org>
 Description:
@ -100,17 +96,6 @@ Description:
 		This attribute indicates the mode that the irq vector named by
 		the file is in (msi vs. msix)
 What:		/sys/bus/pci/devices/.../irq
 Date:		August 2021
 Contact:	Linux PCI developers <linux-pci@vger.kernel.org>
 Description:
 		If a driver has enabled MSI (not MSI-X), "irq" contains the
 		IRQ of the first MSI vector. Otherwise "irq" contains the
 		IRQ of the legacy INTx interrupt.
 		"irq" being set to 0 indicates that the device isn't
 		capable of generating legacy INTx interrupts.
 What:		/sys/bus/pci/devices/.../remove
 Date:		January 2009
 Contact:	Linux PCI developers <linux-pci@vger.kernel.org>
@ -175,7 +160,7 @@ Description:
 		If the underlying VPD has a writable section then the
 		corresponding section of this file will be writable.
-What:		/sys/bus/pci/devices/.../virtfn<N>
+What:		/sys/bus/pci/devices/.../virtfnN
 Date:		March 2009
 Contact:	Yu Zhao <yu.zhao@intel.com>
 Description:
@ -202,24 +187,6 @@ Description:
 		The symbolic link points to the PCI device sysfs entry of the
 		Physical Function this device associates with.
 What:		/sys/bus/pci/devices/.../modalias
 Date:		May 2005
 Contact:	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
 Description:
 		This attribute indicates the PCI ID of the device object.
 		That is in the format:
 		pci:vXXXXXXXXdXXXXXXXXsvXXXXXXXXsdXXXXXXXXbcXXscXXiXX,
 		where:
 		    - vXXXXXXXX contains the vendor ID;
 		    - dXXXXXXXX contains the device ID;
 		    - svXXXXXXXX contains the sub-vendor ID;
 		    - sdXXXXXXXX contains the subsystem device ID;
 		    - bcXX contains the device class;
 		    - scXX contains the device subclass;
 		    - iXX contains the device class programming interface.
 What:		/sys/bus/pci/slots/.../module
 Date:		June 2009
 Contact:	linux-pci@vger.kernel.org
@ -457,36 +424,3 @@ Description:
 		The file is writable if the PF is bound to a driver that
 		implements ->sriov_set_msix_vec_count().
 What:		/sys/bus/pci/devices/.../resourceN_resize
 Date:		September 2022
 Contact:	Alex Williamson <alex.williamson@redhat.com>
 Description:
 		These files provide an interface to PCIe Resizable BAR support.
 		A file is created for each BAR resource (N) supported by the
 		PCIe Resizable BAR extended capability of the device.  Reading
 		each file exposes the bitmap of available resource sizes:
 		# cat resource1_resize
 		00000000000001c0
 		The bitmap represents supported resource sizes for the BAR,
 		where bit0 = 1MB, bit1 = 2MB, bit2 = 4MB, etc.  In the above
 		example the device supports 64MB, 128MB, and 256MB BAR sizes.
 		When writing the file, the user provides the bit position of
 		the desired resource size, for example:
 		# echo 7 > resource1_resize
 		This indicates to set the size value corresponding to bit 7,
 		128MB.  The resulting size is 2 ^ (bit# + 20).  This definition
 		matches the PCIe specification of this capability.
 		In order to make use of resource resizing, all PCI drivers must
 		be unbound from the device and peer devices under the same
 		parent bridge may need to be soft removed.  In the case of
 		VGA devices, writing a resize value will remove low level
 		console drivers from the device.  Raw users of pci-sysfs
 		resourceN attributes must be terminated prior to resizing.
 		Success of the resizing operation is not guaranteed.
--- a/Documentation/ABI/testing/sysfs-bus-peci
+++ b/Documentation/ABI/testing/sysfs-bus-peci
@ -1,16 +0,0 @@
 What:		/sys/bus/peci/rescan
 Date:		July 2021
 KernelVersion:	5.18
 Contact:	Iwona Winiarska <iwona.winiarska@intel.com>
 Description:
 		Writing a non-zero value to this attribute will
 		initiate scan for PECI devices on all PECI controllers
 		in the system.
 What:		/sys/bus/peci/devices/<controller_id>-<device_addr>/remove
 Date:		July 2021
 KernelVersion:	5.18
 Contact:	Iwona Winiarska <iwona.winiarska@intel.com>
 Description:
 		Writing a non-zero value to this attribute will
 		remove the PECI device and any of its children.
--- a/Documentation/ABI/testing/sysfs-bus-platform
+++ b/Documentation/ABI/testing/sysfs-bus-platform
@ -42,15 +42,3 @@ Date:		August 2021
 Contact:	Barry Song <song.bao.hua@hisilicon.com>
 Description:
 		This attribute will show "msi" if <N> is a valid msi irq
 What:		/sys/bus/platform/devices/.../modalias
 Description:
 		Same as MODALIAS in the uevent at device creation.
 		A platform device that it is exposed via devicetree uses:
 			- of:N`of node name`T`type`
 		Other platform devices use, instead:
 			- platform:`driver name`
--- a/Documentation/ABI/testing/sysfs-bus-platform-devices-occ-hwmon
+++ b/Documentation/ABI/testing/sysfs-bus-platform-devices-occ-hwmon
@ -1,13 +0,0 @@
 What:		/sys/bus/platform/devices/occ-hwmon.X/ffdc
 KernelVersion:	5.15
 Contact:	eajames@linux.ibm.com
 Description:
 		Contains the First Failure Data Capture from the SBEFIFO
 		hardware, if there is any from a previous transfer. Otherwise,
 		the file is empty. The data is cleared when it's been
 		completely read by a user. As the name suggests, only the data
 		from the first error is saved, until it's cleared upon read. The OCC hwmon driver, running on
 		a Baseboard Management Controller (BMC), communicates with
 		POWER9 and up processors over the Self-Boot Engine (SBE) FIFO.
 		In many error conditions, the SBEFIFO will return error data
 		indicating the type of error and system state, etc.
--- a/Documentation/ABI/testing/sysfs-bus-platform-onboard-usb-hub
+++ b/Documentation/ABI/testing/sysfs-bus-platform-onboard-usb-hub
@ -1,8 +0,0 @@
 What:		/sys/bus/platform/devices/<dev>/always_powered_in_suspend
 Date:		June 2022
 KernelVersion:	5.20
 Contact:	Matthias Kaehlcke <matthias@kaehlcke.net>
 		linux-usb@vger.kernel.org
 Description:
 		(RW) Controls whether the USB hub remains always powered
 		during system suspend or not.
--- a/Documentation/ABI/testing/sysfs-bus-rapidio
+++ b/Documentation/ABI/testing/sysfs-bus-rapidio
@ -1,4 +1,4 @@
-What:		/sys/bus/rapidio/devices/<nn>:<d>:<iiii>
+What:		/sys/bus/rapidio/devices/nn:d:iiii
 Description:
 		For each RapidIO device, the RapidIO subsystem creates files in
 		an individual subdirectory with the following name format of
@ -29,7 +29,7 @@ Description:
 Attributes Common for All RapidIO Devices
 -----------------------------------------
-What:		/sys/bus/rapidio/devices/<nn>:<d>:<iiii>/did
+What:		/sys/bus/rapidio/devices/nn:d:iiii/did
 Date:		Nov, 2005
 KernelVersion:	v2.6.15
 Contact:	Matt Porter <mporter@kernel.crashing.org>,
@ -37,7 +37,7 @@ Contact:	Matt Porter <mporter@kernel.crashing.org>,
 Description:
 		(RO) returns the device identifier
-What:		/sys/bus/rapidio/devices/<nn>:<d>:<iiii>/vid
+What:		/sys/bus/rapidio/devices/nn:d:iiii/vid
 Date:		Nov, 2005
 KernelVersion:	v2.6.15
 Contact:	Matt Porter <mporter@kernel.crashing.org>,
@ -45,7 +45,7 @@ Contact:	Matt Porter <mporter@kernel.crashing.org>,
 Description:
 		(RO) returns the device vendor identifier
-What:		/sys/bus/rapidio/devices/<nn>:<d>:<iiii>/device_rev
+What:		/sys/bus/rapidio/devices/nn:d:iiii/device_rev
 Date:		Nov, 2005
 KernelVersion:	v2.6.15
 Contact:	Matt Porter <mporter@kernel.crashing.org>,
@ -53,7 +53,7 @@ Contact:	Matt Porter <mporter@kernel.crashing.org>,
 Description:
 		(RO) returns the device revision level
-What:		/sys/bus/rapidio/devices/<nn>:<d>:<iiii>/asm_did
+What:		/sys/bus/rapidio/devices/nn:d:iiii/asm_did
 Date:		Nov, 2005
 KernelVersion:	v2.6.15
 Contact:	Matt Porter <mporter@kernel.crashing.org>,
@ -61,7 +61,7 @@ Contact:	Matt Porter <mporter@kernel.crashing.org>,
 Description:
 		(RO) returns identifier for the assembly containing the device
-What:		/sys/bus/rapidio/devices/<nn>:<d>:<iiii>/asm_rev
+What:		/sys/bus/rapidio/devices/nn:d:iiii/asm_rev
 Date:		Nov, 2005
 KernelVersion:	v2.6.15
 Contact:	Matt Porter <mporter@kernel.crashing.org>,
@ -70,7 +70,7 @@ Description:
 		(RO) returns revision level of the assembly containing the
 		device
-What:		/sys/bus/rapidio/devices/<nn>:<d>:<iiii>/asm_vid
+What:		/sys/bus/rapidio/devices/nn:d:iiii/asm_vid
 Date:		Nov, 2005
 KernelVersion:	v2.6.15
 Contact:	Matt Porter <mporter@kernel.crashing.org>,
@ -79,7 +79,7 @@ Description:
 		(RO) returns vendor identifier of the assembly containing the
 		device
-What:		/sys/bus/rapidio/devices/<nn>:<d>:<iiii>/destid
+What:		/sys/bus/rapidio/devices/nn:d:iiii/destid
 Date:		Mar, 2011
 KernelVersion:	v2.6.3
 Contact:	Matt Porter <mporter@kernel.crashing.org>,
@ -88,7 +88,7 @@ Description:
 		(RO) returns device destination ID assigned by the enumeration
 		routine
-What:		/sys/bus/rapidio/devices/<nn>:<d>:<iiii>/lprev
+What:		/sys/bus/rapidio/devices/nn:d:iiii/lprev
 Date:		Mar, 2011
 KernelVersion:	v2.6.39
 Contact:	Matt Porter <mporter@kernel.crashing.org>,
@ -97,7 +97,7 @@ Description:
 		(RO) returns name of previous device (switch) on the path to the
 		device that that owns this attribute
-What:		/sys/bus/rapidio/devices/<nn>:<d>:<iiii>/modalias
+What:		/sys/bus/rapidio/devices/nn:d:iiii/modalias
 Date:		Jul, 2013
 KernelVersion:	v3.11
 Contact:	Matt Porter <mporter@kernel.crashing.org>,
@ -105,7 +105,7 @@ Contact:	Matt Porter <mporter@kernel.crashing.org>,
 Description:
 		(RO) returns the device modalias
-What:		/sys/bus/rapidio/devices/<nn>:<d>:<iiii>/config
+What:		/sys/bus/rapidio/devices/nn:d:iiii/config
 Date:		Nov, 2005
 KernelVersion:	v2.6.15
 Contact:	Matt Porter <mporter@kernel.crashing.org>,
@ -128,7 +128,7 @@ device-specific sysfs attributes by specifying a callback function that may be
 set by the switch initialization routine during enumeration or discovery
 process.
-What:		/sys/bus/rapidio/devices/<nn>:<s>:<iiii>/routes
+What:		/sys/bus/rapidio/devices/nn:s:iiii/routes
 Date:		Nov, 2005
 KernelVersion:	v2.6.15
 Contact:	Matt Porter <mporter@kernel.crashing.org>,
@ -138,7 +138,7 @@ Description:
 		This attribute reports only valid routing table entries, one
 		line for each entry.
-What:		/sys/bus/rapidio/devices/<nn>:<s>:<iiii>/destid
+What:		/sys/bus/rapidio/devices/nn:s:iiii/destid
 Date:		Mar, 2011
 KernelVersion:	v2.6.3
 Contact:	Matt Porter <mporter@kernel.crashing.org>,
@ -147,7 +147,7 @@ Description:
 		(RO) device destination ID of the associated device that defines
 		a route to the switch
-What:		/sys/bus/rapidio/devices/<nn>:<s>:<iiii>/hopcount
+What:		/sys/bus/rapidio/devices/nn:s:iiii/hopcount
 Date:		Mar, 2011
 KernelVersion:	v2.6.39
 Contact:	Matt Porter <mporter@kernel.crashing.org>,
@ -155,7 +155,7 @@ Contact:	Matt Porter <mporter@kernel.crashing.org>,
 Description:
 		(RO) number of hops on the path to the switch
-What:		/sys/bus/rapidio/devices/<nn>:<s>:<iiii>/lnext
+What:		/sys/bus/rapidio/devices/nn:s:iiii/lnext
 Date:		Mar, 2011
 KernelVersion:	v2.6.39
 Contact:	Matt Porter <mporter@kernel.crashing.org>,
@ -172,7 +172,7 @@ Device-specific Switch Attributes
 IDT_GEN2-
-What:		/sys/bus/rapidio/devices/<nn>:<s>:<iiii>/errlog
+What:		/sys/bus/rapidio/devices/nn:s:iiii/errlog
 Date:		Oct, 2010
 KernelVersion:	v2.6.37
 Contact:	Matt Porter <mporter@kernel.crashing.org>,
--- a/Documentation/ABI/testing/sysfs-bus-soundwire-master
+++ b/Documentation/ABI/testing/sysfs-bus-soundwire-master
@ -1,13 +1,13 @@
-What:		/sys/bus/soundwire/devices/sdw-master-<N>/revision
+What:		/sys/bus/soundwire/devices/sdw-master-N/revision
-		/sys/bus/soundwire/devices/sdw-master-<N>/clk_stop_modes
+		/sys/bus/soundwire/devices/sdw-master-N/clk_stop_modes
-		/sys/bus/soundwire/devices/sdw-master-<N>/clk_freq
+		/sys/bus/soundwire/devices/sdw-master-N/clk_freq
-		/sys/bus/soundwire/devices/sdw-master-<N>/clk_gears
+		/sys/bus/soundwire/devices/sdw-master-N/clk_gears
-		/sys/bus/soundwire/devices/sdw-master-<N>/default_col
+		/sys/bus/soundwire/devices/sdw-master-N/default_col
-		/sys/bus/soundwire/devices/sdw-master-<N>/default_frame_rate
+		/sys/bus/soundwire/devices/sdw-master-N/default_frame_rate
-		/sys/bus/soundwire/devices/sdw-master-<N>/default_row
+		/sys/bus/soundwire/devices/sdw-master-N/default_row
-		/sys/bus/soundwire/devices/sdw-master-<N>/dynamic_shape
+		/sys/bus/soundwire/devices/sdw-master-N/dynamic_shape
-		/sys/bus/soundwire/devices/sdw-master-<N>/err_threshold
+		/sys/bus/soundwire/devices/sdw-master-N/err_threshold
-		/sys/bus/soundwire/devices/sdw-master-<N>/max_clk_freq
+		/sys/bus/soundwire/devices/sdw-master-N/max_clk_freq
 Date:		April 2020
--- a/Documentation/ABI/testing/sysfs-bus-soundwire-slave
+++ b/Documentation/ABI/testing/sysfs-bus-soundwire-slave
@ -64,37 +64,37 @@ Description:	SoundWire Slave Data Port-0 DisCo properties.
 		Data port 0 are used by the bus to configure the Data Port 0.
-What:		/sys/bus/soundwire/devices/sdw:.../dp<N>_src/max_word
+What:		/sys/bus/soundwire/devices/sdw:.../dpN_src/max_word
-		/sys/bus/soundwire/devices/sdw:.../dp<N>_src/min_word
+		/sys/bus/soundwire/devices/sdw:.../dpN_src/min_word
-		/sys/bus/soundwire/devices/sdw:.../dp<N>_src/words
+		/sys/bus/soundwire/devices/sdw:.../dpN_src/words
-		/sys/bus/soundwire/devices/sdw:.../dp<N>_src/type
+		/sys/bus/soundwire/devices/sdw:.../dpN_src/type
-		/sys/bus/soundwire/devices/sdw:.../dp<N>_src/max_grouping
+		/sys/bus/soundwire/devices/sdw:.../dpN_src/max_grouping
-		/sys/bus/soundwire/devices/sdw:.../dp<N>_src/simple_ch_prep_sm
+		/sys/bus/soundwire/devices/sdw:.../dpN_src/simple_ch_prep_sm
-		/sys/bus/soundwire/devices/sdw:.../dp<N>_src/ch_prep_timeout
+		/sys/bus/soundwire/devices/sdw:.../dpN_src/ch_prep_timeout
-		/sys/bus/soundwire/devices/sdw:.../dp<N>_src/imp_def_interrupts
+		/sys/bus/soundwire/devices/sdw:.../dpN_src/imp_def_interrupts
-		/sys/bus/soundwire/devices/sdw:.../dp<N>_src/min_ch
+		/sys/bus/soundwire/devices/sdw:.../dpN_src/min_ch
-		/sys/bus/soundwire/devices/sdw:.../dp<N>_src/max_ch
+		/sys/bus/soundwire/devices/sdw:.../dpN_src/max_ch
-		/sys/bus/soundwire/devices/sdw:.../dp<N>_src/channels
+		/sys/bus/soundwire/devices/sdw:.../dpN_src/channels
-		/sys/bus/soundwire/devices/sdw:.../dp<N>_src/ch_combinations
+		/sys/bus/soundwire/devices/sdw:.../dpN_src/ch_combinations
-		/sys/bus/soundwire/devices/sdw:.../dp<N>_src/max_async_buffer
+		/sys/bus/soundwire/devices/sdw:.../dpN_src/max_async_buffer
-		/sys/bus/soundwire/devices/sdw:.../dp<N>_src/block_pack_mode
+		/sys/bus/soundwire/devices/sdw:.../dpN_src/block_pack_mode
-		/sys/bus/soundwire/devices/sdw:.../dp<N>_src/port_encoding
+		/sys/bus/soundwire/devices/sdw:.../dpN_src/port_encoding
-		/sys/bus/soundwire/devices/sdw:.../dp<N>_sink/max_word
+		/sys/bus/soundwire/devices/sdw:.../dpN_sink/max_word
-		/sys/bus/soundwire/devices/sdw:.../dp<N>_sink/min_word
+		/sys/bus/soundwire/devices/sdw:.../dpN_sink/min_word
-		/sys/bus/soundwire/devices/sdw:.../dp<N>_sink/words
+		/sys/bus/soundwire/devices/sdw:.../dpN_sink/words
-		/sys/bus/soundwire/devices/sdw:.../dp<N>_sink/type
+		/sys/bus/soundwire/devices/sdw:.../dpN_sink/type
-		/sys/bus/soundwire/devices/sdw:.../dp<N>_sink/max_grouping
+		/sys/bus/soundwire/devices/sdw:.../dpN_sink/max_grouping
-		/sys/bus/soundwire/devices/sdw:.../dp<N>_sink/simple_ch_prep_sm
+		/sys/bus/soundwire/devices/sdw:.../dpN_sink/simple_ch_prep_sm
-		/sys/bus/soundwire/devices/sdw:.../dp<N>_sink/ch_prep_timeout
+		/sys/bus/soundwire/devices/sdw:.../dpN_sink/ch_prep_timeout
-		/sys/bus/soundwire/devices/sdw:.../dp<N>_sink/imp_def_interrupts
+		/sys/bus/soundwire/devices/sdw:.../dpN_sink/imp_def_interrupts
-		/sys/bus/soundwire/devices/sdw:.../dp<N>_sink/min_ch
+		/sys/bus/soundwire/devices/sdw:.../dpN_sink/min_ch
-		/sys/bus/soundwire/devices/sdw:.../dp<N>_sink/max_ch
+		/sys/bus/soundwire/devices/sdw:.../dpN_sink/max_ch
-		/sys/bus/soundwire/devices/sdw:.../dp<N>_sink/channels
+		/sys/bus/soundwire/devices/sdw:.../dpN_sink/channels
-		/sys/bus/soundwire/devices/sdw:.../dp<N>_sink/ch_combinations
+		/sys/bus/soundwire/devices/sdw:.../dpN_sink/ch_combinations
-		/sys/bus/soundwire/devices/sdw:.../dp<N>_sink/max_async_buffer
+		/sys/bus/soundwire/devices/sdw:.../dpN_sink/max_async_buffer
-		/sys/bus/soundwire/devices/sdw:.../dp<N>_sink/block_pack_mode
+		/sys/bus/soundwire/devices/sdw:.../dpN_sink/block_pack_mode
-		/sys/bus/soundwire/devices/sdw:.../dp<N>_sink/port_encoding
+		/sys/bus/soundwire/devices/sdw:.../dpN_sink/port_encoding
 Date:		May 2020
--- a/Documentation/ABI/testing/sysfs-bus-surface_aggregator-tabletsw
+++ b/Documentation/ABI/testing/sysfs-bus-surface_aggregator-tabletsw
@ -1,57 +0,0 @@
 What:		/sys/bus/surface_aggregator/devices/01:0e:01:00:01/state
 Date:		July 2022
 KernelVersion:	5.20
 Contact:	Maximilian Luz <luzmaximilian@gmail.com>
 Description:
 		This attribute returns a string with the current type-cover
 		or device posture, as indicated by the embedded controller.
 		Currently returned posture states are:
 		- "disconnected": The type-cover has been disconnected.
 		- "closed": The type-cover has been folded closed and lies on
 		  top of the display.
 		- "laptop": The type-cover is open and in laptop-mode, i.e.,
 		  ready for normal use.
 		- "folded-canvas": The type-cover has been folded back
 		  part-ways, but does not lie flush with the back side of the
 		  device. In general, this means that the kick-stand is used
 		  and extended atop of the cover.
 		- "folded-back": The type cover has been fully folded back and
 		  lies flush with the back side of the device.
 		- "<unknown>": The current state is unknown to the driver, for
 		  example due to newer as-of-yet unsupported hardware.
 		New states may be introduced with new hardware. Users therefore
 		must not rely on this list of states being exhaustive and
 		gracefully handle unknown states.
 What:		/sys/bus/surface_aggregator/devices/01:26:01:00:01/state
 Date:		July 2022
 KernelVersion:	5.20
 Contact:	Maximilian Luz <luzmaximilian@gmail.com>
 Description:
 		This attribute returns a string with the current device posture, as indicated by the embedded controller. Currently
 		returned posture states are:
 		- "closed": The lid of the device is closed.
 		- "laptop": The lid of the device is opened and the device
 		  operates as a normal laptop.
 		- "slate": The screen covers the keyboard or has been flipped
 		  back and the device operates mainly based on touch input.
 		- "tablet": The device operates as tablet and exclusively
 		  relies on touch input (or external peripherals).
 		- "<unknown>": The current state is unknown to the driver, for
 		  example due to newer as-of-yet unsupported hardware.
 		New states may be introduced with new hardware. Users therefore
 		must not rely on this list of states being exhaustive and
 		gracefully handle unknown states.
--- a/Documentation/ABI/testing/sysfs-bus-thunderbolt
+++ b/Documentation/ABI/testing/sysfs-bus-thunderbolt
@ -153,7 +153,7 @@ Date:		Jan 2020
 KernelVersion:	5.5
 Contact:	Mika Westerberg <mika.westerberg@linux.intel.com>
 Description:	This attribute reports number of RX lanes the device is
-		using simultaneously through its upstream port.
+		using simultaneusly through its upstream port.
 What:		/sys/bus/thunderbolt/devices/.../tx_speed
 Date:		Jan 2020
@ -167,7 +167,7 @@ Date:		Jan 2020
 KernelVersion:	5.5
 Contact:	Mika Westerberg <mika.westerberg@linux.intel.com>
 Description:	This attribute reports number of TX lanes the device is
-		using simultaneously through its upstream port.
+		using simultaneusly through its upstream port.
 What:		/sys/bus/thunderbolt/devices/.../vendor
 Date:		Sep 2017
@ -293,16 +293,6 @@ Contact:	thunderbolt-software@lists.01.org
 Description:	This contains XDomain service specific settings as
 		bitmask. Format: %x
 What:		/sys/bus/thunderbolt/devices/usb4_portX/connector
 Date:		April 2022
 Contact:	Heikki Krogerus <heikki.krogerus@linux.intel.com>
 Description:
 		Symlink to the USB Type-C connector. This link is only
 		created when USB Type-C Connector Class is enabled,
 		and only if the system firmware is capable of
 		describing the connection between a port and its
 		connector.
 What:		/sys/bus/thunderbolt/devices/usb4_portX/link
 Date:		Sep 2021
 KernelVersion:	v5.14
--- a/Documentation/ABI/testing/sysfs-bus-usb
+++ b/Documentation/ABI/testing/sysfs-bus-usb
@ -1,4 +1,4 @@
-What:		/sys/bus/usb/devices/<INTERFACE>/authorized
+What:		/sys/bus/usb/devices/INTERFACE/authorized
 Date:		August 2015
 Description:
 		This allows to authorize (1) or deauthorize (0)
@ -166,14 +166,14 @@ Description:
 		The file will be present for all speeds of USB devices, and will
 		always read "no" for USB 1.1 and USB 2.0 devices.
-What:		/sys/bus/usb/devices/.../<hub_interface>/port<X>
+What:		/sys/bus/usb/devices/.../(hub interface)/portX
 Date:		August 2012
 Contact:	Lan Tianyu <tianyu.lan@intel.com>
 Description:
-		The /sys/bus/usb/devices/.../<hub_interface>/port<X>
+		The /sys/bus/usb/devices/.../(hub interface)/portX
 		is usb port device's sysfs directory.
-What:		/sys/bus/usb/devices/.../<hub_interface>/port<X>/connect_type
+What:		/sys/bus/usb/devices/.../(hub interface)/portX/connect_type
 Date:		January 2013
 Contact:	Lan Tianyu <tianyu.lan@intel.com>
 Description:
@ -182,7 +182,7 @@ Description:
 		The file will read "hotplug", "hardwired" and "not used" if the
 		information is available, and "unknown" otherwise.
-What:		/sys/bus/usb/devices/.../<hub_interface>/port<X>/location
+What:		/sys/bus/usb/devices/.../(hub interface)/portX/location
 Date:		October 2018
 Contact:	Bjørn Mork <bjorn@mork.no>
 Description:
@ -192,7 +192,7 @@ Description:
 		raw location value as a hex integer.
-What:		/sys/bus/usb/devices/.../<hub_interface>/port<X>/quirks
+What:		/sys/bus/usb/devices/.../(hub interface)/portX/quirks
 Date:		May 2018
 Contact:	Nicolas Boichat <drinkcat@chromium.org>
 Description:
@ -216,7 +216,7 @@ Description:
 		   used to help make enumeration work better on some high speed
 		   devices.
-What:		/sys/bus/usb/devices/.../<hub_interface>/port<X>/over_current_count
+What:		/sys/bus/usb/devices/.../(hub interface)/portX/over_current_count
 Date:		February 2018
 Contact:	Richard Leitner <richard.leitner@skidata.com>
 Description:
@ -230,10 +230,10 @@ Description:
 		Any time this value changes the corresponding hub device will send a
 		udev event with the following attributes::
-		  OVER_CURRENT_PORT=/sys/bus/usb/devices/.../<hub_interface>/port<X>
+		  OVER_CURRENT_PORT=/sys/bus/usb/devices/.../(hub interface)/portX
 		  OVER_CURRENT_COUNT=[current value of this sysfs attribute]
-What:		/sys/bus/usb/devices/.../<hub_interface>/port<X>/usb3_lpm_permit
+What:		/sys/bus/usb/devices/.../(hub interface)/portX/usb3_lpm_permit
 Date:		November 2015
 Contact:	Lu Baolu <baolu.lu@linux.intel.com>
 Description:
@ -244,26 +244,6 @@ Description:
 		is permitted, "u2" if only u2 is permitted, "u1_u2" if both u1 and
 		u2 are permitted.
 What:		/sys/bus/usb/devices/.../<hub_interface>/port<X>/connector
 Date:		December 2021
 Contact:	Heikki Krogerus <heikki.krogerus@linux.intel.com>
 Description:
 		Link to the USB Type-C connector when available. This link is
 		only created when USB Type-C Connector Class is enabled, and
 		only if the system firmware is capable of describing the
 		connection between a port and its connector.
 What:		/sys/bus/usb/devices/.../<hub_interface>/port<X>/disable
 Date:		June 2022
 Contact:	Michael Grzeschik <m.grzeschik@pengutronix.de>
 Description:
 		This file controls the state of a USB port, including
 		Vbus power output (but only on hubs that support
 		power switching -- most hubs don't support it). If
 		a port is disabled, the port is unusable: Devices
 		attached to the port will not be detected, initialized,
 		or enumerated.
 What:		/sys/bus/usb/devices/.../power/usb2_lpm_l1_timeout
 Date:		May 2013
 Contact:	Mathias Nyman <mathias.nyman@linux.intel.com>
@ -308,277 +288,3 @@ Description:
 		USB 3.2 adds Dual-lane support, 2 rx and 2 tx -lanes over Type-C.
 		Inter-Chip SSIC devices support asymmetric lanes up to 4 lanes per
 		direction. Devices before USB 3.2 are single lane (tx_lanes = 1)
 What:		/sys/bus/usb/devices/usbX/bAlternateSetting
 Description:
 		The current interface alternate setting number, in decimal.
 		See USB specs for its meaning.
 What:		/sys/bus/usb/devices/usbX/bcdDevice
 Description:
 		The device's release number, in hexadecimal.
 		See USB specs for its meaning.
 What:		/sys/bus/usb/devices/usbX/bConfigurationValue
 Description:
 		While a USB device typically have just one configuration
 		setting, some devices support multiple configurations.
 		This value shows the current configuration, in decimal.
 		Changing its value will change the device's configuration
 		to another setting.
 		The number of configurations supported by a device is at:
 			/sys/bus/usb/devices/usbX/bNumConfigurations
 		See USB specs for its meaning.
 What:		/sys/bus/usb/devices/usbX/bDeviceClass
 Description:
 		Class code of the device, in hexadecimal.
 		See USB specs for its meaning.
 What:		/sys/bus/usb/devices/usbX/bDeviceProtocol
 Description:
 		Protocol code of the device, in hexadecimal.
 		See USB specs for its meaning.
 What:		/sys/bus/usb/devices/usbX/bDeviceSubClass
 Description:
 		Subclass code of the device, in hexadecimal.
 		See USB specs for its meaning.
 What:		/sys/bus/usb/devices/usbX/bInterfaceClass
 Description:
 		Class code of the interface, in hexadecimal.
 		See USB specs for its meaning.
 What:		/sys/bus/usb/devices/usbX/bInterfaceNumber
 Description:
 		Interface number, in hexadecimal.
 		See USB specs for its meaning.
 What:		/sys/bus/usb/devices/usbX/bInterfaceProtocol
 Description:
 		Protocol code of the interface, in hexadecimal.
 		See USB specs for its meaning.
 What:		/sys/bus/usb/devices/usbX/bInterfaceSubClass
 Description:
 		Subclass code of the interface, in hexadecimal.
 		See USB specs for its meaning.
 What:		/sys/bus/usb/devices/usbX/bmAttributes
 Description:
 		Attributes of the current configuration, in hexadecimal.
 		See USB specs for its meaning.
 What:		/sys/bus/usb/devices/usbX/bMaxPacketSize0
 Description:
 		Maximum endpoint 0 packet size, in decimal.
 		See USB specs for its meaning.
 What:		/sys/bus/usb/devices/usbX/bMaxPower
 Description:
 		Maximum power consumption of the active configuration of
 		the device, in miliamperes.
 What:		/sys/bus/usb/devices/usbX/bNumConfigurations
 Description:
 		Number of the possible configurations of the device, in
 		decimal. The current configuration is controlled via:
 			/sys/bus/usb/devices/usbX/bConfigurationValue
 		See USB specs for its meaning.
 What:		/sys/bus/usb/devices/usbX/bNumEndpoints
 Description:
 		Number of endpoints used on this interface, in hexadecimal.
 		See USB specs for its meaning.
 What:		/sys/bus/usb/devices/usbX/bNumInterfaces
 Description:
 		Number of interfaces on this device, in decimal.
 What:		/sys/bus/usb/devices/usbX/busnum
 Description:
 		Number of the bus.
 What:		/sys/bus/usb/devices/usbX/configuration
 Description:
 		Contents of the string descriptor associated with the
 		current configuration. It may include the firmware version
 		of a device and/or its serial number.
 What:		/sys/bus/usb/devices/usbX/descriptors
 Description:
 		Contains the interface descriptors, in binary.
 What:		/sys/bus/usb/devices/usbX/idProduct
 Description:
 		Product ID, in hexadecimal.
 What:		/sys/bus/usb/devices/usbX/idVendor
 Description:
 		Vendor ID, in hexadecimal.
 What:		/sys/bus/usb/devices/usbX/devspec
 Description:
 		Displays the Device Tree Open Firmware node of the interface.
 What:		/sys/bus/usb/devices/usbX/avoid_reset_quirk
 Description:
 		Most devices have this set to zero.
 		If the value is 1, enable a USB quirk that prevents this
 		device to use reset.
 		(read/write)
 What:		/sys/bus/usb/devices/usbX/devnum
 Description:
 		USB interface device number, in decimal.
 What:		/sys/bus/usb/devices/usbX/devpath
 Description:
 		String containing the USB interface device path.
 What:		/sys/bus/usb/devices/usbX/manufacturer
 Description:
 		Vendor specific string containing the name of the
 		manufacturer of the device.
 What:		/sys/bus/usb/devices/usbX/maxchild
 Description:
 		Number of ports of an USB hub
 What:		/sys/bus/usb/devices/usbX/persist
 Description:
 		Keeps the device even if it gets disconnected.
 What:		/sys/bus/usb/devices/usbX/product
 Description:
 		Vendor specific string containing the name of the
 		device's product.
 What:		/sys/bus/usb/devices/usbX/speed
 Description:
 		Shows the device's max speed, according to the USB version,
 		in Mbps.
 		Can be:
 			=======		====================
 			Unknown		speed unknown
 			1.5		Low speed
 			15		Full speed
 			480		High Speed
 			5000		Super Speed
 			10000		Super Speed+
 			20000		Super Speed+ Gen 2x2
 			=======		====================
 What:		/sys/bus/usb/devices/usbX/supports_autosuspend
 Description:
 		Returns 1 if the device doesn't support autosuspend.
 		Otherwise, returns 0.
 What:		/sys/bus/usb/devices/usbX/urbnum
 Description:
 		Number of URBs submitted for the whole device.
 What:		/sys/bus/usb/devices/usbX/version
 Description:
 		String containing the USB device version, as encoded
 		at the BCD descriptor.
 What:		/sys/bus/usb/devices/usbX/power/autosuspend
 Description:
 		Time in milliseconds for the device to autosuspend. If the
 		value is negative, then autosuspend is prevented.
 		(read/write)
 What:		/sys/bus/usb/devices/usbX/power/active_duration
 Description:
 		The total time the device has not been suspended.
 What:		/sys/bus/usb/devices/usbX/power/connected_duration
 Description:
 		The total time (in msec) that the device has been connected.
 What:		/sys/bus/usb/devices/usbX/power/level
 Description:
 What:		/sys/bus/usb/devices/usbX/ep_<N>/bEndpointAddress
 Description:
 		The address of the endpoint described by this descriptor,
 		in hexadecimal. The endpoint direction on this bitmapped field
 		is also shown at:
 			/sys/bus/usb/devices/usbX/ep_<N>/direction
 		See USB specs for its meaning.
 What:		/sys/bus/usb/devices/usbX/ep_<N>/bInterval
 Description:
 		The interval of the endpoint as described on its descriptor,
 		in hexadecimal. The actual interval depends on the version
 		of the USB. Also shown in time units at
 		/sys/bus/usb/devices/usbX/ep_<N>/interval.
 What:		/sys/bus/usb/devices/usbX/ep_<N>/bLength
 Description:
 		Number of bytes of the endpoint descriptor, in hexadecimal.
 What:		/sys/bus/usb/devices/usbX/ep_<N>/bmAttributes
 Description:
 		Attributes which apply to the endpoint as described on its
 		descriptor, in hexadecimal. The endpoint type on this
 		bitmapped field is also shown at:
 			/sys/bus/usb/devices/usbX/ep_<N>/type
 		See USB specs for its meaning.
 What:		/sys/bus/usb/devices/usbX/ep_<N>/direction
 Description:
 		Direction of the endpoint. Can be:
 		    - both (on control endpoints)
 		    - in
 		    - out
 What:		/sys/bus/usb/devices/usbX/ep_<N>/interval
 Description:
 		Interval for polling endpoint for data transfers, in
 		milisseconds or microseconds.
 What:		/sys/bus/usb/devices/usbX/ep_<N>/type
 Description:
 		Descriptor type. Can be:
 		    - Control
 		    - Isoc
 		    - Bulk
 		    - Interrupt
 		    - unknown
 What:		/sys/bus/usb/devices/usbX/ep_<N>/wMaxPacketSize
 Description:
 		Maximum packet size this endpoint is capable of
 		sending or receiving, in hexadecimal.
--- a/Documentation/ABI/testing/sysfs-bus-vdpa
+++ b/Documentation/ABI/testing/sysfs-bus-vdpa
@ -1,57 +0,0 @@
 What:		/sys/bus/vdpa/driver_autoprobe
 Date:		March 2020
 Contact:	virtualization@lists.linux-foundation.org
 Description:
 		This file determines whether new devices are immediately bound
 		to a driver after the creation. It initially contains 1, which
 		means the kernel automatically binds devices to a compatible
 		driver immediately after they are created.
 		Writing "0" to this file disable this feature, any other string
 		enable it.
 What:		/sys/bus/vdpa/driver_probe
 Date:		March 2020
 Contact:	virtualization@lists.linux-foundation.org
 Description:
 		Writing a device name to this file will cause the kernel binds
 		devices to a compatible driver.
 		This can be useful when /sys/bus/vdpa/driver_autoprobe is
 		disabled.
 What:		/sys/bus/vdpa/drivers/.../bind
 Date:		March 2020
 Contact:	virtualization@lists.linux-foundation.org
 Description:
 		Writing a device name to this file will cause the driver to
 		attempt to bind to the device. This is useful for overriding
 		default bindings.
 What:		/sys/bus/vdpa/drivers/.../unbind
 Date:		March 2020
 Contact:	virtualization@lists.linux-foundation.org
 Description:
 		Writing a device name to this file will cause the driver to
 		attempt to unbind from the device. This may be useful when
 		overriding default bindings.
 What:		/sys/bus/vdpa/devices/.../driver_override
 Date:		November 2021
 Contact:	virtualization@lists.linux-foundation.org
 Description:
 		This file allows the driver for a device to be specified.
 		When specified, only a driver with a name matching the value
 		written to driver_override will have an opportunity to bind to
 		the device. The override is specified by writing a string to the
 		driver_override file (echo vhost-vdpa > driver_override) and may
 		be cleared with an empty string (echo > driver_override).
 		This returns the device to standard matching rules binding.
 		Writing to driver_override does not automatically unbind the
 		device from its current driver or make any attempt to
 		automatically load the specified driver. If no driver with a
 		matching name is currently loaded in the kernel, the device will
 		not bind to any driver. This also allows devices to opt-out of
 		driver binding using a driver_override name such as "none".
 		Only a single driver may be specified in the override, there is
 		no support for parsing delimiters.
--- a/Documentation/ABI/testing/sysfs-class-bdi
+++ b/Documentation/ABI/testing/sysfs-class-bdi
@ -23,17 +23,14 @@ default
 	The default backing dev, used for non-block device backed
 	filesystems which do not provide their own BDI.
-What:		/sys/class/bdi/<bdi>/read_ahead_kb
+Files under /sys/class/bdi/<bdi>/
-Date:		January 2008
+
-Contact:	Peter Zijlstra <a.p.zijlstra@chello.nl>
+read_ahead_kb (read-write)
-Description:
+
 	Size of the read-ahead window in kilobytes
-	(read-write)
+min_ratio (read-write)
-What:		/sys/class/bdi/<bdi>/min_ratio
+
 Date:		January 2008
 Contact:	Peter Zijlstra <a.p.zijlstra@chello.nl>
 Description:
 	Under normal circumstances each device is given a part of the
 	total write-back cache that relates to its current average
 	writeout speed in relation to the other devices.
@ -42,12 +39,8 @@ Description:
 	percentage of the write-back cache to a particular device.
 	For example, this is useful for providing a minimum QoS.
-	(read-write)
+max_ratio (read-write)
 What:		/sys/class/bdi/<bdi>/max_ratio
 Date:		January 2008
 Contact:	Peter Zijlstra <a.p.zijlstra@chello.nl>
 Description:
 	Allows limiting a particular device to use not more than the
 	given percentage of the write-back cache.  This is useful in
 	situations where we want to avoid one device taking all or
@ -55,12 +48,7 @@ Description:
 	mount that is prone to get stuck, or a FUSE mount which cannot
 	be trusted to play fair.
-	(read-write)
+stable_pages_required (read-only)
-What:		/sys/class/bdi/<bdi>/stable_pages_required
+
 Date:		January 2008
 Contact:	Peter Zijlstra <a.p.zijlstra@chello.nl>
 Description:
 	If set, the backing device requires that all pages comprising a write
 	request must not be changed until writeout is complete.
 	(read-only)
--- a/Documentation/ABI/testing/sysfs-class-cxl
+++ b/Documentation/ABI/testing/sysfs-class-cxl
@ -103,8 +103,8 @@ What:           /sys/class/cxl/<afu>/api_version_compatible
 Date:           September 2014
 Contact:        linuxppc-dev@lists.ozlabs.org
 Description:    read only
-                Decimal value of the lowest version of the userspace API
+                Decimal value of the the lowest version of the userspace API
-                this kernel supports.
+                this this kernel supports.
 Users:		https://github.com/ibm-capi/libcxl
@ -166,11 +166,10 @@ Description:    read only
                Decimal value of the Per Process MMIO space length.
 Users:		https://github.com/ibm-capi/libcxl
-What:           /sys/class/cxl/<afu>m/pp_mmio_off
+What:           /sys/class/cxl/<afu>m/pp_mmio_off (not in a guest)
 Date:           September 2014
 Contact:        linuxppc-dev@lists.ozlabs.org
 Description:    read only
                (not in a guest)
                Decimal value of the Per Process MMIO space offset.
 Users:		https://github.com/ibm-capi/libcxl
@ -191,31 +190,28 @@ Description:    read only
                Identifies the revision level of the PSL.
 Users:		https://github.com/ibm-capi/libcxl
-What:           /sys/class/cxl/<card>/base_image
+What:           /sys/class/cxl/<card>/base_image (not in a guest)
 Date:           September 2014
 Contact:        linuxppc-dev@lists.ozlabs.org
 Description:    read only
                (not in a guest)
                Identifies the revision level of the base image for devices
                that support loadable PSLs. For FPGAs this field identifies
                the image contained in the on-adapter flash which is loaded
                during the initial program load.
 Users:		https://github.com/ibm-capi/libcxl
-What:           /sys/class/cxl/<card>/image_loaded
+What:           /sys/class/cxl/<card>/image_loaded (not in a guest)
 Date:           September 2014
 Contact:        linuxppc-dev@lists.ozlabs.org
 Description:    read only
                (not in a guest)
                Will return "user" or "factory" depending on the image loaded
                onto the card.
 Users:		https://github.com/ibm-capi/libcxl
-What:           /sys/class/cxl/<card>/load_image_on_perst
+What:           /sys/class/cxl/<card>/load_image_on_perst (not in a guest)
 Date:           December 2014
 Contact:        linuxppc-dev@lists.ozlabs.org
 Description:    read/write
                (not in a guest)
                Valid entries are "none", "user", and "factory".
                "none" means PERST will not cause image to be loaded to the
                card.  A power cycle is required to load the image.
@ -239,11 +235,10 @@ Description:    write only
                contexts on the card AFUs.
 Users:		https://github.com/ibm-capi/libcxl
-What:		/sys/class/cxl/<card>/perst_reloads_same_image
+What:		/sys/class/cxl/<card>/perst_reloads_same_image (not in a guest)
 Date:		July 2015
 Contact:	linuxppc-dev@lists.ozlabs.org
 Description:	read/write
                (not in a guest)
 		Trust that when an image is reloaded via PERST, it will not
 		have changed.
--- a/Documentation/ABI/testing/sysfs-class-devfreq-event
+++ b/Documentation/ABI/testing/sysfs-class-devfreq-event
@ -1,25 +1,25 @@
-What:		/sys/class/devfreq-event/event<x>/
+What:		/sys/class/devfreq-event/event(x)/
 Date:		January 2017
 Contact:	Chanwoo Choi <cw00.choi@samsung.com>
 Description:
 		Provide a place in sysfs for the devfreq-event objects.
 		This allows accessing various devfreq-event specific variables.
-		The name of devfreq-event object denoted as 'event<x>' which
+		The name of devfreq-event object denoted as 'event(x)' which
 		includes the unique number of 'x' for each devfreq-event object.
-What:		/sys/class/devfreq-event/event<x>/name
+What:		/sys/class/devfreq-event/event(x)/name
 Date:		January 2017
 Contact:	Chanwoo Choi <cw00.choi@samsung.com>
 Description:
-		The /sys/class/devfreq-event/event<x>/name attribute contains
+		The /sys/class/devfreq-event/event(x)/name attribute contains
 		the name of the devfreq-event object. This attribute is
 		read-only.
-What:		/sys/class/devfreq-event/event<x>/enable_count
+What:		/sys/class/devfreq-event/event(x)/enable_count
 Date:		January 2017
 Contact:	Chanwoo Choi <cw00.choi@samsung.com>
 Description:
-		The /sys/class/devfreq-event/event<x>/enable_count attribute
+		The /sys/class/devfreq-event/event(x)/enable_count attribute
 		contains the reference count to enable the devfreq-event
 		object. If the device is enabled, the value of attribute is
 		greater than zero.
--- a/Documentation/ABI/testing/sysfs-class-extcon
+++ b/Documentation/ABI/testing/sysfs-class-extcon
@ -65,19 +65,19 @@ Description:
 		interface associated with each cable cannot update
 		multiple cable states of an extcon device simultaneously.
-What:		/sys/class/extcon/.../cable.X/name
+What:		/sys/class/extcon/.../cable.x/name
 Date:		February 2012
 Contact:	MyungJoo Ham <myungjoo.ham@samsung.com>
 Description:
-		The /sys/class/extcon/.../cable.X/name shows the name of cable
+		The /sys/class/extcon/.../cable.x/name shows the name of cable
-		"X" (integer between 0 and 31) of an extcon device.
+		"x" (integer between 0 and 31) of an extcon device.
-What:		/sys/class/extcon/.../cable.X/state
+What:		/sys/class/extcon/.../cable.x/state
 Date:		February 2012
 Contact:	MyungJoo Ham <myungjoo.ham@samsung.com>
 Description:
-		The /sys/class/extcon/.../cable.X/state shows and stores the
+		The /sys/class/extcon/.../cable.x/state shows and stores the
-		state of cable "X" (integer between 0 and 31) of an extcon
+		state of cable "x" (integer between 0 and 31) of an extcon
 		device. The state value is either 0 (detached) or 1
 		(attached).
--- a/Documentation/ABI/testing/sysfs-class-fc
+++ b/Documentation/ABI/testing/sysfs-class-fc
@ -1,27 +0,0 @@
 What:		/sys/class/fc/fc_udev_device/appid_store
 Date:		Aug 2021
 Contact:	Muneendra Kumar <muneendra.kumar@broadconm.com>
 Description:
 		This interface allows an admin to set an FC application
 		identifier in the blkcg associated with a cgroup id. The
 		identifier is typically a UUID that is associated with
 		an application or logical entity such as a virtual
 		machine or container group. The application or logical
 		entity utilizes a block device via the cgroup id.
 		FC adapter drivers may query the identifier and tag FC
 		traffic based on the identifier. FC host and FC fabric
 		entities can utilize the application id and FC traffic
 		tag to identify traffic sources.
 		The interface expects a string "<cgroupid>:<appid>" where:
 		<cgroupid> is inode of the cgroup in hexadecimal
 		<appid> is user provided string upto 128 characters
 		in length.
 		If an appid_store is done for a cgroup id that already
 		has an appid set, the new value will override the
 		previous value.
 		If an admin wants to remove an FC application identifier
 		from a cgroup, an appid_store should be done with the
 		following string: "<cgroupid>:"
--- a/Documentation/ABI/testing/sysfs-class-firmware
+++ b/Documentation/ABI/testing/sysfs-class-firmware
@ -1,77 +0,0 @@
 What: 		/sys/class/firmware/.../data
 Date:		July 2022
 KernelVersion:	5.19
 Contact:	Russ Weight <russell.h.weight@intel.com>
 Description:	The data sysfs file is used for firmware-fallback and for
 		firmware uploads. Cat a firmware image to this sysfs file
 		after you echo 1 to the loading sysfs file. When the firmware
 		image write is complete, echo 0 to the loading sysfs file. This
 		sequence will signal the completion of the firmware write and
 		signal the lower-level driver that the firmware data is
 		available.
 What: 		/sys/class/firmware/.../cancel
 Date:		July 2022
 KernelVersion:	5.19
 Contact:	Russ Weight <russell.h.weight@intel.com>
 Description:	Write-only. For firmware uploads, write a "1" to this file to
 		request that the transfer of firmware data to the lower-level
 		device be canceled. This request will be rejected (EBUSY) if
 		the update cannot be canceled (e.g. a FLASH write is in
 		progress) or (ENODEV) if there is no firmware update in progress.
 What: 		/sys/class/firmware/.../error
 Date:		July 2022
 KernelVersion:	5.19
 Contact:	Russ Weight <russell.h.weight@intel.com>
 Description:	Read-only. Returns a string describing a failed firmware
 		upload. This string will be in the form of <STATUS>:<ERROR>,
 		where <STATUS> will be one of the status strings described
 		for the status sysfs file and <ERROR> will be one of the
 		following: "hw-error", "timeout", "user-abort", "device-busy",
 		"invalid-file-size", "read-write-error", "flash-wearout". The
 		error sysfs file is only meaningful when the current firmware
 		upload status is "idle". If this file is read while a firmware
 		transfer is in progress, then the read will fail with EBUSY.
 What: 		/sys/class/firmware/.../loading
 Date:		July 2022
 KernelVersion:	5.19
 Contact:	Russ Weight <russell.h.weight@intel.com>
 Description:	The loading sysfs file is used for both firmware-fallback and
 		for firmware uploads. Echo 1 onto the loading file to indicate
 		you are writing a firmware file to the data sysfs node. Echo
 		-1 onto this file to abort the data write or echo 0 onto this
 		file to indicate that the write is complete. For firmware
 		uploads, the zero value also triggers the transfer of the
 		firmware data to the lower-level device driver.
 What: 		/sys/class/firmware/.../remaining_size
 Date:		July 2022
 KernelVersion:	5.19
 Contact:	Russ Weight <russell.h.weight@intel.com>
 Description:	Read-only. For firmware upload, this file contains the size
 		of the firmware data that remains to be transferred to the
 		lower-level device driver. The size value is initialized to
 		the full size of the firmware image that was previously
 		written to the data sysfs file. This value is periodically
 		updated during the "transferring" phase of the firmware
 		upload.
 		Format: "%u".
 What: 		/sys/class/firmware/.../status
 Date:		July 2022
 KernelVersion:	5.19
 Contact:	Russ Weight <russell.h.weight@intel.com>
 Description:	Read-only. Returns a string describing the current status of
 		a firmware upload. The string will be one of the following:
 		idle, "receiving", "preparing", "transferring", "programming".
 What: 		/sys/class/firmware/.../timeout
 Date:		July 2022
 KernelVersion:	5.19
 Contact:	Russ Weight <russell.h.weight@intel.com>
 Description:	This file supports the timeout mechanism for firmware
 		fallback.  This file has no affect on firmware uploads. For
 		more information on timeouts please see the documentation
 		for firmware fallback.
--- a/Documentation/ABI/testing/sysfs-class-firmware-attributes
+++ b/Documentation/ABI/testing/sysfs-class-firmware-attributes
@ -116,7 +116,7 @@ Description:
 					    <value>[ForceIf:<attribute>=<value>]
 					    <value>[ForceIfNot:<attribute>=<value>]
-					For example::
+					For example:
 					    LegacyOrom/dell_value_modifier has value:
 						    Disabled[ForceIf:SecureBoot=Enabled]
@ -161,15 +161,6 @@ Description:
 						power-on:
 							Representing a password required to use
 							the system
 						system-mgmt:
 							Representing System Management password.
 							See Lenovo extensions section for details
 						HDD:
 							Representing HDD password
 							See Lenovo extensions section for details
 						NVMe:
 							Representing NVMe password
 							See Lenovo extensions section for details
 		mechanism:
 					The means of authentication.  This attribute is mandatory.
@ -212,17 +203,10 @@ Description:
 		the next boot.
 		Lenovo specific class extensions
-		--------------------------------
+		------------------------------
 		On Lenovo systems the following additional settings are available:
 		role: system-mgmt	This gives the same authority as the bios-admin password to control
 					security related features. The authorities allocated can be set via
 					the BIOS menu SMP Access Control Policy
 		role: HDD & NVMe	This password is used to unlock access to the drive at boot. Note see
 					'level' and 'index' extensions below.
 		lenovo_encoding:
 					The encoding method that is used. This can be either "ascii"
 					or "scancode". Default is set to "ascii"
@ -232,71 +216,6 @@ Description:
 					two char code (e.g. "us", "fr", "gr") and may vary per platform.
 					Default is set to "us"
 		level:
 					Available for HDD and NVMe authentication to set 'user' or 'master'
 					privilege level.
 					If only the user password is configured then this should be used to
 					unlock the drive at boot. If both master and user passwords are set
 					then either can be used. If a master password is set a user password
 					is required.
 					This attribute defaults to 'user' level
 		index:
 					Used with HDD and NVME authentication to set the drive index
 					that is being referenced (e.g hdd0, hdd1 etc)
 					This attribute defaults to device 0.
 		certificate, signature, save_signature:
 					These attributes are used for certificate based authentication. This is
 					used in conjunction with a signing server as an alternative to password
 					based authentication.
 					The user writes to the attribute(s) with a BASE64 encoded string obtained
 					from the signing server.
 					The attributes can be displayed to check the stored value.
 					Some usage examples:
 						Installing a certificate to enable feature::
 							echo "supervisor password" > authentication/Admin/current_password
 							echo "signed certificate" > authentication/Admin/certificate
 						Updating the installed certificate::
 							echo "signature" > authentication/Admin/signature
 							echo "signed certificate" > authentication/Admin/certificate
 						Removing the installed certificate::
 							echo "signature" > authentication/Admin/signature
 							echo "" > authentication/Admin/certificate
 						Changing a BIOS setting::
 							echo "signature" > authentication/Admin/signature
 							echo "save signature" > authentication/Admin/save_signature
 							echo Enable > attribute/PasswordBeep/current_value
 					You cannot enable certificate authentication if a supervisor password
 					has not been set.
 					Clearing the certificate results in no bios-admin authentication method
 					being configured allowing anyone to make changes.
 					After any of these operations the system must reboot for the changes to
 					take effect.
 		certificate_thumbprint:
 					Read only attribute used to display the MD5, SHA1 and SHA256 thumbprints
 					for the certificate installed in the BIOS.
 		certificate_to_password:
 					Write only attribute used to switch from certificate based authentication
 					back to password based.
 					Usage::
 						echo "signature" > authentication/Admin/signature
 						echo "password" > authentication/Admin/certificate_to_password
 What:		/sys/class/firmware-attributes/*/attributes/pending_reboot
 Date:		February 2021
 KernelVersion:	5.11
@ -349,7 +268,7 @@ Description:
 		    # echo "factory" > /sys/class/firmware-attributes/*/device/attributes/reset_bios
 		    # cat /sys/class/firmware-attributes/*/device/attributes/reset_bios
-		    builtinsafe lastknowngood [factory] custom
+		    # builtinsafe lastknowngood [factory] custom
 		Note that any changes to this attribute requires a reboot
 		for changes to take effect.
--- a/Documentation/ABI/testing/sysfs-class-gnss
+++ b/Documentation/ABI/testing/sysfs-class-gnss
@ -1,4 +1,4 @@
-What:		/sys/class/gnss/gnss<N>/type
+What:		/sys/class/gnss/gnssN/type
 Date:		May 2018
 KernelVersion:	4.18
 Contact:	Johan Hovold <johan@kernel.org>
--- a/Documentation/ABI/testing/sysfs-class-hwmon
+++ b/Documentation/ABI/testing/sysfs-class-hwmon
@ -1,949 +0,0 @@
 What:		/sys/class/hwmon/hwmonX/name
 Description:
 		The chip name.
 		This should be a short, lowercase string, not containing
 		whitespace, dashes, or the wildcard character '*'.
 		This attribute represents the chip name. It is the only
 		mandatory attribute.
 		I2C devices get this attribute created automatically.
 		RO
 What:		/sys/class/hwmon/hwmonX/label
 Description:
 		A descriptive label that allows to uniquely identify a
 		device within the system.
 		The contents of the label are free-form.
 		RO
 What:		/sys/class/hwmon/hwmonX/update_interval
 Description:
 		The interval at which the chip will update readings.
 		Unit: millisecond
 		RW
 		Some devices have a variable update rate or interval.
 		This attribute can be used to change it to the desired value.
 What:		/sys/class/hwmon/hwmonX/inY_min
 Description:
 		Voltage min value.
 		Unit: millivolt
 		RW
 What:		/sys/class/hwmon/hwmonX/inY_lcrit
 Description:
 		Voltage critical min value.
 		Unit: millivolt
 		RW
 		If voltage drops to or below this limit, the system may
 		take drastic action such as power down or reset. At the very
 		least, it should report a fault.
 What:		/sys/class/hwmon/hwmonX/inY_max
 Description:
 		Voltage max value.
 		Unit: millivolt
 		RW
 What:		/sys/class/hwmon/hwmonX/inY_crit
 Description:
 		Voltage critical max value.
 		Unit: millivolt
 		RW
 		If voltage reaches or exceeds this limit, the system may
 		take drastic action such as power down or reset. At the very
 		least, it should report a fault.
 What:		/sys/class/hwmon/hwmonX/inY_input
 Description:
 		Voltage input value.
 		Unit: millivolt
 		RO
 		Voltage measured on the chip pin.
 		Actual voltage depends on the scaling resistors on the
 		motherboard, as recommended in the chip datasheet.
 		This varies by chip and by motherboard.
 		Because of this variation, values are generally NOT scaled
 		by the chip driver, and must be done by the application.
 		However, some drivers (notably lm87 and via686a)
 		do scale, because of internal resistors built into a chip.
 		These drivers will output the actual voltage. Rule of
 		thumb: drivers should report the voltage values at the
 		"pins" of the chip.
 What:		/sys/class/hwmon/hwmonX/inY_average
 Description:
 		Average voltage
 		Unit: millivolt
 		RO
 What:		/sys/class/hwmon/hwmonX/inY_lowest
 Description:
 		Historical minimum voltage
 		Unit: millivolt
 		RO
 What:		/sys/class/hwmon/hwmonX/inY_highest
 Description:
 		Historical maximum voltage
 		Unit: millivolt
 		RO
 What:		/sys/class/hwmon/hwmonX/inY_reset_history
 Description:
 		Reset inX_lowest and inX_highest
 		WO
 What:		/sys/class/hwmon/hwmonX/in_reset_history
 Description:
 		Reset inX_lowest and inX_highest for all sensors
 		WO
 What:		/sys/class/hwmon/hwmonX/inY_label
 Description:
 		Suggested voltage channel label.
 		Text string
 		Should only be created if the driver has hints about what
 		this voltage channel is being used for, and user-space
 		doesn't. In all other cases, the label is provided by
 		user-space.
 		RO
 What:		/sys/class/hwmon/hwmonX/inY_enable
 Description:
 		Enable or disable the sensors.
 		When disabled the sensor read will return -ENODATA.
 		- 1: Enable
 		- 0: Disable
 		RW
 What:		/sys/class/hwmon/hwmonX/cpuY_vid
 Description:
 		CPU core reference voltage.
 		Unit: millivolt
 		RO
 		Not always correct.
 What:		/sys/class/hwmon/hwmonX/vrm
 Description:
 		Voltage Regulator Module version number.
 		RW (but changing it should no more be necessary)
 		Originally the VRM standard version multiplied by 10, but now
 		an arbitrary number, as not all standards have a version
 		number.
 		Affects the way the driver calculates the CPU core reference
 		voltage from the vid pins.
 What:		/sys/class/hwmon/hwmonX/inY_rated_min
 Description:
 		Minimum rated voltage.
 		Unit: millivolt
 		RO
 What:		/sys/class/hwmon/hwmonX/inY_rated_max
 Description:
 		Maximum rated voltage.
 		Unit: millivolt
 		RO
 What:		/sys/class/hwmon/hwmonX/fanY_min
 Description:
 		Fan minimum value
 		Unit: revolution/min (RPM)
 		RW
 What:		/sys/class/hwmon/hwmonX/fanY_max
 Description:
 		Fan maximum value
 		Unit: revolution/min (RPM)
 		Only rarely supported by the hardware.
 		RW
 What:		/sys/class/hwmon/hwmonX/fanY_input
 Description:
 		Fan input value.
 		Unit: revolution/min (RPM)
 		RO
 What:		/sys/class/hwmon/hwmonX/fanY_div
 Description:
 		Fan divisor.
 		Integer value in powers of two (1, 2, 4, 8, 16, 32, 64, 128).
 		RW
 		Some chips only support values 1, 2, 4 and 8.
 		Note that this is actually an internal clock divisor, which
 		affects the measurable speed range, not the read value.
 What:		/sys/class/hwmon/hwmonX/fanY_pulses
 Description:
 		Number of tachometer pulses per fan revolution.
 		Integer value, typically between 1 and 4.
 		RW
 		This value is a characteristic of the fan connected to the
 		device's input, so it has to be set in accordance with the fan
 		model.
 		Should only be created if the chip has a register to configure
 		the number of pulses. In the absence of such a register (and
 		thus attribute) the value assumed by all devices is 2 pulses
 		per fan revolution.
 What:		/sys/class/hwmon/hwmonX/fanY_target
 Description:
 		Desired fan speed
 		Unit: revolution/min (RPM)
 		RW
 		Only makes sense if the chip supports closed-loop fan speed
 		control based on the measured fan speed.
 What:		/sys/class/hwmon/hwmonX/fanY_label
 Description:
 		Suggested fan channel label.
 		Text string
 		Should only be created if the driver has hints about what
 		this fan channel is being used for, and user-space doesn't.
 		In all other cases, the label is provided by user-space.
 		RO
 What:		/sys/class/hwmon/hwmonX/fanY_enable
 Description:
 		Enable or disable the sensors.
 		When disabled the sensor read will return -ENODATA.
 		- 1: Enable
 		- 0: Disable
 		RW
 What:		/sys/class/hwmon/hwmonX/pwmY
 Description:
 		Pulse width modulation fan control.
 		Integer value in the range 0 to 255
 		RW
 		255 is max or 100%.
 What:		/sys/class/hwmon/hwmonX/pwmY_enable
 Description:
 		Fan speed control method:
 		- 0: no fan speed control (i.e. fan at full speed)
 		- 1: manual fan speed control enabled (using `pwmY`)
 		- 2+: automatic fan speed control enabled
 		Check individual chip documentation files for automatic mode
 		details.
 		RW
 What:		/sys/class/hwmon/hwmonX/pwmY_mode
 Description:
 		- 0: DC mode (direct current)
 		- 1: PWM mode (pulse-width modulation)
 		RW
 What:		/sys/class/hwmon/hwmonX/pwmY_freq
 Description:
 		Base PWM frequency in Hz.
 		Only possibly available when pwmN_mode is PWM, but not always
 		present even then.
 		RW
 What:		/sys/class/hwmon/hwmonX/pwmY_auto_channels_temp
 Description:
 		Select which temperature channels affect this PWM output in
 		auto mode.
 		Bitfield, 1 is temp1, 2 is temp2, 4 is temp3 etc...
 		Which values are possible depend on the chip used.
 		RW
 What:		/sys/class/hwmon/hwmonX/pwmY_auto_pointZ_pwm
 What:		/sys/class/hwmon/hwmonX/pwmY_auto_pointZ_temp
 What:		/sys/class/hwmon/hwmonX/pwmY_auto_pointZ_temp_hyst
 Description:
 		Define the PWM vs temperature curve.
 		Number of trip points is chip-dependent. Use this for chips
 		which associate trip points to PWM output channels.
 		RW
 What:		/sys/class/hwmon/hwmonX/tempY_auto_pointZ_pwm
 What:		/sys/class/hwmon/hwmonX/tempY_auto_pointZ_temp
 What:		/sys/class/hwmon/hwmonX/tempY_auto_pointZ_temp_hyst
 Description:
 		Define the PWM vs temperature curve.
 		Number of trip points is chip-dependent. Use this for chips
 		which associate trip points to temperature channels.
 		RW
 What:		/sys/class/hwmon/hwmonX/tempY_type
 Description:
 		Sensor type selection.
 		Integers 1 to 6
 		RW
 		- 1: CPU embedded diode
 		- 2: 3904 transistor
 		- 3: thermal diode
 		- 4: thermistor
 		- 5: AMD AMDSI
 		- 6: Intel PECI
 		Not all types are supported by all chips
 What:		/sys/class/hwmon/hwmonX/tempY_max
 Description:
 		Temperature max value.
 		Unit: millidegree Celsius (or millivolt, see below)
 		RW
 What:		/sys/class/hwmon/hwmonX/tempY_min
 Description:
 		Temperature min value.
 		Unit: millidegree Celsius
 		RW
 What:		/sys/class/hwmon/hwmonX/tempY_max_hyst
 Description:
 		Temperature hysteresis value for max limit.
 		Unit: millidegree Celsius
 		Must be reported as an absolute temperature, NOT a delta
 		from the max value.
 		RW
 What:		/sys/class/hwmon/hwmonX/tempY_min_hyst
 Description:
 		Temperature hysteresis value for min limit.
 		Unit: millidegree Celsius
 		Must be reported as an absolute temperature, NOT a delta
 		from the min value.
 		RW
 What:		/sys/class/hwmon/hwmonX/tempY_input
 Description:
 		Temperature input value.
 		Unit: millidegree Celsius
 		RO
 What:		/sys/class/hwmon/hwmonX/tempY_crit
 Description:
 		Temperature critical max value, typically greater than
 		corresponding temp_max values.
 		Unit: millidegree Celsius
 		RW
 What:		/sys/class/hwmon/hwmonX/tempY_crit_alarm
 Description:
 		Critical high temperature alarm flag.
 		- 0: OK
 		- 1: temperature has reached tempY_crit
 		RW
 		Contrary to regular alarm flags which clear themselves
 		automatically when read, this one sticks until cleared by
 		the user. This is done by writing 0 to the file. Writing
 		other values is unsupported.
 What:		/sys/class/hwmon/hwmonX/tempY_crit_hyst
 Description:
 		Temperature hysteresis value for critical limit.
 		Unit: millidegree Celsius
 		Must be reported as an absolute temperature, NOT a delta
 		from the critical value.
 		RW
 What:		/sys/class/hwmon/hwmonX/tempY_emergency
 Description:
 		Temperature emergency max value, for chips supporting more than
 		two upper temperature limits. Must be equal or greater than
 		corresponding temp_crit values.
 		Unit: millidegree Celsius
 		RW
 What:		/sys/class/hwmon/hwmonX/tempY_emergency_hyst
 Description:
 		Temperature hysteresis value for emergency limit.
 		Unit: millidegree Celsius
 		Must be reported as an absolute temperature, NOT a delta
 		from the emergency value.
 		RW
 What:		/sys/class/hwmon/hwmonX/tempY_lcrit
 Description:
 		Temperature critical min value, typically lower than
 		corresponding temp_min values.
 		Unit: millidegree Celsius
 		RW
 What:		/sys/class/hwmon/hwmonX/tempY_lcrit_hyst
 Description:
 		Temperature hysteresis value for critical min limit.
 		Unit: millidegree Celsius
 		Must be reported as an absolute temperature, NOT a delta
 		from the critical min value.
 		RW
 What:		/sys/class/hwmon/hwmonX/tempY_offset
 Description:
 		Temperature offset which is added to the temperature reading
 		by the chip.
 		Unit: millidegree Celsius
 		Read/Write value.
 What:		/sys/class/hwmon/hwmonX/tempY_label
 Description:
 		Suggested temperature channel label.
 		Text string
 		Should only be created if the driver has hints about what
 		this temperature channel is being used for, and user-space
 		doesn't. In all other cases, the label is provided by
 		user-space.
 		RO
 What:		/sys/class/hwmon/hwmonX/tempY_lowest
 Description:
 		Historical minimum temperature
 		Unit: millidegree Celsius
 		RO
 What:		/sys/class/hwmon/hwmonX/tempY_highest
 Description:
 		Historical maximum temperature
 		Unit: millidegree Celsius
 		RO
 What:		/sys/class/hwmon/hwmonX/tempY_reset_history
 Description:
 		Reset temp_lowest and temp_highest
 		WO
 What:		/sys/class/hwmon/hwmonX/temp_reset_history
 Description:
 		Reset temp_lowest and temp_highest for all sensors
 		WO
 What:		/sys/class/hwmon/hwmonX/tempY_enable
 Description:
 		Enable or disable the sensors.
 		When disabled the sensor read will return -ENODATA.
 		- 1: Enable
 		- 0: Disable
 		RW
 What:		/sys/class/hwmon/hwmonX/tempY_rated_min
 Description:
 		Minimum rated temperature.
 		Unit: millidegree Celsius
 		RO
 What:		/sys/class/hwmon/hwmonX/tempY_rated_max
 Description:
 		Maximum rated temperature.
 		Unit: millidegree Celsius
 		RO
 What:		/sys/class/hwmon/hwmonX/currY_max
 Description:
 		Current max value
 		Unit: milliampere
 		RW
 What:		/sys/class/hwmon/hwmonX/currY_min
 Description:
 		Current min value.
 		Unit: milliampere
 		RW
 What:		/sys/class/hwmon/hwmonX/currY_lcrit
 Description:
 		Current critical low value
 		Unit: milliampere
 		RW
 What:		/sys/class/hwmon/hwmonX/currY_crit
 Description:
 		Current critical high value.
 		Unit: milliampere
 		RW
 What:		/sys/class/hwmon/hwmonX/currY_input
 Description:
 		Current input value
 		Unit: milliampere
 		RO
 What:		/sys/class/hwmon/hwmonX/currY_average
 Description:
 		Average current use
 		Unit: milliampere
 		RO
 What:		/sys/class/hwmon/hwmonX/currY_lowest
 Description:
 		Historical minimum current
 		Unit: milliampere
 		RO
 What:		/sys/class/hwmon/hwmonX/currY_highest
 Description:
 		Historical maximum current
 		Unit: milliampere
 		RO
 What:		/sys/class/hwmon/hwmonX/currY_reset_history
 Description:
 		Reset currX_lowest and currX_highest
 		WO
 What:		/sys/class/hwmon/hwmonX/curr_reset_history
 Description:
 		Reset currX_lowest and currX_highest for all sensors
 		WO
 What:		/sys/class/hwmon/hwmonX/currY_enable
 Description:
 		Enable or disable the sensors.
 		When disabled the sensor read will return -ENODATA.
 		- 1: Enable
 		- 0: Disable
 		RW
 What:		/sys/class/hwmon/hwmonX/currY_rated_min
 Description:
 		Minimum rated current.
 		Unit: milliampere
 		RO
 What:		/sys/class/hwmon/hwmonX/currY_rated_max
 Description:
 		Maximum rated current.
 		Unit: milliampere
 		RO
 What:		/sys/class/hwmon/hwmonX/powerY_average
 Description:
 		Average power use
 		Unit: microWatt
 		RO
 What:		/sys/class/hwmon/hwmonX/powerY_average_interval
 Description:
 		Power use averaging interval.  A poll
 		notification is sent to this file if the
 		hardware changes the averaging interval.
 		Unit: milliseconds
 		RW
 What:		/sys/class/hwmon/hwmonX/powerY_average_interval_max
 Description:
 		Maximum power use averaging interval
 		Unit: milliseconds
 		RO
 What:		/sys/class/hwmon/hwmonX/powerY_average_interval_min
 Description:
 		Minimum power use averaging interval
 		Unit: milliseconds
 		RO
 What:		/sys/class/hwmon/hwmonX/powerY_average_highest
 Description:
 		Historical average maximum power use
 		Unit: microWatt
 		RO
 What:		/sys/class/hwmon/hwmonX/powerY_average_lowest
 Description:
 		Historical average minimum power use
 		Unit: microWatt
 		RO
 What:		/sys/class/hwmon/hwmonX/powerY_average_max
 Description:
 		A poll notification is sent to
 		`powerY_average` when power use
 		rises above this value.
 		Unit: microWatt
 		RW
 What:		/sys/class/hwmon/hwmonX/powerY_average_min
 Description:
 		A poll notification is sent to
 		`powerY_average` when power use
 		sinks below this value.
 		Unit: microWatt
 		RW
 What:		/sys/class/hwmon/hwmonX/powerY_input
 Description:
 		Instantaneous power use
 		Unit: microWatt
 		RO
 What:		/sys/class/hwmon/hwmonX/powerY_input_highest
 Description:
 		Historical maximum power use
 		Unit: microWatt
 		RO
 What:		/sys/class/hwmon/hwmonX/powerY_input_lowest
 Description:
 		Historical minimum power use
 		Unit: microWatt
 		RO
 What:		/sys/class/hwmon/hwmonX/powerY_reset_history
 Description:
 		Reset input_highest, input_lowest,
 		average_highest and average_lowest.
 		WO
 What:		/sys/class/hwmon/hwmonX/powerY_accuracy
 Description:
 		Accuracy of the power meter.
 		Unit: Percent
 		RO
 What:		/sys/class/hwmon/hwmonX/powerY_cap
 Description:
 		If power use rises above this limit, the
 		system should take action to reduce power use.
 		A poll notification is sent to this file if the
 		cap is changed by the hardware.  The `*_cap`
 		files only appear if the cap is known to be
 		enforced by hardware.
 		Unit: microWatt
 		RW
 What:		/sys/class/hwmon/hwmonX/powerY_cap_hyst
 Description:
 		Margin of hysteresis built around capping and
 		notification.
 		Unit: microWatt
 		RW
 What:		/sys/class/hwmon/hwmonX/powerY_cap_max
 Description:
 		Maximum cap that can be set.
 		Unit: microWatt
 		RO
 What:		/sys/class/hwmon/hwmonX/powerY_cap_min
 Description:
 		Minimum cap that can be set.
 		Unit: microWatt
 		RO
 What:		/sys/class/hwmon/hwmonX/powerY_max
 Description:
 		Maximum power.
 		Unit: microWatt
 		RW
 What:		/sys/class/hwmon/hwmonX/powerY_crit
 Description:
 		Critical maximum power.
 		If power rises to or above this limit, the
 		system is expected take drastic action to reduce
 		power consumption, such as a system shutdown or
 		a forced powerdown of some devices.
 		Unit: microWatt
 		RW
 What:		/sys/class/hwmon/hwmonX/powerY_enable
 Description:
 		Enable or disable the sensors.
 		When disabled the sensor read will return
 		-ENODATA.
 		- 1: Enable
 		- 0: Disable
 		RW
 What:		/sys/class/hwmon/hwmonX/powerY_rated_min
 Description:
 		Minimum rated power.
 		Unit: microWatt
 		RO
 What:		/sys/class/hwmon/hwmonX/powerY_rated_max
 Description:
 		Maximum rated power.
 		Unit: microWatt
 		RO
 What:		/sys/class/hwmon/hwmonX/energyY_input
 Description:
 		Cumulative energy use
 		Unit: microJoule
 		RO
 What:		/sys/class/hwmon/hwmonX/energyY_enable
 Description:
 		Enable or disable the sensors.
 		When disabled the sensor read will return
 		-ENODATA.
 		- 1: Enable
 		- 0: Disable
 		RW
 What:		/sys/class/hwmon/hwmonX/humidityY_input
 Description:
 		Humidity
 		Unit: milli-percent (per cent mille, pcm)
 		RO
 What:		/sys/class/hwmon/hwmonX/humidityY_enable
 Description:
 		Enable or disable the sensors
 		When disabled the sensor read will return
 		-ENODATA.
 		- 1: Enable
 		- 0: Disable
 		RW
 What:		/sys/class/hwmon/hwmonX/humidityY_rated_min
 Description:
 		Minimum rated humidity.
 		Unit: milli-percent (per cent mille, pcm)
 		RO
 What:		/sys/class/hwmon/hwmonX/humidityY_rated_max
 Description:
 		Maximum rated humidity.
 		Unit: milli-percent (per cent mille, pcm)
 		RO
 What:		/sys/class/hwmon/hwmonX/intrusionY_alarm
 Description:
 		Chassis intrusion detection
 		- 0: OK
 		- 1: intrusion detected
 		RW
 		Contrary to regular alarm flags which clear themselves
 		automatically when read, this one sticks until cleared by
 		the user. This is done by writing 0 to the file. Writing
 		other values is unsupported.
 What:		/sys/class/hwmon/hwmonX/intrusionY_beep
 Description:
 		Chassis intrusion beep
 		- 0: disable
 		- 1: enable
 		RW
 What:		/sys/class/hwmon/hwmonX/device/pec
 Description:
 		PEC support on I2C devices
 		- 0, off, n: disable
 		- 1, on, y: enable
 		RW
--- a/Documentation/ABI/testing/sysfs-class-mei
+++ b/Documentation/ABI/testing/sysfs-class-mei
@ -6,7 +6,7 @@ Description:
 		The mei/ class sub-directory belongs to mei device class
-What:		/sys/class/mei/mei<N>/
+What:		/sys/class/mei/meiN/
 Date:		May 2014
 KernelVersion:	3.17
 Contact:	Tomas Winkler <tomas.winkler@intel.com>
@ -14,7 +14,7 @@ Description:
 		The /sys/class/mei/meiN directory is created for
 		each probed mei device
-What:		/sys/class/mei/mei<N>/fw_status
+What:		/sys/class/mei/meiN/fw_status
 Date:		Nov 2014
 KernelVersion:	3.19
 Contact:	Tomas Winkler <tomas.winkler@intel.com>
@ -29,7 +29,7 @@ Description:	Display fw status registers content
 		Also number of registers varies between 1 and 6
 		depending on generation.
-What:		/sys/class/mei/mei<N>/hbm_ver
+What:		/sys/class/mei/meiN/hbm_ver
 Date:		Aug 2016
 KernelVersion:	4.9
 Contact:	Tomas Winkler <tomas.winkler@intel.com>
@ -38,7 +38,7 @@ Description:	Display the negotiated HBM protocol version.
 		The HBM protocol version negotiated
 		between the driver and the device.
-What:		/sys/class/mei/mei<N>/hbm_ver_drv
+What:		/sys/class/mei/meiN/hbm_ver_drv
 Date:		Aug 2016
 KernelVersion:	4.9
 Contact:	Tomas Winkler <tomas.winkler@intel.com>
@ -46,7 +46,7 @@ Description:	Display the driver HBM protocol version.
 		The HBM protocol version supported by the driver.
-What:		/sys/class/mei/mei<N>/tx_queue_limit
+What:		/sys/class/mei/meiN/tx_queue_limit
 Date:		Jan 2018
 KernelVersion:	4.16
 Contact:	Tomas Winkler <tomas.winkler@intel.com>
@ -55,7 +55,7 @@ Description:	Configure tx queue limit
 		Set maximal number of pending writes
 		per opened session.
-What:		/sys/class/mei/mei<N>/fw_ver
+What:		/sys/class/mei/meiN/fw_ver
 Date:		May 2018
 KernelVersion:	4.18
 Contact:	Tomas Winkler <tomas.winkler@intel.com>
@ -66,7 +66,7 @@ Description:	Display the ME firmware version.
 		There can be up to three such blocks for different
 		FW components.
-What:		/sys/class/mei/mei<N>/dev_state
+What:		/sys/class/mei/meiN/dev_state
 Date:		Mar 2019
 KernelVersion:	5.1
 Contact:	Tomas Winkler <tomas.winkler@intel.com>
@ -81,7 +81,7 @@ Description:	Display the ME device state.
 		POWER_DOWN
 		POWER_UP
-What:		/sys/class/mei/mei<N>/trc
+What:		/sys/class/mei/meiN/trc
 Date:		Nov 2019
 KernelVersion:	5.5
 Contact:	Tomas Winkler <tomas.winkler@intel.com>
@ -91,7 +91,7 @@ Description:	Display trc status register content
 		status information into trc status register
 		for BIOS and OS to monitor fw health.
-What:		/sys/class/mei/mei<N>/kind
+What:		/sys/class/mei/meiN/kind
 Date:		Jul 2020
 KernelVersion:	5.8
 Contact:	Tomas Winkler <tomas.winkler@intel.com>
--- a/Documentation/ABI/testing/sysfs-class-mic
+++ b/Documentation/ABI/testing/sysfs-class-mic
@ -8,7 +8,7 @@ Description:
 		PCIe form factor add-in Coprocessor card based on the Intel Many
 		Integrated Core (MIC) architecture that runs a Linux OS.
-What:		/sys/class/mic/mic<X>
+What:		/sys/class/mic/mic(x)
 Date:		October 2013
 KernelVersion:	3.13
 Contact:	Sudeep Dutt <sudeep.dutt@intel.com>
@ -17,7 +17,7 @@ Description:
 		represent MIC devices (0,1,..etc). Each directory has
 		information specific to that MIC device.
-What:		/sys/class/mic/mic<X>/family
+What:		/sys/class/mic/mic(x)/family
 Date:		October 2013
 KernelVersion:	3.13
 Contact:	Sudeep Dutt <sudeep.dutt@intel.com>
@ -25,7 +25,7 @@ Description:
 		Provides information about the Coprocessor family for an Intel
 		MIC device. For example - "x100"
-What:		/sys/class/mic/mic<X>/stepping
+What:		/sys/class/mic/mic(x)/stepping
 Date:		October 2013
 KernelVersion:	3.13
 Contact:	Sudeep Dutt <sudeep.dutt@intel.com>
@ -33,7 +33,7 @@ Description:
 		Provides information about the silicon stepping for an Intel
 		MIC device. For example - "A0" or "B0"
-What:		/sys/class/mic/mic<X>/state
+What:		/sys/class/mic/mic(x)/state
 Date:		October 2013
 KernelVersion:	3.13
 Contact:	Sudeep Dutt <sudeep.dutt@intel.com>
@ -69,7 +69,7 @@ Description:
 		"shutdown"  Initiates card OS shutdown.
 		==========  ===================================================
-What:		/sys/class/mic/mic<X>/shutdown_status
+What:		/sys/class/mic/mic(x)/shutdown_status
 Date:		October 2013
 KernelVersion:	3.13
 Contact:	Sudeep Dutt <sudeep.dutt@intel.com>
@ -88,7 +88,7 @@ Description:
 		"restart"   Shutdown because of a restart command.
 		==========  ===================================================
-What:		/sys/class/mic/mic<X>/cmdline
+What:		/sys/class/mic/mic(x)/cmdline
 Date:		October 2013
 KernelVersion:	3.13
 Contact:	Sudeep Dutt <sudeep.dutt@intel.com>
@ -104,7 +104,7 @@ Description:
 		or modify existing ones and then write the whole kernel command
 		line back to this entry.
-What:		/sys/class/mic/mic<X>/firmware
+What:		/sys/class/mic/mic(x)/firmware
 Date:		October 2013
 KernelVersion:	3.13
 Contact:	Sudeep Dutt <sudeep.dutt@intel.com>
@ -114,7 +114,7 @@ Description:
 		card can be found. The entry can be written to change the
 		firmware image location under /lib/firmware/.
-What:		/sys/class/mic/mic<X>/ramdisk
+What:		/sys/class/mic/mic(x)/ramdisk
 Date:		October 2013
 KernelVersion:	3.13
 Contact:	Sudeep Dutt <sudeep.dutt@intel.com>
@ -124,7 +124,7 @@ Description:
 		OS boot can be found. The entry can be written to change
 		the ramdisk image location under /lib/firmware/.
-What:		/sys/class/mic/mic<X>/bootmode
+What:		/sys/class/mic/mic(x)/bootmode
 Date:		October 2013
 KernelVersion:	3.13
 Contact:	Sudeep Dutt <sudeep.dutt@intel.com>
@ -135,7 +135,7 @@ Description:
 		a) linux - Boot a Linux image.
 		b) flash - Boot an image for flash updates.
-What:		/sys/class/mic/mic<X>/log_buf_addr
+What:		/sys/class/mic/mic(x)/log_buf_addr
 Date:		October 2013
 KernelVersion:	3.13
 Contact:	Sudeep Dutt <sudeep.dutt@intel.com>
@ -149,7 +149,7 @@ Description:
 		log buffer address to be written can be found in the System.map
 		file of the card OS.
-What:		/sys/class/mic/mic<X>/log_buf_len
+What:		/sys/class/mic/mic(x)/log_buf_len
 Date:		October 2013
 KernelVersion:	3.13
 Contact:	Sudeep Dutt <sudeep.dutt@intel.com>
@ -163,7 +163,7 @@ Description:
 		buffer length address to be written can be found in the
 		System.map file of the card OS.
-What:		/sys/class/mic/mic<X>/heartbeat_enable
+What:		/sys/class/mic/mic(x)/heartbeat_enable
 Date:		March 2015
 KernelVersion:	4.4
 Contact:	Ashutosh Dixit <ashutosh.dixit@intel.com>
--- a/Documentation/ABI/testing/sysfs-class-mux
+++ b/Documentation/ABI/testing/sysfs-class-mux
@ -7,7 +7,7 @@ Description:
 		Framework and provides a sysfs interface for using MUX
 		controllers.
-What:		/sys/class/mux/muxchip<N>/
+What:		/sys/class/mux/muxchipN/
 Date:		April 2017
 KernelVersion:	4.13
 Contact:	Peter Rosin <peda@axentia.se>
--- a/Documentation/ABI/testing/sysfs-class-power
+++ b/Documentation/ABI/testing/sysfs-class-power
@ -364,10 +364,7 @@ Date:		April 2019
 Contact:	linux-pm@vger.kernel.org
 Description:
 		Represents a battery percentage level, above which charging will
-		stop. Not all hardware is capable of setting this to an arbitrary
+		stop.
 		percentage. Drivers will round written values to the nearest
 		supported value. Reading back the value will show the actual
 		threshold set by the driver.
 		Access: Read, Write
@ -383,17 +380,13 @@ Description:
 		algorithm to adjust the charge rate dynamically, without
 		any user configuration required. "Custom" means that the charger
 		uses the charge_control_* properties as configuration for some
-		different algorithm. "Long Life" means the charger reduces its
+		different algorithm.
 		charging rate in order to prolong the battery health. "Bypass"
 		means the charger bypasses the charging path around the
 		integrated converter allowing for a "smart" wall adaptor to
 		perform the power conversion externally.
 		Access: Read, Write
 		Valid values:
 			      "Unknown", "N/A", "Trickle", "Fast", "Standard",
-			      "Adaptive", "Custom", "Long Life", "Bypass"
+			      "Adaptive", "Custom"
 What:		/sys/class/power_supply/<supply_name>/charge_term_current
 Date:		July 2014
@ -420,7 +413,7 @@ Description:
 			      "Over voltage", "Unspecified failure", "Cold",
 			      "Watchdog timer expire", "Safety timer expire",
 			      "Over current", "Calibration required", "Warm",
-			      "Cool", "Hot", "No battery"
+			      "Cool", "Hot"
 What:		/sys/class/power_supply/<supply_name>/precharge_current
 Date:		June 2017
@ -462,21 +455,6 @@ Description:
 			      "Unknown", "Charging", "Discharging",
 			      "Not charging", "Full"
 What:		/sys/class/power_supply/<supply_name>/charge_behaviour
 Date:		November 2021
 Contact:	linux-pm@vger.kernel.org
 Description:
 		Represents the charging behaviour.
 		Access: Read, Write
 		Valid values:
 			================ ====================================
 			auto:            Charge normally, respect thresholds
 			inhibit-charge:  Do not charge while AC is attached
 			force-discharge: Force discharge while AC is attached
 			================ ====================================
 What:		/sys/class/power_supply/<supply_name>/technology
 Date:		May 2007
 Contact:	linux-pm@vger.kernel.org
@ -502,19 +480,6 @@ Description:
 		Valid values: Represented in microvolts
 What:		/sys/class/power_supply/<supply_name>/cycle_count
 Date:		January 2010
 Contact:	linux-pm@vger.kernel.org
 Description:
 		Reports the number of full charge + discharge cycles the
 		battery has undergone.
 		Access: Read
 		Valid values:
 			Integer > 0: representing full cycles
 			Integer = 0: cycle_count info is not available
 **USB Properties**
 What:		/sys/class/power_supply/<supply_name>/input_current_limit
--- a/Documentation/ABI/testing/sysfs-class-pwm
+++ b/Documentation/ABI/testing/sysfs-class-pwm
@ -7,7 +7,7 @@ Description:
 		Framework and provides a sysfs interface for using PWM
 		channels.
-What:		/sys/class/pwm/pwmchip<N>/
+What:		/sys/class/pwm/pwmchipN/
 Date:		May 2013
 KernelVersion:	3.11
 Contact:	H Hartley Sweeten <hsweeten@visionengravers.com>
@ -16,14 +16,14 @@ Description:
 		probed PWM controller/chip where N is the base of the
 		PWM chip.
-What:		/sys/class/pwm/pwmchip<N>/npwm
+What:		/sys/class/pwm/pwmchipN/npwm
 Date:		May 2013
 KernelVersion:	3.11
 Contact:	H Hartley Sweeten <hsweeten@visionengravers.com>
 Description:
 		The number of PWM channels supported by the PWM chip.
-What:		/sys/class/pwm/pwmchip<N>/export
+What:		/sys/class/pwm/pwmchipN/export
 Date:		May 2013
 KernelVersion:	3.11
 Contact:	H Hartley Sweeten <hsweeten@visionengravers.com>
@ -31,14 +31,14 @@ Description:
 		Exports a PWM channel from the PWM chip for sysfs control.
 		Value is between 0 and /sys/class/pwm/pwmchipN/npwm - 1.
-What:		/sys/class/pwm/pwmchip<N>/unexport
+What:		/sys/class/pwm/pwmchipN/unexport
 Date:		May 2013
 KernelVersion:	3.11
 Contact:	H Hartley Sweeten <hsweeten@visionengravers.com>
 Description:
 		Unexports a PWM channel.
-What:		/sys/class/pwm/pwmchip<N>/pwmX
+What:		/sys/class/pwm/pwmchipN/pwmX
 Date:		May 2013
 KernelVersion:	3.11
 Contact:	H Hartley Sweeten <hsweeten@visionengravers.com>
@ -47,21 +47,21 @@ Description:
 		each exported PWM channel where X is the exported PWM
 		channel number.
-What:		/sys/class/pwm/pwmchip<N>/pwmX/period
+What:		/sys/class/pwm/pwmchipN/pwmX/period
 Date:		May 2013
 KernelVersion:	3.11
 Contact:	H Hartley Sweeten <hsweeten@visionengravers.com>
 Description:
 		Sets the PWM signal period in nanoseconds.
-What:		/sys/class/pwm/pwmchip<N>/pwmX/duty_cycle
+What:		/sys/class/pwm/pwmchipN/pwmX/duty_cycle
 Date:		May 2013
 KernelVersion:	3.11
 Contact:	H Hartley Sweeten <hsweeten@visionengravers.com>
 Description:
 		Sets the PWM signal duty cycle in nanoseconds.
-What:		/sys/class/pwm/pwmchip<N>/pwmX/polarity
+What:		/sys/class/pwm/pwmchipN/pwmX/polarity
 Date:		May 2013
 KernelVersion:	3.11
 Contact:	H Hartley Sweeten <hsweeten@visionengravers.com>
@ -69,7 +69,7 @@ Description:
 		Sets the output polarity of the PWM signal to "normal" or
 		"inversed".
-What:		/sys/class/pwm/pwmchip<N>/pwmX/enable
+What:		/sys/class/pwm/pwmchipN/pwmX/enable
 Date:		May 2013
 KernelVersion:	3.11
 Contact:	H Hartley Sweeten <hsweeten@visionengravers.com>
@ -78,10 +78,10 @@ Description:
 		0 is disabled
 		1 is enabled
-What:		/sys/class/pwm/pwmchip<N>/pwmX/capture
+What:		/sys/class/pwm/pwmchipN/pwmX/capture
 Date:		June 2016
 KernelVersion:	4.8
-Contact:	Lee Jones <lee@kernel.org>
+Contact:	Lee Jones <lee.jones@linaro.org>
 Description:
 		Capture information about a PWM signal. The output format is a
 		pair unsigned integers (period and duty cycle), separated by a
--- a/Documentation/ABI/testing/sysfs-class-rapidio
+++ b/Documentation/ABI/testing/sysfs-class-rapidio
@ -10,7 +10,7 @@ Description:
 		NOTE: An mport ID is not a RapidIO destination ID assigned to a
 		given local mport device.
-What:		/sys/class/rapidio_port/rapidio<N>/sys_size
+What:		/sys/class/rapidio_port/rapidioN/sys_size
 Date:		Apr, 2014
 KernelVersion:	v3.15
 Contact:	Matt Porter <mporter@kernel.crashing.org>,
@ -22,7 +22,7 @@ Description:
 		1 = large (16-bit destination ID, max. 65536 devices).
-What:		/sys/class/rapidio_port/rapidio<N>/port_destid
+What:		/sys/class/rapidio_port/rapidioN/port_destid
 Date:		Apr, 2014
 KernelVersion:	v3.15
 Contact:	Matt Porter <mporter@kernel.crashing.org>,
--- a/Documentation/ABI/testing/sysfs-class-rc
+++ b/Documentation/ABI/testing/sysfs-class-rc
@ -7,7 +7,7 @@ Description:
 		core and provides a sysfs interface for configuring infrared
 		remote controller receivers.
-What:		/sys/class/rc/rc<N>/
+What:		/sys/class/rc/rcN/
 Date:		Apr 2010
 KernelVersion:	2.6.35
 Contact:	Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
@ -15,7 +15,7 @@ Description:
 		A /sys/class/rc/rcN directory is created for each remote
 		control receiver device where N is the number of the receiver.
-What:		/sys/class/rc/rc<N>/protocols
+What:		/sys/class/rc/rcN/protocols
 Date:		Jun 2010
 KernelVersion:	2.6.36
 Contact:	Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
@ -40,7 +40,7 @@ Description:
 		Write fails with EINVAL if an invalid protocol combination or
 		unknown protocol name is used.
-What:		/sys/class/rc/rc<N>/filter
+What:		/sys/class/rc/rcN/filter
 Date:		Jan 2014
 KernelVersion:	3.15
 Contact:	Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
@ -55,7 +55,7 @@ Description:
 		This value may be reset to 0 if the current protocol is altered.
-What:		/sys/class/rc/rc<N>/filter_mask
+What:		/sys/class/rc/rcN/filter_mask
 Date:		Jan 2014
 KernelVersion:	3.15
 Contact:	Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
@ -72,7 +72,7 @@ Description:
 		This value may be reset to 0 if the current protocol is altered.
-What:		/sys/class/rc/rc<N>/wakeup_protocols
+What:		/sys/class/rc/rcN/wakeup_protocols
 Date:		Feb 2017
 KernelVersion:	4.11
 Contact:	Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
@ -98,7 +98,7 @@ Description:
 		unknown protocol name is used, or if wakeup is not supported by
 		the hardware.
-What:		/sys/class/rc/rc<N>/wakeup_filter
+What:		/sys/class/rc/rcN/wakeup_filter
 Date:		Jan 2014
 KernelVersion:	3.15
 Contact:	Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
@ -117,7 +117,7 @@ Description:
 		This value may be reset to 0 if the wakeup protocol is altered.
-What:		/sys/class/rc/rc<N>/wakeup_filter_mask
+What:		/sys/class/rc/rcN/wakeup_filter_mask
 Date:		Jan 2014
 KernelVersion:	3.15
 Contact:	Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
--- a/Documentation/ABI/testing/sysfs-class-rc-nuvoton
+++ b/Documentation/ABI/testing/sysfs-class-rc-nuvoton
@ -1,4 +1,4 @@
-What:		/sys/class/rc/rc<N>/wakeup_data
+What:		/sys/class/rc/rcN/wakeup_data
 Date:		Mar 2016
 KernelVersion:	4.6
 Contact:	Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
--- a/Documentation/ABI/testing/sysfs-class-regulator
+++ b/Documentation/ABI/testing/sysfs-class-regulator
@ -370,84 +370,3 @@ Description:
 		'unknown' means software cannot determine the state, or
 		the reported state is invalid.
 What:		/sys/class/regulator/.../under_voltage
 Date:		April 2022
 KernelVersion:	5.18
 Contact:	Zev Weiss <zev@bewilderbeest.net>
 Description:
 		Some regulator directories will contain a field called
 		under_voltage.  This indicates if the device reports an
 		under-voltage fault (1) or not (0).
 What:		/sys/class/regulator/.../over_current
 Date:		April 2022
 KernelVersion:	5.18
 Contact:	Zev Weiss <zev@bewilderbeest.net>
 Description:
 		Some regulator directories will contain a field called
 		over_current.  This indicates if the device reports an
 		over-current fault (1) or not (0).
 What:		/sys/class/regulator/.../regulation_out
 Date:		April 2022
 KernelVersion:	5.18
 Contact:	Zev Weiss <zev@bewilderbeest.net>
 Description:
 		Some regulator directories will contain a field called
 		regulation_out.  This indicates if the device reports an
 		out-of-regulation fault (1) or not (0).
 What:		/sys/class/regulator/.../fail
 Date:		April 2022
 KernelVersion:	5.18
 Contact:	Zev Weiss <zev@bewilderbeest.net>
 Description:
 		Some regulator directories will contain a field called
 		fail.  This indicates if the device reports an output failure
 		(1) or not (0).
 What:		/sys/class/regulator/.../over_temp
 Date:		April 2022
 KernelVersion:	5.18
 Contact:	Zev Weiss <zev@bewilderbeest.net>
 Description:
 		Some regulator directories will contain a field called
 		over_temp.  This indicates if the device reports an
 		over-temperature fault (1) or not (0).
 What:		/sys/class/regulator/.../under_voltage_warn
 Date:		April 2022
 KernelVersion:	5.18
 Contact:	Zev Weiss <zev@bewilderbeest.net>
 Description:
 		Some regulator directories will contain a field called
 		under_voltage_warn.  This indicates if the device reports an
 		under-voltage warning (1) or not (0).
 What:		/sys/class/regulator/.../over_current_warn
 Date:		April 2022
 KernelVersion:	5.18
 Contact:	Zev Weiss <zev@bewilderbeest.net>
 Description:
 		Some regulator directories will contain a field called
 		over_current_warn.  This indicates if the device reports an
 		over-current warning (1) or not (0).
 What:		/sys/class/regulator/.../over_voltage_warn
 Date:		April 2022
 KernelVersion:	5.18
 Contact:	Zev Weiss <zev@bewilderbeest.net>
 Description:
 		Some regulator directories will contain a field called
 		over_voltage_warn.  This indicates if the device reports an
 		over-voltage warning (1) or not (0).
 What:		/sys/class/regulator/.../over_temp_warn
 Date:		April 2022
 KernelVersion:	5.18
 Contact:	Zev Weiss <zev@bewilderbeest.net>
 Description:
 		Some regulator directories will contain a field called
 		over_temp_warn.  This indicates if the device reports an
 		over-temperature warning (1) or not (0).
--- a/Documentation/ABI/testing/sysfs-class-rtrs-client
+++ b/Documentation/ABI/testing/sysfs-class-rtrs-client
@ -78,7 +78,7 @@ What:		/sys/class/rtrs-client/<session-name>/paths/<src@dst>/hca_name
 Date:		Feb 2020
 KernelVersion:	5.7
 Contact:	Jack Wang <jinpu.wang@cloud.ionos.com> Danil Kipnis <danil.kipnis@cloud.ionos.com>
-Description:	RO, Contains the name of HCA the connection established on.
+Description:	RO, Contains the the name of HCA the connection established on.
 What:		/sys/class/rtrs-client/<session-name>/paths/<src@dst>/hca_port
 Date:		Feb 2020
--- a/Documentation/ABI/testing/sysfs-class-rtrs-server
+++ b/Documentation/ABI/testing/sysfs-class-rtrs-server
@ -24,7 +24,7 @@ What:		/sys/class/rtrs-server/<session-name>/paths/<src@dst>/hca_name
 Date:		Feb 2020
 KernelVersion:	5.7
 Contact:	Jack Wang <jinpu.wang@cloud.ionos.com> Danil Kipnis <danil.kipnis@cloud.ionos.com>
-Description:	RO, Contains the name of HCA the connection established on.
+Description:	RO, Contains the the name of HCA the connection established on.
 What:		/sys/class/rtrs-server/<session-name>/paths/<src@dst>/hca_port
 Date:		Feb 2020
--- a/Show more
+++ b/Show more