code:
what:		/sys/kernel/mm/damon/
Date:		Mar 2022
Contact:	SeongJae Park <sj@kernel.org>
Description:	Interface for Data Access MONitoring (DAMON).  Contains files
		for controlling DAMON.  For more details on DAMON itself,
		please refer to Documentation/admin-guide/mm/damon/index.rst.

What:		/sys/kernel/mm/damon/admin/
Date:		Mar 2022
Contact:	SeongJae Park <sj@kernel.org>
Description:	Interface for privileged users of DAMON.  Contains files for
		controlling DAMON that aimed to be used by privileged users.

What:		/sys/kernel/mm/damon/admin/kdamonds/nr_kdamonds
Date:		Mar 2022
Contact:	SeongJae Park <sj@kernel.org>
Description:	Writing a number 'N' to this file creates the number of
		directories for controlling each DAMON worker thread (kdamond)
		named '0' to 'N-1' under the kdamonds/ directory.

What:		/sys/kernel/mm/damon/admin/kdamonds/<K>/state
Date:		Mar 2022
Contact:	SeongJae Park <sj@kernel.org>
Description:	Writing 'on' or 'off' to this file makes the kdamond starts or
		stops, respectively.  Reading the file returns the keywords
		based on the current status.  Writing 'commit' to this file
		makes the kdamond reads the user inputs in the sysfs files
		except 'state' again.  Writing 'update_schemes_stats' to the
		file updates contents of schemes stats files of the kdamond.
		Writing 'update_schemes_tried_regions' to the file updates
		contents of 'tried_regions' directory of every scheme directory
		of this kdamond.  Writing 'clear_schemes_tried_regions' to the
		file removes contents of the 'tried_regions' directory.

What:		/sys/kernel/mm/damon/admin/kdamonds/<K>/pid
Date:		Mar 2022
Contact:	SeongJae Park <sj@kernel.org>
Description:	Reading this file returns the pid of the kdamond if it is
		running.

What:		/sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/nr_contexts
Date:		Mar 2022
Contact:	SeongJae Park <sj@kernel.org>
Description:	Writing a number 'N' to this file creates the number of
		directories for controlling each DAMON context named '0' to
		'N-1' under the contexts/ directory.

What:		/sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/avail_operations
Date:		Apr 2022
Contact:	SeongJae Park <sj@kernel.org>
Description:	Reading this file returns the available monitoring operations
		sets on the currently running kernel.

What:		/sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/operations
Date:		Mar 2022
Contact:	SeongJae Park <sj@kernel.org>
Description:	Writing a keyword for a monitoring operations set ('vaddr' for
		virtual address spaces monitoring, 'fvaddr' for fixed virtual
		address ranges monitoring, and 'paddr' for the physical address
		space monitoring) to this file makes the context to use the
		operations set.  Reading the file returns the keyword for the
		operations set the context is set to use.

		Note that only the operations sets that listed in
		'avail_operations' file are valid inputs.

What:		/sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/monitoring_attrs/intervals/sample_us
Date:		Mar 2022
Contact:	SeongJae Park <sj@kernel.org>
Description:	Writing a value to this file sets the sampling interval of the
		DAMON context in microseconds as the value.  Reading this file
		returns the value.

What:		/sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/monitoring_attrs/intervals/aggr_us
Date:		Mar 2022
Contact:	SeongJae Park <sj@kernel.org>
Description:	Writing a value to this file sets the aggregation interval of
		the DAMON context in microseconds as the value.  Reading this
		file returns the value.

What:		/sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/monitoring_attrs/intervals/update_us
Date:		Mar 2022
Contact:	SeongJae Park <sj@kernel.org>
Description:	Writing a value to this file sets the update interval of the
		DAMON context in microseconds as the value.  Reading this file
		returns the value.

What:		/sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/monitoring_attrs/nr_regions/min

WDate:		Mar 2022
Contact:	SeongJae Park <sj@kernel.org>
Description:	Writing a value to this file sets the minimum number of
		monitoring regions of the DAMON context as the value.  Reading
		this file returns the value.

What:		/sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/monitoring_attrs/nr_regions/max
Date:		Mar 2022
Contact:	SeongJae Park <sj@kernel.org>
Description:	Writing a value to this file sets the maximum number of
		monitoring regions of the DAMON context as the value.  Reading
		this file returns the value.

What:		/sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/targets/nr_targets
Date:		Mar 2022
Contact:	SeongJae Park <sj@kernel.org>
Description:	Writing a number 'N' to this file creates the number of
		directories for controlling each DAMON target of the context
		named '0' to 'N-1' under the contexts/ directory.

What:		/sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/targets/<T>/pid_target
Date:		Mar 2022
Contact:	SeongJae Park <sj@kernel.org>
Description:	Writing to and reading from this file sets and gets the pid of
		the target process if the context is for virtual address spaces
		monitoring, respectively.

What:		/sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/targets/<T>/regions/nr_regions
Date:		Mar 2022
Contact:	SeongJae Park <sj@kernel.org>
Description:	Writing a number 'N' to this file creates the number of
		directories for setting each DAMON target memory region of the
		context named '0' to 'N-1' under the regions/ directory.  In
		case of the virtual address space monitoring, DAMON
		automatically sets the target memory region based on the target
		processes' mappings.

What:		/sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/targets/<T>/regions/<R>/start
Date:		Mar 2022
Contact:	SeongJae Park <sj@kernel.org>
Description:	Writing to and reading from this file sets and gets the start
		address of the monitoring region.

What:		/sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/targets/<T>/regions/<R>/end
Date:		Mar 2022
Contact:	SeongJae Park <sj@kernel.org>
Description:	Writing to and reading from this file sets and gets the end
		address of the monitoring region.

What:		/sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/schemes/nr_schemes
Date:		Mar 2022
Contact:	SeongJae Park <sj@kernel.org>
Description:	Writing a number 'N' to this file creates the number of
		directories for controlling each DAMON-based operation scheme
		of the context named '0' to 'N-1' under the schemes/ directory.

What:		/sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/schemes/<S>/action
Date:		Mar 2022
Contact:	SeongJae Park <sj@kernel.org>
Description:	Writing to and reading from this file sets and gets the action
		of the scheme.

What:		/sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/schemes/<S>/access_pattern/sz/min
Date:		Mar 2022
Contact:	SeongJae Park <sj@kernel.org>
Description:	Writing to and reading from this file sets and gets the mimimum
		size of the scheme's target regions in bytes.

What:		/sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/schemes/<S>/access_pattern/sz/max
Date:		Mar 2022
Contact:	SeongJae Park <sj@kernel.org>
Description:	Writing to and reading from this file sets and gets the maximum
		size of the scheme's target regions in bytes.

What:		/sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/schemes/<S>/access_pattern/nr_accesses/min
Date:		Mar 2022
Contact:	SeongJae Park <sj@kernel.org>
Description:	Writing to and reading from this file sets and gets the manimum
		'nr_accesses' of the scheme's target regions.

What:		/sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/schemes/<S>/access_pattern/nr_accesses/max
Date:		Mar 2022
Contact:	SeongJae Park <sj@kernel.org>
Description:	Writing to and reading from this file sets and gets the maximum
		'nr_accesses' of the scheme's target regions.

What:		/sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/schemes/<S>/access_pattern/age/min
Date:		Mar 2022
Contact:	SeongJae Park <sj@kernel.org>
Description:	Writing to and reading from this file sets and gets the minimum
		'age' of the scheme's target regions.

What:		/sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/schemes/<S>/access_pattern/age/max
Date:		Mar 2022
Contact:	SeongJae Park <sj@kernel.org>
Description:	Writing to and reading from this file sets and gets the maximum
		'age' of the scheme's target regions.

What:		/sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/schemes/<S>/quotas/ms
Date:		Mar 2022
Contact:	SeongJae Park <sj@kernel.org>
Description:	Writing to and reading from this file sets and gets the time
		quota of the scheme in milliseconds.

What:		/sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/schemes/<S>/quotas/bytes
Date:		Mar 2022
Contact:	SeongJae Park <sj@kernel.org>
Description:	Writing to and reading from this file sets and gets the size
		quota of the scheme in bytes.

What:		/sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/schemes/<S>/quotas/reset_interval_ms
Date:		Mar 2022
Contact:	SeongJae Park <sj@kernel.org>
Description:	Writing to and reading from this file sets and gets the quotas
		charge reset interval of the scheme in milliseconds.

What:		/sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/schemes/<S>/quotas/weights/sz_permil
Date:		Mar 2022
Contact:	SeongJae Park <sj@kernel.org>
Description:	Writing to and reading from this file sets and gets the
		under-quota limit regions prioritization weight for 'size' in
		permil.

What:		/sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/schemes/<S>/quotas/weights/nr_accesses_permil
Date:		Mar 2022
Contact:	SeongJae Park <sj@kernel.org>
Description:	Writing to and reading from this file sets and gets the
		under-quota limit regions prioritization weight for
		'nr_accesses' in permil.

What:		/sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/schemes/<S>/quotas/weights/age_permil
Date:		Mar 2022
Contact:	SeongJae Park <sj@kernel.org>
Description:	Writing to and reading from this file sets and gets the
		under-quota limit regions prioritization weight for 'age' in
		permil.

What:		/sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/schemes/<S>/watermarks/metric
Date:		Mar 2022
Contact:	SeongJae Park <sj@kernel.org>
Description:	Writing to and reading from this file sets and gets the metric
		of the watermarks for the scheme.  The writable/readable
		keywords for this file are 'none' for disabling the watermarks
		feature, or 'free_mem_rate' for the system's global free memory
		rate in permil.

What:		/sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/schemes/<S>/watermarks/interval_us
Date:		Mar 2022
Contact:	SeongJae Park <sj@kernel.org>
Description:	Writing to and reading from this file sets and gets the metric
		check interval of the watermarks for the scheme in
		microseconds.

What:		/sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/schemes/<S>/watermarks/high
Date:		Mar 2022
Contact:	SeongJae Park <sj@kernel.org>
Description:	Writing to and reading from this file sets and gets the high
		watermark of the scheme in permil.

What:		/sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/schemes/<S>/watermarks/mid
Date:		Mar 2022
Contact:	SeongJae Park <sj@kernel.org>
Description:	Writing to and reading from this file sets and gets the mid
		watermark of the scheme in permil.

What:		/sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/schemes/<S>/watermarks/low
Date:		Mar 2022
Contact:	SeongJae Park <sj@kernel.org>
Description:	Writing to and reading from this file sets and gets the low
		watermark of the scheme in permil.

What:		/sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/schemes/<S>/stats/nr_tried
Date:		Mar 2022
Contact:	SeongJae Park <sj@kernel.org>
Description:	Reading this file returns the number of regions that the action
		of the scheme has tried to be applied.

What:		/sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/schemes/<S>/stats/sz_tried
Date:		Mar 2022
Contact:	SeongJae Park <sj@kernel.org>
Description:	Reading this file returns the total size of regions that the
		action of the scheme has tried to be applied in bytes.

What:		/sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/schemes/<S>/stats/nr_applied
Date:		Mar 2022
Contact:	SeongJae Park <sj@kernel.org>
Description:	Reading this file returns the number of regions that the action
		of the scheme has successfully applied.

What:		/sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/schemes/<S>/stats/sz_applied
Date:		Mar 2022
Contact:	SeongJae Park <sj@kernel.org>
Description:	Reading this file returns the total size of regions that the
		action of the scheme has successfully applied in bytes.

What:		/sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/schemes/<S>/stats/qt_exceeds
Date:		Mar 2022
Contact:	SeongJae Park <sj@kernel.org>
Description:	Reading this file returns the number of the exceed events of
		the scheme's quotas.

What:		/sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/schemes/<S>/tried_regions/<R>/start
Date:		Oct 2022
Contact:	SeongJae Park <sj@kernel.org>
Description:	Reading this file returns the start address of a memory region
		that corresponding DAMON-based Operation Scheme's action has
		tried to be applied.

What:		/sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/schemes/<S>/tried_regions/<R>/end
Date:		Oct 2022
Contact:	SeongJae Park <sj@kernel.org>
Description:	Reading this file returns the end address of a memory region
		that corresponding DAMON-based Operation Scheme's action has
		tried to be applied.

What:		/sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/schemes/<S>/tried_regions/<R>/nr_accesses
Date:		Oct 2022
Contact:	SeongJae Park <sj@kernel.org>
Description:	Reading this file returns the 'nr_accesses' of a memory region
		that corresponding DAMON-based Operation Scheme's action has
		tried to be applied.

