code:
Note:
  This documents additional properties of any device beyond what
  is documented in Documentation/admin-guide/sysfs-rules.rst

What:		/sys/devices/*/of_node
Date:		February 2015
Contact:	Device Tree mailing list <devicetree@vger.kernel.org>
Description:
		Any device associated with a device-tree node will have
		an of_path symlink pointing to the corresponding device
		node in /sys/firmware/devicetree/

What:		/sys/devices/*/devspec
Date:		October 2016
Contact:	Device Tree mailing list <devicetree@vger.kernel.org>
Description:
		If CONFIG_OF is enabled, then this file is present. When
		read, it returns full name of the device node.

What:		/sys/devices/*/obppath
Date:		October 2016
Contact:	Device Tree mailing list <devicetree@vger.kernel.org>
Description:
		If CONFIG_OF is enabled, then this file is present. When
		read, it returns full name of the device node.

What:		/sys/devices/*/dev
Date:		Jun 2006
Contact:	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Description:
		Major and minor numbers of the character device corresponding
		to the device (in <major>:<minor> format).

path: Documentation/ABI/stable/sysfs-devices


code:
What:		/sys/devices/system/node/possible
Date:		October 2002
Contact:	Linux Memory Management list <linux-mm@kvack.org>
Description:
		Nodes that could be possibly become online at some point.

What:		/sys/devices/system/node/online
Date:		October 2002
Contact:	Linux Memory Management list <linux-mm@kvack.org>
Description:
		Nodes that are online.

What:		/sys/devices/system/node/has_normal_memory
Date:		October 2002
Contact:	Linux Memory Management list <linux-mm@kvack.org>
Description:
		Nodes that have regular memory.

What:		/sys/devices/system/node/has_cpu
Date:		October 2002
Contact:	Linux Memory Management list <linux-mm@kvack.org>
Description:
		Nodes that have one or more CPUs.

What:		/sys/devices/system/node/has_high_memory
Date:		October 2002
Contact:	Linux Memory Management list <linux-mm@kvack.org>
Description:
		Nodes that have regular or high memory.
		Depends on CONFIG_HIGHMEM.

What:		/sys/devices/system/node/nodeX
Date:		October 2002
Contact:	Linux Memory Management list <linux-mm@kvack.org>
Description:
		When CONFIG_NUMA is enabled, this is a directory containing
		information on node X such as what CPUs are local to the
		node. Each file is detailed next.

What:		/sys/devices/system/node/nodeX/cpumap
Date:		October 2002
Contact:	Linux Memory Management list <linux-mm@kvack.org>
Description:
		The node's cpumap.

What:		/sys/devices/system/node/nodeX/cpulist
Date:		October 2002
Contact:	Linux Memory Management list <linux-mm@kvack.org>
Description:
		The CPUs associated to the node.

What:		/sys/devices/system/node/nodeX/meminfo
Date:		October 2002
Contact:	Linux Memory Management list <linux-mm@kvack.org>
Description:
		Provides information about the node's distribution and memory
		utilization. Similar to /proc/meminfo, see Documentation/filesystems/proc.rst

What:		/sys/devices/system/node/nodeX/numastat
Date:		October 2002
Contact:	Linux Memory Management list <linux-mm@kvack.org>
Description:
		The node's hit/miss statistics, in units of pages.
		See Documentation/admin-guide/numastat.rst

What:		/sys/devices/system/node/nodeX/distance
Date:		October 2002
Contact:	Linux Memory Management list <linux-mm@kvack.org>
Description:
		Distance between the node and all the other nodes
		in the system.

What:		/sys/devices/system/node/nodeX/vmstat
Date:		October 2002
Contact:	Linux Memory Management list <linux-mm@kvack.org>
Description:
		The node's zoned virtual memory statistics.
		This is a superset of numastat.

What:		/sys/devices/system/node/nodeX/compact
Date:		February 2010
Contact:	Mel Gorman <mel@csn.ul.ie>
Description:
		When this file is written to, all memory within that node
		will be compacted. When it completes, memory will be freed
		into blocks which have as many contiguous pages as possible

What:		/sys/devices/system/node/nodeX/hugepages/hugepages-<size>/
Date:		December 2009
Contact:	Lee Schermerhorn <lee.schermerhorn@hp.com>
Description:
		The node's huge page size control/query attributes.
		See Documentation/admin-guide/mm/hugetlbpage.rst

What:		/sys/devices/system/node/nodeX/accessY/
Date:		December 2018
Contact:	Keith Busch <keith.busch@intel.com>
Description:
		The node's relationship to other nodes for access class "Y".

What:		/sys/devices/system/node/nodeX/accessY/initiators/
Date:		December 2018
Contact:	Keith Busch <keith.busch@intel.com>
Description:
		The directory containing symlinks to memory initiator
		nodes that have class "Y" access to this target node's
		memory. CPUs and other memory initiators in nodes not in
		the list accessing this node's memory may have different
		performance.

What:		/sys/devices/system/node/nodeX/accessY/targets/
Date:		December 2018
Contact:	Keith Busch <keith.busch@intel.com>
Description:
		The directory containing symlinks to memory targets that
		this initiator node has class "Y" access.

What:		/sys/devices/system/node/nodeX/accessY/initiators/read_bandwidth
Date:		December 2018
Contact:	Keith Busch <keith.busch@intel.com>
Description:
		This node's read bandwidth in MB/s when accessed from
		nodes found in this access class's linked initiators.

What:		/sys/devices/system/node/nodeX/accessY/initiators/read_latency
Date:		December 2018
Contact:	Keith Busch <keith.busch@intel.com>
Description:
		This node's read latency in nanoseconds when accessed
		from nodes found in this access class's linked initiators.

What:		/sys/devices/system/node/nodeX/accessY/initiators/write_bandwidth
Date:		December 2018
Contact:	Keith Busch <keith.busch@intel.com>
Description:
		This node's write bandwidth in MB/s when accessed from
		found in this access class's linked initiators.

What:		/sys/devices/system/node/nodeX/accessY/initiators/write_latency
Date:		December 2018
Contact:	Keith Busch <keith.busch@intel.com>
Description:
		This node's write latency in nanoseconds when access
		from nodes found in this class's linked initiators.

What:		/sys/devices/system/node/nodeX/memory_side_cache/indexY/
Date:		December 2018
Contact:	Keith Busch <keith.busch@intel.com>
Description:
		The directory containing attributes for the memory-side cache
		level 'Y'.

What:		/sys/devices/system/node/nodeX/memory_side_cache/indexY/indexing
Date:		December 2018
Contact:	Keith Busch <keith.busch@intel.com>
Description:
		The caches associativity indexing: 0 for direct mapped,
		non-zero if indexed.

What:		/sys/devices/system/node/nodeX/memory_side_cache/indexY/line_size
Date:		December 2018
Contact:	Keith Busch <keith.busch@intel.com>
Description:
		The number of bytes accessed from the next cache level on a
		cache miss.

What:		/sys/devices/system/node/nodeX/memory_side_cache/indexY/size
Date:		December 2018
Contact:	Keith Busch <keith.busch@intel.com>
Description:
		The size of this memory side cache in bytes.

What:		/sys/devices/system/node/nodeX/memory_side_cache/indexY/write_policy
Date:		December 2018
Contact:	Keith Busch <keith.busch@intel.com>
Description:
		The cache write policy: 0 for write-back, 1 for write-through,
		other or unknown.

What:		/sys/devices/system/node/nodeX/x86/sgx_total_bytes
Date:		November 2021
Contact:	Jarkko Sakkinen <jarkko@kernel.org>
Description:
		The total amount of SGX physical memory in bytes.

repo_name: angery/linux


code:
What: 		/sys/devices/system/cpu/dscr_default
Date:		13-May-2014
KernelVersion:	v3.15.0
Contact:
Description:	Writes are equivalent to writing to
		/sys/devices/system/cpu/cpuN/dscr on all CPUs.
		Reads return the last written value or 0.
		This value is not a global default: it is a way to set
		all per-CPU defaults at the same time.
Values:		64 bit unsigned integer (bit field)

What: 		/sys/devices/system/cpu/cpu[0-9]+/dscr
Date:		13-May-2014
KernelVersion:	v3.15.0
Contact:
Description:	Default value for the Data Stream Control Register (DSCR) on
		a CPU.
		This default value is used when the kernel is executing and
		for any process that has not set the DSCR itself.
		If a process ever sets the DSCR (via direct access to the
		SPR) that value will be persisted for that process and used
		on any CPU where it executes (overriding the value described
		here).
		If set by a process it will be inherited by child processes.
Values:		64 bit unsigned integer (bit field)

What:           /sys/devices/system/cpu/cpuX/topology/physical_package_id
Description:    physical package id of cpuX. Typically corresponds to a physical
                socket number, but the actual value is architecture and platform
                dependent.
Values:         integer

