code:
What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/kone/roccatkone<minor>/actual_dpi
Date:		March 2010
Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
Description:	It is possible to switch the dpi setting of the mouse with the
		press of a button.

		When read, this file returns the raw number of the actual dpi
		setting reported by the mouse. This number has to be further
		processed to receive the real dpi value:

		===== =====
		VALUE DPI
		===== =====
		1     800
		2     1200
		3     1600
		4     2000
		5     2400
		6     3200
		===== =====

		This file is readonly.
Users:		http://roccat.sourceforge.net

What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/kone/roccatkone<minor>/actual_profile
Date:		March 2010
Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
Description:	When read, this file returns the number of the actual profile.

		This file is readonly.
Users:		http://roccat.sourceforge.net

What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/kone/roccatkone<minor>/firmware_version
Date:		March 2010
Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
Description:	When read, this file returns the raw integer version number of the
		firmware reported by the mouse. Using the integer value eases
		further usage in other programs. To receive the real version
		number the decimal point has to be shifted 2 positions to the
		left. E.g. a returned value of 138 means 1.38

		This file is readonly.
Users:		http://roccat.sourceforge.net

What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/kone/roccatkone<minor>/profile[1-5]
Date:		March 2010
Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
Description:	The mouse can store 5 profiles which can be switched by the
                press of a button. A profile holds information like button
                mappings, sensitivity, the colors of the 5 leds and light
                effects.

                When read, these files return the respective profile. The
                returned data is 975 bytes in size.

		When written, this file lets one write the respective profile
		data back to the mouse. The data has to be 975 bytes long.

		The mouse will reject invalid data, whereas the profile number
		stored in the profile doesn't need to fit the number of the
		store.
Users:		http://roccat.sourceforge.net

What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/kone/roccatkone<minor>/settings
Date:		March 2010
Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
Description:	When read, this file returns the settings stored in the mouse.
		The size of the data is 36 bytes and holds information like the
		startup_profile, tcu state and calibration_data.

		When written, this file lets write settings back to the mouse.
		The data has to be 36 bytes long. The mouse will reject invalid
		data.
Users:		http://roccat.sourceforge.net

What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/kone/roccatkone<minor>/startup_profile
Date:		March 2010
Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
Description:	The integer value of this attribute ranges from 1 to 5.

                When read, this attribute returns the number of the profile
                that's active when the mouse is powered on.

		When written, this file sets the number of the startup profile
		and the mouse activates this profile immediately.
Users:		http://roccat.sourceforge.net

What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/kone/roccatkone<minor>/tcu
Date:		March 2010
Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
Description:	The mouse has a "Tracking Control Unit" which lets the user
		calibrate the laser power to fit the mousepad surface.
		When read, this file returns the current state of the TCU,
		where 0 means off and 1 means on.

		Writing 0 in this file will switch the TCU off.

		Writing 1 in this file will start the calibration which takes
		around 6 seconds to complete and activates the TCU.

Users:		http://roccat.sourceforge.net

What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/kone/roccatkone<minor>/weight
Date:		March 2010
Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
Description:	The mouse can be equipped with one of four supplied weights
		ranging from 5 to 20 grams which are recognized by the mouse
		and its value can be read out. When read, this file returns the
		raw value returned by the mouse which eases further processing
		in other software.

		The values map to the weights as follows:

		===== ======
		VALUE WEIGHT
		===== ======
		0     none
		1     5g
		2     10g
		3     15g
		4     20g
		===== ======

		This file is readonly.
Users:		http://roccat.sourceforge.net


code:
What:		/sys/class/leds/SRWS1::<serial>::RPM1
What:		/sys/class/leds/SRWS1::<serial>::RPM2
What:		/sys/class/leds/SRWS1::<serial>::RPM3
What:		/sys/class/leds/SRWS1::<serial>::RPM4
What:		/sys/class/leds/SRWS1::<serial>::RPM5
What:		/sys/class/leds/SRWS1::<serial>::RPM6
What:		/sys/class/leds/SRWS1::<serial>::RPM7
What:		/sys/class/leds/SRWS1::<serial>::RPM8
What:		/sys/class/leds/SRWS1::<serial>::RPM9
What:		/sys/class/leds/SRWS1::<serial>::RPM10
What:		/sys/class/leds/SRWS1::<serial>::RPM11
What:		/sys/class/leds/SRWS1::<serial>::RPM12
What:		/sys/class/leds/SRWS1::<serial>::RPM13
What:		/sys/class/leds/SRWS1::<serial>::RPM14
What:		/sys/class/leds/SRWS1::<serial>::RPM15
What:		/sys/class/leds/SRWS1::<serial>::RPMALL
Date:		Jan 2013
KernelVersion:	3.9
Contact:	Simon Wood <simon@mungewell.org>
Description:	Provides a control for turning on/off the LEDs which form
		an RPM meter on the front of the controller

repo_name: angery/linux


code:
What:		/sys/bus/hid/drivers/wiimote/<dev>/led1
What:		/sys/bus/hid/drivers/wiimote/<dev>/led2
What:		/sys/bus/hid/drivers/wiimote/<dev>/led3
What:		/sys/bus/hid/drivers/wiimote/<dev>/led4
Date:		July 2011
KernelVersion:	3.1
Contact:	David Herrmann <dh.herrmann@googlemail.com>
Description:	Make it possible to set/get current led state. Reading from it
		returns 0 if led is off and 1 if it is on. Writing 0 to it
		disables the led, writing 1 enables it.