What:		/sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/schemes/<S>/tried_regions/<R>/age
Date:		Oct 2022
Contact:	SeongJae Park <sj@kernel.org>
Description:	Reading this file returns the 'age' of a memory region that
		corresponding DAMON-based Operation Scheme's action has tried
		to be applied.


code:
What:		/sys/kernel/mm/hugepages/
Date:		June 2008
Contact:	Nishanth Aravamudan <nacc@us.ibm.com>, hugetlb maintainers
Description:
		/sys/kernel/mm/hugepages/ contains a number of subdirectories
		of the form hugepages-<size>kB, where <size> is the page size
		of the hugepages supported by the kernel/CPU combination.

		Under these directories are a number of files:

			- nr_hugepages
			- nr_overcommit_hugepages
			- free_hugepages
			- surplus_hugepages
			- resv_hugepages

		See Documentation/admin-guide/mm/hugetlbpage.rst for details.

repo_name: angery/linux


code:
What:		/sys/kernel/mm/ksm
Date:		September 2009
KernelVersion:	2.6.32
Contact:	Linux memory management mailing list <linux-mm@kvack.org>
Description:	Interface for Kernel Samepage Merging (KSM)

What:		/sys/kernel/mm/ksm/full_scans
What:		/sys/kernel/mm/ksm/pages_shared
What:		/sys/kernel/mm/ksm/pages_sharing
What:		/sys/kernel/mm/ksm/pages_to_scan
What:		/sys/kernel/mm/ksm/pages_unshared
What:		/sys/kernel/mm/ksm/pages_volatile
What:		/sys/kernel/mm/ksm/run
What:		/sys/kernel/mm/ksm/sleep_millisecs
Date:		September 2009
Contact:	Linux memory management mailing list <linux-mm@kvack.org>
Description:	Kernel Samepage Merging daemon sysfs interface

		full_scans: how many times all mergeable areas have been
		scanned.

		pages_shared: how many shared pages are being used.

		pages_sharing: how many more sites are sharing them i.e. how
		much saved.

		pages_to_scan: how many present pages to scan before ksmd goes
		to sleep.

		pages_unshared: how many pages unique but repeatedly checked
		for merging.

		pages_volatile: how many pages changing too fast to be placed
		in a tree.

		run: write 0 to disable ksm, read 0 while ksm is disabled.

			- write 1 to run ksm, read 1 while ksm is running.
			- write 2 to disable ksm and unmerge all its pages.

		sleep_millisecs: how many milliseconds ksm should sleep between
		scans.

		See Documentation/mm/ksm.rst for more information.

What:		/sys/kernel/mm/ksm/merge_across_nodes
Date:		January 2013
KernelVersion:	3.9
Contact:	Linux memory management mailing list <linux-mm@kvack.org>
Description:	Control merging pages across different NUMA nodes.

		When it is set to 0 only pages from the same node are merged,
		otherwise pages from all nodes can be merged together (default).


code:
What:		/sys/devices/virtual/memory_tiering/
Date:		August 2022
Contact:	Linux memory management mailing list <linux-mm@kvack.org>
Description:	A collection of all the memory tiers allocated.

		Individual memory tier details are contained in subdirectories
		named by the abstract distance of the memory tier.

		/sys/devices/virtual/memory_tiering/memory_tierN/

What:		/sys/devices/virtual/memory_tiering/memory_tierN/
		/sys/devices/virtual/memory_tiering/memory_tierN/nodelist
Date:		August 2022
Contact:	Linux memory management mailing list <linux-mm@kvack.org>
Description:	Directory with details of a specific memory tier

		This is the directory containing information about a particular
		memory tier, memtierN, where N is derived based on abstract distance.

		A smaller value of N implies a higher (faster) memory tier in the
		hierarchy.

		nodelist: NUMA nodes that are part of this memory tier.


code:
What:		/sys/kernel/mm/numa/
Date:		June 2021
Contact:	Linux memory management mailing list <linux-mm@kvack.org>
Description:	Interface for NUMA

What:		/sys/kernel/mm/numa/demotion_enabled
Date:		June 2021
Contact:	Linux memory management mailing list <linux-mm@kvack.org>
Description:	Enable/disable demoting pages during reclaim

		Page migration during reclaim is intended for systems
		with tiered memory configurations.  These systems have
		multiple types of memory with varied performance
		characteristics instead of plain NUMA systems where
		the same kind of memory is found at varied distances.
		Allowing page migration during reclaim enables these
		systems to migrate pages from fast tiers to slow tiers
		when the fast tier is under pressure.  This migration
		is performed before swap.  It may move data to a NUMA
		node that does not fall into the cpuset of the
		allocating process which might be construed to violate
		the guarantees of cpusets.  This should not be enabled
		on systems which need strict cpuset location
		guarantees.


code:
What:		/sys/kernel/mm/swap/
Date:		August 2017
Contact:	Linux memory management mailing list <linux-mm@kvack.org>
Description:	Interface for swapping

What:		/sys/kernel/mm/swap/vma_ra_enabled
Date:		August 2017
Contact:	Linux memory management mailing list <linux-mm@kvack.org>
Description:	Enable/disable VMA based swap readahead.

		If set to true, the VMA based swap readahead algorithm
		will be used for swappable anonymous pages mapped in a
		VMA, and the global swap readahead algorithm will be
		still used for tmpfs etc. other users.  If set to
		false, the global swap readahead algorithm will be
		used for all swappable pages.


code:
What:		/sys/kernel/oops_count
Date:		November 2022
KernelVersion:	6.2.0
Contact:	Linux Kernel Hardening List <linux-hardening@vger.kernel.org>
Description:
		Shows how many times the system has Oopsed since last boot.


code:
What:		/sys/kernel/reboot
Date:		November 2020
KernelVersion:	5.11
Contact:	Matteo Croce <mcroce@microsoft.com>
Description:	Interface to set the kernel reboot behavior, similarly to
		what can be done via the reboot= cmdline option.
		(see Documentation/admin-guide/kernel-parameters.txt)

What:		/sys/kernel/reboot/mode
Date:		November 2020
KernelVersion:	5.11
Contact:	Matteo Croce <mcroce@microsoft.com>
Description:	Reboot mode. Valid values are: cold warm hard soft gpio

What:		/sys/kernel/reboot/type
Date:		November 2020
KernelVersion:	5.11
Contact:	Matteo Croce <mcroce@microsoft.com>
Description:	Reboot type. Valid values are: bios acpi kbd triple efi pci

What:		/sys/kernel/reboot/cpu
Date:		November 2020
KernelVersion:	5.11
Contact:	Matteo Croce <mcroce@microsoft.com>
Description:	CPU number to use to reboot.

What:		/sys/kernel/reboot/force
Date:		November 2020
KernelVersion:	5.11
Contact:	Matteo Croce <mcroce@microsoft.com>
Description:	Don't wait for any other CPUs on reboot and
		avoid anything that could hang.


code:
What:		/sys/kernel/slab
Date:		May 2007
KernelVersion:	2.6.22
Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
		Christoph Lameter <cl@linux-foundation.org>
Description:
		The /sys/kernel/slab directory contains a snapshot of the
		internal state of the SLUB allocator for each cache.  Certain
		files may be modified to change the behavior of the cache (and
		any cache it aliases, if any).
Users:		kernel memory tuning tools

What:		/sys/kernel/slab/<cache>/aliases
Date:		May 2007
KernelVersion:	2.6.22
Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
		Christoph Lameter <cl@linux-foundation.org>
Description:
		The aliases file is read-only and specifies how many caches
		have merged into this cache.

What:		/sys/kernel/slab/<cache>/align
Date:		May 2007
KernelVersion:	2.6.22
Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
		Christoph Lameter <cl@linux-foundation.org>
Description:
		The align file is read-only and specifies the cache's object
		alignment in bytes.

What:		/sys/kernel/slab/<cache>/alloc_calls
Date:		May 2007
KernelVersion:	2.6.22
Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
		Christoph Lameter <cl@linux-foundation.org>
Description:
		The alloc_calls file is read-only and lists the kernel code
		locations from which allocations for this cache were performed.
		The alloc_calls file only contains information if debugging is
		enabled for that cache (see Documentation/mm/slub.rst).

What:		/sys/kernel/slab/<cache>/alloc_fastpath
Date:		February 2008
KernelVersion:	2.6.25
Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
		Christoph Lameter <cl@linux-foundation.org>
Description:
		The alloc_fastpath file shows how many objects have been
		allocated using the fast path.  It can be written to clear the
		current count.
		Available when CONFIG_SLUB_STATS is enabled.

What:		/sys/kernel/slab/<cache>/alloc_from_partial
Date:		February 2008
KernelVersion:	2.6.25
Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
		Christoph Lameter <cl@linux-foundation.org>
Description:
		The alloc_from_partial file shows how many times a cpu slab has
		been full and it has been refilled by using a slab from the list
		of partially used slabs.  It can be written to clear the current
		count.
		Available when CONFIG_SLUB_STATS is enabled.

What:		/sys/kernel/slab/<cache>/alloc_refill
Date:		February 2008
KernelVersion:	2.6.25
Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
		Christoph Lameter <cl@linux-foundation.org>
Description:
		The alloc_refill file shows how many times the per-cpu freelist
		was empty but there were objects available as the result of
		remote cpu frees.  It can be written to clear the current count.
		Available when CONFIG_SLUB_STATS is enabled.

What:		/sys/kernel/slab/<cache>/alloc_slab
Date:		February 2008
KernelVersion:	2.6.25
Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
		Christoph Lameter <cl@linux-foundation.org>
Description:
		The alloc_slab file is shows how many times a new slab had to
		be allocated from the page allocator.  It can be written to
		clear the current count.
		Available when CONFIG_SLUB_STATS is enabled.

What:		/sys/kernel/slab/<cache>/alloc_slowpath
Date:		February 2008
KernelVersion:	2.6.25
Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
		Christoph Lameter <cl@linux-foundation.org>
Description:
		The alloc_slowpath file shows how many objects have been
		allocated using the slow path because of a refill or
		allocation from a partial or new slab.  It can be written to
		clear the current count.
		Available when CONFIG_SLUB_STATS is enabled.

What:		/sys/kernel/slab/<cache>/cache_dma
Date:		May 2007
KernelVersion:	2.6.22
Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
		Christoph Lameter <cl@linux-foundation.org>
Description:
		The cache_dma file is read-only and specifies whether objects
		are from ZONE_DMA.
		Available when CONFIG_ZONE_DMA is enabled.

What:		/sys/kernel/slab/<cache>/cpu_slabs
Date:		May 2007
KernelVersion:	2.6.22
Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
		Christoph Lameter <cl@linux-foundation.org>
Description:
		The cpu_slabs file is read-only and displays how many cpu slabs
		are active and their NUMA locality.

What:		/sys/kernel/slab/<cache>/cpuslab_flush
Date:		April 2009
KernelVersion:	2.6.31
Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
		Christoph Lameter <cl@linux-foundation.org>
Description:
		The file cpuslab_flush shows how many times a cache's cpu slabs
		have been flushed as the result of destroying or shrinking a
		cache, a cpu going offline, or as the result of forcing an
		allocation from a certain node.  It can be written to clear the
		current count.
		Available when CONFIG_SLUB_STATS is enabled.

What:		/sys/kernel/slab/<cache>/ctor
Date:		May 2007
KernelVersion:	2.6.22
Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
		Christoph Lameter <cl@linux-foundation.org>
Description:
		The ctor file is read-only and specifies the cache's object
		constructor function, which is invoked for each object when a
		new slab is allocated.

What:		/sys/kernel/slab/<cache>/deactivate_empty
Date:		February 2008
KernelVersion:	2.6.25
Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
		Christoph Lameter <cl@linux-foundation.org>
Description:
		The deactivate_empty file shows how many times an empty cpu slab
		was deactivated.  It can be written to clear the current count.
		Available when CONFIG_SLUB_STATS is enabled.

What:		/sys/kernel/slab/<cache>/deactivate_full
Date:		February 2008
KernelVersion:	2.6.25
Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
		Christoph Lameter <cl@linux-foundation.org>
Description:
		The deactivate_full file shows how many times a full cpu slab
		was deactivated.  It can be written to clear the current count.
		Available when CONFIG_SLUB_STATS is enabled.

What:		/sys/kernel/slab/<cache>/deactivate_remote_frees
Date:		February 2008
KernelVersion:	2.6.25
Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
		Christoph Lameter <cl@linux-foundation.org>
Description:
		The deactivate_remote_frees file shows how many times a cpu slab
		has been deactivated and contained free objects that were freed
		remotely.  It can be written to clear the current count.
		Available when CONFIG_SLUB_STATS is enabled.

What:		/sys/kernel/slab/<cache>/deactivate_to_head
Date:		February 2008
KernelVersion:	2.6.25
Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
		Christoph Lameter <cl@linux-foundation.org>