What:           /sys/devices/system/cpu/cpuX/topology/die_id
Description:    the CPU die ID of cpuX. Typically it is the hardware platform's
                identifier (rather than the kernel's). The actual value is
                architecture and platform dependent.
Values:         integer

What:           /sys/devices/system/cpu/cpuX/topology/core_id
Description:    the CPU core ID of cpuX. Typically it is the hardware platform's
                identifier (rather than the kernel's). The actual value is
                architecture and platform dependent.
Values:         integer

What:           /sys/devices/system/cpu/cpuX/topology/cluster_id
Description:    the cluster ID of cpuX.  Typically it is the hardware platform's
                identifier (rather than the kernel's). The actual value is
                architecture and platform dependent.
Values:         integer

What:           /sys/devices/system/cpu/cpuX/topology/book_id
Description:    the book ID of cpuX. Typically it is the hardware platform's
                identifier (rather than the kernel's). The actual value is
                architecture and platform dependent. it's only used on s390.
Values:         integer

What:           /sys/devices/system/cpu/cpuX/topology/drawer_id
Description:    the drawer ID of cpuX. Typically it is the hardware platform's
                identifier (rather than the kernel's). The actual value is
                architecture and platform dependent. it's only used on s390.
Values:         integer

What:           /sys/devices/system/cpu/cpuX/topology/core_cpus
Description:    internal kernel map of CPUs within the same core.
                (deprecated name: "thread_siblings")
Values:         hexadecimal bitmask.

What:           /sys/devices/system/cpu/cpuX/topology/core_cpus_list
Description:    human-readable list of CPUs within the same core.
                The format is like 0-3, 8-11, 14,17.
                (deprecated name: "thread_siblings_list").
Values:         decimal list.

What:           /sys/devices/system/cpu/cpuX/topology/package_cpus
Description:    internal kernel map of the CPUs sharing the same physical_package_id.
                (deprecated name: "core_siblings").
Values:         hexadecimal bitmask.

What:           /sys/devices/system/cpu/cpuX/topology/package_cpus_list
Description:    human-readable list of CPUs sharing the same physical_package_id.
                The format is like 0-3, 8-11, 14,17.
                (deprecated name: "core_siblings_list")
Values:         decimal list.

What:           /sys/devices/system/cpu/cpuX/topology/die_cpus
Description:    internal kernel map of CPUs within the same die.
Values:         hexadecimal bitmask.

What:           /sys/devices/system/cpu/cpuX/topology/ppin
Description:    per-socket protected processor inventory number
Values:         hexadecimal.

What:           /sys/devices/system/cpu/cpuX/topology/die_cpus_list
Description:    human-readable list of CPUs within the same die.
                The format is like 0-3, 8-11, 14,17.
Values:         decimal list.

What:           /sys/devices/system/cpu/cpuX/topology/cluster_cpus
Description:    internal kernel map of CPUs within the same cluster.
Values:         hexadecimal bitmask.

What:           /sys/devices/system/cpu/cpuX/topology/cluster_cpus_list
Description:    human-readable list of CPUs within the same cluster.
                The format is like 0-3, 8-11, 14,17.
Values:         decimal list.

What:           /sys/devices/system/cpu/cpuX/topology/book_siblings
Description:    internal kernel map of cpuX's hardware threads within the same
                book_id. it's only used on s390.
Values:         hexadecimal bitmask.

What:           /sys/devices/system/cpu/cpuX/topology/book_siblings_list
Description:    human-readable list of cpuX's hardware threads within the same
                book_id.
                The format is like 0-3, 8-11, 14,17. it's only used on s390.
Values:         decimal list.

What:           /sys/devices/system/cpu/cpuX/topology/drawer_siblings
Description:    internal kernel map of cpuX's hardware threads within the same
                drawer_id. it's only used on s390.
Values:         hexadecimal bitmask.

What:           /sys/devices/system/cpu/cpuX/topology/drawer_siblings_list
Description:    human-readable list of cpuX's hardware threads within the same
                drawer_id.
                The format is like 0-3, 8-11, 14,17. it's only used on s390.
Values:         decimal list.


code:
What:		/sys/devices/system/xen_memory/xen_memory0/max_retry_count
Date:		May 2011
KernelVersion:	2.6.39
Contact:	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Description:
		The maximum number of times the balloon driver will
		attempt to increase the balloon before giving up.  See
		also 'retry_count' below.
		A value of zero means retry forever and is the default one.

What:		/sys/devices/system/xen_memory/xen_memory0/max_schedule_delay
Date:		May 2011
KernelVersion:	2.6.39
Contact:	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Description:
		The limit that 'schedule_delay' (see below) will be
		increased to. The default value is 32 seconds.

What:		/sys/devices/system/xen_memory/xen_memory0/retry_count
Date:		May 2011
KernelVersion:	2.6.39
Contact:	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Description:
		The current number of times that the balloon driver
		has attempted to increase the size of the balloon.
		The default value is one. With max_retry_count being
		zero (unlimited), this means that the driver will attempt
		to retry with a 'schedule_delay' delay.

What:		/sys/devices/system/xen_memory/xen_memory0/schedule_delay
Date:		May 2011
KernelVersion:	2.6.39
Contact:	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Description:
		The time (in seconds) to wait between attempts to
		increase the balloon.  Each time the balloon cannot be
		increased, 'schedule_delay' is increased (until
		'max_schedule_delay' is reached at which point it
		will use the max value).

What:		/sys/devices/system/xen_memory/xen_memory0/target
Date:		April 2008
KernelVersion:	2.6.26
Contact:	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Description:
		The target number of pages to adjust this domain's
		memory reservation to.

What:		/sys/devices/system/xen_memory/xen_memory0/target_kb
Date:		April 2008
KernelVersion:	2.6.26
Contact:	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Description:
		As target above, except the value is in KiB.

What:		/sys/devices/system/xen_memory/xen_memory0/info/current_kb
Date:		April 2008
KernelVersion:	2.6.26
Contact:	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Description:
		Current size (in KiB) of this domain's memory
		reservation.

What:		/sys/devices/system/xen_memory/xen_memory0/info/high_kb
Date:		April 2008
KernelVersion:	2.6.26
Contact:	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Description:
		Amount (in KiB) of high memory in the balloon.

What:		/sys/devices/system/xen_memory/xen_memory0/info/low_kb
Date:		April 2008
KernelVersion:	2.6.26
Contact:	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Description:
		Amount (in KiB) of low (or normal) memory in the
		balloon.

What:		/sys/devices/system/xen_memory/xen_memory0/scrub_pages
Date:		September 2018
KernelVersion:	4.20
Contact:	xen-devel@lists.xenproject.org
Description:
		Control scrubbing pages before returning them to Xen for others domains
		use. Can be set with xen_scrub_pages cmdline
		parameter. Default value controlled with CONFIG_XEN_SCRUB_PAGES_DEFAULT.


code:
What:		/sys/bus/platform/drivers/aspeed-vuart/*/lpc_address
Date:		April 2017
Contact:	Jeremy Kerr <jk@ozlabs.org>
Description:	Configures which IO port the host side of the UART
		will appear on the host <-> BMC LPC bus.
Users:		OpenBMC.  Proposed changes should be mailed to
		openbmc@lists.ozlabs.org

What:		/sys/bus/platform/drivers/aspeed-vuart/*/sirq
Date:		April 2017
Contact:	Jeremy Kerr <jk@ozlabs.org>
Description:	Configures which interrupt number the host side of
		the UART will appear on the host <-> BMC LPC bus.
Users:		OpenBMC.  Proposed changes should be mailed to
		openbmc@lists.ozlabs.org

What:		/sys/bus/platform/drivers/aspeed-vuart/*/sirq_polarity
Date:		July 2019
Contact:	Oskar Senft <osk@google.com>
Description:	Configures the polarity of the serial interrupt to the
		host via the BMC LPC bus.
		Set to 0 for active-low or 1 for active-high.
Users:		OpenBMC.  Proposed changes should be mailed to
		openbmc@lists.ozlabs.org


code:
What:		/sys/bus/dsa/devices/dsa<m>/version
Date:		Apr 15, 2020
KernelVersion:	5.8.0
Contact:	dmaengine@vger.kernel.org
Description:	The hardware version number.

What:           /sys/bus/dsa/devices/dsa<m>/cdev_major
Date:           Oct 25, 2019
KernelVersion:  5.6.0
Contact:        dmaengine@vger.kernel.org
Description:	The major number that the character device driver assigned to
		this device.

What:           /sys/bus/dsa/devices/dsa<m>/errors
Date:           Oct 25, 2019
KernelVersion:  5.6.0
Contact:        dmaengine@vger.kernel.org
Description:    The error information for this device.

What:           /sys/bus/dsa/devices/dsa<m>/max_batch_size
Date:           Oct 25, 2019
KernelVersion:  5.6.0
Contact:        dmaengine@vger.kernel.org
Description:    The largest number of work descriptors in a batch.

What:           /sys/bus/dsa/devices/dsa<m>/max_work_queues_size
Date:           Oct 25, 2019
KernelVersion:  5.6.0
Contact:        dmaengine@vger.kernel.org
Description:    The maximum work queue size supported by this device.

What:           /sys/bus/dsa/devices/dsa<m>/max_engines
Date:           Oct 25, 2019
KernelVersion:  5.6.0
Contact:        dmaengine@vger.kernel.org
Description:    The maximum number of engines supported by this device.

What:           /sys/bus/dsa/devices/dsa<m>/max_groups
Date:           Oct 25, 2019
KernelVersion:  5.6.0
Contact:        dmaengine@vger.kernel.org
Description:    The maximum number of groups can be created under this device.

What:           /sys/bus/dsa/devices/dsa<m>/max_read_buffers
Date:           Dec 10, 2021
KernelVersion:  5.17.0
Contact:        dmaengine@vger.kernel.org
Description:    The total number of read buffers supported by this device.
		The read buffers represent resources within the DSA
		implementation, and these resources are allocated by engines to
		support operations. See DSA spec v1.2 9.2.4 Total Read Buffers.

What:           /sys/bus/dsa/devices/dsa<m>/max_transfer_size
Date:           Oct 25, 2019
KernelVersion:  5.6.0
Contact:        dmaengine@vger.kernel.org
Description:    The number of bytes to be read from the source address to
		perform the operation. The maximum transfer size is dependent on
		the workqueue the descriptor was submitted to.

What:           /sys/bus/dsa/devices/dsa<m>/max_work_queues
Date:           Oct 25, 2019
KernelVersion:  5.6.0
Contact:        dmaengine@vger.kernel.org
Description:    The maximum work queue number that this device supports.

What:           /sys/bus/dsa/devices/dsa<m>/numa_node
Date:           Oct 25, 2019
KernelVersion:  5.6.0
Contact:        dmaengine@vger.kernel.org
Description:    The numa node number for this device.

What:           /sys/bus/dsa/devices/dsa<m>/op_cap
Date:           Oct 25, 2019
KernelVersion:  5.6.0
Contact:        dmaengine@vger.kernel.org
Description:    The operation capability bit mask specify the operation types
		supported by the this device.

What:		/sys/bus/dsa/devices/dsa<m>/pasid_enabled
Date:		Oct 27, 2020
KernelVersion:	5.11.0
Contact:	dmaengine@vger.kernel.org
Description:	To indicate if PASID (process address space identifier) is
		enabled or not for this device.

What:           /sys/bus/dsa/devices/dsa<m>/state
Date:           Oct 25, 2019
KernelVersion:  5.6.0
Contact:        dmaengine@vger.kernel.org
Description:    The state information of this device. It can be either enabled
		or disabled.

What:           /sys/bus/dsa/devices/dsa<m>/group<m>.<n>
Date:           Oct 25, 2019
KernelVersion:  5.6.0
Contact:        dmaengine@vger.kernel.org
Description:    The assigned group under this device.

What:           /sys/bus/dsa/devices/dsa<m>/engine<m>.<n>
Date:           Oct 25, 2019
KernelVersion:  5.6.0
Contact:        dmaengine@vger.kernel.org
Description:    The assigned engine under this device.

What:           /sys/bus/dsa/devices/dsa<m>/wq<m>.<n>
Date:           Oct 25, 2019
KernelVersion:  5.6.0
Contact:        dmaengine@vger.kernel.org
Description:    The assigned work queue under this device.

What:           /sys/bus/dsa/devices/dsa<m>/configurable
Date:           Oct 25, 2019
KernelVersion:  5.6.0
Contact:        dmaengine@vger.kernel.org
Description:    To indicate if this device is configurable or not.

What:           /sys/bus/dsa/devices/dsa<m>/read_buffer_limit
Date:           Dec 10, 2021
KernelVersion:  5.17.0
Contact:        dmaengine@vger.kernel.org
Description:    The maximum number of read buffers that may be in use at
		one time by operations that access low bandwidth memory in the
		device. See DSA spec v1.2 9.2.8 GENCFG on Global Read Buffer Limit.

What:		/sys/bus/dsa/devices/dsa<m>/cmd_status
Date:		Aug 28, 2020
KernelVersion:	5.10.0
Contact:	dmaengine@vger.kernel.org
Description:	The last executed device administrative command's status/error.
		Also last configuration error overloaded.
		Writing to it will clear the status.

What:		/sys/bus/dsa/devices/wq<m>.<n>/block_on_fault
Date:		Oct 27, 2020
KernelVersion:	5.11.0
Contact:	dmaengine@vger.kernel.org
Description:	To indicate block on fault is allowed or not for the work queue
		to support on demand paging.

What:           /sys/bus/dsa/devices/wq<m>.<n>/group_id
Date:           Oct 25, 2019
KernelVersion:  5.6.0
Contact:        dmaengine@vger.kernel.org
Description:    The group id that this work queue belongs to.

What:           /sys/bus/dsa/devices/wq<m>.<n>/size
Date:           Oct 25, 2019
KernelVersion:  5.6.0
Contact:        dmaengine@vger.kernel.org
Description:    The work queue size for this work queue.

What:           /sys/bus/dsa/devices/wq<m>.<n>/type
Date:           Oct 25, 2019
KernelVersion:  5.6.0
Contact:        dmaengine@vger.kernel.org
Description:    The type of this work queue, it can be "kernel" type for work
		queue usages in the kernel space or "user" type for work queue
		usages by applications in user space.

What:           /sys/bus/dsa/devices/wq<m>.<n>/cdev_minor
Date:           Oct 25, 2019
KernelVersion:  5.6.0
Contact:        dmaengine@vger.kernel.org
Description:    The minor number assigned to this work queue by the character
		device driver.

What:           /sys/bus/dsa/devices/wq<m>.<n>/mode
Date:           Oct 25, 2019
KernelVersion:  5.6.0
Contact:        dmaengine@vger.kernel.org
Description:    The work queue mode type for this work queue.

What:           /sys/bus/dsa/devices/wq<m>.<n>/priority
Date:           Oct 25, 2019
KernelVersion:  5.6.0
Contact:        dmaengine@vger.kernel.org
Description:    The priority value of this work queue, it is a value relative to
		other work queue in the same group to control quality of service
		for dispatching work from multiple workqueues in the same group.

What:           /sys/bus/dsa/devices/wq<m>.<n>/state
Date:           Oct 25, 2019
KernelVersion:  5.6.0
Contact:        dmaengine@vger.kernel.org
Description:    The current state of the work queue.

What:           /sys/bus/dsa/devices/wq<m>.<n>/threshold
Date:           Oct 25, 2019
KernelVersion:  5.6.0
Contact:        dmaengine@vger.kernel.org
Description:    The number of entries in this work queue that may be filled
		via a limited portal.

What:		/sys/bus/dsa/devices/wq<m>.<n>/max_transfer_size
Date:		Aug 28, 2020
KernelVersion:	5.10.0
Contact:	dmaengine@vger.kernel.org
Description:	The max transfer sized for this workqueue. Cannot exceed device
		max transfer size. Configurable parameter.

What:		/sys/bus/dsa/devices/wq<m>.<n>/max_batch_size
Date:		Aug 28, 2020
KernelVersion:	5.10.0
Contact:	dmaengine@vger.kernel.org
Description:	The max batch size for this workqueue. Cannot exceed device
		max batch size. Configurable parameter.

What:		/sys/bus/dsa/devices/wq<m>.<n>/ats_disable
Date:		Nov 13, 2020
KernelVersion:	5.11.0
Contact:	dmaengine@vger.kernel.org
Description:	Indicate whether ATS disable is turned on for the workqueue.
		0 indicates ATS is on, and 1 indicates ATS is off for the workqueue.

What:		/sys/bus/dsa/devices/wq<m>.<n>/occupancy
Date		May 25, 2021
KernelVersion:	5.14.0
Contact:	dmaengine@vger.kernel.org
Description:	Show the current number of entries in this WQ if WQ Occupancy
		Support bit WQ capabilities is 1.

What:		/sys/bus/dsa/devices/wq<m>.<n>/enqcmds_retries
Date		Oct 29, 2021
KernelVersion:	5.17.0
Contact:	dmaengine@vger.kernel.org
Description:	Indicate the number of retires for an enqcmds submission on a sharedwq.
		A max value to set attribute is capped at 64.

What:		/sys/bus/dsa/devices/wq<m>.<n>/op_config
Date:		Sept 14, 2022
KernelVersion:	6.0.0
Contact:	dmaengine@vger.kernel.org
Description:	Shows the operation capability bits displayed in bitmap format
		presented by %*pb printk() output format specifier.
		The attribute can be configured when the WQ is disabled in
		order to configure the WQ to accept specific bits that
		correlates to the operations allowed. It's visible only
		on platforms that support the capability.

What:           /sys/bus/dsa/devices/engine<m>.<n>/group_id
Date:           Oct 25, 2019
KernelVersion:  5.6.0
Contact:        dmaengine@vger.kernel.org
Description:    The group that this engine belongs to.

What:		/sys/bus/dsa/devices/group<m>.<n>/use_read_buffer_limit
Date:		Dec 10, 2021
KernelVersion:	5.17.0
Contact:	dmaengine@vger.kernel.org
Description:	Enable the use of global read buffer limit for the group. See DSA
		spec v1.2 9.2.18 GRPCFG Use Global Read Buffer Limit.

What:		/sys/bus/dsa/devices/group<m>.<n>/read_buffers_allowed
Date:		Dec 10, 2021
KernelVersion:	5.17.0
Contact:	dmaengine@vger.kernel.org
Description:	Indicates max number of read buffers that may be in use at one time
		by all engines in the group. See DSA spec v1.2 9.2.18 GRPCFG Read
		Buffers Allowed.

What:		/sys/bus/dsa/devices/group<m>.<n>/read_buffers_reserved
Date:		Dec 10, 2021
KernelVersion:	5.17.0
Contact:	dmaengine@vger.kernel.org
Description:	Indicates the number of Read Buffers reserved for the use of
		engines in the group. See DSA spec v1.2 9.2.18 GRPCFG Read Buffers
		Reserved.

What:		/sys/bus/dsa/devices/group<m>.<n>/desc_progress_limit
Date:		Sept 14, 2022
KernelVersion:	6.0.0
Contact:	dmaengine@vger.kernel.org
Description:	Allows control of the number of work descriptors that can be
		concurrently processed by an engine in the group as a fraction
		of the Maximum Work Descriptors in Progress value specified in
		the ENGCAP register. The acceptable values are 0 (default),
		1 (1/2 of max value), 2 (1/4 of the max value), and 3 (1/8 of
		the max value). It's visible only on platforms that support
		the capability.

What:		/sys/bus/dsa/devices/group<m>.<n>/batch_progress_limit
Date:		Sept 14, 2022
KernelVersion:	6.0.0
Contact:	dmaengine@vger.kernel.org
Description:	Allows control of the number of batch descriptors that can be
		concurrently processed by an engine in the group as a fraction
		of the Maximum Batch Descriptors in Progress value specified in
		the ENGCAP register. The acceptable values are 0 (default),
		1 (1/2 of max value), 2 (1/4 of the max value), and 3 (1/8 of
		the max value). It's visible only on platforms that support
		the capability.


code:
What:           /sys/devices/pciXXXX:XX/0000:XX:XX.X/dma/dma<n>chan<n>/quickdata/cap
Date:           December 3, 2009
KernelVersion:  2.6.32
Contact:        dmaengine@vger.kernel.org
Description:	Capabilities the DMA supports.Currently there are DMA_PQ, DMA_PQ_VAL,
		DMA_XOR,DMA_XOR_VAL,DMA_INTERRUPT.

What:           /sys/devices/pciXXXX:XX/0000:XX:XX.X/dma/dma<n>chan<n>/quickdata/ring_active
Date:           December 3, 2009
KernelVersion:  2.6.32
Contact:        dmaengine@vger.kernel.org
Description:	The number of descriptors active in the ring.

What:           /sys/devices/pciXXXX:XX/0000:XX:XX.X/dma/dma<n>chan<n>/quickdata/ring_size
Date:           December 3, 2009
KernelVersion:  2.6.32
Contact:        dmaengine@vger.kernel.org
Description:	Descriptor ring size, total number of descriptors available.

What:           /sys/devices/pciXXXX:XX/0000:XX:XX.X/dma/dma<n>chan<n>/quickdata/version
Date:           December 3, 2009
KernelVersion:  2.6.32
Contact:        dmaengine@vger.kernel.org
Description:	Version of ioatdma device.

What:           /sys/devices/pciXXXX:XX/0000:XX:XX.X/dma/dma<n>chan<n>/quickdata/intr_coalesce
Date:           August 8, 2017
KernelVersion:  4.14
Contact:        dmaengine@vger.kernel.org
Description:	Tune-able interrupt delay value per channel basis.


code:
What:		/sys/devices/platform/firmware\:zynqmp-firmware/ggs*
Date:		March 2020
KernelVersion:	5.6
Contact:	"Jolly Shah" <jollys@xilinx.com>
Description:
		Read/Write PMU global general storage register value,
		GLOBAL_GEN_STORAGE{0:3}.
		Global general storage register that can be used
		by system to pass information between masters.

		The register is reset during system or power-on
		resets. Three registers are used by the FSBL and
		other Xilinx software products: GLOBAL_GEN_STORAGE{4:6}.

		Usage::

		    # cat /sys/devices/platform/firmware\:zynqmp-firmware/ggs0
		    # echo <value> > /sys/devices/platform/firmware\:zynqmp-firmware/ggs0

		Example::

		    # cat /sys/devices/platform/firmware\:zynqmp-firmware/ggs0
		    # echo 0x1234ABCD > /sys/devices/platform/firmware\:zynqmp-firmware/ggs0

Users:		Xilinx

What:		/sys/devices/platform/firmware\:zynqmp-firmware/pggs*
Date:		March 2020
KernelVersion:	5.6
Contact:	"Jolly Shah" <jollys@xilinx.com>
Description:
		Read/Write PMU persistent global general storage register
		value, PERS_GLOB_GEN_STORAGE{0:3}.
		Persistent global general storage register that
		can be used by system to pass information between
		masters.

		This register is only reset by the power-on reset
		and maintains its value through a system reset.
		Four registers are used by the FSBL and other Xilinx
		software products: PERS_GLOB_GEN_STORAGE{4:7}.
		Register is reset only by a POR reset.

		Usage::

		    # cat /sys/devices/platform/firmware\:zynqmp-firmware/pggs0
		    # echo <value> > /sys/devices/platform/firmware\:zynqmp-firmware/pggs0

		Example::

		    # cat /sys/devices/platform/firmware\:zynqmp-firmware/pggs0
		    # echo 0x1234ABCD > /sys/devices/platform/firmware\:zynqmp-firmware/pggs0

Users:		Xilinx

What:		/sys/devices/platform/firmware\:zynqmp-firmware/shutdown_scope
Date:		March 2020
KernelVersion:	5.6
Contact:	"Jolly Shah" <jollys@xilinx.com>
Description:
		This sysfs interface allows to set the shutdown scope for the
		next shutdown request. When the next shutdown is performed, the
		platform specific portion of PSCI-system_off can use the chosen
		shutdown scope.

		Following are available shutdown scopes(subtypes):

		subsystem:
				Only the APU along with all of its peripherals
				not used by other processing units will be
				shut down. This may result in the FPD power
				domain being shut down provided that no other
				processing unit uses FPD peripherals or DRAM.
		ps_only:
				The complete PS will be shut down, including the
				RPU, PMU, etc.  Only the PL domain (FPGA)
				remains untouched.
		system:
				The complete system/device is shut down.

		Usage::

		    # cat /sys/devices/platform/firmware\:zynqmp-firmware/shutdown_scope
		    # echo <scope> > /sys/devices/platform/firmware\:zynqmp-firmware/shutdown_scope

		Example::

		    # cat /sys/devices/platform/firmware\:zynqmp-firmware/shutdown_scope
		    # echo "subsystem" > /sys/devices/platform/firmware\:zynqmp-firmware/shutdown_scope

Users:		Xilinx

What:		/sys/devices/platform/firmware\:zynqmp-firmware/health_status
Date:		March 2020
KernelVersion:	5.6
Contact:	"Jolly Shah" <jollys@xilinx.com>
Description:
		This sysfs interface allows to set the health status. If PMUFW
		is compiled with CHECK_HEALTHY_BOOT, it will check the healthy
		bit on FPD WDT expiration. If healthy bit is set by a user
		application running in Linux, PMUFW will do APU only restart. If
		healthy bit is not set during FPD WDT expiration, PMUFW will do
		system restart.

		Usage:

		Set healthy bit::

		    # echo 1 > /sys/devices/platform/firmware\:zynqmp-firmware/health_status

		Unset healthy bit::

		    # echo 0 > /sys/devices/platform/firmware\:zynqmp-firmware/health_status

Users:		Xilinx

What:		/sys/devices/platform/firmware\:zynqmp-firmware/feature_config_id
Date:		Feb 2022
KernelVersion:	5.18
Contact:	"Ronak Jain" <ronak.jain@xilinx.com>
Description:
		This sysfs interface allows user to configure features at
		runtime. The user can enable or disable features running at
		firmware as well as the user can configure the parameters of
		the features at runtime. The supported features are over
		temperature and external watchdog. Here, the external watchdog
		is completely different than the /dev/watchdog as the external
		watchdog is running on the firmware and it is used to monitor
		the health of firmware not APU(Linux). Also, the external
		watchdog is interfaced outside of the zynqmp soc.

		The supported config ids are for the feature configuration is,
		1. PM_FEATURE_OVERTEMP_STATUS = 1, the user can enable or
		disable the over temperature feature.
		2. PM_FEATURE_OVERTEMP_VALUE = 2, the user can configure the
		over temperature limit in Degree Celsius.
		3. PM_FEATURE_EXTWDT_STATUS = 3, the user can enable or disable
		the external watchdog feature.
		4. PM_FEATURE_EXTWDT_VALUE = 4, the user can configure the
		external watchdog feature.

		Usage:

		Select over temperature config ID to enable/disable feature
		# echo 1 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_id

		Check over temperature config ID is selected or not
		# cat /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_id
		The expected result is 1.

		Select over temperature config ID to configure OT limit
		# echo 2 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_id

		Check over temperature config ID is selected or not
		# cat /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_id
		The expected result is 2.

		Select external watchdog config ID to enable/disable feature
		# echo 3 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_id

		Check external watchdog config ID is selected or not
		# cat /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_id
		The expected result is 3.

		Select external watchdog config ID to configure time interval
		# echo 4 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_id

		Check external watchdog config ID is selected or not
		# cat /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_id
		The expected result is 4.

Users:		Xilinx

What:		/sys/devices/platform/firmware\:zynqmp-firmware/feature_config_value
Date:		Feb 2022
KernelVersion:	5.18
Contact:	"Ronak Jain" <ronak.jain@xilinx.com>
Description:
		This sysfs interface allows to configure features at runtime.
		The user can enable or disable features running at firmware.
		Also, the user can configure the parameters of the features
		at runtime. The supported features are over temperature and
		external watchdog. Here, the external watchdog is completely
		different than the /dev/watchdog as the external watchdog is
		running on the firmware and it is used to monitor the health
		of firmware not APU(Linux). Also, the external watchdog is
		interfaced outside of the zynqmp soc.

		By default the features are disabled in the firmware. The user
		can enable features by querying appropriate config id of the
		features.

		The default limit for the over temperature is 90 Degree Celsius.
		The default timer interval for the external watchdog is 570ms.

		The supported config ids are for the feature configuration is,
		1. PM_FEATURE_OVERTEMP_STATUS = 1, the user can enable or
		disable the over temperature feature.
		2. PM_FEATURE_OVERTEMP_VALUE = 2, the user can configure the
		over temperature limit in Degree Celsius.
		3. PM_FEATURE_EXTWDT_STATUS = 3, the user can enable or disable
		the external watchdog feature.
		4. PM_FEATURE_EXTWDT_VALUE = 4, the user can configure the
		external watchdog feature.

		Usage:

		Enable over temperature feature
		# echo 1 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_id
		# echo 1 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_value

		Check whether the over temperature feature is enabled or not
		# cat /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_value
		The expected result is 1.

		Disable over temperature feature
		# echo 1 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_id
		# echo 0 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_value

		Check whether the over temperature feature is disabled or not
		# cat /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_value
		The expected result is 0.

		Configure over temperature limit to 50 Degree Celsius
		# echo 2 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_id
		# echo 50 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_value

		Check whether the over temperature limit is configured or not
		# cat /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_value
		The expected result is 50.

		Enable external watchdog feature
		# echo 3 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_id
		# echo 1 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_value

		Check whether the external watchdog feature is enabled or not
		# cat /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_value
		The expected result is 1.

		Disable external watchdog feature
		# echo 3 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_id
		# echo 0 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_value

		Check whether the external watchdog feature is disabled or not
		# cat /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_value
		The expected result is 0.

		Configure external watchdog timer interval to 500ms
		# echo 4 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_id
		# echo 500 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_value

		Check whether the external watchdog timer interval is configured or not
		# cat /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_value
		The expected result is 500.

Users:		Xilinx


code:
What:		/sys/class/infiniband_srp/srp-<hca>-<port_number>/add_target
Date:		January 2, 2006
KernelVersion:	2.6.15
Contact:	linux-rdma@vger.kernel.org
Description:	Interface for making ib_srp connect to a new target.
		One can request ib_srp to connect to a new target by writing
		a comma-separated list of login parameters to this sysfs
		attribute. The supported parameters are:

		* id_ext, a 16-digit hexadecimal number specifying the eight
		  byte identifier extension in the 16-byte SRP target port
		  identifier. The target port identifier is sent by ib_srp
		  to the target in the SRP_LOGIN_REQ request.
		* ioc_guid, a 16-digit hexadecimal number specifying the eight
		  byte I/O controller GUID portion of the 16-byte target port
		  identifier.
		* dgid, a 32-digit hexadecimal number specifying the
		  destination GID.
		* pkey, a four-digit hexadecimal number specifying the
		  InfiniBand partition key.
		* service_id, a 16-digit hexadecimal number specifying the
		  InfiniBand service ID used to establish communication with
		  the SRP target. How to find out the value of the service ID
		  is specified in the documentation of the SRP target.
		* max_sect, a decimal number specifying the maximum number of
		  512-byte sectors to be transferred via a single SCSI command.
		* max_cmd_per_lun, a decimal number specifying the maximum
		  number of outstanding commands for a single LUN.
		* io_class, a hexadecimal number specifying the SRP I/O class.
		  Must be either 0xff00 (rev 10) or 0x0100 (rev 16a). The I/O
		  class defines the format of the SRP initiator and target
		  port identifiers.
		* initiator_ext, a 16-digit hexadecimal number specifying the
		  identifier extension portion of the SRP initiator port
		  identifier. This data is sent by the initiator to the target
		  in the SRP_LOGIN_REQ request.
		* cmd_sg_entries, a number in the range 1..255 that specifies
		  the maximum number of data buffer descriptors stored in the
		  SRP_CMD information unit itself. With allow_ext_sg=0 the
		  parameter cmd_sg_entries defines the maximum S/G list length
		  for a single SRP_CMD, and commands whose S/G list length
		  exceeds this limit after S/G list collapsing will fail.
		* allow_ext_sg, whether ib_srp is allowed to include a partial
		  memory descriptor list in an SRP_CMD instead of the entire
		  list. If a partial memory descriptor list has been included
		  in an SRP_CMD the remaining memory descriptors are
		  communicated from initiator to target via an additional RDMA
		  transfer. Setting allow_ext_sg to 1 increases the maximum
		  amount of data that can be transferred between initiator and
		  target via a single SCSI command. Since not all SRP target
		  implementations support partial memory descriptor lists the
		  default value for this option is 0.
		* sg_tablesize, a number in the range 1..2048 specifying the
		  maximum S/G list length the SCSI layer is allowed to pass to
		  ib_srp. Specifying a value that exceeds cmd_sg_entries is
		  only safe with partial memory descriptor list support enabled
		  (allow_ext_sg=1).
		* comp_vector, a number in the range 0..n-1 specifying the
		  MSI-X completion vector of the first RDMA channel. Some
		  HCA's allocate multiple (n) MSI-X vectors per HCA port. If
		  the IRQ affinity masks of these interrupts have been
		  configured such that each MSI-X interrupt is handled by a
		  different CPU then the comp_vector parameter can be used to
		  spread the SRP completion workload over multiple CPU's.
		* tl_retry_count, a number in the range 2..7 specifying the
		  IB RC retry count.
		* queue_size, the maximum number of commands that the
		  initiator is allowed to queue per SCSI host. The default
		  value for this parameter is 62. The lowest supported value
		  is 2.
		* max_it_iu_size, a decimal number specifying the maximum
		  initiator to target information unit length.

What:		/sys/class/infiniband_srp/srp-<hca>-<port_number>/ibdev
Date:		January 2, 2006
KernelVersion:	2.6.15
Contact:	linux-rdma@vger.kernel.org
Description:	HCA name (<hca>).

What:		/sys/class/infiniband_srp/srp-<hca>-<port_number>/port
Date:		January 2, 2006
KernelVersion:	2.6.15
Contact:	linux-rdma@vger.kernel.org
Description:	HCA port number (<port_number>).

What:		/sys/class/scsi_host/host<n>/allow_ext_sg
Date:		May 19, 2011
KernelVersion:	2.6.39
Contact:	linux-rdma@vger.kernel.org
Description:	Whether ib_srp is allowed to include a partial memory
		descriptor list in an SRP_CMD when communicating with an SRP
		target.

What:		/sys/class/scsi_host/host<n>/ch_count
Date:		April 1, 2015
KernelVersion:	3.19
Contact:	linux-rdma@vger.kernel.org
Description:	Number of RDMA channels used for communication with the SRP
		target.

What:		/sys/class/scsi_host/host<n>/cmd_sg_entries
Date:		May 19, 2011
KernelVersion:	2.6.39
Contact:	linux-rdma@vger.kernel.org
Description:	Maximum number of data buffer descriptors that may be sent to
		the target in a single SRP_CMD request.

What:		/sys/class/scsi_host/host<n>/comp_vector
Date:		September 2, 2013
KernelVersion:	3.11
Contact:	linux-rdma@vger.kernel.org
Description:	Completion vector used for the first RDMA channel.

What:		/sys/class/scsi_host/host<n>/dgid
Date:		June 17, 2006
KernelVersion:	2.6.17
Contact:	linux-rdma@vger.kernel.org
Description:	InfiniBand destination GID used for communication with the SRP
		target. Differs from orig_dgid if port redirection has happened.

What:		/sys/class/scsi_host/host<n>/id_ext
Date:		June 17, 2006
KernelVersion:	2.6.17
Contact:	linux-rdma@vger.kernel.org
Description:	Eight-byte identifier extension portion of the 16-byte target
		port identifier.

What:		/sys/class/scsi_host/host<n>/ioc_guid
Date:		June 17, 2006
KernelVersion:	2.6.17
Contact:	linux-rdma@vger.kernel.org
Description:	Eight-byte I/O controller GUID portion of the 16-byte target
		port identifier.

What:		/sys/class/scsi_host/host<n>/local_ib_device
Date:		November 29, 2006
KernelVersion:	2.6.19
Contact:	linux-rdma@vger.kernel.org
Description:	Name of the InfiniBand HCA used for communicating with the
		SRP target.

What:		/sys/class/scsi_host/host<n>/local_ib_port
Date:		November 29, 2006
KernelVersion:	2.6.19
Contact:	linux-rdma@vger.kernel.org
Description:	Number of the HCA port used for communicating with the
		SRP target.

What:		/sys/class/scsi_host/host<n>/orig_dgid
Date:		June 17, 2006
KernelVersion:	2.6.17
Contact:	linux-rdma@vger.kernel.org
Description:	InfiniBand destination GID specified in the parameters
		written to the add_target sysfs attribute.

What:		/sys/class/scsi_host/host<n>/pkey
Date:		June 17, 2006
KernelVersion:	2.6.17
Contact:	linux-rdma@vger.kernel.org
Description:	A 16-bit number representing the InfiniBand partition key used
		for communication with the SRP target.

What:		/sys/class/scsi_host/host<n>/req_lim
Date:		October 20, 2010
KernelVersion:	2.6.36
Contact:	linux-rdma@vger.kernel.org
Description:	Number of requests ib_srp can send to the target before it has
		to wait for more credits. For more information see also the
		SRP credit algorithm in the SRP specification.

What:		/sys/class/scsi_host/host<n>/service_id
Date:		June 17, 2006
KernelVersion:	2.6.17
Contact:	linux-rdma@vger.kernel.org
Description:	InfiniBand service ID used for establishing communication with
		the SRP	target.

What:		/sys/class/scsi_host/host<n>/sgid
Date:		February 1, 2014
KernelVersion:	3.13
Contact:	linux-rdma@vger.kernel.org
Description:	InfiniBand GID of the source port used for communication with
		the SRP target.

What:		/sys/class/scsi_host/host<n>/zero_req_lim
Date:		September 20, 2006
KernelVersion:	2.6.18
Contact:	linux-rdma@vger.kernel.org
Description:	Number of times the initiator had to wait before sending a
		request to the target because it ran out of credits. For more
		information see also the SRP credit algorithm in the SRP
		specification.


code:
What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/asic_health
Date:		June 2018
KernelVersion:	4.19
Contact:	Vadim Pasternak <vadimp@nvidia.com>
Description:	This file shows ASIC health status. The possible values are:
		0 - health failed, 2 - health OK, 3 - ASIC in booting state.

		The files are read only.

What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/cpld1_version
What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/cpld2_version
Date:		June 2018
KernelVersion:	4.19
Contact:	Vadim Pasternak <vadimp@nvidia.com>
Description:	These files show with which CPLD versions have been burned
		on carrier and switch boards.

		The files are read only.

What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/fan_dir
Date:		December 2018
KernelVersion:	5.0
Contact:	Vadim Pasternak <vadimp@nvidia.com>
Description:	This file shows the system fans direction:
		forward direction - relevant bit is set 0;
		reversed direction - relevant bit is set 1.

		The files are read only.

What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/cpld3_version
Date:		November 2018
KernelVersion:	5.0
Contact:	Vadim Pasternak <vadimp@nvidia.com>
Description:	These files show with which CPLD versions have been burned
		on LED or Gearbox board.

		The files are read only.

What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/jtag_enable
Date:		November 2018
KernelVersion:	5.0
Contact:	Vadim Pasternak <vadimp@nvidia.com>
Description:	These files enable and disable the access to the JTAG domain.
		By default access to the JTAG domain is disabled.

		The file is read/write.

What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/select_iio
Date:		June 2018
KernelVersion:	4.19
Contact:	Vadim Pasternak <vadimp@nvidia.com>
Description:	This file allows iio devices selection.

		Attribute select_iio can be written with 0 or with 1. It
		selects which one of iio devices can be accessed.

		The file is read/write.

What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/psu1_on
		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/psu2_on
		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/pwr_cycle
		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/pwr_down
Date:		June 2018
KernelVersion:	4.19
Contact:	Vadim Pasternak <vadimp@nvidia.com>
Description:	These files allow asserting system power cycling, switching
		power supply units on and off and system's main power domain
		shutdown.
		Expected behavior:
		When pwr_cycle is written 1: auxiliary power domain will go
		down and after short period (about 1 second) up.
		When  psu1_on or psu2_on is written 1, related unit will be
		disconnected from the power source, when written 0 - connected.
		If both are written 1 - power supplies main power domain will
		go down.
		When pwr_down is written 1, system's main power domain will go
		down.

		The files are write only.

What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/reset_aux_pwr_or_ref
What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/reset_asic_thermal
What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/reset_hotswap_or_halt
What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/reset_hotswap_or_wd
What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/reset_fw_reset
What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/reset_long_pb
What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/reset_main_pwr_fail
What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/reset_short_pb
What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/reset_sw_reset
Date:		June 2018
KernelVersion:	4.19
Contact:	Vadim Pasternak <vadimp@nvidia.com>
Description:	These files show the system reset cause, as following: power
		auxiliary outage or power refresh, ASIC thermal shutdown, halt,
		hotswap, watchdog, firmware reset, long press power button,
		short press power button, software reset. Value 1 in file means
		this is reset cause, 0 - otherwise. Only one of the above
		causes could be 1 at the same time, representing only last
		reset cause.

		The files are read only.

What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/reset_comex_pwr_fail
What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/reset_from_comex
What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/reset_system
What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/reset_voltmon_upgrade_fail
Date:		November 2018
KernelVersion:	5.0
Contact:	Vadim Pasternak <vadimp@nvidia.com>
Description:	These files show the system reset cause, as following: ComEx
		power fail, reset from ComEx, system platform reset, reset
		due to voltage monitor devices upgrade failure,
		Value 1 in file means this is reset cause, 0 - otherwise.
		Only one bit could be 1 at the same time, representing only
		the last reset cause.

		The files are read only.

What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/cpld4_version
Date:		November 2018
KernelVersion:	5.0
Contact:	Vadim Pasternak <vadimp@nvidia.com>
Description:	These files show with which CPLD versions have been burned
		on LED board.

		The files are read only.

What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/reset_comex_thermal
What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/reset_comex_wd
What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/reset_from_asic
What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/reset_reload_bios
What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/reset_sff_wd
What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/reset_swb_wd
Date:		June 2019
KernelVersion:	5.3
Contact:	Vadim Pasternak <vadimp@nvidia.com>
Description:	These files show the system reset cause, as following:
		COMEX thermal shutdown; wathchdog power off or reset was derived
		by one of the next components: COMEX, switch board or by Small Form
		Factor mezzanine, reset requested from ASIC, reset caused by BIOS
		reload. Value 1 in file means this is reset cause, 0 - otherwise.
		Only one of the above causes could be 1 at the same time, representing
		only last reset cause.

		The files are read only.

What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/config1
What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/config2
Date:		January 2020
KernelVersion:	5.6
Contact:	Vadim Pasternak <vadimp@nvidia.com>
Description:	These files show system static topology identification
		like system's static I2C topology, number and type of FPGA
		devices within the system and so on.

		The files are read only.

What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/reset_ac_pwr_fail
What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/reset_platform
What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/reset_soc
What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/reset_sw_pwr_off
Date:		January 2020
KernelVersion:	5.6
Contact:	Vadim Pasternak <vadimp@nvidia.com>
Description:	These files show the system reset causes, as following: reset
		due to AC power failure, reset invoked from software by
		assertion reset signal through CPLD. reset caused by signal
		asserted by SOC through ACPI register, reset invoked from
		software by assertion power off signal through CPLD.

		The files are read only.

What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/pcie_asic_reset_dis
Date:		January 2020
KernelVersion:	5.6
Contact:	Vadim Pasternak <vadimp@nvidia.com>
Description:	This file allows to retain ASIC up during PCIe root complex
		reset, when attribute is set 1.

		The file is read/write.

What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/vpd_wp
Date:		January 2020
KernelVersion:	5.6
Contact:	Vadim Pasternak <vadimp@nvidia.com>
Description:	This file allows to overwrite system VPD hardware write
		protection when attribute is set 1.

		The file is read/write.

What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/voltreg_update_status
Date:		January 2020
KernelVersion:	5.6
Contact:	Vadim Pasternak <vadimp@nvidia.com>
Description:	This file exposes the configuration update status of burnable
		voltage regulator devices. The status values are as following:
		0 - OK; 1 - CRC failure; 2 = I2C failure; 3 - in progress.

		The file is read only.

What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/ufm_version
Date:		January 2020
KernelVersion:	5.6
Contact:	Vadim Pasternak <vadimp@nvidia.com>
Description:	This file exposes the firmware version of burnable voltage
		regulator devices.

		The file is read only.

What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/cpld1_pn
What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/cpld2_pn
What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/cpld3_pn
What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/cpld4_pn
What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/cpld1_version_min
What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/cpld2_version_min
What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/cpld3_version_min
What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/cpld4_version_min
Date:		July 2020
KernelVersion:	5.9
Contact:	Vadim Pasternak <vadimp@nvidia.com>
Description:	These files show with which CPLD part numbers and minor
		versions have been burned CPLD devices equipped on a
		system.

		The files are read only.

What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/bios_active_image
What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/bios_auth_fail
What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/bios_upgrade_fail
Date:		October 2021
KernelVersion:	5.16
Contact:	Vadim Pasternak <vadimp@nvidia.com>
Description:	The files represent BIOS statuses:

		bios_active_image: location of current active BIOS image:
		0: Top, 1: Bottom.
		The reported value should correspond to value expected by OS
		in case of BIOS safe mode is 0. This bit is related to Intel
		top-swap feature of DualBios on the same flash.

		bios_auth_fail: BIOS upgrade is failed because provided BIOS
		image is not signed correctly.

		bios_upgrade_fail: BIOS upgrade is failed by some other
		reason not because authentication. For example due to
		physical SPI flash problem.

		The files are read only.

What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc1_enable
What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc2_enable
What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc3_enable
What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc4_enable
What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc5_enable
What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc6_enable
What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc7_enable
What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc8_enable
Date:		October 2021
KernelVersion:	5.16
Contact:	Vadim Pasternak <vadimp@nvidia.com>
Description:	These files allow line cards enable state control.
		Expected behavior:
		When  lc{n}_enable is written 1, related line card is released
		from the reset state, when 0 - is hold in reset state.

		The files are read/write.

What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc1_pwr
What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc2_pwr
What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc3_pwr
What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc4_pwr
What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc5_pwr
What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc6_pwr
What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc7_pwr
What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc8_pwr
Date:		October 2021
KernelVersion:	5.16
Contact:	Vadim Pasternak <vadimp@nvidia.com>
Description:	These files switching line cards power on and off.
		Expected behavior:
		When  lc{n}_pwr is written 1, related line card is powered
		on, when written 0 - powered off.

		The files are read/write.

What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc1_rst_mask
What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc2_rst_mask
What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc3_rst_mask
What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc4_rst_mask
What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc5_rst_mask
What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc6_rst_mask
What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc7_rst_mask
What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/lc8_rst_mask
Date:		October 2021
KernelVersion:	5.16
Contact:	Vadim Pasternak <vadimp@nvidia.com>
Description:	These files clear line card reset bit enforced by ASIC, when it
		sets it due to some abnormal ASIC behavior.
		Expected behavior:
		When lc{n}_rst_mask is written 1, related line card reset bit
		is cleared, when written 0 - no effect.

		The files are write only.

What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/os_started
Date:		October 2021
KernelVersion:	5.16
Contact:	Vadim Pasternak <vadimp@nvidia.com>
Description:	This file, when written 1, indicates to programmable devices
		that OS is taking control over it.

		The file is read/write.

What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/pm_mgmt_en
Date:		October 2021
KernelVersion:	5.16
Contact:	Vadim Pasternak <vadimp@nvidia.com>
Description:	This file assigns power management control ownership.
		When power management control is provided by hardware, hardware
		will automatically power off one or more line previously
		powered line cards in case system power budget is getting
		insufficient. It could be in case when some of power units lost
		power good state.
		When pm_mgmt_en is written 1, power management control by
		software is enabled, 0 - power management control by hardware.
		Note that for any setting of pm_mgmt_en attribute hardware will
		not allow to power on any new line card in case system power
		budget is insufficient.
		Same in case software will try to power on several line cards
		at once - hardware will power line cards while system has
		enough power budget.
		Default is 0.

		The file is read/write.

What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/psu3_on
What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/psu4_on
Date:		October 2021
KernelVersion:	5.16
Contact:	Vadim Pasternak <vadimp@nvidia.com>
Description:	These files switching power supply units on and off.
		Expected behavior:
		When  psu3_on or psu4_on is written 1, related unit will be
		disconnected from the power source, when written 0 - connected.

		The files are write only.

What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/shutdown_unlock
Date:		October 2021
KernelVersion:	5.16
Contact:	Vadim Pasternak <vadimp@nvidia.com>
Description:	This file allows to unlock ASIC after thermal shutdown event.
		When system thermal shutdown is enforced by ASIC, ASIC is
		getting locked and after system boot it will not be available.
		Software can decide to unlock it by setting this attribute to
		1 and then perform system power cycle by setting pwr_cycle
		attribute to 1 (power cycle of main power domain).
		Before setting shutdown_unlock to 1 it is recommended to
		validate that system reboot cause is reset_asic_thermal or
		reset_thermal_spc_or_pciesw.
		In case shutdown_unlock is not set 1, the only way to release
		ASIC from locking - is full system power cycle through the
		external power distribution unit.
		Default is 1.

		The file is read/write.

What:		/sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/cpld1_pn
What:		/sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/cpld1_version
What:		/sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/cpld1_version_min
Date:		October 2021
KernelVersion:	5.16
Contact:	Vadim Pasternak <vadimp@nvidia.com>
Description:	These files show with which CPLD major and minor versions
		and part number has been burned CPLD device on line card.

		The files are read only.

What:		/sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/fpga1_pn
What:		/sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/fpga1_version
What:		/sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/fpga1_version_min
Date:		October 2021
KernelVersion:	5.16
Contact:	Vadim Pasternak <vadimp@nvidia.com>
Description:	These files show with which FPGA major and minor versions
		and part number has been burned FPGA device on line card.

		The files are read only.

What:		/sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/vpd_wp
Date:		October 2021
KernelVersion:	5.16
Contact:	Vadim Pasternak <vadimp@nvidia.com>
Description:	This file allow to overwrite line card VPD hardware write
		protection mode. When attribute is set 1 - write protection is
		disabled, when 0 - enabled.
		Default is 0.
		If the system is in locked-down mode writing this file will not
		be allowed.
		The purpose if this file is to allow line card VPD burning
		during production flow.

		The file is read/write.

What:		/sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/reset_aux_pwr_or_ref
What:		/sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/reset_dc_dc_pwr_fail
What:		/sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/reset_fpga_not_done
What:		/sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/reset_from_chassis
What:		/sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/reset_line_card
What:		/sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/reset_pwr_off_from_chassis
Date:		October 2021
KernelVersion:	5.16
Contact:	Vadim Pasternak <vadimp@nvidia.com>
Description:	These files show the line reset cause, as following: power
		auxiliary outage or power refresh, DC-to-DC power failure, FPGA reset
		failed, line card reset failed, power off from chassis.
		Value 1 in file means this is reset cause, 0 - otherwise. Only one of
		the above causes could be 1 at the same time, representing only last
		reset cause.

		The files are read only.

What:		/sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/cpld_upgrade_en
What:		/sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/fpga_upgrade_en
Date:		October 2021
KernelVersion:	5.16
Contact:	Vadim Pasternak <vadimp@nvidia.com>
Description:	These files allow CPLD and FPGA burning. Value 1 in file means burning
		is enabled, 0 - otherwise.
		If the system is in locked-down mode writing these files will
		not be allowed.
		The purpose of these files to allow line card CPLD and FPGA
		upgrade through the JTAG daisy-chain.

		The files are read/write.

What:		/sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/qsfp_pwr_en
What:		/sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/pwr_en
Date:		October 2021
KernelVersion:	5.16
Contact:	Vadim Pasternak <vadimp@nvidia.com>
Description:	These files allow to power on/off all QSFP ports and whole line card.
		The attributes are set 1 for power on, 0 - for power off.

		The files are read/write.

What:		/sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/agb_spi_burn_en
What:		/sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/fpga_spi_burn_en
Date:		October 2021
KernelVersion:	5.16
Contact:	Vadim Pasternak <vadimp@nvidia.com>
Description:	These files allow gearboxes and FPGA SPI flash burning.
		The attributes are set 1 to enable burning, 0 - to disable.
		If the system is in locked-down mode writing these files will
		not be allowed.
		The purpose of these files to allow line card Gearboxes and FPGA
		burning during production flow.

		The file is read/write.

What:		/sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/max_power
What:		/sys/devices/platform/mlxplat/i2c_mlxcpld.*/i2c-*/i2c-*/i2c-*/*-0032/mlxreg-io.*/hwmon/hwmon*/config
Date:		October 2021
KernelVersion:	5.16
Contact:	Vadim Pasternak <vadimp@nvidia.com>
Description:	These files provide the maximum powered required for line card
		feeding and line card configuration Id.

		The files are read only.

What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/phy_reset
Date:		May 2022
KernelVersion:	5.19
Contact:	Vadim Pasternak <vadimp@nvidia.com>
Description:	This file allows to reset PHY 88E1548 when attribute is set 0
		due to some abnormal PHY behavior.
		Expected behavior:
		When phy_reset is written 1, all PHY 88E1548 are released
		from the reset state, when 0 - are hold in reset state.

		The files are read/write.

What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/mac_reset
Date:		May 2022
KernelVersion:	5.19
Contact:	Vadim Pasternak <vadimp@nvidia.com>
Description:	This file allows to reset ASIC MT52132 when attribute is set 0
		due to some abnormal ASIC behavior.
		Expected behavior:
		When mac_reset is written 1, the ASIC MT52132 is released
		from the reset state, when 0 - is hold in reset state.

		The files are read/write.

What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/qsfp_pwr_good
Date:		May 2022
KernelVersion:	5.19
Contact:	Vadim Pasternak <vadimp@nvidia.com>
Description:	This file shows QSFP ports power status. The value is set to 0
		when one of any QSFP ports is plugged. The value is set to 1 when
		there are no any QSFP ports are plugged.
		The possible values are:
		0 - Power good, 1 - Not power good.

		The files are read only.

What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/asic2_health
Date:		July 2022
KernelVersion:	5.20
Contact:	Vadim Pasternak <vadimp@nvidia.com>
Description:	This file shows 2-nd ASIC health status. The possible values are:
		0 - health failed, 2 - health OK, 3 - ASIC in booting state.

		The file is read only.

What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/asic_reset
What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/asic2_reset
Date:		July 2022
KernelVersion:	5.20
Contact:	Vadim Pasternak <vadimp@nvidia.com>
Description:	These files allow to each of ASICs by writing 1.

		The files are write only.

What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/comm_chnl_ready
Date:		July 2022
KernelVersion:	5.20
Contact:	Vadim Pasternak <vadimp@nvidia.com>
Description:	This file is used to indicate remote end (for example BMC) that system
	        host CPU is ready for sending telemetry data to remote end.
		For indication the file should be written 1.

		The file is write only.

What:		/sys/devices/platform/mlxplat/mlxreg-io/hwmon/hwmon*/config3
Date:		January 2020
KernelVersion:	5.6
Contact:	Vadim Pasternak <vadimp@nvidia.com>
Description:	The file indicates COME module hardware configuration.
		The value is pushed by hardware through GPIO pins.
		The purpose is to expose some minor BOM changes for the same system SKU.

		The file is read only.


code:
What:		/sys/bus/pci/drivers/qla2xxx/.../devices/*
Date:		September 2009
Contact:	QLogic Linux Driver <linux-driver@qlogic.com>
Description:	qla2xxx-udev.sh currently looks for uevent CHANGE events to
		signal a firmware-dump has been generated by the driver and is
		ready for retrieval.
Users:		qla2xxx-udev.sh.  Proposed changes should be mailed to
		linux-driver@qlogic.com


code:
What:		/sys/accessibility/speakup/attrib_bleep
KernelVersion:	2.6
Contact:	speakup@linux-speakup.org
Description:	Beeps the PC speaker when there is an attribute change such as
		foreground or background color when using speakup review
		commands. One = on, zero = off.

What:		/sys/accessibility/speakup/bell_pos
KernelVersion:	2.6
Contact:	speakup@linux-speakup.org
Description:	This works much like a typewriter bell. If for example 72 is
		echoed to bell_pos, it will beep the PC speaker when typing on
		a line past character 72.

What:		/sys/accessibility/speakup/bleeps
KernelVersion:	2.6
Contact:	speakup@linux-speakup.org
Description:	This controls whether one hears beeps through the PC speaker
		when using speakup's review commands.
		TODO: what values does it accept?

What:		/sys/accessibility/speakup/bleep_time
KernelVersion:	2.6
Contact:	speakup@linux-speakup.org
Description:	This controls the duration of the PC speaker beeps speakup
		produces.
		TODO: What are the units? Jiffies?

What:		/sys/accessibility/speakup/cursor_time
KernelVersion:	2.6
Contact:	speakup@linux-speakup.org
Description:	This controls cursor delay when using arrow keys. When a
		connection is very slow, with the default setting, when moving
		with  the arrows, or backspacing etc. speakup says the incorrect
		characters. Set this to a higher value to adjust for the delay
		and better synchronisation between cursor position and speech.

What:		/sys/accessibility/speakup/cur_phonetic
KernelVersion:	6.2
Contact:	speakup@linux-speakup.org
Description:	This allows speakup to speak letters phoneticaly when arrowing through
		a word letter by letter. This doesn't affect the spelling when typing
		the characters. When cur_phonetic=1, speakup will speak characters
		phoneticaly when arrowing over a letter. When cur_phonetic=0, speakup
		will speak letters as normally.

What:		/sys/accessibility/speakup/delimiters
KernelVersion:	2.6
Contact:	speakup@linux-speakup.org
Description:	Delimit a word from speakup.
		TODO: add more info

What:		/sys/accessibility/speakup/ex_num
KernelVersion:	2.6
Contact:	speakup@linux-speakup.org
Description:	TODO:

What:		/sys/accessibility/speakup/key_echo
KernelVersion:	2.6
Contact:	speakup@linux-speakup.org
Description:	Controls if speakup speaks keys when they are typed. One = on,
		zero = off or don't echo keys.

What:		/sys/accessibility/speakup/keymap
KernelVersion:	2.6
Contact:	speakup@linux-speakup.org
Description:	Speakup keymap remaps keys to Speakup functions.
		It uses a binary
		format. A special program called genmap is needed to compile a
		textual  keymap into the binary format which is then loaded into
		/sys/accessibility/speakup/keymap.

What:		/sys/accessibility/speakup/no_interrupt
KernelVersion:	2.6
Contact:	speakup@linux-speakup.org
Description:	Controls if typing interrupts output from speakup. With
		no_interrupt set to zero, typing on the keyboard will interrupt
		speakup if for example
		the say screen command is used before the
		entire screen  is read.

		With no_interrupt set to one, if the say
		screen command is used, and one then types on the keyboard,
		speakup will continue to say the whole screen regardless until
		it finishes.

What:		/sys/accessibility/speakup/punc_all
KernelVersion:	2.6
Contact:	speakup@linux-speakup.org
Description:	This is a list of all the punctuation speakup should speak when
		punc_level is set to four.

What:		/sys/accessibility/speakup/punc_level
KernelVersion:	2.6
Contact:	speakup@linux-speakup.org
Description:	Controls the level of punctuation spoken as the screen is
		displayed, not reviewed. Levels range from zero no punctuation,
		to four, all punctuation. One corresponds to punc_some, two
		corresponds to punc_most, and three as well as four both
		correspond to punc_all. Some hardware synthesizers may have
		different levels each corresponding to  three and four for
		punc_level. Also note that if punc_level is set to zero, and
		key_echo is set to one, typed punctuation is still spoken as it
		is typed.

What:		/sys/accessibility/speakup/punc_most
KernelVersion:	2.6
Contact:	speakup@linux-speakup.org
Description:	This is a list of all the punctuation speakup should speak when
		punc_level is set to two.

What:		/sys/accessibility/speakup/punc_some
KernelVersion:	2.6
Contact:	speakup@linux-speakup.org
Description:	This is a list of all the punctuation speakup should speak when
		punc_level is set to one.

What:		/sys/accessibility/speakup/reading_punc
KernelVersion:	2.6
Contact:	speakup@linux-speakup.org
Description:	Almost the same as punc_level, the differences being that
		reading_punc controls the level of punctuation when reviewing
		the screen with speakup's screen review commands. The other
		difference is that reading_punc set to three speaks punc_all,
		and reading_punc set to four speaks all punctuation, including
		spaces.

What:		/sys/accessibility/speakup/repeats
KernelVersion:	2.6
Contact:	speakup@linux-speakup.org
Description:	A list of characters speakup repeats. Normally, when there are
		more than three characters in a row, speakup
		just reads three of
		those characters. For example, "......" would be read as dot,
		dot, dot. If a . is added to the list of characters in repeats,
		"......" would be read as dot, dot, dot, times six.

What:		/sys/accessibility/speakup/say_control
KernelVersion:	2.6
Contact:	speakup@linux-speakup.org
Description:	If set to one, speakup speaks shift, alt and control when those
		keys are pressed. If say_control is set to zero, shift, ctrl,
		and alt are not spoken when they are pressed.

What:		/sys/accessibility/speakup/say_word_ctl
KernelVersion:	2.6
Contact:	speakup@linux-speakup.org
Description:	TODO:

What:		/sys/accessibility/speakup/silent
KernelVersion:	2.6
Contact:	speakup@linux-speakup.org
Description:	TODO:

What:		/sys/accessibility/speakup/spell_delay
KernelVersion:	2.6
Contact:	speakup@linux-speakup.org
Description:	This controls how fast a word is spelled
		when speakup's say word
		review command is pressed twice quickly to speak the current
		word being reviewed. Zero just speaks the letters one after
		another, while values one through four
		seem to introduce more of
		a pause between the spelling of each letter by speakup.

What:		/sys/accessibility/speakup/synth
KernelVersion:	2.6
Contact:	speakup@linux-speakup.org
Description:	Gets or sets the synthesizer driver currently in use. Reading
		synth returns the synthesizer driver currently in use. Writing
		synth switches to the given synthesizer driver, provided it is
		either built into the kernel, or already loaded as a module.

What:		/sys/accessibility/speakup/synth_direct
KernelVersion:	2.6
Contact:	speakup@linux-speakup.org
Description:	Sends whatever is written to synth_direct
		directly to the speech synthesizer in use, bypassing speakup.
		This could be used to make the synthesizer speak
		a string, or to
		send control sequences to the synthesizer to change how the
		synthesizer behaves.

What:		/sys/accessibility/speakup/version
KernelVersion:	2.6
Contact:	speakup@linux-speakup.org
Description:	Reading version returns the version of speakup, and the version
		of the synthesizer driver currently in use.

What:		/sys/accessibility/speakup/i18n/announcements
KernelVersion:	2.6
Contact:	speakup@linux-speakup.org
Description:	This file contains various general announcements, most of which
		cannot be categorized.  You will find messages such as "You
		killed Speakup", "I'm alive", "leaving help", "parked",
		"unparked", and others. You will also find the names of the
		screen edges and cursor tracking modes here.

What:		/sys/accessibility/speakup/i18n/chartab
KernelVersion:	2.6
Contact:	speakup@linux-speakup.org
Description:	TODO

What:		/sys/accessibility/speakup/i18n/ctl_keys
KernelVersion:	2.6
Contact:	speakup@linux-speakup.org
Description:	Here, you will find names of control keys.  These are used with
		Speakup's say_control feature.

What:		/sys/accessibility/speakup/i18n/function_names
KernelVersion:	2.6
Contact:	speakup@linux-speakup.org
Description:	Here, you will find a list of names for Speakup functions.
		These are used by the help system.  For example, suppose that
		you have activated help mode, and you pressed
		keypad 3.  Speakup
		says: "keypad 3 is character, say next."
		The message "character, say next" names a Speakup function, and
		it comes from this function_names file.

What:		/sys/accessibility/speakup/i18n/states
KernelVersion:	2.6
Contact:	speakup@linux-speakup.org
Description:	This file contains names for key states.
		Again, these are part of the help system.  For instance, if you
		had pressed speakup + keypad 3, you would hear:
		"speakup keypad 3 is go to bottom edge."

		The speakup key is depressed, so the name of the key state is
		speakup.

		This part of the message comes from the states collection.

What:		/sys/accessibility/speakup/i18n/characters
KernelVersion:	2.6
Contact:	speakup@linux-speakup.org
Description:	Through this sys entry, Speakup gives you the ability to change
		how Speakup pronounces a given character. You could, for
		example, change how some punctuation characters are spoken. You
		can even change how Speakup will pronounce certain letters. For
		further details see '12.  Changing the Pronunciation of
		Characters' in Speakup User's Guide (file spkguide.txt in
		source).

What:		/sys/accessibility/speakup/i18n/colors
KernelVersion:	2.6
Contact:	speakup@linux-speakup.org
Description:	When you use the "say attributes" function, Speakup says the
		name of the foreground and background colors.  These names come
		from the i18n/colors file.

What:		/sys/accessibility/speakup/i18n/formatted
KernelVersion:	2.6
Contact:	speakup@linux-speakup.org
Description:	This group of messages contains embedded formatting codes, to
		specify the type and width of displayed data.  If you change
		these, you must preserve all of the formatting codes, and they
		must appear in the order used by the default messages.

What:		/sys/accessibility/speakup/i18n/key_names
KernelVersion:	2.6
Contact:	speakup@linux-speakup.org
Description:	Again, key_names is used by Speakup's help system.  In the
		previous example, Speakup said that you pressed "keypad 3."
		This name came from the key_names file.

What:		/sys/accessibility/speakup/<synth-name>/
KernelVersion:	2.6
Contact:	speakup@linux-speakup.org
Description:	In `/sys/accessibility/speakup` is a directory corresponding to
		the synthesizer driver currently in use (E.G) `soft` for the
		soft driver. This directory contains files which control the
		speech synthesizer itself,
		as opposed to controlling the speakup
		screen reader. The parameters in this directory have the same
		names and functions across all
		supported synthesizers. The range
		of values for freq, pitch, rate, and vol is the same for all
		supported synthesizers, with the given range being internally
		mapped by the driver to  more or less fit the range of values
		supported for a given parameter by the individual synthesizer.
		Below is a description of values and  parameters for soft
		synthesizer, which is currently the most commonly used.

What:		/sys/accessibility/speakup/<synth-name>/caps_start
KernelVersion:	2.6
Contact:	speakup@linux-speakup.org
Description:	This is the string that is sent to the synthesizer to cause it
		to start speaking uppercase letters. For the soft synthesizer
		and most others, this causes the pitch of the voice to rise
		above the currently set pitch.

What:		/sys/accessibility/speakup/<synth-name>/caps_stop
KernelVersion:	2.6
Contact:	speakup@linux-speakup.org
Description:	This is the string sent to the synthesizer to cause it to stop
		speaking uppercase letters. In the case of the soft synthesizer
		and most others, this returns the pitch of the voice
		down to the
		currently set pitch.

What:		/sys/accessibility/speakup/<synth-name>/delay_time
KernelVersion:	2.6
Contact:	speakup@linux-speakup.org
Description:	TODO:

What:		/sys/accessibility/speakup/<synth-name>/direct
KernelVersion:	2.6
Contact:	speakup@linux-speakup.org
Description:	Controls if punctuation is spoken by speakup, or by the
		synthesizer.

		For example, speakup speaks ">" as "greater", while
		the espeak synthesizer used by the soft driver speaks "greater
		than". Zero lets speakup speak the punctuation. One lets the
		synthesizer itself speak punctuation.

What:		/sys/accessibility/speakup/<synth-name>/freq
KernelVersion:	2.6
Contact:	speakup@linux-speakup.org
Description:	Gets or sets the frequency of the speech synthesizer. Range is
		0-9.

What:		/sys/accessibility/speakup/<synth-name>/flush_time
KernelVersion:	5.12
Contact:	speakup@linux-speakup.org
Description:	Gets or sets the timeout to wait for the synthesizer flush to
		complete. This can be used when the cable gets faulty and flush
		notifications are getting lost.

What:		/sys/accessibility/speakup/<synth-name>/full_time
KernelVersion:	2.6
Contact:	speakup@linux-speakup.org
Description:	TODO:

What:		/sys/accessibility/speakup/<synth-name>/jiffy_delta
KernelVersion:	2.6
Contact:	speakup@linux-speakup.org
Description:	This controls how many jiffys the kernel gives to the
		synthesizer. Setting this too high can make a system unstable,
		or even crash it.

What:		/sys/accessibility/speakup/<synth-name>/pitch
KernelVersion:	2.6
Contact:	speakup@linux-speakup.org
Description:	Gets or sets the pitch of the synthesizer. The range is 0-9.

What:		/sys/accessibility/speakup/<synth-name>/inflection
KernelVersion:	5.8
Contact:	speakup@linux-speakup.org
Description:	Gets or sets the inflection of the synthesizer, i.e. the pitch
		range. The range is 0-9.

What:		/sys/accessibility/speakup/<synth-name>/punct
KernelVersion:	2.6
Contact:	speakup@linux-speakup.org
Description:	Gets or sets the amount of punctuation spoken by the
		synthesizer. The range for the soft driver seems to be 0-2.
		TODO: How is this related to speakup's punc_level, or
		reading_punc.

What:		/sys/accessibility/speakup/<synth-name>/rate
KernelVersion:	2.6
Contact:	speakup@linux-speakup.org
Description:	Gets or sets the rate of the synthesizer. Range is from zero
		slowest, to nine fastest.

What:		/sys/accessibility/speakup/<synth-name>/tone
KernelVersion:	2.6
Contact:	speakup@linux-speakup.org
Description:	Gets or sets the tone of the speech synthesizer. The range for
		the soft driver seems to be 0-2. This seems to make no
		difference if using espeak and the espeakup connector.
		TODO: does espeakup support different tonalities?

What:		/sys/accessibility/speakup/<synth-name>/trigger_time
KernelVersion:	2.6
Contact:	speakup@linux-speakup.org
Description:	TODO:

What:		/sys/accessibility/speakup/<synth-name>/voice
KernelVersion:	2.6
Contact:	speakup@linux-speakup.org
Description:	Gets or sets the voice used by the synthesizer if the
		synthesizer can speak in more than one voice. The range for the
		soft driver is 0-7. Note that while espeak supports multiple
		voices, this parameter will not set the voice when the espeakup
		connector is used  between speakup and espeak.

What:		/sys/accessibility/speakup/<synth-name>/vol
KernelVersion:	2.6
Contact:	speakup@linux-speakup.org
Description:	Gets or sets the volume of the speech synthesizer. Range is 0-9,
		with zero being the softest, and nine being the loudest.


code:
What:		/sys/bus/usb/drivers/usbtmc/*/interface_capabilities
What:		/sys/bus/usb/drivers/usbtmc/*/device_capabilities
Date:		August 2008
Contact:	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Description:
		These files show the various USB TMC capabilities as described
		by the device itself.  The full description of the bitfields
		can be found in the USB TMC documents from the USB-IF entitled
		"Universal Serial Bus Test and Measurement Class Specification
		(USBTMC) Revision 1.0" section 4.2.1.8.

		The files are read only.

What:		/sys/bus/usb/drivers/usbtmc/*/usb488_interface_capabilities
What:		/sys/bus/usb/drivers/usbtmc/*/usb488_device_capabilities
Date:		August 2008
Contact:	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Description:
		These files show the various USB TMC capabilities as described
		by the device itself.  The full description of the bitfields
		can be found in the USB TMC documents from the USB-IF entitled
		"Universal Serial Bus Test and Measurement Class, Subclass
		USB488 Specification (USBTMC-USB488) Revision 1.0" section
		4.2.2.

		The files are read only.


code:
What:		/sys/bus/w1/devices/.../page1
Date:		April 2021
Contact:	Luiz Sampaio <sampaio.ime@gmail.com>
Description:	read the contents of the page1 of the DS2438
		see Documentation/w1/slaves/w1_ds2438.rst for detailed information
Users:		any user space application which wants to communicate with DS2438

What:		/sys/bus/w1/devices/.../offset
Date:		April 2021
Contact:	Luiz Sampaio <sampaio.ime@gmail.com>
Description:	write the contents to the offset register of the DS2438
		see Documentation/w1/slaves/w1_ds2438.rst for detailed information
Users:		any user space application which wants to communicate with DS2438


code:
What:		/sys/bus/w1/devices/.../pio
Date:		May 2012
Contact:	Markus Franke <franm@hrz.tu-chemnitz.de>
Description:	read/write the contents of the two PIO's of the DS28E04-100
		see Documentation/w1/slaves/w1_ds28e04.rst for detailed information
Users:		any user space application which wants to communicate with DS28E04-100

What:		/sys/bus/w1/devices/.../eeprom
Date:		May 2012
Contact:	Markus Franke <franm@hrz.tu-chemnitz.de>
Description:	read/write the contents of the EEPROM memory of the DS28E04-100
		see Documentation/w1/slaves/w1_ds28e04.rst for detailed information
Users:		any user space application which wants to communicate with DS28E04-100


code:
What:		/sys/bus/w1/devices/.../w1_seq
Date:		Apr 2015
Contact:	Matt Campbell <mattrcampbell@gmail.com>
Description:	Support for the DS28EA00 chain sequence function
		see Documentation/w1/slaves/w1_therm.rst for detailed information
Users:		any user space application which wants to communicate with DS28EA00


code:
What:		/sys/firmware/efi/vars
Date:		April 2004
Contact:	Matt Domsch <Matt_Domsch@dell.com>
Description:
		This directory exposes interfaces for interactive with
		EFI variables.  For more information on EFI variables,
		see 'Variable Services' in the UEFI specification
		(section 7.2 in specification version 2.3 Errata D).

		In summary, EFI variables are named, and are classified
		into separate namespaces through the use of a vendor
		GUID.  They also have an arbitrary binary value
		associated with them.

		The efivars module enumerates these variables and
		creates a separate directory for each one found.  Each
		directory has a name of the form "<key>-<vendor guid>"
		and contains the following files:

		=============== ========================================
		attributes:	A read-only text file enumerating the
				EFI variable flags.  Potential values
				include:

				EFI_VARIABLE_NON_VOLATILE
				EFI_VARIABLE_BOOTSERVICE_ACCESS
				EFI_VARIABLE_RUNTIME_ACCESS
				EFI_VARIABLE_HARDWARE_ERROR_RECORD
				EFI_VARIABLE_AUTHENTICATED_WRITE_ACCESS

				See the EFI documentation for an
				explanation of each of these variables.

		data:		A read-only binary file that can be read
				to attain the value of the EFI variable

		guid:		The vendor GUID of the variable.  This
				should always match the GUID in the
				variable's name.

		raw_var:	A binary file that can be read to obtain
				a structure that contains everything
				there is to know about the variable.
				For structure definition see "struct
				efi_variable" in the kernel sources.

				This file can also be written to in
				order to update the value of a variable.
				For this to work however, all fields of
				the "struct efi_variable" passed must
				match byte for byte with the structure
				read out of the file, save for the value
				portion.

				**Note** the efi_variable structure
				read/written with this file contains a
				'long' type that may change widths
				depending on your underlying
				architecture.

		size:		As ASCII representation of the size of
				the variable's value.
		=============== ========================================

		In addition, two other magic binary files are provided
		in the top-level directory and are used for adding and
		removing variables:

		=============== ========================================
		new_var:	Takes a "struct efi_variable" and
				instructs the EFI firmware to create a
				new variable.

		del_var:	Takes a "struct efi_variable" and
				instructs the EFI firmware to remove any
				variable that has a matching vendor GUID
				and variable key name.
		=============== ========================================


code:
What:		/sys/firmware/opal/dump
Date:		Feb 2014
Contact:	Stewart Smith <stewart@linux.vnet.ibm.com>
Description:
		This directory exposes interfaces for interacting with
		the FSP and platform dumps through OPAL firmware interface.

		This is only for the powerpc/powernv platform.

		=============== ===============================================
		initiate_dump:	When '1' is written to it,
				we will initiate a dump.
				Read this file for supported commands.

		0xXX-0xYYYY:	A directory for dump of type 0xXX and
				id 0xYYYY (in hex). The name of this
				directory should not be relied upon to
				be in this format, only that it's unique
				among all dumps. For determining the type
				and ID of the dump, use the id and type files.
				Do not rely on any particular size of dump
				type or dump id.
		=============== ===============================================

		Each dump has the following files:

		=============== ===============================================
		id:		An ASCII representation of the dump ID
				in hex (e.g. '0x01')
		type:		An ASCII representation of the type of
				dump in the format "0x%x %s" with the ID
				in hex and a description of the dump type
				(or 'unknown').
				Type '0xffffffff unknown' is used when
				we could not get the type from firmware.
				e.g. '0x02 System/Platform Dump'
		dump:		A binary file containing the dump.
				The size of the dump is the size of this file.
		acknowledge:	When 'ack' is written to this, we will
				acknowledge that we've retrieved the
				dump to the service processor. It will
				then remove it, making the dump
				inaccessible.
				Reading this file will get a list of
				supported actions.
		=============== ===============================================


code:
What:		/sys/firmware/opal/elog
Date:		Feb 2014
Contact:	Stewart Smith <stewart@linux.vnet.ibm.com>
Description:
		This directory exposes error log entries retrieved
		through the OPAL firmware interface.

		Each error log is identified by a unique ID and will
		exist until explicitly acknowledged to firmware.

		Each log entry has a directory in /sys/firmware/opal/elog.

		Log entries may be purged by the service processor
		before retrieved by firmware or retrieved/acknowledged by
		Linux if there is no room for more log entries.

		In the event that Linux has retrieved the log entries
		but not explicitly acknowledged them to firmware and
		the service processor needs more room for log entries,
		the only remaining copy of a log message may be in
		Linux.

		Typically, a user space daemon will monitor for new
		entries, read them out and acknowledge them.

		The service processor may be able to store more log
		entries than firmware can, so after you acknowledge
		an event from Linux you may instantly get another one
		from the queue that was generated some time in the past.

		The raw log format is a binary format. We currently
		do not parse this at all in kernel, leaving it up to
		user space to solve the problem. In future, we may
		do more parsing in kernel and add more files to make
		it easier for simple user space processes to extract
		more information.

		For each log entry (directory), there are the following
		files:

		==============  ================================================
		id:		An ASCII representation of the ID of the
				error log, in hex - e.g. "0x01".

		type:		An ASCII representation of the type id and
				description of the type of error log.
				Currently just "0x00 PEL" - platform error log.
				In the future there may be additional types.

		raw:		A read-only binary file that can be read
				to get the raw log entry. These are
				<16kb, often just hundreds of bytes and
				"average" 2kb.

		acknowledge:	Writing 'ack' to this file will acknowledge
				the error log to firmware (and in turn
				the service processor, if applicable).
				Shortly after acknowledging it, the log
				entry will be removed from sysfs.
				Reading this file will list the supported
				operations (currently just acknowledge).
		==============  ================================================


code:
What:			/sys/fs/orangefs/perf_counters/*
Date:			Jun 2015
Contact:		Mike Marshall <hubcap@omnibond.com>
Description:
			Counters and settings for various caches.
			Read only.

What:			/sys/fs/orangefs/perf_counter_reset
Date:			June 2015
Contact:		Mike Marshall <hubcap@omnibond.com>
Description:
			echo a 0 or a 1 into perf_counter_reset to
			reset all the counters in
			/sys/fs/orangefs/perf_counters
			except ones with PINT_PERF_PRESERVE set.

What:			/sys/fs/orangefs/perf_time_interval_secs
Date:			Jun 2015
Contact:		Mike Marshall <hubcap@omnibond.com>
Description:
			Length of perf counter intervals in
			seconds.

What:			/sys/fs/orangefs/perf_history_size
Date:			Jun 2015
Contact:		Mike Marshall <hubcap@omnibond.com>
Description:
			The perf_counters cache statistics have N, or
			perf_history_size, samples. The default is
			one.

			Every perf_time_interval_secs the (first)
			samples are reset.

			If N is greater than one, the "current" set
			of samples is reset, and the samples from the
			other N-1 intervals remain available.

What:			/sys/fs/orangefs/op_timeout_secs
Date:			Jun 2015
Contact:		Mike Marshall <hubcap@omnibond.com>
Description:
			Service operation timeout in seconds.

What:			/sys/fs/orangefs/slot_timeout_secs
Date:			Jun 2015
Contact:		Mike Marshall <hubcap@omnibond.com>
Description:
			"Slot" timeout in seconds. A "slot"
			is an indexed buffer in the shared
			memory segment used for communication
			between the kernel module and userspace.
			Slots are requested and waited for,
			the wait times out after slot_timeout_secs.

What:			/sys/fs/orangefs/acache/*
Date:			Jun 2015
Contact:		Mike Marshall <hubcap@omnibond.com>
Description:
			Attribute cache configurable settings.

What:			/sys/fs/orangefs/ncache/*
Date:			Jun 2015
Contact:		Mike Marshall <hubcap@omnibond.com>
Description:
			Name cache configurable settings.

What:			/sys/fs/orangefs/capcache/*
Date:			Jun 2015
Contact:		Mike Marshall <hubcap@omnibond.com>
Description:
			Capability cache configurable settings.

What:			/sys/fs/orangefs/ccache/*
Date:			Jun 2015
Contact:		Mike Marshall <hubcap@omnibond.com>
Description:
			Credential cache configurable settings.