What:		/sys/bus/hid/drivers/wiimote/<dev>/extension
Date:		August 2011
KernelVersion:	3.2
Contact:	David Herrmann <dh.herrmann@gmail.com>
Description:	This file contains the currently connected and initialized
		extensions. It can be one of: none, motionp, nunchuck, classic,
		motionp+nunchuck, motionp+classic
		motionp is the official Nintendo Motion+ extension, nunchuck is
		the official Nintendo Nunchuck extension and classic is the
		Nintendo Classic Controller extension. The motionp extension can
		be combined with the other two.

		Starting with kernel-version 3.11 Motion Plus hotplugging is
		supported and if detected, it's no longer reported as static
		extension. You will get uevent notifications for the motion-plus
		device then.

What:		/sys/bus/hid/drivers/wiimote/<dev>/devtype
Date:		May 2013
KernelVersion:	3.11
Contact:	David Herrmann <dh.herrmann@gmail.com>
Description:	While a device is initialized by the wiimote driver, we perform
		a device detection and signal a "change" uevent after it is
		done. This file shows the detected device type. "pending" means
		that the detection is still ongoing, "unknown" means, that the
		device couldn't be detected or loaded. "generic" means, that the
		device couldn't be detected but supports basic Wii Remote
		features and can be used.
		Other strings for each device-type are available and may be
		added if new device-specific detections are added.
		Currently supported are:

			============= =======================================
			gen10:        First Wii Remote generation
			gen20:        Second Wii Remote Plus generation
				      (builtin MP)
			balanceboard: Wii Balance Board
			============= =======================================

What:		/sys/bus/hid/drivers/wiimote/<dev>/bboard_calib
Date:		May 2013
KernelVersion:	3.11
Contact:	David Herrmann <dh.herrmann@gmail.com>
Description:	This attribute is only provided if the device was detected as a
		balance board. It provides a single line with 3 calibration
		values for all 4 sensors. The values are separated by colons and
		are each 2 bytes long (encoded as 4 digit hexadecimal value).
		First, 0kg values for all 4 sensors are written, followed by the
		17kg values for all 4 sensors and last the 34kg values for all 4
		sensors.

		Calibration data is already applied by the kernel to all input
		values but may be used by user-space to perform other
		transformations.

What:		/sys/bus/hid/drivers/wiimote/<dev>/pro_calib
Date:		October 2013
KernelVersion:	3.13
Contact:	David Herrmann <dh.herrmann@gmail.com>
Description:	This attribute is only provided if the device was detected as a
		pro-controller. It provides a single line with 4 calibration
		values for all 4 analog sticks. Format is: "x1:y1 x2:y2". Data
		is prefixed with a +/-. Each value is a signed 16bit number.
		Data is encoded as decimal numbers and specifies the offsets of
		the analog sticks of the pro-controller.

		Calibration data is already applied by the kernel to all input
		values but may be used by user-space to perform other
		transformations.

		Calibration data is detected by the kernel during device setup.
		You can write "scan\n" into this file to re-trigger calibration.
		You can also write data directly in the form "x1:y1 x2:y2" to
		set the calibration values manually.


code:
What:		/sys/class/input/input(x)/device/startup
Date:		March 2014
Contact:	Carlo Caione <carlo@caione.org>
Description:	Startup time in us. Board is powered on if the button is pressed
		for more than <startup_time>

What:		/sys/class/input/input(x)/device/shutdown
Date:		March 2014
Contact:	Carlo Caione <carlo@caione.org>
Description:	Shutdown time in us. Board is powered off if the button is pressed
		for more than <shutdown_time>


code:
What:		/sys/class/input/input(x)/device/function_row_physmap
Date:		January 2021
Contact:	Philip Chen <philipchen@chromium.org>
Description:	A space separated list of scancodes for the top row keys,
		ordered by the physical positions of the keys, from left
		to right.


code:
What:		/sys/bus/i2c/devices/xxx/fw_version
Date:		Aug 2020
Contact:	linux-input@vger.kernel.org
Description:    Reports the firmware version provided by the touchscreen, for example "00_T6" on a EXC80H60

		Access: Read

		Valid values: Represented as string

What:		/sys/bus/i2c/devices/xxx/model
Date:		Aug 2020
Contact:	linux-input@vger.kernel.org
Description:    Reports the model identification provided by the touchscreen, for example "Orion_1320" on a EXC80H60

		Access: Read

		Valid values: Represented as string

What:		/sys/bus/i2c/devices/xxx/type
Date:		Jan 2021
Contact:	linux-input@vger.kernel.org
Description:	Reports the type identification provided by the touchscreen, for example "PCAP82H80 Series"

		Access: Read

		Valid values: Represented as string


code:
What:		/sys/bus/platform/devices/INTC1092:00/intc_reg
Date:		August 2021
KernelVersion:	5.15
Contact:	Shravan S <s.shravan@intel.com>,
		An Sudhakar <sudhakar.an@intel.com>
Description:
		Specific Absorption Rate (SAR) regulatory mode is typically
		derived based on information like mcc (Mobile Country Code) and
		mnc (Mobile Network Code) that is available for the currently
		attached LTE network. A userspace application is required to set
		the current SAR regulatory mode on the Dynamic SAR driver using
		this sysfs node. Such an application can also read back using
		this sysfs node, the currently configured regulatory mode value
		from the Dynamic SAR driver.

		Acceptable regulatory modes are:
			==	====
			0	FCC
			1	CE
			2	ISED
			==	====

		- The regulatory mode value has one of the above values.
		- The default regulatory mode used in the driver is 0.

What:		/sys/bus/platform/devices/INTC1092:00/intc_data
Date:		August 2021
KernelVersion:	5.15
Contact:	Shravan S <s.shravan@intel.com>,
		An Sudhakar <sudhakar.an@intel.com>