Description:
		The deactivate_to_head file shows how many times a partial cpu
		slab was deactivated and added to the head of its node's partial
		list.  It can be written to clear the current count.
		Available when CONFIG_SLUB_STATS is enabled.

What:		/sys/kernel/slab/<cache>/deactivate_to_tail
Date:		February 2008
KernelVersion:	2.6.25
Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
		Christoph Lameter <cl@linux-foundation.org>
Description:
		The deactivate_to_tail file shows how many times a partial cpu
		slab was deactivated and added to the tail of its node's partial
		list.  It can be written to clear the current count.
		Available when CONFIG_SLUB_STATS is enabled.

What:		/sys/kernel/slab/<cache>/destroy_by_rcu
Date:		May 2007
KernelVersion:	2.6.22
Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
		Christoph Lameter <cl@linux-foundation.org>
Description:
		The destroy_by_rcu file is read-only and specifies whether
		slabs (not objects) are freed by rcu.

What:		/sys/kernel/slab/<cache>/free_add_partial
Date:		February 2008
KernelVersion:	2.6.25
Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
		Christoph Lameter <cl@linux-foundation.org>
Description:
		The free_add_partial file shows how many times an object has
		been freed in a full slab so that it had to added to its node's
		partial list.  It can be written to clear the current count.
		Available when CONFIG_SLUB_STATS is enabled.

What:		/sys/kernel/slab/<cache>/free_calls
Date:		May 2007
KernelVersion:	2.6.22
Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
		Christoph Lameter <cl@linux-foundation.org>
Description:
		The free_calls file is read-only and lists the locations of
		object frees if slab debugging is enabled (see
		Documentation/mm/slub.rst).

What:		/sys/kernel/slab/<cache>/free_fastpath
Date:		February 2008
KernelVersion:	2.6.25
Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
		Christoph Lameter <cl@linux-foundation.org>
Description:
		The free_fastpath file shows how many objects have been freed
		using the fast path because it was an object from the cpu slab.
		It can be written to clear the current count.
		Available when CONFIG_SLUB_STATS is enabled.

What:		/sys/kernel/slab/<cache>/free_frozen
Date:		February 2008
KernelVersion:	2.6.25
Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
		Christoph Lameter <cl@linux-foundation.org>
Description:
		The free_frozen file shows how many objects have been freed to
		a frozen slab (i.e. a remote cpu slab).  It can be written to
		clear the current count.
		Available when CONFIG_SLUB_STATS is enabled.

What:		/sys/kernel/slab/<cache>/free_remove_partial
Date:		February 2008
KernelVersion:	2.6.25
Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
		Christoph Lameter <cl@linux-foundation.org>
Description:
		The free_remove_partial file shows how many times an object has
		been freed to a now-empty slab so that it had to be removed from
		its node's partial list.  It can be written to clear the current
		count.
		Available when CONFIG_SLUB_STATS is enabled.

What:		/sys/kernel/slab/<cache>/free_slab
Date:		February 2008
KernelVersion:	2.6.25
Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
		Christoph Lameter <cl@linux-foundation.org>
Description:
		The free_slab file shows how many times an empty slab has been
		freed back to the page allocator.  It can be written to clear
		the current count.
		Available when CONFIG_SLUB_STATS is enabled.

What:		/sys/kernel/slab/<cache>/free_slowpath
Date:		February 2008
KernelVersion:	2.6.25
Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
		Christoph Lameter <cl@linux-foundation.org>
Description:
		The free_slowpath file shows how many objects have been freed
		using the slow path (i.e. to a full or partial slab).  It can
		be written to clear the current count.
		Available when CONFIG_SLUB_STATS is enabled.

What:		/sys/kernel/slab/<cache>/hwcache_align
Date:		May 2007
KernelVersion:	2.6.22
Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
		Christoph Lameter <cl@linux-foundation.org>
Description:
		The hwcache_align file is read-only and specifies whether
		objects are aligned on cachelines.

What:		/sys/kernel/slab/<cache>/min_partial
Date:		February 2009
KernelVersion:	2.6.30
Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
		David Rientjes <rientjes@google.com>
Description:
		The min_partial file specifies how many empty slabs shall
		remain on a node's partial list to avoid the overhead of
		allocating new slabs.  Such slabs may be reclaimed by utilizing
		the shrink file.

What:		/sys/kernel/slab/<cache>/object_size
Date:		May 2007
KernelVersion:	2.6.22
Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
		Christoph Lameter <cl@linux-foundation.org>
Description:
		The object_size file is read-only and specifies the cache's
		object size.

What:		/sys/kernel/slab/<cache>/objects
Date:		May 2007
KernelVersion:	2.6.22
Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
		Christoph Lameter <cl@linux-foundation.org>
Description:
		The objects file is read-only and displays how many objects are
		active and from which nodes they are from.

What:		/sys/kernel/slab/<cache>/objects_partial
Date:		April 2008
KernelVersion:	2.6.26
Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
		Christoph Lameter <cl@linux-foundation.org>
Description:
		The objects_partial file is read-only and displays how many
		objects are on partial slabs and from which nodes they are
		from.

What:		/sys/kernel/slab/<cache>/objs_per_slab
Date:		May 2007
KernelVersion:	2.6.22
Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
		Christoph Lameter <cl@linux-foundation.org>
Description:
		The file objs_per_slab is read-only and specifies how many
		objects may be allocated from a single slab of the order
		specified in /sys/kernel/slab/<cache>/order.

What:		/sys/kernel/slab/<cache>/order
Date:		May 2007
KernelVersion:	2.6.22
Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
		Christoph Lameter <cl@linux-foundation.org>
Description:
		The order file specifies the page order at which new slabs are
		allocated.  It is writable and can be changed to increase the
		number of objects per slab.  If a slab cannot be allocated
		because of fragmentation, SLUB will retry with the minimum order
		possible depending on its characteristics.

		When debug_guardpage_minorder=N (N > 0) parameter is specified
		(see Documentation/admin-guide/kernel-parameters.rst), the minimum possible
		order is used and this sysfs entry can not be used to change
		the order at run time.

What:		/sys/kernel/slab/<cache>/order_fallback
Date:		April 2008
KernelVersion:	2.6.26
Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
		Christoph Lameter <cl@linux-foundation.org>
Description:
		The order_fallback file shows how many times an allocation of a
		new slab has not been possible at the cache's order and instead
		fallen back to its minimum possible order.  It can be written to
		clear the current count.

		Available when CONFIG_SLUB_STATS is enabled.

What:		/sys/kernel/slab/<cache>/partial
Date:		May 2007
KernelVersion:	2.6.22
Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
		Christoph Lameter <cl@linux-foundation.org>
Description:
		The partial file is read-only and displays how long many
		partial slabs there are and how long each node's list is.

What:		/sys/kernel/slab/<cache>/poison
Date:		May 2007
KernelVersion:	2.6.22
Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
		Christoph Lameter <cl@linux-foundation.org>
Description:
		The poison file specifies whether objects should be poisoned
		when a new slab is allocated.

What:		/sys/kernel/slab/<cache>/reclaim_account
Date:		May 2007
KernelVersion:	2.6.22
Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
		Christoph Lameter <cl@linux-foundation.org>
Description:
		The reclaim_account file specifies whether the cache's objects
		are reclaimable (and grouped by their mobility).

What:		/sys/kernel/slab/<cache>/red_zone
Date:		May 2007
KernelVersion:	2.6.22
Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
		Christoph Lameter <cl@linux-foundation.org>
Description:
		The red_zone file specifies whether the cache's objects are red
		zoned.

What:		/sys/kernel/slab/<cache>/remote_node_defrag_ratio
Date:		January 2008
KernelVersion:	2.6.25
Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
		Christoph Lameter <cl@linux-foundation.org>
Description:
		The file remote_node_defrag_ratio specifies the percentage of
		times SLUB will attempt to refill the cpu slab with a partial
		slab from a remote node as opposed to allocating a new slab on
		the local node.  This reduces the amount of wasted memory over
		the entire system but can be expensive.

		Available when CONFIG_NUMA is enabled.

What:		/sys/kernel/slab/<cache>/sanity_checks
Date:		May 2007
KernelVersion:	2.6.22
Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
		Christoph Lameter <cl@linux-foundation.org>
Description:
		The sanity_checks file specifies whether expensive checks
		should be performed on free and, at minimum, enables double free
		checks.  Caches that enable sanity_checks cannot be merged with
		caches that do not.

What:		/sys/kernel/slab/<cache>/shrink
Date:		May 2007
KernelVersion:	2.6.22
Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
		Christoph Lameter <cl@linux-foundation.org>
Description:
		The shrink file is used to reclaim unused slab cache
		memory from a cache.  Empty per-cpu or partial slabs
		are freed and the partial list is sorted so the slabs
		with the fewest available objects are used first.
		It only accepts a value of "1" on write for shrinking
		the cache. Other input values are considered invalid.
		Shrinking slab caches might be expensive and can
		adversely impact other running applications.  So it
		should be used with care.

What:		/sys/kernel/slab/<cache>/slab_size
Date:		May 2007
KernelVersion:	2.6.22
Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
		Christoph Lameter <cl@linux-foundation.org>
Description:
		The slab_size file is read-only and specifies the object size
		with metadata (debugging information and alignment) in bytes.

What:		/sys/kernel/slab/<cache>/slabs
Date:		May 2007
KernelVersion:	2.6.22
Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
		Christoph Lameter <cl@linux-foundation.org>
Description:
		The slabs file is read-only and displays how long many slabs
		there are (both cpu and partial) and from which nodes they are
		from.

What:		/sys/kernel/slab/<cache>/store_user
Date:		May 2007
KernelVersion:	2.6.22
Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
		Christoph Lameter <cl@linux-foundation.org>
Description:
		The store_user file specifies whether the location of
		allocation or free should be tracked for a cache.

What:		/sys/kernel/slab/<cache>/total_objects
Date:		April 2008
KernelVersion:	2.6.26
Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
		Christoph Lameter <cl@linux-foundation.org>
Description:
		The total_objects file is read-only and displays how many total
		objects a cache has and from which nodes they are from.

What:		/sys/kernel/slab/<cache>/trace
Date:		May 2007
KernelVersion:	2.6.22
Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
		Christoph Lameter <cl@linux-foundation.org>
Description:
		The trace file specifies whether object allocations and frees
		should be traced.

What:		/sys/kernel/slab/<cache>/validate
Date:		May 2007
KernelVersion:	2.6.22
Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
		Christoph Lameter <cl@linux-foundation.org>
Description:
		Writing to the validate file causes SLUB to traverse all of its
		cache's objects and check the validity of metadata.

What:		/sys/kernel/slab/<cache>/usersize
Date:		Jun 2017
Contact:	David Windsor <dave@nullcore.net>
Description:
		The usersize file is read-only and contains the usercopy
		region size.

What:		/sys/kernel/slab/<cache>/slabs_cpu_partial
Date:		Aug 2011
Contact:	Christoph Lameter <cl@linux.com>
Description:
		This read-only file shows the number of partialli allocated
		frozen slabs.

What:		/sys/kernel/slab/<cache>/cpu_partial
Date:		Aug 2011
Contact:	Christoph Lameter <cl@linux.com>
Description:
		This read-only file shows the number of per cpu partial
		pages to keep around.


code:
What:		/sys/kernel/vmcoreinfo
Date:		October 2007
KernelVersion:	2.6.24
Contact:	Ken'ichi Ohmichi <oomichi@mxs.nes.nec.co.jp>
		Kexec Mailing List <kexec@lists.infradead.org>
		Vivek Goyal <vgoyal@redhat.com>
Description:
		Shows physical address and size of vmcoreinfo ELF note.
		First value contains physical address of note in hex and
		second value contains the size of note in hex. This ELF
		note info is parsed by second kernel and exported to user
		space as part of ELF note in /proc/vmcore file. This note
		contains various information like struct size, symbol
		values, page size etc.


code:
What:		/sys/kernel/oops_count
Date:		November 2022
KernelVersion:	6.2.0
Contact:	Linux Kernel Hardening List <linux-hardening@vger.kernel.org>
Description:
		Shows how many times the system has Warned since last boot.


code:
What:		/sys/devices/system/machinecheck/machinecheckX/
Contact:	Andi Kleen <ak@linux.intel.com>
Date:		Feb, 2007
Description:
		(X = CPU number)

		Machine checks report internal hardware error conditions
		detected by the CPU. Uncorrected errors typically cause a
		machine check (often with panic), corrected ones cause a
		machine check log entry.

		For more details about the x86 machine check architecture
		see the Intel and AMD architecture manuals from their
		developer websites.

		For more details about the architecture
		see http://one.firstfloor.org/~andi/mce.pdf

		Each CPU has its own directory.

