Skip to content

cloud-kernel
cloud-kernel

openanolis / cloud-kernel
接近 2 年 前同步成功

通知 170
Star 36
Fork 7
cloud-kernel
cloud-kernel
提交 30596ec3 编写于 作者: Z Zhenyu Wang
浏览文件
操作

Back merge 'drm-intel-fixes' into gvt-fixes 

Need for 4.17-rc1
Signed-off-by: NZhenyu Wang <zhenyuw@linux.intel.com>
上级 d54e7934 60cc43fc
展开全部 隐藏空白更改
内联 并排
Showing with 35727 addition and 27832 deletion

要显示的变更太多。

To preserve performance only 1000 of 1000+ files are displayed.
文本差异 电子邮件补丁
.clang-format 0 → 100644
浏览文件 @ 30596ec3
# SPDX-License-Identifier: GPL-2.0
#
# clang-format configuration file. Intended for clang-format >= 4.
#
# For more information, see:
#
# Documentation/process/clang-format.rst
# https://clang.llvm.org/docs/ClangFormat.html
# https://clang.llvm.org/docs/ClangFormatStyleOptions.html
#
---
AccessModifierOffset: -4
AlignAfterOpenBracket: Align
AlignConsecutiveAssignments: false
AlignConsecutiveDeclarations: false
#AlignEscapedNewlines: Left # Unknown to clang-format-4.0
AlignOperands: true
AlignTrailingComments: false
AllowAllParametersOfDeclarationOnNextLine: false
AllowShortBlocksOnASingleLine: false
AllowShortCaseLabelsOnASingleLine: false
AllowShortFunctionsOnASingleLine: None
AllowShortIfStatementsOnASingleLine: false
AllowShortLoopsOnASingleLine: false
AlwaysBreakAfterDefinitionReturnType: None
AlwaysBreakAfterReturnType: None
AlwaysBreakBeforeMultilineStrings: false
AlwaysBreakTemplateDeclarations: false
BinPackArguments: true
BinPackParameters: true
BraceWrapping:
AfterClass: false
AfterControlStatement: false
AfterEnum: false
AfterFunction: true
AfterNamespace: true
AfterObjCDeclaration: false
AfterStruct: false
AfterUnion: false
#AfterExternBlock: false # Unknown to clang-format-5.0
BeforeCatch: false
BeforeElse: false
IndentBraces: false
#SplitEmptyFunction: true # Unknown to clang-format-4.0
#SplitEmptyRecord: true # Unknown to clang-format-4.0
#SplitEmptyNamespace: true # Unknown to clang-format-4.0
BreakBeforeBinaryOperators: None
BreakBeforeBraces: Custom
#BreakBeforeInheritanceComma: false # Unknown to clang-format-4.0
BreakBeforeTernaryOperators: false
BreakConstructorInitializersBeforeComma: false
#BreakConstructorInitializers: BeforeComma # Unknown to clang-format-4.0
BreakAfterJavaFieldAnnotations: false
BreakStringLiterals: false
ColumnLimit: 80
CommentPragmas: '^ IWYU pragma:'
#CompactNamespaces: false # Unknown to clang-format-4.0
ConstructorInitializerAllOnOneLineOrOnePerLine: false
ConstructorInitializerIndentWidth: 8
ContinuationIndentWidth: 8
Cpp11BracedListStyle: false
DerivePointerAlignment: false
DisableFormat: false
ExperimentalAutoDetectBinPacking: false
#FixNamespaceComments: false # Unknown to clang-format-4.0
# Taken from:
# git grep -h '^#define [^[:space:]]*for_each[^[:space:]]*(' include/ \
# | sed "s,^#define \([^[:space:]]*for_each[^[:space:]]*\)(.*$, - '\1'," \
# | sort | uniq
ForEachMacros:
- 'apei_estatus_for_each_section'
- 'ata_for_each_dev'
- 'ata_for_each_link'
- 'ax25_for_each'
- 'ax25_uid_for_each'
- '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'
- 'blkg_for_each_descendant_post'
- 'blkg_for_each_descendant_pre'
- 'blk_queue_for_each_rl'
- 'bond_for_each_slave'
- 'bond_for_each_slave_rcu'
- 'btree_for_each_safe128'
- 'btree_for_each_safe32'
- 'btree_for_each_safe64'
- 'btree_for_each_safel'
- 'card_for_each_dev'
- 'cgroup_taskset_for_each'
- 'cgroup_taskset_for_each_leader'
- 'cpufreq_for_each_entry'
- 'cpufreq_for_each_entry_idx'
- 'cpufreq_for_each_valid_entry'
- 'cpufreq_for_each_valid_entry_idx'
- 'css_for_each_child'
- 'css_for_each_descendant_post'
- 'css_for_each_descendant_pre'
- 'device_for_each_child_node'
- 'drm_atomic_crtc_for_each_plane'
- 'drm_atomic_crtc_state_for_each_plane'
- 'drm_atomic_crtc_state_for_each_plane_state'
- 'drm_for_each_connector_iter'
- 'drm_for_each_crtc'
- 'drm_for_each_encoder'
- 'drm_for_each_encoder_mask'
- 'drm_for_each_fb'
- 'drm_for_each_legacy_plane'
- 'drm_for_each_plane'
- 'drm_for_each_plane_mask'
- 'drm_mm_for_each_hole'
- 'drm_mm_for_each_node'
- 'drm_mm_for_each_node_in_range'
- 'drm_mm_for_each_node_safe'
- 'for_each_active_drhd_unit'
- 'for_each_active_iommu'
- 'for_each_available_child_of_node'
- 'for_each_bio'
- 'for_each_board_func_rsrc'
- 'for_each_bvec'
- 'for_each_child_of_node'
- 'for_each_clear_bit'
- 'for_each_clear_bit_from'
- 'for_each_cmsghdr'
- 'for_each_compatible_node'
- 'for_each_console'
- 'for_each_cpu'
- 'for_each_cpu_and'
- 'for_each_cpu_not'
- 'for_each_cpu_wrap'
- 'for_each_dev_addr'
- 'for_each_dma_cap_mask'
- 'for_each_drhd_unit'
- 'for_each_dss_dev'
- 'for_each_efi_memory_desc'
- 'for_each_efi_memory_desc_in_map'
- 'for_each_endpoint_of_node'
- 'for_each_evictable_lru'
- 'for_each_fib6_node_rt_rcu'
- 'for_each_fib6_walker_rt'
- 'for_each_free_mem_range'
- 'for_each_free_mem_range_reverse'
- 'for_each_func_rsrc'
- 'for_each_hstate'
- 'for_each_if'
- 'for_each_iommu'
- 'for_each_ip_tunnel_rcu'
- 'for_each_irq_nr'
- 'for_each_lru'
- 'for_each_matching_node'
- 'for_each_matching_node_and_match'
- 'for_each_memblock'
- 'for_each_memblock_type'
- 'for_each_memcg_cache_index'
- 'for_each_mem_pfn_range'
- 'for_each_mem_range'
- 'for_each_mem_range_rev'
- 'for_each_migratetype_order'
- 'for_each_msi_entry'
- 'for_each_net'
- 'for_each_netdev'
- 'for_each_netdev_continue'
- 'for_each_netdev_continue_rcu'
- 'for_each_netdev_feature'
- 'for_each_netdev_in_bond_rcu'
- '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_plane_in_state'
- 'for_each_new_private_obj_in_state'
- 'for_each_node'
- 'for_each_node_by_name'
- 'for_each_node_by_type'
- 'for_each_node_mask'
- 'for_each_node_state'
- 'for_each_node_with_cpus'
- 'for_each_node_with_property'
- 'for_each_of_allnodes'
- 'for_each_of_allnodes_from'
- 'for_each_of_pci_range'
- 'for_each_old_connector_in_state'
- 'for_each_old_crtc_in_state'
- 'for_each_oldnew_connector_in_state'
- 'for_each_oldnew_crtc_in_state'
- 'for_each_oldnew_plane_in_state'
- '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_pci_bridge'
- 'for_each_pci_dev'
- 'for_each_pci_msi_entry'
- 'for_each_populated_zone'
- 'for_each_possible_cpu'
- 'for_each_present_cpu'
- 'for_each_prime_number'
- 'for_each_prime_number_from'
- 'for_each_process'
- 'for_each_process_thread'
- 'for_each_property_of_node'
- 'for_each_reserved_mem_region'
- 'for_each_resv_unavail_range'
- 'for_each_rtdcom'
- 'for_each_rtdcom_safe'
- 'for_each_set_bit'
- 'for_each_set_bit_from'
- 'for_each_sg'
- 'for_each_sg_page'
- '__for_each_thread'
- 'for_each_thread'
- 'for_each_zone'
- 'for_each_zone_zonelist'
- 'for_each_zone_zonelist_nodemask'
- 'fwnode_for_each_available_child_node'
- 'fwnode_for_each_child_node'
- 'fwnode_graph_for_each_endpoint'
- 'gadget_for_each_ep'
- 'hash_for_each'
- 'hash_for_each_possible'
- 'hash_for_each_possible_rcu'
- 'hash_for_each_possible_rcu_notrace'
- 'hash_for_each_possible_safe'
- 'hash_for_each_rcu'
- 'hash_for_each_safe'
- 'hctx_for_each_ctx'
- 'hlist_bl_for_each_entry'
- 'hlist_bl_for_each_entry_rcu'
- 'hlist_bl_for_each_entry_safe'
- 'hlist_for_each'
- 'hlist_for_each_entry'
- 'hlist_for_each_entry_continue'
- 'hlist_for_each_entry_continue_rcu'
- 'hlist_for_each_entry_continue_rcu_bh'
- 'hlist_for_each_entry_from'
- 'hlist_for_each_entry_from_rcu'
- 'hlist_for_each_entry_rcu'
- 'hlist_for_each_entry_rcu_bh'
- 'hlist_for_each_entry_rcu_notrace'
- 'hlist_for_each_entry_safe'
- '__hlist_for_each_rcu'
- 'hlist_for_each_safe'
- 'hlist_nulls_for_each_entry'
- 'hlist_nulls_for_each_entry_from'
- 'hlist_nulls_for_each_entry_rcu'
- 'hlist_nulls_for_each_entry_safe'
- '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_ul'
- 'inet_bind_bucket_for_each'
- 'inet_lhash2_for_each_icsk_rcu'
- 'iov_for_each'
- 'key_for_each'
- 'key_for_each_safe'
- 'klp_for_each_func'
- 'klp_for_each_object'
- 'kvm_for_each_memslot'
- 'kvm_for_each_vcpu'
- 'list_for_each'
- 'list_for_each_entry'
- 'list_for_each_entry_continue'
- 'list_for_each_entry_continue_rcu'
- 'list_for_each_entry_continue_reverse'
- 'list_for_each_entry_from'
- 'list_for_each_entry_from_reverse'
- 'list_for_each_entry_lockless'
- 'list_for_each_entry_rcu'
- 'list_for_each_entry_reverse'
- 'list_for_each_entry_safe'
- 'list_for_each_entry_safe_continue'
- 'list_for_each_entry_safe_from'
- 'list_for_each_entry_safe_reverse'
- 'list_for_each_prev'
- 'list_for_each_prev_safe'
- 'list_for_each_safe'
- 'llist_for_each'
- 'llist_for_each_entry'
- 'llist_for_each_entry_safe'
- 'llist_for_each_safe'
- 'media_device_for_each_entity'
- 'media_device_for_each_intf'
- 'media_device_for_each_link'
- 'media_device_for_each_pad'
- 'netdev_for_each_lower_dev'
- 'netdev_for_each_lower_private'
- 'netdev_for_each_lower_private_rcu'
- 'netdev_for_each_mc_addr'
- 'netdev_for_each_uc_addr'
- 'netdev_for_each_upper_dev_rcu'
- 'netdev_hw_addr_list_for_each'
- 'nft_rule_for_each_expr'
- 'nla_for_each_attr'
- 'nla_for_each_nested'
- 'nlmsg_for_each_attr'
- 'nlmsg_for_each_msg'
- 'nr_neigh_for_each'
- 'nr_neigh_for_each_safe'
- 'nr_node_for_each'
- 'nr_node_for_each_safe'
- 'of_for_each_phandle'
- 'of_property_for_each_string'
- 'of_property_for_each_u32'
- 'pci_bus_for_each_resource'
- 'ping_portaddr_for_each_entry'
- 'plist_for_each'
- 'plist_for_each_continue'
- 'plist_for_each_entry'
- 'plist_for_each_entry_continue'
- 'plist_for_each_entry_safe'
- 'plist_for_each_safe'
- 'pnp_for_each_card'
- 'pnp_for_each_dev'
- 'protocol_for_each_card'
- 'protocol_for_each_dev'
- 'queue_for_each_hw_ctx'
- 'radix_tree_for_each_contig'
- 'radix_tree_for_each_slot'
- 'radix_tree_for_each_tagged'
- 'rbtree_postorder_for_each_entry_safe'
- 'resource_list_for_each_entry'
- 'resource_list_for_each_entry_safe'
- 'rhl_for_each_entry_rcu'
- 'rhl_for_each_rcu'
- 'rht_for_each'
- 'rht_for_each_continue'
- 'rht_for_each_entry'
- 'rht_for_each_entry_continue'
- 'rht_for_each_entry_rcu'
- 'rht_for_each_entry_rcu_continue'
- 'rht_for_each_entry_safe'
- 'rht_for_each_rcu'
- 'rht_for_each_rcu_continue'
- '__rq_for_each_bio'
- 'rq_for_each_segment'
- 'scsi_for_each_prot_sg'
- 'scsi_for_each_sg'
- 'sctp_for_each_hentry'
- 'sctp_skb_for_each'
- 'shdma_for_each_chan'
- '__shost_for_each_device'
- 'shost_for_each_device'
- 'sk_for_each'
- 'sk_for_each_bound'
- 'sk_for_each_entry_offset_rcu'
- 'sk_for_each_from'
- 'sk_for_each_rcu'
- 'sk_for_each_safe'
- 'sk_nulls_for_each'
- 'sk_nulls_for_each_from'
- 'sk_nulls_for_each_rcu'
- 'snd_pcm_group_for_each_entry'
- 'snd_soc_dapm_widget_for_each_path'
- 'snd_soc_dapm_widget_for_each_path_safe'
- 'snd_soc_dapm_widget_for_each_sink_path'
- 'snd_soc_dapm_widget_for_each_source_path'
- 'tb_property_for_each'
- 'udp_portaddr_for_each_entry'
- 'udp_portaddr_for_each_entry_rcu'
- 'usb_hub_for_each_child'
- 'v4l2_device_for_each_subdev'
- 'v4l2_m2m_for_each_dst_buf'
- 'v4l2_m2m_for_each_dst_buf_safe'
- 'v4l2_m2m_for_each_src_buf'
- 'v4l2_m2m_for_each_src_buf_safe'
- 'zorro_for_each_dev'
#IncludeBlocks: Preserve # Unknown to clang-format-5.0
IncludeCategories:
- Regex: '.*'
Priority: 1
IncludeIsMainRegex: '(Test)?$'
IndentCaseLabels: false
#IndentPPDirectives: None # Unknown to clang-format-5.0
IndentWidth: 8
IndentWrappedFunctionNames: true
JavaScriptQuotes: Leave
JavaScriptWrapImports: true
KeepEmptyLinesAtTheStartOfBlocks: false
MacroBlockBegin: ''
MacroBlockEnd: ''
MaxEmptyLinesToKeep: 1
NamespaceIndentation: Inner
#ObjCBinPackProtocolList: Auto # Unknown to clang-format-5.0
ObjCBlockIndentWidth: 8
ObjCSpaceAfterProperty: true
ObjCSpaceBeforeProtocolList: true
# Taken from git's rules
#PenaltyBreakAssignment: 10 # Unknown to clang-format-4.0
PenaltyBreakBeforeFirstCallParameter: 30
PenaltyBreakComment: 10
PenaltyBreakFirstLessLess: 0
PenaltyBreakString: 10
PenaltyExcessCharacter: 100
PenaltyReturnTypeOnItsOwnLine: 60
PointerAlignment: Right
ReflowComments: false
SortIncludes: false
#SortUsingDeclarations: false # Unknown to clang-format-4.0
SpaceAfterCStyleCast: false
SpaceAfterTemplateKeyword: true
SpaceBeforeAssignmentOperators: true
#SpaceBeforeCtorInitializerColon: true # Unknown to clang-format-5.0
#SpaceBeforeInheritanceColon: true # Unknown to clang-format-5.0
SpaceBeforeParens: ControlStatements
#SpaceBeforeRangeBasedForLoopColon: true # Unknown to clang-format-5.0
SpaceInEmptyParentheses: false
SpacesBeforeTrailingComments: 1
SpacesInAngles: false
SpacesInContainerLiterals: false
SpacesInCStyleCastParentheses: false
SpacesInParentheses: false
SpacesInSquareBrackets: false
Standard: Cpp03
TabWidth: 8
UseTab: Always
...
.gitignore
浏览文件 @ 30596ec3
......@@ -11,6 +11,7 @@
#
.*
*.a
*.asn1.[ch]
*.bin
*.bz2
*.c.[012]*.*
......@@ -22,6 +23,7 @@
*.gz
*.i
*.ko
*.lex.c
*.ll
*.lst
*.lz4
......@@ -37,6 +39,7 @@
*.so.dbg
*.su
*.symtypes
*.tab.[ch]
*.tar
*.xz
Module.symvers
......@@ -81,12 +84,14 @@ modules.builtin
!.gitignore
!.mailmap
!.cocciconfig
!.clang-format
#
# Generated include files
#
include/config
include/generated
include/ksym
arch/*/include/generated
# stgit generated dirs
......@@ -127,7 +132,3 @@ all.config
# Kdevelop4
*.kdev4
#Automatically generated by ASN.1 compiler
net/ipv4/netfilter/nf_nat_snmp_basic-asn1.c
net/ipv4/netfilter/nf_nat_snmp_basic-asn1.h
.mailmap
浏览文件 @ 30596ec3
......@@ -18,6 +18,7 @@ Aleksey Gorelov <aleksey_gorelov@phoenix.com>
Aleksandar Markovic <aleksandar.markovic@mips.com> <aleksandar.markovic@imgtec.com>
Al Viro <viro@ftp.linux.org.uk>
Al Viro <viro@zenIV.linux.org.uk>
Andi Shyti <andi@etezian.org> <andi.shyti@samsung.com>
Andreas Herrmann <aherrman@de.ibm.com>
Andrey Ryabinin <ryabinin.a.a@gmail.com> <a.ryabinin@samsung.com>
Andrew Morton <akpm@linux-foundation.org>
......@@ -33,9 +34,9 @@ Axel Lin <axel.lin@gmail.com>
Ben Gardner <bgardner@wabtec.com>
Ben M Cahill <ben.m.cahill@intel.com>
Björn Steinbrink <B.Steinbrink@gmx.de>
Boris Brezillon <boris.brezillon@free-electrons.com>
Boris Brezillon <boris.brezillon@free-electrons.com> <b.brezillon.dev@gmail.com>
Boris Brezillon <boris.brezillon@free-electrons.com> <b.brezillon@overkiz.com>
Boris Brezillon <boris.brezillon@bootlin.com> <boris.brezillon@free-electrons.com>
Boris Brezillon <boris.brezillon@bootlin.com> <b.brezillon.dev@gmail.com>
Boris Brezillon <boris.brezillon@bootlin.com> <b.brezillon@overkiz.com>
Brian Avery <b.avery@hp.com>
Brian King <brking@us.ibm.com>
Christoph Hellwig <hch@lst.de>
......@@ -62,6 +63,7 @@ Frank Zago <fzago@systemfabricworks.com>
Greg Kroah-Hartman <greg@echidna.(none)>
Greg Kroah-Hartman <gregkh@suse.de>
Greg Kroah-Hartman <greg@kroah.com>
Gregory CLEMENT <gregory.clement@bootlin.com> <gregory.clement@free-electrons.com>
Henk Vergonet <Henk.Vergonet@gmail.com>
Henrik Kretzschmar <henne@nachtwindheim.de>
Henrik Rydberg <rydberg@bitmath.org>
......@@ -100,6 +102,8 @@ Koushik <raghavendra.koushik@neterion.com>
Krzysztof Kozlowski <krzk@kernel.org> <k.kozlowski@samsung.com>
Krzysztof Kozlowski <krzk@kernel.org> <k.kozlowski.k@gmail.com>
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Leon Romanovsky <leon@kernel.org> <leon@leon.nu>
Leon Romanovsky <leon@kernel.org> <leonro@mellanox.com>
Leonid I Ananiev <leonid.i.ananiev@intel.com>
Linas Vepstas <linas@austin.ibm.com>
Linus Lüssing <linus.luessing@c0d3.blue> <linus.luessing@web.de>
......@@ -126,6 +130,7 @@ Mayuresh Janorkar <mayur@ti.com>
Michael Buesch <m@bues.ch>
Michel Dänzer <michel@tungstengraphics.com>
Miodrag Dinic <miodrag.dinic@mips.com> <miodrag.dinic@imgtec.com>
Miquel Raynal <miquel.raynal@bootlin.com> <miquel.raynal@free-electrons.com>
Mitesh shah <mshah@teja.com>
Mohit Kumar <mohit.kumar@st.com> <mohit.kumar.dhaka@gmail.com>
Morten Welinder <terra@gnome.org>
......
COPYING
浏览文件 @ 30596ec3
The Linux Kernel is provided under:
NOTE! This copyright does *not* cover user programs that use kernel
services by normal system calls - this is merely considered normal use
of the kernel, and does *not* fall under the heading of "derived work".
Also note that the GPL below is copyrighted by the Free Software
Foundation, but the instance of code that it refers to (the Linux
kernel) is copyrighted by me and others who actually wrote it.
SPDX-License-Identifier: GPL-2.0 WITH Linux-syscall-note
Also note that the only valid version of the GPL as far as the kernel
is concerned is _this_ particular version of the license (ie v2, not
v2.2 or v3.x or whatever), unless explicitly otherwise stated.
Being under the terms of the GNU General Public License version 2 only,
according with:
Linus Torvalds
LICENSES/preferred/GPL-2.0
----------------------------------------
With an explicit syscall exception, as stated at:
GNU GENERAL PUBLIC LICENSE
Version 2, June 1991
LICENSES/exceptions/Linux-syscall-note
Copyright (C) 1989, 1991 Free Software Foundation, Inc.
51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
In addition, other licenses may also apply. Please see:
Preamble
Documentation/process/license-rules.rst
The licenses for most software are designed to take away your
freedom to share and change it. By contrast, the GNU General Public
License is intended to guarantee your freedom to share and change free
software--to make sure the software is free for all its users. This
General Public License applies to most of the Free Software
Foundation's software and to any other program whose authors commit to
using it. (Some other Free Software Foundation software is covered by
the GNU Library General Public License instead.) You can apply it to
your programs, too.
When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
this service if you wish), that you receive source code or can get it
if you want it, that you can change the software or use pieces of it
in new free programs; and that you know you can do these things.
To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if you
distribute copies of the software, or if you modify it.
For example, if you distribute copies of such a program, whether
gratis or for a fee, you must give the recipients all the rights that
you have. You must make sure that they, too, receive or can get the
source code. And you must show them these terms so they know their
rights.
We protect your rights with two steps: (1) copyright the software, and
(2) offer you this license which gives you legal permission to copy,
distribute and/or modify the software.
Also, for each author's protection and ours, we want to make certain
that everyone understands that there is no warranty for this free
software. If the software is modified by someone else and passed on, we
want its recipients to know that what they have is not the original, so
that any problems introduced by others will not reflect on the original
authors' reputations.
Finally, any free program is threatened constantly by software
patents. We wish to avoid the danger that redistributors of a free
program will individually obtain patent licenses, in effect making the
program proprietary. To prevent this, we have made it clear that any
patent must be licensed for everyone's free use or not licensed at all.
The precise terms and conditions for copying, distribution and
modification follow.
GNU GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. This License applies to any program or other work which contains
a notice placed by the copyright holder saying it may be distributed
under the terms of this General Public License. The "Program", below,
refers to any such program or work, and a "work based on the Program"
means either the Program or any derivative work under copyright law:
that is to say, a work containing the Program or a portion of it,
either verbatim or with modifications and/or translated into another
language. (Hereinafter, translation is included without limitation in
the term "modification".) Each licensee is addressed as "you".
Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope. The act of
running the Program is not restricted, and the output from the Program
is covered only if its contents constitute a work based on the
Program (independent of having been made by running the Program).
Whether that is true depends on what the Program does.
1. You may copy and distribute verbatim copies of the Program's
source code as you receive it, in any medium, provided that you
conspicuously and appropriately publish on each copy an appropriate
copyright notice and disclaimer of warranty; keep intact all the
notices that refer to this License and to the absence of any warranty;
and give any other recipients of the Program a copy of this License
along with the Program.
You may charge a fee for the physical act of transferring a copy, and
you may at your option offer warranty protection in exchange for a fee.
2. You may modify your copy or copies of the Program or any portion
of it, thus forming a work based on the Program, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:
a) You must cause the modified files to carry prominent notices
stating that you changed the files and the date of any change.
b) You must cause any work that you distribute or publish, that in
whole or in part contains or is derived from the Program or any
part thereof, to be licensed as a whole at no charge to all third
parties under the terms of this License.
c) If the modified program normally reads commands interactively
when run, you must cause it, when started running for such
interactive use in the most ordinary way, to print or display an
announcement including an appropriate copyright notice and a
notice that there is no warranty (or else, saying that you provide
a warranty) and that users may redistribute the program under
these conditions, and telling the user how to view a copy of this
License. (Exception: if the Program itself is interactive but
does not normally print such an announcement, your work based on
the Program is not required to print an announcement.)
These requirements apply to the modified work as a whole. If
identifiable sections of that work are not derived from the Program,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works. But when you
distribute the same sections as part of a whole which is a work based
on the Program, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote it.
Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Program.
In addition, mere aggregation of another work not based on the Program
with the Program (or with a work based on the Program) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.
3. You may copy and distribute the Program (or a work based on it,
under Section 2) in object code or executable form under the terms of
Sections 1 and 2 above provided that you also do one of the following:
a) Accompany it with the complete corresponding machine-readable
source code, which must be distributed under the terms of Sections
1 and 2 above on a medium customarily used for software interchange; or,
b) Accompany it with a written offer, valid for at least three
years, to give any third party, for a charge no more than your
cost of physically performing source distribution, a complete
machine-readable copy of the corresponding source code, to be
distributed under the terms of Sections 1 and 2 above on a medium
customarily used for software interchange; or,
c) Accompany it with the information you received as to the offer
to distribute corresponding source code. (This alternative is
allowed only for noncommercial distribution and only if you
received the program in object code or executable form with such
an offer, in accord with Subsection b above.)
The source code for a work means the preferred form of the work for
making modifications to it. For an executable work, complete source
code means all the source code for all modules it contains, plus any
associated interface definition files, plus the scripts used to
control compilation and installation of the executable. However, as a
special exception, the source code distributed need not include
anything that is normally distributed (in either source or binary
form) with the major components (compiler, kernel, and so on) of the
operating system on which the executable runs, unless that component
itself accompanies the executable.
If distribution of executable or object code is made by offering
access to copy from a designated place, then offering equivalent
access to copy the source code from the same place counts as
distribution of the source code, even though third parties are not
compelled to copy the source along with the object code.
4. You may not copy, modify, sublicense, or distribute the Program
except as expressly provided under this License. Any attempt
otherwise to copy, modify, sublicense or distribute the Program is
void, and will automatically terminate your rights under this License.
However, parties who have received copies, or rights, from you under
this License will not have their licenses terminated so long as such
parties remain in full compliance.
5. You are not required to accept this License, since you have not
signed it. However, nothing else grants you permission to modify or
distribute the Program or its derivative works. These actions are
prohibited by law if you do not accept this License. Therefore, by
modifying or distributing the Program (or any work based on the
Program), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Program or works based on it.
6. Each time you redistribute the Program (or any work based on the
Program), the recipient automatically receives a license from the
original licensor to copy, distribute or modify the Program subject to
these terms and conditions. You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties to
this License.
7. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Program at all. For example, if a patent
license would not permit royalty-free redistribution of the Program by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Program.
If any portion of this section is held invalid or unenforceable under
any particular circumstance, the balance of the section is intended to
apply and the section as a whole is intended to apply in other
circumstances.
It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system, which is
implemented by public license practices. Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.
This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.
8. If the distribution and/or use of the Program is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Program under this License
may add an explicit geographical distribution limitation excluding
those countries, so that distribution is permitted only in or among
countries not thus excluded. In such case, this License incorporates
the limitation as if written in the body of this License.
9. The Free Software Foundation may publish revised and/or new versions
of the General Public License from time to time. Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.
Each version is given a distinguishing version number. If the Program
specifies a version number of this License which applies to it and "any
later version", you have the option of following the terms and conditions
either of that version or of any later version published by the Free
Software Foundation. If the Program does not specify a version number of
this License, you may choose any version ever published by the Free Software
Foundation.
10. If you wish to incorporate parts of the Program into other free
programs whose distribution conditions are different, write to the author
to ask for permission. For software which is copyrighted by the Free
Software Foundation, write to the Free Software Foundation; we sometimes
make exceptions for this. Our decision will be guided by the two goals
of preserving the free status of all derivatives of our free software and
of promoting the sharing and reuse of software generally.
NO WARRANTY
11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
REPAIR OR CORRECTION.
12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.
END OF TERMS AND CONDITIONS
How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) <year> <name of author>
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
Also add information on how to contact you by electronic and paper mail.
If the program is interactive, make it output a short notice like this
when it starts in an interactive mode:
Gnomovision version 69, Copyright (C) year name of author
Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.
The hypothetical commands `show w' and `show c' should show the appropriate
parts of the General Public License. Of course, the commands you use may
be called something other than `show w' and `show c'; they could even be
mouse-clicks or menu items--whatever suits your program.
You should also get your employer (if you work as a programmer) or your
school, if any, to sign a "copyright disclaimer" for the program, if
necessary. Here is a sample; alter the names:
Yoyodyne, Inc., hereby disclaims all copyright interest in the program
`Gnomovision' (which makes passes at compilers) written by James Hacker.
<signature of Ty Coon>, 1 April 1989
Ty Coon, President of Vice
This General Public License does not permit incorporating your program into
proprietary programs. If your program is a subroutine library, you may
consider it more useful to permit linking proprietary applications with the
library. If this is what you want to do, use the GNU Library General
Public License instead of this License.
for more details.
CREDITS
浏览文件 @ 30596ec3
......@@ -1564,6 +1564,11 @@ W: http://www.carumba.com/
D: bug toaster (A1 sauce makes all the difference)
D: Random linux hacker
N: James Hogan
E: jhogan@kernel.org
D: Metag architecture maintainer
D: TZ1090 SoC maintainer
N: Tim Hockin
E: thockin@hockin.org
W: http://www.hockin.org/~thockin
......
Documentation/00-INDEX
浏览文件 @ 30596ec3
......@@ -66,8 +66,6 @@ backlight/
- directory with info on controlling backlights in flat panel displays
bcache.txt
- Block-layer cache on fast SSDs to improve slow (raid) I/O performance.
blackfin/
- directory with documentation for the Blackfin arch.
block/
- info on the Block I/O (BIO) layer.
blockdev/
......@@ -114,8 +112,6 @@ cputopology.txt
- documentation on how CPU topology info is exported via sysfs.
crc32.txt
- brief tutorial on CRC computation
cris/
- directory with info about Linux on CRIS architecture.
crypto/
- directory with info on the Crypto API.
dcdbas.txt
......@@ -172,8 +168,6 @@ fmc/
- information about the FMC bus abstraction
fpga/
- FPGA Manager Core.
frv/
- Fujitsu FR-V Linux documentation.
futex-requeue-pi.txt
- info on requeueing of tasks from a non-PI futex to a PI futex
gcc-plugins.txt
......@@ -276,8 +270,6 @@ memory-hotplug.txt
- Hotpluggable memory support, how to use and current status.
men-chameleon-bus.txt
- info on MEN chameleon bus.
metag/
- directory with info about Linux on Meta architecture.
mic/
- Intel Many Integrated Core (MIC) architecture device driver.
mips/
......@@ -286,8 +278,6 @@ misc-devices/
- directory with info about devices using the misc dev subsystem
mmc/
- directory with info about the MMC subsystem
mn10300/
- directory with info about the mn10300 architecture port
mtd/
- directory with info about memory technology devices (flash)
namespaces/
......
Documentation/ABI/stable/sysfs-bus-vmbus
浏览文件 @ 30596ec3
......@@ -132,3 +132,10 @@ KernelVersion: 4.16
Contact: Stephen Hemminger <sthemmin@microsoft.com>
Description: Monitor bit associated with channel
Users: Debugging tools and userspace drivers
What: /sys/bus/vmbus/devices/vmbus_*/channels/NN/ring
Date: January. 2018
KernelVersion: 4.16
Contact: Stephen Hemminger <sthemmin@microsoft.com>
Description: Binary file created by uio_hv_generic for ring buffer
Users: Userspace drivers
Documentation/ABI/stable/sysfs-class-infiniband 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/ABI/testing/debugfs-cec-error-inj 0 → 100644
浏览文件 @ 30596ec3
What: /sys/kernel/debug/cec/*/error-inj
Date: March 2018
Contact: Hans Verkuil <hans.verkuil@cisco.com>
Description:
The CEC Framework allows for CEC error injection commands through
debugfs. Drivers that support this will create an error-inj file
through which the error injection commands can be given.
The basic syntax is as follows:
Leading spaces/tabs are ignored. If the next character is a '#' or the
end of the line was reached, then the whole line is ignored. Otherwise
a command is expected.
It is up to the driver to decide what commands to implement. The only
exception is that the command 'clear' without any arguments must be
implemented and that it will remove all current error injection
commands.
This ensures that you can always do 'echo clear >error-inj' to clear any
error injections without having to know the details of the driver-specific
commands.
Note that the output of 'error-inj' shall be valid as input to 'error-inj'.
So this must work:
$ cat error-inj >einj.txt
$ cat einj.txt >error-inj
Other than these basic rules described above this ABI is not considered
stable and may change in the future.
Drivers that implement this functionality must document the commands as
part of the CEC documentation and must keep that documentation up to date
when changes are made.
The following CEC error injection implementations exist:
- Documentation/media/uapi/cec/cec-pin-error-inj.rst
Documentation/ABI/testing/ima_policy
浏览文件 @ 30596ec3
......@@ -26,7 +26,7 @@ Description:
[obj_user=] [obj_role=] [obj_type=]]
option: [[appraise_type=]] [permit_directio]
base: func:= [BPRM_CHECK][MMAP_CHECK][FILE_CHECK][MODULE_CHECK]
base: func:= [BPRM_CHECK][MMAP_CHECK][CREDS_CHECK][FILE_CHECK][MODULE_CHECK]
[FIRMWARE_CHECK]
[KEXEC_KERNEL_CHECK] [KEXEC_INITRAMFS_CHECK]
mask:= [[^]MAY_READ] [[^]MAY_WRITE] [[^]MAY_APPEND]
......
Documentation/ABI/testing/sysfs-ata
浏览文件 @ 30596ec3
What: /sys/class/ata_...
Date: August 2008
Contact: Gwendal Grignou<gwendal@google.com>
Description:
Provide a place in sysfs for storing the ATA topology of the system. This allows
retrieving various information about ATA objects.
Provide a place in sysfs for storing the ATA topology of the
system. This allows retrieving various information about ATA
objects.
Files under /sys/class/ata_port
-------------------------------
For each port, a directory ataX is created where X is the ata_port_id of
the port. The device parent is the ata host device.
For each port, a directory ataX is created where X is the ata_port_id of the
port. The device parent is the ata host device.
idle_irq (read)
Number of IRQ received by the port while idle [some ata HBA only].
What: /sys/class/ata_port/ataX/nr_pmp_links
What: /sys/class/ata_port/ataX/idle_irq
Date: May, 2010
KernelVersion: v2.6.37
Contact: Gwendal Grignou <gwendal@chromium.org>
Description:
nr_pmp_links: (RO) If a SATA Port Multiplier (PM) is
connected, the number of links behind it.
nr_pmp_links (read)
idle_irq: (RO) Number of IRQ received by the port while
idle [some ata HBA only].
If a SATA Port Multiplier (PM) is connected, number of link behind it.
What: /sys/class/ata_port/ataX/port_no
Date: May, 2013
KernelVersion: v3.11
Contact: Gwendal Grignou <gwendal@chromium.org>
Description:
(RO) Host local port number. While registering host controller,
port numbers are tracked based upon number of ports available on
the controller. This attribute is needed by udev for composing
persistent links in /dev/disk/by-path.
Files under /sys/class/ata_link
-------------------------------
Behind each port, there is a ata_link. If there is a SATA PM in the
topology, 15 ata_link objects are created.
If a link is behind a port, the directory name is linkX, where X is
ata_port_id of the port.
If a link is behind a PM, its name is linkX.Y where X is ata_port_id
of the parent port and Y the PM port.
Behind each port, there is a ata_link. If there is a SATA PM in the topology, 15
ata_link objects are created.
hw_sata_spd_limit
If a link is behind a port, the directory name is linkX, where X is ata_port_id
of the port. If a link is behind a PM, its name is linkX.Y where X is
ata_port_id of the parent port and Y the PM port.
Maximum speed supported by the connected SATA device.
sata_spd_limit
What: /sys/class/ata_link/linkX[.Y]/hw_sata_spd_limit
What: /sys/class/ata_link/linkX[.Y]/sata_spd_limit
What: /sys/class/ata_link/linkX[.Y]/sata_spd
Date: May, 2010
KernelVersion: v2.6.37
Contact: Gwendal Grignou <gwendal@chromium.org>
Description:
hw_sata_spd_limit: (RO) Maximum speed supported by the
connected SATA device.
Maximum speed imposed by libata.
sata_spd_limit: (RO) Maximum speed imposed by libata.
sata_spd
sata_spd: (RO) Current speed of the link
eg. 1.5, 3 Gbps etc.
Current speed of the link [1.5, 3Gps,...].
Files under /sys/class/ata_device
---------------------------------
Behind each link, up to two ata device are created.
The name of the directory is devX[.Y].Z where:
- X is ata_port_id of the port where the device is connected,
- Y the port of the PM if any, and
- Z the device id: for PATA, there is usually 2 devices [0,1],
only 1 for SATA.
class
Device class. Can be "ata" for disk, "atapi" for packet device,
"pmp" for PM, or "none" if no device was found behind the link.
dma_mode
Behind each link, up to two ata devices are created.
The name of the directory is devX[.Y].Z where:
- X is ata_port_id of the port where the device is connected,
- Y the port of the PM if any, and
- Z the device id: for PATA, there is usually 2 devices [0,1], only 1 for SATA.
What: /sys/class/ata_device/devX[.Y].Z/spdn_cnt
What: /sys/class/ata_device/devX[.Y].Z/gscr
What: /sys/class/ata_device/devX[.Y].Z/ering
What: /sys/class/ata_device/devX[.Y].Z/id
What: /sys/class/ata_device/devX[.Y].Z/pio_mode
What: /sys/class/ata_device/devX[.Y].Z/xfer_mode
What: /sys/class/ata_device/devX[.Y].Z/dma_mode
What: /sys/class/ata_device/devX[.Y].Z/class
Date: May, 2010
KernelVersion: v2.6.37
Contact: Gwendal Grignou <gwendal@chromium.org>
Description:
spdn_cnt: (RO) Number of times libata decided to lower the
speed of link due to errors.
Transfer modes supported by the device when in DMA mode.
Mostly used by PATA device.
gscr: (RO) Cached result of the dump of PM GSCR
register. Valid registers are:
pio_mode
0: SATA_PMP_GSCR_PROD_ID,
1: SATA_PMP_GSCR_REV,
2: SATA_PMP_GSCR_PORT_INFO,
32: SATA_PMP_GSCR_ERROR,
33: SATA_PMP_GSCR_ERROR_EN,
64: SATA_PMP_GSCR_FEAT,
96: SATA_PMP_GSCR_FEAT_EN,
130: SATA_PMP_GSCR_SII_GPIO
Transfer modes supported by the device when in PIO mode.
Mostly used by PATA device.
Only valid if the device is a PM.
xfer_mode
ering: (RO) Formatted output of the error ring of the
device.
Current transfer mode.
id: (RO) Cached result of IDENTIFY command, as
described in ATA8 7.16 and 7.17. Only valid if
the device is not a PM.
id
pio_mode: (RO) Transfer modes supported by the device when
in PIO mode. Mostly used by PATA device.
Cached result of IDENTIFY command, as described in ATA8 7.16 and 7.17.
Only valid if the device is not a PM.
xfer_mode: (RO) Current transfer mode
gscr
dma_mode: (RO) Transfer modes supported by the device when
in DMA mode. Mostly used by PATA device.
Cached result of the dump of PM GSCR register.
Valid registers are:
0: SATA_PMP_GSCR_PROD_ID,
1: SATA_PMP_GSCR_REV,
2: SATA_PMP_GSCR_PORT_INFO,
32: SATA_PMP_GSCR_ERROR,
33: SATA_PMP_GSCR_ERROR_EN,
64: SATA_PMP_GSCR_FEAT,
96: SATA_PMP_GSCR_FEAT_EN,
130: SATA_PMP_GSCR_SII_GPIO
Only valid if the device is a PM.
class: (RO) Device class. Can be "ata" for disk,
"atapi" for packet device, "pmp" for PM, or
"none" if no device was found behind the link.
trim
Shows the DSM TRIM mode currently used by the device. Valid
values are:
unsupported: Drive does not support DSM TRIM
unqueued: Drive supports unqueued DSM TRIM only
queued: Drive supports queued DSM TRIM
forced_unqueued: Drive's queued DSM support is known to be
buggy and only unqueued TRIM commands
are sent
What: /sys/class/ata_device/devX[.Y].Z/trim
Date: May, 2015
KernelVersion: v4.10
Contact: Gwendal Grignou <gwendal@chromium.org>
Description:
(RO) Shows the DSM TRIM mode currently used by the device. Valid
values are:
spdn_cnt
unsupported: Drive does not support DSM TRIM
Number of time libata decided to lower the speed of link due to errors.
unqueued: Drive supports unqueued DSM TRIM only
ering
queued: Drive supports queued DSM TRIM
Formatted output of the error ring of the device.
forced_unqueued: Drive's queued DSM support is known to
be buggy and only unqueued TRIM commands
are sent
Documentation/ABI/testing/sysfs-block-aoe 0 → 100644
浏览文件 @ 30596ec3
What: /sys/block/etherd*/mac
Date: Apr, 2005
KernelVersion: v2.6.12
Contact: Ed L. Cashin <ed.cashin@acm.org>
Description:
(RO) The ethernet address of the remote Ata over Ethernet (AoE)
device.
What: /sys/block/etherd*/netif
Date: Apr, 2005
KernelVersion: v2.6.12
Contact: Ed L. Cashin <ed.cashin@acm.org>
Description:
(RO) The names of the network interfaces on the localhost (comma
separated) through which we are communicating with the remote
AoE device.
What: /sys/block/etherd*/state
Date: Apr, 2005
KernelVersion: v2.6.12
Contact: Ed L. Cashin <ed.cashin@acm.org>
Description:
(RO) Device status. The state attribute is "up" when the device
is ready for I/O and "down" if detected but unusable. The
"down,closewait" state shows that the device is still open and
cannot come up again until it has been closed. The "up,kickme"
state means that the driver wants to send more commands to the
target but found out there were already the max number of
commands waiting for a response. It will retry again after being
kicked by the periodic timer handler routine.
What: /sys/block/etherd*/firmware-version
Date: Apr, 2005
KernelVersion: v2.6.12
Contact: Ed L. Cashin <ed.cashin@acm.org>
Description:
(RO) Version of the firmware in the target.
What: /sys/block/etherd*/payload
Date: Dec, 2012
KernelVersion: v3.10
Contact: Ed L. Cashin <ed.cashin@acm.org>
Description:
(RO) The amount of user data transferred (in bytes) inside each AoE
command on the network, network headers excluded.
Documentation/ABI/testing/sysfs-block-device 0 → 100644
浏览文件 @ 30596ec3
What: /sys/block/*/device/sw_activity
Date: Jun, 2008
KernelVersion: v2.6.27
Contact: linux-ide@vger.kernel.org
Description:
(RW) Used by drivers which support software controlled activity
LEDs.
It has the following valid values:
0 OFF - the LED is not activated on activity
1 BLINK_ON - the LED blinks on every 10ms when activity is
detected.
2 BLINK_OFF - the LED is on when idle, and blinks off
every 10ms when activity is detected.
Note that the user must turn sw_activity OFF it they wish to
control the activity LED via the em_message file.
What: /sys/block/*/device/unload_heads
Date: Sep, 2008
KernelVersion: v2.6.28
Contact: linux-ide@vger.kernel.org
Description:
(RW) Hard disk shock protection
Writing an integer value to this file will take the heads of the
respective drive off the platter and block all I/O operations
for the specified number of milliseconds.
- If the device does not support the unload heads feature,
access is denied with -EOPNOTSUPP.
- The maximal value accepted for a timeout is 30000
milliseconds.
- A previously set timeout can be cancelled and disk can resume
normal operation immediately by specifying a timeout of 0.
- Some hard drives only comply with an earlier version of the
ATA standard, but support the unload feature nonetheless.
There is no safe way Linux can detect these devices, so this
is not enabled by default. If it is known that your device
does support the unload feature, then you can tell the kernel
to enable it by writing -1. It can be disabled again by
writing -2.
- Values below -2 are rejected with -EINVAL
For more information, see
Documentation/laptops/disk-shock-protection.txt
What: /sys/block/*/device/ncq_prio_enable
Date: Oct, 2016
KernelVersion: v4.10
Contact: linux-ide@vger.kernel.org
Description:
(RW) Write to the file to turn on or off the SATA ncq (native
command queueing) support. By default this feature is turned
off.
Documentation/ABI/testing/sysfs-block-loop 0 → 100644
浏览文件 @ 30596ec3
What: /sys/block/loopX/loop/autoclear
Date: Aug, 2010
KernelVersion: v2.6.37
Contact: linux-block@vger.kernel.org
Description:
(RO) Shows if the device is in autoclear mode or not ( "1" or
"0"). Autoclear (if set) indicates that the loopback device will
self-distruct after last close.
What: /sys/block/loopX/loop/backing_file
Date: Aug, 2010
KernelVersion: v2.6.37
Contact: linux-block@vger.kernel.org
Description:
(RO) The path of the backing file that the loop device maps its
data blocks to.
What: /sys/block/loopX/loop/offset
Date: Aug, 2010
KernelVersion: v2.6.37
Contact: linux-block@vger.kernel.org
Description:
(RO) Start offset (in bytes).
What: /sys/block/loopX/loop/sizelimit
Date: Aug, 2010
KernelVersion: v2.6.37
Contact: linux-block@vger.kernel.org
Description:
(RO) The size (in bytes) that the block device maps, starting
from the offset.
What: /sys/block/loopX/loop/partscan
Date: Aug, 2011
KernelVersion: v3.10
Contact: linux-block@vger.kernel.org
Description:
(RO) Shows if automatic partition scanning is enabled for the
device or not ("1" or "0"). This can be requested individually
per loop device during its setup by setting LO_FLAGS_PARTSCAN in
in the ioctl request. By default, no partition tables are
scanned.
What: /sys/block/loopX/loop/dio
Date: Aug, 2015
KernelVersion: v4.10
Contact: linux-block@vger.kernel.org
Description:
(RO) Shows if direct IO is being used to access backing file or
not ("1 or "0").
Documentation/ABI/testing/sysfs-bus-acpi
浏览文件 @ 30596ec3
......@@ -56,3 +56,40 @@ Description:
Writing 1 to this attribute will trigger hot removal of
this device object. This file exists for every device
object that has _EJ0 method.
What: /sys/bus/acpi/devices/.../status
Date: Jan, 2014
Contact: Rafael J. Wysocki <rjw@rjwysocki.net>
Description:
(RO) Returns the ACPI device status: enabled, disabled or
functioning or present, if the method _STA is present.
The return value is a decimal integer representing the device's
status bitmap:
Bit [0] – Set if the device is present.
Bit [1] – Set if the device is enabled and decoding its
resources.
Bit [2] – Set if the device should be shown in the UI.
Bit [3] – Set if the device is functioning properly (cleared if
device failed its diagnostics).
Bit [4] – Set if the battery is present.
Bits [31:5] – Reserved (must be cleared)
If bit [0] is clear, then bit 1 must also be clear (a device
that is not present cannot be enabled).
Bit 0 can be clear (not present) with bit [3] set (device is
functional). This case is used to indicate a valid device for
which no device driver should be loaded.
More special cases are covered in the ACPI specification.
What: /sys/bus/acpi/devices/.../hrv
Date: Apr, 2016
Contact: Rafael J. Wysocki <rjw@rjwysocki.net>
Description:
(RO) Allows users to read the hardware version of non-PCI
hardware, if the _HRV control method is present. It is mostly
useful for non-PCI devices because lspci can list the hardware
version for PCI devices.
Documentation/ABI/testing/sysfs-bus-iio-chemical-vz89x
浏览文件 @ 30596ec3
What: /sys/bus/iio/devices/iio:deviceX/in_concentration_VOC_short_raw
Date: September 2015
KernelVersion: 4.3
Contact: Matt Ranostay <mranostay@gmail.com>
Contact: Matt Ranostay <matt.ranostay@konsulko.com>
Description:
Get the raw calibration VOC value from the sensor.
This value has little application outside of calibration.
Documentation/ABI/testing/sysfs-bus-iio-proximity-as3935
浏览文件 @ 30596ec3
What /sys/bus/iio/devices/iio:deviceX/in_proximity_input
Date: March 2014
KernelVersion: 3.15
Contact: Matt Ranostay <mranostay@gmail.com>
Contact: Matt Ranostay <matt.ranostay@konsulko.com>
Description:
Get the current distance in meters of storm (1km steps)
1000-40000 = distance in meters
......@@ -9,7 +9,7 @@ Description:
What /sys/bus/iio/devices/iio:deviceX/sensor_sensitivity
Date: March 2014
KernelVersion: 3.15
Contact: Matt Ranostay <mranostay@gmail.com>
Contact: Matt Ranostay <matt.ranostay@konsulko.com>
Description:
Show or set the gain boost of the amp, from 0-31 range.
18 = indoors (default)
......
Documentation/ABI/testing/sysfs-bus-nfit 0 → 100644
浏览文件 @ 30596ec3
For all of the nmem device attributes under nfit/*, see the 'NVDIMM Firmware
Interface Table (NFIT)' section in the ACPI specification
(http://www.uefi.org/specifications) for more details.
What: /sys/bus/nd/devices/nmemX/nfit/serial
Date: Jun, 2015
KernelVersion: v4.2
Contact: linux-nvdimm@lists.01.org
Description:
(RO) Serial number of the NVDIMM (non-volatile dual in-line
memory module), assigned by the module vendor.
What: /sys/bus/nd/devices/nmemX/nfit/handle
Date: Apr, 2015
KernelVersion: v4.2
Contact: linux-nvdimm@lists.01.org
Description:
(RO) The address (given by the _ADR object) of the device on its
parent bus of the NVDIMM device containing the NVDIMM region.
What: /sys/bus/nd/devices/nmemX/nfit/device
Date: Apr, 2015
KernelVersion: v4.1
Contact: linux-nvdimm@lists.01.org
Description:
(RO) Device id for the NVDIMM, assigned by the module vendor.
What: /sys/bus/nd/devices/nmemX/nfit/rev_id
Date: Jun, 2015
KernelVersion: v4.2
Contact: linux-nvdimm@lists.01.org
Description:
(RO) Revision of the NVDIMM, assigned by the module vendor.
What: /sys/bus/nd/devices/nmemX/nfit/phys_id
Date: Apr, 2015
KernelVersion: v4.2
Contact: linux-nvdimm@lists.01.org
Description:
(RO) Handle (i.e., instance number) for the SMBIOS (system
management BIOS) Memory Device structure describing the NVDIMM
containing the NVDIMM region.
What: /sys/bus/nd/devices/nmemX/nfit/flags
Date: Jun, 2015
KernelVersion: v4.2
Contact: linux-nvdimm@lists.01.org
Description:
(RO) The flags in the NFIT memory device sub-structure indicate
the state of the data on the nvdimm relative to its energy
source or last "flush to persistence".
The attribute is a translation of the 'NVDIMM State Flags' field
in section 5.2.25.3 'NVDIMM Region Mapping' Structure of the
ACPI specification 6.2.
The health states are "save_fail", "restore_fail", "flush_fail",
"not_armed", "smart_event", "map_fail" and "smart_notify".
What: /sys/bus/nd/devices/nmemX/nfit/format
What: /sys/bus/nd/devices/nmemX/nfit/format1
What: /sys/bus/nd/devices/nmemX/nfit/formats
Date: Apr, 2016
KernelVersion: v4.7
Contact: linux-nvdimm@lists.01.org
Description:
(RO) The interface codes indicate support for persistent memory
mapped directly into system physical address space and / or a
block aperture access mechanism to the NVDIMM media.
The 'formats' attribute displays the number of supported
interfaces.
This layout is compatible with existing libndctl binaries that
only expect one code per-dimm as they will ignore
nmemX/nfit/formats and nmemX/nfit/formatN.
What: /sys/bus/nd/devices/nmemX/nfit/vendor
Date: Apr, 2016
KernelVersion: v4.7
Contact: linux-nvdimm@lists.01.org
Description:
(RO) Vendor id of the NVDIMM.
What: /sys/bus/nd/devices/nmemX/nfit/dsm_mask
Date: May, 2016
KernelVersion: v4.7
Contact: linux-nvdimm@lists.01.org
Description:
(RO) The bitmask indicates the supported device specific control
functions relative to the NVDIMM command family supported by the
device
What: /sys/bus/nd/devices/nmemX/nfit/family
Date: Apr, 2016
KernelVersion: v4.7
Contact: linux-nvdimm@lists.01.org
Description:
(RO) Displays the NVDIMM family command sets. Values
0, 1, 2 and 3 correspond to NVDIMM_FAMILY_INTEL,
NVDIMM_FAMILY_HPE1, NVDIMM_FAMILY_HPE2 and NVDIMM_FAMILY_MSFT
respectively.
See the specifications for these command families here:
http://pmem.io/documents/NVDIMM_DSM_Interface-V1.6.pdf
https://github.com/HewlettPackard/hpe-nvm/blob/master/Documentation/
https://msdn.microsoft.com/library/windows/hardware/mt604741"
What: /sys/bus/nd/devices/nmemX/nfit/id
Date: Apr, 2016
KernelVersion: v4.7
Contact: linux-nvdimm@lists.01.org
Description:
(RO) ACPI specification 6.2 section 5.2.25.9, defines an
identifier for an NVDIMM, which refelects the id attribute.
What: /sys/bus/nd/devices/nmemX/nfit/subsystem_vendor
Date: Apr, 2016
KernelVersion: v4.7
Contact: linux-nvdimm@lists.01.org
Description:
(RO) Sub-system vendor id of the NVDIMM non-volatile memory
subsystem controller.
What: /sys/bus/nd/devices/nmemX/nfit/subsystem_rev_id
Date: Apr, 2016
KernelVersion: v4.7
Contact: linux-nvdimm@lists.01.org
Description:
(RO) Sub-system revision id of the NVDIMM non-volatile memory subsystem
controller, assigned by the non-volatile memory subsystem
controller vendor.
What: /sys/bus/nd/devices/nmemX/nfit/subsystem_device
Date: Apr, 2016
KernelVersion: v4.7
Contact: linux-nvdimm@lists.01.org
Description:
(RO) Sub-system device id for the NVDIMM non-volatile memory
subsystem controller, assigned by the non-volatile memory
subsystem controller vendor.
What: /sys/bus/nd/devices/ndbusX/nfit/revision
Date: Jun, 2015
KernelVersion: v4.2
Contact: linux-nvdimm@lists.01.org
Description:
(RO) ACPI NFIT table revision number.
What: /sys/bus/nd/devices/ndbusX/nfit/scrub
Date: Sep, 2016
KernelVersion: v4.9
Contact: linux-nvdimm@lists.01.org
Description:
(RW) This shows the number of full Address Range Scrubs (ARS)
that have been completed since driver load time. Userspace can
wait on this using select/poll etc. A '+' at the end indicates
an ARS is in progress
Writing a value of 1 triggers an ARS scan.
What: /sys/bus/nd/devices/ndbusX/nfit/hw_error_scrub
Date: Sep, 2016
KernelVersion: v4.9
Contact: linux-nvdimm@lists.01.org
Description:
(RW) Provides a way to toggle the behavior between just adding
the address (cache line) where the MCE happened to the poison
list and doing a full scrub. The former (selective insertion of
the address) is done unconditionally.
This attribute can have the following values written to it:
'0': Switch to the default mode where an exception will only
insert the address of the memory error into the poison and
badblocks lists.
'1': Enable a full scrub to happen if an exception for a memory
error is received.
What: /sys/bus/nd/devices/ndbusX/nfit/dsm_mask
Date: Jun, 2017
KernelVersion: v4.13
Contact: linux-nvdimm@lists.01.org
Description:
(RO) The bitmask indicates the supported bus specific control
functions. See the section named 'NVDIMM Root Device _DSMs' in
the ACPI specification.
What: /sys/bus/nd/devices/regionX/nfit/range_index
Date: Jun, 2015
KernelVersion: v4.2
Contact: linux-nvdimm@lists.01.org
Description:
(RO) A unique number provided by the BIOS to identify an address
range. Used by NVDIMM Region Mapping Structure to uniquely refer
to this structure. Value of 0 is reserved and not used as an
index.
What: /sys/bus/nd/devices/regionX/nfit/ecc_unit_size
Date: Aug, 2017
KernelVersion: v4.14
Contact: linux-nvdimm@lists.01.org
Description:
(RO) Size of a write request to a DIMM that will not incur a
read-modify-write cycle at the memory controller.
When the nfit driver initializes it runs an ARS (Address Range
Scrub) operation across every pmem range. Part of that process
involves determining the ARS capabilities of a given address
range. One of the capabilities that is reported is the 'Clear
Uncorrectable Error Range Length Unit Size' (see: ACPI 6.2
section 9.20.7.4 Function Index 1 - Query ARS Capabilities).
This property indicates the boundary at which the NVDIMM may
need to perform read-modify-write cycles to maintain ECC (Error
Correcting Code) blocks.
Documentation/ABI/testing/sysfs-bus-rapidio 0 → 100644
浏览文件 @ 30596ec3
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
device_name "nn:d:iiii", where:
nn - two-digit hexadecimal ID of RapidIO network where the
device resides
d - device type: 'e' - for endpoint or 's' - for switch
iiii - four-digit device destID for endpoints, or switchID for
switches
For example, below is a list of device directories that
represents a typical RapidIO network with one switch, one host,
and two agent endpoints, as it is seen by the enumerating host
(with destID = 1):
/sys/bus/rapidio/devices/00:e:0000
/sys/bus/rapidio/devices/00:e:0002
/sys/bus/rapidio/devices/00:s:0001
NOTE: An enumerating or discovering endpoint does not create a
sysfs entry for itself, this is why an endpoint with destID=1 is
not shown in the list.
Attributes Common for All RapidIO Devices
-----------------------------------------
What: /sys/bus/rapidio/devices/nn:d:iiii/did
Date: Nov, 2005
KernelVersion: v2.6.15
Contact: Matt Porter <mporter@kernel.crashing.org>,
Alexandre Bounine <alexandre.bounine@idt.com>
Description:
(RO) returns the device identifier
What: /sys/bus/rapidio/devices/nn:d:iiii/vid
Date: Nov, 2005
KernelVersion: v2.6.15
Contact: Matt Porter <mporter@kernel.crashing.org>,
Alexandre Bounine <alexandre.bounine@idt.com>
Description:
(RO) returns the device vendor identifier
What: /sys/bus/rapidio/devices/nn:d:iiii/device_rev
Date: Nov, 2005
KernelVersion: v2.6.15
Contact: Matt Porter <mporter@kernel.crashing.org>,
Alexandre Bounine <alexandre.bounine@idt.com>
Description:
(RO) returns the device revision level
What: /sys/bus/rapidio/devices/nn:d:iiii/asm_did
Date: Nov, 2005
KernelVersion: v2.6.15
Contact: Matt Porter <mporter@kernel.crashing.org>,
Alexandre Bounine <alexandre.bounine@idt.com>
Description:
(RO) returns identifier for the assembly containing the device
What: /sys/bus/rapidio/devices/nn:d:iiii/asm_rev
Date: Nov, 2005
KernelVersion: v2.6.15
Contact: Matt Porter <mporter@kernel.crashing.org>,
Alexandre Bounine <alexandre.bounine@idt.com>
Description:
(RO) returns revision level of the assembly containing the
device
What: /sys/bus/rapidio/devices/nn:d:iiii/asm_vid
Date: Nov, 2005
KernelVersion: v2.6.15
Contact: Matt Porter <mporter@kernel.crashing.org>,
Alexandre Bounine <alexandre.bounine@idt.com>
Description:
(RO) returns vendor identifier of the assembly containing the
device
What: /sys/bus/rapidio/devices/nn:d:iiii/destid
Date: Mar, 2011
KernelVersion: v2.6.3
Contact: Matt Porter <mporter@kernel.crashing.org>,
Alexandre Bounine <alexandre.bounine@idt.com>
Description:
(RO) returns device destination ID assigned by the enumeration
routine
What: /sys/bus/rapidio/devices/nn:d:iiii/lprev
Date: Mar, 2011
KernelVersion: v2.6.39
Contact: Matt Porter <mporter@kernel.crashing.org>,
Alexandre Bounine <alexandre.bounine@idt.com>
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
Date: Jul, 2013
KernelVersion: v3.11
Contact: Matt Porter <mporter@kernel.crashing.org>,
Alexandre Bounine <alexandre.bounine@idt.com>
Description:
(RO) returns the device modalias
What: /sys/bus/rapidio/devices/nn:d:iiii/config
Date: Nov, 2005
KernelVersion: v2.6.15
Contact: Matt Porter <mporter@kernel.crashing.org>,
Alexandre Bounine <alexandre.bounine@idt.com>
Description:
(RW) Binary attribute to read from and write to the device
configuration registers using the RapidIO maintenance
transactions. This attribute is similar in behaviour to the
"config" attribute of PCI devices and provides an access to the
RapidIO device registers using standard file read and write
operations.
RapidIO Switch Device Attributes
--------------------------------
RapidIO switches have additional attributes in sysfs. RapidIO subsystem supports
common and device-specific sysfs attributes for switches. Because switches are
integrated into the RapidIO subsystem, it offers a method to create
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
Date: Nov, 2005
KernelVersion: v2.6.15
Contact: Matt Porter <mporter@kernel.crashing.org>,
Alexandre Bounine <alexandre.bounine@idt.com>
Description:
(RO) reports switch routing information in "destID port" format.
This attribute reports only valid routing table entries, one
line for each entry.
What: /sys/bus/rapidio/devices/nn:s:iiii/destid
Date: Mar, 2011
KernelVersion: v2.6.3
Contact: Matt Porter <mporter@kernel.crashing.org>,
Alexandre Bounine <alexandre.bounine@idt.com>
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
Date: Mar, 2011
KernelVersion: v2.6.39
Contact: Matt Porter <mporter@kernel.crashing.org>,
Alexandre Bounine <alexandre.bounine@idt.com>
Description:
(RO) number of hops on the path to the switch
What: /sys/bus/rapidio/devices/nn:s:iiii/lnext
Date: Mar, 2011
KernelVersion: v2.6.39
Contact: Matt Porter <mporter@kernel.crashing.org>,
Alexandre Bounine <alexandre.bounine@idt.com>
Description:
(RO) returns names of devices linked to the switch except one of
a device linked to the ingress port (reported as "lprev"). This
is an array names with number of lines equal to number of ports
in switch. If a switch port has no attached device, returns
"null" instead of a device name.
Device-specific Switch Attributes
---------------------------------
IDT_GEN2-
What: /sys/bus/rapidio/devices/nn:s:iiii/errlog
Date: Oct, 2010
KernelVersion: v2.6.37
Contact: Matt Porter <mporter@kernel.crashing.org>,
Alexandre Bounine <alexandre.bounine@idt.com>
Description:
(RO) reads contents of device error log until it is empty.
RapidIO Bus Attributes
----------------------
What: /sys/bus/rapidio/scan
Date: May, 2013
KernelVersion: v3.11
Contact: Matt Porter <mporter@kernel.crashing.org>,
Alexandre Bounine <alexandre.bounine@idt.com>
Description:
(WO) Allows to trigger enumeration discovery process from user
space. To initiate an enumeration or discovery process on
specific mport device, a user needs to write mport_ID (not
RapidIO destination ID) into this file. The mport_ID is a
sequential number (0 ... RIO_MAX_MPORTS) assigned to the mport
device. For example, for a machine with a single RapidIO
controller, mport_ID for that controller always will be 0. To
initiate RapidIO enumeration/discovery on all available mports a
user must write '-1' (or RIO_MPORT_ANY) into this attribute
file.
Documentation/ABI/testing/sysfs-bus-rbd
浏览文件 @ 30596ec3
What: /sys/bus/rbd/
Date: November 2010
Contact: Yehuda Sadeh <yehuda@newdream.net>,
Sage Weil <sage@newdream.net>
What: /sys/bus/rbd/add
Date: Oct, 2010
KernelVersion: v2.6.37
Contact: Sage Weil <sage@newdream.net>
Description:
(WO) Add rbd block device.
Being used for adding and removing rbd block devices.
Usage: <mon ip addr> <options> <pool name> <rbd image name> [<snap name>]
Usage: <mon ip addr> <options> <pool name> <rbd image name> [<snap name>]
$ echo "192.168.0.1 name=admin rbd foo" > /sys/bus/rbd/add
$ echo "192.168.0.1 name=admin rbd foo" > /sys/bus/rbd/add
The snapshot name can be "-" or omitted to map the image
read/write. A <dev-id> will be assigned for any registered block
device. If snapshot is used, it will be mapped read-only.
The snapshot name can be "-" or omitted to map the image read/write. A <dev-id>
will be assigned for any registered block device. If snapshot is used, it will
be mapped read-only.
Usage: <dev-id> [force]
What: /sys/bus/rbd/remove
Date: Oct, 2010
KernelVersion: v2.6.37
Contact: Sage Weil <sage@newdream.net>
Description:
(WO) Remove rbd block device.
Usage: <dev-id> [force]
$ echo 2 > /sys/bus/rbd/remove
$ echo 2 > /sys/bus/rbd/remove
Optional "force" argument which when passed will wait for
running requests and then unmap the image. Requests sent to the
driver after initiating the removal will be failed. (August
2016, since 4.9.)
Optional "force" argument which when passed will wait for running requests and
then unmap the image. Requests sent to the driver after initiating the removal
will be failed. (August 2016, since 4.9.)
What: /sys/bus/rbd/add_single_major
Date: December 2013
KernelVersion: 3.14
Contact: Sage Weil <sage@inktank.com>
Description: Available only if rbd module is inserted with single_major
Date: Dec, 2013
KernelVersion: v3.14
Contact: Sage Weil <sage@newdream.net>
Description:
(WO) Available only if rbd module is inserted with single_major
parameter set to true.
Usage is the same as for /sys/bus/rbd/add. If present,
Usage is the same as for /sys/bus/rbd/add. If present, this
should be used instead of the latter: any attempts to use
/sys/bus/rbd/add if /sys/bus/rbd/add_single_major is
available will fail for backwards compatibility reasons.
/sys/bus/rbd/add if /sys/bus/rbd/add_single_major is available
will fail for backwards compatibility reasons.
What: /sys/bus/rbd/remove_single_major
Date: December 2013
KernelVersion: 3.14
Contact: Sage Weil <sage@inktank.com>
Description: Available only if rbd module is inserted with single_major
Date: Dec, 2013
KernelVersion: v3.14
Contact: Sage Weil <sage@newdream.net>
Description:
(WO) Available only if rbd module is inserted with single_major
parameter set to true.
Usage is the same as for /sys/bus/rbd/remove. If present,
Usage is the same as for /sys/bus/rbd/remove. If present, this
should be used instead of the latter: any attempts to use
/sys/bus/rbd/remove if /sys/bus/rbd/remove_single_major is
available will fail for backwards compatibility reasons.
Entries under /sys/bus/rbd/devices/<dev-id>/
--------------------------------------------
client_addr
The ceph unique client entity_addr_t (address + nonce).
The format is <address>:<port>/<nonce>: '1.2.3.4:1234/5678' or
'[1:2:3:4:5:6:7:8]:1234/5678'. (August 2016, since 4.9.)
client_id
The ceph unique client id that was assigned for this specific session.
cluster_fsid
The ceph cluster UUID. (August 2016, since 4.9.)
config_info
The string written into /sys/bus/rbd/add{,_single_major}. (August
2016, since 4.9.)
features
A hexadecimal encoding of the feature bits for this image.
major
The block device major number.
What: /sys/bus/rbd/supported_features
Date: Mar, 2017
KernelVersion: v4.11
Contact: Sage Weil <sage@newdream.net>
Description:
(RO) Displays the features supported by the rbd module so that
userspace can generate meaningful error messages and spell out
unsupported features that need to be disabled.
What: /sys/bus/rbd/devices/<dev-id>/size
What: /sys/bus/rbd/devices/<dev-id>/major
What: /sys/bus/rbd/devices/<dev-id>/client_id
What: /sys/bus/rbd/devices/<dev-id>/pool
What: /sys/bus/rbd/devices/<dev-id>/name
What: /sys/bus/rbd/devices/<dev-id>/refresh
What: /sys/bus/rbd/devices/<dev-id>/current_snap
Date: Oct, 2010
KernelVersion: v2.6.37
Contact: Sage Weil <sage@newdream.net>
Description:
size: (RO) The size (in bytes) of the mapped block
device.
minor
major: (RO) The block device major number.
The block device minor number. (December 2013, since 3.14.)
client_id: (RO) The ceph unique client id that was assigned
for this specific session.
name
pool: (RO) The name of the storage pool where this rbd
image resides. An rbd image name is unique
within its pool.
The name of the rbd image.
name: (RO) The name of the rbd image.
image_id
refresh: (WO) Writing to this file will reread the image
header data and set all relevant data structures
accordingly.
The unique id for the rbd image. (For rbd image format 1
this is empty.)
current_snap: (RO) The current snapshot for which the device
is mapped.
pool
The name of the storage pool where this rbd image resides.
An rbd image name is unique within its pool.
What: /sys/bus/rbd/devices/<dev-id>/pool_id
Date: Jul, 2012
KernelVersion: v3.6
Contact: Sage Weil <sage@newdream.net>
Description:
(RO) The unique identifier for the rbd image's pool. This is a
permanent attribute of the pool. A pool's id will never change.
pool_id
The unique identifier for the rbd image's pool. This is
a permanent attribute of the pool. A pool's id will never
change.
What: /sys/bus/rbd/devices/<dev-id>/image_id
What: /sys/bus/rbd/devices/<dev-id>/features
Date: Oct, 2012
KernelVersion: v3.7
Contact: Sage Weil <sage@newdream.net>
Description:
image_id: (RO) The unique id for the rbd image. (For rbd
image format 1 this is empty.)
size
features: (RO) A hexadecimal encoding of the feature bits
for this image.
The size (in bytes) of the mapped block device.
refresh
What: /sys/bus/rbd/devices/<dev-id>/parent
Date: Nov, 2012
KernelVersion: v3.8
Contact: Sage Weil <sage@newdream.net>
Description:
(RO) Information identifying the chain of parent images in a
layered rbd image. Entries are separated by empty lines.
Writing to this file will reread the image header data and set
all relevant datastructures accordingly.
current_snap
What: /sys/bus/rbd/devices/<dev-id>/minor
Date: Dec, 2013
KernelVersion: v3.14
Contact: Sage Weil <sage@newdream.net>
Description:
(RO) The block device minor number.
The current snapshot for which the device is mapped.
snap_id
What: /sys/bus/rbd/devices/<dev-id>/snap_id
What: /sys/bus/rbd/devices/<dev-id>/config_info
What: /sys/bus/rbd/devices/<dev-id>/cluster_fsid
What: /sys/bus/rbd/devices/<dev-id>/client_addr
Date: Aug, 2016
KernelVersion: v4.9
Contact: Sage Weil <sage@newdream.net>
Description:
snap_id: (RO) The current snapshot's id.
The current snapshot's id. (August 2016, since 4.9.)
config_info: (RO) The string written into
/sys/bus/rbd/add{,_single_major}.
parent
cluster_fsid: (RO) The ceph cluster UUID.
Information identifying the chain of parent images in a layered rbd
image. Entries are separated by empty lines.
client_addr: (RO) The ceph unique client
entity_addr_t (address + nonce). The format is
<address>:<port>/<nonce>: '1.2.3.4:1234/5678' or
'[1:2:3:4:5:6:7:8]:1234/5678'.
Documentation/ABI/testing/sysfs-bus-thunderbolt
浏览文件 @ 30596ec3
What: /sys/bus/thunderbolt/devices/.../domainX/boot_acl
Date: Jun 2018
KernelVersion: 4.17
Contact: thunderbolt-software@lists.01.org
Description: Holds a comma separated list of device unique_ids that
are allowed to be connected automatically during system
startup (e.g boot devices). The list always contains
maximum supported number of unique_ids where unused
entries are empty. This allows the userspace software
to determine how many entries the controller supports.
If there are multiple controllers, each controller has
its own ACL list and size may be different between the
controllers.
System BIOS may have an option "Preboot ACL" or similar
that needs to be selected before this list is taken into
consideration.
Software always updates a full list in each write.
If a device is authorized automatically during boot its
boot attribute is set to 1.
What: /sys/bus/thunderbolt/devices/.../domainX/security
Date: Sep 2017
KernelVersion: 4.13
......@@ -12,6 +35,9 @@ Description: This attribute holds current Thunderbolt security level
minimum. User needs to authorize each device.
dponly: Automatically tunnel Display port (and USB). No
PCIe tunnels are created.
usbonly: Automatically tunnel USB controller of the
connected Thunderbolt dock (and Display Port). All
PCIe links downstream of the dock are removed.
What: /sys/bus/thunderbolt/devices/.../authorized
Date: Sep 2017
......@@ -38,6 +64,13 @@ Description: This attribute is used to authorize Thunderbolt devices
the device did not contain a key at all, and
EKEYREJECTED if the challenge response did not match.
What: /sys/bus/thunderbolt/devices/.../boot
Date: Jun 2018
KernelVersion: 4.17
Contact: thunderbolt-software@lists.01.org
Description: This attribute contains 1 if Thunderbolt device was already
authorized on boot and 0 otherwise.
What: /sys/bus/thunderbolt/devices/.../key
Date: Sep 2017
KernelVersion: 4.13
......
Documentation/ABI/testing/sysfs-bus-usb
浏览文件 @ 30596ec3
......@@ -189,6 +189,16 @@ Description:
The file will read "hotplug", "wired" and "not used" if the
information is available, and "unknown" otherwise.
What: /sys/bus/usb/devices/.../(hub interface)/portX/over_current_count
Date: February 2018
Contact: Richard Leitner <richard.leitner@skidata.com>
Description:
Most hubs are able to detect over-current situations on their
ports and report them to the kernel. This attribute is to expose
the number of over-current situation occurred on a specific port
to user space. This file will contain an unsigned 32 bit value
which wraps to 0 after its maximum is reached.
What: /sys/bus/usb/devices/.../(hub interface)/portX/usb3_lpm_permit
Date: November 2015
Contact: Lu Baolu <baolu.lu@linux.intel.com>
......
Documentation/ABI/testing/sysfs-class-backlight-adp5520 0 → 100644
浏览文件 @ 30596ec3
sysfs interface for analog devices adp5520(01) backlight driver
---------------------------------------------------------------
The backlight brightness control operates at three different levels for the
adp5520 and adp5501 devices: daylight (level 1), office (level 2) and dark
(level 3). By default the brightness operates at the daylight brightness level.
What: /sys/class/backlight/<backlight>/daylight_max
What: /sys/class/backlight/<backlight>/office_max
What: /sys/class/backlight/<backlight>/dark_max
Date: Sep, 2009
KernelVersion: v2.6.32
Contact: Michael Hennerich <michael.hennerich@analog.com>
Description:
(RW) Maximum current setting for the backlight when brightness
is at one of the three levels (daylight, office or dark). This
is an input code between 0 and 127, which is transformed to a
value between 0 mA and 30 mA using linear or non-linear
algorithms.
What: /sys/class/backlight/<backlight>/daylight_dim
What: /sys/class/backlight/<backlight>/office_dim
What: /sys/class/backlight/<backlight>/dark_dim
Date: Sep, 2009
KernelVersion: v2.6.32
Contact: Michael Hennerich <michael.hennerich@analog.com>
Description:
(RW) Dim current setting for the backlight when brightness is at
one of the three levels (daylight, office or dark). This is an
input code between 0 and 127, which is transformed to a value
between 0 mA and 30 mA using linear or non-linear algorithms.
Documentation/ABI/testing/sysfs-class-backlight-adp8860 0 → 100644
浏览文件 @ 30596ec3
sysfs interface for analog devices adp8860 backlight driver
-----------------------------------------------------------
The backlight brightness control operates at three different levels for the
adp8860, adp8861 and adp8863 devices: daylight (level 1), office (level 2) and
dark (level 3). By default the brightness operates at the daylight brightness
level.
What: /sys/class/backlight/<backlight>/ambient_light_level
Date: Apr, 2010
KernelVersion: v2.6.35
Contact: Michael Hennerich <michael.hennerich@analog.com>
Description:
(RO) 13-bit conversion value for the first light sensor—high
byte (Bit 12 to Bit 8). The value is updated every 80 ms (when
the light sensor is enabled).
What: /sys/class/backlight/<backlight>/ambient_light_zone
Date: Apr, 2010
KernelVersion: v2.6.35
Contact: Michael Hennerich <michael.hennerich@analog.com>
Description:
(RW) Read or write the specific level at which the backlight
operates. Value "0" enables automatic ambient light sensing, and
values "1", "2" or "3" set the control to daylight, office or
dark respectively.
What: /sys/class/backlight/<backlight>/l1_daylight_max
What: /sys/class/backlight/<backlight>/l2_office_max
What: /sys/class/backlight/<backlight>/l3_dark_max
Date: Apr, 2010
KernelVersion: v2.6.35
Contact: Michael Hennerich <michael.hennerich@analog.com>
Description:
(RW) Maximum current setting for the backlight when brightness
is at one of the three levels (daylight, office or dark). This
is an input code between 0 and 127, which is transformed to a
value between 0 mA and 30 mA using linear or non-linear
algorithms.
What: /sys/class/backlight/<backlight>/l1_daylight_dim
What: /sys/class/backlight/<backlight>/l2_office_dim
What: /sys/class/backlight/<backlight>/l3_dark_dim
Date: Apr, 2010
KernelVersion: v2.6.35
Contact: Michael Hennerich <michael.hennerich@analog.com>
Description:
(RW) Dim current setting for the backlight when brightness is at
one of the three levels (daylight, office or dark). This is an
input code between 0 and 127, which is transformed to a value
between 0 mA and 30 mA using linear or non-linear algorithms.
Documentation/ABI/testing/sysfs-class-backlight-lm3639 0 → 100644
浏览文件 @ 30596ec3
sysfs interface for Texas Instruments lm3639 backlight + flash led driver chip
------------------------------------------------------------------------------
What: /sys/class/backlight/<backlight>/bled_mode
Date: Oct, 2012
KernelVersion: v3.10
Contact: dri-devel@lists.freedesktop.org
Description:
(WO) Write to the backlight mapping mode. The backlight current
can be mapped for either exponential (value "0") or linear
mapping modes (default).
Documentation/ABI/testing/sysfs-class-bsr 0 → 100644
浏览文件 @ 30596ec3
What: /sys/class/bsr/bsr*/bsr_size
Date: Jul, 2008
KernelVersion: 2.6.27
Contact: Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Description:
(RO) Size of the barrier-synchronization register (BSR)
register in bytes.
What: /sys/class/bsr/bsr*/bsr_length
Date: Jul, 2008
KernelVersion: 2.6.27
Contact: Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Description:
(RO) The length of memory region that can be mapped in bytes.
What: /sys/class/bsr/bsr*/bsr_stride
Date: Jul, 2008
KernelVersion: 2.6.27
Contact: Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Description:
(RO) The stride or the interval at which the allocated BSR bytes
repeat within the mapping.
Documentation/ABI/testing/sysfs-class-infiniband 已删除 100644 → 0
浏览文件 @ d54e7934
What: /sys/class/infiniband/<hca>/ports/<port-number>/gid_attrs/ndevs/<gid-index>
Date: November 29, 2015
KernelVersion: 4.4.0
Contact: linux-rdma@vger.kernel.org
Description: The net-device's name associated with the GID resides
at index <gid-index>.
What: /sys/class/infiniband/<hca>/ports/<port-number>/gid_attrs/types/<gid-index>
Date: November 29, 2015
KernelVersion: 4.4.0
Contact: linux-rdma@vger.kernel.org
Description: The RoCE type of the associated GID resides at index <gid-index>.
This could either be "IB/RoCE v1" for IB and RoCE v1 based GODs
or "RoCE v2" for RoCE v2 based GIDs.
Documentation/ABI/testing/sysfs-class-lcd-s6e63m0 0 → 100644
浏览文件 @ 30596ec3
sysfs interface for the S6E63M0 AMOLED LCD panel driver
-------------------------------------------------------
What: /sys/class/lcd/<lcd>/gamma_mode
Date: May, 2010
KernelVersion: v2.6.35
Contact: dri-devel@lists.freedesktop.org
Description:
(RW) Read or write the gamma mode. Following three modes are
supported:
0 - gamma value 2.2,
1 - gamma value 1.9 and
2 - gamma value 1.7.
What: /sys/class/lcd/<lcd>/gamma_table
Date: May, 2010
KernelVersion: v2.6.35
Contact: dri-devel@lists.freedesktop.org
Description:
(RO) Displays the size of the gamma table i.e. the number of
gamma modes available.
This is a backlight lcd driver. These interfaces are an extension to the API
documented in Documentation/ABI/testing/sysfs-class-lcd and in
Documentation/ABI/stable/sysfs-class-backlight (under
/sys/class/backlight/<backlight>/).
Documentation/ABI/testing/sysfs-class-mei
浏览文件 @ 30596ec3
......@@ -45,3 +45,12 @@ Contact: Tomas Winkler <tomas.winkler@intel.com>
Description: Display the driver HBM protocol version.
The HBM protocol version supported by the driver.
What: /sys/class/mei/meiN/tx_queue_limit
Date: Jan 2018
KernelVersion: 4.16
Contact: Tomas Winkler <tomas.winkler@intel.com>
Description: Configure tx queue limit
Set maximal number of pending writes
per opened session.
Documentation/ABI/testing/sysfs-class-pktcdvd
浏览文件 @ 30596ec3
What: /sys/class/pktcdvd/
Date: Oct. 2006
KernelVersion: 2.6.20
Contact: Thomas Maier <balagi@justmail.de>
Description:
sysfs interface
---------------
The pktcdvd module (packet writing driver) creates the following files in the
sysfs: (<devid> is in the format major:minor)
What: /sys/class/pktcdvd/add
What: /sys/class/pktcdvd/remove
What: /sys/class/pktcdvd/device_map
Date: Oct. 2006
KernelVersion: 2.6.20
Contact: Thomas Maier <balagi@justmail.de>
Description:
add: (WO) Write a block device id (major:minor) to
create a new pktcdvd device and map it to the
block device.
remove: (WO) Write the pktcdvd device id (major:minor)
to remove the pktcdvd device.
device_map: (RO) Shows the device mapping in format:
pktcdvd[0-7] <pktdevid> <blkdevid>
What: /sys/class/pktcdvd/pktcdvd[0-7]/dev
What: /sys/class/pktcdvd/pktcdvd[0-7]/uevent
Date: Oct. 2006
KernelVersion: 2.6.20
Contact: Thomas Maier <balagi@justmail.de>
Description:
dev: (RO) Device id
uevent: (WO) To send a uevent
What: /sys/class/pktcdvd/pktcdvd[0-7]/stat/packets_started
What: /sys/class/pktcdvd/pktcdvd[0-7]/stat/packets_finished
What: /sys/class/pktcdvd/pktcdvd[0-7]/stat/kb_written
What: /sys/class/pktcdvd/pktcdvd[0-7]/stat/kb_read
What: /sys/class/pktcdvd/pktcdvd[0-7]/stat/kb_read_gather
What: /sys/class/pktcdvd/pktcdvd[0-7]/stat/reset
Date: Oct. 2006
KernelVersion: 2.6.20
Contact: Thomas Maier <balagi@justmail.de>
Description:
packets_started: (RO) Number of started packets.
packets_finished: (RO) Number of finished packets.
kb_written: (RO) kBytes written.
kb_read: (RO) kBytes read.
kb_read_gather: (RO) kBytes read to fill write packets.
reset: (WO) Write any value to it to reset
pktcdvd device statistic values, like
bytes read/written.
What: /sys/class/pktcdvd/pktcdvd[0-7]/write_queue/size
What: /sys/class/pktcdvd/pktcdvd[0-7]/write_queue/congestion_off
What: /sys/class/pktcdvd/pktcdvd[0-7]/write_queue/congestion_on
Date: Oct. 2006
KernelVersion: 2.6.20
Contact: Thomas Maier <balagi@justmail.de>
Description:
size: (RO) Contains the size of the bio write queue.
congestion_off: (RW) If bio write queue size is below this mark,
accept new bio requests from the block layer.
The pktcdvd module (packet writing driver) creates
these files in the sysfs:
(<devid> is in format major:minor )
/sys/class/pktcdvd/
add (0200) Write a block device id (major:minor)
to create a new pktcdvd device and map
it to the block device.
remove (0200) Write the pktcdvd device id (major:minor)
to it to remove the pktcdvd device.
device_map (0444) Shows the device mapping in format:
pktcdvd[0-7] <pktdevid> <blkdevid>
/sys/class/pktcdvd/pktcdvd[0-7]/
dev (0444) Device id
uevent (0200) To send an uevent.
/sys/class/pktcdvd/pktcdvd[0-7]/stat/
packets_started (0444) Number of started packets.
packets_finished (0444) Number of finished packets.
kb_written (0444) kBytes written.
kb_read (0444) kBytes read.
kb_read_gather (0444) kBytes read to fill write packets.
reset (0200) Write any value to it to reset
pktcdvd device statistic values, like
bytes read/written.
/sys/class/pktcdvd/pktcdvd[0-7]/write_queue/
size (0444) Contains the size of the bio write
queue.
congestion_off (0644) If bio write queue size is below
this mark, accept new bio requests
from the block layer.
congestion_on (0644) If bio write queue size is higher
as this mark, do no longer accept
bio write requests from the block
layer and wait till the pktcdvd
device has processed enough bio's
so that bio write queue size is
below congestion off mark.
A value of <= 0 disables congestion
control.
congestion_on: (RW) If bio write queue size is higher as this
mark, do no longer accept bio write requests
from the block layer and wait till the pktcdvd
device has processed enough bio's so that bio
write queue size is below congestion off mark.
A value of <= 0 disables congestion control.
Example:
......
Documentation/ABI/testing/sysfs-class-rapidio 0 → 100644
浏览文件 @ 30596ec3
What: /sys/class/rapidio_port
Description:
On-chip RapidIO controllers and PCIe-to-RapidIO bridges
(referenced as "Master Port" or "mport") are presented in sysfs
as the special class of devices: "rapidio_port".
The /sys/class/rapidio_port subdirectory contains individual
subdirectories named as "rapidioN" where N = mport ID registered
with RapidIO subsystem.
NOTE: An mport ID is not a RapidIO destination ID assigned to a
given local mport device.
What: /sys/class/rapidio_port/rapidioN/sys_size
Date: Apr, 2014
KernelVersion: v3.15
Contact: Matt Porter <mporter@kernel.crashing.org>,
Alexandre Bounine <alexandre.bounine@idt.com>
Description:
(RO) reports RapidIO common transport system size:
0 = small (8-bit destination ID, max. 256 devices),
1 = large (16-bit destination ID, max. 65536 devices).
What: /sys/class/rapidio_port/rapidioN/port_destid
Date: Apr, 2014
KernelVersion: v3.15
Contact: Matt Porter <mporter@kernel.crashing.org>,
Alexandre Bounine <alexandre.bounine@idt.com>
Description:
(RO) reports RapidIO destination ID assigned to the given
RapidIO mport device. If value 0xFFFFFFFF is returned this means
that no valid destination ID have been assigned to the mport
(yet). Normally, before enumeration/discovery have been executed
only fabric enumerating mports have a valid destination ID
assigned to them using "hdid=..." rapidio module parameter.
After enumeration or discovery was performed for a given mport device,
the corresponding subdirectory will also contain subdirectories for each
child RapidIO device connected to the mport.
The example below shows mport device subdirectory with several child RapidIO
devices attached to it.
[rio@rapidio ~]$ ls /sys/class/rapidio_port/rapidio0/ -l
total 0
drwxr-xr-x 3 root root 0 Feb 11 15:10 00:e:0001
drwxr-xr-x 3 root root 0 Feb 11 15:10 00:e:0004
drwxr-xr-x 3 root root 0 Feb 11 15:10 00:e:0007
drwxr-xr-x 3 root root 0 Feb 11 15:10 00:s:0002
drwxr-xr-x 3 root root 0 Feb 11 15:10 00:s:0003
drwxr-xr-x 3 root root 0 Feb 11 15:10 00:s:0005
lrwxrwxrwx 1 root root 0 Feb 11 15:11 device -> ../../../0000:01:00.0
-r--r--r-- 1 root root 4096 Feb 11 15:11 port_destid
drwxr-xr-x 2 root root 0 Feb 11 15:11 power
lrwxrwxrwx 1 root root 0 Feb 11 15:04 subsystem -> ../../../../../../class/rapidio_port
-r--r--r-- 1 root root 4096 Feb 11 15:11 sys_size
-rw-r--r-- 1 root root 4096 Feb 11 15:04 uevent
Documentation/ABI/testing/sysfs-class-rtc
浏览文件 @ 30596ec3
......@@ -43,6 +43,14 @@ Contact: linux-rtc@vger.kernel.org
Description:
(RO) The name of the RTC corresponding to this sysfs directory
What: /sys/class/rtc/rtcX/range
Date: January 2018
KernelVersion: 4.16
Contact: linux-rtc@vger.kernel.org
Description:
Valid time range for the RTC, as seconds from epoch, formatted
as [min, max]
What: /sys/class/rtc/rtcX/since_epoch
Date: March 2006
KernelVersion: 2.6.17
......@@ -57,14 +65,6 @@ Contact: linux-rtc@vger.kernel.org
Description:
(RO) RTC-provided time in 24-hour notation (hh:mm:ss)
What: /sys/class/rtc/rtcX/*/nvmem
Date: February 2016
KernelVersion: 4.6
Contact: linux-rtc@vger.kernel.org
Description:
(RW) The non volatile storage exported as a raw file, as
described in Documentation/nvmem/nvmem.txt
What: /sys/class/rtc/rtcX/offset
Date: February 2016
KernelVersion: 4.6
......
Documentation/ABI/testing/sysfs-class-scsi_host
浏览文件 @ 30596ec3
......@@ -27,3 +27,92 @@ Description: This file contains the current status of the "SSD Smart Path"
the direct i/o path to physical devices. This setting is
controller wide, affecting all configured logical drives on the
controller. This file is readable and writable.
What: /sys/class/scsi_host/hostX/link_power_management_policy
Date: Oct, 2007
KernelVersion: v2.6.24
Contact: linux-ide@vger.kernel.org
Description:
(RW) This parameter allows the user to read and set the link
(interface) power management.
There are four possible options:
min_power: Tell the controller to try to make the link use the
least possible power when possible. This may sacrifice some
performance due to increased latency when coming out of lower
power states.
max_performance: Generally, this means no power management.
Tell the controller to have performance be a priority over power
management.
medium_power: Tell the controller to enter a lower power state
when possible, but do not enter the lowest power state, thus
improving latency over min_power setting.
med_power_with_dipm: Identical to the existing medium_power
setting except that it enables dipm (device initiated power
management) on top, which makes it match the Windows IRST (Intel
Rapid Storage Technology) driver settings. This setting is also
close to min_power, except that:
a) It does not use host-initiated slumber mode, but it does
allow device-initiated slumber
b) It does not enable low power device sleep mode (DevSlp).
What: /sys/class/scsi_host/hostX/em_message
What: /sys/class/scsi_host/hostX/em_message_type
Date: Jun, 2008
KernelVersion: v2.6.27
Contact: linux-ide@vger.kernel.org
Description:
em_message: (RW) Enclosure management support. For the LED
protocol, writes and reads correspond to the LED message format
as defined in the AHCI spec.
The user must turn sw_activity (under /sys/block/*/device/) OFF
it they wish to control the activity LED via the em_message
file.
em_message_type: (RO) Displays the current enclosure management
protocol that is being used by the driver (for eg. LED, SAF-TE,
SES-2, SGPIO etc).
What: /sys/class/scsi_host/hostX/ahci_port_cmd
What: /sys/class/scsi_host/hostX/ahci_host_caps
What: /sys/class/scsi_host/hostX/ahci_host_cap2
Date: Mar, 2010
KernelVersion: v2.6.35
Contact: linux-ide@vger.kernel.org
Description:
[to be documented]
What: /sys/class/scsi_host/hostX/ahci_host_version
Date: Mar, 2010
KernelVersion: v2.6.35
Contact: linux-ide@vger.kernel.org
Description:
(RO) Display the version of the AHCI spec implemented by the
host.
What: /sys/class/scsi_host/hostX/em_buffer
Date: Apr, 2010
KernelVersion: v2.6.35
Contact: linux-ide@vger.kernel.org
Description:
(RW) Allows access to AHCI EM (enclosure management) buffer
directly if the host supports EM.
For eg. the AHCI driver supports SGPIO EM messages but the
SATA/AHCI specs do not define the SGPIO message format of the EM
buffer. Different hardware(HW) vendors may have different
definitions. With the em_buffer attribute, this issue can be
solved by allowing HW vendors to provide userland drivers and
tools for their SGPIO initiators.
What: /sys/class/scsi_host/hostX/em_message_supported
Date: Oct, 2009
KernelVersion: v2.6.39
Contact: linux-ide@vger.kernel.org
Description:
(RO) Displays supported enclosure management message types.
Documentation/ABI/testing/sysfs-class-usb_role 0 → 100644
浏览文件 @ 30596ec3
What: /sys/class/usb_role/
Date: Jan 2018
Contact: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Description:
Place in sysfs for USB Role Switches. USB Role Switch is a
device that can select the data role (host or device) for USB
port.
What: /sys/class/usb_role/<switch>/role
Date: Jan 2018
Contact: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Description:
The current role of the switch. This attribute can be used for
requesting role swapping with non-USB Type-C ports. With USB
Type-C ports, the ABI defined for USB Type-C connector class
must be used.
Valid values:
- none
- host
- device
Documentation/ABI/testing/sysfs-devices-platform-ACPI-TAD 0 → 100644
浏览文件 @ 30596ec3
ACPI Time and Alarm (TAD) device attributes.
What: /sys/bus/platform/devices/ACPI000E:00/caps
Date: March 2018
Contact: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Description:
(RO) Hexadecimal bitmask of the TAD attributes are reported by
the platform firmware (see ACPI 6.2, section 9.18.2):
BIT(0): AC wakeup implemented if set
BIT(1): DC wakeup implemented if set
BIT(2): Get/set real time features implemented if set
BIT(3): Real time accuracy in milliseconds if set
BIT(4): Correct status reported for wakeups from S4/S5 if set
BIT(5): The AC timer wakes up from S4 if set
BIT(6): The AC timer wakes up from S5 if set
BIT(7): The DC timer wakes up from S4 if set
BIT(8): The DC timer wakes up from S5 if set
The other bits are reserved.
What: /sys/bus/platform/devices/ACPI000E:00/ac_alarm
Date: March 2018
Contact: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Description:
(RW) The AC alarm timer value.
Reads return the current AC alarm timer value in seconds or
"disabled", if the AC alarm is not set to wake up the system.
Write a new AC alarm timer value in seconds or "disabled" to it
to set the AC alarm timer or to disable it, respectively.
If the AC alarm timer is set through this attribute and it
expires, it will immediately wake up the system from the S3
sleep state (and from S4/S5 too if supported) until its status
is explicitly cleared via the ac_status attribute.
What: /sys/bus/platform/devices/ACPI000E:00/ac_policy
Date: March 2018
Contact: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Description:
(RW) The AC alarm expired timer wake policy (see ACPI 6.2,
Section 9.18 for details).
Reads return the current expired timer wake delay for the AC
alarm timer or "never", if the policy is to discard AC timer
wakeups if the system is on DC power.
Write a new expired timer wake delay for the AC alarm timer in
seconds or "never" to it to set the expired timer wake delay for
the AC alarm timer or to set its expired wake policy to discard
wakeups if the system is on DC power, respectively.
What: /sys/bus/platform/devices/ACPI000E:00/ac_status
Date: March 2018
Contact: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Description:
(RW) The AC alarm status.
Reads return a hexadecimal bitmask representing the AC alarm
timer status with the following meaning of bits (see ACPI 6.2,
Section 9.18.5):
Bit(0): The timer has expired if set.
Bit(1): The timer has woken up the system from a sleep state
(S3 or S4/S5 if supported) if set.
The other bits are reserved.
Reads also cause the AC alarm timer status to be reset.
Another way to reset the the status of the AC alarm timer is to
write (the number) 0 to this file.
If the status return value indicates that the timer has expired,
it will immediately wake up the system from the S3 sleep state
(and from S4/S5 too if supported) until its status is explicitly
cleared through this attribute.
What: /sys/bus/platform/devices/ACPI000E:00/dc_alarm
Date: March 2018
Contact: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Description:
(RW,optional) The DC alarm timer value.
This attribute is only present if the TAD supports a separate
DC timer.
It is analogous to the ac_alarm attribute.
What: /sys/bus/platform/devices/ACPI000E:00/dc_policy
Date: March 2018
Contact: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Description:
(RW,optional) The DC alarm expired timer wake policy.
This attribute is only present if the TAD supports a separate
DC timer.
It is analogous to the ac_policy attribute.
What: /sys/bus/platform/devices/ACPI000E:00/dc_status
Date: March 2018
Contact: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Description:
(RW,optional) The DC alarm status.
This attribute is only present if the TAD supports a separate
DC timer.
It is analogous to the ac_status attribute.
Documentation/ABI/testing/sysfs-devices-platform-ipmi 0 → 100644
浏览文件 @ 30596ec3
What: /sys/devices/platform/ipmi_bmc.*/firmware_revision
Date: Mar, 2006
KernelVersion: v2.6.17
Contact: openipmi-developer@lists.sourceforge.net
Description:
(RO) The major and minor revision of the firmware.
What: /sys/devices/platform/ipmi_bmc.*/aux_firmware_revision
Date: Mar, 2006
KernelVersion: v2.6.17
Contact: openipmi-developer@lists.sourceforge.net
Description:
(RO) Holds additional information about the firmware revision,
such as boot block or internal data structure version numbers.
The meanings of the numbers are specific to the vendor
identified by Manufacturer ID.
What: /sys/devices/platform/ipmi_bmc.*/revision
Date: Mar, 2006
KernelVersion: v2.6.17
Contact: openipmi-developer@lists.sourceforge.net
Description:
(RO) Device revision. Useful for identifying if significant
hardware changes have been made to the implementation of the
management controller.
What: /sys/devices/platform/ipmi_bmc.*/provides_device_sdrs
Date: Mar, 2006
KernelVersion: v2.6.17
Contact: openipmi-developer@lists.sourceforge.net
Description:
(RO) Indicates whether device provides device sensor data
records (1) or not (0).
What: /sys/devices/platform/ipmi_bmc.*/device_id
Date: Mar, 2006
KernelVersion: v2.6.17
Contact: openipmi-developer@lists.sourceforge.net
Description:
(RO) Device id is specified by the manufacturer identified by
the Manufacturer ID field. This field allows controller specific
software to identify the unique application command, OEM
fields, and functionality that are provided by the controller
What: /sys/devices/platform/ipmi_bmc.*/additional_device_support
Date: Mar, 2006
KernelVersion: v2.6.17
Contact: openipmi-developer@lists.sourceforge.net
Description:
(RO) Lists the IPMI ‘logical device’ commands and functions
that the controller supports that are in addition to the
mandatory IPM and Application commands.
What: /sys/devices/platform/ipmi_bmc.*/ipmi_version
Date: Mar, 2006
KernelVersion: v2.6.17
Contact: openipmi-developer@lists.sourceforge.net
Description:
(RO) Displays the IPMI Command Specification Version.
What: /sys/devices/platform/ipmi_bmc.*/manufacturer_id
Date: Mar, 2006
KernelVersion: v2.6.17
Contact: openipmi-developer@lists.sourceforge.net
Description:
(RO) Identifies the manufacturer responsible for the
specification of functionality of the vendor (OEM)-specific
commands, codes, and interfaces used in the controller.
What: /sys/devices/platform/ipmi_bmc.*/product_id
Date: Mar, 2006
KernelVersion: v2.6.17
Contact: openipmi-developer@lists.sourceforge.net
Description:
(RO) Displays a number that identifies a particular system,
module, add-in card, or board set. The number is specified
according to the manufacturer given by Manufacturer ID.
For detailed definitions of the above attributes, refer to section 20.1 'Get
Device ID Command' of the IPMI specification v2.0.
What: /sys/devices/platform/ipmi_bmc.*/guid
Date: Mar, 2006
KernelVersion: v2.6.17
Contact: openipmi-developer@lists.sourceforge.net
Description:
(RO) A GUID (Globally Unique ID), also referred to as a UUID
(Universally Unique Identifier), for the management controller,
as described in section 20.8 'Get Device GUID Command' of the
IPMI specification v2.0.
What: /sys/devices/platform/ipmi_si.*/type
Date: Sep, 2017
KernelVersion: v4.15
Contact: openipmi-developer@lists.sourceforge.net
Description:
(RO) The device interface for IPMI "kcs", "smic", "bt" or
"invalid"
What: /sys/devices/platform/ipmi_si.*/idles
What: /sys/devices/platform/ipmi_si.*/watchdog_pretimeouts
What: /sys/devices/platform/ipmi_si.*/complete_transactions
What: /sys/devices/platform/ipmi_si.*/events
What: /sys/devices/platform/ipmi_si.*/interrupts
What: /sys/devices/platform/ipmi_si.*/hosed_count
What: /sys/devices/platform/ipmi_si.*/long_timeouts
What: /sys/devices/platform/ipmi_si.*/flag_fetches
What: /sys/devices/platform/ipmi_si.*/attentions
What: /sys/devices/platform/ipmi_si.*/incoming_messages
What: /sys/devices/platform/ipmi_si.*/short_timeouts
Date: Sep, 2017
KernelVersion: v4.15
Contact: openipmi-developer@lists.sourceforge.net
Description:
idles: (RO) Number of times the interface was
idle while being polled.
watchdog_pretimeouts: (RO) Number of watchdog pretimeouts.
complete_transactions: (RO) Number of completed messages.
events: (RO) Number of IPMI events received from
the hardware.
interrupts: (RO) Number of interrupts the driver
handled.
hosed_count: (RO) Number of times the hardware didn't
follow the state machine.
long_timeouts: (RO) Number of times the driver
requested a timer while nothing was in
progress.
flag_fetches: (RO) Number of times the driver
requested flags from the hardware.
attentions: (RO) Number of time the driver got an
ATTN from the hardware.
incoming_messages: (RO) Number of asynchronous messages
received.
short_timeouts: (RO) Number of times the driver
requested a timer while an operation was
in progress.
What: /sys/devices/platform/ipmi_si.*/interrupts_enabled
Date: Sep, 2017
KernelVersion: v4.15
Contact: openipmi-developer@lists.sourceforge.net
Description:
(RO) Indicates whether interrupts are enabled or not. The driver
disables interrupts when it gets into a situation where it
cannot handle messages due to lack of memory. Once that
situation clears up, it will re-enable interrupts.
What: /sys/devices/platform/ipmi_si.*/params
Date: Sep, 2017
KernelVersion: v4.15
Contact: openipmi-developer@lists.sourceforge.net
Description:
[to be documented]
What: /sys/devices/platform/dmi-ipmi-ssif.*/type
Date: Sep, 2017
KernelVersion: v4.15
Contact: openipmi-developer@lists.sourceforge.net
Description:
(RO) Shows the IMPI device interface type - "ssif" here.
What: /sys/devices/platform/dmi-ipmi-ssif.*/hosed
What: /sys/devices/platform/dmi-ipmi-ssif.*/alerts
What: /sys/devices/platform/dmi-ipmi-ssif.*/sent_messages
What: /sys/devices/platform/dmi-ipmi-ssif.*/sent_messages_parts
What: /sys/devices/platform/dmi-ipmi-ssif.*/received_messages
What: /sys/devices/platform/dmi-ipmi-ssif.*/received_message_parts
What: /sys/devices/platform/dmi-ipmi-ssif.*/events
What: /sys/devices/platform/dmi-ipmi-ssif.*/watchdog_pretimeouts
What: /sys/devices/platform/dmi-ipmi-ssif.*/flag_fetches
What: /sys/devices/platform/dmi-ipmi-ssif.*/send_retries
What: /sys/devices/platform/dmi-ipmi-ssif.*/receive_retries
What: /sys/devices/platform/dmi-ipmi-ssif.*/send_errors
What: /sys/devices/platform/dmi-ipmi-ssif.*/receive_errors
Date: Sep, 2017
KernelVersion: v4.15
Contact: openipmi-developer@lists.sourceforge.net
Description:
hosed: (RO) Number of times the hardware didn't
follow the state machine.
alerts: (RO) Number of alerts received.
sent_messages: (RO) Number of total messages sent.
sent_message_parts: (RO) Number of message parts sent.
Messages may be broken into parts if
they are long.
receieved_messages: (RO) Number of message responses
received.
received_message_parts: (RO) Number of message fragments
received.
events: (RO) Number of received events.
watchdog_pretimeouts: (RO) Number of watchdog pretimeouts.
flag_fetches: (RO) Number of times a flag fetch was
requested.
send_retries: (RO) Number of time a message was
retried.
receive_retries: (RO) Number of times the receive of a
message was retried.
send_errors: (RO) Number of times the send of a
message failed.
receive_errors: (RO) Number of errors in receiving
messages.
Documentation/ABI/testing/sysfs-devices-platform-trackpoint 0 → 100644
浏览文件 @ 30596ec3
What: /sys/devices/platform/i8042/.../sensitivity
Date: Aug, 2005
KernelVersion: 2.6.14
Contact: linux-input@vger.kernel.org
Description:
(RW) Trackpoint sensitivity.
What: /sys/devices/platform/i8042/.../intertia
Date: Aug, 2005
KernelVersion: 2.6.14
Contact: linux-input@vger.kernel.org
Description:
(RW) Negative inertia factor. High values cause the cursor to
snap backward when the trackpoint is released.
What: /sys/devices/platform/i8042/.../reach
Date: Aug, 2005
KernelVersion: 2.6.14
Contact: linux-input@vger.kernel.org
Description:
(RW) Backup range for z-axis press.
What: /sys/devices/platform/i8042/.../draghys
Date: Aug, 2005
KernelVersion: 2.6.14
Contact: linux-input@vger.kernel.org
Description:
(RW) The drag hysteresis controls how hard it is to drag with
z-axis pressed.
What: /sys/devices/platform/i8042/.../mindrag
Date: Aug, 2005
KernelVersion: 2.6.14
Contact: linux-input@vger.kernel.org
Description:
(RW) Minimum amount of force needed to trigger dragging.
What: /sys/devices/platform/i8042/.../speed
Date: Aug, 2005
KernelVersion: 2.6.14
Contact: linux-input@vger.kernel.org
Description:
(RW) Speed of the trackpoint cursor.
What: /sys/devices/platform/i8042/.../thresh
Date: Aug, 2005
KernelVersion: 2.6.14
Contact: linux-input@vger.kernel.org
Description:
(RW) Minimum value for z-axis force required to trigger a press
or release, relative to the running average.
What: /sys/devices/platform/i8042/.../upthresh
Date: Aug, 2005
KernelVersion: 2.6.14
Contact: linux-input@vger.kernel.org
Description:
(RW) The offset from the running average required to generate a
select (click) on z-axis on release.
What: /sys/devices/platform/i8042/.../ztime
Date: Aug, 2005
KernelVersion: 2.6.14
Contact: linux-input@vger.kernel.org
Description:
(RW) This attribute determines how sharp a press has to be in
order to be recognized.
What: /sys/devices/platform/i8042/.../jenks
Date: Aug, 2005
KernelVersion: 2.6.14
Contact: linux-input@vger.kernel.org
Description:
(RW) Minimum curvature in degrees required to generate a double
click without a release.
What: /sys/devices/platform/i8042/.../skipback
Date: Aug, 2005
KernelVersion: 2.6.14
Contact: linux-input@vger.kernel.org
Description:
(RW) When the skipback bit is set, backup cursor movement during
releases from drags will be suppressed. The default value for
this bit is 0.
What: /sys/devices/platform/i8042/.../ext_dev
Date: Aug, 2005
KernelVersion: 2.6.14
Contact: linux-input@vger.kernel.org
Description:
(RW) Disable (0) or enable (1) external pointing device.
What: /sys/devices/platform/i8042/.../press_to_select
Date: Aug, 2005
KernelVersion: 2.6.14
Contact: linux-input@vger.kernel.org
Description:
(RW) Writing a value of 1 to this file will enable the Press to
Select functions like tapping the control stick to simulate a
left click, and writing 0 will disable it.
What: /sys/devices/platform/i8042/.../drift_time
Date: Dec, 2014
KernelVersion: 3.19
Contact: linux-input@vger.kernel.org
Description:
(RW) This parameter controls the period of time to test for a
‘hands off’ condition (i.e. when no force is applied) before a
drift (noise) calibration occurs.
IBM Trackpoints have a feature to compensate for drift by
recalibrating themselves periodically. By default, if for 0.5
seconds there is no change in position, it's used as the new
zero. This duration is too low. Often, the calibration happens
when the trackpoint is in fact being used.
Documentation/ABI/testing/sysfs-devices-system-cpu
浏览文件 @ 30596ec3
......@@ -198,6 +198,31 @@ Description:
time (in microseconds) this cpu should spend in this idle state
to make the transition worth the effort.
What: /sys/devices/system/cpu/cpuX/cpuidle/stateN/s2idle/
Date: March 2018
KernelVersion: v4.17
Contact: Linux power management list <linux-pm@vger.kernel.org>
Description:
Idle state usage statistics related to suspend-to-idle.
This attribute group is only present for states that can be
used in suspend-to-idle with suspended timekeeping.
What: /sys/devices/system/cpu/cpuX/cpuidle/stateN/s2idle/time
Date: March 2018
KernelVersion: v4.17
Contact: Linux power management list <linux-pm@vger.kernel.org>
Description:
Total time spent by the CPU in suspend-to-idle (with scheduler
tick suspended) after requesting this state.
What: /sys/devices/system/cpu/cpuX/cpuidle/stateN/s2idle/usage
Date: March 2018
KernelVersion: v4.17
Contact: Linux power management list <linux-pm@vger.kernel.org>
Description:
Total number of times this state has been requested by the CPU
while entering suspend-to-idle.
What: /sys/devices/system/cpu/cpu#/cpufreq/*
Date: pre-git history
......
Documentation/ABI/testing/sysfs-driver-fsi-master-gpio 0 → 100644
浏览文件 @ 30596ec3
What: /sys/bus/platform/devices/[..]/fsi-master-gpio/external_mode
Date: Feb 2018
KernelVersion: 4.17
Contact: jk@ozlabs.org
Description:
Controls access arbitration for GPIO-based FSI master. A
value of 0 (the default) sets normal mode, where the
driver performs FSI bus transactions, 1 sets external mode,
where the FSI bus is driven externally (for example, by
a debug device).
Documentation/ABI/testing/sysfs-driver-hid-logitech-hidpp 0 → 100644
浏览文件 @ 30596ec3
What: /sys/bus/hid/drivers/logitech-hidpp-device/<dev>/range
Date: Jan, 2016
KernelVersion: 4.6
Contact: linux-input@vger.kernel.org
Description:
(RW) This attribute controls the amount of 'turn' permitted in
Logitech G920 wheel. Reading from the file shows the current
range of the steering wheel. Writing a value within the min and
max boundary sets the range of the wheel.
What: /sys/bus/hid/drivers/logitech-hidpp-device/<dev>/builtin_power_supply
Date: Apr, 2017
KernelVersion: 4.12
Contact: linux-input@vger.kernel.org
Description:
Presence of this file indicates that HID++ driver is capable of
handling battery properties in the kernel. This way, upower can
add a udev rule to decide whether or not it should use the
internal unifying support or the generic kernel one.
Documentation/ABI/testing/sysfs-driver-hid-ntrig 0 → 100644
浏览文件 @ 30596ec3
What: /sys/bus/hid/drivers/ntrig/<dev>/activate_slack
Date: May, 2010
KernelVersion: 2.6.35
Contact: linux-input@vger.kernel.org
Description:
(RW) Number of contact frames ignored before acknowledging the
start of activity (activating touch).
What: /sys/bus/hid/drivers/ntrig/<dev>/decativate_slack
Date: May, 2010
KernelVersion: 2.6.35
Contact: linux-input@vger.kernel.org
Description:
(RW) Number of empty (no contact) frames ignored before
acknowledging the end of activity (deactivating touch).
When the last finger is removed from the device, it sends a
number of empty frames. By holding off on deactivation for a few
frames false erroneous disconnects can be tolerated, where the
sensor may mistakenly not detect a finger that is still present.
What: /sys/bus/hid/drivers/ntrig/<dev>/activation_width
What: /sys/bus/hid/drivers/ntrig/<dev>/activation_height
Date: May, 2010
KernelVersion: 2.6.35
Contact: linux-input@vger.kernel.org
Description:
Threholds to override activation slack.
activation_width: (RW) Width threshold to immediately
start processing touch events.
activation_height: (RW) Height threshold to immediately
start processing touch events.
What: /sys/bus/hid/drivers/ntrig/<dev>/min_width
What: /sys/bus/hid/drivers/ntrig/<dev>/min_height
Date: May, 2010
KernelVersion: 2.6.35
Contact: linux-input@vger.kernel.org
Description:
Minimum size contact accepted.
min_width: (RW) Minimum touch contact width to decide
activation and activity.
min_height: (RW) Minimum touch contact height to decide
activation and activity.
What: /sys/bus/hid/drivers/ntrig/<dev>/sensor_physical_width
What: /sys/bus/hid/drivers/ntrig/<dev>/sensor_physical_height
Date: May, 2010
KernelVersion: 2.6.35
Contact: linux-input@vger.kernel.org
Description:
(RO) These are internal ranges not used for normal events but
useful for tuning.
What: /sys/bus/hid/drivers/ntrig/<dev>/sensor_logical_width
What: /sys/bus/hid/drivers/ntrig/<dev>/sensor_logical_height
Date: May, 2010
KernelVersion: 2.6.35
Contact: linux-input@vger.kernel.org
Description:
(RO) The range for positions reported during activity.
Documentation/ABI/testing/sysfs-driver-ufs 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/ABI/testing/sysfs-fs-f2fs
浏览文件 @ 30596ec3
......@@ -192,3 +192,14 @@ Date: November 2017
Contact: "Sheng Yong" <shengyong1@huawei.com>
Description:
Controls readahead inode block in readdir.
What: /sys/fs/f2fs/<disk>/extension_list
Date: Feburary 2018
Contact: "Chao Yu" <yuchao0@huawei.com>
Description:
Used to control configure extension list:
- Query: cat /sys/fs/f2fs/<disk>/extension_list
- Add: echo '[h/c]extension' > /sys/fs/f2fs/<disk>/extension_list
- Del: echo '[h/c]!extension' > /sys/fs/f2fs/<disk>/extension_list
- [h] means add/del hot file extension
- [c] means add/del cold file extension
Documentation/ABI/testing/sysfs-kernel-irq
浏览文件 @ 30596ec3
......@@ -51,3 +51,10 @@ Date: September 2016
KernelVersion: 4.9
Contact: Craig Gallek <kraig@google.com>
Description: The type of the interrupt. Either the string 'level' or 'edge'.
What: /sys/kernel/irq/<irq>/wakeup
Date: March 2018
KernelVersion: 4.17
Contact: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Description: The wakeup state of the interrupt. Either the string
'enabled' or 'disabled'.
Documentation/ABI/testing/sysfs-power
浏览文件 @ 30596ec3
......@@ -287,3 +287,17 @@ Description:
Writing a "1" to this file enables the debug messages and
writing a "0" (default) to it disables them. Reads from
this file return the current value.
What: /sys/power/resume_offset
Date: April 2018
Contact: Mario Limonciello <mario.limonciello@dell.com>
Description:
This file is used for telling the kernel an offset into a disk
to use when hibernating the system such as with a swap file.
Reads from this file will display the current offset
the kernel will be using on the next hibernation
attempt.
Using this sysfs file will override any values that were
set using the kernel command line for disk offset.
\ No newline at end of file
Documentation/accelerators/ocxl.rst
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/arm/Atmel/README 已删除 100644 → 0
浏览文件 @ d54e7934
此差异已折叠。
Documentation/arm/Microchip/README 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/arm/stm32/overview.rst 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/arm/stm32/overview.txt 已删除 100644 → 0
浏览文件 @ d54e7934
此差异已折叠。
Documentation/arm/stm32/stm32f429-overview.rst 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/arm/stm32/stm32f746-overview.rst 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/arm/stm32/stm32f769-overview.rst 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/arm/stm32/stm32h743-overview.rst 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/arm/stm32/stm32mp157-overview.rst 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/arm64/elf_hwcaps.txt
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/arm64/memory.txt
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/blackfin/00-INDEX 已删除 100644 → 0
浏览文件 @ d54e7934
此差异已折叠。
Documentation/blackfin/bfin-gpio-notes.txt 已删除 100644 → 0
浏览文件 @ d54e7934
此差异已折叠。
Documentation/blackfin/bfin-spi-notes.txt 已删除 100644 → 0
浏览文件 @ d54e7934
此差异已折叠。
Documentation/bpf/bpf_devel_QA.txt
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/cgroup-v1/memory.txt
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/clk.txt
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/cpu-freq/core.txt
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/cpuidle/sysfs.txt
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/cris/README 已删除 100644 → 0
浏览文件 @ d54e7934
此差异已折叠。
Documentation/crypto/crypto_engine.rst 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/dev-tools/sparse.rst
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/devicetree/bindings/arm/arm,scmi.txt 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/devicetree/bindings/arm/npcm/npcm.txt 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/devicetree/bindings/dma/mtk-hsdma.txt 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/devicetree/bindings/fsi/fsi.txt 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/devicetree/bindings/gpio/gpio-sprd.txt 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/devicetree/bindings/i2c/i2c-synquacer.txt 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/devicetree/bindings/jailhouse.txt 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/devicetree/bindings/media/i2c/ov2685.txt 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/devicetree/bindings/media/i2c/ov5695.txt 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/devicetree/bindings/media/i2c/ov9650.txt 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/devicetree/bindings/media/renesas,ceu.txt 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/devicetree/bindings/mips/mscc.txt 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/devicetree/bindings/nds32/atl2c.txt 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/devicetree/bindings/nds32/cpus.txt 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/devicetree/bindings/net/nixge.txt 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/devicetree/bindings/pmem/pmem-region.txt 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/devicetree/bindings/regulator/88pg86x.txt 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/devicetree/bindings/rng/imx-rng.txt 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/devicetree/bindings/rng/ks-sa-rng.txt 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/devicetree/bindings/rtc/isil,isl12026.txt 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/devicetree/bindings/sound/ak4458.txt 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/devicetree/bindings/sound/ak5558.txt 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/devicetree/bindings/sound/pcm1789.txt 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/devicetree/bindings/sound/tda7419.txt 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/devicetree/bindings/usb/amlogic,dwc3.txt 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/devicetree/bindings/usb/usb-hcd.txt 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/driver-api/device_connection.rst 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/driver-api/gpio.rst 已删除 100644 → 0
浏览文件 @ d54e7934
此差异已折叠。
Documentation/driver-api/gpio/board.rst 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/driver-api/gpio/consumer.rst 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/driver-api/gpio/driver.rst 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/driver-api/gpio/drivers-on-gpio.rst 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/driver-api/gpio/index.rst 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/driver-api/gpio/intro.rst 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/driver-api/gpio/legacy.rst 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/driver-api/index.rst
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/driver-api/scsi.rst
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/fault-injection/nvme-fault-injection.txt 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/features/list-arch.sh
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/filesystems/afs.txt
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/filesystems/ceph.txt
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/filesystems/cifs/TODO
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/filesystems/f2fs.txt
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/filesystems/udf.txt
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/filesystems/xfs.txt
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/frv/README.txt 已删除 100644 → 0
浏览文件 @ d54e7934
此差异已折叠。
Documentation/frv/atomic-ops.txt 已删除 100644 → 0
浏览文件 @ d54e7934
此差异已折叠。
Documentation/frv/booting.txt 已删除 100644 → 0
浏览文件 @ d54e7934
此差异已折叠。
Documentation/frv/clock.txt 已删除 100644 → 0
浏览文件 @ d54e7934
此差异已折叠。
Documentation/frv/configuring.txt 已删除 100644 → 0
浏览文件 @ d54e7934
此差异已折叠。
Documentation/frv/features.txt 已删除 100644 → 0
浏览文件 @ d54e7934
此差异已折叠。
Documentation/frv/gdbinit 已删除 100644 → 0
浏览文件 @ d54e7934
此差异已折叠。
Documentation/frv/gdbstub.txt 已删除 100644 → 0
浏览文件 @ d54e7934
此差异已折叠。
Documentation/frv/kernel-ABI.txt 已删除 100644 → 0
浏览文件 @ d54e7934
此差异已折叠。
Documentation/frv/mmu-layout.txt 已删除 100644 → 0
浏览文件 @ d54e7934
此差异已折叠。
Documentation/gpio/00-INDEX
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/gpio/board.txt 已删除 100644 → 0
浏览文件 @ d54e7934
此差异已折叠。
Documentation/gpio/consumer.txt 已删除 100644 → 0
浏览文件 @ d54e7934
此差异已折叠。
Documentation/gpio/driver.txt 已删除 100644 → 0
浏览文件 @ d54e7934
此差异已折叠。
Documentation/gpio/drivers-on-gpio.txt 已删除 100644 → 0
浏览文件 @ d54e7934
此差异已折叠。
Documentation/gpio/gpio-legacy.txt 已删除 100644 → 0
浏览文件 @ d54e7934
此差异已折叠。
Documentation/gpio/gpio.txt 已删除 100644 → 0
浏览文件 @ d54e7934
此差异已折叠。
Documentation/gpio/sysfs.txt
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/gpu/drivers.rst 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/gpu/drm-kms.rst
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/gpu/index.rst
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/gpu/todo.rst
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/hwmon/adm1275
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/hwmon/lm92
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/hwmon/nct6775
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/hwmon/sht21
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/hwmon/sht3x
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/ia64/serial.txt
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/index.rst
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/infiniband/sysfs.txt
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/input/devices/pxrc.rst 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/isdn/INTERFACE.CAPI
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/isdn/README
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/isdn/README.FAQ
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/isdn/README.gigaset
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/kbuild/kbuild.txt
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/kbuild/kconfig.txt
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/kbuild/makefiles.txt
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/media/uapi/cec/cec-pin-error-inj.rst 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/memory-barriers.txt
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/metag/00-INDEX 已删除 100644 → 0
浏览文件 @ d54e7934
此差异已折叠。
Documentation/metag/kernel-ABI.txt 已删除 100644 → 0
浏览文件 @ d54e7934
此差异已折叠。
Documentation/mn10300/ABI.txt 已删除 100644 → 0
浏览文件 @ d54e7934
此差异已折叠。
Documentation/networking/dpaa2/index.rst 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/networking/i40e.txt
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/networking/ice.txt 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/networking/index.rst
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/networking/irda.txt 已删除 100644 → 0
浏览文件 @ d54e7934
此差异已折叠。
Documentation/networking/net_dim.txt 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/networking/nf_flowtable.txt 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/networking/tls.txt
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/power/swsusp.txt
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/process/4.Coding.rst
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/process/5.Posting.rst
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/process/changes.rst
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/process/clang-format.rst 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/process/howto.rst
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/ptp/ptp.txt
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/rapidio/sysfs.txt
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/s390/vfio-ccw.txt
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/scsi/ChangeLog.1992-1997 已删除 100644 → 0
浏览文件 @ d54e7934
此差异已折叠。
Documentation/scsi/Mylex.txt 已删除 100644 → 0
浏览文件 @ d54e7934
此差异已折叠。
Documentation/scsi/sd-parameters.txt 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/scsi/tmscsim.txt 已删除 100644 → 0
浏览文件 @ d54e7934
此差异已折叠。
Documentation/security/LSM-sctp.rst 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/security/SELinux-sctp.rst 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/sparc/adi.txt 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/sphinx/kerneldoc.py
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/sysctl/kernel.txt
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/sysctl/net.txt
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/sysctl/vm.txt
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/thermal/sysfs-api.txt
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/timers/NO_HZ.txt
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/trace/coresight.txt
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/trace/events-kmem.rst 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/trace/events-kmem.txt 已删除 100644 → 0
浏览文件 @ d54e7934
此差异已折叠。
Documentation/trace/events-msr.rst 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/trace/events-msr.txt 已删除 100644 → 0
浏览文件 @ d54e7934
此差异已折叠。
Documentation/trace/events-nmi.rst 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/trace/events-nmi.txt 已删除 100644 → 0
浏览文件 @ d54e7934
此差异已折叠。
Documentation/trace/events-power.rst 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/trace/events-power.txt 已删除 100644 → 0
浏览文件 @ d54e7934
此差异已折叠。
Documentation/trace/events.rst 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/trace/events.txt 已删除 100644 → 0
浏览文件 @ d54e7934
此差异已折叠。
Documentation/trace/ftrace-design.rst 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/trace/ftrace-design.txt 已删除 100644 → 0
浏览文件 @ d54e7934
此差异已折叠。
Documentation/trace/ftrace-uses.rst
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/trace/ftrace.rst 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/trace/ftrace.txt 已删除 100644 → 0
浏览文件 @ d54e7934
此差异已折叠。
Documentation/trace/histogram.txt 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/trace/hwlat_detector.rst 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/trace/hwlat_detector.txt 已删除 100644 → 0
浏览文件 @ d54e7934
此差异已折叠。
Documentation/trace/index.rst 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/trace/intel_th.rst 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/trace/intel_th.txt 已删除 100644 → 0
浏览文件 @ d54e7934
此差异已折叠。
Documentation/trace/kprobetrace.rst 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/trace/kprobetrace.txt 已删除 100644 → 0
浏览文件 @ d54e7934
此差异已折叠。
Documentation/trace/mmiotrace.rst 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/trace/mmiotrace.txt 已删除 100644 → 0
浏览文件 @ d54e7934
此差异已折叠。
Documentation/trace/stm.rst 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/trace/stm.txt 已删除 100644 → 0
浏览文件 @ d54e7934
此差异已折叠。
Documentation/trace/tracepoint-analysis.rst 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/trace/tracepoint-analysis.txt 已删除 100644 → 0
浏览文件 @ d54e7934
此差异已折叠。
Documentation/trace/tracepoints.rst 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/trace/tracepoints.txt 已删除 100644 → 0
浏览文件 @ d54e7934
此差异已折叠。
Documentation/trace/uprobetracer.rst 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/trace/uprobetracer.txt 已删除 100644 → 0
浏览文件 @ d54e7934
此差异已折叠。
Documentation/virtual/kvm/00-INDEX
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/virtual/kvm/api.txt
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/virtual/kvm/cpuid.txt
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/vm/00-INDEX
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/vm/hmm.txt
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/vm/page_migration
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/x86/00-INDEX
浏览文件 @ 30596ec3
此差异已折叠。
Documentation/x86/x86_64/mm.txt
浏览文件 @ 30596ec3
此差异已折叠。
MAINTAINERS
浏览文件 @ 30596ec3
此差异已折叠。
Makefile
浏览文件 @ 30596ec3
此差异已折叠。
README
浏览文件 @ 30596ec3
此差异已折叠。
arch/Kconfig
浏览文件 @ 30596ec3
此差异已折叠。
arch/alpha/Kconfig
浏览文件 @ 30596ec3
此差异已折叠。
arch/alpha/include/asm/cmpxchg.h
浏览文件 @ 30596ec3
此差异已折叠。
arch/alpha/include/asm/io.h
浏览文件 @ 30596ec3
此差异已折叠。
arch/alpha/include/asm/xchg.h
浏览文件 @ 30596ec3
此差异已折叠。
arch/alpha/include/uapi/asm/mman.h
浏览文件 @ 30596ec3
此差异已折叠。
arch/alpha/kernel/Makefile
浏览文件 @ 30596ec3
此差异已折叠。
arch/alpha/kernel/bugs.c 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
arch/alpha/kernel/entry.S
浏览文件 @ 30596ec3
此差异已折叠。
arch/alpha/kernel/osf_sys.c
浏览文件 @ 30596ec3
此差异已折叠。
arch/alpha/kernel/pci-noop.c
浏览文件 @ 30596ec3
此差异已折叠。
arch/alpha/kernel/pci.c
浏览文件 @ 30596ec3
此差异已折叠。
arch/alpha/kernel/perf_event.c
浏览文件 @ 30596ec3
此差异已折叠。
arch/alpha/kernel/rtc.c
浏览文件 @ 30596ec3
此差异已折叠。
arch/arc/boot/dts/Makefile
浏览文件 @ 30596ec3
此差异已折叠。
arch/arc/kernel/troubleshoot.c
浏览文件 @ 30596ec3
此差异已折叠。
arch/arc/mm/cache.c
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/Kconfig
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/Kconfig.debug
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/Makefile
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/compressed/misc.c
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/compressed/misc.h 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/compressed/string.c
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/deflate_xip_data.sh
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/Makefile
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/am335x-pdu001.dts 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/am33xx.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/am4372.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/am437x-gp-evm.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/am437x-sk-evm.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/am571x-idk.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/am572x-idk.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/animeo_ip.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/armada-370-db.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/armada-370-rd.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/armada-370.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/armada-375-db.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/armada-375.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/armada-380.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/armada-385.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/armada-388-db.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/armada-388-gp.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/armada-388-rd.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/armada-388.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/armada-38x.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/armada-390-db.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/armada-390.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/armada-395-gp.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/armada-395.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/armada-398-db.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/armada-398.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/armada-39x.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/armada-xp-db.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/armada-xp-gp.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/armada-xp.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/artpec6.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/aspeed-bmc-arm-centriq2400-rep.dts 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/aspeed-g4.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/aspeed-g5.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/at91-tse850-3.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/at91rm9200.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/at91sam9260.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/at91sam9260ek.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/at91sam9261.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/at91sam9263.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/at91sam9263ek.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/at91sam9g25.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/at91sam9g45.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/at91sam9n12.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/at91sam9rl.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/at91sam9rlek.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/at91sam9x5.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/atlas7-evb.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/axp209.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/axp22x.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/axp81x.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/bcm2835-rpi.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/bcm283x.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/bcm958622hr.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/bcm958623hr.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/bcm958625hr.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/bcm958625k.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/bcm988312hr.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/da850-evm.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/dra7-evm.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/dra7.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/dra71-evm.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/dra76-evm.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/dra76x-mmc-iodelay.dtsi 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/emev2-kzm9d.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/exynos3250.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/exynos4.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/exynos4210.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/exynos4412-galaxy-s3.dtsi 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/exynos4412-i9300.dts 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/exynos4412-i9305.dts 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/exynos4412-midas.dtsi 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/exynos4412-n710x.dts 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/exynos4412.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/exynos5250.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/exynos5410.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/exynos5440.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/exynos5800.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx1-ads.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx1-apf9328.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx1.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx23-evk.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx23-sansa.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx23-xfi3.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx23.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx25-pdk.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx25-pinfunc.h
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx25.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx27-apf27.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx27-pdk.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx27.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx28-apf28.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx28-evk.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx28-m28.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx28-m28cu3.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx28-m28evk.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx28-sps1.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx28-ts4600.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx28-tx28.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx28.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx31-bug.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx31.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx35-pdk.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx35.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx50-evk.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx50.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx51-apf51.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx51-babbage.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx51-ts4800.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx51.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx53-ard.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx53-cx9020.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx53-m53.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx53-m53evk.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx53-ppd.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx53-smd.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx53-tqma53.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx53-tx53.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx53.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx6dl-phytec-mira-rdk-nand.dts 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx6dl-ts4900.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx6dl-ts7970.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx6dl.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx6q-apf6dev.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx6q-arm2.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx6q-ba16.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx6q-bx50v3.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx6q-cm-fx6.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx6q-dms-ba16.dts 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx6q-evi.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx6q-gk802.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx6q-h100.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx6q-mccmon6.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx6q-novena.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx6q-phytec-mira-rdk-emmc.dts 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx6q-phytec-mira-rdk-nand.dts 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx6q-rex-pro.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx6q-sbc6x.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx6q-tbs2910.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx6q-ts4900.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx6q-ts7970.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx6q.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx6qdl-phytec-mira.dtsi 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx6qdl-phytec-phycore-som.dtsi 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx6qdl-rex.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx6qdl-tx6.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx6qdl-udoo.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx6qdl.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx6qp-phytec-mira-rdk-nand.dts 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx6sl-evk.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx6sl-warp.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx6sl.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx6sx-sdb.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx6sx.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx6ul-14x14-evk.dtsi 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx6ul-geam.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx6ul-isiot.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx6ul-pinfunc.h
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx6ul-tx6ul.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx6ul.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx6ull-colibri-eval-v3.dts 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx6ull-colibri-eval-v3.dtsi 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx6ull-colibri-nonwifi.dtsi 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx6ull-colibri-wifi-eval-v3.dts 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx6ull-colibri-wifi.dtsi 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx6ull-colibri.dtsi 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx6ull-pinfunc-snvs.h 0 → 100644
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx6ull.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx7d-pico.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx7d-sdb.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx7s-warp.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/imx7s.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/keystone-k2e.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/keystone-k2g.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/keystone-k2l.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/keystone.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/kirkwood-b3.dts
浏览文件 @ 30596ec3
此差异已折叠。
arch/arm/boot/dts/kirkwood-db.dtsi
浏览文件 @ 30596ec3
此差异已折叠。
Markdown is supported
0% 或 .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑！
想要评论请 注册 或