Description:
		This sysfs entry is used to retrieve Dynamic SAR information
		emitted/maintained by a BIOS that supports Dynamic SAR.

		The retrieved information is in the order given below:
		- device_mode
		- bandtable_index
		- antennatable_index
		- sartable_index

		The above information is sent as integer values separated
		by a single space. This information can then be pushed to a
		WWAN modem that uses this to control the transmit signal
		level using the Band/Antenna/SAR table index information.
		These parameters are derived/decided by aggregating
		device-mode like laptop/tablet/clamshell etc. and the
		proximity-sensor data available to the embedded controller on
		given host. The regulatory mode configured on Dynamic SAR
		driver also influences these values.

		The userspace applications can poll for changes to this file
		using POLLPRI event on file-descriptor (fd) obtained by opening
		this sysfs entry. Application can then read this information from
		the sysfs node and consume the given information.


code:
What:		/sys/devices/.../hwmon/hwmon<i>/in0_input
Date:		February 2023
KernelVersion:	6.2
Contact:	intel-gfx@lists.freedesktop.org
Description:	RO. Current Voltage in millivolt.

		Only supported for particular Intel i915 graphics platforms.

What:		/sys/devices/.../hwmon/hwmon<i>/power1_max
Date:		February 2023
KernelVersion:	6.2
Contact:	intel-gfx@lists.freedesktop.org
Description:	RW. Card reactive sustained  (PL1/Tau) power limit in microwatts.

		The power controller will throttle the operating frequency
		if the power averaged over a window (typically seconds)
		exceeds this limit.

		Only supported for particular Intel i915 graphics platforms.

What:		/sys/devices/.../hwmon/hwmon<i>/power1_rated_max
Date:		February 2023
KernelVersion:	6.2
Contact:	intel-gfx@lists.freedesktop.org
Description:	RO. Card default power limit (default TDP setting).

		Only supported for particular Intel i915 graphics platforms.

What:		/sys/devices/.../hwmon/hwmon<i>/power1_max_interval
Date:		February 2023
KernelVersion:	6.2
Contact:	intel-gfx@lists.freedesktop.org
Description:	RW. Sustained power limit interval (Tau in PL1/Tau) in
		milliseconds over which sustained power is averaged.

		Only supported for particular Intel i915 graphics platforms.

What:		/sys/devices/.../hwmon/hwmon<i>/power1_crit
Date:		February 2023
KernelVersion:	6.2
Contact:	intel-gfx@lists.freedesktop.org
Description:	RW. Card reactive critical (I1) power limit in microwatts.

		Card reactive critical (I1) power limit in microwatts is exposed
		for client products. The power controller will throttle the
		operating frequency if the power averaged over a window exceeds
		this limit.

		Only supported for particular Intel i915 graphics platforms.

What:		/sys/devices/.../hwmon/hwmon<i>/curr1_crit
Date:		February 2023
KernelVersion:	6.2
Contact:	intel-gfx@lists.freedesktop.org
Description:	RW. Card reactive critical (I1) power limit in milliamperes.

		Card reactive critical (I1) power limit in milliamperes is
		exposed for server products. The power controller will throttle
		the operating frequency if the power averaged over a window
		exceeds this limit.

		Only supported for particular Intel i915 graphics platforms.

What:		/sys/devices/.../hwmon/hwmon<i>/energy1_input
Date:		February 2023
KernelVersion:	6.2
Contact:	intel-gfx@lists.freedesktop.org
Description:	RO. Energy input of device or gt in microjoules.

		For i915 device level hwmon devices (name "i915") this
		reflects energy input for the entire device. For gt level
		hwmon devices (name "i915_gtN") this reflects energy input
		for the gt.

		Only supported for particular Intel i915 graphics platforms.


code:
What:		/sys/bus/spi/devices/.../bmc_version
Date:		June 2020
KernelVersion:	5.10
Contact:	Xu Yilun <yilun.xu@intel.com>
Description:	Read only. Returns the hardware build version of Intel
		MAX10 BMC chip.
		Format: "0x%x".

What:		/sys/bus/spi/devices/.../bmcfw_version
Date:		June 2020
KernelVersion:	5.10
Contact:	Xu Yilun <yilun.xu@intel.com>
Description:	Read only. Returns the firmware version of Intel MAX10
		BMC chip.
		Format: "0x%x".

What:		/sys/bus/spi/devices/.../mac_address
Date:		January 2021
KernelVersion:  5.12
Contact:	Russ Weight <russell.h.weight@intel.com>
Description:	Read only. Returns the first MAC address in a block
		of sequential MAC addresses assigned to the board
		that is managed by the Intel MAX10 BMC. It is stored in
		FLASH storage and is mirrored in the MAX10 BMC register
		space.
		Format: "%02x:%02x:%02x:%02x:%02x:%02x".

What:		/sys/bus/spi/devices/.../mac_count
Date:		January 2021
KernelVersion:  5.12
Contact:	Russ Weight <russell.h.weight@intel.com>
Description:	Read only. Returns the number of sequential MAC
		addresses assigned to the board managed by the Intel
		MAX10 BMC. This value is stored in FLASH and is mirrored
		in the MAX10 BMC register space.
		Format: "%u".


code:
What:		/sys/bus/platform/drivers/intel-m10bmc-sec-update/.../security/sr_root_entry_hash
Date:		Sep 2022
KernelVersion:	5.20
Contact:	Russ Weight <russell.h.weight@intel.com>
Description:	Read only. Returns the root entry hash for the static
		region if one is programmed, else it returns the
		string: "hash not programmed".  This file is only
		visible if the underlying device supports it.
		Format: string.