What:		/sys/devices/system/machinecheck/machinecheckX/bank<Y>
Contact:	Andi Kleen <ak@linux.intel.com>
Date:		Feb, 2007
Description:
		(Y bank number)

		64bit Hex bitmask enabling/disabling specific subevents for
		bank Y.

		When a bit in the bitmask is zero then the respective
		subevent will not be reported.

		By default all events are enabled.

		Note that BIOS maintain another mask to disable specific events
		per bank.  This is not visible here

What:		/sys/devices/system/machinecheck/machinecheckX/check_interval
Contact:	Andi Kleen <ak@linux.intel.com>
Date:		Feb, 2007
Description:
		The entries appear for each CPU, but they are truly shared
		between all CPUs.

		How often to poll for corrected machine check errors, in
		seconds (Note output is hexadecimal). Default 5 minutes.
		When the poller finds MCEs it triggers an exponential speedup
		(poll more often) on the polling interval.  When the poller
		stops finding MCEs, it triggers an exponential backoff
		(poll less often) on the polling interval. The check_interval
		variable is both the initial and maximum polling interval.
		0 means no polling for corrected machine check errors
		(but some corrected errors might be still reported
		in other ways)

What:		/sys/devices/system/machinecheck/machinecheckX/trigger
Contact:	Andi Kleen <ak@linux.intel.com>
Date:		Feb, 2007
Description:
		The entries appear for each CPU, but they are truly shared
		between all CPUs.

		Program to run when a machine check event is detected.
		This is an alternative to running mcelog regularly from cron
		and allows to detect events faster.

What:		/sys/devices/system/machinecheck/machinecheckX/monarch_timeout
Contact:	Andi Kleen <ak@linux.intel.com>
Date:		Feb, 2007
Description:
		How long to wait for the other CPUs to machine check too on a
		exception. 0 to disable waiting for other CPUs.

		Unit: us

What:		/sys/devices/system/machinecheck/machinecheckX/ignore_ce
Contact:	Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
Date:		Jun 2009
Description:
		Disables polling and CMCI for corrected errors.
		All corrected events are not cleared and kept in bank MSRs.

What:		/sys/devices/system/machinecheck/machinecheckX/dont_log_ce
Contact:	Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
Date:		Jun 2009
Description:
		Disables logging for corrected errors.
		All reported corrected errors will be cleared silently.

		This option will be useful if you never care about corrected
		errors.

What:		/sys/devices/system/machinecheck/machinecheckX/cmci_disabled
Contact:	Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
Date:		Jun 2009
Description:
		Disables the CMCI feature.

path: Documentation/ABI/testing/sysfs-mce


code:
What:		/sys/devices/system/memory/soft_offline_page
Date:		Sep 2009
KernelVersion:	2.6.33
Contact:	andi@firstfloor.org
Description:
		Soft-offline the memory page containing the physical address
		written into this file. Input is a hex number specifying the
		physical address of the page. The kernel will then attempt
		to soft-offline it, by moving the contents elsewhere or
		dropping it if possible. The kernel will then be placed
		on the bad page list and never be reused.

		The offlining is done in kernel specific granuality.
		Normally it's the base page size of the kernel, but
		this might change.

		The page must be still accessible, not poisoned. The
		kernel will never kill anything for this, but rather
		fail the offline.  Return value is the size of the
		number, or a error when the offlining failed.  Reading
		the file is not allowed.

What:		/sys/devices/system/memory/hard_offline_page
Date:		Sep 2009
KernelVersion:	2.6.33
Contact:	andi@firstfloor.org
Description:
		Hard-offline the memory page containing the physical
		address written into this file. Input is a hex number
		specifying the physical address of the page. The
		kernel will then attempt to hard-offline the page, by
		trying to drop the page or killing any owner or
		triggering IO errors if needed.  Note this may kill
		any processes owning the page. The kernel will avoid
		to access this page assuming it's poisoned by the
		hardware.

		The offlining is done in kernel specific granuality.
		Normally it's the base page size of the kernel, but
		this might change.

		Return value is the size of the number, or a error when
		the offlining failed.
		Reading the file is not allowed.


code:
What:		/sys/module/pch_phub/drivers/.../pch_mac
Date:		August 2010
KernelVersion:	2.6.35
Contact:	masa-korg@dsn.okisemi.com
Description:	Write/read GbE MAC address.

What:		/sys/module/pch_phub/drivers/.../pch_firmware
Date:		August 2010
KernelVersion:	2.6.35
Contact:	masa-korg@dsn.okisemi.com
Description:	Write/read Option ROM data.

What:		/sys/module/ehci_hcd/drivers/.../uframe_periodic_max
Date:		July 2011
KernelVersion:	3.1
Contact:	Kirill Smelkov <kirr@mns.spb.ru>
Description:	Maximum time allowed for periodic transfers per microframe (μs)

		Note:
		  USB 2.0 sets maximum allowed time for periodic transfers per
		  microframe to be 80%, that is 100 microseconds out of 125
		  microseconds (full microframe).

		  However there are cases, when 80% max isochronous bandwidth is
		  too limiting. For example two video streams could require 110
		  microseconds of isochronous bandwidth per microframe to work
		  together.

		Through this setting it is possible to raise the limit so that
		the host controller would allow allocating more than 100
		microseconds of periodic bandwidth per microframe.

		Beware, non-standard modes are usually not thoroughly tested by
		hardware designers, and the hardware can malfunction when this
		setting differ from default 100.

What:		/sys/module/*/{coresize,initsize}
Date:		Jan 2012
KernelVersion:	3.3
Contact:	Kay Sievers <kay.sievers@vrfy.org>
Description:	Module size in bytes.

What:		/sys/module/*/initstate
Date:		Nov 2006
KernelVersion:	2.6.19
Contact:	Kay Sievers <kay.sievers@vrfy.org>
Description:	Show the initialization state(live, coming, going) of
		the module.

What:		/sys/module/*/taint
Date:		Jan 2012
KernelVersion:	3.3
Contact:	Kay Sievers <kay.sievers@vrfy.org>
Description:	Module taint flags:
			==  =====================
			P   proprietary module
			O   out-of-tree module
			F   force-loaded module
			C   staging driver module
			E   unsigned module
			==  =====================

path: Documentation/ABI/testing/sysfs-module


code:
What:		/sys/fs/ocfs2/
Date:		April 2008
Contact:	ocfs2-devel@oss.oracle.com
Description:
		The /sys/fs/ocfs2 directory contains knobs used by the
		ocfs2-tools to interact with the filesystem.

What:		/sys/fs/ocfs2/max_locking_protocol
Date:		April 2008
Contact:	ocfs2-devel@oss.oracle.com
Description:
		The /sys/fs/ocfs2/max_locking_protocol file displays version
		of ocfs2 locking supported by the filesystem.  This version
		covers how ocfs2 uses distributed locking between cluster
		nodes.

		The protocol version has a major and minor number.  Two
		cluster nodes can interoperate if they have an identical
		major number and an overlapping minor number - thus,
		a node with version 1.10 can interoperate with a node
		sporting version 1.8, as long as both use the 1.8 protocol.

		Reading from this file returns a single line, the major
		number and minor number joined by a period, eg "1.10".

		This file is read-only.  The value is compiled into the
		driver.

What:		/sys/fs/ocfs2/loaded_cluster_plugins
Date:		April 2008
Contact:	ocfs2-devel@oss.oracle.com
Description:
		The /sys/fs/ocfs2/loaded_cluster_plugins file describes
		the available plugins to support ocfs2 cluster operation.
		A cluster plugin is required to use ocfs2 in a cluster.
		There are currently two available plugins:

		* 'o2cb' - The classic o2cb cluster stack that ocfs2 has
			used since its inception.
		* 'user' - A plugin supporting userspace cluster software
			in conjunction with fs/dlm.

		Reading from this file returns the names of all loaded
		plugins, one per line.

		This file is read-only.  Its contents may change as
		plugins are loaded or removed.

What:		/sys/fs/ocfs2/active_cluster_plugin
Date:		April 2008
Contact:	ocfs2-devel@oss.oracle.com
Description:
		The /sys/fs/ocfs2/active_cluster_plugin displays which
		cluster plugin is currently in use by the filesystem.
		The active plugin will appear in the loaded_cluster_plugins
		file as well.  Only one plugin can be used at a time.

		Reading from this file returns the name of the active plugin
		on a single line.

		This file is read-only.  Which plugin is active depends on
		the cluster stack in use.  The contents may change
		when all filesystems are unmounted and the cluster stack
		is changed.

What:		/sys/fs/ocfs2/cluster_stack
Date:		April 2008
Contact:	ocfs2-devel@oss.oracle.com
Description:
		The /sys/fs/ocfs2/cluster_stack file contains the name
		of current ocfs2 cluster stack.  This value is set by
		userspace tools when bringing the cluster stack online.

		Cluster stack names are 4 characters in length.

		When the 'o2cb' cluster stack is used, the 'o2cb' cluster
		plugin is active.  All other cluster stacks use the 'user'
		cluster plugin.

		Reading from this file returns the name of the current
		cluster stack on a single line.

		Writing a new stack name to this file changes the current
		cluster stack unless there are mounted ocfs2 filesystems.
		If there are mounted filesystems, attempts to change the
		stack return an error.

Users:
	ocfs2-tools <ocfs2-tools-devel@oss.oracle.com>


code:
What:		/sys/devices/platform/asus_laptop/display
Date:		January 2007
KernelVersion:	2.6.20
Contact:	"Corentin Chary" <corentincj@iksaif.net>
Description:
		This file allows display switching. The value
		is composed by 4 bits and defined as follow::

		  4321
		  |||`- LCD
		  ||`-- CRT
		  |`--- TV
		  `---- DVI

		Ex:
		    - 0 (0000b) means no display
		    - 3 (0011b) CRT+LCD.

What:		/sys/devices/platform/asus_laptop/gps
Date:		January 2007
KernelVersion:	2.6.20
Contact:	"Corentin Chary" <corentincj@iksaif.net>
Description:
		Control the gps device. 1 means on, 0 means off.
Users:		Lapsus

What:		/sys/devices/platform/asus_laptop/ledd
Date:		January 2007
KernelVersion:	2.6.20
Contact:	"Corentin Chary" <corentincj@iksaif.net>
Description:
		Some models like the W1N have a LED display that can be
		used to display several items of information.
		To control the LED display, use the following::

		    echo 0x0T000DDD > /sys/devices/platform/asus_laptop/

		where T control the 3 letters display, and DDD the 3 digits display.
		The DDD table can be found in Documentation/admin-guide/laptops/asus-laptop.rst

What:		/sys/devices/platform/asus_laptop/bluetooth
Date:		January 2007
KernelVersion:	2.6.20
Contact:	"Corentin Chary" <corentincj@iksaif.net>
Description:
		Control the bluetooth device. 1 means on, 0 means off.
		This may control the led, the device or both.
Users:		Lapsus

What:		/sys/devices/platform/asus_laptop/wlan
Date:		January 2007
KernelVersion:	2.6.20
Contact:	"Corentin Chary" <corentincj@iksaif.net>
Description:
		Control the wlan device. 1 means on, 0 means off.
		This may control the led, the device or both.
Users:		Lapsus

What:		/sys/devices/platform/asus_laptop/wimax
Date:		October 2010
KernelVersion:	2.6.37
Contact:	"Corentin Chary" <corentincj@iksaif.net>
Description:
		Control the wimax device. 1 means on, 0 means off.

What:		/sys/devices/platform/asus_laptop/wwan
Date:		October 2010
KernelVersion:	2.6.37
Contact:	"Corentin Chary" <corentincj@iksaif.net>
Description:
		Control the wwan (3G) device. 1 means on, 0 means off.


code:
What:		/sys/devices/platform/<platform>/cpufv
Date:		Oct 2010
KernelVersion:	2.6.37
Contact:	"Corentin Chary" <corentincj@iksaif.net>
Description:
		Change CPU clock configuration (write-only).
		There are three available clock configuration:

		    * 0 -> Super Performance Mode
		    * 1 -> High Performance Mode
		    * 2 -> Power Saving Mode

What:		/sys/devices/platform/<platform>/camera
Date:		Jan 2010
KernelVersion:	2.6.39
Contact:	"Corentin Chary" <corentincj@iksaif.net>
Description:
		Control the camera. 1 means on, 0 means off.

What:		/sys/devices/platform/<platform>/cardr
Date:		Jan 2010
KernelVersion:	2.6.39
Contact:	"Corentin Chary" <corentincj@iksaif.net>
Description:
		Control the card reader. 1 means on, 0 means off.

What:		/sys/devices/platform/<platform>/touchpad
Date:		Jan 2010
KernelVersion:	2.6.39
Contact:	"Corentin Chary" <corentincj@iksaif.net>
Description:
		Control the card touchpad. 1 means on, 0 means off.

What:		/sys/devices/platform/<platform>/lid_resume
Date:		May 2012
KernelVersion:	3.5
Contact:	"AceLan Kao" <acelan.kao@canonical.com>
Description:
		Resume on lid open. 1 means on, 0 means off.

What:		/sys/devices/platform/<platform>/fan_boost_mode
Date:		Sep 2019
KernelVersion:	5.3
Contact:	"Yurii Pavlovskyi" <yurii.pavlovskyi@gmail.com>
Description:
		Fan boost mode:
			* 0 - normal,
			* 1 - overboost,
			* 2 - silent

What:		/sys/devices/platform/<platform>/throttle_thermal_policy
Date:		Dec 2019
KernelVersion:	5.6
Contact:	"Leonid Maksymchuk" <leonmaxx@gmail.com>
Description:
		Throttle thermal policy mode:
			* 0 - default,
			* 1 - overboost,
			* 2 - silent

What:		/sys/devices/platform/<platform>/gpu_mux_mode
Date:		Aug 2022
KernelVersion:	6.1
Contact:	"Luke Jones" <luke@ljones.dev>
Description:
		Switch the GPU hardware MUX mode. Laptops with this feature can
		can be toggled to boot with only the dGPU (discrete mode) or in
		standard Optimus/Hybrid mode. On switch a reboot is required:

			* 0 - Discrete GPU,
			* 1 - Optimus/Hybrid,

What:		/sys/devices/platform/<platform>/dgpu_disable
Date:		Aug 2022
KernelVersion:	5.17
Contact:	"Luke Jones" <luke@ljones.dev>
Description:
		Disable discrete GPU:
			* 0 - Enable dGPU,
			* 1 - Disable dGPU

What:		/sys/devices/platform/<platform>/egpu_enable
Date:		Aug 2022
KernelVersion:	5.17
Contact:	"Luke Jones" <luke@ljones.dev>
Description:
		Enable the external GPU paired with ROG X-Flow laptops.
		Toggling this setting will also trigger ACPI to disable the dGPU:

			* 0 - Disable,
			* 1 - Enable

What:		/sys/devices/platform/<platform>/panel_od
Date:		Aug 2022
KernelVersion:	5.17
Contact:	"Luke Jones" <luke@ljones.dev>
Description:
		Enable an LCD response-time boost to reduce or remove ghosting:
			* 0 - Disable,
			* 1 - Enable


code:
What:		/sys/devices/platform/at91_can/net/<iface>/mb0_id
Date:		January 2011
KernelVersion:	2.6.38
Contact:	Marc Kleine-Budde <kernel@pengutronix.de>
Description:
		Value representing the can_id of mailbox 0.

		Default: 0x7ff (standard frame)

		Due to a chip bug (errata 50.2.6.3 & 50.3.5.3 in
		"AT91SAM9263 Preliminary 6249H-ATARM-27-Jul-09") the
		contents of mailbox 0 may be send under certain
		conditions (even if disabled or in rx mode).

		The workaround in the errata suggests not to use the
		mailbox and load it with an unused identifier.

		In order to use an extended can_id add the
		CAN_EFF_FLAG (0x80000000U) to the can_id. Example:

		- standard id 0x7ff::

		    echo 0x7ff      > /sys/class/net/can0/mb0_id

		- extended id 0x1fffffff::

		    echo 0x9fffffff > /sys/class/net/can0/mb0_id


code:
What:		/sys/devices/../../gisb_arb_timeout
Date:		May 2014
KernelVersion:	3.17
Contact:	Florian Fainelli <f.fainelli@gmail.com>
Description:
		Returns the currently configured raw timeout value of the
		Broadcom Set Top Box internal GISB bus arbiter. Minimum value
		is 1, and maximum value is 0xffffffff.


code:
What:		/sys/bus/platform/devices/*/srpd
Date:		July 2022
KernelVersion:	5.21
Contact:	Florian Fainelli <f.fainelli@gmail.com>
Description:
		Self Refresh Power Down (SRPD) inactivity timeout counted in
		internal DDR controller clock cycles. Possible values range
		from 0 (disable inactivity timeout) to 65535 (0xffff).