What:		/sys/bus/platform/drivers/intel-m10bmc-sec-update/.../security/pr_root_entry_hash
Date:		Sep 2022
KernelVersion:	5.20
Contact:	Russ Weight <russell.h.weight@intel.com>
Description:	Read only. Returns the root entry hash for the partial
		reconfiguration region if one is programmed, else it
		returns the string: "hash not programmed".  This file
		is only visible if the underlying device supports it.
		Format: string.

What:		/sys/bus/platform/drivers/intel-m10bmc-sec-update/.../security/bmc_root_entry_hash
Date:		Sep 2022
KernelVersion:	5.20
Contact:	Russ Weight <russell.h.weight@intel.com>
Description:	Read only. Returns the root entry hash for the BMC image
		if one is programmed, else it returns the string:
		"hash not programmed".  This file is only visible if the
		underlying device supports it.
		Format: string.

What:		/sys/bus/platform/drivers/intel-m10bmc-sec-update/.../security/sr_canceled_csks
Date:		Sep 2022
KernelVersion:	5.20
Contact:	Russ Weight <russell.h.weight@intel.com>
Description:	Read only. Returns a list of indices for canceled code
		signing keys for the static region. The standard bitmap
		list format is used (e.g. "1,2-6,9").

What:		/sys/bus/platform/drivers/intel-m10bmc-sec-update/.../security/pr_canceled_csks
Date:		Sep 2022
KernelVersion:	5.20
Contact:	Russ Weight <russell.h.weight@intel.com>
Description:	Read only. Returns a list of indices for canceled code
		signing keys for the partial reconfiguration region. The
		standard bitmap list format is used (e.g. "1,2-6,9").

What:		/sys/bus/platform/drivers/intel-m10bmc-sec-update/.../security/bmc_canceled_csks
Date:		Sep 2022
KernelVersion:	5.20
Contact:	Russ Weight <russell.h.weight@intel.com>
Description:	Read only. Returns a list of indices for canceled code
		signing keys for the BMC.  The standard bitmap list format
		is used (e.g. "1,2-6,9").

What:		/sys/bus/platform/drivers/intel-m10bmc-sec-update/.../security/flash_count
Date:		Sep 2022
KernelVersion:	5.20
Contact:	Russ Weight <russell.h.weight@intel.com>
Description:	Read only. Returns number of times the secure update
		staging area has been flashed.
		Format: "%u".


code:
What:		/sys/bus/acpi/intel-rapid-start/wakeup_events
Date:		July 2, 2013
KernelVersion:	3.11
Contact:	Matthew Garrett <mjg59@srcf.ucam.org>
Description:	An integer representing a set of wakeup events as follows:
		1: Wake to enter hibernation when the wakeup timer expires
		2: Wake to enter hibernation when the battery reaches a
		critical level

		These values are ORed together. For example, a value of 3
		indicates that the system will wake to enter hibernation when
		either the wakeup timer expires or the battery reaches a
		critical level.

What:		/sys/bus/acpi/intel-rapid-start/wakeup_time
Date:		July 2, 2013
KernelVersion:	3.11
Contact:	Matthew Garrett <mjg59@srcf.ucam.org>
Description:	An integer representing the length of time the system will
		remain asleep before waking up to enter hibernation.
		This value is in minutes.


code:
What:		/sys/bus/auxiliary/devices/intel_vsec.sdsi.X
Date:		Feb 2022
KernelVersion:	5.18
Contact:	"David E. Box" <david.e.box@linux.intel.com>
Description:
		This directory contains interface files for accessing Intel
		On Demand (formerly Software Defined Silicon or SDSi) features
		on a CPU. X represents the socket instance (though not the
		socket ID). The socket ID is determined by reading the
		registers file and decoding it per the specification.

		Some files communicate with On Demand hardware through a
		mailbox. Should the operation fail, one of the following error
		codes may be returned:

		==========	=====
		Error Code	Cause
		==========	=====
		EIO		General mailbox failure. Log may indicate cause.
		EBUSY		Mailbox is owned by another agent.
		EPERM		On Demand capability is not enabled in hardware.
		EPROTO		Failure in mailbox protocol detected by driver.
				See log for details.
		EOVERFLOW	For provision commands, the size of the data
				exceeds what may be written.
		ESPIPE		Seeking is not allowed.
		ETIMEDOUT	Failure to complete mailbox transaction in time.
		==========	=====

What:		/sys/bus/auxiliary/devices/intel_vsec.sdsi.X/guid
Date:		Feb 2022
KernelVersion:	5.18
Contact:	"David E. Box" <david.e.box@linux.intel.com>
Description:
		(RO) The GUID for the registers file. The GUID identifies
		the layout of the registers file in this directory.
		Information about the register layouts for a particular GUID
		is available at http://github.com/intel/intel-sdsi

What:		/sys/bus/auxiliary/devices/intel_vsec.sdsi.X/registers
Date:		Feb 2022
KernelVersion:	5.18
Contact:	"David E. Box" <david.e.box@linux.intel.com>
Description:
		(RO) Contains information needed by applications to provision
		a CPU and monitor status information. The layout of this file
		is determined by the GUID in this directory. Information about
		the layout for a particular GUID is available at
		http://github.com/intel/intel-sdsi

What:		/sys/bus/auxiliary/devices/intel_vsec.sdsi.X/provision_akc
Date:		Feb 2022
KernelVersion:	5.18
Contact:	"David E. Box" <david.e.box@linux.intel.com>
Description:
		(WO) Used to write an Authentication Key Certificate (AKC) to
		the On Demand NVRAM for the CPU. The AKC is used to authenticate
		a Capability Activation Payload. Mailbox command.

What:		/sys/bus/auxiliary/devices/intel_vsec.sdsi.X/provision_cap
Date:		Feb 2022
KernelVersion:	5.18
Contact:	"David E. Box" <david.e.box@linux.intel.com>
Description:
		(WO) Used to write a Capability Activation Payload (CAP) to the
		On Demand NVRAM for the CPU. CAPs are used to activate a given
		CPU feature. A CAP is validated by On Demand hardware using a
		previously provisioned AKC file. Upon successful authentication,
		the CPU configuration is updated. A cold reboot is required to
		fully activate the feature. Mailbox command.

What:		/sys/bus/auxiliary/devices/intel_vsec.sdsi.X/meter_certificate
Date:		Nov 2022
KernelVersion:	6.2
Contact:	"David E. Box" <david.e.box@linux.intel.com>
Description:
		(RO) Used to read back the current meter certificate for the CPU
		from Intel On Demand hardware. The meter certificate contains
		utilization metrics of On Demand enabled features. Mailbox
		command.

What:		/sys/bus/auxiliary/devices/intel_vsec.sdsi.X/state_certificate
Date:		Feb 2022
KernelVersion:	5.18
Contact:	"David E. Box" <david.e.box@linux.intel.com>
Description:
		(RO) Used to read back the current state certificate for the CPU
		from On Demand hardware. The state certificate contains
		information about the current licenses on the CPU. Mailbox
		command.