What:		/sys/bus/platform/devices/*/frequency
Date:		July 2022
KernelVersion:	5.21
Contact:	Florian Fainelli <f.fainelli@gmail.com>
Description:
		DDR PHY frequency in Hz.


code:
What:		/sys/bus/platform/devices/ci_hdrc.0/inputs/a_bus_req
Date:		Feb 2014
Contact:	Li Jun <jun.li@nxp.com>
Description:
		Can be set and read.
		Set a_bus_req(A-device bus request) input to be 1 if
		the application running on the A-device wants to use the bus,
		and to be 0 when the application no longer wants to use
		the bus(or wants to work as peripheral). a_bus_req can also
		be set to 1 by kernel in response to remote wakeup signaling
		from the B-device, the A-device should decide to resume the bus.

		Valid values are "1" and "0".

		Reading: returns 1 if the application running on the A-device
		is using the bus as host role, otherwise 0.

What:		/sys/bus/platform/devices/ci_hdrc.0/inputs/a_bus_drop
Date:		Feb 2014
Contact:	Li Jun <jun.li@nxp.com>
Description:
		Can be set and read
		The a_bus_drop(A-device bus drop) input is 1 when the
		application running on the A-device wants to power down
		the bus, and is 0 otherwise, When a_bus_drop is 1, then
		the a_bus_req shall be 0.

		Valid values are "1" and "0".

		Reading: returns 1 if the bus is off(vbus is turned off) by
			 A-device, otherwise 0.

What:		/sys/bus/platform/devices/ci_hdrc.0/inputs/b_bus_req
Date:		Feb 2014
Contact:	Li Jun <jun.li@nxp.com>
Description:
		Can be set and read.
		The b_bus_req(B-device bus request) input is 1 during the time
		that the application running on the B-device wants to use the
		bus as host, and is 0 when the application no longer wants to
		work as host and decides to switch back to be peripheral.

		Valid values are "1" and "0".

		Reading: returns if the application running on the B device
		is using the bus as host role, otherwise 0.

What:		/sys/bus/platform/devices/ci_hdrc.0/inputs/a_clr_err
Date:		Feb 2014
Contact:	Li Jun <jun.li@nxp.com>
Description:
		Only can be set.
		The a_clr_err(A-device Vbus error clear) input is used to clear
		vbus error, then A-device will power down the bus.

		Valid value is "1"


code:
What:		/sys/bus/platform/devices/ci_hdrc.0/role
Date:		Mar 2017
Contact:	Peter Chen <peter.chen@nxp.com>
Description:
		When read, it returns string "gadget" or "host", indicating
		the current controller role.

		It will do role switch when "gadget" or "host" is written to it.
		Only controller at dual-role configuration supports writing.


code:
What:		/sys/class/leds/dell::kbd_backlight/als_enabled
Date:		December 2014
KernelVersion:	3.19
Contact:	Gabriele Mazzotta <gabriele.mzt@gmail.com>,
		Pali Rohár <pali@kernel.org>
Description:
		This file allows to control the automatic keyboard
		illumination mode on some systems that have an ambient
		light sensor. Write 1 to this file to enable the auto
		mode, 0 to disable it.

What:		/sys/class/leds/dell::kbd_backlight/als_setting
Date:		December 2014
KernelVersion:	3.19
Contact:	Gabriele Mazzotta <gabriele.mzt@gmail.com>,
		Pali Rohár <pali@kernel.org>
Description:
		This file allows to specifiy the on/off threshold value,
		as reported by the ambient light sensor.

What:		/sys/class/leds/dell::kbd_backlight/start_triggers
Date:		December 2014
KernelVersion:	3.19
Contact:	Gabriele Mazzotta <gabriele.mzt@gmail.com>,
		Pali Rohár <pali@kernel.org>
Description:
		This file allows to control the input triggers that
		turn on the keyboard backlight illumination that is
		disabled because of inactivity.
		Read the file to see the triggers available. The ones
		enabled are preceded by '+', those disabled by '-'.

		To enable a trigger, write its name preceded by '+' to
		this file. To disable a trigger, write its name preceded
		by '-' instead.

		For example, to enable the keyboard as trigger run::

		    echo +keyboard > /sys/class/leds/dell::kbd_backlight/start_triggers

		To disable it::

		    echo -keyboard > /sys/class/leds/dell::kbd_backlight/start_triggers

		Note that not all the available triggers can be configured.

What:		/sys/class/leds/dell::kbd_backlight/stop_timeout
Date:		December 2014
KernelVersion:	3.19
Contact:	Gabriele Mazzotta <gabriele.mzt@gmail.com>,
		Pali Rohár <pali@kernel.org>
Description:
		This file allows to specify the interval after which the
		keyboard illumination is disabled because of inactivity.
		The timeouts are expressed in seconds, minutes, hours and
		days, for which the symbols are 's', 'm', 'h' and 'd'
		respectively.

		To configure the timeout, write to this file a value along
		with any the above units. If no unit is specified, the value
		is assumed to be expressed in seconds.

		For example, to set the timeout to 10 minutes run::

		    echo 10m > /sys/class/leds/dell::kbd_backlight/stop_timeout

		Note that when this file is read, the returned value might be
		expressed in a different unit than the one used when the timeout
		was set.

		Also note that only some timeouts are supported and that
		some systems might fall back to a specific timeout in case
		an invalid timeout is written to this file.


code:
What:		/sys/bus/wmi/devices/6932965F-1671-4CEB-B988-D3AB0A901919/dell_privacy_supported_type
Date:		Apr 2021
KernelVersion:	5.13
Contact:	"<perry.yuan@dell.com>"
Description:
		Display which dell hardware level privacy devices are supported
		“Dell Privacy” is a set of HW, FW, and SW features to enhance
		Dell’s commitment to platform privacy for MIC, Camera, and
		ePrivacy screens.
		The supported hardware privacy devices are:

		Attributes:
			Microphone Mute:
				Identifies the local microphone can be muted by hardware, no applications
				is available to capture system mic sound

			Camera Shutter:
				Identifies camera shutter controlled by hardware, which is a micromechanical
				shutter assembly that is built onto the camera module to block capturing images
				from outside the laptop

		Values:

			supported:
				The privacy device is supported by this system

			unsupported:
				The privacy device is not supported on this system

		For example to check which privacy devices are supported::

		    # cat /sys/bus/wmi/drivers/dell-privacy/6932965F-1671-4CEB-B988-D3AB0A901919/dell_privacy_supported_type
		    [Microphone Mute] [supported]
		    [Camera Shutter] [supported]
		    [ePrivacy Screen] [unsupported]

What:		/sys/bus/wmi/devices/6932965F-1671-4CEB-B988-D3AB0A901919/dell_privacy_current_state
Date:		Apr 2021
KernelVersion:	5.13
Contact:	"<perry.yuan@dell.com>"
Description:
		Allow user space to check current dell privacy device state.
		Describes the Device State class exposed by BIOS which can be
		consumed by various applications interested in knowing the Privacy
		feature capabilities

		Attributes:
			Microphone:
				Identifies the local microphone can be muted by hardware, no applications
				is available to capture system mic sound

			Camera Shutter:
				Identifies camera shutter controlled by hardware, which is a micromechanical
				shutter assembly that is built onto the camera module to block capturing images
				from outside the laptop

		Values:
			muted:
				Identifies the privacy device is turned off
				and cannot send stream to OS applications

			unmuted:
				Identifies the privacy device is turned on,
				audio or camera driver can get stream from mic
				and camera module to OS applications

		For example to check all supported current privacy device states::

		    # cat /sys/bus/wmi/drivers/dell-privacy/6932965F-1671-4CEB-B988-D3AB0A901919/dell_privacy_current_state
		    [Microphone] [unmuted]
		    [Camera Shutter] [unmuted]


code:
What:		/sys/devices/platform/<platform>/tokens/*
Date:		November 2017
KernelVersion:	4.15
Contact:	Dell.Client.Kernel@dell.com
Description:
		A read-only description of Dell platform tokens
		available on the machine.

		Each token attribute is available as a pair of
		sysfs attributes readable by a process with
		CAP_SYS_ADMIN.

		For example the token ID "5" would be available
		as the following attributes:

		- 0005_location
		- 0005_value

		Tokens will vary from machine to machine, and
		only tokens available on that machine will be
		displayed.


code:
What:		/sys/class/power_supply/<battery_name>/eppid
Date:		September 2022
KernelVersion:	6.1
Contact:	Armin Wolf <W_Armin@gmx.de>
Description:
		Reports the Dell ePPID (electronic Dell Piece Part Identification)
		of the ACPI battery.


code:
What:		/sys/bus/platform/devices/dfl-fme.0/ports_num
Date:		June 2018
KernelVersion:  4.19
Contact:	Wu Hao <hao.wu@intel.com>
Description:	Read-only. One DFL FPGA device may have more than 1
		port/Accelerator Function Unit (AFU). It returns the
		number of ports on the FPGA device when read it.

What:		/sys/bus/platform/devices/dfl-fme.0/bitstream_id
Date:		June 2018
KernelVersion:  4.19
Contact:	Wu Hao <hao.wu@intel.com>
Description:	Read-only. It returns Bitstream (static FPGA region)
		identifier number, which includes the detailed version
		and other information of this static FPGA region.

What:		/sys/bus/platform/devices/dfl-fme.0/bitstream_metadata
Date:		June 2018
KernelVersion:  4.19
Contact:	Wu Hao <hao.wu@intel.com>
Description:	Read-only. It returns Bitstream (static FPGA region) meta
		data, which includes the synthesis date, seed and other
		information of this static FPGA region.

What:		/sys/bus/platform/devices/dfl-fme.0/cache_size
Date:		August 2019
KernelVersion:  5.4
Contact:	Wu Hao <hao.wu@intel.com>
Description:	Read-only. It returns cache size of this FPGA device.

What:		/sys/bus/platform/devices/dfl-fme.0/fabric_version
Date:		August 2019
KernelVersion:  5.4
Contact:	Wu Hao <hao.wu@intel.com>
Description:	Read-only. It returns fabric version of this FPGA device.
		Userspace applications need this information to select
		best data channels per different fabric design.

What:		/sys/bus/platform/devices/dfl-fme.0/socket_id
Date:		August 2019
KernelVersion:  5.4
Contact:	Wu Hao <hao.wu@intel.com>
Description:	Read-only. It returns socket_id to indicate which socket
		this FPGA belongs to, only valid for integrated solution.
		User only needs this information, in case standard numa node
		can't provide correct information.

What:		/sys/bus/platform/devices/dfl-fme.0/errors/pcie0_errors
Date:		August 2019
KernelVersion:  5.4
Contact:	Wu Hao <hao.wu@intel.com>
Description:	Read-Write. Read this file for errors detected on pcie0 link.
		Write this file to clear errors logged in pcie0_errors. Write
		fails with -EINVAL if input parsing fails or input error code
		doesn't match.

What:		/sys/bus/platform/devices/dfl-fme.0/errors/pcie1_errors
Date:		August 2019
KernelVersion:  5.4
Contact:	Wu Hao <hao.wu@intel.com>
Description:	Read-Write. Read this file for errors detected on pcie1 link.
		Write this file to clear errors logged in pcie1_errors. Write
		fails with -EINVAL if input parsing fails or input error code
		doesn't match.

What:		/sys/bus/platform/devices/dfl-fme.0/errors/nonfatal_errors
Date:		August 2019
KernelVersion:  5.4
Contact:	Wu Hao <hao.wu@intel.com>
Description:	Read-only. It returns non-fatal errors detected.

What:		/sys/bus/platform/devices/dfl-fme.0/errors/catfatal_errors
Date:		August 2019
KernelVersion:  5.4
Contact:	Wu Hao <hao.wu@intel.com>
Description:	Read-only. It returns catastrophic and fatal errors detected.

What:		/sys/bus/platform/devices/dfl-fme.0/errors/inject_errors
Date:		August 2019
KernelVersion:  5.4
Contact:	Wu Hao <hao.wu@intel.com>
Description:	Read-Write. Read this file to check errors injected. Write this
		file to inject errors for testing purpose. Write fails with
		-EINVAL if input parsing fails or input inject error code isn't
		supported.

What:		/sys/bus/platform/devices/dfl-fme.0/errors/fme_errors
Date:		August 2019
KernelVersion:  5.4
Contact:	Wu Hao <hao.wu@intel.com>
Description:	Read-Write. Read this file to get errors detected on FME.
		Write this file to clear errors logged in fme_errors. Write
		fials with -EINVAL if input parsing fails or input error code
		doesn't match.

What:		/sys/bus/platform/devices/dfl-fme.0/errors/first_error
Date:		August 2019
KernelVersion:  5.4
Contact:	Wu Hao <hao.wu@intel.com>
Description:	Read-only. Read this file to get the first error detected by
		hardware.

What:		/sys/bus/platform/devices/dfl-fme.0/errors/next_error
Date:		August 2019
KernelVersion:  5.4
Contact:	Wu Hao <hao.wu@intel.com>
Description:	Read-only. Read this file to get the second error detected by
		hardware.

What:		/sys/bus/platform/devices/dfl-fme.0/hwmon/hwmonX/name
Date:		October 2019
KernelVersion:	5.5
Contact:	Wu Hao <hao.wu@intel.com>
Description:	Read-Only. Read this file to get the name of hwmon device, it
		supports values:

		=================  =========================
		'dfl_fme_thermal'  thermal hwmon device name
		'dfl_fme_power'    power hwmon device name
		=================  =========================

What:		/sys/bus/platform/devices/dfl-fme.0/hwmon/hwmonX/temp1_input
Date:		October 2019
KernelVersion:	5.5
Contact:	Wu Hao <hao.wu@intel.com>
Description:	Read-Only. It returns FPGA device temperature in millidegrees
		Celsius.

What:		/sys/bus/platform/devices/dfl-fme.0/hwmon/hwmonX/temp1_max
Date:		October 2019
KernelVersion:	5.5
Contact:	Wu Hao <hao.wu@intel.com>
Description:	Read-Only. It returns hardware threshold1 temperature in
		millidegrees Celsius. If temperature rises at or above this
		threshold, hardware starts 50% or 90% throttling (see
		'temp1_max_policy').

What:		/sys/bus/platform/devices/dfl-fme.0/hwmon/hwmonX/temp1_crit
Date:		October 2019
KernelVersion:	5.5
Contact:	Wu Hao <hao.wu@intel.com>
Description:	Read-Only. It returns hardware threshold2 temperature in
		millidegrees Celsius. If temperature rises at or above this
		threshold, hardware starts 100% throttling.

What:		/sys/bus/platform/devices/dfl-fme.0/hwmon/hwmonX/temp1_emergency
Date:		October 2019
KernelVersion:	5.5
Contact:	Wu Hao <hao.wu@intel.com>
Description:	Read-Only. It returns hardware trip threshold temperature in
		millidegrees Celsius. If temperature rises at or above this
		threshold, a fatal event will be triggered to board management
		controller (BMC) to shutdown FPGA.

What:		/sys/bus/platform/devices/dfl-fme.0/hwmon/hwmonX/temp1_max_alarm
Date:		October 2019
KernelVersion:	5.5
Contact:	Wu Hao <hao.wu@intel.com>
Description:	Read-only. It returns 1 if temperature is currently at or above
		hardware threshold1 (see 'temp1_max'), otherwise 0.

What:		/sys/bus/platform/devices/dfl-fme.0/hwmon/hwmonX/temp1_crit_alarm
Date:		October 2019
KernelVersion:	5.5
Contact:	Wu Hao <hao.wu@intel.com>
Description:	Read-only. It returns 1 if temperature is currently at or above
		hardware threshold2 (see 'temp1_crit'), otherwise 0.

What:		/sys/bus/platform/devices/dfl-fme.0/hwmon/hwmonX/temp1_max_policy
Date:		October 2019
KernelVersion:	5.5
Contact:	Wu Hao <hao.wu@intel.com>
Description:	Read-Only. Read this file to get the policy of hardware threshold1
		(see 'temp1_max'). It only supports two values (policies):

		==  ==========================
		 0  AP2 state (90% throttling)
	         1  AP1 state (50% throttling)
		==  ==========================

What:		/sys/bus/platform/devices/dfl-fme.0/hwmon/hwmonX/power1_input
Date:		October 2019
KernelVersion:	5.5
Contact:	Wu Hao <hao.wu@intel.com>
Description:	Read-Only. It returns current FPGA power consumption in uW.

What:		/sys/bus/platform/devices/dfl-fme.0/hwmon/hwmonX/power1_max
Date:		October 2019
KernelVersion:	5.5
Contact:	Wu Hao <hao.wu@intel.com>
Description:	Read-Write. Read this file to get current hardware power
		threshold1 in uW. If power consumption rises at or above
		this threshold, hardware starts 50% throttling.
		Write this file to set current hardware power threshold1 in uW.
		As hardware only accepts values in Watts, so input value will
		be round down per Watts (< 1 watts part will be discarded) and
		clamped within the range from 0 to 127 Watts. Write fails with
		-EINVAL if input parsing fails.

What:		/sys/bus/platform/devices/dfl-fme.0/hwmon/hwmonX/power1_crit
Date:		October 2019
KernelVersion:	5.5
Contact:	Wu Hao <hao.wu@intel.com>
Description:	Read-Write. Read this file to get current hardware power
		threshold2 in uW. If power consumption rises at or above
		this threshold, hardware starts 90% throttling.
		Write this file to set current hardware power threshold2 in uW.
		As hardware only accepts values in Watts, so input value will
		be round down per Watts (< 1 watts part will be discarded) and
		clamped within the range from 0 to 127 Watts. Write fails with
		-EINVAL if input parsing fails.

What:		/sys/bus/platform/devices/dfl-fme.0/hwmon/hwmonX/power1_max_alarm
Date:		October 2019
KernelVersion:	5.5
Contact:	Wu Hao <hao.wu@intel.com>
Description:	Read-only. It returns 1 if power consumption is currently at or
		above hardware threshold1 (see 'power1_max'), otherwise 0.

What:		/sys/bus/platform/devices/dfl-fme.0/hwmon/hwmonX/power1_crit_alarm
Date:		October 2019
KernelVersion:	5.5
Contact:	Wu Hao <hao.wu@intel.com>
Description:	Read-only. It returns 1 if power consumption is currently at or
		above hardware threshold2 (see 'power1_crit'), otherwise 0.

What:		/sys/bus/platform/devices/dfl-fme.0/hwmon/hwmonX/power1_xeon_limit
Date:		October 2019
KernelVersion:	5.5
Contact:	Wu Hao <hao.wu@intel.com>
Description:	Read-Only. It returns power limit for XEON in uW.

What:		/sys/bus/platform/devices/dfl-fme.0/hwmon/hwmonX/power1_fpga_limit
Date:		October 2019
KernelVersion:	5.5
Contact:	Wu Hao <hao.wu@intel.com>
Description:	Read-Only. It returns power limit for FPGA in uW.

What:		/sys/bus/platform/devices/dfl-fme.0/hwmon/hwmonX/power1_ltr
Date:		October 2019
KernelVersion:	5.5
Contact:	Wu Hao <hao.wu@intel.com>
Description:	Read-only. Read this file to get current Latency Tolerance
		Reporting (ltr) value. It returns 1 if all Accelerated
		Function Units (AFUs) can tolerate latency >= 40us for memory
		access or 0 if any AFU is latency sensitive (< 40us).


code:
What:		/sys/bus/platform/devices/dfl-port.0/id
Date:		June 2018
KernelVersion:	4.19
Contact:	Wu Hao <hao.wu@intel.com>
Description:	Read-only. It returns id of this port. One DFL FPGA device
		may have more than one port. Userspace could use this id to
		distinguish different ports under same FPGA device.

What:		/sys/bus/platform/devices/dfl-port.0/afu_id
Date:		June 2018
KernelVersion:	4.19
Contact:	Wu Hao <hao.wu@intel.com>
Description:	Read-only. User can program different PR bitstreams to FPGA
		Accelerator Function Unit (AFU) for different functions. It
		returns uuid which could be used to identify which PR bitstream
		is programmed in this AFU.

What:		/sys/bus/platform/devices/dfl-port.0/power_state
Date:		August 2019
KernelVersion:	5.4
Contact:	Wu Hao <hao.wu@intel.com>
Description:	Read-only. It reports the APx (AFU Power) state, different APx
		means different throttling level. When reading this file, it
		returns "0" - Normal / "1" - AP1 / "2" - AP2 / "6" - AP6.

What:		/sys/bus/platform/devices/dfl-port.0/ap1_event
Date:		August 2019
KernelVersion:	5.4
Contact:	Wu Hao <hao.wu@intel.com>
Description:	Read-write. Read this file for AP1 (AFU Power State 1) event.
		It's used to indicate transient AP1 state. Write 1 to this
		file to clear AP1 event.

What:		/sys/bus/platform/devices/dfl-port.0/ap2_event
Date:		August 2019
KernelVersion:	5.4
Contact:	Wu Hao <hao.wu@intel.com>
Description:	Read-write. Read this file for AP2 (AFU Power State 2) event.
		It's used to indicate transient AP2 state. Write 1 to this
		file to clear AP2 event.

What:		/sys/bus/platform/devices/dfl-port.0/ltr
Date:		August 2019
KernelVersion:	5.4
Contact:	Wu Hao <hao.wu@intel.com>
Description:	Read-write. Read or set AFU latency tolerance reporting value.
		Set ltr to 1 if the AFU can tolerate latency >= 40us or set it
		to 0 if it is latency sensitive.

What:		/sys/bus/platform/devices/dfl-port.0/userclk_freqcmd
Date:		August 2019
KernelVersion:	5.4
Contact:	Wu Hao <hao.wu@intel.com>
Description:	Write-only. User writes command to this interface to set
		userclock to AFU.

What:		/sys/bus/platform/devices/dfl-port.0/userclk_freqsts
Date:		August 2019
KernelVersion:	5.4
Contact:	Wu Hao <hao.wu@intel.com>
Description:	Read-only. Read this file to get the status of issued command
		to userclck_freqcmd.

What:		/sys/bus/platform/devices/dfl-port.0/userclk_freqcntrcmd
Date:		August 2019
KernelVersion:	5.4
Contact:	Wu Hao <hao.wu@intel.com>
Description:	Write-only. User writes command to this interface to set
		userclock counter.

What:		/sys/bus/platform/devices/dfl-port.0/userclk_freqcntrsts
Date:		August 2019
KernelVersion:	5.4
Contact:	Wu Hao <hao.wu@intel.com>
Description:	Read-only. Read this file to get the status of issued command
		to userclck_freqcntrcmd.

What:		/sys/bus/platform/devices/dfl-port.0/errors/errors
Date:		August 2019
KernelVersion:	5.4
Contact:	Wu Hao <hao.wu@intel.com>
Description:	Read-Write. Read this file to get errors detected on port and
		Accelerated Function Unit (AFU). Write error code to this file
		to clear errors. Write fails with -EINVAL if input parsing
		fails or input error code doesn't match. Write fails with
		-EBUSY or -ETIMEDOUT if error can't be cleared as hardware
		in low power state (-EBUSY) or not respoding (-ETIMEDOUT).

What:		/sys/bus/platform/devices/dfl-port.0/errors/first_error
Date:		August 2019
KernelVersion:	5.4
Contact:	Wu Hao <hao.wu@intel.com>
Description:	Read-only. Read this file to get the first error detected by
		hardware.

What:		/sys/bus/platform/devices/dfl-port.0/errors/first_malformed_req
Date:		August 2019
KernelVersion:	5.4
Contact:	Wu Hao <hao.wu@intel.com>
Description:	Read-only. Read this file to get the first malformed request
		captured by hardware.


code:
What:		/sys/bus/platform/devices/INT3407:00/dptf_power/charger_type
Date:		Jul, 2016
KernelVersion:	v4.10
Contact:	linux-acpi@vger.kernel.org
Description:
		(RO) The charger type - Traditional, Hybrid or NVDC.

What:		/sys/bus/platform/devices/INT3407:00/dptf_power/adapter_rating_mw
Date:		Jul, 2016
KernelVersion:	v4.10
Contact:	linux-acpi@vger.kernel.org
Description:
		(RO) Adapter rating in milliwatts (the maximum Adapter power).
		Must be 0 if no AC Adaptor is plugged in.

What:		/sys/bus/platform/devices/INT3407:00/dptf_power/max_platform_power_mw
Date:		Jul, 2016
KernelVersion:	v4.10
Contact:	linux-acpi@vger.kernel.org
Description:
		(RO) Maximum platform power that can be supported by the battery
		in milliwatts.

What:		/sys/bus/platform/devices/INT3407:00/dptf_power/platform_power_source
Date:		Jul, 2016
KernelVersion:	v4.10
Contact:	linux-acpi@vger.kernel.org
Description:
		(RO) Display the platform power source

		========= ============================
		bits[3:0] Current power source
			  - 0x00 = DC
			  - 0x01 = AC
			  - 0x02 = USB
			  - 0x03 = Wireless Charger
		bits[7:4] Power source sequence number
		========= ============================

What:		/sys/bus/platform/devices/INT3407:00/dptf_power/battery_steady_power
Date:		Jul, 2016
KernelVersion:	v4.10
Contact:	linux-acpi@vger.kernel.org
Description:
		(RO) The maximum sustained power for battery in milliwatts.

What:		/sys/bus/platform/devices/INT3407:00/dptf_power/rest_of_platform_power_mw
Date:		June, 2020
KernelVersion:	v5.8
Contact:	linux-acpi@vger.kernel.org
Description:
		(RO) Shows the rest (outside of SoC) of worst-case platform power.

What:		/sys/bus/platform/devices/INT3407:00/dptf_power/prochot_confirm
Date:		June, 2020
KernelVersion:	v5.8
Contact:	linux-acpi@vger.kernel.org
Description:
		(WO) Confirm embedded controller about a prochot notification.

What:		/sys/bus/platform/devices/INT3532:00/dptf_battery/max_platform_power_mw
Date:		June, 2020
KernelVersion:	v5.8
Contact:	linux-acpi@vger.kernel.org
Description:
		(RO) The maximum platform power that can be supported by the battery in milli watts.

What:		/sys/bus/platform/devices/INT3532:00/dptf_battery/max_steady_state_power_mw
Date:		June, 2020
KernelVersion:	v5.8
Contact:	linux-acpi@vger.kernel.org
Description:
		(RO) The maximum sustained power for battery in milli watts.

What:		/sys/bus/platform/devices/INT3532:00/dptf_battery/high_freq_impedance_mohm
Date:		June, 2020
KernelVersion:	v5.8
Contact:	linux-acpi@vger.kernel.org
Description:
		(RO) The high frequency impedance value that can be obtained from battery
		fuel gauge in milli Ohms.

What:		/sys/bus/platform/devices/INT3532:00/dptf_battery/no_load_voltage_mv
Date:		June, 2020
KernelVersion:	v5.8
Contact:	linux-acpi@vger.kernel.org
Description:
		(RO) The no-load voltage that can be obtained from battery fuel gauge in
		milli volts.

What:		/sys/bus/platform/devices/INT3532:00/dptf_battery/current_discharge_capbility_ma
Date:		June, 2020
KernelVersion:	v5.8
Contact:	linux-acpi@vger.kernel.org
Description:
		(RO) The battery discharge current capability obtained from battery fuel gauge in
		milli Amps.

What:		/sys/bus/platform/devices/INTC1045:00/pch_fivr_switch_frequency/freq_mhz_low_clock
Date:		November, 2020
KernelVersion:	v5.10
Contact:	linux-acpi@vger.kernel.org
Description:
		(RW) The PCH FIVR (Fully Integrated Voltage Regulator) switching frequency in MHz,
		when FIVR clock is 19.2MHz or 24MHz.

What:		/sys/bus/platform/devices/INTC1045:00/pch_fivr_switch_frequency/freq_mhz_high_clock
Date:		November, 2020
KernelVersion:	v5.10
Contact:	linux-acpi@vger.kernel.org
Description:
		(RW) The PCH FIVR (Fully Integrated Voltage Regulator) switching frequency in MHz,
		when FIVR clock is 38.4MHz.

What:		/sys/bus/platform/devices/INTC1045:00/pch_fivr_switch_frequency/fivr_switching_freq_mhz
Date:		September, 2021
KernelVersion:	v5.15
Contact:	linux-acpi@vger.kernel.org
Description:
		(RO) Get the FIVR switching control frequency in MHz.

What:		/sys/bus/platform/devices/INTC1045:00/pch_fivr_switch_frequency/fivr_switching_fault_status
Date:		September, 2021
KernelVersion:	v5.15
Contact:	linux-acpi@vger.kernel.org
Description:
		(RO) Read the FIVR switching frequency control fault status.

What:		/sys/bus/platform/devices/INTC1045:00/pch_fivr_switch_frequency/ssc_clock_info
Date:		September, 2021
KernelVersion:	v5.15
Contact:	linux-acpi@vger.kernel.org
Description:
		(RO) Presents SSC (spread spectrum clock) information for EMI
		(Electro magnetic interference) control. This is a bit mask.

		=======	==========================================
		Bits	Description
		=======	==========================================
		[7:0]	Sets clock spectrum spread percentage:
			0x00=0.2% , 0x3F=10%
			1 LSB = 0.1% increase in spread (for
			settings 0x01 thru 0x1C)
			1 LSB = 0.2% increase in spread (for
			settings 0x1E thru 0x3F)
		[8]	When set to 1, enables spread
			spectrum clock
		[9]	0: Triangle mode. FFC frequency
			walks around the Fcenter in a linear
			fashion
			1: Random walk mode. FFC frequency
			changes randomly within the SSC
			(Spread spectrum clock) range
		[10]	0: No white noise. 1: Add white noise
			to spread waveform
		[11]	When 1, future writes are ignored.
		=======	==========================================


code:
What:		/sys/devices/platform/eeepc/disp
Date:		May 2008
KernelVersion:	2.6.26
Contact:	"Corentin Chary" <corentincj@iksaif.net>
Description:
		This file allows display switching.

		- 1 = LCD
		- 2 = CRT
		- 3 = LCD+CRT

		If you run X11, you should use xrandr instead.

What:		/sys/devices/platform/eeepc/camera
Date:		May 2008
KernelVersion:	2.6.26
Contact:	"Corentin Chary" <corentincj@iksaif.net>
Description:
		Control the camera. 1 means on, 0 means off.

What:		/sys/devices/platform/eeepc/cardr
Date:		May 2008
KernelVersion:	2.6.26
Contact:	"Corentin Chary" <corentincj@iksaif.net>
Description:
		Control the card reader. 1 means on, 0 means off.

What:		/sys/devices/platform/eeepc/cpufv
Date:		Jun 2009
KernelVersion:	2.6.31
Contact:	"Corentin Chary" <corentincj@iksaif.net>
Description:
		Change CPU clock configuration.
		On the Eee PC 1000H there are three available clock configuration:

		    * 0 -> Super Performance Mode
		    * 1 -> High Performance Mode
		    * 2 -> Power Saving Mode

		On Eee PC 701 there is only 2 available clock configurations.
		Available configuration are listed in available_cpufv file.
		Reading this file will show the raw hexadecimal value which
		is defined as follow::

		  | 8 bit | 8 bit |
		      |       `---- Current mode
		      `------------ Availables modes

		For example, 0x301 means: mode 1 selected, 3 available modes.

What:		/sys/devices/platform/eeepc/available_cpufv
Date:		Jun 2009
KernelVersion:	2.6.31
Contact:	"Corentin Chary" <corentincj@iksaif.net>
Description:
		List available cpufv modes.


code:
What:		/sys/devices/platform/hidma-*/chid
		/sys/devices/platform/QCOM8061:*/chid