code:
What:		/sys/devices/*/<our-device>/nvmem
Date:		December 2017
Contact:	PrasannaKumar Muralidharan <prasannatsmkumar@gmail.com>
Description:	read-only access to the efuse on the Ingenic JZ4780 SoC
		The SoC has a one time programmable 8K efuse that is
		split into segments. The driver supports read only.
		The segments are:

		===== ======== =================
		0x000   64 bit Random Number
		0x008  128 bit Ingenic Chip ID
		0x018  128 bit Customer ID
		0x028 3520 bit Reserved
		0x1E0    8 bit Protect Segment
		0x1E1 2296 bit HDMI Key
		0x300 2048 bit Security boot key
		===== ======== =================

Users:		any user space application which wants to read the Chip
		and Customer ID


code:
What:           /sys/bus/pci/drivers/pciback/quirks
Date:           Oct 2011
KernelVersion:  3.1
Contact:        xen-devel@lists.xenproject.org
Description:
                If the permissive attribute is set, then writing a string in
                the format of DDDD:BB:DD.F-REG:SIZE:MASK will allow the guest
                to write and read from the PCI device. That is Domain:Bus:
                Device.Function-Register:Size:Mask (Domain is optional).
                For example::

                  #echo 00:19.0-E0:2:FF > /sys/bus/pci/drivers/pciback/quirks

                will allow the guest to read and write to the configuration
                register 0x0E.

What:           /sys/bus/pci/drivers/pciback/allow_interrupt_control
Date:           Jan 2020
KernelVersion:  5.6
Contact:        xen-devel@lists.xenproject.org
Description:
                List of devices which can have interrupt control flag (INTx,
                MSI, MSI-X) set by a connected guest. It is meant to be set
                only when the guest is a stubdomain hosting device model (qemu)
                and the actual device is assigned to a HVM. It is not safe
                (similar to permissive attribute) to set for a devices assigned
                to a PV guest. The device is automatically removed from this
                list when the connected pcifront terminates.


code:
What:		/sys/class/tpm/tpmX/ppi/
Date:		August 2012
KernelVersion:	3.6
Contact:	xiaoyan.zhang@intel.com
Description:
		This folder includes the attributes related with PPI (Physical
		Presence Interface). Only if TPM is supported by BIOS, this
		folder makes sense. The folder path can be got by command
		'find /sys/ -name 'pcrs''. For the detail information of PPI,
		please refer to the PPI specification from

		http://www.trustedcomputinggroup.org/

		In Linux 4.2 ppi was moved to the character device directory.
		A symlink from tpmX/device/ppi to tpmX/ppi to provide backwards
		compatibility.

What:		/sys/class/tpm/tpmX/ppi/version
Date:		August 2012
Contact:	xiaoyan.zhang@intel.com
Description:
		This attribute shows the version of the PPI supported by the
		platform.
		This file is readonly.

What:		/sys/class/tpm/tpmX/ppi/request
Date:		August 2012
Contact:	xiaoyan.zhang@intel.com
Description:
		This attribute shows the request for an operation to be
		executed in the pre-OS environment. It is the only input from
		the OS to the pre-OS environment. The request should be an
		integer value range from 1 to 160, and 0 means no request.
		This file can be read and written.

What:		/sys/class/tpm/tpmX/ppi/response
Date:		August 2012
Contact:	xiaoyan.zhang@intel.com
Description:
		This attribute shows the response to the most recent operation
		request it acted upon. The format is "<request> <response num>
		: <response description>".
		This file is readonly.

What:		/sys/class/tpm/tpmX/ppi/transition_action
Date:		August 2012
Contact:	xiaoyan.zhang@intel.com
Description:
		This attribute shows the platform-specific action that should
		take place in order to transition to the BIOS for execution of
		a requested operation. The format is "<action num>: <action
		description>".
		This file is readonly.

What:		/sys/class/tpm/tpmX/ppi/tcg_operations
Date:		August 2012
Contact:	xiaoyan.zhang@intel.com
Description:
		This attribute shows whether it is allowed to request an
		operation to be executed in the pre-OS environment by the BIOS
		for the requests defined by TCG, i.e. requests from 1 to 22.
		The format is "<request> <status num>: <status description>".
		This attribute is only supported by PPI version 1.2+.
		This file is readonly.

What:		/sys/class/tpm/tpmX/ppi/vs_operations
Date:		August 2012
Contact:	xiaoyan.zhang@intel.com
Description:
		This attribute shows whether it is allowed to request an
		operation to be executed in the pre-OS environment by the BIOS
		for the verdor specific requests, i.e. requests from 128 to
		255. The format is same with tcg_operations. This attribute
		is also only supported by PPI version 1.2+.
		This file is readonly.


code:
What:		/sys/bus/pci/devices/<BDF>/qat/state
Date:		June 2022
KernelVersion:	5.20
Contact:	qat-linux@intel.com
Description:	(RW) Reports the current state of the QAT device. Write to
		the file to start or stop the device.

		The values are:

		* up: the device is up and running
		* down: the device is down

		It is possible to transition the device from up to down only
		if the device is up and vice versa.

		This attribute is only available for qat_4xxx devices.

What:		/sys/bus/pci/devices/<BDF>/qat/cfg_services
Date:		June 2022
KernelVersion:	5.20
Contact:	qat-linux@intel.com
Description:	(RW) Reports the current configuration of the QAT device.
		Write to the file to change the configured services.

		The values are:

		* sym;asym: the device is configured for running crypto
		  services
		* dc: the device is configured for running compression services

		It is possible to set the configuration only if the device
		is in the `down` state (see /sys/bus/pci/devices/<BDF>/qat/state)

		The following example shows how to change the configuration of
		a device configured for running crypto services in order to
		run data compression::

			# cat /sys/bus/pci/devices/<BDF>/qat/state
			up
			# cat /sys/bus/pci/devices/<BDF>/qat/cfg_services
			sym;asym
			# echo down > /sys/bus/pci/devices/<BDF>/qat/state
			# echo dc > /sys/bus/pci/devices/<BDF>/qat/cfg_services
			# echo up > /sys/bus/pci/devices/<BDF>/qat/state
			# cat /sys/bus/pci/devices/<BDF>/qat/cfg_services
			dc

		This attribute is only available for qat_4xxx devices.


code:
What:		/sys/devices/platform/samsung/performance_level
Date:		January 1, 2010
KernelVersion:	2.6.33
Contact:	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Description:	Some Samsung laptops have different "performance levels"
		that can be modified by a function key, and by this
		sysfs file.  These values don't always make a whole lot
		of sense, but some users like to modify them to keep
		their fans quiet at all costs.  Reading from this file
		will show the current performance level.  Writing to the
		file can change this value.

			Valid options:
				- "silent"
				- "normal"
				- "overclock"

		Note that not all laptops support all of these options.
		Specifically, not all support the "overclock" option,
		and it's still unknown if this value even changes
		anything, other than making the user feel a bit better.

What:		/sys/devices/platform/samsung/battery_life_extender
Date:		December 1, 2011
KernelVersion:	3.3
Contact:	Corentin Chary <corentin.chary@gmail.com>
Description:	Max battery charge level can be modified, battery cycle
		life can be extended by reducing the max battery charge
		level.

		- 0 means normal battery mode (100% charge)
		- 1 means battery life extender mode (80% charge)

What:		/sys/devices/platform/samsung/usb_charge
Date:		December 1, 2011
KernelVersion:	3.3
Contact:	Corentin Chary <corentin.chary@gmail.com>
Description:	Use your USB ports to charge devices, even
		when your laptop is powered off.
		1 means enabled, 0 means disabled.

What:		/sys/devices/platform/samsung/lid_handling
Date:		December 11, 2014
KernelVersion:	3.19
Contact:	Julijonas Kikutis <julijonas.kikutis@gmail.com>
Description:	Some Samsung laptops handle lid closing quicker and
		only handle lid opening with this mode enabled.
		1 means enabled, 0 means disabled.


code:
What:		/sys/bus/scsi/drivers/st/debug_flag
Date:		October 2015
KernelVersion:	?.?
Contact:	shane.seymour@hpe.com
Description:
		This file allows you to turn debug output from the st driver
		off if you write a '0' to the file or on if you write a '1'.
		Note that debug output requires that the module be compiled
		with the #define DEBUG set to a non-zero value (this is the
		default). If DEBUG is set to 0 then this file will not
		appear in sysfs as its presence is conditional upon debug
		output support being compiled into the module.


code:
What:		/sys/devices/*/<our-device>/fuse
Date:		February 2014
Contact:	Peter De Schrijver <pdeschrijver@nvidia.com>
Description:	read-only access to the efuses on Tegra20, Tegra30, Tegra114
		and Tegra124 SoC's from NVIDIA. The efuses contain write once
		data programmed at the factory. The data is layed out in 32bit
		words in LSB first format. Each bit represents a single value
		as decoded from the fuse registers. Bits order/assignment
		exactly matches the HW registers, including any unused bits.
Users:		any user space application which wants to read the efuses on
		Tegra SoC's


code:
What:		/sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/kbd_backlight_mode
Date:		June 8, 2014
KernelVersion:	3.15
Contact:	Azael Avalos <coproscefalo@gmail.com>
Description:	This file controls the keyboard backlight operation mode, valid
		values are:

			* 0x1  -> FN-Z
			* 0x2  -> AUTO (also called TIMER)
			* 0x8  -> ON
			* 0x10 -> OFF

		Note that from kernel 3.16 onwards this file accepts all listed
		parameters, kernel 3.15 only accepts the first two (FN-Z and
		AUTO).
		Also note that toggling this value on type 1 devices, requires
		a reboot for changes to take effect.
Users:		KToshiba

What:		/sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/kbd_backlight_timeout
Date:		June 8, 2014
KernelVersion:	3.15
Contact:	Azael Avalos <coproscefalo@gmail.com>
Description:	This file controls the timeout of the keyboard backlight
		whenever the operation mode is set to AUTO (or TIMER),
		valid values range from 0-60.
		Note that the kernel 3.15 only had support for the first
		keyboard type, the kernel 3.16 added support for the second
		type and the range accepted for type 2 is 1-60.
		See the entry named "kbd_type"
Users:		KToshiba

What:		/sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/position
Date:		June 8, 2014
KernelVersion:	3.15
Contact:	Azael Avalos <coproscefalo@gmail.com>
Description:	This file shows the absolute position of the built-in
		accelereometer.

What:		/sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/touchpad
Date:		June 8, 2014
KernelVersion:	3.15
Contact:	Azael Avalos <coproscefalo@gmail.com>
Description:	This files controls the status of the touchpad and pointing
		stick (if available), valid values are:

			* 0 -> OFF
			* 1 -> ON

Users:		KToshiba

What:		/sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/available_kbd_modes
Date:		August 3, 2014
KernelVersion:	3.16
Contact:	Azael Avalos <coproscefalo@gmail.com>
Description:	This file shows the supported keyboard backlight modes
		the system supports, which can be:

			* 0x1  -> FN-Z
			* 0x2  -> AUTO (also called TIMER)
			* 0x8  -> ON
			* 0x10 -> OFF

		Note that not all keyboard types support the listed modes.
		See the entry named "available_kbd_modes"
Users:		KToshiba

What:		/sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/kbd_type
Date:		August 3, 2014
KernelVersion:	3.16
Contact:	Azael Avalos <coproscefalo@gmail.com>
Description:	This file shows the current keyboard backlight type,
		which can be:

			* 1 -> Type 1, supporting modes FN-Z and AUTO
			* 2 -> Type 2, supporting modes TIMER, ON and OFF
Users:		KToshiba

What:		/sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/usb_sleep_charge
Date:		January 23, 2015
KernelVersion:	4.0
Contact:	Azael Avalos <coproscefalo@gmail.com>
Description:	This file controls the USB Sleep & Charge charging mode, which
		can be:

			* 0 -> Disabled		(0x00)
			* 1 -> Alternate	(0x09)
			* 2 -> Auto		(0x21)
			* 3 -> Typical		(0x11)

		Note that from kernel 4.1 onwards this file accepts all listed
		values, kernel 4.0 only supports the first three.
		Note that this feature only works when connected to power, if
		you want to use it under battery, see the entry named
		"sleep_functions_on_battery"
Users:		KToshiba

What:		/sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/sleep_functions_on_battery
Date:		January 23, 2015
KernelVersion:	4.0
Contact:	Azael Avalos <coproscefalo@gmail.com>
Description:	This file controls the USB Sleep Functions under battery, and
		set the level at which point they will be disabled, accepted
		values can be:

			* 0	-> Disabled
			* 1-100	-> Battery level to disable sleep functions

		Currently it prints two values, the first one indicates if the
		feature is enabled or disabled, while the second one shows the
		current battery level set.
		Note that when the value is set to disabled, the sleep function
		will only work when connected to power.
Users:		KToshiba

What:		/sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/usb_rapid_charge
Date:		January 23, 2015
KernelVersion:	4.0
Contact:	Azael Avalos <coproscefalo@gmail.com>
Description:	This file controls the USB Rapid Charge state, which can be:

			* 0 -> Disabled
			* 1 -> Enabled

		Note that toggling this value requires a reboot for changes to
		take effect.
Users:		KToshiba

What:		/sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/usb_sleep_music
Date:		January 23, 2015
KernelVersion:	4.0
Contact:	Azael Avalos <coproscefalo@gmail.com>
Description:	This file controls the Sleep & Music state, which values can be:

			* 0 -> Disabled
			* 1 -> Enabled

		Note that this feature only works when connected to power, if
		you want to use it under battery, see the entry named
		"sleep_functions_on_battery"
Users:		KToshiba

What:		/sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/version
Date:		February 12, 2015
KernelVersion:	4.0
Contact:	Azael Avalos <coproscefalo@gmail.com>
Description:	This file shows the current version of the driver
Users:		KToshiba

What:		/sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/fan
Date:		February 12, 2015
KernelVersion:	4.0
Contact:	Azael Avalos <coproscefalo@gmail.com>
Description:	This file controls the state of the internal fan, valid
		values are:

			* 0 -> OFF
			* 1 -> ON

What:		/sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/kbd_function_keys
Date:		February 12, 2015
KernelVersion:	4.0
Contact:	Azael Avalos <coproscefalo@gmail.com>
Description:	This file controls the Special Functions (hotkeys) operation
		mode, valid values are:

			* 0 -> Normal Operation
			* 1 -> Special Functions

		In the "Normal Operation" mode, the F{1-12} keys are as usual
		and the hotkeys are accessed via FN-F{1-12}.
		In the "Special Functions" mode, the F{1-12} keys trigger the
		hotkey and the F{1-12} keys are accessed via FN-F{1-12}.
		Note that toggling this value requires a reboot for changes to
		take effect.
Users:		KToshiba

What:		/sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/panel_power_on
Date:		February 12, 2015
KernelVersion:	4.0
Contact:	Azael Avalos <coproscefalo@gmail.com>
Description:	This file controls whether the laptop should turn ON whenever
		the LID is opened, valid values are:

			* 0 -> Disabled
			* 1 -> Enabled

		Note that toggling this value requires a reboot for changes to
		take effect.