Date:		Dec 2015
KernelVersion:	4.4
Contact:	"Sinan Kaya <okaya@codeaurora.org>"
Description:
		Contains the ID of the channel within the HIDMA instance.
		It is used to associate a given HIDMA channel with the
		priority and weight calls in the management interface.


code:
What:		/sys/devices/platform/hidma-mgmt*/chanops/chan*/priority
		/sys/devices/platform/QCOM8060:*/chanops/chan*/priority
Date:		Nov 2015
KernelVersion:	4.4
Contact:	"Sinan Kaya <okaya@codeaurora.org>"
Description:
		Contains either 0 or 1 and indicates if the DMA channel is a
		low priority (0) or high priority (1) channel.

What:		/sys/devices/platform/hidma-mgmt*/chanops/chan*/weight
		/sys/devices/platform/QCOM8060:*/chanops/chan*/weight
Date:		Nov 2015
KernelVersion:	4.4
Contact:	"Sinan Kaya <okaya@codeaurora.org>"
Description:
		Contains 0..15 and indicates the weight of the channel among
		equal priority channels during round robin scheduling.

What:		/sys/devices/platform/hidma-mgmt*/chreset_timeout_cycles
		/sys/devices/platform/QCOM8060:*/chreset_timeout_cycles
Date:		Nov 2015
KernelVersion:	4.4
Contact:	"Sinan Kaya <okaya@codeaurora.org>"
Description:
		Contains the platform specific cycle value to wait after a
		reset command is issued. If the value is chosen too short,
		then the HW will issue a reset failure interrupt. The value
		is platform specific and should not be changed without
		consultance.