Users:		KToshiba

What:		/sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/usb_three
Date:		February 12, 2015
KernelVersion:	4.0
Contact:	Azael Avalos <coproscefalo@gmail.com>
Description:	This file controls the USB 3 functionality, valid values are:

			* 0 -> Disabled (Acts as a regular USB 2)
			* 1 -> Enabled (Full USB 3 functionality)

		Note that toggling this value requires a reboot for changes to
		take effect.
Users:		KToshiba

What:		/sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/cooling_method
Date:		2016
KernelVersion:	4.6
Contact:	Azael Avalos <coproscefalo@gmail.com>
Description:	This file controls the Cooling Method feature.
		Reading this file prints two values, the first is the actual cooling method
		and the second is the maximum cooling method supported.
		When the maximum cooling method is ONE, valid values are:

			* 0 -> Maximum Performance
			* 1 -> Battery Optimized

		When the maximum cooling method is TWO, valid values are:

			* 0 -> Maximum Performance
			* 1 -> Performance
			* 2 -> Battery Optimized

Users:		KToshiba


code:
What:		/sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS620A:00/protection_level
Date:		August 16, 2014
KernelVersion:	3.17
Contact:	Azael Avalos <coproscefalo@gmail.com>
Description:	This file controls the built-in accelerometer protection level,
		valid values are:

			* 0 -> Disabled
			* 1 -> Low
			* 2 -> Medium
			* 3 -> High

		The default potection value is set to 2 (Medium).
Users:		KToshiba

What:		/sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS620A:00/reset_protection
Date:		August 16, 2014
KernelVersion:	3.17
Contact:	Azael Avalos <coproscefalo@gmail.com>
Description:	This file turns off the built-in accelerometer for a few
		seconds and then restore normal operation. Accepting 1 as the
		only parameter.


code:
What:		/sys/bus/typec/devices/.../displayport/configuration
Date:		July 2018
Contact:	Heikki Krogerus <heikki.krogerus@linux.intel.com>
Description:
		Shows the current DisplayPort configuration for the connector.
		Valid values are USB, source and sink. Source means DisplayPort
		source, and sink means DisplayPort sink.

		All supported configurations are listed as space separated list
		with the active one wrapped in square brackets.

		Source example:

			USB [source] sink

		The configuration can be changed by writing to the file

		Note. USB configuration does not equal to Exit Mode. It is
		separate configuration defined in VESA DisplayPort Alt Mode on
		USB Type-C Standard. Functionally it equals to the situation
		where the mode has been exited (to exit the mode, see
		Documentation/ABI/testing/sysfs-bus-typec, and use file
		/sys/bus/typec/devices/.../active).

What:		/sys/bus/typec/devices/.../displayport/pin_assignment
Date:		July 2018
Contact:	Heikki Krogerus <heikki.krogerus@linux.intel.com>
Description:
		VESA DisplayPort Alt Mode on USB Type-C Standard defines six
		different pin assignments for USB Type-C connector that are
		labeled A, B, C, D, E, and F. The supported pin assignments are
		listed as space separated list with the active one wrapped in
		square brackets.

		Example:

			C [D]

		Pin assignment can be changed by writing to the file. It is
		possible to set pin assignment before configuration has been
		set, but the assignment will not be active before the
		connector is actually configured.

		Note. As of VESA DisplayPort Alt Mode on USB Type-C Standard
		version 1.0b, pin assignments A, B, and F are deprecated. Only
		pin assignment D can now carry simultaneously one channel of
		USB SuperSpeed protocol. From user perspective pin assignments C
		and E are equal, where all channels on the connector are used
		for carrying DisplayPort protocol (allowing higher resolutions).


code:
What:           /sys/class/uacce/<dev_name>/api
Date:           Feb 2020
KernelVersion:  5.7
Contact:        linux-accelerators@lists.ozlabs.org
Description:    Api of the device
                Can be any string and up to userspace to parse.
                Application use the api to match the correct driver

What:           /sys/class/uacce/<dev_name>/flags
Date:           Feb 2020
KernelVersion:  5.7
Contact:        linux-accelerators@lists.ozlabs.org
Description:    Attributes of the device, see UACCE_DEV_xxx flag defined in uacce.h

What:           /sys/class/uacce/<dev_name>/available_instances
Date:           Feb 2020
KernelVersion:  5.7
Contact:        linux-accelerators@lists.ozlabs.org
Description:    Available instances left of the device
                Return -ENODEV if uacce_ops get_available_instances is not provided

What:           /sys/class/uacce/<dev_name>/algorithms
Date:           Feb 2020
KernelVersion:  5.7
Contact:        linux-accelerators@lists.ozlabs.org
Description:    Algorithms supported by this accelerator, separated by new line.
                Can be any string and up to userspace to parse.

What:           /sys/class/uacce/<dev_name>/region_mmio_size
Date:           Feb 2020
KernelVersion:  5.7
Contact:        linux-accelerators@lists.ozlabs.org
Description:    Size (bytes) of mmio region queue file

What:           /sys/class/uacce/<dev_name>/region_dus_size
Date:           Feb 2020
KernelVersion:  5.7
Contact:        linux-accelerators@lists.ozlabs.org
Description:    Size (bytes) of dus region queue file


code:
What:		/sys/bus/i2c/drivers/ucsi_ccg/.../do_flash
Date:		May 2019
Contact:	Ajay Gupta <ajayg@nvidia.com>
Description:
		Tell the driver for Cypress CCGx Type-C controller to attempt
		firmware upgrade by writing [Yy1] to the file.