What:		/sys/devices/platform/hidma-mgmt*/dma_channels
		/sys/devices/platform/QCOM8060:*/dma_channels
Date:		Nov 2015
KernelVersion:	4.4
Contact:	"Sinan Kaya <okaya@codeaurora.org>"
Description:
		Contains the number of dma channels supported by one instance
		of HIDMA hardware. The value may change from chip to chip.

What:		/sys/devices/platform/hidma-mgmt*/hw_version_major
		/sys/devices/platform/QCOM8060:*/hw_version_major
Date:		Nov 2015
KernelVersion:	4.4
Contact:	"Sinan Kaya <okaya@codeaurora.org>"
Description:
		Version number major for the hardware.

What:		/sys/devices/platform/hidma-mgmt*/hw_version_minor
		/sys/devices/platform/QCOM8060:*/hw_version_minor
Date:		Nov 2015
KernelVersion:	4.4
Contact:	"Sinan Kaya <okaya@codeaurora.org>"
Description:
		Version number minor for the hardware.

What:		/sys/devices/platform/hidma-mgmt*/max_rd_xactions
		/sys/devices/platform/QCOM8060:*/max_rd_xactions
Date:		Nov 2015
KernelVersion:	4.4
Contact:	"Sinan Kaya <okaya@codeaurora.org>"
Description:
		Contains a value between 0 and 31. Maximum number of
		read transactions that can be issued back to back.
		Choosing a higher number gives better performance but
		can also cause performance reduction to other peripherals
		sharing the same bus.

What:		/sys/devices/platform/hidma-mgmt*/max_read_request
		/sys/devices/platform/QCOM8060:*/max_read_request
Date:		Nov 2015
KernelVersion:	4.4
Contact:	"Sinan Kaya <okaya@codeaurora.org>"
Description:
		Size of each read request. The value needs to be a power
		of two and can be between 128 and 1024.

What:		/sys/devices/platform/hidma-mgmt*/max_wr_xactions
		/sys/devices/platform/QCOM8060:*/max_wr_xactions
Date:		Nov 2015
KernelVersion:	4.4
Contact:	"Sinan Kaya <okaya@codeaurora.org>"
Description:
		Contains a value between 0 and 31. Maximum number of
		write transactions that can be issued back to back.
		Choosing a higher number gives better performance but
		can also cause performance reduction to other peripherals
		sharing the same bus.

What:		/sys/devices/platform/hidma-mgmt*/max_write_request
		/sys/devices/platform/QCOM8060:*/max_write_request
Date:		Nov 2015
KernelVersion:	4.4
Contact:	"Sinan Kaya <okaya@codeaurora.org>"
Description:
		Size of each write request. The value needs to be a power
		of two and can be between 128 and 1024.


code:
What:		/sys/devices/platform/<i2c-demux-name>/available_masters
Date:		January 2016
KernelVersion:	4.6
Contact:	Wolfram Sang <wsa+renesas@sang-engineering.com>
Description:
		Reading the file will give you a list of masters which can be
		selected for a demultiplexed bus. The format is
		"<index>:<name>". Example from a Renesas Lager board::

		  0:/i2c@e6500000 1:/i2c@e6508000

What:		/sys/devices/platform/<i2c-demux-name>/current_master
Date:		January 2016
KernelVersion:	4.6
Contact:	Wolfram Sang <wsa+renesas@sang-engineering.com>
Description:
		This file selects/shows the active I2C master for a demultiplexed
		bus. It uses the <index> value from the file 'available_masters'.


code:
What:		/sys/bus/platform/devices/VPC2004:*/camera_power
Date:		Dec 2010
KernelVersion:	2.6.37
Contact:	"Ike Panhc <ike.pan@canonical.com>"
Description:
		Control the power of camera module. 1 means on, 0 means off.

What:		/sys/bus/platform/devices/VPC2004:*/fan_mode
Date:		June 2012
KernelVersion:	3.6
Contact:	"Maxim Mikityanskiy <maxtram95@gmail.com>"
Description:
		Change fan mode
		There are four available modes:

			* 0 -> Super Silent Mode
			* 1 -> Standard Mode
			* 2 -> Dust Cleaning
			* 4 -> Efficient Thermal Dissipation Mode

What:		/sys/bus/platform/devices/VPC2004:*/touchpad
Date:		May 2017
KernelVersion:	4.13
Contact:	"Ritesh Raj Sarraf <rrs@debian.org>"
Description:
		Control touchpad mode.
			* 1 -> Switched On
			* 0 -> Switched Off

What:		/sys/bus/platform/devices/VPC2004:*/conservation_mode
Date:		Aug 2017
KernelVersion:	4.14
Contact:	platform-driver-x86@vger.kernel.org
Description:
		Controls whether the conservation mode is enabled or not.
		This feature limits the maximum battery charge percentage to
		around 50-60% in order to prolong the lifetime of the battery.

What:		/sys/bus/platform/devices/VPC2004:*/fn_lock
Date:		May 2018
KernelVersion:	4.18
Contact:	"Oleg Keri <ezhi99@gmail.com>"
Description:
		Control fn-lock mode.

			* 1 -> Switched On
			* 0 -> Switched Off

		For example::

		  # echo "0" >	\
		  /sys/bus/pci/devices/0000:00:1f.0/PNP0C09:00/VPC2004:00/fn_lock

What:		/sys/bus/platform/devices/VPC2004:*/usb_charging
Date:		Feb 2021
KernelVersion:	5.12
Contact:	platform-driver-x86@vger.kernel.org
Description:
		Controls whether the "always on USB charging" feature is
		enabled or not. This feature enables charging USB devices
		even if the computer is not turned on.


code:
What:		/sys/devices/virtual/misc/intel_ifs_<N>/run_test
Date:		Nov 16 2022
KernelVersion:	6.2
Contact:	"Jithu Joseph" <jithu.joseph@intel.com>
Description:	Write <cpu#> to trigger IFS test for one online core.
		Note that the test is per core. The cpu# can be
		for any thread on the core. Running on one thread
		completes the test for the core containing that thread.
		Example: to test the core containing cpu5: echo 5 >
		/sys/devices/virtual/misc/intel_ifs_<N>/run_test

What:		/sys/devices/virtual/misc/intel_ifs_<N>/status
Date:		Nov 16 2022
KernelVersion:	6.2
Contact:	"Jithu Joseph" <jithu.joseph@intel.com>
Description:	The status of the last test. It can be one of "pass", "fail"
		or "untested".

What:		/sys/devices/virtual/misc/intel_ifs_<N>/details
Date:		Nov 16 2022
KernelVersion:	6.2
Contact:	"Jithu Joseph" <jithu.joseph@intel.com>
Description:	Additional information regarding the last test. The details file reports
		the hex value of the SCAN_STATUS MSR. Note that the error_code field
		may contain driver defined software code not defined in the Intel SDM.

What:		/sys/devices/virtual/misc/intel_ifs_<N>/image_version
Date:		Nov 16 2022
KernelVersion:	6.2
Contact:	"Jithu Joseph" <jithu.joseph@intel.com>
Description:	Version (hexadecimal) of loaded IFS binary image. If no scan image
		is loaded reports "none".

What:		/sys/devices/virtual/misc/intel_ifs_<N>/current_batch
Date:		Nov 16 2022
KernelVersion:	6.2
Contact:	"Jithu Joseph" <jithu.joseph@intel.com>
Description:	Write a number less than or equal to 0xff to load an IFS test image.
		The number written treated as the 2 digit suffix in the following file name:
		/lib/firmware/intel/ifs_<N>/ff-mm-ss-02x.scan
		Reading the file will provide the suffix of the currently loaded IFS test image.


code:
What:		/sys/devices/platform/<platform>/etr3
Date:		Apr 2021
KernelVersion:	5.13
Contact:	"Tomas Winkler" <tomas.winkler@intel.com>
Description:
		The file exposes "Extended Test Mode Register 3" global
		reset bits. The bits are used during an Intel platform
		manufacturing process to indicate that consequent reset
		of the platform is a "global reset". This type of reset
		is required in order for manufacturing configurations
		to take effect.

		Display global reset setting bits for PMC.

			* bit 31 - global reset is locked
			* bit 20 - global reset is set

		Writing bit 20 value to the etr3 will induce
		a platform "global reset" upon consequent platform reset,
		in case the register is not locked.
		The "global reset bit" should be locked on a production
		system and the file is in read-only mode.


code:
What:		/sys/bus/wmi/devices/44FADEB1-B204-40F2-8581-394BBDC1B651/firmware_update_request
Date:		April 2020
KernelVersion:	5.7
Contact:	"Jithu Joseph" <jithu.joseph@intel.com>
Description:
		Allow user space entities to trigger update of Slim
		Bootloader (SBL). This attribute normally has a value
		of 0 and userspace can signal SBL to update firmware,
		on next reboot, by writing a value of 1.
		There are two available states:

		    * 0 -> Skip firmware update while rebooting
		    * 1 -> Attempt firmware update on next reboot


code:
What:		/sys/devices/platform/<platform>/force_power
Date:		September 2017
KernelVersion:	4.15
Contact:	"Mario Limonciello" <mario.limonciello@outlook.com>
Description:
		Modify the platform force power state, influencing
		Thunderbolt controllers to turn on or off when no
		devices are connected (write-only)
		There are two available states:

		    * 0 -> Force power disabled
		    * 1 -> Force power enabled


code:
What:		/sys/devices/platform/kim/dev_name
Date:		January 2010
KernelVersion:	2.6.38
Contact:	"Pavan Savoy" <pavan_savoy@ti.com>
Description:
		Name of the UART device at which the WL128x chip
		is connected. example: "/dev/ttyS0".

		The device name flows down to architecture specific board
		initialization file from the ATAGS bootloader
		firmware. The name exposed is read from the user-space
		dameon and opens the device when install is requested.

What:		/sys/devices/platform/kim/baud_rate
Date:		January 2010
KernelVersion:	2.6.38
Contact:	"Pavan Savoy" <pavan_savoy@ti.com>
Description:
		The maximum reliable baud-rate the host can support.
		Different platforms tend to have different high-speed
		UART configurations, so the baud-rate needs to be set
		locally and also sent across to the WL128x via a HCI-VS
		command. The entry is read and made use by the user-space
		daemon when the ldisc install is requested.

What:		/sys/devices/platform/kim/flow_cntrl
Date:		January 2010
KernelVersion:	2.6.38
Contact:	"Pavan Savoy" <pavan_savoy@ti.com>
Description:
		The WL128x makes use of flow control mechanism, and this
		entry most often should be 1, the host's UART is required
		to have the capability of flow-control, or else this
		entry can be made use of for exceptions.

What:		/sys/devices/platform/kim/install
Date:		January 2010
KernelVersion:	2.6.38
Contact:	"Pavan Savoy" <pavan_savoy@ti.com>
Description:
		When one of the protocols Bluetooth, FM or GPS wants to make
		use of the shared UART transport, it registers to the shared
		transport driver, which will signal the user-space for opening,
		configuring baud and install line discipline via this sysfs
		entry. This entry would be polled upon by the user-space
		daemon managing the UART, and is notified about the change
		by the sysfs_notify. The value would be '1' when UART needs
		to be opened/ldisc installed, and would be '0' when UART
		is no more required and needs to be closed.


code:
What:		/sys/devices/platform/lg-laptop/reader_mode
Date:		October 2018
KernelVersion:	4.20
Contact:	"Matan Ziv-Av <matan@svgalib.org>
Description:
        Control reader mode. 1 means on, 0 means off.

What:		/sys/devices/platform/lg-laptop/fn_lock
Date:		October 2018
KernelVersion:	4.20
Contact:	"Matan Ziv-Av <matan@svgalib.org>
Description:
        Control FN lock mode. 1 means on, 0 means off.

What:		/sys/devices/platform/lg-laptop/battery_care_limit
Date:		October 2018
KernelVersion:	4.20
Contact:	"Matan Ziv-Av <matan@svgalib.org>
Description:
        Deprecated use /sys/class/power_supply/CMB0/charge_control_end_threshold
        Maximal battery charge level. Accepted values are 80 or 100.

What:		/sys/devices/platform/lg-laptop/fan_mode
Date:		October 2018
KernelVersion:	4.20
Contact:	"Matan Ziv-Av <matan@svgalib.org>
Description:
        Control fan mode. 1 for performance mode, 0 for silent mode.

What:		/sys/devices/platform/lg-laptop/usb_charge
Date:		October 2018
KernelVersion:	4.20
Contact:	"Matan Ziv-Av <matan@svgalib.org>
Description:
        Control USB port charging when device is turned off.
        1 means on, 0 means off.