lael-labs/linux

CREDITS+9−0

@@ -1910,6 +1910,15 @@ S: 660 Harvard Ave. #7 · 1909 unmodified lines
1910	S: Santa Clara, CA 95051	1910	S: Santa Clara, CA 95051
1911	S: USA	1911	S: USA
1912		1912
		1913	N: Kukjin Kim
		1914	E: kgene@kernel.org
		1915	D: Samsung S3C, S5P and Exynos ARM architectures
		1916
		1917	N: Sangbeom Kim
		1918	E: sbkim73@samsung.com
		1919	D: Samsung SoC Audio (ASoC) drivers
		1920	D: Samsung PMIC (RTC, regulators, MFD) drivers
		1921
1913	N: Russell King	1922	N: Russell King
1914	E: rmk@arm.linux.org.uk	1923	E: rmk@arm.linux.org.uk
1915	D: Linux/arm integrator, maintainer & hacker	1924	D: Linux/arm integrator, maintainer & hacker

Documentation/ABI/README+9−1

 	layout of the files below for details on how to do this.)
   obsolete/
-  	This directory documents interfaces that are still remaining in
+	This directory documents interfaces that are still remaining in
 	the kernel, but are marked to be removed at some later point in
 	time.  The description of the interface will document the reason
 	why it is obsolete and when it can be expected to be removed.
 		be changed further.
+Note:
+   The fields should be use a simple notation, compatible with ReST markup.
+   Also, the file **should not** have a top-level index, like::
+	===
+	foo
+	===
 How things move between levels:
 Interfaces in stable may move to obsolete, as long as the proper

Documentation/ABI/obsolete/sysfs-class-dax+4−4

@@ -8,11 +8,11 @@ Description: Device DAX is the device-centric analogue of Filesystem · 7 unmodified lines
8	system. Device DAX is strict, precise and predictable.	8	system. Device DAX is strict, precise and predictable.
9	Specifically this interface:	9	Specifically this interface:
10		10
11	1/ Guarantees fault granularity with respect to a given	11	1. Guarantees fault granularity with respect to a given
12	page size (pte, pmd, or pud) set at configuration time.	12	page size (pte, pmd, or pud) set at configuration time.
13		13
14	2/ Enforces deterministic behavior by being strict about	14	2. Enforces deterministic behavior by being strict about
15	what fault scenarios are supported.	15	what fault scenarios are supported.
16		16
17	The /sys/class/dax/ interface enumerates all the	17	The /sys/class/dax/ interface enumerates all the
18	device-dax instances in the system. The ABI is	18	device-dax instances in the system. The ABI is

Documentation/ABI/obsolete/sysfs-driver-hid-roccat-pyra+3−0

 		setting reported by the mouse. This number has to be further
 		processed to receive the real dpi value:
+		===== ====
 		VALUE DPI
+		===== ====
 		1     400
 		2     800
 		4     1600
+		===== ====
 		This file is readonly.
 		Has never been used. If bookkeeping is done, it's done in userland tools.

Documentation/ABI/obsolete/sysfs-gpio+2−0

@@ -13,6 +13,8 @@ Description: · 12 unmodified lines
13	GPIOs are identified as they are inside the kernel, using integers in	13	GPIOs are identified as they are inside the kernel, using integers in
14	the range 0..INT_MAX. See Documentation/admin-guide/gpio for more information.	14	the range 0..INT_MAX. See Documentation/admin-guide/gpio for more information.
15		15
		16	::
		17
16	/sys/class/gpio	18	/sys/class/gpio
17	/export ... asks the kernel to export a GPIO to userspace	19	/export ... asks the kernel to export a GPIO to userspace
18	/unexport ... to return a GPIO to the kernel	20	/unexport ... to return a GPIO to the kernel

Documentation/ABI/removed/devfs+1−0

@@ -5,6 +5,7 @@ Description: · 4 unmodified lines
5	devfs has been unmaintained for a number of years, has unfixable	5	devfs has been unmaintained for a number of years, has unfixable
6	races, contains a naming policy within the kernel that is	6	races, contains a naming policy within the kernel that is
7	against the LSB, and can be replaced by using udev.	7	against the LSB, and can be replaced by using udev.
		8
8	The files fs/devfs/, include/linux/devfs_fs.h were removed,	9	The files fs/devfs/, include/linux/devfs_fs.h were removed,
9	along with the assorted devfs function calls throughout the	10	along with the assorted devfs function calls throughout the
10	kernel tree.	11	kernel tree.

Documentation/ABI/removed/raw1394+1−0

@@ -7,6 +7,7 @@ Description: · 6 unmodified lines
7	to implement sensible device security policies, and its low level	7	to implement sensible device security policies, and its low level
8	of abstraction that required userspace clients to duplicate much	8	of abstraction that required userspace clients to duplicate much
9	of the kernel's ieee1394 core functionality.	9	of the kernel's ieee1394 core functionality.
		10
10	Replaced by /dev/fw*, i.e. the <linux/firewire-cdev.h> ABI of	11	Replaced by /dev/fw*, i.e. the <linux/firewire-cdev.h> ABI of
11	firewire-core.	12	firewire-core.
12		13

Documentation/ABI/removed/sysfs-class-rfkill+1−1

@@ -10,4 +10,4 @@ Description: This file was deprecated because there no longer was a way to · 9 unmodified lines
10	claim just control over a single rfkill instance.	10	claim just control over a single rfkill instance.
11	This file was scheduled to be removed in 2012, and was removed	11	This file was scheduled to be removed in 2012, and was removed
12	in 2016.	12	in 2016.
13	Values: 0: Kernel handles events	13	Values: 0: Kernel handles events

Documentation/ABI/removed/video1394+1−0

@@ -8,6 +8,7 @@ Description: · 7 unmodified lines
8	performance issues in its first generation. Any video1394 user had	8	performance issues in its first generation. Any video1394 user had
9	to use raw1394 + libraw1394 too because video1394 did not provide	9	to use raw1394 + libraw1394 too because video1394 did not provide
10	asynchronous I/O for device discovery and configuration.	10	asynchronous I/O for device discovery and configuration.
		11
11	Replaced by /dev/fw*, i.e. the <linux/firewire-cdev.h> ABI of	12	Replaced by /dev/fw*, i.e. the <linux/firewire-cdev.h> ABI of
12	firewire-core.	13	firewire-core.
13		14

Documentation/ABI/stable/firewire-cdev+38−31

Documentation/ABI/stable/sysfs-acpi-pmprofile+15−11

@@ -1,22 +1,26 @@
1	What: /sys/firmware/acpi/pm_profile	1	What: /sys/firmware/acpi/pm_profile
2	Date: 03-Nov-2011	2	Date: 03-Nov-2011
3	KernelVersion: v3.2	3	KernelVersion: v3.2
4	Contact: linux-acpi@vger.kernel.org	4	Contact: linux-acpi@vger.kernel.org
5	Description: The ACPI pm_profile sysfs interface exports the platform	5	Description: The ACPI pm_profile sysfs interface exports the platform
6	power management (and performance) requirement expectations	6	power management (and performance) requirement expectations
7	as provided by BIOS. The integer value is directly passed as	7	as provided by BIOS. The integer value is directly passed as
8	retrieved from the FADT ACPI table.	8	retrieved from the FADT ACPI table.
9	Values: For possible values see ACPI specification:	9
		10	Values: For possible values see ACPI specification:
10	5.2.9 Fixed ACPI Description Table (FADT)	11	5.2.9 Fixed ACPI Description Table (FADT)
11	Field: Preferred_PM_Profile	12	Field: Preferred_PM_Profile
12		13
13	Currently these values are defined by spec:	14	Currently these values are defined by spec:
14	0 Unspecified	15
15	1 Desktop	16	== =================
16	2 Mobile	17	0 Unspecified
17	3 Workstation	18	1 Desktop
18	4 Enterprise Server	19	2 Mobile
19	5 SOHO Server	20	3 Workstation
20	6 Appliance PC	21	4 Enterprise Server
21	7 Performance Server	22	5 SOHO Server
		23	6 Appliance PC
		24	7 Performance Server
22	>7 Reserved	25	>7 Reserved
		26	== =================

Documentation/ABI/stable/sysfs-bus-firewire+3−0

@@ -47,6 +47,7 @@ Description: · 46 unmodified lines
47	IEEE 1394 node device attribute.	47	IEEE 1394 node device attribute.
48	Read-only and immutable.	48	Read-only and immutable.
49	Values: 1: The sysfs entry represents a local node (a controller card).	49	Values: 1: The sysfs entry represents a local node (a controller card).
		50
50	0: The sysfs entry represents a remote node.	51	0: The sysfs entry represents a remote node.
51		52
52		53
@@ -125,7 +126,9 @@ Description: · 72 unmodified lines
125	Read-only attribute, immutable during the target's lifetime.	126	Read-only attribute, immutable during the target's lifetime.
126	Format, as exposed by firewire-sbp2 since 2.6.22, May 2007:	127	Format, as exposed by firewire-sbp2 since 2.6.22, May 2007:
127	Colon-separated hexadecimal string representations of	128	Colon-separated hexadecimal string representations of
		129
128	u64 EUI-64 : u24 directory_ID : u16 LUN	130	u64 EUI-64 : u24 directory_ID : u16 LUN
		131
129	without 0x prefixes, without whitespace. The former sbp2 driver	132	without 0x prefixes, without whitespace. The former sbp2 driver
130	(removed in 2.6.37 after being superseded by firewire-sbp2) used	133	(removed in 2.6.37 after being superseded by firewire-sbp2) used
131	a somewhat shorter format which was not as close to SAM.	134	a somewhat shorter format which was not as close to SAM.

Documentation/ABI/stable/sysfs-bus-nvmem+10−9

@@ -9,13 +9,14 @@ Description: · 8 unmodified lines
9	Note: This file is only present if CONFIG_NVMEM_SYSFS	9	Note: This file is only present if CONFIG_NVMEM_SYSFS
10	is enabled	10	is enabled
11		11
12	ex:	12	ex::
13	hexdump /sys/bus/nvmem/devices/qfprom0/nvmem
14		13
15	0000000 0000 0000 0000 0000 0000 0000 0000 0000	14	hexdump /sys/bus/nvmem/devices/qfprom0/nvmem
16	*	15
17	00000a0 db10 2240 0000 e000 0c00 0c00 0000 0c00	16	0000000 0000 0000 0000 0000 0000 0000 0000 0000
18	0000000 0000 0000 0000 0000 0000 0000 0000 0000	17	*
19	...	18	00000a0 db10 2240 0000 e000 0c00 0c00 0000 0c00
20	*	19	0000000 0000 0000 0000 0000 0000 0000 0000 0000
21	0001000	20	...
		21	*
		22	0001000

Documentation/ABI/stable/sysfs-bus-usb+4−2

@@ -50,8 +50,10 @@ Description: · 49 unmodified lines
50		50
51	Tools can use this file and the connected_duration file to	51	Tools can use this file and the connected_duration file to
52	compute the percentage of time that a device has been active.	52	compute the percentage of time that a device has been active.
53	For example,	53	For example::
54	echo $((100 * `cat active_duration` / `cat connected_duration`))	54
		55	echo $((100 * `cat active_duration` / `cat connected_duration`))
		56
55	will give an integer percentage. Note that this does not	57	will give an integer percentage. Note that this does not
56	account for counter wrap.	58	account for counter wrap.
57	Users:	59	Users:

Documentation/ABI/stable/sysfs-bus-vmbus+0−7

@@ -63,13 +63,6 @@ Contact: Stephen Hemminger <sthemmin@microsoft.com> · 62 unmodified lines
63	Description: VCPU (sub)channel is affinitized to	63	Description: VCPU (sub)channel is affinitized to
64	Users: tools/hv/lsvmbus and other debugging tools	64	Users: tools/hv/lsvmbus and other debugging tools
65		65
66	What: /sys/bus/vmbus/devices/<UUID>/channels/<N>/cpu
67	Date: September. 2017
68	KernelVersion: 4.14
69	Contact: Stephen Hemminger <sthemmin@microsoft.com>
70	Description: VCPU (sub)channel is affinitized to
71	Users: tools/hv/lsvmbus and other debugging tools
72
73	What: /sys/bus/vmbus/devices/<UUID>/channels/<N>/in_mask	66	What: /sys/bus/vmbus/devices/<UUID>/channels/<N>/in_mask
74	Date: September. 2017	67	Date: September. 2017
75	KernelVersion: 4.14	68	KernelVersion: 4.14

Documentation/ABI/stable/sysfs-bus-w1+1−0

@@ -6,6 +6,7 @@ Description: Bus scanning interval, microseconds component. · 5 unmodified lines
6	control systems are attached/generate presence for as short as	6	control systems are attached/generate presence for as short as
7	100 ms - hence the tens-to-hundreds milliseconds scan intervals	7	100 ms - hence the tens-to-hundreds milliseconds scan intervals
8	are required.	8	are required.
		9
9	see Documentation/w1/w1-generic.rst for detailed information.	10	see Documentation/w1/w1-generic.rst for detailed information.
10	Users: any user space application which wants to know bus scanning	11	Users: any user space application which wants to know bus scanning
11	interval	12	interval

Documentation/ABI/stable/sysfs-class-backlight+1−0

@@ -4,6 +4,7 @@ KernelVersion: 2.6.12 · 3 unmodified lines
4	Contact: Richard Purdie <rpurdie@rpsys.net>	4	Contact: Richard Purdie <rpurdie@rpsys.net>
5	Description:	5	Description:
6	Control BACKLIGHT power, values are FB_BLANK_* from fb.h	6	Control BACKLIGHT power, values are FB_BLANK_* from fb.h
		7
7	- FB_BLANK_UNBLANK (0) : power on.	8	- FB_BLANK_UNBLANK (0) : power on.
8	- FB_BLANK_POWERDOWN (4) : power off	9	- FB_BLANK_POWERDOWN (4) : power off
9	Users: HAL	10	Users: HAL

Documentation/ABI/stable/sysfs-class-infiniband+66−27

 KernelVersion:	v2.6.12
 Contact:	linux-rdma@vger.kernel.org
 Description:
+		=============== ===========================================
 		node_type:	(RO) Node type (CA, RNIC, usNIC, usNIC UDP,
 				switch or router)
 		node_guid:	(RO) Node GUID
 		sys_image_guid:	(RO) System image GUID
+		=============== ===========================================
 What:		/sys/class/infiniband/<device>/node_desc
 Contact:	linux-rdma@vger.kernel.org
 Description:
+		=============== ===============================================
 		lid:		(RO) Port LID
 		rate:		(RO) Port data rate (active width * active
 		cap_mask:	(RO) Port capability mask. 2 bits here are
 				settable- IsCommunicationManagementSupported
-				(set when CM module is loaded) and IsSM (set via
+				(set when CM module is loaded) and IsSM (set
-				open of issmN file).
+				via open of issmN file).
+		=============== ===============================================
 What:		/sys/class/infiniband/<device>/ports/<port-num>/link_layer
 KernelVersion:	v2.6.12
 Contact:	linux-rdma@vger.kernel.org
 Description:
-		Errors info:
+		**Errors info**:
-		-----------
 		symbol_error: (RO) Total number of minor link errors detected on
 		one or more physical lanes.
 		intervention. It can also indicate hardware issues or extremely
 		poor link signal integrity
-		Data info:
+		**Data info**:
-		---------
 		port_xmit_data: (RO) Total number of data octets, divided by 4
 		(lanes), transmitted on all VLs. This is 64 bit counter
 		transmitted on all VLs from the port. This may include multicast
 		packets with errors.
-		Misc info:
+		**Misc info**:
-		---------
 		port_xmit_discards: (RO) Total number of outbound packets
 		discarded by the port because the port is down or congested.
 		two umad devices and two issm devices, while a switch will have
 		one device of each type (for switch port 0).
+		======= =====================================
 		ibdev:	(RO) Show Infiniband (IB) device name
 		port:	(RO) Display port number
+		======= =====================================
 What:		/sys/class/infiniband_mad/abi_version
 KernelVersion:	v2.6.14
 Contact:	linux-rdma@vger.kernel.org
 Description:
+		=============== ===========================================
 		ibdev:		(RO) Display Infiniband (IB) device name
 		abi_version:	(RO) Show ABI version of IB device specific
 				interfaces.
+		=============== ===========================================
 What:		/sys/class/infiniband_verbs/abi_version
 KernelVersion:	v2.6.12
 Contact:	linux-rdma@vger.kernel.org
 Description:
+		=============== ================================================
 		hw_rev:		(RO) Hardware revision number
 		hca_type:	(RO) Host Channel Adapter type: MT23108, MT25208
 				(MT23108 compat mode), MT25208 or MT25204
 		board_id:	(RO) Manufacturing board ID
+		=============== ================================================
 sysfs interface for Mellanox ConnectX HCA IB driver (mlx4)
 KernelVersion:	v2.6.24
 Contact:	linux-rdma@vger.kernel.org
 Description:
+		=============== ===============================
 		hw_rev:		(RO) Hardware revision number
 		hca_type:	(RO) Host channel adapter type
 		board_id:	(RO) Manufacturing board ID
+		=============== ===============================
 What:		/sys/class/infiniband/mlx4_X/iov/ports/<port-num>/gids/<n>
 		example, ports/1/pkeys/10 contains the value at index 10 in port
 		1's P_Key table.
+		======================= ==========================================
 		gids/<n>:		(RO) The physical port gids n = 0..127
 		admin_guids/<n>:	(RW) Allows examining or changing the
 					guest, whenever it uses its pkey index
 					1, will actually be using the real pkey
 					index 10.
+		======================= ==========================================
 What:		/sys/class/infiniband/mlx4_X/iov/<pci-slot-num>/ports/<m>/smi_enabled
 		Enabling QP0 on VFs for selected VF/port. By default, no VFs are
 		enabled for QP0 operation.
-		smi_enabled:	(RO) Indicates whether smi is currently enabled
+		================= ==== ===========================================
-				for the indicated VF/port
+		smi_enabled:	  (RO) Indicates whether smi is currently enabled
+				       for the indicated VF/port
-		enable_smi_admin:(RW) Used by the admin to request that smi
+		enable_smi_admin: (RW) Used by the admin to request that smi
-				capability be enabled or disabled for the
+				       capability be enabled or disabled for the
-				indicated VF/port. 0 = disable, 1 = enable.
+				       indicated VF/port. 0 = disable, 1 = enable.
+		================= ==== ===========================================
 		The requested enablement will occur at the next reset of the VF
 		(e.g. driver restart on the VM which owns the VF).
 Contact:	linux-rdma@vger.kernel.org
 Description:
+		=============== =============================================
 		hw_rev:		(RO) Hardware revision number
 		hca_type:	(RO) Driver short name. Should normally match
 		board_id:	(RO) Manufacturing board id. (Vendor + device
 				information)
+		=============== =============================================
 sysfs interface for Intel IB driver qib
 KernelVersion:	v2.6.35
 Contact:	linux-rdma@vger.kernel.org
 Description:
+		=============== ======================================================
 		version:	(RO) Display version information of installed software
 				and drivers.
 		chip_reset:	(WO) Reset the chip if possible by writing
 				"reset" to this file. Only allowed if no user
 				contexts are open that use chip resources.
+		=============== ======================================================
 What:		/sys/class/infiniband/qibX/ports/N/sl2vl/[0-15]
 Description:
 		Per-port congestion control. Both are binary attributes.
-		cc_table_bin:	(RO) Congestion control table size followed by
+		=============== ================================================
+		cc_table_bin	(RO) Congestion control table size followed by
 				table entries.
-		cc_settings_bin:(RO) Congestion settings: port control, control
+		cc_settings_bin (RO) Congestion settings: port control, control
 				map and an array of 16 entries for the
 				congestion entries - increase, timer, event log
 				trigger threshold and the minimum injection rate
 				delay.
+		=============== ================================================
 What:		/sys/class/infiniband/qibX/ports/N/linkstate/loopback
 What:		/sys/class/infiniband/qibX/ports/N/linkstate/led_override
 Description:
 		[to be documented]
+		=============== ===============================================
 		loopback:	(WO)
 		led_override:	(WO)
 		hrtbt_enable:	(RW)
 				errors. Possible states are- "Initted",
 				"Present", "IB_link_up", "IB_configured" or
 				"Fatal_Hardware_Error".
+		=============== ===============================================
 What:		/sys/class/infiniband/qibX/ports/N/diag_counters/rc_resends
 What:		/sys/class/infiniband/qibX/ports/N/diag_counters/seq_naks
 		linux-rdma@vger.kernel.org
 Description:
+		=============== ===============================================
 		board_id:	(RO) Manufacturing board id
 		config:		(RO) Report the configuration for this PF
 		iface:		(RO) Shows which network interface this usNIC
 				entry is associated to (visible with ifconfig).
+		=============== ===============================================
 What:		/sys/class/infiniband/usnic_X/qpn/summary
 What:		/sys/class/infiniband/usnic_X/qpn/context
 KernelVersion:	v4.6
 Contact:	linux-rdma@vger.kernel.org
 Description:
+		=============== =============================================
 		hw_rev:		(RO) Hardware revision number
 		board_id:	(RO) Manufacturing board id
 				available.
 		tempsense:	(RO) Thermal sense information
+		=============== =============================================
 What:		/sys/class/infiniband/hfi1_X/ports/N/CCMgtA/cc_settings_bin
 Description:
 		Per-port congestion control.
-		cc_table_bin:	(RO) CCA tables used by PSM2 Congestion control
+		=============== ================================================
+		cc_table_bin	(RO) CCA tables used by PSM2 Congestion control
 				table size followed by table entries. Binary
 				attribute.
-		cc_settings_bin:(RO) Congestion settings: port control, control
+		cc_settings_bin (RO) Congestion settings: port control, control
 				map and an array of 16 entries for the
 				congestion entries - increase, timer, event log
 				trigger threshold and the minimum injection rate
 				delay. Binary attribute.
-		cc_prescan:	(RW) enable prescanning for faster BECN
+		cc_prescan	(RW) enable prescanning for faster BECN
 				response. Write "on" to enable and "off" to
 				disable.
+		=============== ================================================
 What:		/sys/class/infiniband/hfi1_X/ports/N/sc2vl/[0-31]
 What:		/sys/class/infiniband/hfi1_X/ports/N/sl2sc/[0-31]
 KernelVersion:	v4.6
 Contact:	linux-rdma@vger.kernel.org
 Description:
+		=============== ===================================================
 		sc2vl/:		(RO) 32 files (0 - 31) used to translate sl->vl
 		sl2sc/:		(RO) 32 files (0 - 31) used to translate sl->sc
 		vl2mtu/:	(RO) 16 files (0 - 15) used to determine MTU for vl
+		=============== ===================================================
 What:		/sys/class/infiniband/hfi1_X/sdma_N/cpu_list
 Description:
 		sdma<N>/ contains one directory per sdma engine (0 - 15)
+		=============== ==============================================
 		cpu_list:	(RW) List of cpus for user-process to sdma
 				engine assignment.
 		vl:		(RO) Displays the virtual lane (vl) the sdma
 				engine maps to.
+		=============== ==============================================
 		This interface gives the user control on the affinity settings
 		for the device. As an example, to set an sdma engine irq
 		affinity and thread affinity of a user processes to use the
 		sdma engine, which is "near" in terms of NUMA configuration, or
-		physical cpu location, the user will do:
+		physical cpu location, the user will do::
-		echo "3" > /proc/irq/<N>/smp_affinity_list
+		  echo "3" > /proc/irq/<N>/smp_affinity_list
-		echo "4-7" > /sys/devices/.../sdma3/cpu_list
+		  echo "4-7" > /sys/devices/.../sdma3/cpu_list
-		cat /sys/devices/.../sdma3/vl
+		  cat /sys/devices/.../sdma3/vl
-		0
+		  0
-		echo "8" > /proc/irq/<M>/smp_affinity_list
+		  echo "8" > /proc/irq/<M>/smp_affinity_list
-		echo "9-12" > /sys/devices/.../sdma4/cpu_list
+		  echo "9-12" > /sys/devices/.../sdma4/cpu_list
-		cat /sys/devices/.../sdma4/vl
+		  cat /sys/devices/.../sdma4/vl
-		1
+		  1
 		to make sure that when a process runs on cpus 4,5,6, or 7, and
 		uses vl=0, then sdma engine 3 is selected by the driver, and
 KernelVersion:	v4.10
 Contact:	linux-rdma@vger.kernel.org
 Description:
+		=============== ==== ========================
 		hw_rev:		(RO) Hardware revision number
 		hca_type:	(RO) Show HCA type (I40IW)
 		board_id:	(RO) I40IW board ID
+		=============== ==== ========================
 sysfs interface for QLogic qedr NIC Driver
 Contact:	linux-rdma@vger.kernel.org
 Description:
+		=============== ==== ========================
 		hw_rev:		(RO) Hardware revision number
 		hca_type:	(RO) Display HCA type
+		=============== ==== ========================
 sysfs interface for VMware Paravirtual RDMA driver
 Contact:	linux-rdma@vger.kernel.org
 Description:
+		=============== ==== =====================================
 		hw_rev:		(RO) Hardware revision number
 		hca_type:	(RO) Host channel adapter type
 		board_id:	(RO) Display PVRDMA manufacturing board ID
+		=============== ==== =====================================
 sysfs interface for Broadcom NetXtreme-E RoCE driver
 KernelVersion:	v4.11
 Contact:	linux-rdma@vger.kernel.org
 Description:
+		=============== ==== =========================
 		hw_rev:		(RO) Hardware revision number
 		hca_type:	(RO) Host channel adapter type
+		=============== ==== =========================

Documentation/ABI/stable/sysfs-class-rfkill+9−4

@@ -2,7 +2,7 @@ rfkill - radio frequency (RF) connector kill switch support · 1 unmodified line
2		2
3	For details to this subsystem look at Documentation/driver-api/rfkill.rst.	3	For details to this subsystem look at Documentation/driver-api/rfkill.rst.
4		4
5	For the deprecated /sys/class/rfkill/*/claim knobs of this interface look in	5	For the deprecated ``/sys/class/rfkill/*/claim`` knobs of this interface look in
6	Documentation/ABI/removed/sysfs-class-rfkill.	6	Documentation/ABI/removed/sysfs-class-rfkill.
7		7
8	What: /sys/class/rfkill	8	What: /sys/class/rfkill
@@ -36,9 +36,10 @@ KernelVersion v2.6.22 · 27 unmodified lines
36	Contact: linux-wireless@vger.kernel.org	36	Contact: linux-wireless@vger.kernel.org
37	Description: Whether the soft blocked state is initialised from non-volatile	37	Description: Whether the soft blocked state is initialised from non-volatile
38	storage at startup.	38	storage at startup.
39	Values: A numeric value.	39	Values: A numeric value:
40	0: false	40
41	1: true	41	- 0: false
		42	- 1: true
42		43
43		44
44	What: /sys/class/rfkill/rfkill[0-9]+/state	45	What: /sys/class/rfkill/rfkill[0-9]+/state
@@ -54,6 +55,7 @@ Description: Current state of the transmitter. · 9 unmodified lines
54	through this interface. There will likely be another attempt to	55	through this interface. There will likely be another attempt to
55	remove it in the future.	56	remove it in the future.
56	Values: A numeric value.	57	Values: A numeric value.
		58
57	0: RFKILL_STATE_SOFT_BLOCKED	59	0: RFKILL_STATE_SOFT_BLOCKED
58	transmitter is turned off by software	60	transmitter is turned off by software
59	1: RFKILL_STATE_UNBLOCKED	61	1: RFKILL_STATE_UNBLOCKED
@@ -69,6 +71,7 @@ KernelVersion v2.6.34 · 9 unmodified lines
69	Contact: linux-wireless@vger.kernel.org	71	Contact: linux-wireless@vger.kernel.org
70	Description: Current hardblock state. This file is read only.	72	Description: Current hardblock state. This file is read only.
71	Values: A numeric value.	73	Values: A numeric value.
		74
72	0: inactive	75	0: inactive
73	The transmitter is (potentially) active.	76	The transmitter is (potentially) active.
74	1: active	77	1: active
@@ -82,7 +85,9 @@ KernelVersion v2.6.34 · 7 unmodified lines
82	Contact: linux-wireless@vger.kernel.org	85	Contact: linux-wireless@vger.kernel.org
83	Description: Current softblock state. This file is read and write.	86	Description: Current softblock state. This file is read and write.
84	Values: A numeric value.	87	Values: A numeric value.
		88
85	0: inactive	89	0: inactive
86	The transmitter is (potentially) active.	90	The transmitter is (potentially) active.
		91
87	1: active	92	1: active
88	The transmitter is turned off by software.	93	The transmitter is turned off by software.

Documentation/ABI/stable/sysfs-class-tpm+50−50

@@ -32,11 +32,11 @@ KernelVersion: 2.6.12 · 31 unmodified lines
32	Contact: linux-integrity@vger.kernel.org	32	Contact: linux-integrity@vger.kernel.org
33	Description: The "caps" property contains TPM manufacturer and version info.	33	Description: The "caps" property contains TPM manufacturer and version info.
34		34
35	Example output:	35	Example output::
36		36
37	Manufacturer: 0x53544d20	37	Manufacturer: 0x53544d20
38	TCG version: 1.2	38	TCG version: 1.2
39	Firmware version: 8.16	39	Firmware version: 8.16
40		40
41	Manufacturer is a hex dump of the 4 byte manufacturer info	41	Manufacturer is a hex dump of the 4 byte manufacturer info
42	space in a TPM. TCG version shows the TCG TPM spec level that	42	space in a TPM. TCG version shows the TCG TPM spec level that
@@ -54,9 +54,9 @@ Description: The "durations" property shows the 3 vendor-specific values · 11 unmodified lines
54	any longer than necessary before starting to poll for a	54	any longer than necessary before starting to poll for a
55	result.	55	result.
56		56
57	Example output:	57	Example output::
58		58
59	3015000 4508000 180995000 [original]	59	3015000 4508000 180995000 [original]
60		60
61	Here the short, medium and long durations are displayed in	61	Here the short, medium and long durations are displayed in
62	usecs. "[original]" indicates that the values are displayed	62	usecs. "[original]" indicates that the values are displayed
@@ -92,14 +92,14 @@ Description: The "pcrs" property will dump the current value of all Platform · 29 unmodified lines
92	values may be constantly changing, the output is only valid	92	values may be constantly changing, the output is only valid
93	for a snapshot in time.	93	for a snapshot in time.
94		94
95	Example output:	95	Example output::
96		96
97	PCR-00: 3A 3F 78 0F 11 A4 B4 99 69 FC AA 80 CD 6E 39 57 C3 3B 22 75	97	PCR-00: 3A 3F 78 0F 11 A4 B4 99 69 FC AA 80 CD 6E 39 57 C3 3B 22 75
98	PCR-01: 3A 3F 78 0F 11 A4 B4 99 69 FC AA 80 CD 6E 39 57 C3 3B 22 75	98	PCR-01: 3A 3F 78 0F 11 A4 B4 99 69 FC AA 80 CD 6E 39 57 C3 3B 22 75
99	PCR-02: 3A 3F 78 0F 11 A4 B4 99 69 FC AA 80 CD 6E 39 57 C3 3B 22 75	99	PCR-02: 3A 3F 78 0F 11 A4 B4 99 69 FC AA 80 CD 6E 39 57 C3 3B 22 75
100	PCR-03: 3A 3F 78 0F 11 A4 B4 99 69 FC AA 80 CD 6E 39 57 C3 3B 22 75	100	PCR-03: 3A 3F 78 0F 11 A4 B4 99 69 FC AA 80 CD 6E 39 57 C3 3B 22 75
101	PCR-04: 3A 3F 78 0F 11 A4 B4 99 69 FC AA 80 CD 6E 39 57 C3 3B 22 75	101	PCR-04: 3A 3F 78 0F 11 A4 B4 99 69 FC AA 80 CD 6E 39 57 C3 3B 22 75
102	...	102	...
103		103
104	The number of PCRs and hex bytes needed to represent a PCR	104	The number of PCRs and hex bytes needed to represent a PCR
105	value will vary depending on TPM chip version. For TPM 1.1 and	105	value will vary depending on TPM chip version. For TPM 1.1 and
@@ -119,44 +119,44 @@ Description: The "pubek" property will return the TPM's public endorsement · 13 unmodified lines
119	ated at TPM manufacture time and exists for the life of the	119	ated at TPM manufacture time and exists for the life of the
120	chip.	120	chip.
121		121
122	Example output:	122	Example output::
123		123
124	Algorithm: 00 00 00 01	124	Algorithm: 00 00 00 01
125	Encscheme: 00 03	125	Encscheme: 00 03
126	Sigscheme: 00 01	126	Sigscheme: 00 01
127	Parameters: 00 00 08 00 00 00 00 02 00 00 00 00	127	Parameters: 00 00 08 00 00 00 00 02 00 00 00 00
128	Modulus length: 256	128	Modulus length: 256
129	Modulus:	129	Modulus:
130	B4 76 41 82 C9 20 2C 10 18 40 BC 8B E5 44 4C 6C	130	B4 76 41 82 C9 20 2C 10 18 40 BC 8B E5 44 4C 6C
131	3A B2 92 0C A4 9B 2A 83 EB 5C 12 85 04 48 A0 B6	131	3A B2 92 0C A4 9B 2A 83 EB 5C 12 85 04 48 A0 B6
132	1E E4 81 84 CE B2 F2 45 1C F0 85 99 61 02 4D EB	132	1E E4 81 84 CE B2 F2 45 1C F0 85 99 61 02 4D EB
133	86 C4 F7 F3 29 60 52 93 6B B2 E5 AB 8B A9 09 E3	133	86 C4 F7 F3 29 60 52 93 6B B2 E5 AB 8B A9 09 E3
134	D7 0E 7D CA 41 BF 43 07 65 86 3C 8C 13 7A D0 8B	134	D7 0E 7D CA 41 BF 43 07 65 86 3C 8C 13 7A D0 8B
135	82 5E 96 0B F8 1F 5F 34 06 DA A2 52 C1 A9 D5 26	135	82 5E 96 0B F8 1F 5F 34 06 DA A2 52 C1 A9 D5 26
136	0F F4 04 4B D9 3F 2D F2 AC 2F 74 64 1F 8B CD 3E	136	0F F4 04 4B D9 3F 2D F2 AC 2F 74 64 1F 8B CD 3E
137	1E 30 38 6C 70 63 69 AB E2 50 DF 49 05 2E E1 8D	137	1E 30 38 6C 70 63 69 AB E2 50 DF 49 05 2E E1 8D
138	6F 78 44 DA 57 43 69 EE 76 6C 38 8A E9 8E A3 F0	138	6F 78 44 DA 57 43 69 EE 76 6C 38 8A E9 8E A3 F0
139	A7 1F 3C A8 D0 12 15 3E CA 0E BD FA 24 CD 33 C6	139	A7 1F 3C A8 D0 12 15 3E CA 0E BD FA 24 CD 33 C6
140	47 AE A4 18 83 8E 22 39 75 93 86 E6 FD 66 48 B6	140	47 AE A4 18 83 8E 22 39 75 93 86 E6 FD 66 48 B6
141	10 AD 94 14 65 F9 6A 17 78 BD 16 53 84 30 BF 70	141	10 AD 94 14 65 F9 6A 17 78 BD 16 53 84 30 BF 70
142	E0 DC 65 FD 3C C6 B0 1E BF B9 C1 B5 6C EF B1 3A	142	E0 DC 65 FD 3C C6 B0 1E BF B9 C1 B5 6C EF B1 3A
143	F8 28 05 83 62 26 11 DC B4 6B 5A 97 FF 32 26 B6	143	F8 28 05 83 62 26 11 DC B4 6B 5A 97 FF 32 26 B6
144	F7 02 71 CF 15 AE 16 DD D1 C1 8E A8 CF 9B 50 7B	144	F7 02 71 CF 15 AE 16 DD D1 C1 8E A8 CF 9B 50 7B
145	C3 91 FF 44 1E CF 7C 39 FE 17 77 21 20 BD CE 9B	145	C3 91 FF 44 1E CF 7C 39 FE 17 77 21 20 BD CE 9B
146		146
147	Possible values:	147	Possible values::
148		148
149	Algorithm: TPM_ALG_RSA (1)	149	Algorithm: TPM_ALG_RSA (1)
150	Encscheme: TPM_ES_RSAESPKCSv15 (2)	150	Encscheme: TPM_ES_RSAESPKCSv15 (2)
151	TPM_ES_RSAESOAEP_SHA1_MGF1 (3)	151	TPM_ES_RSAESOAEP_SHA1_MGF1 (3)
152	Sigscheme: TPM_SS_NONE (1)	152	Sigscheme: TPM_SS_NONE (1)
153	Parameters, a byte string of 3 u32 values:	153	Parameters, a byte string of 3 u32 values:
154	Key Length (bits): 00 00 08 00 (2048)	154	Key Length (bits): 00 00 08 00 (2048)
155	Num primes: 00 00 00 02 (2)	155	Num primes: 00 00 00 02 (2)
156	Exponent Size: 00 00 00 00 (0 means the	156	Exponent Size: 00 00 00 00 (0 means the
157	default exp)	157	default exp)
158	Modulus Length: 256 (bytes)	158	Modulus Length: 256 (bytes)
159	Modulus: The 256 byte Endorsement Key modulus	159	Modulus: The 256 byte Endorsement Key modulus
160		160
161	What: /sys/class/tpm/tpmX/device/temp_deactivated	161	What: /sys/class/tpm/tpmX/device/temp_deactivated
162	Date: April 2006	162	Date: April 2006
@@ -176,9 +176,9 @@ Description: The "timeouts" property shows the 4 vendor-specific values · 13 unmodified lines
176	timeouts is defined by the TPM interface spec that the chip	176	timeouts is defined by the TPM interface spec that the chip
177	conforms to.	177	conforms to.
178		178
179	Example output:	179	Example output::
180		180
181	750000 750000 750000 750000 [original]	181	750000 750000 750000 750000 [original]
182		182
183	The four timeout values are shown in usecs, with a trailing	183	The four timeout values are shown in usecs, with a trailing
184	"[original]" or "[adjusted]" depending on whether the values	184	"[original]" or "[adjusted]" depending on whether the values
@@ -191,6 +191,6 @@ Contact: linux-integrity@vger.kernel.org · 6 unmodified lines
191	Description: The "tpm_version_major" property shows the TCG spec major version	191	Description: The "tpm_version_major" property shows the TCG spec major version
192	implemented by the TPM device.	192	implemented by the TPM device.
193		193
194	Example output:	194	Example output::
195		195
196	2	196	2

Documentation/ABI/stable/sysfs-devices+3−2

@@ -1,5 +1,6 @@
1	# Note: This documents additional properties of any device beyond what	1	Note:
2	# is documented in Documentation/admin-guide/sysfs-rules.rst	2	This documents additional properties of any device beyond what
		3	is documented in Documentation/admin-guide/sysfs-rules.rst
3		4
4	What: /sys/devices/*/of_node	5	What: /sys/devices/*/of_node
5	Date: February 2015	6	Date: February 2015

Documentation/ABI/stable/sysfs-driver-firmware-zynqmp+37−25

@@ -12,13 +12,15 @@ Description: · 11 unmodified lines
12	resets. Three registers are used by the FSBL and	12	resets. Three registers are used by the FSBL and
13	other Xilinx software products: GLOBAL_GEN_STORAGE{4:6}.	13	other Xilinx software products: GLOBAL_GEN_STORAGE{4:6}.
14		14
15	Usage:	15	Usage::
16	# cat /sys/devices/platform/firmware\:zynqmp-firmware/ggs0	16
17	# echo <value> > /sys/devices/platform/firmware\:zynqmp-firmware/ggs0	17	# cat /sys/devices/platform/firmware\:zynqmp-firmware/ggs0
		18	# echo <value> > /sys/devices/platform/firmware\:zynqmp-firmware/ggs0
		19
		20	Example::
18		21
19	Example:	22	# cat /sys/devices/platform/firmware\:zynqmp-firmware/ggs0
20	# cat /sys/devices/platform/firmware\:zynqmp-firmware/ggs0	23	# echo 0x1234ABCD > /sys/devices/platform/firmware\:zynqmp-firmware/ggs0
21	# echo 0x1234ABCD > /sys/devices/platform/firmware\:zynqmp-firmware/ggs0
22		24
23	Users: Xilinx	25	Users: Xilinx
24		26
@@ -39,13 +41,15 @@ Description: · 14 unmodified lines
39	software products: PERS_GLOB_GEN_STORAGE{4:7}.	41	software products: PERS_GLOB_GEN_STORAGE{4:7}.
40	Register is reset only by a POR reset.	42	Register is reset only by a POR reset.
41		43
42	Usage:	44	Usage::
43	# cat /sys/devices/platform/firmware\:zynqmp-firmware/pggs0	45
44	# echo <value> > /sys/devices/platform/firmware\:zynqmp-firmware/pggs0	46	# cat /sys/devices/platform/firmware\:zynqmp-firmware/pggs0
		47	# echo <value> > /sys/devices/platform/firmware\:zynqmp-firmware/pggs0
		48
		49	Example::
45		50
46	Example:	51	# cat /sys/devices/platform/firmware\:zynqmp-firmware/pggs0
47	# cat /sys/devices/platform/firmware\:zynqmp-firmware/pggs0	52	# echo 0x1234ABCD > /sys/devices/platform/firmware\:zynqmp-firmware/pggs0
48	# echo 0x1234ABCD > /sys/devices/platform/firmware\:zynqmp-firmware/pggs0
49		53
50	Users: Xilinx	54	Users: Xilinx
51		55
@@ -61,23 +65,28 @@ Description: · 9 unmodified lines
61		65
62	Following are available shutdown scopes(subtypes):	66	Following are available shutdown scopes(subtypes):
63		67
64	subsystem: Only the APU along with all of its peripherals	68	subsystem:
		69	Only the APU along with all of its peripherals
65	not used by other processing units will be	70	not used by other processing units will be
66	shut down. This may result in the FPD power	71	shut down. This may result in the FPD power
67	domain being shut down provided that no other	72	domain being shut down provided that no other
68	processing unit uses FPD peripherals or DRAM.	73	processing unit uses FPD peripherals or DRAM.
69	ps_only: The complete PS will be shut down, including the	74	ps_only:
		75	The complete PS will be shut down, including the
70	RPU, PMU, etc. Only the PL domain (FPGA)	76	RPU, PMU, etc. Only the PL domain (FPGA)
71	remains untouched.	77	remains untouched.
72	system: The complete system/device is shut down.	78	system:
		79	The complete system/device is shut down.
73		80
74	Usage:	81	Usage::
75	# cat /sys/devices/platform/firmware\:zynqmp-firmware/shutdown_scope	82
76	# echo <scope> > /sys/devices/platform/firmware\:zynqmp-firmware/shutdown_scope	83	# cat /sys/devices/platform/firmware\:zynqmp-firmware/shutdown_scope
		84	# echo <scope> > /sys/devices/platform/firmware\:zynqmp-firmware/shutdown_scope
		85
		86	Example::
77		87
78	Example:	88	# cat /sys/devices/platform/firmware\:zynqmp-firmware/shutdown_scope
79	# cat /sys/devices/platform/firmware\:zynqmp-firmware/shutdown_scope	89	# echo "subsystem" > /sys/devices/platform/firmware\:zynqmp-firmware/shutdown_scope
80	# echo "subsystem" > /sys/devices/platform/firmware\:zynqmp-firmware/shutdown_scope
81		90
82	Users: Xilinx	91	Users: Xilinx
83		92
@@ -94,10 +103,13 @@ Description: · 10 unmodified lines
94	system restart.	103	system restart.
95		104
96	Usage:	105	Usage:
97	Set healthy bit
98	# echo 1 > /sys/devices/platform/firmware\:zynqmp-firmware/health_status
99		106
100	Unset healthy bit	107	Set healthy bit::
101	# echo 0 > /sys/devices/platform/firmware\:zynqmp-firmware/health_status	108
		109	# echo 1 > /sys/devices/platform/firmware\:zynqmp-firmware/health_status
		110
		111	Unset healthy bit::
		112
		113	# echo 0 > /sys/devices/platform/firmware\:zynqmp-firmware/health_status
102		114
103	Users: Xilinx	115	Users: Xilinx

Documentation/ABI/stable/sysfs-driver-ib_srp+1−0

@@ -6,6 +6,7 @@ Description: Interface for making ib_srp connect to a new target. · 5 unmodified lines
6	One can request ib_srp to connect to a new target by writing	6	One can request ib_srp to connect to a new target by writing
7	a comma-separated list of login parameters to this sysfs	7	a comma-separated list of login parameters to this sysfs
8	attribute. The supported parameters are:	8	attribute. The supported parameters are:
		9
9	* id_ext, a 16-digit hexadecimal number specifying the eight	10	* id_ext, a 16-digit hexadecimal number specifying the eight
10	byte identifier extension in the 16-byte SRP target port	11	byte identifier extension in the 16-byte SRP target port
11	identifier. The target port identifier is sent by ib_srp	12	identifier. The target port identifier is sent by ib_srp

Documentation/ABI/stable/sysfs-driver-speakup+4−0

Documentation/ABI/stable/sysfs-firmware-efi-vars+4−0

 		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:
 		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.
 				instructs the EFI firmware to remove any
 				variable that has a matching vendor GUID
 				and variable key name.
+		=============== ========================================

Documentation/ABI/stable/sysfs-firmware-opal-dump+5−0

 		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.
 				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
 				inaccessible.
 				Reading this file will get a list of
 				supported actions.
+		=============== ===============================================

Documentation/ABI/stable/sysfs-firmware-opal-elog+2−0

 		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".
 				entry will be removed from sysfs.
 				Reading this file will list the supported
 				operations (currently just acknowledge).
+		==============  ================================================

Documentation/ABI/stable/sysfs-hypervisor-xen+3−0

 		Space separated list of supported guest system types. Each type
 		is in the format: <class>-<major>.<minor>-<arch>
 		With:
+			======== ============================================
 			<class>: "xen" -- x86: paravirtualized, arm: standard
 				 "hvm" -- x86 only: fully virtualized
 			<major>: major guest interface version
 				 "x86_64": 64 bit x86 guest
 				 "armv7l": 32 bit arm guest
 				 "aarch64": 64 bit arm guest
+			======== ============================================
 What:		/sys/hypervisor/properties/changeset
 Date:		March 2009

Documentation/ABI/stable/vdso+9−2

+What:		vDSO
+Date:		July 2011
+KernelVersion:	3.0
+Contact:	Andy Lutomirski <luto@kernel.org>
+Description:
 On some architectures, when the kernel loads any userspace program it
 maps an ELF DSO into that program's address space.  This DSO is called
 the vDSO and it often contains useful and highly-optimized alternatives
 ABI of those symbols is considered stable.  It may vary across architectures,
 though.
-(As of this writing, this ABI documentation as been confirmed for x86_64.
+Note:
+ As of this writing, this ABI documentation as been confirmed for x86_64.
  The maintainers of the other vDSO-using architectures should confirm
- that it is correct for their architecture.)
+ that it is correct for their architecture.

Documentation/ABI/testing/configfs-acpi+25−9

@@ -14,7 +14,8 @@ Description: · 13 unmodified lines
14	This group contains the configuration for user defined ACPI	14	This group contains the configuration for user defined ACPI
15	tables. The attributes of a user define table are:	15	tables. The attributes of a user define table are:
16		16
17	aml - a binary attribute that the user can use to	17	aml
		18	- a binary attribute that the user can use to
18	fill in the ACPI aml definitions. Once the aml	19	fill in the ACPI aml definitions. Once the aml
19	data is written to this file and the file is	20	data is written to this file and the file is
20	closed the table will be loaded and ACPI devices	21	closed the table will be loaded and ACPI devices
@@ -26,11 +27,26 @@ Description: · 5 unmodified lines
26	The rest of the attributes are read-only and are valid only	27	The rest of the attributes are read-only and are valid only
27	after the table has been loaded by filling the aml entry:	28	after the table has been loaded by filling the aml entry:
28		29
29	signature - ASCII table signature	30	signature
30	length - length of table in bytes, including the header	31	- ASCII table signature
31	revision - ACPI Specification minor version number	32
32	oem_id - ASCII OEM identification	33	length
33	oem_table_id - ASCII OEM table identification	34	- length of table in bytes, including the header
34	oem_revision - OEM revision number	35
35	asl_compiler_id - ASCII ASL compiler vendor ID	36	revision
36	asl_compiler_revision - ASL compiler version	37	- ACPI Specification minor version number
		38
		39	oem_id
		40	- ASCII OEM identification
		41
		42	oem_table_id
		43	- ASCII OEM table identification
		44
		45	oem_revision
		46	- OEM revision number
		47
		48	asl_compiler_id
		49	- ASCII ASL compiler vendor ID
		50
		51	asl_compiler_revision
		52	- ASL compiler version

Documentation/ABI/testing/configfs-most+90−45

 Description:
 		The attributes:
-		buffer_size	configure the buffer size for this channel
+		buffer_size
+				configure the buffer size for this channel
-		subbuffer_size	configure the sub-buffer size for this channel
+		subbuffer_size
+				configure the sub-buffer size for this channel
 				(needed for synchronous and isochrnous data)
-		num_buffers	configure number of buffers used for this
+		num_buffers
+				configure number of buffers used for this
 				channel
-		datatype	configure type of data that will travel over
+		datatype
+				configure type of data that will travel over
 				this channel
-		direction	configure whether this link will be an input
+		direction
+				configure whether this link will be an input
 				or output
-		dbr_size	configure DBR data buffer size (this is used
+		dbr_size
+				configure DBR data buffer size (this is used
 				for MediaLB communication only)
 		packets_per_xact
 				transmitted via USB (this is used for USB
 				communication only)
-		device		name of the device the link is to be attached to
+		device
+				name of the device the link is to be attached to
-		channel		name of the channel the link is to be attached to
+		channel
+				name of the channel the link is to be attached to
-		comp_params	pass parameters needed by some components
+		comp_params
+				pass parameters needed by some components
-		create_link	write '1' to this attribute to trigger the
+		create_link
+				write '1' to this attribute to trigger the
 				creation of the link. In case of speculative
 				configuration, the creation is post-poned until
 				a physical device is being attached to the bus.
-		destroy_link	write '1' to this attribute to destroy an
+		destroy_link
+				write '1' to this attribute to destroy an
 				active link
 What: 		/sys/kernel/config/most_video/<link>
 Description:
 		The attributes:
-		buffer_size	configure the buffer size for this channel
+		buffer_size
+				configure the buffer size for this channel
-		subbuffer_size	configure the sub-buffer size for this channel
+		subbuffer_size
+				configure the sub-buffer size for this channel
 				(needed for synchronous and isochrnous data)
-		num_buffers	configure number of buffers used for this
+		num_buffers
+				configure number of buffers used for this
 				channel
-		datatype	configure type of data that will travel over
+		datatype
+				configure type of data that will travel over
 				this channel
-		direction	configure whether this link will be an input
+		direction
+				configure whether this link will be an input
 				or output
-		dbr_size	configure DBR data buffer size (this is used
+		dbr_size
+				configure DBR data buffer size (this is used
 				for MediaLB communication only)
 		packets_per_xact
 				transmitted via USB (this is used for USB
 				communication only)
-		device		name of the device the link is to be attached to
+		device
+				name of the device the link is to be attached to
-		channel		name of the channel the link is to be attached to
+		channel
+				name of the channel the link is to be attached to
-		comp_params	pass parameters needed by some components
+		comp_params
+				pass parameters needed by some components
-		create_link	write '1' to this attribute to trigger the
+		create_link
+				write '1' to this attribute to trigger the
 				creation of the link. In case of speculative
 				configuration, the creation is post-poned until
 				a physical device is being attached to the bus.
-		destroy_link	write '1' to this attribute to destroy an
+		destroy_link
+				write '1' to this attribute to destroy an
 				active link
 What: 		/sys/kernel/config/most_net/<link>
 Description:
 		The attributes:
-		buffer_size	configure the buffer size for this channel
+		buffer_size
+				configure the buffer size for this channel
-		subbuffer_size	configure the sub-buffer size for this channel
+		subbuffer_size
+				configure the sub-buffer size for this channel
 				(needed for synchronous and isochrnous data)
-		num_buffers	configure number of buffers used for this
+		num_buffers
+				configure number of buffers used for this
 				channel
-		datatype	configure type of data that will travel over
+		datatype
+				configure type of data that will travel over
 				this channel
-		direction	configure whether this link will be an input
+		direction
+				configure whether this link will be an input
 				or output
-		dbr_size	configure DBR data buffer size (this is used
+		dbr_size
+				configure DBR data buffer size (this is used
 				for MediaLB communication only)
 		packets_per_xact
 				transmitted via USB (this is used for USB
 				communication only)
-		device		name of the device the link is to be attached to
+		device
+				name of the device the link is to be attached to
-		channel		name of the channel the link is to be attached to
+		channel
+				name of the channel the link is to be attached to
-		comp_params	pass parameters needed by some components
+		comp_params
+				pass parameters needed by some components
-		create_link	write '1' to this attribute to trigger the
+		create_link
+				write '1' to this attribute to trigger the
 				creation of the link. In case of speculative
 				configuration, the creation is post-poned until
 				a physical device is being attached to the bus.
-		destroy_link	write '1' to this attribute to destroy an
+		destroy_link
+				write '1' to this attribute to destroy an
 				active link
 What: 		/sys/kernel/config/most_sound/<card>
 Description:
 		The attributes:
-		create_card	write '1' to this attribute to trigger the
+		create_card
+				write '1' to this attribute to trigger the
                                 registration of the sound card with the ALSA
 				subsystem.
 Description:
 		The attributes:
-		buffer_size	configure the buffer size for this channel
+		buffer_size
+				configure the buffer size for this channel
-		subbuffer_size	configure the sub-buffer size for this channel
+		subbuffer_size
+				configure the sub-buffer size for this channel
 				(needed for synchronous and isochrnous data)
-		num_buffers	configure number of buffers used for this
+		num_buffers
+				configure number of buffers used for this
 				channel
-		datatype	configure type of data that will travel over
+		datatype
+				configure type of data that will travel over
 				this channel
-		direction	configure whether this link will be an input
+		direction
+				configure whether this link will be an input
 				or output
-		dbr_size	configure DBR data buffer size (this is used
+		dbr_size
+				configure DBR data buffer size (this is used
 				for MediaLB communication only)
 		packets_per_xact
 				transmitted via USB (this is used for USB
 				communication only)
-		device		name of the device the link is to be attached to
+		device
+				name of the device the link is to be attached to
-		channel		name of the channel the link is to be attached to
+		channel
+				name of the channel the link is to be attached to
-		comp_params	pass parameters needed by some components
+		comp_params
+				pass parameters needed by some components
-		create_link	write '1' to this attribute to trigger the
+		create_link
+				write '1' to this attribute to trigger the
 				creation of the link. In case of speculative
 				configuration, the creation is post-poned until
 				a physical device is being attached to the bus.
-		destroy_link	write '1' to this attribute to destroy an
+		destroy_link
+				write '1' to this attribute to destroy an
 				active link

Documentation/ABI/testing/configfs-spear-pcie-gadget+19−17

@@ -10,22 +10,24 @@ Description: · 9 unmodified lines
10	This interfaces can be used to show spear's PCIe device capability.	10	This interfaces can be used to show spear's PCIe device capability.
11		11
12	Nodes are only visible when configfs is mounted. To mount configfs	12	Nodes are only visible when configfs is mounted. To mount configfs
13	in /config directory use:	13	in /config directory use::
14	# mount -t configfs none /config/
15		14
16	For nth PCIe Device Controller	15	# mount -t configfs none /config/
17	/config/pcie-gadget.n/	16
18	link ... used to enable ltssm and read its status.	17	For nth PCIe Device Controller /config/pcie-gadget.n/:
19	int_type ...used to configure and read type of supported	18
20	interrupt	19	=============== ======================================================
21	no_of_msi ... used to configure number of MSI vector needed and	20	link used to enable ltssm and read its status.
		21	int_type used to configure and read type of supported interrupt
		22	no_of_msi used to configure number of MSI vector needed and
22	to read no of MSI granted.	23	to read no of MSI granted.
23	inta ... write 1 to assert INTA and 0 to de-assert.	24	inta write 1 to assert INTA and 0 to de-assert.
24	send_msi ... write MSI vector to be sent.	25	send_msi write MSI vector to be sent.
25	vendor_id ... used to write and read vendor id (hex)	26	vendor_id used to write and read vendor id (hex)
26	device_id ... used to write and read device id (hex)	27	device_id used to write and read device id (hex)
27	bar0_size ... used to write and read bar0_size	28	bar0_size used to write and read bar0_size
28	bar0_address ... used to write and read bar0 mapped area in hex.	29	bar0_address used to write and read bar0 mapped area in hex.
29	bar0_rw_offset ... used to write and read offset of bar0 where	30	bar0_rw_offset used to write and read offset of bar0 where bar0_data
30	bar0_data will be written or read.	31	will be written or read.
31	bar0_data ... used to write and read data at bar0_rw_offset.	32	bar0_data used to write and read data at bar0_rw_offset.
		33	=============== ======================================================

Documentation/ABI/testing/configfs-usb-gadget+51−36

@@ -12,22 +12,24 @@ Description: · 11 unmodified lines
12		12
13	The attributes of a gadget:	13	The attributes of a gadget:
14		14
15	UDC - bind a gadget to UDC/unbind a gadget;	15	================ ============================================
16	write UDC's name found in /sys/class/udc/*	16	UDC bind a gadget to UDC/unbind a gadget;
17	to bind a gadget, empty string "" to unbind.	17	write UDC's name found in /sys/class/udc/*
18		18	to bind a gadget, empty string "" to unbind.
19	max_speed - maximum speed the driver supports. Valid	19
20	names are super-speed-plus, super-speed,	20	max_speed maximum speed the driver supports. Valid
21	high-speed, full-speed, and low-speed.	21	names are super-speed-plus, super-speed,
22		22	high-speed, full-speed, and low-speed.
23	bDeviceClass - USB device class code	23
24	bDeviceSubClass - USB device subclass code	24	bDeviceClass USB device class code
25	bDeviceProtocol - USB device protocol code	25	bDeviceSubClass USB device subclass code
26	bMaxPacketSize0 - maximum endpoint 0 packet size	26	bDeviceProtocol USB device protocol code
27	bcdDevice - bcd device release number	27	bMaxPacketSize0 maximum endpoint 0 packet size
28	bcdUSB - bcd USB specification version number	28	bcdDevice bcd device release number
29	idProduct - product ID	29	bcdUSB bcd USB specification version number
30	idVendor - vendor ID	30	idProduct product ID
		31	idVendor vendor ID
		32	================ ============================================
31		33
32	What: /config/usb-gadget/gadget/configs	34	What: /config/usb-gadget/gadget/configs
33	Date: Jun 2013	35	Date: Jun 2013
@@ -41,8 +43,10 @@ KernelVersion: 3.11 · 7 unmodified lines
41	Description:	43	Description:
42	The attributes of a configuration:	44	The attributes of a configuration:
43		45
44	bmAttributes - configuration characteristics	46	================ ======================================
45	MaxPower - maximum power consumption from the bus	47	bmAttributes configuration characteristics
		48	MaxPower maximum power consumption from the bus
		49	================ ======================================
46		50
47	What: /config/usb-gadget/gadget/configs/config/strings	51	What: /config/usb-gadget/gadget/configs/config/strings
48	Date: Jun 2013	52	Date: Jun 2013
@@ -57,7 +61,9 @@ KernelVersion: 3.11 · 8 unmodified lines
57	Description:	61	Description:
58	The attributes:	62	The attributes:
59		63
60	configuration - configuration description	64	================ =========================
		65	configuration configuration description
		66	================ =========================
61		67
62		68
63	What: /config/usb-gadget/gadget/functions	69	What: /config/usb-gadget/gadget/functions
@@ -76,8 +82,10 @@ Description: · 12 unmodified lines
76		82
77	The attributes:	83	The attributes:
78		84
79	compatible_id - 8-byte string for "Compatible ID"	85	================= =====================================
80	sub_compatible_id - 8-byte string for "Sub Compatible ID"	86	compatible_id 8-byte string for "Compatible ID"
		87	sub_compatible_id 8-byte string for "Sub Compatible ID"
		88	================= =====================================
81		89
82	What: /config/usb-gadget/gadget/functions/<func>.<inst>/interface.<n>/<property>	90	What: /config/usb-gadget/gadget/functions/<func>.<inst>/interface.<n>/<property>
83	Date: May 2014	91	Date: May 2014
@@ -89,16 +97,19 @@ Description: · 5 unmodified lines
89		97
90	The attributes:	98	The attributes:
91		99
92	type - value 1..7 for interpreting the data	100	===== ===============================================
93	1: unicode string	101	type value 1..7 for interpreting the data
94	2: unicode string with environment variable	102
95	3: binary	103	- 1: unicode string
96	4: little-endian 32-bit	104	- 2: unicode string with environment variable
97	5: big-endian 32-bit	105	- 3: binary
98	6: unicode string with a symbolic link	106	- 4: little-endian 32-bit
99	7: multiple unicode strings	107	- 5: big-endian 32-bit
100	data - blob of data to be interpreted depending on	108	- 6: unicode string with a symbolic link
		109	- 7: multiple unicode strings
		110	data blob of data to be interpreted depending on
101	type	111	type
		112	===== ===============================================
102		113
103	What: /config/usb-gadget/gadget/strings	114	What: /config/usb-gadget/gadget/strings
104	Date: Jun 2013	115	Date: Jun 2013
@@ -113,9 +124,11 @@ KernelVersion: 3.11 · 8 unmodified lines
113	Description:	124	Description:
114	The attributes:	125	The attributes:
115		126
116	serialnumber - gadget's serial number (string)	127	============ =================================
117	product - gadget's product description	128	serialnumber gadget's serial number (string)
118	manufacturer - gadget's manufacturer description	129	product gadget's product description
		130	manufacturer gadget's manufacturer description
		131	============ =================================
119		132
120	What: /config/usb-gadget/gadget/os_desc	133	What: /config/usb-gadget/gadget/os_desc
121	Date: May 2014	134	Date: May 2014
@@ -123,8 +136,10 @@ KernelVersion: 3.16 · 1 unmodified line
123	Description:	136	Description:
124	This group contains "OS String" extension handling attributes.	137	This group contains "OS String" extension handling attributes.
125		138
126	use - flag turning "OS Desctiptors" support on/off	139	============= ===============================================
127	b_vendor_code - one-byte value used for custom per-device and	140	use flag turning "OS Desctiptors" support on/off
		141	b_vendor_code one-byte value used for custom per-device and
128	per-interface requests	142	per-interface requests
129	qw_sign - an identifier to be reported as "OS String"	143	qw_sign an identifier to be reported as "OS String"
130	proper	144	proper
		145	============= ===============================================

Documentation/ABI/testing/configfs-usb-gadget-ecm+8−4

 Description:
 		The attributes:
-		ifname		- network device interface name associated with
+		ifname
+			      - network device interface name associated with
 				this function instance
-		qmult		- queue length multiplier for high and
+		qmult
+			      - queue length multiplier for high and
 				super speed
-		host_addr	- MAC address of host's end of this
+		host_addr
+			      - MAC address of host's end of this
 				Ethernet over USB link
-		dev_addr	- MAC address of device's end of this
+		dev_addr
+			      - MAC address of device's end of this
 				Ethernet over USB link

Documentation/ABI/testing/configfs-usb-gadget-eem+6−4

 Description:
 		The attributes:
-		ifname		- network device interface name associated with
+		==========	=============================================
+		ifname		network device interface name associated with
 				this function instance
-		qmult		- queue length multiplier for high and
+		qmult		queue length multiplier for high and
 				super speed
-		host_addr	- MAC address of host's end of this
+		host_addr	MAC address of host's end of this
 				Ethernet over USB link
-		dev_addr	- MAC address of device's end of this
+		dev_addr	MAC address of device's end of this
 				Ethernet over USB link
+		==========	=============================================

Documentation/ABI/testing/configfs-usb-gadget-hid+6−4

@@ -4,8 +4,10 @@ KernelVersion: 3.19 · 3 unmodified lines
4	Description:	4	Description:
5	The attributes:	5	The attributes:
6		6
7	protocol - HID protocol to use	7	============= ============================================
8	report_desc - blob corresponding to HID report descriptors	8	protocol HID protocol to use
		9	report_desc blob corresponding to HID report descriptors
9	except the data passed through /dev/hidg<N>	10	except the data passed through /dev/hidg<N>
10	report_length - HID report length	11	report_length HID report length
11	subclass - HID device subclass to use	12	subclass HID device subclass to use
		13	============= ============================================

Documentation/ABI/testing/configfs-usb-gadget-loopback+4−2

@@ -4,5 +4,7 @@ KernelVersion: 3.13 · 3 unmodified lines
4	Description:	4	Description:
5	The attributes:	5	The attributes:
6		6
7	qlen - depth of loopback queue	7	======= =======================
8	buflen - buffer length	8	qlen depth of loopback queue
		9	buflen buffer length
		10	======= =======================

Documentation/ABI/testing/configfs-usb-gadget-mass-storage+11−7

 Description:
 		The attributes:
-		stall		- Set to permit function to halt bulk endpoints.
+		===========	==============================================
+		stall		Set to permit function to halt bulk endpoints.
 				Disabled on some USB devices known not to work
 				correctly. You should set it to true.
-		num_buffers	- Number of pipeline buffers. Valid numbers
+		num_buffers	Number of pipeline buffers. Valid numbers
 				are 2..4. Available only if
 				CONFIG_USB_GADGET_DEBUG_FILES is set.
+		===========	==============================================
 What:		/config/usb-gadget/gadget/functions/mass_storage.name/lun.name
 Date:		Oct 2013
 Description:
 		The attributes:
-		file		- The path to the backing file for the LUN.
+		===========	==============================================
+		file		The path to the backing file for the LUN.
 				Required if LUN is not marked as removable.
-		ro		- Flag specifying access to the LUN shall be
+		ro		Flag specifying access to the LUN shall be
 				read-only. This is implied if CD-ROM emulation
 				is enabled as well as when it was impossible
 				to open "filename" in R/W mode.
-		removable	- Flag specifying that LUN shall be indicated as
+		removable	Flag specifying that LUN shall be indicated as
 				being removable.
-		cdrom		- Flag specifying that LUN shall be reported as
+		cdrom		Flag specifying that LUN shall be reported as
 				being a CD-ROM.
-		nofua		- Flag specifying that FUA flag
+		nofua		Flag specifying that FUA flag
 				in SCSI WRITE(10,12)
+		===========	==============================================

Documentation/ABI/testing/configfs-usb-gadget-midi+8−6

@@ -4,9 +4,11 @@ KernelVersion: 3.19 · 3 unmodified lines
4	Description:	4	Description:
5	The attributes:	5	The attributes:
6		6
7	index - index value for the USB MIDI adapter	7	========== ====================================
8	id - ID string for the USB MIDI adapter	8	index index value for the USB MIDI adapter
9	buflen - MIDI buffer length	9	id ID string for the USB MIDI adapter
10	qlen - USB read request queue length	10	buflen MIDI buffer length
11	in_ports - number of MIDI input ports	11	qlen USB read request queue length
12	out_ports - number of MIDI output ports	12	in_ports number of MIDI input ports
		13	out_ports number of MIDI output ports
		14	========== ====================================

Documentation/ABI/testing/configfs-usb-gadget-printer+4−2

@@ -4,6 +4,8 @@ KernelVersion: 4.1 · 3 unmodified lines
4	Description:	4	Description:
5	The attributes:	5	The attributes:
6		6
7	pnp_string - Data to be passed to the host in pnp string	7	========== ===========================================
8	q_len - Number of requests per endpoint	8	pnp_string Data to be passed to the host in pnp string
		9	q_len Number of requests per endpoint
		10	========== ===========================================
9		11

Documentation/ABI/testing/configfs-usb-gadget-rndis+9−7

@@ -4,14 +4,16 @@ KernelVersion: 3.11 · 3 unmodified lines
4	Description:	4	Description:
5	The attributes:	5	The attributes:
6		6
7	ifname - network device interface name associated with	7	========= =============================================
		8	ifname network device interface name associated with
8	this function instance	9	this function instance
9	qmult - queue length multiplier for high and	10	qmult queue length multiplier for high and
10	super speed	11	super speed
11	host_addr - MAC address of host's end of this	12	host_addr MAC address of host's end of this
12	Ethernet over USB link	13	Ethernet over USB link
13	dev_addr - MAC address of device's end of this	14	dev_addr MAC address of device's end of this
14	Ethernet over USB link	15	Ethernet over USB link
15	class - USB interface class, default is 02 (hex)	16	class USB interface class, default is 02 (hex)
16	subclass - USB interface subclass, default is 06 (hex)	17	subclass USB interface subclass, default is 06 (hex)
17	protocol - USB interface protocol, default is 00 (hex)	18	protocol USB interface protocol, default is 00 (hex)
		19	========= =============================================

Documentation/ABI/testing/configfs-usb-gadget-sourcesink+10−8

@@ -4,11 +4,13 @@ KernelVersion: 3.13 · 3 unmodified lines
4	Description:	4	Description:
5	The attributes:	5	The attributes:
6		6
7	pattern - 0 (all zeros), 1 (mod63), 2 (none)	7	============== ==================================
8	isoc_interval - 1..16	8	pattern 0 (all zeros), 1 (mod63), 2 (none)
9	isoc_maxpacket - 0 - 1023 (fs), 0 - 1024 (hs/ss)	9	isoc_interval 1..16
10	isoc_mult - 0..2 (hs/ss only)	10	isoc_maxpacket 0 - 1023 (fs), 0 - 1024 (hs/ss)
11	isoc_maxburst - 0..15 (ss only)	11	isoc_mult 0..2 (hs/ss only)
12	buflen - buffer length	12	isoc_maxburst 0..15 (ss only)
13	bulk_qlen - depth of queue for bulk	13	buflen buffer length
14	iso_qlen - depth of queue for iso	14	bulk_qlen depth of queue for bulk
		15	iso_qlen depth of queue for iso
		16	============== ==================================

Documentation/ABI/testing/configfs-usb-gadget-subset+6−4

 Description:
 		The attributes:
-		ifname		- network device interface name associated with
+		==========	=============================================
+		ifname		network device interface name associated with
 				this function instance
-		qmult		- queue length multiplier for high and
+		qmult		queue length multiplier for high and
 				super speed
-		host_addr	- MAC address of host's end of this
+		host_addr	MAC address of host's end of this
 				Ethernet over USB link
-		dev_addr	- MAC address of device's end of this
+		dev_addr	MAC address of device's end of this
 				Ethernet over USB link
+		==========	=============================================

Documentation/ABI/testing/configfs-usb-gadget-uac1+10−8

@@ -4,11 +4,13 @@ KernelVersion: 4.14 · 3 unmodified lines
4	Description:	4	Description:
5	The attributes:	5	The attributes:
6		6
7	c_chmask - capture channel mask	7	========== ===================================
8	c_srate - capture sampling rate	8	c_chmask capture channel mask
9	c_ssize - capture sample size (bytes)	9	c_srate capture sampling rate
10	p_chmask - playback channel mask	10	c_ssize capture sample size (bytes)
11	p_srate - playback sampling rate	11	p_chmask playback channel mask
12	p_ssize - playback sample size (bytes)	12	p_srate playback sampling rate
13	req_number - the number of pre-allocated request	13	p_ssize playback sample size (bytes)
14	for both capture and playback	14	req_number the number of pre-allocated request
		15	for both capture and playback
		16	========== ===================================

Documentation/ABI/testing/configfs-usb-gadget-uac2+8−6

@@ -4,9 +4,11 @@ KernelVersion: 3.18 · 3 unmodified lines
4	Description:	4	Description:
5	The attributes:	5	The attributes:
6		6
7	c_chmask - capture channel mask	7	========= ============================
8	c_srate - capture sampling rate	8	c_chmask capture channel mask
9	c_ssize - capture sample size (bytes)	9	c_srate capture sampling rate
10	p_chmask - playback channel mask	10	c_ssize capture sample size (bytes)
11	p_srate - playback sampling rate	11	p_chmask playback channel mask
12	p_ssize - playback sample size (bytes)	12	p_srate playback sampling rate
		13	p_ssize playback sample size (bytes)
		14	========= ============================

Documentation/ABI/testing/configfs-usb-gadget-uvc+126−94

@@ -3,9 +3,11 @@ Date: Dec 2014 · 2 unmodified lines
3	KernelVersion: 4.0	3	KernelVersion: 4.0
4	Description: UVC function directory	4	Description: UVC function directory
5		5
6	streaming_maxburst - 0..15 (ss only)	6	=================== =============================
7	streaming_maxpacket - 1..1023 (fs), 1..3072 (hs/ss)	7	streaming_maxburst 0..15 (ss only)
8	streaming_interval - 1..16	8	streaming_maxpacket 1..1023 (fs), 1..3072 (hs/ss)
		9	streaming_interval 1..16
		10	=================== =============================
9		11
10	What: /config/usb-gadget/gadget/functions/uvc.name/control	12	What: /config/usb-gadget/gadget/functions/uvc.name/control
11	Date: Dec 2014	13	Date: Dec 2014
@@ -13,8 +15,11 @@ KernelVersion: 4.0 · 1 unmodified line
13	Description: Control descriptors	15	Description: Control descriptors
14		16
15	All attributes read only:	17	All attributes read only:
16	bInterfaceNumber - USB interface number for this	18
17	streaming interface	19	================ =============================
		20	bInterfaceNumber USB interface number for this
		21	streaming interface
		22	================ =============================
18		23
19	What: /config/usb-gadget/gadget/functions/uvc.name/control/class	24	What: /config/usb-gadget/gadget/functions/uvc.name/control/class
20	Date: Dec 2014	25	Date: Dec 2014
@@ -47,13 +52,16 @@ KernelVersion: 4.0 · 26 unmodified lines
47	Description: Default output terminal descriptors	52	Description: Default output terminal descriptors
48		53
49	All attributes read only:	54	All attributes read only:
50	iTerminal - index of string descriptor	55
51	bSourceID - id of the terminal to which this terminal	56	============== =============================================
		57	iTerminal index of string descriptor
		58	bSourceID id of the terminal to which this terminal
52	is connected	59	is connected
53	bAssocTerminal - id of the input terminal to which this output	60	bAssocTerminal id of the input terminal to which this output
54	terminal is associated	61	terminal is associated
55	wTerminalType - terminal type	62	wTerminalType terminal type
56	bTerminalID - a non-zero id of this terminal	63	bTerminalID a non-zero id of this terminal
		64	============== =============================================
57		65
58	What: /config/usb-gadget/gadget/functions/uvc.name/control/terminal/camera	66	What: /config/usb-gadget/gadget/functions/uvc.name/control/terminal/camera
59	Date: Dec 2014	67	Date: Dec 2014
@@ -66,16 +74,19 @@ KernelVersion: 4.0 · 6 unmodified lines
66	Description: Default camera terminal descriptors	74	Description: Default camera terminal descriptors
67		75
68	All attributes read only:	76	All attributes read only:
69	bmControls - bitmap specifying which controls are	77
70	supported for the video stream	78	======================== ====================================
71	wOcularFocalLength - the value of Locular	79	bmControls bitmap specifying which controls are
72	wObjectiveFocalLengthMax- the value of Lmin	80	supported for the video stream
73	wObjectiveFocalLengthMin- the value of Lmax	81	wOcularFocalLength the value of Locular
74	iTerminal - index of string descriptor	82	wObjectiveFocalLengthMax the value of Lmin
75	bAssocTerminal - id of the output terminal to which	83	wObjectiveFocalLengthMin the value of Lmax
76	this terminal is connected	84	iTerminal index of string descriptor
77	wTerminalType - terminal type	85	bAssocTerminal id of the output terminal to which
78	bTerminalID - a non-zero id of this terminal	86	this terminal is connected
		87	wTerminalType terminal type
		88	bTerminalID a non-zero id of this terminal
		89	======================== ====================================
79		90
80	What: /config/usb-gadget/gadget/functions/uvc.name/control/processing	91	What: /config/usb-gadget/gadget/functions/uvc.name/control/processing
81	Date: Dec 2014	92	Date: Dec 2014
@@ -88,13 +99,16 @@ KernelVersion: 4.0 · 6 unmodified lines
88	Description: Default processing unit descriptors	99	Description: Default processing unit descriptors
89		100
90	All attributes read only:	101	All attributes read only:
91	iProcessing - index of string descriptor	102
92	bmControls - bitmap specifying which controls are	103	=============== ========================================
		104	iProcessing index of string descriptor
		105	bmControls bitmap specifying which controls are
93	supported for the video stream	106	supported for the video stream
94	wMaxMultiplier - maximum digital magnification x100	107	wMaxMultiplier maximum digital magnification x100
95	bSourceID - id of the terminal to which this unit is	108	bSourceID id of the terminal to which this unit is
96	connected	109	connected
97	bUnitID - a non-zero id of this unit	110	bUnitID a non-zero id of this unit
		111	=============== ========================================
98		112
99	What: /config/usb-gadget/gadget/functions/uvc.name/control/header	113	What: /config/usb-gadget/gadget/functions/uvc.name/control/header
100	Date: Dec 2014	114	Date: Dec 2014
@@ -114,8 +128,11 @@ KernelVersion: 4.0 · 13 unmodified lines
114	Description: Streaming descriptors	128	Description: Streaming descriptors
115		129
116	All attributes read only:	130	All attributes read only:
117	bInterfaceNumber - USB interface number for this	131
118	streaming interface	132	================ =============================
		133	bInterfaceNumber USB interface number for this
		134	streaming interface
		135	================ =============================
119		136
120	What: /config/usb-gadget/gadget/functions/uvc.name/streaming/class	137	What: /config/usb-gadget/gadget/functions/uvc.name/streaming/class
121	Date: Dec 2014	138	Date: Dec 2014
@@ -148,13 +165,16 @@ KernelVersion: 4.0 · 26 unmodified lines
148	Description: Default color matching descriptors	165	Description: Default color matching descriptors
149		166
150	All attributes read only:	167	All attributes read only:
151	bMatrixCoefficients - matrix used to compute luma and	168
152	chroma values from the color primaries	169	======================== ======================================
153	bTransferCharacteristics- optoelectronic transfer	170	bMatrixCoefficients matrix used to compute luma and
154	characteristic of the source picutre,	171	chroma values from the color primaries
155	also called the gamma function	172	bTransferCharacteristics optoelectronic transfer
156	bColorPrimaries - color primaries and the reference	173	characteristic of the source picutre,
157	white	174	also called the gamma function
		175	bColorPrimaries color primaries and the reference
		176	white
		177	======================== ======================================
158		178
159	What: /config/usb-gadget/gadget/functions/uvc.name/streaming/mjpeg	179	What: /config/usb-gadget/gadget/functions/uvc.name/streaming/mjpeg
160	Date: Dec 2014	180	Date: Dec 2014
@@ -168,47 +188,52 @@ Description: Specific MJPEG format descriptors · 7 unmodified lines
168		188
169	All attributes read only,	189	All attributes read only,
170	except bmaControls and bDefaultFrameIndex:	190	except bmaControls and bDefaultFrameIndex:
171	bFormatIndex - unique id for this format descriptor;	191
		192	=================== =====================================
		193	bFormatIndex unique id for this format descriptor;
172	only defined after parent header is	194	only defined after parent header is
173	linked into the streaming class;	195	linked into the streaming class;
174	read-only	196	read-only
175	bmaControls - this format's data for bmaControls in	197	bmaControls this format's data for bmaControls in
176	the streaming header	198	the streaming header
177	bmInterfaceFlags - specifies interlace information,	199	bmInterfaceFlags specifies interlace information,
178	read-only	200	read-only
179	bAspectRatioY - the X dimension of the picture aspect	201	bAspectRatioY the X dimension of the picture aspect
180	ratio, read-only	202	ratio, read-only
181	bAspectRatioX - the Y dimension of the picture aspect	203	bAspectRatioX the Y dimension of the picture aspect
182	ratio, read-only	204	ratio, read-only
183	bmFlags - characteristics of this format,	205	bmFlags characteristics of this format,
184	read-only	206	read-only
185	bDefaultFrameIndex - optimum frame index for this stream	207	bDefaultFrameIndex optimum frame index for this stream
		208	=================== =====================================
186		209
187	What: /config/usb-gadget/gadget/functions/uvc.name/streaming/mjpeg/name/name	210	What: /config/usb-gadget/gadget/functions/uvc.name/streaming/mjpeg/name/name
188	Date: Dec 2014	211	Date: Dec 2014
189	KernelVersion: 4.0	212	KernelVersion: 4.0
190	Description: Specific MJPEG frame descriptors	213	Description: Specific MJPEG frame descriptors
191		214
192	bFrameIndex - unique id for this framedescriptor;	215	========================= =====================================
193	only defined after parent format is	216	bFrameIndex unique id for this framedescriptor;
194	linked into the streaming header;	217	only defined after parent format is
195	read-only	218	linked into the streaming header;
196	dwFrameInterval - indicates how frame interval can be	219	read-only
197	programmed; a number of values	220	dwFrameInterval indicates how frame interval can be
198	separated by newline can be specified	221	programmed; a number of values
199	dwDefaultFrameInterval - the frame interval the device would	222	separated by newline can be specified
200	like to use as default	223	dwDefaultFrameInterval the frame interval the device would
201	dwMaxVideoFrameBufferSize- the maximum number of bytes the	224	like to use as default
202	compressor will produce for a video	225	dwMaxVideoFrameBufferSize the maximum number of bytes the
203	frame or still image	226	compressor will produce for a video
204	dwMaxBitRate - the maximum bit rate at the shortest	227	frame or still image
205	frame interval in bps	228	dwMaxBitRate the maximum bit rate at the shortest
206	dwMinBitRate - the minimum bit rate at the longest	229	frame interval in bps
207	frame interval in bps	230	dwMinBitRate the minimum bit rate at the longest
208	wHeight - height of decoded bitmap frame in px	231	frame interval in bps
209	wWidth - width of decoded bitmam frame in px	232	wHeight height of decoded bitmap frame in px
210	bmCapabilities - still image support, fixed frame-rate	233	wWidth width of decoded bitmam frame in px
211	support	234	bmCapabilities still image support, fixed frame-rate
		235	support
		236	========================= =====================================
212		237
213	What: /config/usb-gadget/gadget/functions/uvc.name/streaming/uncompressed	238	What: /config/usb-gadget/gadget/functions/uvc.name/streaming/uncompressed
214	Date: Dec 2014	239	Date: Dec 2014
@@ -220,50 +245,54 @@ Date: Dec 2014 · 5 unmodified lines
220	KernelVersion: 4.0	245	KernelVersion: 4.0
221	Description: Specific uncompressed format descriptors	246	Description: Specific uncompressed format descriptors
222		247
223	bFormatIndex - unique id for this format descriptor;	248	================== =======================================
		249	bFormatIndex unique id for this format descriptor;
224	only defined after parent header is	250	only defined after parent header is
225	linked into the streaming class;	251	linked into the streaming class;
226	read-only	252	read-only
227	bmaControls - this format's data for bmaControls in	253	bmaControls this format's data for bmaControls in
228	the streaming header	254	the streaming header
229	bmInterfaceFlags - specifies interlace information,	255	bmInterfaceFlags specifies interlace information,
230	read-only	256	read-only
231	bAspectRatioY - the X dimension of the picture aspect	257	bAspectRatioY the X dimension of the picture aspect
232	ratio, read-only	258	ratio, read-only
233	bAspectRatioX - the Y dimension of the picture aspect	259	bAspectRatioX the Y dimension of the picture aspect
234	ratio, read-only	260	ratio, read-only
235	bDefaultFrameIndex - optimum frame index for this stream	261	bDefaultFrameIndex optimum frame index for this stream
236	bBitsPerPixel - number of bits per pixel used to	262	bBitsPerPixel number of bits per pixel used to
237	specify color in the decoded video	263	specify color in the decoded video
238	frame	264	frame
239	guidFormat - globally unique id used to identify	265	guidFormat globally unique id used to identify
240	stream-encoding format	266	stream-encoding format
		267	================== =======================================
241		268
242	What: /config/usb-gadget/gadget/functions/uvc.name/streaming/uncompressed/name/name	269	What: /config/usb-gadget/gadget/functions/uvc.name/streaming/uncompressed/name/name
243	Date: Dec 2014	270	Date: Dec 2014
244	KernelVersion: 4.0	271	KernelVersion: 4.0
245	Description: Specific uncompressed frame descriptors	272	Description: Specific uncompressed frame descriptors
246		273
247	bFrameIndex - unique id for this framedescriptor;	274	========================= =====================================
248	only defined after parent format is	275	bFrameIndex unique id for this framedescriptor;
249	linked into the streaming header;	276	only defined after parent format is
250	read-only	277	linked into the streaming header;
251	dwFrameInterval - indicates how frame interval can be	278	read-only
252	programmed; a number of values	279	dwFrameInterval indicates how frame interval can be
253	separated by newline can be specified	280	programmed; a number of values
254	dwDefaultFrameInterval - the frame interval the device would	281	separated by newline can be specified
255	like to use as default	282	dwDefaultFrameInterval the frame interval the device would
256	dwMaxVideoFrameBufferSize- the maximum number of bytes the	283	like to use as default
257	compressor will produce for a video	284	dwMaxVideoFrameBufferSize the maximum number of bytes the
258	frame or still image	285	compressor will produce for a video
259	dwMaxBitRate - the maximum bit rate at the shortest	286	frame or still image
260	frame interval in bps	287	dwMaxBitRate the maximum bit rate at the shortest
261	dwMinBitRate - the minimum bit rate at the longest	288	frame interval in bps
262	frame interval in bps	289	dwMinBitRate the minimum bit rate at the longest
263	wHeight - height of decoded bitmap frame in px	290	frame interval in bps
264	wWidth - width of decoded bitmam frame in px	291	wHeight height of decoded bitmap frame in px
265	bmCapabilities - still image support, fixed frame-rate	292	wWidth width of decoded bitmam frame in px
266	support	293	bmCapabilities still image support, fixed frame-rate
		294	support
		295	========================= =====================================
267		296
268	What: /config/usb-gadget/gadget/functions/uvc.name/streaming/header	297	What: /config/usb-gadget/gadget/functions/uvc.name/streaming/header
269	Date: Dec 2014	298	Date: Dec 2014
@@ -276,17 +305,20 @@ KernelVersion: 4.0 · 6 unmodified lines
276	Description: Specific streaming header descriptors	305	Description: Specific streaming header descriptors
277		306
278	All attributes read only:	307	All attributes read only:
279	bTriggerUsage - how the host software will respond to	308
		309	==================== =====================================
		310	bTriggerUsage how the host software will respond to
280	a hardware trigger interrupt event	311	a hardware trigger interrupt event
281	bTriggerSupport - flag specifying if hardware	312	bTriggerSupport flag specifying if hardware
282	triggering is supported	313	triggering is supported
283	bStillCaptureMethod - method of still image caputre	314	bStillCaptureMethod method of still image caputre
284	supported	315	supported
285	bTerminalLink - id of the output terminal to which	316	bTerminalLink id of the output terminal to which
286	the video endpoint of this interface	317	the video endpoint of this interface
287	is connected	318	is connected
288	bmInfo - capabilities of this video streaming	319	bmInfo capabilities of this video streaming
289	interface	320	interface
		321	==================== =====================================
290		322
291	What: /sys/class/udc/udc.name/device/gadget/video4linux/video.name/function_name	323	What: /sys/class/udc/udc.name/device/gadget/video4linux/video.name/function_name
292	Date: May 2018	324	Date: May 2018

Documentation/ABI/testing/debugfs-cec-error-inj+1−1

@@ -23,7 +23,7 @@ error injections without having to know the details of the driver-specific · 22 unmodified lines
23	commands.	23	commands.
24		24
25	Note that the output of 'error-inj' shall be valid as input to 'error-inj'.	25	Note that the output of 'error-inj' shall be valid as input to 'error-inj'.
26	So this must work:	26	So this must work::
27		27
28	$ cat error-inj >einj.txt	28	$ cat error-inj >einj.txt
29	$ cat einj.txt >error-inj	29	$ cat einj.txt >error-inj

Documentation/ABI/testing/debugfs-driver-habanalabs+9−3

Documentation/ABI/testing/debugfs-ec+6−5

@@ -6,7 +6,7 @@ Description: · 5 unmodified lines
6	General information like which GPE is assigned to the EC and whether	6	General information like which GPE is assigned to the EC and whether
7	the global lock should get used.	7	the global lock should get used.
8	Knowing the EC GPE one can watch the amount of HW events related to	8	Knowing the EC GPE one can watch the amount of HW events related to
9	the EC here (XY -> GPE number from /sys/kernel/debug/ec/*/gpe):	9	the EC here (XY -> GPE number from `/sys/kernel/debug/ec/*/gpe`):
10	/sys/firmware/acpi/interrupts/gpeXY	10	/sys/firmware/acpi/interrupts/gpeXY
11		11
12	The io file is binary and a userspace tool located here:	12	The io file is binary and a userspace tool located here:
@@ -14,7 +14,8 @@ ftp://ftp.suse.com/pub/people/trenn/sources/ec/ · 1 unmodified line
14	should get used to read out the 256 Embedded Controller registers	14	should get used to read out the 256 Embedded Controller registers
15	or writing to them.	15	or writing to them.
16		16
17	CAUTION: Do not write to the Embedded Controller if you don't know	17	CAUTION:
18	what you are doing! Rebooting afterwards also is a good idea.	18	Do not write to the Embedded Controller if you don't know
19	This can influence the way your machine is cooled and fans may	19	what you are doing! Rebooting afterwards also is a good idea.
20	not get switched on again after you did a wrong write.	20	This can influence the way your machine is cooled and fans may
		21	not get switched on again after you did a wrong write.

Documentation/ABI/testing/debugfs-moxtet+21−9

@@ -2,13 +2,19 @@ What: /sys/kernel/debug/moxtet/input · 1 unmodified line
2	Date: March 2019	2	Date: March 2019
3	KernelVersion: 5.3	3	KernelVersion: 5.3
4	Contact: Marek Behún <marek.behun@nic.cz>	4	Contact: Marek Behún <marek.behun@nic.cz>
5	Description: (R) Read input from the shift registers, in hexadecimal.	5	Description: (Read) Read input from the shift registers, in hexadecimal.
6	Returns N+1 bytes, where N is the number of Moxtet connected	6	Returns N+1 bytes, where N is the number of Moxtet connected
7	modules. The first byte is from the CPU board itself.	7	modules. The first byte is from the CPU board itself.
8	Example: 101214	8
9	10: CPU board with SD card	9	Example::
10	12: 2 = PCIe module, 1 = IRQ not active	10
11	14: 4 = Peridot module, 1 = IRQ not active	11	101214
		12
		13	== =======================================
		14	10 CPU board with SD card
		15	12 2 = PCIe module, 1 = IRQ not active
		16	14 4 = Peridot module, 1 = IRQ not active
		17	== =======================================
12		18
13	What: /sys/kernel/debug/moxtet/output	19	What: /sys/kernel/debug/moxtet/output
14	Date: March 2019	20	Date: March 2019
@@ -17,7 +23,13 @@ Contact: Marek Behún <marek.behun@nic.cz> · 2 unmodified lines
17	Description: (RW) Read last written value to the shift registers, in	23	Description: (RW) Read last written value to the shift registers, in
18	hexadecimal, or write values to the shift registers, also	24	hexadecimal, or write values to the shift registers, also
19	in hexadecimal.	25	in hexadecimal.
20	Example: 0102	26
21	01: 01 was last written, or is to be written, to the	27	Example::
22	first module's shift register	28
23	02: the same for second module	29	0102
		30
		31	== ================================================
		32	01 01 was last written, or is to be written, to the
		33	first module's shift register
		34	02 the same for second module
		35	== ================================================

Documentation/ABI/testing/debugfs-pfo-nx-crypto+14−14

@@ -4,42 +4,42 @@ KernelVersion: 3.4 · 3 unmodified lines
4	Contact: Kent Yoder <key@linux.vnet.ibm.com>	4	Contact: Kent Yoder <key@linux.vnet.ibm.com>
5	Description:	5	Description:
6		6
7	These debugfs interfaces are built by the nx-crypto driver, built in	7	These debugfs interfaces are built by the nx-crypto driver, built in
8	arch/powerpc/crypto/nx.	8	arch/powerpc/crypto/nx.
9		9
10	Error Detection	10	Error Detection
11	===============	11	===============
12		12
13	errors:	13	errors:
14	- A u32 providing a total count of errors since the driver was loaded. The	14	A u32 providing a total count of errors since the driver was loaded. The
15	only errors counted here are those returned from the hcall, H_COP_OP.	15	only errors counted here are those returned from the hcall, H_COP_OP.
16		16
17	last_error:	17	last_error:
18	- The most recent non-zero return code from the H_COP_OP hcall. -EBUSY is not	18	The most recent non-zero return code from the H_COP_OP hcall. -EBUSY is not
19	recorded here (the hcall will retry until -EBUSY goes away).	19	recorded here (the hcall will retry until -EBUSY goes away).
20		20
21	last_error_pid:	21	last_error_pid:
22	- The process ID of the process who received the most recent error from the	22	The process ID of the process who received the most recent error from the
23	hcall.	23	hcall.
24		24
25	Device Use	25	Device Use
26	==========	26	==========
27		27
28	aes_bytes:	28	aes_bytes:
29	- The total number of bytes encrypted using AES in any of the driver's	29	The total number of bytes encrypted using AES in any of the driver's
30	supported modes.	30	supported modes.
31		31
32	aes_ops:	32	aes_ops:
33	- The total number of AES operations submitted to the hardware.	33	The total number of AES operations submitted to the hardware.
34		34
35	sha256_bytes:	35	sha256_bytes:
36	- The total number of bytes hashed by the hardware using SHA-256.	36	The total number of bytes hashed by the hardware using SHA-256.
37		37
38	sha256_ops:	38	sha256_ops:
39	- The total number of SHA-256 operations submitted to the hardware.	39	The total number of SHA-256 operations submitted to the hardware.
40		40
41	sha512_bytes:	41	sha512_bytes:
42	- The total number of bytes hashed by the hardware using SHA-512.	42	The total number of bytes hashed by the hardware using SHA-512.
43		43
44	sha512_ops:	44	sha512_ops:
45	- The total number of SHA-512 operations submitted to the hardware.	45	The total number of SHA-512 operations submitted to the hardware.

Documentation/ABI/testing/debugfs-pktcdvd+6−7

 Contact:        Thomas Maier <balagi@justmail.de>
 Description:
-debugfs interface
------------------
 The pktcdvd module (packet writing driver) creates
 these files in debugfs:
 /sys/kernel/debug/pktcdvd/pktcdvd[0-7]/
-    info            (0444) Lots of driver statistics and infos.
-Example:
+    ====            ====== ====================================
--------
+    info            0444   Lots of driver statistics and infos.
+    ====            ====== ====================================
+Example::
-cat /sys/kernel/debug/pktcdvd/pktcdvd0/info
+    cat /sys/kernel/debug/pktcdvd/pktcdvd0/info

Documentation/ABI/testing/debugfs-turris-mox-rwtm+10−5

@@ -2,8 +2,13 @@ What: /sys/kernel/debug/turris-mox-rwtm/do_sign · 1 unmodified line
2	Date: Jun 2020	2	Date: Jun 2020
3	KernelVersion: 5.8	3	KernelVersion: 5.8
4	Contact: Marek Behún <marek.behun@nic.cz>	4	Contact: Marek Behún <marek.behun@nic.cz>
5	Description: (W) Message to sign with the ECDSA private key stored in	5	Description:
6	device's OTP. The message must be exactly 64 bytes (since	6
7	this is intended for SHA-512 hashes).	7	======= ===========================================================
8	(R) The resulting signature, 136 bytes. This contains the R and	8	(Write) Message to sign with the ECDSA private key stored in
9	S values of the ECDSA signature, both in big-endian format.	9	device's OTP. The message must be exactly 64 bytes
		10	(since this is intended for SHA-512 hashes).
		11	(Read) The resulting signature, 136 bytes. This contains the
		12	R and S values of the ECDSA signature, both in
		13	big-endian format.
		14	======= ===========================================================

Documentation/ABI/testing/debugfs-wilco-ec+11−10

@@ -27,16 +27,17 @@ Description: · 26 unmodified lines
27	for writing, two for the type and at least a single byte of	27	for writing, two for the type and at least a single byte of
28	data.	28	data.
29		29
30	Example:	30	Example::
31	// Request EC info type 3 (EC firmware build date)	31
32	// Corresponds with sending type 0x00f0 with	32	// Request EC info type 3 (EC firmware build date)
33	// MBOX = [38, 00, 03, 00]	33	// Corresponds with sending type 0x00f0 with
34	$ echo 00 f0 38 00 03 00 > /sys/kernel/debug/wilco_ec/raw	34	// MBOX = [38, 00, 03, 00]
35	// View the result. The decoded ASCII result "12/21/18" is	35	$ echo 00 f0 38 00 03 00 > /sys/kernel/debug/wilco_ec/raw
36	// included after the raw hex.	36	// View the result. The decoded ASCII result "12/21/18" is
37	// Corresponds with MBOX = [00, 00, 31, 32, 2f, 32, 31, 38, ...]	37	// included after the raw hex.
38	$ cat /sys/kernel/debug/wilco_ec/raw	38	// Corresponds with MBOX = [00, 00, 31, 32, 2f, 32, 31, 38, ...]
39	00 00 31 32 2f 32 31 2f 31 38 00 38 00 01 00 2f 00 ..12/21/18.8...	39	$ cat /sys/kernel/debug/wilco_ec/raw
		40	00 00 31 32 2f 32 31 2f 31 38 00 38 00 01 00 2f 00 ..12/21/18.8...
40		41
41	Note that the first 16 bytes of the received MBOX[] will be	42	Note that the first 16 bytes of the received MBOX[] will be
42	printed, even if some of the data is junk, and skipping bytes	43	printed, even if some of the data is junk, and skipping bytes

Documentation/ABI/testing/dell-smbios-wmi+16−16

Documentation/ABI/testing/dev-kmsg+17−10

@@ -6,6 +6,7 @@ Description: The /dev/kmsg character device node provides userspace access · 5 unmodified lines
6	to the kernel's printk buffer.	6	to the kernel's printk buffer.
7		7
8	Injecting messages:	8	Injecting messages:
		9
9	Every write() to the opened device node places a log entry in	10	Every write() to the opened device node places a log entry in
10	the kernel's printk buffer.	11	the kernel's printk buffer.
11		12
@@ -21,6 +22,7 @@ Description: The /dev/kmsg character device node provides userspace access · 9 unmodified lines
21	the messages can always be reliably determined.	22	the messages can always be reliably determined.
22		23
23	Accessing the buffer:	24	Accessing the buffer:
		25
24	Every read() from the opened device node receives one record	26	Every read() from the opened device node receives one record
25	of the kernel's printk buffer.	27	of the kernel's printk buffer.
26		28
@@ -48,6 +50,7 @@ Description: The /dev/kmsg character device node provides userspace access · 21 unmodified lines
48	if needed, without limiting the interface to a single reader.	50	if needed, without limiting the interface to a single reader.
49		51
50	The device supports seek with the following parameters:	52	The device supports seek with the following parameters:
		53
51	SEEK_SET, 0	54	SEEK_SET, 0
52	seek to the first entry in the buffer	55	seek to the first entry in the buffer
53	SEEK_END, 0	56	SEEK_END, 0
@@ -87,18 +90,22 @@ Description: The /dev/kmsg character device node provides userspace access · 33 unmodified lines
87	readable context of the message, for reliable processing in	90	readable context of the message, for reliable processing in
88	userspace.	91	userspace.
89		92
90	Example:	93	Example::
91	7,160,424069,-;pci_root PNP0A03:00: host bridge window [io 0x0000-0x0cf7] (ignored)	94
92	SUBSYSTEM=acpi	95	7,160,424069,-;pci_root PNP0A03:00: host bridge window [io 0x0000-0x0cf7] (ignored)
93	DEVICE=+acpi:PNP0A03:00	96	SUBSYSTEM=acpi
94	6,339,5140900,-;NET: Registered protocol family 10	97	DEVICE=+acpi:PNP0A03:00
95	30,340,5690716,-;udevd[80]: starting version 181	98	6,339,5140900,-;NET: Registered protocol family 10
		99	30,340,5690716,-;udevd[80]: starting version 181
96		100
97	The DEVICE= key uniquely identifies devices the following way:	101	The DEVICE= key uniquely identifies devices the following way:
98	b12:8 - block dev_t	102
99	c127:3 - char dev_t	103	============ =================
100	n8 - netdev ifindex	104	b12:8 block dev_t
101	+sound:card0 - subsystem:devname	105	c127:3 char dev_t
		106	n8 netdev ifindex
		107	+sound:card0 subsystem:devname
		108	============ =================
102		109
103	The flags field carries '-' by default. A 'c' indicates a	110	The flags field carries '-' by default. A 'c' indicates a
104	fragment of a line. Note, that these hints about continuation	111	fragment of a line. Note, that these hints about continuation

Documentation/ABI/testing/evm+12−5

 		echoing a value to <securityfs>/evm made up of the
 		following bits:
+		===	  ==================================================
 		Bit	  Effect
+		===	  ==================================================
 		0	  Enable HMAC validation and creation
 		1	  Enable digital signature validation
 		2	  Permit modification of EVM-protected metadata at
 			  runtime. Not supported if HMAC validation and
 			  creation is enabled.
 		31	  Disable further runtime modification of EVM policy
+		===	  ==================================================
-		For example:
+		For example::
-		echo 1 ><securityfs>/evm
+		  echo 1 ><securityfs>/evm
 		will enable HMAC validation and creation
-		echo 0x80000003 ><securityfs>/evm
+		::
+		  echo 0x80000003 ><securityfs>/evm
 		will enable HMAC and digital signature validation and
 		HMAC creation and disable all further modification of policy.
-		echo 0x80000006 ><securityfs>/evm
+		::
+		  echo 0x80000006 ><securityfs>/evm
 		will enable digital signature validation, permit
 		modification of EVM-protected metadata and
 		Shows the set of extended attributes used to calculate or
 		validate the EVM signature, and allows additional attributes
 		to be added at runtime. Any signatures generated after
-		additional attributes are added (and on files posessing those
+		additional attributes are added (and on files possessing those
 		additional attributes) will only be valid if the same
 		additional attributes are configured on system boot. Writing
 		a single period (.) will lock the xattr list from any further

Documentation/ABI/testing/gpio-cdev+7−6

@@ -12,15 +12,16 @@ Description: · 11 unmodified lines
12	The following file operations are supported:	12	The following file operations are supported:
13		13
14	open(2)	14	open(2)
15	Currently the only useful flags are O_RDWR.	15	Currently the only useful flags are O_RDWR.
16		16
17	ioctl(2)	17	ioctl(2)
18	Initiate various actions.	18	Initiate various actions.
19	See the inline documentation in [include/uapi]<linux/gpio.h>	19
20	for descriptions of all ioctls.	20	See the inline documentation in [include/uapi]<linux/gpio.h>
		21	for descriptions of all ioctls.
21		22
22	close(2)	23	close(2)
23	Stops and free up the I/O contexts that was associated	24	Stops and free up the I/O contexts that was associated
24	with the file descriptor.	25	with the file descriptor.
25		26
26	Users: TBD	27	Users: TBD

Documentation/ABI/testing/ima_policy+18−12

@@ -15,19 +15,22 @@ Description: · 14 unmodified lines
15	IMA appraisal, if configured, uses these file measurements	15	IMA appraisal, if configured, uses these file measurements
16	for local measurement appraisal.	16	for local measurement appraisal.
17		17
18	rule format: action [condition ...]	18	::
19		19
20	action: measure \| dont_measure \| appraise \| dont_appraise \|	20	rule format: action [condition ...]
21	audit \| hash \| dont_hash	21
22	condition:= base \| lsm [option]	22	action: measure \| dont_measure \| appraise \| dont_appraise \|
		23	audit \| hash \| dont_hash
		24	condition:= base \| lsm [option]
23	base: [[func=] [mask=] [fsmagic=] [fsuuid=] [uid=]	25	base: [[func=] [mask=] [fsmagic=] [fsuuid=] [uid=]
24	[euid=] [fowner=] [fsname=]]	26	[euid=] [fowner=] [fsname=]]
25	lsm: [[subj_user=] [subj_role=] [subj_type=]	27	lsm: [[subj_user=] [subj_role=] [subj_type=]
26	[obj_user=] [obj_role=] [obj_type=]]	28	[obj_user=] [obj_role=] [obj_type=]]
27	option: [[appraise_type=]] [template=] [permit_directio]	29	option: [[appraise_type=]] [template=] [permit_directio]
28	[appraise_flag=] [keyrings=]	30	[appraise_flag=] [keyrings=]
29	base: func:= [BPRM_CHECK][MMAP_CHECK][CREDS_CHECK][FILE_CHECK][MODULE_CHECK]	31	base:
30	[FIRMWARE_CHECK]	32	func:= [BPRM_CHECK][MMAP_CHECK][CREDS_CHECK][FILE_CHECK]MODULE_CHECK]
		33	[FIRMWARE_CHECK]
31	[KEXEC_KERNEL_CHECK] [KEXEC_INITRAMFS_CHECK]	34	[KEXEC_KERNEL_CHECK] [KEXEC_INITRAMFS_CHECK]
32	[KEXEC_CMDLINE] [KEY_CHECK]	35	[KEXEC_CMDLINE] [KEY_CHECK]
33	mask:= [[^]MAY_READ] [[^]MAY_WRITE] [[^]MAY_APPEND]	36	mask:= [[^]MAY_READ] [[^]MAY_WRITE] [[^]MAY_APPEND]
@@ -37,8 +40,9 @@ Description: · 3 unmodified lines
37	uid:= decimal value	40	uid:= decimal value
38	euid:= decimal value	41	euid:= decimal value
39	fowner:= decimal value	42	fowner:= decimal value
40	lsm: are LSM specific	43	lsm: are LSM specific
41	option: appraise_type:= [imasig] [imasig\|modsig]	44	option:
		45	appraise_type:= [imasig] [imasig\|modsig]
42	appraise_flag:= [check_blacklist]	46	appraise_flag:= [check_blacklist]
43	Currently, blacklist check is only for files signed with appended	47	Currently, blacklist check is only for files signed with appended
44	signature.	48	signature.
@@ -49,7 +53,7 @@ Description: · 4 unmodified lines
49	(eg, ima-ng). Only valid when action is "measure".	53	(eg, ima-ng). Only valid when action is "measure".
50	pcr:= decimal value	54	pcr:= decimal value
51		55
52	default policy:	56	default policy:
53	# PROC_SUPER_MAGIC	57	# PROC_SUPER_MAGIC
54	dont_measure fsmagic=0x9fa0	58	dont_measure fsmagic=0x9fa0
55	dont_appraise fsmagic=0x9fa0	59	dont_appraise fsmagic=0x9fa0
@@ -97,7 +101,8 @@ Description: · 41 unmodified lines
97		101
98	Examples of LSM specific definitions:	102	Examples of LSM specific definitions:
99		103
100	SELinux:	104	SELinux::
		105
101	dont_measure obj_type=var_log_t	106	dont_measure obj_type=var_log_t
102	dont_appraise obj_type=var_log_t	107	dont_appraise obj_type=var_log_t
103	dont_measure obj_type=auditd_log_t	108	dont_measure obj_type=auditd_log_t
@@ -105,10 +110,11 @@ Description: · 1 unmodified line
105	measure subj_user=system_u func=FILE_CHECK mask=MAY_READ	110	measure subj_user=system_u func=FILE_CHECK mask=MAY_READ
106	measure subj_role=system_r func=FILE_CHECK mask=MAY_READ	111	measure subj_role=system_r func=FILE_CHECK mask=MAY_READ
107		112
108	Smack:	113	Smack::
		114
109	measure subj_user=_ func=FILE_CHECK mask=MAY_READ	115	measure subj_user=_ func=FILE_CHECK mask=MAY_READ
110		116
111	Example of measure rules using alternate PCRs:	117	Example of measure rules using alternate PCRs::
112		118
113	measure func=KEXEC_KERNEL_CHECK pcr=4	119	measure func=KEXEC_KERNEL_CHECK pcr=4
114	measure func=KEXEC_INITRAMFS_CHECK pcr=5	120	measure func=KEXEC_INITRAMFS_CHECK pcr=5

Documentation/ABI/testing/procfs-diskstats+26−20

@@ -6,32 +6,38 @@ Description: · 5 unmodified lines
6	of block devices. Each line contains the following 14	6	of block devices. Each line contains the following 14
7	fields:	7	fields:
8		8
9	1 - major number	9	== ===================================
10	2 - minor mumber	10	1 major number
11	3 - device name	11	2 minor mumber
12	4 - reads completed successfully	12	3 device name
13	5 - reads merged	13	4 reads completed successfully
14	6 - sectors read	14	5 reads merged
15	7 - time spent reading (ms)	15	6 sectors read
16	8 - writes completed	16	7 time spent reading (ms)
17	9 - writes merged	17	8 writes completed
18	10 - sectors written	18	9 writes merged
19	11 - time spent writing (ms)	19	10 sectors written
20	12 - I/Os currently in progress	20	11 time spent writing (ms)
21	13 - time spent doing I/Os (ms)	21	12 I/Os currently in progress
22	14 - weighted time spent doing I/Os (ms)	22	13 time spent doing I/Os (ms)
		23	14 weighted time spent doing I/Os (ms)
		24	== ===================================
23		25
24	Kernel 4.18+ appends four more fields for discard	26	Kernel 4.18+ appends four more fields for discard
25	tracking putting the total at 18:	27	tracking putting the total at 18:
26		28
27	15 - discards completed successfully	29	== ===================================
28	16 - discards merged	30	15 discards completed successfully
29	17 - sectors discarded	31	16 discards merged
30	18 - time spent discarding	32	17 sectors discarded
		33	18 time spent discarding
		34	== ===================================
31		35
32	Kernel 5.5+ appends two more fields for flush requests:	36	Kernel 5.5+ appends two more fields for flush requests:
33		37
34	19 - flush requests completed successfully	38	== =====================================
35	20 - time spent flushing	39	19 flush requests completed successfully
		40	20 time spent flushing
		41	== =====================================
36		42
37	For more details refer to Documentation/admin-guide/iostats.rst	43	For more details refer to Documentation/admin-guide/iostats.rst

Documentation/ABI/testing/procfs-smaps_rollup+24−24

@@ -14,28 +14,28 @@ Description: · 13 unmodified lines
14	For more details, see Documentation/filesystems/proc.rst	14	For more details, see Documentation/filesystems/proc.rst
15	and the procfs man page.	15	and the procfs man page.
16		16
17	Typical output looks like this:	17	Typical output looks like this::
18		18
19	00100000-ff709000 ---p 00000000 00:00 0 [rollup]	19	00100000-ff709000 ---p 00000000 00:00 0 [rollup]
20	Size: 1192 kB	20	Size: 1192 kB
21	KernelPageSize: 4 kB	21	KernelPageSize: 4 kB
22	MMUPageSize: 4 kB	22	MMUPageSize: 4 kB
23	Rss: 884 kB	23	Rss: 884 kB
24	Pss: 385 kB	24	Pss: 385 kB
25	Pss_Anon: 301 kB	25	Pss_Anon: 301 kB
26	Pss_File: 80 kB	26	Pss_File: 80 kB
27	Pss_Shmem: 4 kB	27	Pss_Shmem: 4 kB
28	Shared_Clean: 696 kB	28	Shared_Clean: 696 kB
29	Shared_Dirty: 0 kB	29	Shared_Dirty: 0 kB
30	Private_Clean: 120 kB	30	Private_Clean: 120 kB
31	Private_Dirty: 68 kB	31	Private_Dirty: 68 kB
32	Referenced: 884 kB	32	Referenced: 884 kB
33	Anonymous: 68 kB	33	Anonymous: 68 kB
34	LazyFree: 0 kB	34	LazyFree: 0 kB
35	AnonHugePages: 0 kB	35	AnonHugePages: 0 kB
36	ShmemPmdMapped: 0 kB	36	ShmemPmdMapped: 0 kB
37	Shared_Hugetlb: 0 kB	37	Shared_Hugetlb: 0 kB
38	Private_Hugetlb: 0 kB	38	Private_Hugetlb: 0 kB
39	Swap: 0 kB	39	Swap: 0 kB
40	SwapPss: 0 kB	40	SwapPss: 0 kB
41	Locked: 385 kB	41	Locked: 385 kB

Documentation/ABI/testing/pstore+9−10

Documentation/ABI/testing/sysfs-block+21−17

@@ -4,23 +4,27 @@ Contact: Jerome Marchand <jmarchan@redhat.com> · 3 unmodified lines
4	Description:	4	Description:
5	The /sys/block/<disk>/stat files displays the I/O	5	The /sys/block/<disk>/stat files displays the I/O
6	statistics of disk <disk>. They contain 11 fields:	6	statistics of disk <disk>. They contain 11 fields:
7	1 - reads completed successfully	7
8	2 - reads merged	8	== ==============================================
9	3 - sectors read	9	1 reads completed successfully
10	4 - time spent reading (ms)	10	2 reads merged
11	5 - writes completed	11	3 sectors read
12	6 - writes merged	12	4 time spent reading (ms)
13	7 - sectors written	13	5 writes completed
14	8 - time spent writing (ms)	14	6 writes merged
15	9 - I/Os currently in progress	15	7 sectors written
16	10 - time spent doing I/Os (ms)	16	8 time spent writing (ms)
17	11 - weighted time spent doing I/Os (ms)	17	9 I/Os currently in progress
18	12 - discards completed	18	10 time spent doing I/Os (ms)
19	13 - discards merged	19	11 weighted time spent doing I/Os (ms)
20	14 - sectors discarded	20	12 discards completed
21	15 - time spent discarding (ms)	21	13 discards merged
22	16 - flush requests completed	22	14 sectors discarded
23	17 - time spent flushing (ms)	23	15 time spent discarding (ms)
		24	16 flush requests completed
		25	17 time spent flushing (ms)
		26	== ==============================================
		27
24	For more details refer Documentation/admin-guide/iostats.rst	28	For more details refer Documentation/admin-guide/iostats.rst
25		29
26		30

Documentation/ABI/testing/sysfs-block-device+2−0

 		It has the following valid values:
+		==	========================================================
 		0	OFF - the LED is not activated on activity
 		1	BLINK_ON - the LED blinks on every 10ms when activity is
 			detected.
 		2	BLINK_OFF - the LED is on when idle, and blinks off
 			every 10ms when activity is detected.
+		==	========================================================
 		Note that the user must turn sw_activity OFF it they wish to
 		control the activity LED via the em_message file.

Documentation/ABI/testing/sysfs-block-rnbd+2−2

@@ -9,9 +9,9 @@ Description: To unmap a volume, "normal" or "force" has to be written to: · 8 unmodified lines
9	is using the device. When "force" is used, the device is also unmapped	9	is using the device. When "force" is used, the device is also unmapped
10	when device is in use. All I/Os that are in progress will fail.	10	when device is in use. All I/Os that are in progress will fail.
11		11
12	Example:	12	Example::
13		13
14	# echo "normal" > /sys/block/rnbd0/rnbd/unmap_device	14	# echo "normal" > /sys/block/rnbd0/rnbd/unmap_device
15		15
16	What: /sys/block/rnbd<N>/rnbd/state	16	What: /sys/block/rnbd<N>/rnbd/state
17	Date: Feb 2020	17	Date: Feb 2020

Documentation/ABI/testing/sysfs-bus-acpi+11−8

 		This attribute indicates the full path of ACPI namespace
 		object associated with the device object.  For example,
 		\_SB_.PCI0.
 		This file is not present for device objects representing
 		fixed ACPI hardware features (like power and sleep
 		buttons).
 		The return value is a decimal integer representing the device's
 		status bitmap:
-		Bit [0] –  Set if the device is present.
+		===========  ==================================================
-		Bit [1] –  Set if the device is enabled and decoding its
+		Bit [0]      Set if the device is present.
-		           resources.
+		Bit [1]      Set if the device is enabled and decoding its
-		Bit [2] –  Set if the device should be shown in the UI.
+		             resources.
-		Bit [3] –  Set if the device is functioning properly (cleared if
+		Bit [2]      Set if the device should be shown in the UI.
-		           device failed its diagnostics).
+		Bit [3]      Set if the device is functioning properly (cleared
-		Bit [4] –  Set if the battery is present.
+			     if device failed its diagnostics).
-		Bits [31:5] –  Reserved (must be cleared)
+		Bit [4]      Set if the battery is present.
+		Bits [31:5]  Reserved (must be cleared)
+		===========  ==================================================
 		If bit [0] is clear, then bit 1 must also be clear (a device
 		that is not present cannot be enabled).

Documentation/ABI/testing/sysfs-bus-coresight-devices-cti+30−30

@@ -8,50 +8,50 @@ What: /sys/bus/coresight/devices/<cti-name>/powered · 7 unmodified lines
8	Date: March 2020	8	Date: March 2020
9	KernelVersion 5.7	9	KernelVersion 5.7
10	Contact: Mike Leach or Mathieu Poirier	10	Contact: Mike Leach or Mathieu Poirier
11	Description: (R) Indicate if the CTI hardware is powered.	11	Description: (Read) Indicate if the CTI hardware is powered.
12		12
13	What: /sys/bus/coresight/devices/<cti-name>/ctmid	13	What: /sys/bus/coresight/devices/<cti-name>/ctmid
14	Date: March 2020	14	Date: March 2020
15	KernelVersion 5.7	15	KernelVersion 5.7
16	Contact: Mike Leach or Mathieu Poirier	16	Contact: Mike Leach or Mathieu Poirier
17	Description: (R) Display the associated CTM ID	17	Description: (Read) Display the associated CTM ID
18		18
19	What: /sys/bus/coresight/devices/<cti-name>/nr_trigger_cons	19	What: /sys/bus/coresight/devices/<cti-name>/nr_trigger_cons
20	Date: March 2020	20	Date: March 2020
21	KernelVersion 5.7	21	KernelVersion 5.7
22	Contact: Mike Leach or Mathieu Poirier	22	Contact: Mike Leach or Mathieu Poirier
23	Description: (R) Number of devices connected to triggers on this CTI	23	Description: (Read) Number of devices connected to triggers on this CTI
24		24
25	What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/name	25	What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/name
26	Date: March 2020	26	Date: March 2020
27	KernelVersion 5.7	27	KernelVersion 5.7
28	Contact: Mike Leach or Mathieu Poirier	28	Contact: Mike Leach or Mathieu Poirier
29	Description: (R) Name of connected device <N>	29	Description: (Read) Name of connected device <N>
30		30
31	What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/in_signals	31	What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/in_signals
32	Date: March 2020	32	Date: March 2020
33	KernelVersion 5.7	33	KernelVersion 5.7
34	Contact: Mike Leach or Mathieu Poirier	34	Contact: Mike Leach or Mathieu Poirier
35	Description: (R) Input trigger signals from connected device <N>	35	Description: (Read) Input trigger signals from connected device <N>
36		36
37	What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/in_types	37	What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/in_types
38	Date: March 2020	38	Date: March 2020
39	KernelVersion 5.7	39	KernelVersion 5.7
40	Contact: Mike Leach or Mathieu Poirier	40	Contact: Mike Leach or Mathieu Poirier
41	Description: (R) Functional types for the input trigger signals	41	Description: (Read) Functional types for the input trigger signals
42	from connected device <N>	42	from connected device <N>
43		43
44	What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/out_signals	44	What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/out_signals
45	Date: March 2020	45	Date: March 2020
46	KernelVersion 5.7	46	KernelVersion 5.7
47	Contact: Mike Leach or Mathieu Poirier	47	Contact: Mike Leach or Mathieu Poirier
48	Description: (R) Output trigger signals to connected device <N>	48	Description: (Read) Output trigger signals to connected device <N>
49		49
50	What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/out_types	50	What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/out_types
51	Date: March 2020	51	Date: March 2020
52	KernelVersion 5.7	52	KernelVersion 5.7
53	Contact: Mike Leach or Mathieu Poirier	53	Contact: Mike Leach or Mathieu Poirier
54	Description: (R) Functional types for the output trigger signals	54	Description: (Read) Functional types for the output trigger signals
55	to connected device <N>	55	to connected device <N>
56		56
57	What: /sys/bus/coresight/devices/<cti-name>/regs/inout_sel	57	What: /sys/bus/coresight/devices/<cti-name>/regs/inout_sel
@@ -88,7 +88,7 @@ What: /sys/bus/coresight/devices/<cti-name>/regs/intack · 30 unmodified lines
88	Date: March 2020	88	Date: March 2020
89	KernelVersion 5.7	89	KernelVersion 5.7
90	Contact: Mike Leach or Mathieu Poirier	90	Contact: Mike Leach or Mathieu Poirier
91	Description: (W) Write the INTACK register.	91	Description: (Write) Write the INTACK register.
92		92
93	What: /sys/bus/coresight/devices/<cti-name>/regs/appset	93	What: /sys/bus/coresight/devices/<cti-name>/regs/appset
94	Date: March 2020	94	Date: March 2020
@@ -101,99 +101,99 @@ What: /sys/bus/coresight/devices/<cti-name>/regs/appclear · 6 unmodified lines
101	Date: March 2020	101	Date: March 2020
102	KernelVersion 5.7	102	KernelVersion 5.7
103	Contact: Mike Leach or Mathieu Poirier	103	Contact: Mike Leach or Mathieu Poirier
104	Description: (W) Write APPCLEAR register to deactivate channel.	104	Description: (Write) Write APPCLEAR register to deactivate channel.
105		105
106	What: /sys/bus/coresight/devices/<cti-name>/regs/apppulse	106	What: /sys/bus/coresight/devices/<cti-name>/regs/apppulse
107	Date: March 2020	107	Date: March 2020
108	KernelVersion 5.7	108	KernelVersion 5.7
109	Contact: Mike Leach or Mathieu Poirier	109	Contact: Mike Leach or Mathieu Poirier
110	Description: (W) Write APPPULSE to pulse a channel active for one clock	110	Description: (Write) Write APPPULSE to pulse a channel active for one clock
111	cycle.	111	cycle.
112		112
113	What: /sys/bus/coresight/devices/<cti-name>/regs/chinstatus	113	What: /sys/bus/coresight/devices/<cti-name>/regs/chinstatus
114	Date: March 2020	114	Date: March 2020
115	KernelVersion 5.7	115	KernelVersion 5.7
116	Contact: Mike Leach or Mathieu Poirier	116	Contact: Mike Leach or Mathieu Poirier
117	Description: (R) Read current status of channel inputs.	117	Description: (Read) Read current status of channel inputs.
118		118
119	What: /sys/bus/coresight/devices/<cti-name>/regs/choutstatus	119	What: /sys/bus/coresight/devices/<cti-name>/regs/choutstatus
120	Date: March 2020	120	Date: March 2020
121	KernelVersion 5.7	121	KernelVersion 5.7
122	Contact: Mike Leach or Mathieu Poirier	122	Contact: Mike Leach or Mathieu Poirier
123	Description: (R) read current status of channel outputs.	123	Description: (Read) read current status of channel outputs.
124		124
125	What: /sys/bus/coresight/devices/<cti-name>/regs/triginstatus	125	What: /sys/bus/coresight/devices/<cti-name>/regs/triginstatus
126	Date: March 2020	126	Date: March 2020
127	KernelVersion 5.7	127	KernelVersion 5.7
128	Contact: Mike Leach or Mathieu Poirier	128	Contact: Mike Leach or Mathieu Poirier
129	Description: (R) read current status of input trigger signals	129	Description: (Read) read current status of input trigger signals
130		130
131	What: /sys/bus/coresight/devices/<cti-name>/regs/trigoutstatus	131	What: /sys/bus/coresight/devices/<cti-name>/regs/trigoutstatus
132	Date: March 2020	132	Date: March 2020
133	KernelVersion 5.7	133	KernelVersion 5.7
134	Contact: Mike Leach or Mathieu Poirier	134	Contact: Mike Leach or Mathieu Poirier
135	Description: (R) read current status of output trigger signals.	135	Description: (Read) read current status of output trigger signals.
136		136
137	What: /sys/bus/coresight/devices/<cti-name>/channels/trigin_attach	137	What: /sys/bus/coresight/devices/<cti-name>/channels/trigin_attach
138	Date: March 2020	138	Date: March 2020
139	KernelVersion 5.7	139	KernelVersion 5.7
140	Contact: Mike Leach or Mathieu Poirier	140	Contact: Mike Leach or Mathieu Poirier
141	Description: (W) Attach a CTI input trigger to a CTM channel.	141	Description: (Write) Attach a CTI input trigger to a CTM channel.
142		142
143	What: /sys/bus/coresight/devices/<cti-name>/channels/trigin_detach	143	What: /sys/bus/coresight/devices/<cti-name>/channels/trigin_detach
144	Date: March 2020	144	Date: March 2020
145	KernelVersion 5.7	145	KernelVersion 5.7
146	Contact: Mike Leach or Mathieu Poirier	146	Contact: Mike Leach or Mathieu Poirier
147	Description: (W) Detach a CTI input trigger from a CTM channel.	147	Description: (Write) Detach a CTI input trigger from a CTM channel.
148		148
149	What: /sys/bus/coresight/devices/<cti-name>/channels/trigout_attach	149	What: /sys/bus/coresight/devices/<cti-name>/channels/trigout_attach
150	Date: March 2020	150	Date: March 2020
151	KernelVersion 5.7	151	KernelVersion 5.7
152	Contact: Mike Leach or Mathieu Poirier	152	Contact: Mike Leach or Mathieu Poirier
153	Description: (W) Attach a CTI output trigger to a CTM channel.	153	Description: (Write) Attach a CTI output trigger to a CTM channel.
154		154
155	What: /sys/bus/coresight/devices/<cti-name>/channels/trigout_detach	155	What: /sys/bus/coresight/devices/<cti-name>/channels/trigout_detach
156	Date: March 2020	156	Date: March 2020
157	KernelVersion 5.7	157	KernelVersion 5.7
158	Contact: Mike Leach or Mathieu Poirier	158	Contact: Mike Leach or Mathieu Poirier
159	Description: (W) Detach a CTI output trigger from a CTM channel.	159	Description: (Write) Detach a CTI output trigger from a CTM channel.
160		160
161	What: /sys/bus/coresight/devices/<cti-name>/channels/chan_gate_enable	161	What: /sys/bus/coresight/devices/<cti-name>/channels/chan_gate_enable
162	Date: March 2020	162	Date: March 2020
163	KernelVersion 5.7	163	KernelVersion 5.7
164	Contact: Mike Leach or Mathieu Poirier	164	Contact: Mike Leach or Mathieu Poirier
165	Description: (RW) Enable CTIGATE for single channel (W) or list enabled	165	Description: (RW) Enable CTIGATE for single channel (Write) or list enabled
166	channels through the gate (R).	166	channels through the gate (R).
167		167
168	What: /sys/bus/coresight/devices/<cti-name>/channels/chan_gate_disable	168	What: /sys/bus/coresight/devices/<cti-name>/channels/chan_gate_disable
169	Date: March 2020	169	Date: March 2020
170	KernelVersion 5.7	170	KernelVersion 5.7
171	Contact: Mike Leach or Mathieu Poirier	171	Contact: Mike Leach or Mathieu Poirier
172	Description: (W) Disable CTIGATE for single channel.	172	Description: (Write) Disable CTIGATE for single channel.
173		173
174	What: /sys/bus/coresight/devices/<cti-name>/channels/chan_set	174	What: /sys/bus/coresight/devices/<cti-name>/channels/chan_set
175	Date: March 2020	175	Date: March 2020
176	KernelVersion 5.7	176	KernelVersion 5.7
177	Contact: Mike Leach or Mathieu Poirier	177	Contact: Mike Leach or Mathieu Poirier
178	Description: (W) Activate a single channel.	178	Description: (Write) Activate a single channel.
179		179
180	What: /sys/bus/coresight/devices/<cti-name>/channels/chan_clear	180	What: /sys/bus/coresight/devices/<cti-name>/channels/chan_clear
181	Date: March 2020	181	Date: March 2020
182	KernelVersion 5.7	182	KernelVersion 5.7
183	Contact: Mike Leach or Mathieu Poirier	183	Contact: Mike Leach or Mathieu Poirier
184	Description: (W) Deactivate a single channel.	184	Description: (Write) Deactivate a single channel.
185		185
186	What: /sys/bus/coresight/devices/<cti-name>/channels/chan_pulse	186	What: /sys/bus/coresight/devices/<cti-name>/channels/chan_pulse
187	Date: March 2020	187	Date: March 2020
188	KernelVersion 5.7	188	KernelVersion 5.7
189	Contact: Mike Leach or Mathieu Poirier	189	Contact: Mike Leach or Mathieu Poirier
190	Description: (W) Pulse a single channel - activate for a single clock cycle.	190	Description: (Write) Pulse a single channel - activate for a single clock cycle.
191		191
192	What: /sys/bus/coresight/devices/<cti-name>/channels/trigout_filtered	192	What: /sys/bus/coresight/devices/<cti-name>/channels/trigout_filtered
193	Date: March 2020	193	Date: March 2020
194	KernelVersion 5.7	194	KernelVersion 5.7
195	Contact: Mike Leach or Mathieu Poirier	195	Contact: Mike Leach or Mathieu Poirier
196	Description: (R) List of output triggers filtered across all connections.	196	Description: (Read) List of output triggers filtered across all connections.
197		197
198	What: /sys/bus/coresight/devices/<cti-name>/channels/trig_filter_enable	198	What: /sys/bus/coresight/devices/<cti-name>/channels/trig_filter_enable
199	Date: March 2020	199	Date: March 2020
@@ -205,13 +205,13 @@ What: /sys/bus/coresight/devices/<cti-name>/channels/chan_inuse · 5 unmodified lines
205	Date: March 2020	205	Date: March 2020
206	KernelVersion 5.7	206	KernelVersion 5.7
207	Contact: Mike Leach or Mathieu Poirier	207	Contact: Mike Leach or Mathieu Poirier
208	Description: (R) show channels with at least one attached trigger signal.	208	Description: (Read) show channels with at least one attached trigger signal.
209		209
210	What: /sys/bus/coresight/devices/<cti-name>/channels/chan_free	210	What: /sys/bus/coresight/devices/<cti-name>/channels/chan_free
211	Date: March 2020	211	Date: March 2020
212	KernelVersion 5.7	212	KernelVersion 5.7
213	Contact: Mike Leach or Mathieu Poirier	213	Contact: Mike Leach or Mathieu Poirier
214	Description: (R) show channels with no attached trigger signals.	214	Description: (Read) show channels with no attached trigger signals.
215		215
216	What: /sys/bus/coresight/devices/<cti-name>/channels/chan_xtrigs_sel	216	What: /sys/bus/coresight/devices/<cti-name>/channels/chan_xtrigs_sel
217	Date: March 2020	217	Date: March 2020
@@ -224,18 +224,18 @@ What: /sys/bus/coresight/devices/<cti-name>/channels/chan_xtrigs_in · 6 unmodified lines
224	Date: March 2020	224	Date: March 2020
225	KernelVersion 5.7	225	KernelVersion 5.7
226	Contact: Mike Leach or Mathieu Poirier	226	Contact: Mike Leach or Mathieu Poirier
227	Description: (R) Read to see input triggers connected to selected view	227	Description: (Read) Read to see input triggers connected to selected view
228	channel.	228	channel.
229		229
230	What: /sys/bus/coresight/devices/<cti-name>/channels/chan_xtrigs_out	230	What: /sys/bus/coresight/devices/<cti-name>/channels/chan_xtrigs_out
231	Date: March 2020	231	Date: March 2020
232	KernelVersion 5.7	232	KernelVersion 5.7
233	Contact: Mike Leach or Mathieu Poirier	233	Contact: Mike Leach or Mathieu Poirier
234	Description: (R) Read to see output triggers connected to selected view	234	Description: (Read) Read to see output triggers connected to selected view
235	channel.	235	channel.
236		236
237	What: /sys/bus/coresight/devices/<cti-name>/channels/chan_xtrigs_reset	237	What: /sys/bus/coresight/devices/<cti-name>/channels/chan_xtrigs_reset
238	Date: March 2020	238	Date: March 2020
239	KernelVersion 5.7	239	KernelVersion 5.7
240	Contact: Mike Leach or Mathieu Poirier	240	Contact: Mike Leach or Mathieu Poirier
241	Description: (W) Clear all channel / trigger programming.	241	Description: (Write) Clear all channel / trigger programming.

Documentation/ABI/testing/sysfs-bus-coresight-devices-etb10+12−9

@@ -4,7 +4,10 @@ KernelVersion: 3.19 · 3 unmodified lines
4	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	4	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
5	Description: (RW) Add/remove a sink from a trace path. There can be multiple	5	Description: (RW) Add/remove a sink from a trace path. There can be multiple
6	source for a single sink.	6	source for a single sink.
7	ex: echo 1 > /sys/bus/coresight/devices/20010000.etb/enable_sink	7
		8	ex::
		9
		10	echo 1 > /sys/bus/coresight/devices/20010000.etb/enable_sink
8		11
9	What: /sys/bus/coresight/devices/<memory_map>.etb/trigger_cntr	12	What: /sys/bus/coresight/devices/<memory_map>.etb/trigger_cntr
10	Date: November 2014	13	Date: November 2014
@@ -20,21 +23,21 @@ What: /sys/bus/coresight/devices/<memory_map>.etb/mgmt/rdp · 9 unmodified lines
20	Date: March 2016	23	Date: March 2016
21	KernelVersion: 4.7	24	KernelVersion: 4.7
22	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	25	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
23	Description: (R) Defines the depth, in words, of the trace RAM in powers of	26	Description: (Read) Defines the depth, in words, of the trace RAM in powers of
24	2. The value is read directly from HW register RDP, 0x004.	27	2. The value is read directly from HW register RDP, 0x004.
25		28
26	What: /sys/bus/coresight/devices/<memory_map>.etb/mgmt/sts	29	What: /sys/bus/coresight/devices/<memory_map>.etb/mgmt/sts
27	Date: March 2016	30	Date: March 2016
28	KernelVersion: 4.7	31	KernelVersion: 4.7
29	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	32	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
30	Description: (R) Shows the value held by the ETB status register. The value	33	Description: (Read) Shows the value held by the ETB status register. The value
31	is read directly from HW register STS, 0x00C.	34	is read directly from HW register STS, 0x00C.
32		35
33	What: /sys/bus/coresight/devices/<memory_map>.etb/mgmt/rrp	36	What: /sys/bus/coresight/devices/<memory_map>.etb/mgmt/rrp
34	Date: March 2016	37	Date: March 2016
35	KernelVersion: 4.7	38	KernelVersion: 4.7
36	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	39	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
37	Description: (R) Shows the value held by the ETB RAM Read Pointer register	40	Description: (Read) Shows the value held by the ETB RAM Read Pointer register
38	that is used to read entries from the Trace RAM over the APB	41	that is used to read entries from the Trace RAM over the APB
39	interface. The value is read directly from HW register RRP,	42	interface. The value is read directly from HW register RRP,
40	0x014.	43	0x014.
@@ -43,7 +46,7 @@ What: /sys/bus/coresight/devices/<memory_map>.etb/mgmt/rwp · 2 unmodified lines
43	Date: March 2016	46	Date: March 2016
44	KernelVersion: 4.7	47	KernelVersion: 4.7
45	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	48	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
46	Description: (R) Shows the value held by the ETB RAM Write Pointer register	49	Description: (Read) Shows the value held by the ETB RAM Write Pointer register
47	that is used to sets the write pointer to write entries from	50	that is used to sets the write pointer to write entries from
48	the CoreSight bus into the Trace RAM. The value is read directly	51	the CoreSight bus into the Trace RAM. The value is read directly
49	from HW register RWP, 0x018.	52	from HW register RWP, 0x018.
@@ -52,21 +55,21 @@ What: /sys/bus/coresight/devices/<memory_map>.etb/mgmt/trg · 2 unmodified lines
52	Date: March 2016	55	Date: March 2016
53	KernelVersion: 4.7	56	KernelVersion: 4.7
54	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	57	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
55	Description: (R) Similar to "trigger_cntr" above except that this value is	58	Description: (Read) Similar to "trigger_cntr" above except that this value is
56	read directly from HW register TRG, 0x01C.	59	read directly from HW register TRG, 0x01C.
57		60
58	What: /sys/bus/coresight/devices/<memory_map>.etb/mgmt/ctl	61	What: /sys/bus/coresight/devices/<memory_map>.etb/mgmt/ctl
59	Date: March 2016	62	Date: March 2016
60	KernelVersion: 4.7	63	KernelVersion: 4.7
61	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	64	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
62	Description: (R) Shows the value held by the ETB Control register. The value	65	Description: (Read) Shows the value held by the ETB Control register. The value
63	is read directly from HW register CTL, 0x020.	66	is read directly from HW register CTL, 0x020.
64		67
65	What: /sys/bus/coresight/devices/<memory_map>.etb/mgmt/ffsr	68	What: /sys/bus/coresight/devices/<memory_map>.etb/mgmt/ffsr
66	Date: March 2016	69	Date: March 2016
67	KernelVersion: 4.7	70	KernelVersion: 4.7
68	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	71	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
69	Description: (R) Shows the value held by the ETB Formatter and Flush Status	72	Description: (Read) Shows the value held by the ETB Formatter and Flush Status
70	register. The value is read directly from HW register FFSR,	73	register. The value is read directly from HW register FFSR,
71	0x300.	74	0x300.
72		75
@@ -74,6 +77,6 @@ What: /sys/bus/coresight/devices/<memory_map>.etb/mgmt/ffcr · 1 unmodified line
74	Date: March 2016	77	Date: March 2016
75	KernelVersion: 4.7	78	KernelVersion: 4.7
76	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	79	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
77	Description: (R) Shows the value held by the ETB Formatter and Flush Control	80	Description: (Read) Shows the value held by the ETB Formatter and Flush Control
78	register. The value is read directly from HW register FFCR,	81	register. The value is read directly from HW register FFCR,
79	0x304.	82	0x304.

Documentation/ABI/testing/sysfs-bus-coresight-devices-etm3x+5−5

@@ -146,28 +146,28 @@ What: /sys/bus/coresight/devices/<memory_map>.[etm\|ptm]/nr_addr_cmp · 145 unmodified lines
146	Date: November 2014	146	Date: November 2014
147	KernelVersion: 3.19	147	KernelVersion: 3.19
148	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	148	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
149	Description: (R) Provides the number of address comparators pairs accessible	149	Description: (Read) Provides the number of address comparators pairs accessible
150	on a trace unit, as specified by bit 3:0 of register ETMCCR.	150	on a trace unit, as specified by bit 3:0 of register ETMCCR.
151		151
152	What: /sys/bus/coresight/devices/<memory_map>.[etm\|ptm]/nr_cntr	152	What: /sys/bus/coresight/devices/<memory_map>.[etm\|ptm]/nr_cntr
153	Date: November 2014	153	Date: November 2014
154	KernelVersion: 3.19	154	KernelVersion: 3.19
155	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	155	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
156	Description: (R) Provides the number of counters accessible on a trace unit,	156	Description: (Read) Provides the number of counters accessible on a trace unit,
157	as specified by bit 15:13 of register ETMCCR.	157	as specified by bit 15:13 of register ETMCCR.
158		158
159	What: /sys/bus/coresight/devices/<memory_map>.[etm\|ptm]/nr_ctxid_cmp	159	What: /sys/bus/coresight/devices/<memory_map>.[etm\|ptm]/nr_ctxid_cmp
160	Date: November 2014	160	Date: November 2014
161	KernelVersion: 3.19	161	KernelVersion: 3.19
162	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	162	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
163	Description: (R) Provides the number of context ID comparator available on a	163	Description: (Read) Provides the number of context ID comparator available on a
164	trace unit, as specified by bit 25:24 of register ETMCCR.	164	trace unit, as specified by bit 25:24 of register ETMCCR.
165		165
166	What: /sys/bus/coresight/devices/<memory_map>.[etm\|ptm]/reset	166	What: /sys/bus/coresight/devices/<memory_map>.[etm\|ptm]/reset
167	Date: November 2014	167	Date: November 2014
168	KernelVersion: 3.19	168	KernelVersion: 3.19
169	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	169	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
170	Description: (W) Cancels all configuration on a trace unit and set it back	170	Description: (Write) Cancels all configuration on a trace unit and set it back
171	to its boot configuration.	171	to its boot configuration.
172		172
173	What: /sys/bus/coresight/devices/<memory_map>.[etm\|ptm]/seq_12_event	173	What: /sys/bus/coresight/devices/<memory_map>.[etm\|ptm]/seq_12_event
@@ -216,7 +216,7 @@ What: /sys/bus/coresight/devices/<memory_map>.[etm\|ptm]/curr_seq_state · 42 unmodified lines
216	Date: November 2014	216	Date: November 2014
217	KernelVersion: 3.19	217	KernelVersion: 3.19
218	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	218	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
219	Description: (R) Holds the current state of the sequencer.	219	Description: (Read) Holds the current state of the sequencer.
220		220
221	What: /sys/bus/coresight/devices/<memory_map>.[etm\|ptm]/sync_freq	221	What: /sys/bus/coresight/devices/<memory_map>.[etm\|ptm]/sync_freq
222	Date: November 2014	222	Date: November 2014

Documentation/ABI/testing/sysfs-bus-coresight-devices-etm4x+38−38

@@ -12,75 +12,75 @@ What: /sys/bus/coresight/devices/etm<N>/cpu · 11 unmodified lines
12	Date: April 2015	12	Date: April 2015
13	KernelVersion: 4.01	13	KernelVersion: 4.01
14	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	14	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
15	Description: (R) The CPU this tracing entity is associated with.	15	Description: (Read) The CPU this tracing entity is associated with.
16		16
17	What: /sys/bus/coresight/devices/etm<N>/nr_pe_cmp	17	What: /sys/bus/coresight/devices/etm<N>/nr_pe_cmp
18	Date: April 2015	18	Date: April 2015
19	KernelVersion: 4.01	19	KernelVersion: 4.01
20	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	20	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
21	Description: (R) Indicates the number of PE comparator inputs that are	21	Description: (Read) Indicates the number of PE comparator inputs that are
22	available for tracing.	22	available for tracing.
23		23
24	What: /sys/bus/coresight/devices/etm<N>/nr_addr_cmp	24	What: /sys/bus/coresight/devices/etm<N>/nr_addr_cmp
25	Date: April 2015	25	Date: April 2015
26	KernelVersion: 4.01	26	KernelVersion: 4.01
27	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	27	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
28	Description: (R) Indicates the number of address comparator pairs that are	28	Description: (Read) Indicates the number of address comparator pairs that are
29	available for tracing.	29	available for tracing.
30		30
31	What: /sys/bus/coresight/devices/etm<N>/nr_cntr	31	What: /sys/bus/coresight/devices/etm<N>/nr_cntr
32	Date: April 2015	32	Date: April 2015
33	KernelVersion: 4.01	33	KernelVersion: 4.01
34	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	34	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
35	Description: (R) Indicates the number of counters that are available for	35	Description: (Read) Indicates the number of counters that are available for
36	tracing.	36	tracing.
37		37
38	What: /sys/bus/coresight/devices/etm<N>/nr_ext_inp	38	What: /sys/bus/coresight/devices/etm<N>/nr_ext_inp
39	Date: April 2015	39	Date: April 2015
40	KernelVersion: 4.01	40	KernelVersion: 4.01
41	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	41	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
42	Description: (R) Indicates how many external inputs are implemented.	42	Description: (Read) Indicates how many external inputs are implemented.
43		43
44	What: /sys/bus/coresight/devices/etm<N>/numcidc	44	What: /sys/bus/coresight/devices/etm<N>/numcidc
45	Date: April 2015	45	Date: April 2015
46	KernelVersion: 4.01	46	KernelVersion: 4.01
47	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	47	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
48	Description: (R) Indicates the number of Context ID comparators that are	48	Description: (Read) Indicates the number of Context ID comparators that are
49	available for tracing.	49	available for tracing.
50		50
51	What: /sys/bus/coresight/devices/etm<N>/numvmidc	51	What: /sys/bus/coresight/devices/etm<N>/numvmidc
52	Date: April 2015	52	Date: April 2015
53	KernelVersion: 4.01	53	KernelVersion: 4.01
54	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	54	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
55	Description: (R) Indicates the number of VMID comparators that are available	55	Description: (Read) Indicates the number of VMID comparators that are available
56	for tracing.	56	for tracing.
57		57
58	What: /sys/bus/coresight/devices/etm<N>/nrseqstate	58	What: /sys/bus/coresight/devices/etm<N>/nrseqstate
59	Date: April 2015	59	Date: April 2015
60	KernelVersion: 4.01	60	KernelVersion: 4.01
61	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	61	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
62	Description: (R) Indicates the number of sequencer states that are	62	Description: (Read) Indicates the number of sequencer states that are
63	implemented.	63	implemented.
64		64
65	What: /sys/bus/coresight/devices/etm<N>/nr_resource	65	What: /sys/bus/coresight/devices/etm<N>/nr_resource
66	Date: April 2015	66	Date: April 2015
67	KernelVersion: 4.01	67	KernelVersion: 4.01
68	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	68	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
69	Description: (R) Indicates the number of resource selection pairs that are	69	Description: (Read) Indicates the number of resource selection pairs that are
70	available for tracing.	70	available for tracing.
71		71
72	What: /sys/bus/coresight/devices/etm<N>/nr_ss_cmp	72	What: /sys/bus/coresight/devices/etm<N>/nr_ss_cmp
73	Date: April 2015	73	Date: April 2015
74	KernelVersion: 4.01	74	KernelVersion: 4.01
75	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	75	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
76	Description: (R) Indicates the number of single-shot comparator controls that	76	Description: (Read) Indicates the number of single-shot comparator controls that
77	are available for tracing.	77	are available for tracing.
78		78
79	What: /sys/bus/coresight/devices/etm<N>/reset	79	What: /sys/bus/coresight/devices/etm<N>/reset
80	Date: April 2015	80	Date: April 2015
81	KernelVersion: 4.01	81	KernelVersion: 4.01
82	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	82	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
83	Description: (W) Cancels all configuration on a trace unit and set it back	83	Description: (Write) Cancels all configuration on a trace unit and set it back
84	to its boot configuration.	84	to its boot configuration.
85		85
86	What: /sys/bus/coresight/devices/etm<N>/mode	86	What: /sys/bus/coresight/devices/etm<N>/mode
@@ -300,7 +300,7 @@ What: /sys/bus/coresight/devices/etm<N>/addr_cmp_view · 213 unmodified lines
300	Date: December 2019	300	Date: December 2019
301	KernelVersion: 5.5	301	KernelVersion: 5.5
302	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	302	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
303	Description: (R) Print the current settings for the selected address	303	Description: (Read) Print the current settings for the selected address
304	comparator.	304	comparator.
305		305
306	What: /sys/bus/coresight/devices/etm<N>/sshot_idx	306	What: /sys/bus/coresight/devices/etm<N>/sshot_idx
@@ -319,7 +319,7 @@ What: /sys/bus/coresight/devices/etm<N>/sshot_status · 12 unmodified lines
319	Date: December 2019	319	Date: December 2019
320	KernelVersion: 5.5	320	KernelVersion: 5.5
321	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	321	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
322	Description: (R) Print the current value of the selected single shot	322	Description: (Read) Print the current value of the selected single shot
323	status register.	323	status register.
324		324
325	What: /sys/bus/coresight/devices/etm<N>/sshot_pe_ctrl	325	What: /sys/bus/coresight/devices/etm<N>/sshot_pe_ctrl
@@ -333,111 +333,111 @@ What: /sys/bus/coresight/devices/etm<N>/mgmt/trcoslsr · 7 unmodified lines
333	Date: April 2015	333	Date: April 2015
334	KernelVersion: 4.01	334	KernelVersion: 4.01
335	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	335	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
336	Description: (R) Print the content of the OS Lock Status Register (0x304).	336	Description: (Read) Print the content of the OS Lock Status Register (0x304).
337	The value it taken directly from the HW.	337	The value it taken directly from the HW.
338		338
339	What: /sys/bus/coresight/devices/etm<N>/mgmt/trcpdcr	339	What: /sys/bus/coresight/devices/etm<N>/mgmt/trcpdcr
340	Date: April 2015	340	Date: April 2015
341	KernelVersion: 4.01	341	KernelVersion: 4.01
342	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	342	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
343	Description: (R) Print the content of the Power Down Control Register	343	Description: (Read) Print the content of the Power Down Control Register
344	(0x310). The value is taken directly from the HW.	344	(0x310). The value is taken directly from the HW.
345		345
346	What: /sys/bus/coresight/devices/etm<N>/mgmt/trcpdsr	346	What: /sys/bus/coresight/devices/etm<N>/mgmt/trcpdsr
347	Date: April 2015	347	Date: April 2015
348	KernelVersion: 4.01	348	KernelVersion: 4.01
349	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	349	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
350	Description: (R) Print the content of the Power Down Status Register	350	Description: (Read) Print the content of the Power Down Status Register
351	(0x314). The value is taken directly from the HW.	351	(0x314). The value is taken directly from the HW.
352		352
353	What: /sys/bus/coresight/devices/etm<N>/mgmt/trclsr	353	What: /sys/bus/coresight/devices/etm<N>/mgmt/trclsr
354	Date: April 2015	354	Date: April 2015
355	KernelVersion: 4.01	355	KernelVersion: 4.01
356	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	356	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
357	Description: (R) Print the content of the SW Lock Status Register	357	Description: (Read) Print the content of the SW Lock Status Register
358	(0xFB4). The value is taken directly from the HW.	358	(0xFB4). The value is taken directly from the HW.
359		359
360	What: /sys/bus/coresight/devices/etm<N>/mgmt/trcauthstatus	360	What: /sys/bus/coresight/devices/etm<N>/mgmt/trcauthstatus
361	Date: April 2015	361	Date: April 2015
362	KernelVersion: 4.01	362	KernelVersion: 4.01
363	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	363	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
364	Description: (R) Print the content of the Authentication Status Register	364	Description: (Read) Print the content of the Authentication Status Register
365	(0xFB8). The value is taken directly from the HW.	365	(0xFB8). The value is taken directly from the HW.
366		366
367	What: /sys/bus/coresight/devices/etm<N>/mgmt/trcdevid	367	What: /sys/bus/coresight/devices/etm<N>/mgmt/trcdevid
368	Date: April 2015	368	Date: April 2015
369	KernelVersion: 4.01	369	KernelVersion: 4.01
370	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	370	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
371	Description: (R) Print the content of the Device ID Register	371	Description: (Read) Print the content of the Device ID Register
372	(0xFC8). The value is taken directly from the HW.	372	(0xFC8). The value is taken directly from the HW.
373		373
374	What: /sys/bus/coresight/devices/etm<N>/mgmt/trcdevtype	374	What: /sys/bus/coresight/devices/etm<N>/mgmt/trcdevtype
375	Date: April 2015	375	Date: April 2015
376	KernelVersion: 4.01	376	KernelVersion: 4.01
377	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	377	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
378	Description: (R) Print the content of the Device Type Register	378	Description: (Read) Print the content of the Device Type Register
379	(0xFCC). The value is taken directly from the HW.	379	(0xFCC). The value is taken directly from the HW.
380		380
381	What: /sys/bus/coresight/devices/etm<N>/mgmt/trcpidr0	381	What: /sys/bus/coresight/devices/etm<N>/mgmt/trcpidr0
382	Date: April 2015	382	Date: April 2015
383	KernelVersion: 4.01	383	KernelVersion: 4.01
384	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	384	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
385	Description: (R) Print the content of the Peripheral ID0 Register	385	Description: (Read) Print the content of the Peripheral ID0 Register
386	(0xFE0). The value is taken directly from the HW.	386	(0xFE0). The value is taken directly from the HW.
387		387
388	What: /sys/bus/coresight/devices/etm<N>/mgmt/trcpidr1	388	What: /sys/bus/coresight/devices/etm<N>/mgmt/trcpidr1
389	Date: April 2015	389	Date: April 2015
390	KernelVersion: 4.01	390	KernelVersion: 4.01
391	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	391	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
392	Description: (R) Print the content of the Peripheral ID1 Register	392	Description: (Read) Print the content of the Peripheral ID1 Register
393	(0xFE4). The value is taken directly from the HW.	393	(0xFE4). The value is taken directly from the HW.
394		394
395	What: /sys/bus/coresight/devices/etm<N>/mgmt/trcpidr2	395	What: /sys/bus/coresight/devices/etm<N>/mgmt/trcpidr2
396	Date: April 2015	396	Date: April 2015
397	KernelVersion: 4.01	397	KernelVersion: 4.01
398	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	398	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
399	Description: (R) Print the content of the Peripheral ID2 Register	399	Description: (Read) Print the content of the Peripheral ID2 Register
400	(0xFE8). The value is taken directly from the HW.	400	(0xFE8). The value is taken directly from the HW.
401		401
402	What: /sys/bus/coresight/devices/etm<N>/mgmt/trcpidr3	402	What: /sys/bus/coresight/devices/etm<N>/mgmt/trcpidr3
403	Date: April 2015	403	Date: April 2015
404	KernelVersion: 4.01	404	KernelVersion: 4.01
405	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	405	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
406	Description: (R) Print the content of the Peripheral ID3 Register	406	Description: (Read) Print the content of the Peripheral ID3 Register
407	(0xFEC). The value is taken directly from the HW.	407	(0xFEC). The value is taken directly from the HW.
408		408
409	What: /sys/bus/coresight/devices/etm<N>/mgmt/trcconfig	409	What: /sys/bus/coresight/devices/etm<N>/mgmt/trcconfig
410	Date: February 2016	410	Date: February 2016
411	KernelVersion: 4.07	411	KernelVersion: 4.07
412	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	412	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
413	Description: (R) Print the content of the trace configuration register	413	Description: (Read) Print the content of the trace configuration register
414	(0x010) as currently set by SW.	414	(0x010) as currently set by SW.
415		415
416	What: /sys/bus/coresight/devices/etm<N>/mgmt/trctraceid	416	What: /sys/bus/coresight/devices/etm<N>/mgmt/trctraceid
417	Date: February 2016	417	Date: February 2016
418	KernelVersion: 4.07	418	KernelVersion: 4.07
419	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	419	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
420	Description: (R) Print the content of the trace ID register (0x040).	420	Description: (Read) Print the content of the trace ID register (0x040).
421		421
422	What: /sys/bus/coresight/devices/etm<N>/trcidr/trcidr0	422	What: /sys/bus/coresight/devices/etm<N>/trcidr/trcidr0
423	Date: April 2015	423	Date: April 2015
424	KernelVersion: 4.01	424	KernelVersion: 4.01
425	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	425	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
426	Description: (R) Returns the tracing capabilities of the trace unit (0x1E0).	426	Description: (Read) Returns the tracing capabilities of the trace unit (0x1E0).
427	The value is taken directly from the HW.	427	The value is taken directly from the HW.
428		428
429	What: /sys/bus/coresight/devices/etm<N>/trcidr/trcidr1	429	What: /sys/bus/coresight/devices/etm<N>/trcidr/trcidr1
430	Date: April 2015	430	Date: April 2015
431	KernelVersion: 4.01	431	KernelVersion: 4.01
432	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	432	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
433	Description: (R) Returns the tracing capabilities of the trace unit (0x1E4).	433	Description: (Read) Returns the tracing capabilities of the trace unit (0x1E4).
434	The value is taken directly from the HW.	434	The value is taken directly from the HW.
435		435
436	What: /sys/bus/coresight/devices/etm<N>/trcidr/trcidr2	436	What: /sys/bus/coresight/devices/etm<N>/trcidr/trcidr2
437	Date: April 2015	437	Date: April 2015
438	KernelVersion: 4.01	438	KernelVersion: 4.01
439	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	439	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
440	Description: (R) Returns the maximum size of the data value, data address,	440	Description: (Read) Returns the maximum size of the data value, data address,
441	VMID, context ID and instuction address in the trace unit	441	VMID, context ID and instuction address in the trace unit
442	(0x1E8). The value is taken directly from the HW.	442	(0x1E8). The value is taken directly from the HW.
443		443
@@ -445,7 +445,7 @@ What: /sys/bus/coresight/devices/etm<N>/trcidr/trcidr3 · 1 unmodified line
445	Date: April 2015	445	Date: April 2015
446	KernelVersion: 4.01	446	KernelVersion: 4.01
447	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	447	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
448	Description: (R) Returns the value associated with various resources	448	Description: (Read) Returns the value associated with various resources
449	available to the trace unit. See the Trace Macrocell	449	available to the trace unit. See the Trace Macrocell
450	architecture specification for more details (0x1E8).	450	architecture specification for more details (0x1E8).
451	The value is taken directly from the HW.	451	The value is taken directly from the HW.
@@ -454,42 +454,42 @@ What: /sys/bus/coresight/devices/etm<N>/trcidr/trcidr4 · 2 unmodified lines
454	Date: April 2015	454	Date: April 2015
455	KernelVersion: 4.01	455	KernelVersion: 4.01
456	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	456	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
457	Description: (R) Returns how many resources the trace unit supports (0x1F0).	457	Description: (Read) Returns how many resources the trace unit supports (0x1F0).
458	The value is taken directly from the HW.	458	The value is taken directly from the HW.
459		459
460	What: /sys/bus/coresight/devices/etm<N>/trcidr/trcidr5	460	What: /sys/bus/coresight/devices/etm<N>/trcidr/trcidr5
461	Date: April 2015	461	Date: April 2015
462	KernelVersion: 4.01	462	KernelVersion: 4.01
463	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	463	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
464	Description: (R) Returns how many resources the trace unit supports (0x1F4).	464	Description: (Read) Returns how many resources the trace unit supports (0x1F4).
465	The value is taken directly from the HW.	465	The value is taken directly from the HW.
466		466
467	What: /sys/bus/coresight/devices/etm<N>/trcidr/trcidr8	467	What: /sys/bus/coresight/devices/etm<N>/trcidr/trcidr8
468	Date: April 2015	468	Date: April 2015
469	KernelVersion: 4.01	469	KernelVersion: 4.01
470	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	470	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
471	Description: (R) Returns the maximum speculation depth of the instruction	471	Description: (Read) Returns the maximum speculation depth of the instruction
472	trace stream. (0x180). The value is taken directly from the HW.	472	trace stream. (0x180). The value is taken directly from the HW.
473		473
474	What: /sys/bus/coresight/devices/etm<N>/trcidr/trcidr9	474	What: /sys/bus/coresight/devices/etm<N>/trcidr/trcidr9
475	Date: April 2015	475	Date: April 2015
476	KernelVersion: 4.01	476	KernelVersion: 4.01
477	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	477	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
478	Description: (R) Returns the number of P0 right-hand keys that the trace unit	478	Description: (Read) Returns the number of P0 right-hand keys that the trace unit
479	can use (0x184). The value is taken directly from the HW.	479	can use (0x184). The value is taken directly from the HW.
480		480
481	What: /sys/bus/coresight/devices/etm<N>/trcidr/trcidr10	481	What: /sys/bus/coresight/devices/etm<N>/trcidr/trcidr10
482	Date: April 2015	482	Date: April 2015
483	KernelVersion: 4.01	483	KernelVersion: 4.01
484	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	484	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
485	Description: (R) Returns the number of P1 right-hand keys that the trace unit	485	Description: (Read) Returns the number of P1 right-hand keys that the trace unit
486	can use (0x188). The value is taken directly from the HW.	486	can use (0x188). The value is taken directly from the HW.
487		487
488	What: /sys/bus/coresight/devices/etm<N>/trcidr/trcidr11	488	What: /sys/bus/coresight/devices/etm<N>/trcidr/trcidr11
489	Date: April 2015	489	Date: April 2015
490	KernelVersion: 4.01	490	KernelVersion: 4.01
491	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	491	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
492	Description: (R) Returns the number of special P1 right-hand keys that the	492	Description: (Read) Returns the number of special P1 right-hand keys that the
493	trace unit can use (0x18C). The value is taken directly from	493	trace unit can use (0x18C). The value is taken directly from
494	the HW.	494	the HW.
495		495
@@ -497,7 +497,7 @@ What: /sys/bus/coresight/devices/etm<N>/trcidr/trcidr12 · 1 unmodified line
497	Date: April 2015	497	Date: April 2015
498	KernelVersion: 4.01	498	KernelVersion: 4.01
499	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	499	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
500	Description: (R) Returns the number of conditional P1 right-hand keys that	500	Description: (Read) Returns the number of conditional P1 right-hand keys that
501	the trace unit can use (0x190). The value is taken directly	501	the trace unit can use (0x190). The value is taken directly
502	from the HW.	502	from the HW.
503		503
@@ -505,6 +505,6 @@ What: /sys/bus/coresight/devices/etm<N>/trcidr/trcidr13 · 1 unmodified line
505	Date: April 2015	505	Date: April 2015
506	KernelVersion: 4.01	506	KernelVersion: 4.01
507	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	507	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
508	Description: (R) Returns the number of special conditional P1 right-hand keys	508	Description: (Read) Returns the number of special conditional P1 right-hand keys
509	that the trace unit can use (0x194). The value is taken	509	that the trace unit can use (0x194). The value is taken
510	directly from the HW.	510	directly from the HW.

Documentation/ABI/testing/sysfs-bus-coresight-devices-stm+1−1

@@ -42,7 +42,7 @@ What: /sys/bus/coresight/devices/<memory_map>.stm/status · 41 unmodified lines
42	Date: April 2016	42	Date: April 2016
43	KernelVersion: 4.7	43	KernelVersion: 4.7
44	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	44	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
45	Description: (R) List various control and status registers. The specific	45	Description: (Read) List various control and status registers. The specific
46	layout and content is driver specific.	46	layout and content is driver specific.
47		47
48	What: /sys/bus/coresight/devices/<memory_map>.stm/traceid	48	What: /sys/bus/coresight/devices/<memory_map>.stm/traceid

Documentation/ABI/testing/sysfs-bus-coresight-devices-tmc+10−10

@@ -11,21 +11,21 @@ What: /sys/bus/coresight/devices/<memory_map>.tmc/mgmt/rsz · 10 unmodified lines
11	Date: March 2016	11	Date: March 2016
12	KernelVersion: 4.7	12	KernelVersion: 4.7
13	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	13	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
14	Description: (R) Defines the size, in 32-bit words, of the local RAM buffer.	14	Description: (Read) Defines the size, in 32-bit words, of the local RAM buffer.
15	The value is read directly from HW register RSZ, 0x004.	15	The value is read directly from HW register RSZ, 0x004.
16		16
17	What: /sys/bus/coresight/devices/<memory_map>.tmc/mgmt/sts	17	What: /sys/bus/coresight/devices/<memory_map>.tmc/mgmt/sts
18	Date: March 2016	18	Date: March 2016
19	KernelVersion: 4.7	19	KernelVersion: 4.7
20	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	20	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
21	Description: (R) Shows the value held by the TMC status register. The value	21	Description: (Read) Shows the value held by the TMC status register. The value
22	is read directly from HW register STS, 0x00C.	22	is read directly from HW register STS, 0x00C.
23		23
24	What: /sys/bus/coresight/devices/<memory_map>.tmc/mgmt/rrp	24	What: /sys/bus/coresight/devices/<memory_map>.tmc/mgmt/rrp
25	Date: March 2016	25	Date: March 2016
26	KernelVersion: 4.7	26	KernelVersion: 4.7
27	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	27	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
28	Description: (R) Shows the value held by the TMC RAM Read Pointer register	28	Description: (Read) Shows the value held by the TMC RAM Read Pointer register
29	that is used to read entries from the Trace RAM over the APB	29	that is used to read entries from the Trace RAM over the APB
30	interface. The value is read directly from HW register RRP,	30	interface. The value is read directly from HW register RRP,
31	0x014.	31	0x014.
@@ -34,7 +34,7 @@ What: /sys/bus/coresight/devices/<memory_map>.tmc/mgmt/rwp · 2 unmodified lines
34	Date: March 2016	34	Date: March 2016
35	KernelVersion: 4.7	35	KernelVersion: 4.7
36	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	36	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
37	Description: (R) Shows the value held by the TMC RAM Write Pointer register	37	Description: (Read) Shows the value held by the TMC RAM Write Pointer register
38	that is used to sets the write pointer to write entries from	38	that is used to sets the write pointer to write entries from
39	the CoreSight bus into the Trace RAM. The value is read directly	39	the CoreSight bus into the Trace RAM. The value is read directly
40	from HW register RWP, 0x018.	40	from HW register RWP, 0x018.
@@ -43,21 +43,21 @@ What: /sys/bus/coresight/devices/<memory_map>.tmc/mgmt/trg · 2 unmodified lines
43	Date: March 2016	43	Date: March 2016
44	KernelVersion: 4.7	44	KernelVersion: 4.7
45	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	45	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
46	Description: (R) Similar to "trigger_cntr" above except that this value is	46	Description: (Read) Similar to "trigger_cntr" above except that this value is
47	read directly from HW register TRG, 0x01C.	47	read directly from HW register TRG, 0x01C.
48		48
49	What: /sys/bus/coresight/devices/<memory_map>.tmc/mgmt/ctl	49	What: /sys/bus/coresight/devices/<memory_map>.tmc/mgmt/ctl
50	Date: March 2016	50	Date: March 2016
51	KernelVersion: 4.7	51	KernelVersion: 4.7
52	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	52	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
53	Description: (R) Shows the value held by the TMC Control register. The value	53	Description: (Read) Shows the value held by the TMC Control register. The value
54	is read directly from HW register CTL, 0x020.	54	is read directly from HW register CTL, 0x020.
55		55
56	What: /sys/bus/coresight/devices/<memory_map>.tmc/mgmt/ffsr	56	What: /sys/bus/coresight/devices/<memory_map>.tmc/mgmt/ffsr
57	Date: March 2016	57	Date: March 2016
58	KernelVersion: 4.7	58	KernelVersion: 4.7
59	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	59	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
60	Description: (R) Shows the value held by the TMC Formatter and Flush Status	60	Description: (Read) Shows the value held by the TMC Formatter and Flush Status
61	register. The value is read directly from HW register FFSR,	61	register. The value is read directly from HW register FFSR,
62	0x300.	62	0x300.
63		63
@@ -65,7 +65,7 @@ What: /sys/bus/coresight/devices/<memory_map>.tmc/mgmt/ffcr · 1 unmodified line
65	Date: March 2016	65	Date: March 2016
66	KernelVersion: 4.7	66	KernelVersion: 4.7
67	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	67	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
68	Description: (R) Shows the value held by the TMC Formatter and Flush Control	68	Description: (Read) Shows the value held by the TMC Formatter and Flush Control
69	register. The value is read directly from HW register FFCR,	69	register. The value is read directly from HW register FFCR,
70	0x304.	70	0x304.
71		71
@@ -73,7 +73,7 @@ What: /sys/bus/coresight/devices/<memory_map>.tmc/mgmt/mode · 1 unmodified line
73	Date: March 2016	73	Date: March 2016
74	KernelVersion: 4.7	74	KernelVersion: 4.7
75	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	75	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
76	Description: (R) Shows the value held by the TMC Mode register, which	76	Description: (Read) Shows the value held by the TMC Mode register, which
77	indicate the mode the device has been configured to enact. The	77	indicate the mode the device has been configured to enact. The
78	The value is read directly from the MODE register, 0x028.	78	The value is read directly from the MODE register, 0x028.
79		79
@@ -81,7 +81,7 @@ What: /sys/bus/coresight/devices/<memory_map>.tmc/mgmt/devid · 1 unmodified line
81	Date: March 2016	81	Date: March 2016
82	KernelVersion: 4.7	82	KernelVersion: 4.7
83	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>	83	Contact: Mathieu Poirier <mathieu.poirier@linaro.org>
84	Description: (R) Indicates the capabilities of the Coresight TMC.	84	Description: (Read) Indicates the capabilities of the Coresight TMC.
85	The value is read directly from the DEVID register, 0xFC8,	85	The value is read directly from the DEVID register, 0xFC8,
86		86
87	What: /sys/bus/coresight/devices/<memory_map>.tmc/buffer_size	87	What: /sys/bus/coresight/devices/<memory_map>.tmc/buffer_size

Documentation/ABI/testing/sysfs-bus-css+3−0

Documentation/ABI/testing/sysfs-bus-dfl+2−0

@@ -4,6 +4,7 @@ KernelVersion: 5.10 · 3 unmodified lines
4	Contact: Xu Yilun <yilun.xu@intel.com>	4	Contact: Xu Yilun <yilun.xu@intel.com>
5	Description: Read-only. It returns type of DFL FIU of the device. Now DFL	5	Description: Read-only. It returns type of DFL FIU of the device. Now DFL
6	supports 2 FIU types, 0 for FME, 1 for PORT.	6	supports 2 FIU types, 0 for FME, 1 for PORT.
		7
7	Format: 0x%x	8	Format: 0x%x
8		9
9	What: /sys/bus/dfl/devices/dfl_dev.X/feature_id	10	What: /sys/bus/dfl/devices/dfl_dev.X/feature_id
@@ -12,4 +13,5 @@ KernelVersion: 5.10 · 2 unmodified lines
12	Contact: Xu Yilun <yilun.xu@intel.com>	13	Contact: Xu Yilun <yilun.xu@intel.com>
13	Description: Read-only. It returns feature identifier local to its DFL FIU	14	Description: Read-only. It returns feature identifier local to its DFL FIU
14	type.	15	type.
		16
15	Format: 0x%x	17	Format: 0x%x

Documentation/ABI/testing/sysfs-bus-event_source-devices-dfl_fme+7−7

Documentation/ABI/testing/sysfs-bus-event_source-devices-format+2−1

@@ -10,7 +10,8 @@ Description: · 9 unmodified lines
10	name/value pairs.	10	name/value pairs.
11		11
12	Userspace must be prepared for the possibility that attributes	12	Userspace must be prepared for the possibility that attributes
13	define overlapping bit ranges. For example:	13	define overlapping bit ranges. For example::
		14
14	attr1 = 'config:0-23'	15	attr1 = 'config:0-23'
15	attr2 = 'config:0-7'	16	attr2 = 'config:0-7'
16	attr3 = 'config:12-35'	17	attr3 = 'config:12-35'

Documentation/ABI/testing/sysfs-bus-event_source-devices-hv_24x7+3−3

@@ -7,7 +7,7 @@ Description: Read-only. Attribute group to describe the magic bits · 6 unmodified lines
7		7
8	Each attribute under this group defines a bit range of the	8	Each attribute under this group defines a bit range of the
9	perf_event_attr.config. All supported attributes are listed	9	perf_event_attr.config. All supported attributes are listed
10	below.	10	below::
11		11
12	chip = "config:16-31"	12	chip = "config:16-31"
13	core = "config:16-31"	13	core = "config:16-31"
@@ -16,9 +16,9 @@ Description: Read-only. Attribute group to describe the magic bits · 2 unmodified lines
16	offset = "config:32-63"	16	offset = "config:32-63"
17	vcpu = "config:16-31"	17	vcpu = "config:16-31"
18		18
19	For example,	19	For example::
20		20
21	PM_PB_CYC = "domain=1,offset=0x80,chip=?,lpar=0x0"	21	PM_PB_CYC = "domain=1,offset=0x80,chip=?,lpar=0x0"
22		22
23	In this event, '?' after chip specifies that	23	In this event, '?' after chip specifies that
24	this value will be provided by user while running this event.	24	this value will be provided by user while running this event.

Documentation/ABI/testing/sysfs-bus-event_source-devices-hv_gpci+4−3

@@ -7,7 +7,7 @@ Description: Read-only. Attribute group to describe the magic bits · 6 unmodified lines
7		7
8	Each attribute under this group defines a bit range of the	8	Each attribute under this group defines a bit range of the
9	perf_event_attr.config. All supported attributes are listed	9	perf_event_attr.config. All supported attributes are listed
10	below.	10	below::
11		11
12	counter_info_version = "config:16-23"	12	counter_info_version = "config:16-23"
13	length = "config:24-31"	13	length = "config:24-31"
@@ -20,9 +20,9 @@ Description: Read-only. Attribute group to describe the magic bits · 6 unmodified lines
20	secondary_index = "config:0-15"	20	secondary_index = "config:0-15"
21	starting_index = "config:32-63"	21	starting_index = "config:32-63"
22		22
23	For example,	23	For example::
24		24
25	processor_core_utilization_instructions_completed = "request=0x94,	25	processor_core_utilization_instructions_completed = "request=0x94,
26	phys_processor_idx=?,counter_info_version=0x8,	26	phys_processor_idx=?,counter_info_version=0x8,
27	length=8,offset=0x18"	27	length=8,offset=0x18"
28		28
@@ -36,6 +36,7 @@ Description: · 7 unmodified lines
36	'0' if the hypervisor is configured to forbid access to event	36	'0' if the hypervisor is configured to forbid access to event
37	counters being accumulated by other guests and to physical	37	counters being accumulated by other guests and to physical
38	domain event counters.	38	domain event counters.
		39
39	'1' if that access is allowed.	40	'1' if that access is allowed.
40		41
41	What: /sys/bus/event_source/devices/hv_gpci/interface/ga	42	What: /sys/bus/event_source/devices/hv_gpci/interface/ga

Documentation/ABI/testing/sysfs-bus-fcoe+45−23

@@ -3,16 +3,19 @@ Date: August 2012 · 2 unmodified lines
3	KernelVersion: TBD	3	KernelVersion: TBD
4	Contact: Robert Love <robert.w.love@intel.com>, devel@open-fcoe.org	4	Contact: Robert Love <robert.w.love@intel.com>, devel@open-fcoe.org
5	Description: The FCoE bus. Attributes in this directory are control interfaces.	5	Description: The FCoE bus. Attributes in this directory are control interfaces.
		6
6	Attributes:	7	Attributes:
7		8
8	ctlr_create: 'FCoE Controller' instance creation interface. Writing an	9	ctlr_create:
		10	'FCoE Controller' instance creation interface. Writing an
9	<ifname> to this file will allocate and populate sysfs with a	11	<ifname> to this file will allocate and populate sysfs with a
10	fcoe_ctlr_device (ctlr_X). The user can then configure any	12	fcoe_ctlr_device (ctlr_X). The user can then configure any
11	per-port settings and finally write to the fcoe_ctlr_device's	13	per-port settings and finally write to the fcoe_ctlr_device's
12	'start' attribute to begin the kernel's discovery and login	14	'start' attribute to begin the kernel's discovery and login
13	process.	15	process.
14		16
15	ctlr_destroy: 'FCoE Controller' instance removal interface. Writing a	17	ctlr_destroy:
		18	'FCoE Controller' instance removal interface. Writing a
16	fcoe_ctlr_device's sysfs name to this file will log the	19	fcoe_ctlr_device's sysfs name to this file will log the
17	fcoe_ctlr_device out of the fabric or otherwise connected	20	fcoe_ctlr_device out of the fabric or otherwise connected
18	FCoE devices. It will also free all kernel memory allocated	21	FCoE devices. It will also free all kernel memory allocated
@@ -32,11 +35,13 @@ Description: 'FCoE Controller' instances on the fcoe bus. · 13 unmodified lines
32		35
33	Attributes:	36	Attributes:
34		37
35	fcf_dev_loss_tmo: Device loss timeout period (see below). Changing	38	fcf_dev_loss_tmo:
		39	Device loss timeout period (see below). Changing
36	this value will change the dev_loss_tmo for all	40	this value will change the dev_loss_tmo for all
37	FCFs discovered by this controller.	41	FCFs discovered by this controller.
38		42
39	mode: Display or change the FCoE Controller's mode. Possible	43	mode:
		44	Display or change the FCoE Controller's mode. Possible
40	modes are 'Fabric' and 'VN2VN'. If a FCoE Controller	45	modes are 'Fabric' and 'VN2VN'. If a FCoE Controller
41	is started in 'Fabric' mode then FIP FCF discovery is	46	is started in 'Fabric' mode then FIP FCF discovery is
42	initiated and ultimately a fabric login is attempted.	47	initiated and ultimately a fabric login is attempted.
@@ -44,23 +49,30 @@ Attributes: · 1 unmodified line
44	FIP VN2VN discovery and login is performed. A FCoE	49	FIP VN2VN discovery and login is performed. A FCoE
45	Controller only supports one mode at a time.	50	Controller only supports one mode at a time.
46		51
47	enabled: Whether an FCoE controller is enabled or disabled.	52	enabled:
		53	Whether an FCoE controller is enabled or disabled.
48	0 if disabled, 1 if enabled. Writing either 0 or 1	54	0 if disabled, 1 if enabled. Writing either 0 or 1
49	to this file will enable or disable the FCoE controller.	55	to this file will enable or disable the FCoE controller.
50		56
51	lesb/link_fail: Link Error Status Block (LESB) link failure count.	57	lesb/link_fail:
		58	Link Error Status Block (LESB) link failure count.
52		59
53	lesb/vlink_fail: Link Error Status Block (LESB) virtual link	60	lesb/vlink_fail:
		61	Link Error Status Block (LESB) virtual link
54	failure count.	62	failure count.
55		63
56	lesb/miss_fka: Link Error Status Block (LESB) missed FCoE	64	lesb/miss_fka:
		65	Link Error Status Block (LESB) missed FCoE
57	Initialization Protocol (FIP) Keep-Alives (FKA).	66	Initialization Protocol (FIP) Keep-Alives (FKA).
58		67
59	lesb/symb_err: Link Error Status Block (LESB) symbolic error count.	68	lesb/symb_err:
		69	Link Error Status Block (LESB) symbolic error count.
60		70
61	lesb/err_block: Link Error Status Block (LESB) block error count.	71	lesb/err_block:
		72	Link Error Status Block (LESB) block error count.
62		73
63	lesb/fcs_error: Link Error Status Block (LESB) Fibre Channel	74	lesb/fcs_error:
		75	Link Error Status Block (LESB) Fibre Channel
64	Services error count.	76	Services error count.
65		77
66	Notes: ctlr_X (global increment starting at 0)	78	Notes: ctlr_X (global increment starting at 0)
@@ -75,31 +87,41 @@ Description: 'FCoE FCF' instances on the fcoe bus. A FCF is a Fibre Channel · 8 unmodified lines
75	Fibre Channel frames into a FC fabric. It can also take	87	Fibre Channel frames into a FC fabric. It can also take
76	outbound FC frames and pack them in Ethernet packets to	88	outbound FC frames and pack them in Ethernet packets to
77	be sent to their destination on the Ethernet segment.	89	be sent to their destination on the Ethernet segment.
		90
78	Attributes:	91	Attributes:
79		92
80	fabric_name: Identifies the fabric that the FCF services.	93	fabric_name:
		94	Identifies the fabric that the FCF services.
81		95
82	switch_name: Identifies the FCF.	96	switch_name:
		97	Identifies the FCF.
83		98
84	priority: The switch's priority amongst other FCFs on the same	99	priority:
		100	The switch's priority amongst other FCFs on the same
85	fabric.	101	fabric.
86		102
87	selected: 1 indicates that the switch has been selected for use;	103	selected:
		104	1 indicates that the switch has been selected for use;
88	0 indicates that the switch will not be used.	105	0 indicates that the switch will not be used.
89		106
90	fc_map: The Fibre Channel MAP	107	fc_map:
		108	The Fibre Channel MAP
91		109
92	vfid: The Virtual Fabric ID	110	vfid:
		111	The Virtual Fabric ID
93		112
94	mac: The FCF's MAC address	113	mac:
		114	The FCF's MAC address
95		115
96	fka_period: The FIP Keep-Alive period	116	fka_period:
		117	The FIP Keep-Alive period
97		118
98	fabric_state: The internal kernel state	119	fabric_state: The internal kernel state
99	"Unknown" - Initialization value	120
100	"Disconnected" - No link to the FCF/fabric	121	- "Unknown" - Initialization value
101	"Connected" - Host is connected to the FCF	122	- "Disconnected" - No link to the FCF/fabric
102	"Deleted" - FCF is being removed from the system	123	- "Connected" - Host is connected to the FCF
		124	- "Deleted" - FCF is being removed from the system
103		125
104	dev_loss_tmo: The device loss timeout period for this FCF.	126	dev_loss_tmo: The device loss timeout period for this FCF.
105		127

Documentation/ABI/testing/sysfs-bus-fsl-mc+8−4

@@ -6,8 +6,10 @@ Description: · 5 unmodified lines
6	the driver to attempt to bind to the device found at	6	the driver to attempt to bind to the device found at
7	this location. The format for the location is Object.Id	7	this location. The format for the location is Object.Id
8	and is the same as found in /sys/bus/fsl-mc/devices/.	8	and is the same as found in /sys/bus/fsl-mc/devices/.
9	For example:	9
10	# echo dpni.2 > /sys/bus/fsl-mc/drivers/fsl_dpaa2_eth/bind	10	For example::
		11
		12	# echo dpni.2 > /sys/bus/fsl-mc/drivers/fsl_dpaa2_eth/bind
11		13
12	What: /sys/bus/fsl-mc/drivers/.../unbind	14	What: /sys/bus/fsl-mc/drivers/.../unbind
13	Date: December 2016	15	Date: December 2016
@@ -17,5 +19,7 @@ Description: · 3 unmodified lines
17	driver to attempt to unbind from the device found at	19	driver to attempt to unbind from the device found at
18	this location. The format for the location is Object.Id	20	this location. The format for the location is Object.Id
19	and is the same as found in /sys/bus/fsl-mc/devices/.	21	and is the same as found in /sys/bus/fsl-mc/devices/.
20	For example:	22
21	# echo dpni.2 > /sys/bus/fsl-mc/drivers/fsl_dpaa2_eth/unbind	23	For example::
		24
		25	# echo dpni.2 > /sys/bus/fsl-mc/drivers/fsl_dpaa2_eth/unbind

Documentation/ABI/testing/sysfs-bus-i2c-devices-fsa9480+16−10

@@ -3,19 +3,25 @@ Date: February 2011 · 2 unmodified lines
3	Contact: Minkyu Kang <mk7.kang@samsung.com>	3	Contact: Minkyu Kang <mk7.kang@samsung.com>
4	Description:	4	Description:
5	show what device is attached	5	show what device is attached
6	NONE - no device	6
7	USB - USB device is attached	7	======= ======================
8	UART - UART is attached	8	NONE no device
9	CHARGER - Charger is attaced	9	USB USB device is attached
10	JIG - JIG is attached	10	UART UART is attached
		11	CHARGER Charger is attaced
		12	JIG JIG is attached
		13	======= ======================
11		14
12	What: /sys/bus/i2c/devices/.../switch	15	What: /sys/bus/i2c/devices/.../switch
13	Date: February 2011	16	Date: February 2011
14	Contact: Minkyu Kang <mk7.kang@samsung.com>	17	Contact: Minkyu Kang <mk7.kang@samsung.com>
15	Description:	18	Description:
16	show or set the state of manual switch	19	show or set the state of manual switch
17	VAUDIO - switch to VAUDIO path	20
18	UART - switch to UART path	21	======= ==============================
19	AUDIO - switch to AUDIO path	22	VAUDIO switch to VAUDIO path
20	DHOST - switch to DHOST path	23	UART switch to UART path
21	AUTO - switch automatically by device	24	AUDIO switch to AUDIO path
		25	DHOST switch to DHOST path
		26	AUTO switch automatically by device
		27	======= ==============================

Documentation/ABI/testing/sysfs-bus-i2c-devices-pca954x+15−12

@@ -6,15 +6,18 @@ Description: · 5 unmodified lines
6	Value that exists only for mux devices that can be	6	Value that exists only for mux devices that can be
7	written to control the behaviour of the multiplexer on	7	written to control the behaviour of the multiplexer on
8	idle. Possible values:	8	idle. Possible values:
9	-2 - disconnect on idle, i.e. deselect the last used	9
10	channel, which is useful when there is a device	10	=========== ===============================================
11	with an address that conflicts with another	11	-2 disconnect on idle, i.e. deselect the last used
12	device on another mux on the same parent bus.	12	channel, which is useful when there is a device
13	-1 - leave the mux as-is, which is the most optimal	13	with an address that conflicts with another
14	setting in terms of I2C operations and is the	14	device on another mux on the same parent bus.
15	default mode.	15	-1 leave the mux as-is, which is the most optimal
16	0..<nchans> - set the mux to a predetermined channel,	16	setting in terms of I2C operations and is the
17	which is useful if there is one channel that is	17	default mode.
18	used almost always, and you want to reduce the	18	0..<nchans> set the mux to a predetermined channel,
19	latency for normal operations after rare	19	which is useful if there is one channel that is
20	transactions on other channels	20	used almost always, and you want to reduce the
		21	latency for normal operations after rare
		22	transactions on other channels
		23	=========== ===============================================

Documentation/ABI/testing/sysfs-bus-i3c+2−0

@@ -84,6 +84,7 @@ Description: · 83 unmodified lines
84	by space. Modes can be "hdr-ddr", "hdr-tsp" and "hdr-tsl".	84	by space. Modes can be "hdr-ddr", "hdr-tsp" and "hdr-tsl".
85	See the I3C specification for more details about these HDR	85	See the I3C specification for more details about these HDR
86	modes.	86	modes.
		87
87	This entry describes the HDRCAP of the master controller	88	This entry describes the HDRCAP of the master controller
88	driving the bus.	89	driving the bus.
89		90
@@ -135,6 +136,7 @@ Description: · 45 unmodified lines
135	Expose the HDR (High Data Rate) capabilities of a device.	136	Expose the HDR (High Data Rate) capabilities of a device.
136	Returns a list of supported HDR mode, each element is separated	137	Returns a list of supported HDR mode, each element is separated
137	by space. Modes can be "hdr-ddr", "hdr-tsp" and "hdr-tsl".	138	by space. Modes can be "hdr-ddr", "hdr-tsp" and "hdr-tsl".
		139
138	See the I3C specification for more details about these HDR	140	See the I3C specification for more details about these HDR
139	modes.	141	modes.
140		142

Documentation/ABI/testing/sysfs-bus-iio+29−1

Documentation/ABI/testing/sysfs-bus-iio-adc-envelope-detector+4−1

@@ -5,7 +5,8 @@ Contact: Peter Rosin <peda@axentia.se> · 4 unmodified lines
5	Description:	5	Description:
6	The DAC is used to find the peak level of an alternating	6	The DAC is used to find the peak level of an alternating
7	voltage input signal by a binary search using the output	7	voltage input signal by a binary search using the output
8	of a comparator wired to an interrupt pin. Like so:	8	of a comparator wired to an interrupt pin. Like so::
		9
9	_	10	_
10	\| \	11	\| \
11	input +------>-------\|+ \	12	input +------>-------\|+ \
@@ -19,10 +20,12 @@ Description: · 7 unmodified lines
19	\| irq\|------<-------'	20	\| irq\|------<-------'
20	\| \|	21	\| \|
21	'-------'	22	'-------'
		23
22	The boolean invert attribute (0/1) should be set when the	24	The boolean invert attribute (0/1) should be set when the
23	input signal is centered around the maximum value of the	25	input signal is centered around the maximum value of the
24	dac instead of zero. The envelope detector will search	26	dac instead of zero. The envelope detector will search
25	from below in this case and will also invert the result.	27	from below in this case and will also invert the result.
		28
26	The edge/level of the interrupt is also switched to its	29	The edge/level of the interrupt is also switched to its
27	opposite value.	30	opposite value.
28		31

Documentation/ABI/testing/sysfs-bus-iio-adc-hi8435+5−0

Documentation/ABI/testing/sysfs-bus-iio-adc-stm32+3−0

@@ -5,10 +5,13 @@ Description: · 4 unmodified lines
5	The STM32 ADC can be configured to use external trigger sources	5	The STM32 ADC can be configured to use external trigger sources
6	(e.g. timers, pwm or exti gpio). Then, it can be tuned to start	6	(e.g. timers, pwm or exti gpio). Then, it can be tuned to start
7	conversions on external trigger by either:	7	conversions on external trigger by either:
		8
8	- "rising-edge"	9	- "rising-edge"
9	- "falling-edge"	10	- "falling-edge"
10	- "both-edges".	11	- "both-edges".
		12
11	Reading returns current trigger polarity.	13	Reading returns current trigger polarity.
		14
12	Writing value before enabling conversions sets trigger polarity.	15	Writing value before enabling conversions sets trigger polarity.
13		16
14	What: /sys/bus/iio/devices/triggerX/trigger_polarity_available	17	What: /sys/bus/iio/devices/triggerX/trigger_polarity_available

Documentation/ABI/testing/sysfs-bus-iio-cros-ec+1−1

@@ -4,7 +4,7 @@ KernelVersion: 4.7 · 3 unmodified lines
4	Contact: linux-iio@vger.kernel.org	4	Contact: linux-iio@vger.kernel.org
5	Description:	5	Description:
6	Writing '1' will perform a FOC (Fast Online Calibration). The	6	Writing '1' will perform a FOC (Fast Online Calibration). The
7	corresponding calibration offsets can be read from *_calibbias	7	corresponding calibration offsets can be read from `*_calibbias`
8	entries.	8	entries.
9		9
10	What: /sys/bus/iio/devices/iio:deviceX/location	10	What: /sys/bus/iio/devices/iio:deviceX/location

Documentation/ABI/testing/sysfs-bus-iio-dfsdm-adc-stm32+7−1

@@ -3,14 +3,20 @@ KernelVersion: 4.14 · 2 unmodified lines
3	Contact: arnaud.pouliquen@st.com	3	Contact: arnaud.pouliquen@st.com
4	Description:	4	Description:
5	For audio purpose only.	5	For audio purpose only.
		6
6	Used by audio driver to set/get the spi input frequency.	7	Used by audio driver to set/get the spi input frequency.
		8
7	This is mandatory if DFSDM is slave on SPI bus, to	9	This is mandatory if DFSDM is slave on SPI bus, to
8	provide information on the SPI clock frequency during runtime	10	provide information on the SPI clock frequency during runtime
9	Notice that the SPI frequency should be a multiple of sample	11	Notice that the SPI frequency should be a multiple of sample
10	frequency to ensure the precision.	12	frequency to ensure the precision.
11	if DFSDM input is SPI master	13
		14	if DFSDM input is SPI master:
		15
12	Reading SPI clkout frequency,	16	Reading SPI clkout frequency,
13	error on writing	17	error on writing
		18
14	If DFSDM input is SPI Slave:	19	If DFSDM input is SPI Slave:
		20
15	Reading returns value previously set.	21	Reading returns value previously set.
16	Writing value before starting conversions.	22	Writing value before starting conversions.

Documentation/ABI/testing/sysfs-bus-iio-distance-srf08+5−2

@@ -15,8 +15,11 @@ Description: · 14 unmodified lines
15	first object echoed in meters. Default value is 6.020.	15	first object echoed in meters. Default value is 6.020.
16	This setting limits the time the driver is waiting for a	16	This setting limits the time the driver is waiting for a
17	echo.	17	echo.
		18
18	Showing the range of available values is represented as the	19	Showing the range of available values is represented as the
19	minimum value, the step and the maximum value, all enclosed	20	minimum value, the step and the maximum value, all enclosed
20	in square brackets.	21	in square brackets.
21	Example:	22
22	[0.043 0.043 11.008]	23	Example::
		24
		25	[0.043 0.043 11.008]

Documentation/ABI/testing/sysfs-bus-iio-frequency-ad9523+2−0

@@ -8,7 +8,9 @@ KernelVersion: 3.4.0 · 7 unmodified lines
8	Contact: linux-iio@vger.kernel.org	8	Contact: linux-iio@vger.kernel.org
9	Description:	9	Description:
10	Reading returns either '1' or '0'.	10	Reading returns either '1' or '0'.
		11
11	'1' means that the clock in question is present.	12	'1' means that the clock in question is present.
		13
12	'0' means that the clock is missing.	14	'0' means that the clock is missing.
13		15
14	What: /sys/bus/iio/devices/iio:deviceX/pllY_locked	16	What: /sys/bus/iio/devices/iio:deviceX/pllY_locked

Documentation/ABI/testing/sysfs-bus-iio-frequency-adf4371+5−5

@@ -27,12 +27,12 @@ What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_name · 26 unmodified lines
27	KernelVersion:	27	KernelVersion:
28	Contact: linux-iio@vger.kernel.org	28	Contact: linux-iio@vger.kernel.org
29	Description:	29	Description:
30	Reading returns the datasheet name for channel Y:	30	Reading returns the datasheet name for channel Y::
31		31
32	out_altvoltage0_name: RF8x	32	out_altvoltage0_name: RF8x
33	out_altvoltage1_name: RFAUX8x	33	out_altvoltage1_name: RFAUX8x
34	out_altvoltage2_name: RF16x	34	out_altvoltage2_name: RF16x
35	out_altvoltage3_name: RF32x	35	out_altvoltage3_name: RF32x
36		36
37	What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_powerdown	37	What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_powerdown
38	KernelVersion:	38	KernelVersion:

Documentation/ABI/testing/sysfs-bus-iio-health-afe440x+8−4

@@ -6,10 +6,14 @@ Description: · 5 unmodified lines
6	Get measured values from the ADC for these stages. Y is the	6	Get measured values from the ADC for these stages. Y is the
7	specific stage number corresponding to datasheet stage names	7	specific stage number corresponding to datasheet stage names
8	as follows:	8	as follows:
9	1 -> LED2	9
10	2 -> ALED2/LED3	10	== ==========
11	3 -> LED1	11	1 LED2
12	4 -> ALED1/LED4	12	2 ALED2/LED3
		13	3 LED1
		14	4 ALED1/LED4
		15	== ==========
		16
13	Note that channels 5 and 6 represent LED2-ALED2 and LED1-ALED1	17	Note that channels 5 and 6 represent LED2-ALED2 and LED1-ALED1
14	respectively which simply helper channels containing the	18	respectively which simply helper channels containing the
15	calculated difference in the value of stage 1 - 2 and 3 - 4.	19	calculated difference in the value of stage 1 - 2 and 3 - 4.

Documentation/ABI/testing/sysfs-bus-iio-light-isl29018+4−2

@@ -15,5 +15,7 @@ Description: · 14 unmodified lines
15	Scheme 0 has wider dynamic range, Scheme 1 proximity detection	15	Scheme 0 has wider dynamic range, Scheme 1 proximity detection
16	is less affected by the ambient IR noise variation.	16	is less affected by the ambient IR noise variation.
17		17
18	0 Sensing IR from LED and ambient	18	== =============================================
19	1 Sensing IR from LED with ambient IR rejection	19	0 Sensing IR from LED and ambient
		20	1 Sensing IR from LED with ambient IR rejection
		21	== =============================================

Documentation/ABI/testing/sysfs-bus-iio-lptimer-stm32+17−12

@@ -17,9 +17,11 @@ KernelVersion: 4.13 · 16 unmodified lines
17	Contact: fabrice.gasnier@st.com	17	Contact: fabrice.gasnier@st.com
18	Description:	18	Description:
19	Configure the device counter quadrature modes:	19	Configure the device counter quadrature modes:
		20
20	- non-quadrature:	21	- non-quadrature:
21	Encoder IN1 input servers as the count input (up	22	Encoder IN1 input servers as the count input (up
22	direction).	23	direction).
		24
23	- quadrature:	25	- quadrature:
24	Encoder IN1 and IN2 inputs are mixed to get direction	26	Encoder IN1 and IN2 inputs are mixed to get direction
25	and count.	27	and count.
@@ -35,23 +37,26 @@ KernelVersion: 4.13 · 9 unmodified lines
35	Contact: fabrice.gasnier@st.com	37	Contact: fabrice.gasnier@st.com
36	Description:	38	Description:
37	Configure the device encoder/counter active edge:	39	Configure the device encoder/counter active edge:
		40
38	- rising-edge	41	- rising-edge
39	- falling-edge	42	- falling-edge
40	- both-edges	43	- both-edges
41		44
42	In non-quadrature mode, device counts up on active edge.	45	In non-quadrature mode, device counts up on active edge.
		46
43	In quadrature mode, encoder counting scenarios are as follows:	47	In quadrature mode, encoder counting scenarios are as follows:
44	----------------------------------------------------------------	48
		49	+---------+----------+--------------------+--------------------+
45	\| Active \| Level on \| IN1 signal \| IN2 signal \|	50	\| Active \| Level on \| IN1 signal \| IN2 signal \|
46	\| edge \| opposite \|------------------------------------------	51	\| edge \| opposite +----------+---------+----------+---------+
47	\| \| signal \| Rising \| Falling \| Rising \| Falling \|	52	\| \| signal \| Rising \| Falling \| Rising \| Falling \|
48	----------------------------------------------------------------	53	+---------+----------+----------+---------+----------+---------+
49	\| Rising \| High -> \| Down \| - \| Up \| - \|	54	\| Rising \| High -> \| Down \| - \| Up \| - \|
50	\| edge \| Low -> \| Up \| - \| Down \| - \|	55	\| edge \| Low -> \| Up \| - \| Down \| - \|
51	----------------------------------------------------------------	56	+---------+----------+----------+---------+----------+---------+
52	\| Falling \| High -> \| - \| Up \| - \| Down \|	57	\| Falling \| High -> \| - \| Up \| - \| Down \|
53	\| edge \| Low -> \| - \| Down \| - \| Up \|	58	\| edge \| Low -> \| - \| Down \| - \| Up \|
54	----------------------------------------------------------------	59	+---------+----------+----------+---------+----------+---------+
55	\| Both \| High -> \| Down \| Up \| Up \| Down \|	60	\| Both \| High -> \| Down \| Up \| Up \| Down \|
56	\| edges \| Low -> \| Up \| Down \| Down \| Up \|	61	\| edges \| Low -> \| Up \| Down \| Down \| Up \|
57	----------------------------------------------------------------	62	+---------+----------+----------+---------+----------+---------+

Documentation/ABI/testing/sysfs-bus-iio-magnetometer-hmc5843+12−7

@@ -5,11 +5,16 @@ Contact: linux-iio@vger.kernel.org · 4 unmodified lines
5	Description:	5	Description:
6	Current configuration and available configurations	6	Current configuration and available configurations
7	for the bias current.	7	for the bias current.
8	normal - Normal measurement configurations (default)	8
9	positivebias - Positive bias configuration	9	============ ============================================
10	negativebias - Negative bias configuration	10	normal Normal measurement configurations (default)
11	disabled - Only available on HMC5983. Disables magnetic	11	positivebias Positive bias configuration
		12	negativebias Negative bias configuration
		13	disabled Only available on HMC5983. Disables magnetic
12	sensor and enables temperature sensor.	14	sensor and enables temperature sensor.
13	Note: The effect of this configuration may vary	15	============ ============================================
14	according to the device. For exact documentation	16
15	check the device's datasheet.	17	Note:
		18	The effect of this configuration may vary
		19	according to the device. For exact documentation
		20	check the device's datasheet.

Documentation/ABI/testing/sysfs-bus-iio-temperature-max31856+13−6

@@ -5,9 +5,12 @@ Description: · 4 unmodified lines
5	Open-circuit fault. The detection of open-circuit faults,	5	Open-circuit fault. The detection of open-circuit faults,
6	such as those caused by broken thermocouple wires.	6	such as those caused by broken thermocouple wires.
7	Reading returns either '1' or '0'.	7	Reading returns either '1' or '0'.
8	'1' = An open circuit such as broken thermocouple wires	8
9	has been detected.	9	=== =======================================================
10	'0' = No open circuit or broken thermocouple wires are detected	10	'1' An open circuit such as broken thermocouple wires
		11	has been detected.
		12	'0' No open circuit or broken thermocouple wires are detected
		13	=== =======================================================
11		14
12	What: /sys/bus/iio/devices/iio:deviceX/fault_ovuv	15	What: /sys/bus/iio/devices/iio:deviceX/fault_ovuv
13	KernelVersion: 5.1	16	KernelVersion: 5.1
@@ -18,7 +21,11 @@ Description: · 4 unmodified lines
18	cables by integrated MOSFETs at the T+ and T- inputs, and the	21	cables by integrated MOSFETs at the T+ and T- inputs, and the
19	BIAS output. These MOSFETs turn off when the input voltage is	22	BIAS output. These MOSFETs turn off when the input voltage is
20	negative or greater than VDD.	23	negative or greater than VDD.
		24
21	Reading returns either '1' or '0'.	25	Reading returns either '1' or '0'.
22	'1' = The input voltage is negative or greater than VDD.	26
23	'0' = The input voltage is positive and less than VDD (normal	27	=== =======================================================
24	state).	28	'1' The input voltage is negative or greater than VDD.
		29	'0' The input voltage is positive and less than VDD (normal
		30	state).
		31	=== =======================================================

Documentation/ABI/testing/sysfs-bus-iio-timer-stm32+93−50

@@ -3,67 +3,85 @@ KernelVersion: 4.11 · 2 unmodified lines
3	Contact: benjamin.gaignard@st.com	3	Contact: benjamin.gaignard@st.com
4	Description:	4	Description:
5	Reading returns the list possible master modes which are:	5	Reading returns the list possible master modes which are:
6	- "reset" : The UG bit from the TIMx_EGR register is	6
		7
		8	- "reset"
		9	The UG bit from the TIMx_EGR register is
7	used as trigger output (TRGO).	10	used as trigger output (TRGO).
8	- "enable" : The Counter Enable signal CNT_EN is used	11	- "enable"
		12	The Counter Enable signal CNT_EN is used
9	as trigger output.	13	as trigger output.
10	- "update" : The update event is selected as trigger output.	14	- "update"
		15	The update event is selected as trigger output.
11	For instance a master timer can then be used	16	For instance a master timer can then be used
12	as a prescaler for a slave timer.	17	as a prescaler for a slave timer.
13	- "compare_pulse" : The trigger output send a positive pulse	18	- "compare_pulse"
14	when the CC1IF flag is to be set.	19	The trigger output send a positive pulse
15	- "OC1REF" : OC1REF signal is used as trigger output.	20	when the CC1IF flag is to be set.
16	- "OC2REF" : OC2REF signal is used as trigger output.	21	- "OC1REF"
17	- "OC3REF" : OC3REF signal is used as trigger output.	22	OC1REF signal is used as trigger output.
18	- "OC4REF" : OC4REF signal is used as trigger output.	23	- "OC2REF"
		24	OC2REF signal is used as trigger output.
		25	- "OC3REF"
		26	OC3REF signal is used as trigger output.
		27	- "OC4REF"
		28	OC4REF signal is used as trigger output.
		29
19	Additional modes (on TRGO2 only):	30	Additional modes (on TRGO2 only):
20	- "OC5REF" : OC5REF signal is used as trigger output.	31
21	- "OC6REF" : OC6REF signal is used as trigger output.	32	- "OC5REF"
		33	OC5REF signal is used as trigger output.
		34	- "OC6REF"
		35	OC6REF signal is used as trigger output.
22	- "compare_pulse_OC4REF":	36	- "compare_pulse_OC4REF":
23	OC4REF rising or falling edges generate pulses.	37	OC4REF rising or falling edges generate pulses.
24	- "compare_pulse_OC6REF":	38	- "compare_pulse_OC6REF":
25	OC6REF rising or falling edges generate pulses.	39	OC6REF rising or falling edges generate pulses.
26	- "compare_pulse_OC4REF_r_or_OC6REF_r":	40	- "compare_pulse_OC4REF_r_or_OC6REF_r":
27	OC4REF or OC6REF rising edges generate pulses.	41	OC4REF or OC6REF rising edges generate pulses.
28	- "compare_pulse_OC4REF_r_or_OC6REF_f":	42	- "compare_pulse_OC4REF_r_or_OC6REF_f":
29	OC4REF rising or OC6REF falling edges generate pulses.	43	OC4REF rising or OC6REF falling edges generate
		44	pulses.
30	- "compare_pulse_OC5REF_r_or_OC6REF_r":	45	- "compare_pulse_OC5REF_r_or_OC6REF_r":
31	OC5REF or OC6REF rising edges generate pulses.	46	OC5REF or OC6REF rising edges generate pulses.
32	- "compare_pulse_OC5REF_r_or_OC6REF_f":	47	- "compare_pulse_OC5REF_r_or_OC6REF_f":
33	OC5REF rising or OC6REF falling edges generate pulses.	48	OC5REF rising or OC6REF falling edges generate
34		49	pulses.
35	+-----------+ +-------------+ +---------+	50
36	\| Prescaler +-> \| Counter \| +-> \| Master \| TRGO(2)	51	::
37	+-----------+ +--+--------+-+ \|-> \| Control +-->	52
38	\| \| \|\| +---------+	53	+-----------+ +-------------+ +---------+
39	+--v--------+-+ OCxREF \|\| +---------+	54	\| Prescaler +-> \| Counter \| +-> \| Master \| TRGO(2)
40	\| Chx compare +----------> \| Output \| ChX	55	+-----------+ +--+--------+-+ \|-> \| Control +-->
41	+-----------+-+ \| \| Control +-->	56	\| \| \|\| +---------+
42	. \| \| +---------+	57	+--v--------+-+ OCxREF \|\| +---------+
43	. \| \| .	58	\| Chx compare +----------> \| Output \| ChX
44	+-----------v-+ OC6REF \| .	59	+-----------+-+ \| \| Control +-->
45	\| Ch6 compare +---------+>	60	. \| \| +---------+
46	+-------------+	61	. \| \| .
47		62	+-----------v-+ OC6REF \| .
48	Example with: "compare_pulse_OC4REF_r_or_OC6REF_r":	63	\| Ch6 compare +---------+>
49		64	+-------------+
50	X	65
51	X X	66	Example with: "compare_pulse_OC4REF_r_or_OC6REF_r"::
52	X . . X	67
53	X . . X	68	X
54	X . . X	69	X X
55	count X . . . . X	70	X . . X
56	. . . .	71	X . . X
57	. . . .	72	X . . X
58	+---------------+	73	count X . . . . X
59	OC4REF \| . . \|	74	. . . .
60	+-+ . . +-+	75	. . . .
61	. +---+ .	76	+---------------+
62	OC6REF . \| \| .	77	OC4REF \| . . \|
63	+-------+ +-------+	78	+-+ . . +-+
64	+-+ +-+	79	. +---+ .
65	TRGO2 \| \| \| \|	80	OC6REF . \| \| .
66	+-+ +---+ +---------+	81	+-------+ +-------+
		82	+-+ +-+
		83	TRGO2 \| \| \| \|
		84	+-+ +---+ +---------+
67		85
68	What: /sys/bus/iio/devices/triggerX/master_mode	86	What: /sys/bus/iio/devices/triggerX/master_mode
69	KernelVersion: 4.11	87	KernelVersion: 4.11
@@ -91,6 +109,30 @@ Description: · 21 unmodified lines
91	When counting down the counter start from preset value	109	When counting down the counter start from preset value
92	and fire event when reach 0.	110	and fire event when reach 0.
93		111
		112	What: /sys/bus/iio/devices/iio:deviceX/in_count_quadrature_mode_available
		113	KernelVersion: 4.12
		114	Contact: benjamin.gaignard@st.com
		115	Description:
		116	Reading returns the list possible quadrature modes.
		117
		118	What: /sys/bus/iio/devices/iio:deviceX/in_count0_quadrature_mode
		119	KernelVersion: 4.12
		120	Contact: benjamin.gaignard@st.com
		121	Description:
		122	Configure the device counter quadrature modes:
		123
		124	channel_A:
		125	Encoder A input servers as the count input and B as
		126	the UP/DOWN direction control input.
		127
		128	channel_B:
		129	Encoder B input serves as the count input and A as
		130	the UP/DOWN direction control input.
		131
		132	quadrature:
		133	Encoder A and B inputs are mixed to get direction
		134	and count with a scale of 0.25.
		135
94	What: /sys/bus/iio/devices/iio:deviceX/in_count_enable_mode_available	136	What: /sys/bus/iio/devices/iio:deviceX/in_count_enable_mode_available
95	KernelVersion: 4.12	137	KernelVersion: 4.12
96	Contact: benjamin.gaignard@st.com	138	Contact: benjamin.gaignard@st.com
@@ -104,6 +146,7 @@ Description: · 7 unmodified lines
104	Configure the device counter enable modes, in all case	146	Configure the device counter enable modes, in all case
105	counting direction is set by in_count0_count_direction	147	counting direction is set by in_count0_count_direction
106	attribute and the counter is clocked by the internal clock.	148	attribute and the counter is clocked by the internal clock.
		149
107	always:	150	always:
108	Counter is always ON.	151	Counter is always ON.
109		152

Documentation/ABI/testing/sysfs-bus-intel_th-devices-gth+7−4

@@ -10,10 +10,13 @@ Date: June 2015 · 9 unmodified lines
10	KernelVersion: 4.3	10	KernelVersion: 4.3
11	Contact: Alexander Shishkin <alexander.shishkin@linux.intel.com>	11	Contact: Alexander Shishkin <alexander.shishkin@linux.intel.com>
12	Description: (RO) Output port type:	12	Description: (RO) Output port type:
13	0: not present,	13
14	1: MSU (Memory Storage Unit)	14	== =========================
15	2: CTP (Common Trace Port)	15	0 not present,
16	4: PTI (MIPI PTI).	16	1 MSU (Memory Storage Unit)
		17	2 CTP (Common Trace Port)
		18	4 PTI (MIPI PTI).
		19	== =========================
17		20
18	What: /sys/bus/intel_th/devices/<intel_th_id>-gth/outputs/[0-7]_drop	21	What: /sys/bus/intel_th/devices/<intel_th_id>-gth/outputs/[0-7]_drop
19	Date: June 2015	22	Date: June 2015

Documentation/ABI/testing/sysfs-bus-intel_th-devices-msc+4−0

Documentation/ABI/testing/sysfs-bus-most+4−2

@@ -235,7 +235,8 @@ KernelVersion: 4.15 · 234 unmodified lines
235	Contact: Christian Gromm <christian.gromm@microchip.com>	235	Contact: Christian Gromm <christian.gromm@microchip.com>
236	Description:	236	Description:
237	This is to read back the configured direction of the channel.	237	This is to read back the configured direction of the channel.
238	The following strings will be accepted:	238	The following strings will be accepted::
		239
239	'tx',	240	'tx',
240	'rx'	241	'rx'
241	Users:	242	Users:
@@ -246,7 +247,8 @@ KernelVersion: 4.15 · 4 unmodified lines
246	Contact: Christian Gromm <christian.gromm@microchip.com>	247	Contact: Christian Gromm <christian.gromm@microchip.com>
247	Description:	248	Description:
248	This is to read back the configured data type of the channel.	249	This is to read back the configured data type of the channel.
249	The following strings will be accepted:	250	The following strings will be accepted::
		251
250	'control',	252	'control',
251	'async',	253	'async',
252	'sync',	254	'sync',

Documentation/ABI/testing/sysfs-bus-moxtet-devices+3−3

@@ -2,16 +2,16 @@ What: /sys/bus/moxtet/devices/moxtet-<name>.<addr>/module_description · 1 unmodified line
2	Date: March 2019	2	Date: March 2019
3	KernelVersion: 5.3	3	KernelVersion: 5.3
4	Contact: Marek Behún <marek.behun@nic.cz>	4	Contact: Marek Behún <marek.behun@nic.cz>
5	Description: (R) Moxtet module description. Format: string	5	Description: (Read) Moxtet module description. Format: string
6		6
7	What: /sys/bus/moxtet/devices/moxtet-<name>.<addr>/module_id	7	What: /sys/bus/moxtet/devices/moxtet-<name>.<addr>/module_id
8	Date: March 2019	8	Date: March 2019
9	KernelVersion: 5.3	9	KernelVersion: 5.3
10	Contact: Marek Behún <marek.behun@nic.cz>	10	Contact: Marek Behún <marek.behun@nic.cz>
11	Description: (R) Moxtet module ID. Format: %x	11	Description: (Read) Moxtet module ID. Format: %x
12		12
13	What: /sys/bus/moxtet/devices/moxtet-<name>.<addr>/module_name	13	What: /sys/bus/moxtet/devices/moxtet-<name>.<addr>/module_name
14	Date: March 2019	14	Date: March 2019
15	KernelVersion: 5.3	15	KernelVersion: 5.3
16	Contact: Marek Behún <marek.behun@nic.cz>	16	Contact: Marek Behún <marek.behun@nic.cz>
17	Description: (R) Moxtet module name. Format: string	17	Description: (Read) Moxtet module name. Format: string

Documentation/ABI/testing/sysfs-bus-nfit+1−1

@@ -1,4 +1,4 @@
1	For all of the nmem device attributes under nfit/*, see the 'NVDIMM Firmware	1	For all of the nmem device attributes under ``nfit/*``, see the 'NVDIMM Firmware
2	Interface Table (NFIT)' section in the ACPI specification	2	Interface Table (NFIT)' section in the ACPI specification
3	(http://www.uefi.org/specifications) for more details.	3	(http://www.uefi.org/specifications) for more details.
4		4

Documentation/ABI/testing/sysfs-bus-nvdimm+6−0

@@ -1,2 +1,8 @@
		1	What: nvdimm
		2	Date: July 2020
		3	KernelVersion: 5.8
		4	Contact: Dan Williams <dan.j.williams@intel.com>
		5	Description:
		6
1	The libnvdimm sub-system implements a common sysfs interface for	7	The libnvdimm sub-system implements a common sysfs interface for
2	platform nvdimm resources. See Documentation/driver-api/nvdimm/.	8	platform nvdimm resources. See Documentation/driver-api/nvdimm/.

Documentation/ABI/testing/sysfs-bus-papr-pmem+15−8

 		at 'Documentation/powerpc/papr_hcalls.rst' . Below are
 		the flags reported in this sysfs file:
-		* "not_armed"	: Indicates that NVDIMM contents will not
+		* "not_armed"
+				  Indicates that NVDIMM contents will not
 				  survive a power cycle.
-		* "flush_fail"	: Indicates that NVDIMM contents
+		* "flush_fail"
+				  Indicates that NVDIMM contents
 				  couldn't be flushed during last
 				  shut-down event.
-		* "restore_fail": Indicates that NVDIMM contents
+		* "restore_fail"
+				  Indicates that NVDIMM contents
 				  couldn't be restored during NVDIMM
 				  initialization.
-		* "encrypted"	: NVDIMM contents are encrypted.
+		* "encrypted"
-		* "smart_notify": There is health event for the NVDIMM.
+				  NVDIMM contents are encrypted.
-		* "scrubbed"	: Indicating that contents of the
+		* "smart_notify"
+				  There is health event for the NVDIMM.
+		* "scrubbed"
+				  Indicating that contents of the
 				  NVDIMM have been scrubbed.
-		* "locked"	: Indicating that NVDIMM contents cant
+		* "locked"
+				  Indicating that NVDIMM contents cant
 				  be modified until next power cycle.
 What:		/sys/bus/nd/devices/nmemX/papr/perf_stats
 		* "MedWDur " : Media Write Duration
 		* "CchRHCnt" : Cache Read Hit Count
 		* "CchWHCnt" : Cache Write Hit Count
 		* "FastWCnt" : Fast Write Count

Documentation/ABI/testing/sysfs-bus-pci+14−8

@@ -7,8 +7,10 @@ Description: · 6 unmodified lines
7	this location. This is useful for overriding default	7	this location. This is useful for overriding default
8	bindings. The format for the location is: DDDD:BB:DD.F.	8	bindings. The format for the location is: DDDD:BB:DD.F.
9	That is Domain:Bus:Device.Function and is the same as	9	That is Domain:Bus:Device.Function and is the same as
10	found in /sys/bus/pci/devices/. For example:	10	found in /sys/bus/pci/devices/. For example::
11	# echo 0000:00:19.0 > /sys/bus/pci/drivers/foo/bind	11
		12	# echo 0000:00:19.0 > /sys/bus/pci/drivers/foo/bind
		13
12	(Note: kernels before 2.6.28 may require echo -n).	14	(Note: kernels before 2.6.28 may require echo -n).
13		15
14	What: /sys/bus/pci/drivers/.../unbind	16	What: /sys/bus/pci/drivers/.../unbind
@@ -20,8 +22,10 @@ Description: · 5 unmodified lines
20	this location. This may be useful when overriding default	22	this location. This may be useful when overriding default
21	bindings. The format for the location is: DDDD:BB:DD.F.	23	bindings. The format for the location is: DDDD:BB:DD.F.
22	That is Domain:Bus:Device.Function and is the same as	24	That is Domain:Bus:Device.Function and is the same as
23	found in /sys/bus/pci/devices/. For example:	25	found in /sys/bus/pci/devices/. For example::
24	# echo 0000:00:19.0 > /sys/bus/pci/drivers/foo/unbind	26
		27	# echo 0000:00:19.0 > /sys/bus/pci/drivers/foo/unbind
		28
25	(Note: kernels before 2.6.28 may require echo -n).	29	(Note: kernels before 2.6.28 may require echo -n).
26		30
27	What: /sys/bus/pci/drivers/.../new_id	31	What: /sys/bus/pci/drivers/.../new_id
@@ -38,8 +42,9 @@ Description: · 10 unmodified lines
38	Class, Class Mask, and Private Driver Data. The Vendor ID	42	Class, Class Mask, and Private Driver Data. The Vendor ID
39	and Device ID fields are required, the rest are optional.	43	and Device ID fields are required, the rest are optional.
40	Upon successfully adding an ID, the driver will probe	44	Upon successfully adding an ID, the driver will probe
41	for the device and attempt to bind to it. For example:	45	for the device and attempt to bind to it. For example::
42	# echo "8086 10f5" > /sys/bus/pci/drivers/foo/new_id	46
		47	# echo "8086 10f5" > /sys/bus/pci/drivers/foo/new_id
43		48
44	What: /sys/bus/pci/drivers/.../remove_id	49	What: /sys/bus/pci/drivers/.../remove_id
45	Date: February 2009	50	Date: February 2009
@@ -54,8 +59,9 @@ Description: · 8 unmodified lines
54	required, the rest are optional. After successfully	59	required, the rest are optional. After successfully
55	removing an ID, the driver will no longer support the	60	removing an ID, the driver will no longer support the
56	device. This is useful to ensure auto probing won't	61	device. This is useful to ensure auto probing won't
57	match the driver to the device. For example:	62	match the driver to the device. For example::
58	# echo "8086 10f5" > /sys/bus/pci/drivers/foo/remove_id	63
		64	# echo "8086 10f5" > /sys/bus/pci/drivers/foo/remove_id
59		65
60	What: /sys/bus/pci/rescan	66	What: /sys/bus/pci/rescan
61	Date: January 2009	67	Date: January 2009

Documentation/ABI/testing/sysfs-bus-pci-devices-aer_stats+58−61

@@ -1,6 +1,6 @@
1	==========================
2	PCIe Device AER statistics	1	PCIe Device AER statistics
3	==========================	2	--------------------------
		3
4	These attributes show up under all the devices that are AER capable. These	4	These attributes show up under all the devices that are AER capable. These
5	statistical counters indicate the errors "as seen/reported by the device".	5	statistical counters indicate the errors "as seen/reported by the device".
6	Note that this may mean that if an endpoint is causing problems, the AER	6	Note that this may mean that if an endpoint is causing problems, the AER
@@ -17,19 +17,18 @@ Description: List of correctable errors seen and reported by this · 10 unmodified lines
17	PCI device using ERR_COR. Note that since multiple errors may	17	PCI device using ERR_COR. Note that since multiple errors may
18	be reported using a single ERR_COR message, thus	18	be reported using a single ERR_COR message, thus
19	TOTAL_ERR_COR at the end of the file may not match the actual	19	TOTAL_ERR_COR at the end of the file may not match the actual
20	total of all the errors in the file. Sample output:	20	total of all the errors in the file. Sample output::
21	-------------------------------------------------------------------------	21
22	localhost /sys/devices/pci0000:00/0000:00:1c.0 # cat aer_dev_correctable	22	localhost /sys/devices/pci0000:00/0000:00:1c.0 # cat aer_dev_correctable
23	Receiver Error 2	23	Receiver Error 2
24	Bad TLP 0	24	Bad TLP 0
25	Bad DLLP 0	25	Bad DLLP 0
26	RELAY_NUM Rollover 0	26	RELAY_NUM Rollover 0
27	Replay Timer Timeout 0	27	Replay Timer Timeout 0
28	Advisory Non-Fatal 0	28	Advisory Non-Fatal 0
29	Corrected Internal Error 0	29	Corrected Internal Error 0
30	Header Log Overflow 0	30	Header Log Overflow 0
31	TOTAL_ERR_COR 2	31	TOTAL_ERR_COR 2
32	-------------------------------------------------------------------------
33		32
34	What: /sys/bus/pci/devices/<dev>/aer_dev_fatal	33	What: /sys/bus/pci/devices/<dev>/aer_dev_fatal
35	Date: July 2018	34	Date: July 2018
@@ -39,28 +38,27 @@ Description: List of uncorrectable fatal errors seen and reported by this · 3 unmodified lines
39	PCI device using ERR_FATAL. Note that since multiple errors may	38	PCI device using ERR_FATAL. Note that since multiple errors may
40	be reported using a single ERR_FATAL message, thus	39	be reported using a single ERR_FATAL message, thus
41	TOTAL_ERR_FATAL at the end of the file may not match the actual	40	TOTAL_ERR_FATAL at the end of the file may not match the actual
42	total of all the errors in the file. Sample output:	41	total of all the errors in the file. Sample output::
43	-------------------------------------------------------------------------	42
44	localhost /sys/devices/pci0000:00/0000:00:1c.0 # cat aer_dev_fatal	43	localhost /sys/devices/pci0000:00/0000:00:1c.0 # cat aer_dev_fatal
45	Undefined 0	44	Undefined 0
46	Data Link Protocol 0	45	Data Link Protocol 0
47	Surprise Down Error 0	46	Surprise Down Error 0
48	Poisoned TLP 0	47	Poisoned TLP 0
49	Flow Control Protocol 0	48	Flow Control Protocol 0
50	Completion Timeout 0	49	Completion Timeout 0
51	Completer Abort 0	50	Completer Abort 0
52	Unexpected Completion 0	51	Unexpected Completion 0
53	Receiver Overflow 0	52	Receiver Overflow 0
54	Malformed TLP 0	53	Malformed TLP 0
55	ECRC 0	54	ECRC 0
56	Unsupported Request 0	55	Unsupported Request 0
57	ACS Violation 0	56	ACS Violation 0
58	Uncorrectable Internal Error 0	57	Uncorrectable Internal Error 0
59	MC Blocked TLP 0	58	MC Blocked TLP 0
60	AtomicOp Egress Blocked 0	59	AtomicOp Egress Blocked 0
61	TLP Prefix Blocked Error 0	60	TLP Prefix Blocked Error 0
62	TOTAL_ERR_FATAL 0	61	TOTAL_ERR_FATAL 0
63	-------------------------------------------------------------------------
64		62
65	What: /sys/bus/pci/devices/<dev>/aer_dev_nonfatal	63	What: /sys/bus/pci/devices/<dev>/aer_dev_nonfatal
66	Date: July 2018	64	Date: July 2018
@@ -70,32 +68,31 @@ Description: List of uncorrectable nonfatal errors seen and reported by this · 3 unmodified lines
70	PCI device using ERR_NONFATAL. Note that since multiple errors	68	PCI device using ERR_NONFATAL. Note that since multiple errors
71	may be reported using a single ERR_FATAL message, thus	69	may be reported using a single ERR_FATAL message, thus
72	TOTAL_ERR_NONFATAL at the end of the file may not match the	70	TOTAL_ERR_NONFATAL at the end of the file may not match the
73	actual total of all the errors in the file. Sample output:	71	actual total of all the errors in the file. Sample output::
74	-------------------------------------------------------------------------	72
75	localhost /sys/devices/pci0000:00/0000:00:1c.0 # cat aer_dev_nonfatal	73	localhost /sys/devices/pci0000:00/0000:00:1c.0 # cat aer_dev_nonfatal
76	Undefined 0	74	Undefined 0
77	Data Link Protocol 0	75	Data Link Protocol 0
78	Surprise Down Error 0	76	Surprise Down Error 0
79	Poisoned TLP 0	77	Poisoned TLP 0
80	Flow Control Protocol 0	78	Flow Control Protocol 0
81	Completion Timeout 0	79	Completion Timeout 0
82	Completer Abort 0	80	Completer Abort 0
83	Unexpected Completion 0	81	Unexpected Completion 0
84	Receiver Overflow 0	82	Receiver Overflow 0
85	Malformed TLP 0	83	Malformed TLP 0
86	ECRC 0	84	ECRC 0
87	Unsupported Request 0	85	Unsupported Request 0
88	ACS Violation 0	86	ACS Violation 0
89	Uncorrectable Internal Error 0	87	Uncorrectable Internal Error 0
90	MC Blocked TLP 0	88	MC Blocked TLP 0
91	AtomicOp Egress Blocked 0	89	AtomicOp Egress Blocked 0
92	TLP Prefix Blocked Error 0	90	TLP Prefix Blocked Error 0
93	TOTAL_ERR_NONFATAL 0	91	TOTAL_ERR_NONFATAL 0
94	-------------------------------------------------------------------------
95		92
96	============================
97	PCIe Rootport AER statistics	93	PCIe Rootport AER statistics
98	============================	94	----------------------------
		95
99	These attributes show up under only the rootports (or root complex event	96	These attributes show up under only the rootports (or root complex event
100	collectors) that are AER capable. These indicate the number of error messages as	97	collectors) that are AER capable. These indicate the number of error messages as
101	"reported to" the rootport. Please note that the rootports also transmit	98	"reported to" the rootport. Please note that the rootports also transmit

Documentation/ABI/testing/sysfs-bus-pci-devices-catpt+1−0

@@ -4,6 +4,7 @@ Contact: Cezary Rojewski <cezary.rojewski@intel.com> · 3 unmodified lines
4	Description:	4	Description:
5	Version of AudioDSP firmware ASoC catpt driver is	5	Version of AudioDSP firmware ASoC catpt driver is
6	communicating with.	6	communicating with.
		7
7	Format: %d.%d.%d.%d, type:major:minor:build.	8	Format: %d.%d.%d.%d, type:major:minor:build.
8		9
9	What: /sys/devices/pci0000:00/<dev>/fw_info	10	What: /sys/devices/pci0000:00/<dev>/fw_info

Documentation/ABI/testing/sysfs-bus-pci-drivers-ehci_hcd+2−2

@@ -21,11 +21,11 @@ Description: · 20 unmodified lines
21	number returns the port to normal operation.	21	number returns the port to normal operation.
22		22
23	For example: To force the high-speed device attached to	23	For example: To force the high-speed device attached to
24	port 4 on bus 2 to run at full speed:	24	port 4 on bus 2 to run at full speed::
25		25
26	echo 4 >/sys/bus/usb/devices/usb2/../companion	26	echo 4 >/sys/bus/usb/devices/usb2/../companion
27		27
28	To return the port to high-speed operation:	28	To return the port to high-speed operation::
29		29
30	echo -4 >/sys/bus/usb/devices/usb2/../companion	30	echo -4 >/sys/bus/usb/devices/usb2/../companion
31		31

Documentation/ABI/testing/sysfs-bus-rapidio+13−10

@@ -4,24 +4,27 @@ Description: · 3 unmodified lines
4	an individual subdirectory with the following name format of	4	an individual subdirectory with the following name format of
5	device_name "nn:d:iiii", where:	5	device_name "nn:d:iiii", where:
6		6
7	nn - two-digit hexadecimal ID of RapidIO network where the	7	==== ========================================================
		8	nn two-digit hexadecimal ID of RapidIO network where the
8	device resides	9	device resides
9	d - device type: 'e' - for endpoint or 's' - for switch	10	d device type: 'e' - for endpoint or 's' - for switch
10	iiii - four-digit device destID for endpoints, or switchID for	11	iiii four-digit device destID for endpoints, or switchID for
11	switches	12	switches
		13	==== ========================================================
12		14
13	For example, below is a list of device directories that	15	For example, below is a list of device directories that
14	represents a typical RapidIO network with one switch, one host,	16	represents a typical RapidIO network with one switch, one host,
15	and two agent endpoints, as it is seen by the enumerating host	17	and two agent endpoints, as it is seen by the enumerating host
16	(with destID = 1):	18	(with destID = 1)::
17		19
18	/sys/bus/rapidio/devices/00:e:0000	20	/sys/bus/rapidio/devices/00:e:0000
19	/sys/bus/rapidio/devices/00:e:0002	21	/sys/bus/rapidio/devices/00:e:0002
20	/sys/bus/rapidio/devices/00:s:0001	22	/sys/bus/rapidio/devices/00:s:0001
21		23
22	NOTE: An enumerating or discovering endpoint does not create a	24	NOTE:
23	sysfs entry for itself, this is why an endpoint with destID=1 is	25	An enumerating or discovering endpoint does not create a
24	not shown in the list.	26	sysfs entry for itself, this is why an endpoint with destID=1
		27	is not shown in the list.
25		28
26	Attributes Common for All RapidIO Devices	29	Attributes Common for All RapidIO Devices
27	-----------------------------------------	30	-----------------------------------------

Documentation/ABI/testing/sysfs-bus-rbd+24−13

@@ -7,6 +7,8 @@ Description: · 6 unmodified lines
7		7
8	Usage: <mon ip addr> <options> <pool name> <rbd image name> [<snap name>]	8	Usage: <mon ip addr> <options> <pool name> <rbd image name> [<snap name>]
9		9
		10	Example::
		11
10	$ echo "192.168.0.1 name=admin rbd foo" > /sys/bus/rbd/add	12	$ echo "192.168.0.1 name=admin rbd foo" > /sys/bus/rbd/add
11		13
12	The snapshot name can be "-" or omitted to map the image	14	The snapshot name can be "-" or omitted to map the image
@@ -23,6 +25,8 @@ Description: · 10 unmodified lines
23		25
24	Usage: <dev-id> [force]	26	Usage: <dev-id> [force]
25		27
		28	Example::
		29
26	$ echo 2 > /sys/bus/rbd/remove	30	$ echo 2 > /sys/bus/rbd/remove
27		31
28	Optional "force" argument which when passed will wait for	32	Optional "force" argument which when passed will wait for
@@ -80,26 +84,29 @@ Date: Oct, 2010 · 51 unmodified lines
80	KernelVersion: v2.6.37	84	KernelVersion: v2.6.37
81	Contact: Sage Weil <sage@newdream.net>	85	Contact: Sage Weil <sage@newdream.net>
82	Description:	86	Description:
83	size: (RO) The size (in bytes) of the mapped block	87
		88	============== ================================================
		89	size (RO) The size (in bytes) of the mapped block
84	device.	90	device.
85		91
86	major: (RO) The block device major number.	92	major (RO) The block device major number.
87		93
88	client_id: (RO) The ceph unique client id that was assigned	94	client_id (RO) The ceph unique client id that was assigned
89	for this specific session.	95	for this specific session.
90		96
91	pool: (RO) The name of the storage pool where this rbd	97	pool (RO) The name of the storage pool where this rbd
92	image resides. An rbd image name is unique	98	image resides. An rbd image name is unique
93	within its pool.	99	within its pool.
94		100
95	name: (RO) The name of the rbd image.	101	name (RO) The name of the rbd image.
96		102
97	refresh: (WO) Writing to this file will reread the image	103	refresh (WO) Writing to this file will reread the image
98	header data and set all relevant data structures	104	header data and set all relevant data structures
99	accordingly.	105	accordingly.
100		106
101	current_snap: (RO) The current snapshot for which the device	107	current_snap (RO) The current snapshot for which the device
102	is mapped.	108	is mapped.
		109	============== ================================================
103		110
104		111
105	What: /sys/bus/rbd/devices/<dev-id>/pool_id	112	What: /sys/bus/rbd/devices/<dev-id>/pool_id
@@ -117,11 +124,13 @@ Date: Oct, 2012 · 11 unmodified lines
117	KernelVersion: v3.7	124	KernelVersion: v3.7
118	Contact: Sage Weil <sage@newdream.net>	125	Contact: Sage Weil <sage@newdream.net>
119	Description:	126	Description:
120	image_id: (RO) The unique id for the rbd image. (For rbd	127	========= ===============================================
		128	image_id (RO) The unique id for the rbd image. (For rbd
121	image format 1 this is empty.)	129	image format 1 this is empty.)
122		130
123	features: (RO) A hexadecimal encoding of the feature bits	131	features (RO) A hexadecimal encoding of the feature bits
124	for this image.	132	for this image.
		133	========= ===============================================
125		134
126		135
127	What: /sys/bus/rbd/devices/<dev-id>/parent	136	What: /sys/bus/rbd/devices/<dev-id>/parent
@@ -149,14 +158,16 @@ Date: Aug, 2016 · 21 unmodified lines
149	KernelVersion: v4.9	158	KernelVersion: v4.9
150	Contact: Sage Weil <sage@newdream.net>	159	Contact: Sage Weil <sage@newdream.net>
151	Description:	160	Description:
152	snap_id: (RO) The current snapshot's id.	161	============ ================================================
		162	snap_id (RO) The current snapshot's id.
153		163
154	config_info: (RO) The string written into	164	config_info (RO) The string written into
155	/sys/bus/rbd/add{,_single_major}.	165	/sys/bus/rbd/add{,_single_major}.
156		166
157	cluster_fsid: (RO) The ceph cluster UUID.	167	cluster_fsid (RO) The ceph cluster UUID.
158		168
159	client_addr: (RO) The ceph unique client	169	client_addr (RO) The ceph unique client
160	entity_addr_t (address + nonce). The format is	170	entity_addr_t (address + nonce). The format is
161	<address>:<port>/<nonce>: '1.2.3.4:1234/5678' or	171	<address>:<port>/<nonce>: '1.2.3.4:1234/5678' or
162	'[1:2:3:4:5:6:7:8]:1234/5678'.	172	'[1:2:3:4:5:6:7:8]:1234/5678'.
		173	============ ================================================

Documentation/ABI/testing/sysfs-bus-siox+3−0

@@ -8,6 +8,7 @@ Description: · 7 unmodified lines
8	When the file contains a "1" the bus is operated and periodically	8	When the file contains a "1" the bus is operated and periodically
9	does a push-pull cycle to write and read data from the	9	does a push-pull cycle to write and read data from the
10	connected devices.	10	connected devices.
		11
11	When writing a "0" or "1" the bus moves to the described state.	12	When writing a "0" or "1" the bus moves to the described state.
12		13
13	What: /sys/bus/siox/devices/siox-X/device_add	14	What: /sys/bus/siox/devices/siox-X/device_add
@@ -21,8 +22,10 @@ Description: · 7 unmodified lines
21	to add a new device dynamically. <type> is the name that is used to match	22	to add a new device dynamically. <type> is the name that is used to match
22	to a driver (similar to the platform bus). <inbytes> and <outbytes> define	23	to a driver (similar to the platform bus). <inbytes> and <outbytes> define
23	the length of the input and output shift register in bytes respectively.	24	the length of the input and output shift register in bytes respectively.
		25
24	<statustype> defines the 4 bit device type that is check to identify connection	26	<statustype> defines the 4 bit device type that is check to identify connection
25	problems.	27	problems.
		28
26	The new device is added to the end of the existing chain.	29	The new device is added to the end of the existing chain.
27		30
28	What: /sys/bus/siox/devices/siox-X/device_remove	31	What: /sys/bus/siox/devices/siox-X/device_remove

Documentation/ABI/testing/sysfs-bus-thunderbolt+35−23

@@ -37,16 +37,18 @@ Contact: thunderbolt-software@lists.01.org · 36 unmodified lines
37	Description: This attribute holds current Thunderbolt security level	37	Description: This attribute holds current Thunderbolt security level
38	set by the system BIOS. Possible values are:	38	set by the system BIOS. Possible values are:
39		39
40	none: All devices are automatically authorized	40	======= ==================================================
41	user: Devices are only authorized based on writing	41	none All devices are automatically authorized
42	appropriate value to the authorized attribute	42	user Devices are only authorized based on writing
43	secure: Require devices that support secure connect at	43	appropriate value to the authorized attribute
44	minimum. User needs to authorize each device.	44	secure Require devices that support secure connect at
45	dponly: Automatically tunnel Display port (and USB). No	45	minimum. User needs to authorize each device.
46	PCIe tunnels are created.	46	dponly Automatically tunnel Display port (and USB). No
47	usbonly: Automatically tunnel USB controller of the	47	PCIe tunnels are created.
		48	usbonly Automatically tunnel USB controller of the
48	connected Thunderbolt dock (and Display Port). All	49	connected Thunderbolt dock (and Display Port). All
49	PCIe links downstream of the dock are removed.	50	PCIe links downstream of the dock are removed.
		51	======= ==================================================
50		52
51	What: /sys/bus/thunderbolt/devices/.../authorized	53	What: /sys/bus/thunderbolt/devices/.../authorized
52	Date: Sep 2017	54	Date: Sep 2017
@@ -61,17 +63,23 @@ Description: This attribute is used to authorize Thunderbolt devices · 8 unmodified lines
61	yet authorized.	63	yet authorized.
62		64
63	Possible values are supported:	65	Possible values are supported:
64	1: The device will be authorized and connected	66
		67	== ===========================================
		68	1 The device will be authorized and connected
		69	== ===========================================
65		70
66	When key attribute contains 32 byte hex string the possible	71	When key attribute contains 32 byte hex string the possible
67	values are:	72	values are:
68	1: The 32 byte hex string is added to the device NVM and	73
69	the device is authorized.	74	== ========================================================
70	2: Send a challenge based on the 32 byte hex string. If the	75	1 The 32 byte hex string is added to the device NVM and
71	challenge response from device is valid, the device is	76	the device is authorized.
72	authorized. In case of failure errno will be ENOKEY if	77	2 Send a challenge based on the 32 byte hex string. If the
73	the device did not contain a key at all, and	78	challenge response from device is valid, the device is
74	EKEYREJECTED if the challenge response did not match.	79	authorized. In case of failure errno will be ENOKEY if
		80	the device did not contain a key at all, and
		81	EKEYREJECTED if the challenge response did not match.
		82	== ========================================================
75		83
76	What: /sys/bus/thunderbolt/devices/.../boot	84	What: /sys/bus/thunderbolt/devices/.../boot
77	Date: Jun 2018	85	Date: Jun 2018
@@ -185,10 +193,11 @@ Description: When new NVM image is written to the non-active NVM · 107 unmodified lines
185	verification fails an error code is returned instead.	193	verification fails an error code is returned instead.
186		194
187	This file will accept writing values "1" or "2"	195	This file will accept writing values "1" or "2"
		196
188	- Writing "1" will flush the image to the storage	197	- Writing "1" will flush the image to the storage
189	area and authenticate the image in one action.	198	area and authenticate the image in one action.
190	- Writing "2" will run some basic validation on the image	199	- Writing "2" will run some basic validation on the image
191	and flush it to the storage area.	200	and flush it to the storage area.
192		201
193	When read holds status of the last authentication	202	When read holds status of the last authentication
194	operation if an error occurred during the process. This	203	operation if an error occurred during the process. This
@@ -205,9 +214,11 @@ Description: This contains name of the property directory the XDomain · 10 unmodified lines
205	question. Following directories are already reserved by	214	question. Following directories are already reserved by
206	the Apple XDomain specification:	215	the Apple XDomain specification:
207		216
208	network: IP/ethernet over Thunderbolt	217	======== ===============================================
209	targetdm: Target disk mode protocol over Thunderbolt	218	network IP/ethernet over Thunderbolt
210	extdisp: External display mode protocol over Thunderbolt	219	targetdm Target disk mode protocol over Thunderbolt
		220	extdisp External display mode protocol over Thunderbolt
		221	======== ===============================================
211		222
212	What: /sys/bus/thunderbolt/devices/<xdomain>.<service>/modalias	223	What: /sys/bus/thunderbolt/devices/<xdomain>.<service>/modalias
213	Date: Jan 2018	224	Date: Jan 2018
@@ -285,7 +296,8 @@ Description: For supported devices, automatically authenticate the new Thunderbo · 71 unmodified lines
285	image when the device is disconnected from the host system.	296	image when the device is disconnected from the host system.
286		297
287	This file will accept writing values "1" or "2"	298	This file will accept writing values "1" or "2"
		299
288	- Writing "1" will flush the image to the storage	300	- Writing "1" will flush the image to the storage
289	area and prepare the device for authentication on disconnect.	301	area and prepare the device for authentication on disconnect.
290	- Writing "2" will run some basic validation on the image	302	- Writing "2" will run some basic validation on the image
291	and flush it to the storage area.	303	and flush it to the storage area.

Documentation/ABI/testing/sysfs-bus-usb+19−13

@@ -9,6 +9,7 @@ Description: · 8 unmodified lines
9	by writing INTERFACE to /sys/bus/usb/drivers_probe	9	by writing INTERFACE to /sys/bus/usb/drivers_probe
10	This allows to avoid side-effects with drivers	10	This allows to avoid side-effects with drivers
11	that need multiple interfaces.	11	that need multiple interfaces.
		12
12	A deauthorized interface cannot be probed or claimed.	13	A deauthorized interface cannot be probed or claimed.
13		14
14	What: /sys/bus/usb/devices/usbX/interface_authorized_default	15	What: /sys/bus/usb/devices/usbX/interface_authorized_default
@@ -72,24 +73,27 @@ Description: · 57 unmodified lines
72	table at compile time. The format for the device ID is:	73	table at compile time. The format for the device ID is:
73	idVendor idProduct bInterfaceClass RefIdVendor RefIdProduct	74	idVendor idProduct bInterfaceClass RefIdVendor RefIdProduct
74	The vendor ID and device ID fields are required, the	75	The vendor ID and device ID fields are required, the
75	rest is optional. The Ref* tuple can be used to tell the	76	rest is optional. The `Ref*` tuple can be used to tell the
76	driver to use the same driver_data for the new device as	77	driver to use the same driver_data for the new device as
77	it is used for the reference device.	78	it is used for the reference device.
78	Upon successfully adding an ID, the driver will probe	79	Upon successfully adding an ID, the driver will probe
79	for the device and attempt to bind to it. For example:	80	for the device and attempt to bind to it. For example::
80	# echo "8086 10f5" > /sys/bus/usb/drivers/foo/new_id	81
		82	# echo "8086 10f5" > /sys/bus/usb/drivers/foo/new_id
81		83
82	Here add a new device (0458:7045) using driver_data from	84	Here add a new device (0458:7045) using driver_data from
83	an already supported device (0458:704c):	85	an already supported device (0458:704c)::
84	# echo "0458 7045 0 0458 704c" > /sys/bus/usb/drivers/foo/new_id	86
		87	# echo "0458 7045 0 0458 704c" > /sys/bus/usb/drivers/foo/new_id
85		88
86	Reading from this file will list all dynamically added	89	Reading from this file will list all dynamically added
87	device IDs in the same format, with one entry per	90	device IDs in the same format, with one entry per
88	line. For example:	91	line. For example::
89	# cat /sys/bus/usb/drivers/foo/new_id	92
90	8086 10f5	93	# cat /sys/bus/usb/drivers/foo/new_id
91	dead beef 06	94	8086 10f5
92	f00d cafe	95	dead beef 06
		96	f00d cafe
93		97
94	The list will be truncated at PAGE_SIZE bytes due to	98	The list will be truncated at PAGE_SIZE bytes due to
95	sysfs restrictions.	99	sysfs restrictions.
@@ -209,9 +213,11 @@ Description: · 113 unmodified lines
209	advance, and behaves well according to the specification.	213	advance, and behaves well according to the specification.
210	This attribute is a bit-field that controls the behavior of	214	This attribute is a bit-field that controls the behavior of
211	a specific port:	215	a specific port:
		216
212	- Bit 0 of this field selects the "old" enumeration scheme,	217	- Bit 0 of this field selects the "old" enumeration scheme,
213	as it is considerably faster (it only causes one USB reset	218	as it is considerably faster (it only causes one USB reset
214	instead of 2).	219	instead of 2).
		220
215	The old enumeration scheme can also be selected globally	221	The old enumeration scheme can also be selected globally
216	using /sys/module/usbcore/parameters/old_scheme_first, but	222	using /sys/module/usbcore/parameters/old_scheme_first, but
217	it is often not desirable as the new scheme was introduced to	223	it is often not desirable as the new scheme was introduced to
@@ -233,10 +239,10 @@ Description: · 15 unmodified lines
233	poll() for monitoring changes to this value in user space.	239	poll() for monitoring changes to this value in user space.
234		240
235	Any time this value changes the corresponding hub device will send a	241	Any time this value changes the corresponding hub device will send a
236	udev event with the following attributes:	242	udev event with the following attributes::
237		243
238	OVER_CURRENT_PORT=/sys/bus/usb/devices/.../(hub interface)/portX	244	OVER_CURRENT_PORT=/sys/bus/usb/devices/.../(hub interface)/portX
239	OVER_CURRENT_COUNT=[current value of this sysfs attribute]	245	OVER_CURRENT_COUNT=[current value of this sysfs attribute]
240		246
241	What: /sys/bus/usb/devices/.../(hub interface)/portX/usb3_lpm_permit	247	What: /sys/bus/usb/devices/.../(hub interface)/portX/usb3_lpm_permit
242	Date: November 2015	248	Date: November 2015

Documentation/ABI/testing/sysfs-bus-usb-devices-usbsevseg+5−2

Documentation/ABI/testing/sysfs-bus-vfio-mdev+6−4

@@ -28,8 +28,9 @@ Description: · 27 unmodified lines
28	Writing UUID to this file will create mediated device of	28	Writing UUID to this file will create mediated device of
29	type <type-id> for parent device <device>. This is a	29	type <type-id> for parent device <device>. This is a
30	write-only file.	30	write-only file.
31	For example:	31	For example::
32	# echo "83b8f4f2-509f-382f-3c1e-e6bfe0fa1001" > \	32
		33	# echo "83b8f4f2-509f-382f-3c1e-e6bfe0fa1001" > \
33	/sys/devices/foo/mdev_supported_types/foo-1/create	34	/sys/devices/foo/mdev_supported_types/foo-1/create
34		35
35	What: /sys/.../mdev_supported_types/<type-id>/devices/	36	What: /sys/.../mdev_supported_types/<type-id>/devices/
@@ -107,5 +108,6 @@ Description: · 71 unmodified lines
107	Writing '1' to this file destroys the mediated device. The	108	Writing '1' to this file destroys the mediated device. The
108	vendor driver can fail the remove() callback if that device	109	vendor driver can fail the remove() callback if that device
109	is active and the vendor driver doesn't support hot unplug.	110	is active and the vendor driver doesn't support hot unplug.
110	Example:	111	Example::
111	# echo 1 > /sys/bus/mdev/devices/<UUID>/remove	112
		113	# echo 1 > /sys/bus/mdev/devices/<UUID>/remove

Documentation/ABI/testing/sysfs-c2port+0−7

@@ -66,13 +66,6 @@ Description: · 65 unmodified lines
66	the "erase" command on the on-board flash of the connected	66	the "erase" command on the on-board flash of the connected
67	micro.	67	micro.
68		68
69	What: /sys/class/c2port/c2portX/flash_erase
70	Date: October 2008
71	Contact: Rodolfo Giometti <giometti@linux.it>
72	Description:
73	The /sys/class/c2port/c2portX/flash_erase file show the
74	on-board flash size of the connected micro.
75
76	What: /sys/class/c2port/c2portX/reset	69	What: /sys/class/c2port/c2portX/reset
77	Date: October 2008	70	Date: October 2008
78	Contact: Rodolfo Giometti <giometti@linux.it>	71	Contact: Rodolfo Giometti <giometti@linux.it>

Documentation/ABI/testing/sysfs-class-backlight+60−0

@@ -24,3 +24,63 @@ Description: · 23 unmodified lines
24	non-linear	24	non-linear
25	The brightness changes non-linearly with each step. Brightness	25	The brightness changes non-linearly with each step. Brightness
26	controls should use a linear mapping for a linear perception.	26	controls should use a linear mapping for a linear perception.
		27
		28	What: /sys/class/backlight/<backlight>/ambient_light_level
		29	Date: Apr, 2010
		30	KernelVersion: v2.6.35
		31	Contact: Michael Hennerich <michael.hennerich@analog.com>
		32	Description:
		33	(RO) Get conversion value of the light sensor.
		34
		35	The value is automatically updated every 80 ms when the
		36	light sensor is enabled.
		37
		38	The value range is device-driver specific:
		39
		40	For ADP8870:
		41
		42	It returns integer between 0 (dark) and 8000 (max ambient
		43	brightness).
		44
		45	For ADP8860:
		46
		47	It returns a 13-bits integer.
		48
		49	What: /sys/class/backlight/<backlight>/ambient_light_zone
		50	Date: Apr, 2010
		51	KernelVersion: v2.6.35
		52	Contact: Michael Hennerich <michael.hennerich@analog.com>,
		53	device-drivers-devel@blackfin.uclinux.org
		54
		55	Description:
		56	(RW) Read or write the specific brightness level at which the
		57	backlight operates.
		58
		59	The value meaning is device-driver specific:
		60
		61	For ADP8860:
		62
		63	== ==========================
		64	0 Off: Backlight set to 0 mA
		65	1 Level 1: daylight
		66	2 Level 2: bright
		67	3 Level 3: dark
		68	== ==========================
		69
		70	For ADP8870:
		71
		72	== ==========================
		73	0 Off: Backlight set to 0 mA
		74	1 Level 1: daylight
		75	2 Level 2: bright
		76	3 Level 3: office
		77	4 Level 4: indoor
		78	5 Level 5: dark
		79	== ==========================
		80
		81	Writing 0 returns to normal/automatic ambient light level
		82	operation.
		83
		84	It can be enabled by writing the value stored in
		85	/sys/class/backlight/<backlight>/max_brightness to
		86	/sys/class/backlight/<backlight>/brightness.

Documentation/ABI/testing/sysfs-class-backlight-adp8860+2−19

@@ -6,25 +6,8 @@ adp8860, adp8861 and adp8863 devices: daylight (level 1), office (level 2) and · 5 unmodified lines
6	dark (level 3). By default the brightness operates at the daylight brightness	6	dark (level 3). By default the brightness operates at the daylight brightness
7	level.	7	level.
8		8
9	What: /sys/class/backlight/<backlight>/ambient_light_level	9	See also /sys/class/backlight/<backlight>/ambient_light_level and
10	Date: Apr, 2010	10	/sys/class/backlight/<backlight>/ambient_light_zone.
11	KernelVersion: v2.6.35
12	Contact: Michael Hennerich <michael.hennerich@analog.com>
13	Description:
14	(RO) 13-bit conversion value for the first light sensor—high
15	byte (Bit 12 to Bit 8). The value is updated every 80 ms (when
16	the light sensor is enabled).
17
18
19	What: /sys/class/backlight/<backlight>/ambient_light_zone
20	Date: Apr, 2010
21	KernelVersion: v2.6.35
22	Contact: Michael Hennerich <michael.hennerich@analog.com>
23	Description:
24	(RW) Read or write the specific level at which the backlight
25	operates. Value "0" enables automatic ambient light sensing, and
26	values "1", "2" or "3" set the control to daylight, office or
27	dark respectively.
28		11
29		12
30	What: /sys/class/backlight/<backlight>/l1_daylight_max	13	What: /sys/class/backlight/<backlight>/l1_daylight_max

Documentation/ABI/testing/sysfs-class-backlight-driver-adp8870+3−27

@@ -1,3 +1,6 @@
		1	See also /sys/class/backlight/<backlight>/ambient_light_level and
		2	/sys/class/backlight/<backlight>/ambient_light_zone.
		3
1	What: /sys/class/backlight/<backlight>/<ambient light zone>_max	4	What: /sys/class/backlight/<backlight>/<ambient light zone>_max
2	What: /sys/class/backlight/<backlight>/l1_daylight_max	5	What: /sys/class/backlight/<backlight>/l1_daylight_max
3	What: /sys/class/backlight/<backlight>/l2_bright_max	6	What: /sys/class/backlight/<backlight>/l2_bright_max
@@ -27,30 +30,3 @@ Description: · 23 unmodified lines
27	set to 0. Full off when the backlight is disabled.	30	set to 0. Full off when the backlight is disabled.
28	This file will also show the dim brightness level stored for	31	This file will also show the dim brightness level stored for
29	this <ambient light zone>.	32	this <ambient light zone>.
30
31	What: /sys/class/backlight/<backlight>/ambient_light_level
32	Date: May 2011
33	KernelVersion: 3.0
34	Contact: device-drivers-devel@blackfin.uclinux.org
35	Description:
36	Get conversion value of the light sensor.
37	This value is updated every 80 ms (when the light sensor
38	is enabled). Returns integer between 0 (dark) and
39	8000 (max ambient brightness)
40
41	What: /sys/class/backlight/<backlight>/ambient_light_zone
42	Date: May 2011
43	KernelVersion: 3.0
44	Contact: device-drivers-devel@blackfin.uclinux.org
45	Description:
46	Get/Set current ambient light zone. Reading returns
47	integer between 1..5 (1 = daylight, 2 = bright, ..., 5 = dark).
48	Writing a value between 1..5 forces the backlight controller
49	to enter the corresponding ambient light zone.
50	Writing 0 returns to normal/automatic ambient light level
51	operation. The ambient light sensing feature on these devices
52	is an extension to the API documented in
53	Documentation/ABI/stable/sysfs-class-backlight.
54	It can be enabled by writing the value stored in
55	/sys/class/backlight/<backlight>/max_brightness to
56	/sys/class/backlight/<backlight>/brightness.

Documentation/ABI/testing/sysfs-class-backlight-driver-lm3533+16−10

 		Get the ALS output channel used as input in
 		ALS-current-control mode (0, 1), where:
-		0 - out_current0 (backlight 0)
+		==  ==========================
-		1 - out_current1 (backlight 1)
+		0   out_current0 (backlight 0)
+		1   out_current1 (backlight 1)
+		==  ==========================
 What:		/sys/class/backlight/<backlight>/als_en
 Date:		May 2012
 Description:
 		Set the brightness-mapping mode (0, 1), where:
-		0 - exponential mode
+		==  ================
-		1 - linear mode
+		0   exponential mode
+		1   linear mode
+		==  ================
 What:		/sys/class/backlight/<backlight>/pwm
 Date:		April 2012
 Description:
 		Set the PWM-input control mask (5 bits), where:
-		bit 5 - PWM-input enabled in Zone 4
+		=====   ===========================
-		bit 4 - PWM-input enabled in Zone 3
+		bit 5   PWM-input enabled in Zone 4
-		bit 3 - PWM-input enabled in Zone 2
+		bit 4   PWM-input enabled in Zone 3
-		bit 2 - PWM-input enabled in Zone 1
+		bit 3   PWM-input enabled in Zone 2
-		bit 1 - PWM-input enabled in Zone 0
+		bit 2   PWM-input enabled in Zone 1
-		bit 0 - PWM-input enabled
+		bit 1   PWM-input enabled in Zone 0
+		bit 0   PWM-input enabled
+		=====   ===========================

Documentation/ABI/testing/sysfs-class-bdi+0−1

@@ -24,7 +24,6 @@ default · 23 unmodified lines
24	filesystems which do not provide their own BDI.	24	filesystems which do not provide their own BDI.
25		25
26	Files under /sys/class/bdi/<bdi>/	26	Files under /sys/class/bdi/<bdi>/
27	---------------------------------
28		27
29	read_ahead_kb (read-write)	28	read_ahead_kb (read-write)
30		29

Documentation/ABI/testing/sysfs-class-chromeos+8−7

@@ -17,13 +17,14 @@ Date: August 2015 · 16 unmodified lines
17	KernelVersion: 4.2	17	KernelVersion: 4.2
18	Description:	18	Description:
19	Tell the EC to reboot in various ways. Options are:	19	Tell the EC to reboot in various ways. Options are:
20	"cancel": Cancel a pending reboot.	20
21	"ro": Jump to RO without rebooting.	21	- "cancel": Cancel a pending reboot.
22	"rw": Jump to RW without rebooting.	22	- "ro": Jump to RO without rebooting.
23	"cold": Cold reboot.	23	- "rw": Jump to RW without rebooting.
24	"disable-jump": Disable jump until next reboot.	24	- "cold": Cold reboot.
25	"hibernate": Hibernate the EC.	25	- "disable-jump": Disable jump until next reboot.
26	"at-shutdown": Reboot after an AP shutdown.	26	- "hibernate": Hibernate the EC.
		27	- "at-shutdown": Reboot after an AP shutdown.
27		28
28	What: /sys/class/chromeos/<ec-device-name>/version	29	What: /sys/class/chromeos/<ec-device-name>/version
29	Date: August 2015	30	Date: August 2015

Documentation/ABI/testing/sysfs-class-cxl+16−7

@@ -72,11 +72,16 @@ Description: read/write · 71 unmodified lines
72	when performing the START_WORK ioctl. Only applicable when	72	when performing the START_WORK ioctl. Only applicable when
73	running under hashed page table mmu.	73	running under hashed page table mmu.
74	Possible values:	74	Possible values:
75	none: No prefaulting (default)	75
76	work_element_descriptor: Treat the work element	76	======================= ======================================
77	descriptor as an effective address and	77	none No prefaulting (default)
78	prefault what it points to.	78	work_element_descriptor Treat the work element
79	all: all segments process calling START_WORK maps.	79	descriptor as an effective address and
		80	prefault what it points to.
		81	all all segments process calling
		82	START_WORK maps.
		83	======================= ======================================
		84
80	Users: https://github.com/ibm-capi/libcxl	85	Users: https://github.com/ibm-capi/libcxl
81		86
82	What: /sys/class/cxl/<afu>/reset	87	What: /sys/class/cxl/<afu>/reset
@@ -212,6 +217,7 @@ Description: read/write · 129 unmodified lines
212	card. A power cycle is required to load the image.	217	card. A power cycle is required to load the image.
213	"none" could be useful for debugging because the trace arrays	218	"none" could be useful for debugging because the trace arrays
214	are preserved.	219	are preserved.
		220
215	"user" and "factory" means PERST will cause either the user or	221	"user" and "factory" means PERST will cause either the user or
216	user or factory image to be loaded.	222	user or factory image to be loaded.
217	Default is to reload on PERST whichever image the card has	223	Default is to reload on PERST whichever image the card has
@@ -235,8 +241,11 @@ Contact: linuxppc-dev@lists.ozlabs.org · 17 unmodified lines
235	Description: read/write	241	Description: read/write
236	Trust that when an image is reloaded via PERST, it will not	242	Trust that when an image is reloaded via PERST, it will not
237	have changed.	243	have changed.
238	0 = don't trust, the image may be different (default)	244
239	1 = trust that the image will not change.	245	== =================================================
		246	0 don't trust, the image may be different (default)
		247	1 trust that the image will not change.
		248	== =================================================
240	Users: https://github.com/ibm-capi/libcxl	249	Users: https://github.com/ibm-capi/libcxl
241		250
242	What: /sys/class/cxl/<card>/psl_timebase_synced	251	What: /sys/class/cxl/<card>/psl_timebase_synced

Documentation/ABI/testing/sysfs-class-devfreq+4−2

@@ -62,7 +62,8 @@ Description: · 61 unmodified lines
62	driver should provide the list of available frequencies	62	driver should provide the list of available frequencies
63	with its profile. If need to reset the statistics of devfreq	63	with its profile. If need to reset the statistics of devfreq
64	behavior on a specific device, enter 0(zero) to 'trans_stat'	64	behavior on a specific device, enter 0(zero) to 'trans_stat'
65	as following:	65	as following::
		66
66	echo 0 > /sys/class/devfreq/.../trans_stat	67	echo 0 > /sys/class/devfreq/.../trans_stat
67		68
68	What: /sys/class/devfreq/.../userspace/set_freq	69	What: /sys/class/devfreq/.../userspace/set_freq
@@ -117,6 +118,7 @@ Description: · 48 unmodified lines
117	This work timer is used by devfreq workqueue in order to	118	This work timer is used by devfreq workqueue in order to
118	monitor the device status such as utilization. The user	119	monitor the device status such as utilization. The user
119	can change the work timer on runtime according to their demand	120	can change the work timer on runtime according to their demand
120	as following:	121	as following::
		122
121	echo deferrable > /sys/class/devfreq/.../timer	123	echo deferrable > /sys/class/devfreq/.../timer
122	echo delayed > /sys/class/devfreq/.../timer	124	echo delayed > /sys/class/devfreq/.../timer

Documentation/ABI/testing/sysfs-class-devlink+17−13

@@ -18,9 +18,9 @@ Description: · 17 unmodified lines
18		18
19	This will be one of the following strings:	19	This will be one of the following strings:
20		20
21	'consumer unbind'	21	- 'consumer unbind'
22	'supplier unbind'	22	- 'supplier unbind'
23	'never'	23	- 'never'
24		24
25	'consumer unbind' means the device link will be removed when	25	'consumer unbind' means the device link will be removed when
26	the consumer's driver is unbound from the consumer device.	26	the consumer's driver is unbound from the consumer device.
@@ -49,8 +49,10 @@ Description: · 22 unmodified lines
49		49
50	This will be one of the following strings:	50	This will be one of the following strings:
51		51
52	'0' - Does not affect runtime power management	52	=== ========================================
53	'1' - Affects runtime power management	53	'0' Does not affect runtime power management
		54	'1' Affects runtime power management
		55	=== ========================================
54		56
55	What: /sys/class/devlink/.../status	57	What: /sys/class/devlink/.../status
56	Date: May 2020	58	Date: May 2020
@@ -68,13 +70,13 @@ Description: · 11 unmodified lines
68		70
69	This will be one of the following strings:	71	This will be one of the following strings:
70		72
71	'not tracked'	73	- 'not tracked'
72	'dormant'	74	- 'dormant'
73	'available'	75	- 'available'
74	'consumer probing'	76	- 'consumer probing'
75	'active'	77	- 'active'
76	'supplier unbinding'	78	- 'supplier unbinding'
77	'unknown'	79	- 'unknown'
78		80
79	'not tracked' means this device link does not track the status	81	'not tracked' means this device link does not track the status
80	and has no impact on the binding, unbinding and syncing the	82	and has no impact on the binding, unbinding and syncing the
@@ -114,8 +116,10 @@ Description: · 33 unmodified lines
114		116
115	This will be one of the following strings:	117	This will be one of the following strings:
116		118
		119	=== ================================
117	'0'	120	'0'
118	'1' - Affects runtime power management	121	'1' Affects runtime power management
		122	=== ================================
119		123
120	'0' means the device link can affect other device behaviors	124	'0' means the device link can affect other device behaviors
121	like binding/unbinding, suspend/resume, runtime power	125	like binding/unbinding, suspend/resume, runtime power

Documentation/ABI/testing/sysfs-class-extcon+19−15

@@ -39,19 +39,22 @@ Description: · 38 unmodified lines
39	callback.	39	callback.
40		40
41	If the default callback for showing function is used, the	41	If the default callback for showing function is used, the
42	format is like this:	42	format is like this::
43	# cat state	43
44	USB_OTG=1	44	# cat state
45	HDMI=0	45	USB_OTG=1
46	TA=1	46	HDMI=0
47	EAR_JACK=0	47	TA=1
48	#	48	EAR_JACK=0
		49	#
		50
49	In this example, the extcon device has USB_OTG and TA	51	In this example, the extcon device has USB_OTG and TA
50	cables attached and HDMI and EAR_JACK cables detached.	52	cables attached and HDMI and EAR_JACK cables detached.
51		53
52	In order to update the state of an extcon device, enter a hex	54	In order to update the state of an extcon device, enter a hex
53	state number starting with 0x:	55	state number starting with 0x::
54	# echo 0xHEX > state	56
		57	# echo 0xHEX > state
55		58
56	This updates the whole state of the extcon device.	59	This updates the whole state of the extcon device.
57	Inputs of all the methods are required to meet the	60	Inputs of all the methods are required to meet the
@@ -84,12 +87,13 @@ Contact: MyungJoo Ham <myungjoo.ham@samsung.com> · 26 unmodified lines
84	Description:	87	Description:
85	Shows the relations of mutually exclusiveness. For example,	88	Shows the relations of mutually exclusiveness. For example,
86	if the mutually_exclusive array of extcon device is	89	if the mutually_exclusive array of extcon device is
87	{0x3, 0x5, 0xC, 0x0}, then the output is:	90	{0x3, 0x5, 0xC, 0x0}, then the output is::
88	# ls mutually_exclusive/	91
89	0x3	92	# ls mutually_exclusive/
90	0x5	93	0x3
91	0xc	94	0x5
92	#	95	0xc
		96	#
93		97
94	Note that mutually_exclusive is a sub-directory of the extcon	98	Note that mutually_exclusive is a sub-directory of the extcon
95	device and the file names under the mutually_exclusive	99	device and the file names under the mutually_exclusive

Documentation/ABI/testing/sysfs-class-fpga-manager+2−3

 		* firmware request	= firmware class request in progress
 		* firmware request error = firmware request failed
 		* write init		= preparing FPGA for programming
-		* write init error	= Error while preparing FPGA for
+		* write init error	= Error while preparing FPGA for programming
-					  programming
 		* write			= FPGA ready to receive image data
 		* write error		= Error while programming
 		* write complete	= Doing post programming steps
 		programming errors to userspace. This is a list of strings for
 		the supported status.
-		* reconfig operation error 	- invalid operations detected by
+		* reconfig operation error	- invalid operations detected by
 						  reconfiguration hardware.
 						  e.g. start reconfiguration
 						  with errors not cleared

Documentation/ABI/testing/sysfs-class-gnss+2−0

 		The GNSS receiver type. The currently identified types reflect
 		the protocol(s) supported by the receiver:
+			======		===========
 			"NMEA"		NMEA 0183
 			"SiRF"		SiRF Binary
 			"UBX"		UBX
+			======		===========
 		Note that also non-"NMEA" type receivers typically support a
 		subset of NMEA 0183 with vendor extensions (e.g. to allow

Documentation/ABI/testing/sysfs-class-led+24−4

@@ -3,9 +3,26 @@ Date: March 2006 · 2 unmodified lines
3	KernelVersion: 2.6.17	3	KernelVersion: 2.6.17
4	Contact: Richard Purdie <rpurdie@rpsys.net>	4	Contact: Richard Purdie <rpurdie@rpsys.net>
5	Description:	5	Description:
6	Set the brightness of the LED. Most LEDs don't	6	Set the brightness of the LED.
7	have hardware brightness support, so will just be turned on for	7
8	non-zero brightness settings. The value is between 0 and	8	Most LEDs don't have hardware brightness support, so will
		9	just be turned on for non-zero brightness settings.
		10
		11	.. Note::
		12
		13	For multicolor LEDs, writing to this file will update all
		14	LEDs within the group to a calculated percentage of what
		15	each color LED intensity is set to.
		16
		17	The percentage is calculated for each grouped LED via
		18	the equation below::
		19
		20	led_brightness = brightness * multi_intensity/max_brightness
		21
		22	For additional details please refer to
		23	Documentation/leds/leds-class-multicolor.rst.
		24
		25	The value is between 0 and
9	/sys/class/leds/<led>/max_brightness.	26	/sys/class/leds/<led>/max_brightness.
10		27
11	Writing 0 to this file clears active trigger.	28	Writing 0 to this file clears active trigger.
@@ -13,6 +30,8 @@ Description: · 1 unmodified line
13	Writing non-zero to this file while trigger is active changes the	30	Writing non-zero to this file while trigger is active changes the
14	top brightness trigger is going to use.	31	top brightness trigger is going to use.
15		32
		33
		34
16	What: /sys/class/leds/<led>/max_brightness	35	What: /sys/class/leds/<led>/max_brightness
17	Date: March 2006	36	Date: March 2006
18	KernelVersion: 2.6.17	37	KernelVersion: 2.6.17
@@ -47,10 +66,11 @@ Contact: Richard Purdie <rpurdie@rpsys.net> · 28 unmodified lines
47	Description:	66	Description:
48	Set the trigger for this LED. A trigger is a kernel based source	67	Set the trigger for this LED. A trigger is a kernel based source
49	of LED events.	68	of LED events.
		69
50	You can change triggers in a similar manner to the way an IO	70	You can change triggers in a similar manner to the way an IO
51	scheduler is chosen. Trigger specific parameters can appear in	71	scheduler is chosen. Trigger specific parameters can appear in
52	/sys/class/leds/<led> once a given trigger is selected. For	72	/sys/class/leds/<led> once a given trigger is selected. For
53	their documentation see sysfs-class-led-trigger-*.	73	their documentation see `sysfs-class-led-trigger-*`.
54		74
55	What: /sys/class/leds/<led>/inverted	75	What: /sys/class/leds/<led>/inverted
56	Date: January 2011	76	Date: January 2011

Documentation/ABI/testing/sysfs-class-led-driver-el15203000+0−130

@@ -1,133 +1,3 @@
1	What: /sys/class/leds/<led>/hw_pattern
2	Date: September 2019
3	KernelVersion: 5.5
4	Description:
5	Specify a hardware pattern for the EL15203000 LED.
6	The LEDs board supports only predefined patterns by firmware
7	for specific LEDs.
8
9	Breathing mode for Screen frame light tube:
10	"0 4000 1 4000"
11
12	^
13	\|
14	Max-\| ---
15	\| / \
16	\| / \
17	\| / \ /
18	\| / \ /
19	Min-\|- ---
20	\|
21	0------4------8--> time (sec)
22
23	Cascade mode for Pipe LED:
24	"1 800 2 800 4 800 8 800 16 800"
25
26	^
27	\|
28	0 On -\|----+ +----+ +---
29	\| \| \| \| \|
30	Off-\| +-------------------+ +-------------------+
31	\|
32	1 On -\| +----+ +----+
33	\| \| \| \| \|
34	Off \|----+ +-------------------+ +------------------
35	\|
36	2 On -\| +----+ +----+
37	\| \| \| \| \|
38	Off-\|---------+ +-------------------+ +-------------
39	\|
40	3 On -\| +----+ +----+
41	\| \| \| \| \|
42	Off-\|--------------+ +-------------------+ +--------
43	\|
44	4 On -\| +----+ +----+
45	\| \| \| \| \|
46	Off-\|-------------------+ +-------------------+ +---
47	\|
48	0---0.8--1.6--2.4--3.2---4---4.8--5.6--6.4--7.2---8--> time (sec)
49
50	Inverted cascade mode for Pipe LED:
51	"30 800 29 800 27 800 23 800 15 800"
52
53	^
54	\|
55	0 On -\| +-------------------+ +-------------------+
56	\| \| \| \| \|
57	Off-\|----+ +----+ +---
58	\|
59	1 On -\|----+ +-------------------+ +------------------
60	\| \| \| \| \|
61	Off \| +----+ +----+
62	\|
63	2 On -\|---------+ +-------------------+ +-------------
64	\| \| \| \| \|
65	Off-\| +----+ +----+
66	\|
67	3 On -\|--------------+ +-------------------+ +--------
68	\| \| \| \| \|
69	Off-\| +----+ +----+
70	\|
71	4 On -\|-------------------+ +-------------------+ +---
72	\| \| \| \| \|
73	Off-\| +----+ +----+
74	\|
75	0---0.8--1.6--2.4--3.2---4---4.8--5.6--6.4--7.2---8--> time (sec)
76
77	Bounce mode for Pipe LED:
78	"1 800 2 800 4 800 8 800 16 800 16 800 8 800 4 800 2 800 1 800"
79
80	^
81	\|
82	0 On -\|----+ +--------
83	\| \| \|
84	Off-\| +---------------------------------------+
85	\|
86	1 On -\| +----+ +----+
87	\| \| \| \| \|
88	Off \|----+ +-----------------------------+ +--------
89	\|
90	2 On -\| +----+ +----+
91	\| \| \| \| \|
92	Off-\|---------+ +-------------------+ +-------------
93	\|
94	3 On -\| +----+ +----+
95	\| \| \| \| \|
96	Off-\|--------------+ +---------+ +------------------
97	\|
98	4 On -\| +---------+
99	\| \| \|
100	Off-\|-------------------+ +-----------------------
101	\|
102	0---0.8--1.6--2.4--3.2---4---4.8--5.6--6.4--7.2---8--> time (sec)
103
104	Inverted bounce mode for Pipe LED:
105	"30 800 29 800 27 800 23 800 15 800 15 800 23 800 27 800 29 800 30 800"
106
107	^
108	\|
109	0 On -\| +---------------------------------------+
110	\| \| \|
111	Off-\|----+ +--------
112	\|
113	1 On -\|----+ +-----------------------------+ +--------
114	\| \| \| \| \|
115	Off \| +----+ +----+
116	\|
117	2 On -\|---------+ +-------------------+ +-------------
118	\| \| \| \| \|
119	Off-\| +----+ +----+
120	\|
121	3 On -\|--------------+ +---------+ +------------------
122	\| \| \| \| \|
123	Off-\| +----+ +----+
124	\|
125	4 On -\|-------------------+ +-----------------------
126	\| \| \|
127	Off-\| +---------+
128	\|
129	0---0.8--1.6--2.4--3.2---4---4.8--5.6--6.4--7.2---8--> time (sec)
130
131	What: /sys/class/leds/<led>/repeat	1	What: /sys/class/leds/<led>/repeat
132	Date: September 2019	2	Date: September 2019
133	KernelVersion: 5.5	3	KernelVersion: 5.5

Documentation/ABI/testing/sysfs-class-led-driver-lm3533+26−18

@@ -6,8 +6,10 @@ Description: · 5 unmodified lines
6	Set the ALS output channel to use as input in	6	Set the ALS output channel to use as input in
7	ALS-current-control mode (1, 2), where:	7	ALS-current-control mode (1, 2), where:
8		8
9	1 - out_current1	9	== ============
10	2 - out_current2	10	1 out_current1
		11	2 out_current2
		12	== ============
11		13
12	What: /sys/class/leds/<led>/als_en	14	What: /sys/class/leds/<led>/als_en
13	Date: May 2012	15	Date: May 2012
@@ -24,14 +26,16 @@ Contact: Johan Hovold <jhovold@gmail.com> · 10 unmodified lines
24	Description:	26	Description:
25	Set the pattern generator fall and rise times (0..7), where:	27	Set the pattern generator fall and rise times (0..7), where:
26		28
27	0 - 2048 us	29	== =======
28	1 - 262 ms	30	0 2048 us
29	2 - 524 ms	31	1 262 ms
30	3 - 1.049 s	32	2 524 ms
31	4 - 2.097 s	33	3 1.049 s
32	5 - 4.194 s	34	4 2.097 s
33	6 - 8.389 s	35	5 4.194 s
34	7 - 16.78 s	36	6 8.389 s
		37	7 16.78 s
		38	== =======
35		39
36	What: /sys/class/leds/<led>/id	40	What: /sys/class/leds/<led>/id
37	Date: April 2012	41	Date: April 2012
@@ -47,8 +51,10 @@ Contact: Johan Hovold <jhovold@gmail.com> · 9 unmodified lines
47	Description:	51	Description:
48	Set the brightness-mapping mode (0, 1), where:	52	Set the brightness-mapping mode (0, 1), where:
49		53
50	0 - exponential mode	54	== ================
51	1 - linear mode	55	0 exponential mode
		56	1 linear mode
		57	== ================
52		58
53	What: /sys/class/leds/<led>/pwm	59	What: /sys/class/leds/<led>/pwm
54	Date: April 2012	60	Date: April 2012
@@ -57,9 +63,11 @@ Contact: Johan Hovold <jhovold@gmail.com> · 2 unmodified lines
57	Description:	63	Description:
58	Set the PWM-input control mask (5 bits), where:	64	Set the PWM-input control mask (5 bits), where:
59		65
60	bit 5 - PWM-input enabled in Zone 4	66	===== ===========================
61	bit 4 - PWM-input enabled in Zone 3	67	bit 5 PWM-input enabled in Zone 4
62	bit 3 - PWM-input enabled in Zone 2	68	bit 4 PWM-input enabled in Zone 3
63	bit 2 - PWM-input enabled in Zone 1	69	bit 3 PWM-input enabled in Zone 2
64	bit 1 - PWM-input enabled in Zone 0	70	bit 2 PWM-input enabled in Zone 1
65	bit 0 - PWM-input enabled	71	bit 1 PWM-input enabled in Zone 0
		72	bit 0 PWM-input enabled
		73	===== ===========================

Documentation/ABI/testing/sysfs-class-led-driver-sc27xx+0−22

@@ -1,22 +0,0 @@
1	What: /sys/class/leds/<led>/hw_pattern
2	Date: September 2018
3	KernelVersion: 4.20
4	Description:
5	Specify a hardware pattern for the SC27XX LED. For the SC27XX
6	LED controller, it only supports 4 stages to make a single
7	hardware pattern, which is used to configure the rise time,
8	high time, fall time and low time for the breathing mode.
9
10	For the breathing mode, the SC27XX LED only expects one brightness
11	for the high stage. To be compatible with the hardware pattern
12	format, we should set brightness as 0 for rise stage, fall
13	stage and low stage.
14
15	Min stage duration: 125 ms
16	Max stage duration: 31875 ms
17
18	Since the stage duration step is 125 ms, the duration should be
19	a multiplier of 125, like 125ms, 250ms, 375ms, 500ms ... 31875ms.
20
21	Thus the format of the hardware pattern values should be:
22	"0 rise_duration brightness high_duration 0 fall_duration 0 low_duration".

Documentation/ABI/testing/sysfs-class-led-flash+18−9

 		Flash faults are re-read after strobing the flash. Possible
 		flash faults:
-		* led-over-voltage - flash controller voltage to the flash LED
+		* led-over-voltage
+			flash controller voltage to the flash LED
 			has exceeded the limit specific to the flash controller
-		* flash-timeout-exceeded - the flash strobe was still on when
+		* flash-timeout-exceeded
+			the flash strobe was still on when
 			the timeout set by the user has expired; not all flash
 			controllers may set this in all such conditions
-		* controller-over-temperature - the flash controller has
+		* controller-over-temperature
+			the flash controller has
 			overheated
-		* controller-short-circuit - the short circuit protection
+		* controller-short-circuit
+			the short circuit protection
 			of the flash controller has been triggered
-		* led-power-supply-over-current - current in the LED power
+		* led-power-supply-over-current
+			current in the LED power
 			supply has exceeded the limit specific to the flash
 			controller
-		* indicator-led-fault - the flash controller has detected
+		* indicator-led-fault
+			the flash controller has detected
 			a short or open circuit condition on the indicator LED
-		* led-under-voltage - flash controller voltage to the flash
+		* led-under-voltage
+			flash controller voltage to the flash
 			LED has been below the minimum limit specific to
 			the flash
-		* controller-under-voltage - the input voltage of the flash
+		* controller-under-voltage
+			the input voltage of the flash
 			controller is below the limit under which strobing the
 			flash at full current will not be possible;
 			the condition persists until this flag is no longer set
-		* led-over-temperature - the temperature of the LED has exceeded
+		* led-over-temperature
+			the temperature of the LED has exceeded
 			its allowed upper limit

Documentation/ABI/testing/sysfs-class-led-multicolor+6−17

-What:		/sys/class/leds/<led>/brightness
-Date:		March 2020
-KernelVersion:	5.9
-Contact:	Dan Murphy <dmurphy@ti.com>
-Description:	read/write
-		Writing to this file will update all LEDs within the group to a
-		calculated percentage of what each color LED intensity is set
-		to. The percentage is calculated for each grouped LED via the
-		equation below:
-		led_brightness = brightness * multi_intensity/max_brightness
-		For additional details please refer to
-		Documentation/leds/leds-class-multicolor.rst.
-		The value of the LED is from 0 to
-		/sys/class/leds/<led>/max_brightness.
 What:		/sys/class/leds/<led>/multi_index
 Date:		March 2020
 		as an array of strings as they are indexed in the
 		multi_intensity file.
+		For additional details please refer to
+		Documentation/leds/leds-class-multicolor.rst.
 What:		/sys/class/leds/<led>/multi_intensity
 Date:		March 2020
 KernelVersion:	5.9
 		This file contains array of integers. Order of components is
 		described by the multi_index array. The maximum intensity should
 		not exceed /sys/class/leds/<led>/max_brightness.
+		For additional details please refer to
+		Documentation/leds/leds-class-multicolor.rst.

Documentation/ABI/testing/sysfs-class-led-trigger-netdev+7−0

Documentation/ABI/testing/sysfs-class-led-trigger-pattern+2−2

@@ -23,8 +23,8 @@ Description: · 22 unmodified lines
23		23
24	Since different LED hardware can have different semantics of	24	Since different LED hardware can have different semantics of
25	hardware patterns, each driver is expected to provide its own	25	hardware patterns, each driver is expected to provide its own
26	description for the hardware patterns in their ABI documentation	26	description for the hardware patterns in their documentation
27	file.	27	file at Documentation/leds/.
28		28
29	What: /sys/class/leds/<led>/repeat	29	What: /sys/class/leds/<led>/repeat
30	Date: September 2018	30	Date: September 2018

Documentation/ABI/testing/sysfs-class-led-trigger-usbport+1−0

@@ -8,5 +8,6 @@ Description: · 7 unmodified lines
8	selected for the USB port trigger. Selecting ports makes trigger	8	selected for the USB port trigger. Selecting ports makes trigger
9	observing them for any connected devices and lighting on LED if	9	observing them for any connected devices and lighting on LED if
10	there are any.	10	there are any.
		11
11	Echoing "1" value selects USB port. Echoing "0" unselects it.	12	Echoing "1" value selects USB port. Echoing "0" unselects it.
12	Current state can be also read.	13	Current state can be also read.

Documentation/ABI/testing/sysfs-class-leds-gt683r+5−3

 		of one LED will update the mode of its two sibling devices as
 		well. Possible values are:
-		0 - normal
+		==  =========
-		1 - audio
+		0   normal
-		2 - breathing
+		1   audio
+		2   breathing
+		==  =========
 		Normal: LEDs are fully on when enabled
 		Audio:  LEDs brightness depends on sound level

Documentation/ABI/testing/sysfs-class-mic+32−20

@@ -41,24 +41,33 @@ Description: · 40 unmodified lines
41	When read, this entry provides the current state of an Intel	41	When read, this entry provides the current state of an Intel
42	MIC device in the context of the card OS. Possible values that	42	MIC device in the context of the card OS. Possible values that
43	will be read are:	43	will be read are:
44	"ready" - The MIC device is ready to boot the card OS. On	44
45	reading this entry after an OSPM resume, a "boot" has to be	45
46	written to this entry if the card was previously shutdown	46	=============== ===============================================
47	during OSPM suspend.	47	"ready" The MIC device is ready to boot the card OS.
48	"booting" - The MIC device has initiated booting a card OS.	48	On reading this entry after an OSPM resume,
49	"online" - The MIC device has completed boot and is online	49	a "boot" has to be written to this entry if
50	"shutting_down" - The card OS is shutting down.	50	the card was previously shutdown during OSPM
51	"resetting" - A reset has been initiated for the MIC device	51	suspend.
52	"reset_failed" - The MIC device has failed to reset.	52	"booting" The MIC device has initiated booting a card OS.
		53	"online" The MIC device has completed boot and is online
		54	"shutting_down" The card OS is shutting down.
		55	"resetting" A reset has been initiated for the MIC device
		56	"reset_failed" The MIC device has failed to reset.
		57	=============== ===============================================
53		58
54	When written, this sysfs entry triggers different state change	59	When written, this sysfs entry triggers different state change
55	operations depending upon the current state of the card OS.	60	operations depending upon the current state of the card OS.
56	Acceptable values are:	61	Acceptable values are:
57	"boot" - Boot the card OS image specified by the combination	62
58	of firmware, ramdisk, cmdline and bootmode	63
59	sysfs entries.	64	========== ===================================================
60	"reset" - Initiates device reset.	65	"boot" Boot the card OS image specified by the combination
61	"shutdown" - Initiates card OS shutdown.	66	of firmware, ramdisk, cmdline and bootmode
		67	sysfs entries.
		68	"reset" Initiates device reset.
		69	"shutdown" Initiates card OS shutdown.
		70	========== ===================================================
62		71
63	What: /sys/class/mic/mic(x)/shutdown_status	72	What: /sys/class/mic/mic(x)/shutdown_status
64	Date: October 2013	73	Date: October 2013
@@ -69,12 +78,15 @@ Description: · 4 unmodified lines
69	OS can shutdown because of various reasons. When read, this	78	OS can shutdown because of various reasons. When read, this
70	entry provides the status on why the card OS was shutdown.	79	entry provides the status on why the card OS was shutdown.
71	Possible values are:	80	Possible values are:
72	"nop" - shutdown status is not applicable, when the card OS is	81
73	"online"	82	========== ===================================================
74	"crashed" - Shutdown because of a HW or SW crash.	83	"nop" shutdown status is not applicable, when the card OS
75	"halted" - Shutdown because of a halt command.	84	is "online"
76	"poweroff" - Shutdown because of a poweroff command.	85	"crashed" Shutdown because of a HW or SW crash.
77	"restart" - Shutdown because of a restart command.	86	"halted" Shutdown because of a halt command.
		87	"poweroff" Shutdown because of a poweroff command.
		88	"restart" Shutdown because of a restart command.
		89	========== ===================================================
78		90
79	What: /sys/class/mic/mic(x)/cmdline	91	What: /sys/class/mic/mic(x)/cmdline
80	Date: October 2013	92	Date: October 2013

Documentation/ABI/testing/sysfs-class-net+42−19

@@ -4,10 +4,13 @@ KernelVersion: 3.17 · 3 unmodified lines
4	Contact: netdev@vger.kernel.org	4	Contact: netdev@vger.kernel.org
5	Description:	5	Description:
6	Indicates the name assignment type. Possible values are:	6	Indicates the name assignment type. Possible values are:
7	1: enumerated by the kernel, possibly in an unpredictable way	7
8	2: predictably named by the kernel	8	== ==========================================================
9	3: named by userspace	9	1 enumerated by the kernel, possibly in an unpredictable way
10	4: renamed	10	2 predictably named by the kernel
		11	3 named by userspace
		12	4 renamed
		13	== ==========================================================
11		14
12	What: /sys/class/net/<iface>/addr_assign_type	15	What: /sys/class/net/<iface>/addr_assign_type
13	Date: July 2010	16	Date: July 2010
@@ -15,10 +18,13 @@ KernelVersion: 3.2 · 1 unmodified line
15	Contact: netdev@vger.kernel.org	18	Contact: netdev@vger.kernel.org
16	Description:	19	Description:
17	Indicates the address assignment type. Possible values are:	20	Indicates the address assignment type. Possible values are:
18	0: permanent address	21
19	1: randomly generated	22	== =============================
20	2: stolen from another device	23	0 permanent address
21	3: set using dev_set_mac_address	24	1 randomly generated
		25	2 stolen from another device
		26	3 set using dev_set_mac_address
		27	== =============================
22		28
23	What: /sys/class/net/<iface>/addr_len	29	What: /sys/class/net/<iface>/addr_len
24	Date: April 2005	30	Date: April 2005
@@ -51,9 +57,12 @@ Description: · 26 unmodified lines
51	Default value 0 does not forward any link local frames.	57	Default value 0 does not forward any link local frames.
52		58
53	Restricted bits:	59	Restricted bits:
54	0: 01-80-C2-00-00-00 Bridge Group Address used for STP	60
55	1: 01-80-C2-00-00-01 (MAC Control) 802.3 used for MAC PAUSE	61	== ========================================================
56	2: 01-80-C2-00-00-02 (Link Aggregation) 802.3ad	62	0 01-80-C2-00-00-00 Bridge Group Address used for STP
		63	1 01-80-C2-00-00-01 (MAC Control) 802.3 used for MAC PAUSE
		64	2 01-80-C2-00-00-02 (Link Aggregation) 802.3ad
		65	== ========================================================
57		66
58	Any values not setting these bits can be used. Take special	67	Any values not setting these bits can be used. Take special
59	care when forwarding control frames e.g. 802.1X-PAE or LLDP.	68	care when forwarding control frames e.g. 802.1X-PAE or LLDP.
@@ -74,8 +83,11 @@ Contact: netdev@vger.kernel.org · 14 unmodified lines
74	Description:	83	Description:
75	Indicates the current physical link state of the interface.	84	Indicates the current physical link state of the interface.
76	Posssible values are:	85	Posssible values are:
77	0: physical link is down	86
78	1: physical link is up	87	== =====================
		88	0 physical link is down
		89	1 physical link is up
		90	== =====================
79		91
80	Note: some special devices, e.g: bonding and team drivers will	92	Note: some special devices, e.g: bonding and team drivers will
81	allow this attribute to be written to force a link state for	93	allow this attribute to be written to force a link state for
@@ -131,8 +143,11 @@ Contact: netdev@vger.kernel.org · 49 unmodified lines
131	Description:	143	Description:
132	Indicates whether the interface is under test. Possible	144	Indicates whether the interface is under test. Possible
133	values are:	145	values are:
134	0: interface is not being tested	146
135	1: interface is being tested	147	== =============================
		148	0 interface is not being tested
		149	1 interface is being tested
		150	== =============================
136		151
137	When an interface is under test, it cannot be expected	152	When an interface is under test, it cannot be expected
138	to pass packets as normal.	153	to pass packets as normal.
@@ -144,8 +159,11 @@ Contact: netdev@vger.kernel.org · 5 unmodified lines
144	Description:	159	Description:
145	Indicates the interface latest or current duplex value. Possible	160	Indicates the interface latest or current duplex value. Possible
146	values are:	161	values are:
147	half: half duplex	162
148	full: full duplex	163	==== ===========
		164	half half duplex
		165	full full duplex
		166	==== ===========
149		167
150	Note: This attribute is only valid for interfaces that implement	168	Note: This attribute is only valid for interfaces that implement
151	the ethtool get_link_ksettings method (mostly Ethernet).	169	the ethtool get_link_ksettings method (mostly Ethernet).
@@ -196,8 +214,11 @@ Description: · 44 unmodified lines
196	Indicates the interface link mode, as a decimal number. This	214	Indicates the interface link mode, as a decimal number. This
197	attribute should be used in conjunction with 'dormant' attribute	215	attribute should be used in conjunction with 'dormant' attribute
198	to determine the interface usability. Possible values:	216	to determine the interface usability. Possible values:
199	0: default link mode	217
200	1: dormant link mode	218	== =================
		219	0 default link mode
		220	1 dormant link mode
		221	== =================
201		222
202	What: /sys/class/net/<iface>/mtu	223	What: /sys/class/net/<iface>/mtu
203	Date: April 2005	224	Date: April 2005
@@ -226,7 +247,9 @@ KernelVersion: 2.6.17 · 22 unmodified lines
226	Contact: netdev@vger.kernel.org	247	Contact: netdev@vger.kernel.org
227	Description:	248	Description:
228	Indicates the interface RFC2863 operational state as a string.	249	Indicates the interface RFC2863 operational state as a string.
		250
229	Possible values are:	251	Possible values are:
		252
230	"unknown", "notpresent", "down", "lowerlayerdown", "testing",	253	"unknown", "notpresent", "down", "lowerlayerdown", "testing",
231	"dormant", "up".	254	"dormant", "up".
232		255

Documentation/ABI/testing/sysfs-class-net-cdc_ncm+3−3

@@ -91,9 +91,9 @@ Date: May 2014 · 90 unmodified lines
91	KernelVersion: 3.16	91	KernelVersion: 3.16
92	Contact: Bjørn Mork <bjorn@mork.no>	92	Contact: Bjørn Mork <bjorn@mork.no>
93	Description:	93	Description:
94	Bit 0: 16-bit NTB supported (set to 1)	94	- Bit 0: 16-bit NTB supported (set to 1)
95	Bit 1: 32-bit NTB supported	95	- Bit 1: 32-bit NTB supported
96	Bits 2 – 15: reserved (reset to zero; must be ignored by host)	96	- Bits 2 – 15: reserved (reset to zero; must be ignored by host)
97		97
98	What: /sys/class/net/<iface>/cdc_ncm/dwNtbInMaxSize	98	What: /sys/class/net/<iface>/cdc_ncm/dwNtbInMaxSize
99	Date: May 2014	99	Date: May 2014

Documentation/ABI/testing/sysfs-class-net-phydev+2−0

@@ -35,7 +35,9 @@ Description: · 34 unmodified lines
35	Ethernet driver during bus enumeration, encoded in string.	35	Ethernet driver during bus enumeration, encoded in string.
36	This interface mode is used to configure the Ethernet MAC with the	36	This interface mode is used to configure the Ethernet MAC with the
37	appropriate mode for its data lines to the PHY hardware.	37	appropriate mode for its data lines to the PHY hardware.
		38
38	Possible values are:	39	Possible values are:
		40
39	<empty> (not available), mii, gmii, sgmii, tbi, rev-mii,	41	<empty> (not available), mii, gmii, sgmii, tbi, rev-mii,
40	rmii, rgmii, rgmii-id, rgmii-rxid, rgmii-txid, rtbi, smii	42	rmii, rgmii, rgmii-id, rgmii-rxid, rgmii-txid, rtbi, smii
41	xgmii, moca, qsgmii, trgmii, 1000base-x, 2500base-x, rxaui,	43	xgmii, moca, qsgmii, trgmii, 1000base-x, 2500base-x, rxaui,

Documentation/ABI/testing/sysfs-class-ocxl+11−6

@@ -11,8 +11,11 @@ Contact: linuxppc-dev@lists.ozlabs.org · 10 unmodified lines
11	Description: read only	11	Description: read only
12	Number of contexts for the AFU, in the format <n>/<max>	12	Number of contexts for the AFU, in the format <n>/<max>
13	where:	13	where:
14	n: number of currently active contexts, for debug	14
15	max: maximum number of contexts supported by the AFU	15	==== ===============================================
		16	n number of currently active contexts, for debug
		17	max maximum number of contexts supported by the AFU
		18	==== ===============================================
16		19
17	What: /sys/class/ocxl/<afu name>/pp_mmio_size	20	What: /sys/class/ocxl/<afu name>/pp_mmio_size
18	Date: January 2018	21	Date: January 2018
@@ -40,7 +43,9 @@ Contact: linuxppc-dev@lists.ozlabs.org · 21 unmodified lines
40	Description: read/write	43	Description: read/write
41	Control whether the FPGA is reloaded on a link reset. Enabled	44	Control whether the FPGA is reloaded on a link reset. Enabled
42	through a vendor-specific logic block on the FPGA.	45	through a vendor-specific logic block on the FPGA.
43	0 Do not reload FPGA image from flash	46
44	1 Reload FPGA image from flash	47	=========== ===========================================
45	unavailable	48	0 Do not reload FPGA image from flash
46	The device does not support this capability	49	1 Reload FPGA image from flash
		50	unavailable The device does not support this capability
		51	=========== ===========================================

Documentation/ABI/testing/sysfs-class-pktcdvd+21−17

Documentation/ABI/testing/sysfs-class-power+275−250

@@ -1,4 +1,4 @@
1	===== General Properties =====	1	General Properties
2		2
3	What: /sys/class/power_supply/<supply_name>/manufacturer	3	What: /sys/class/power_supply/<supply_name>/manufacturer
4	Date: May 2007	4	Date: May 2007
@@ -36,14 +36,238 @@ Description: · 31 unmodified lines
36	Access: Read	36	Access: Read
37	Valid values: "Battery", "UPS", "Mains", "USB", "Wireless"	37	Valid values: "Battery", "UPS", "Mains", "USB", "Wireless"
38		38
39	===== Battery Properties =====	39	Battery and USB properties
		40
		41	What: /sys/class/power_supply/<supply_name>/current_avg
		42	Date: May 2007
		43	Contact: linux-pm@vger.kernel.org
		44	Description:
		45	Battery:
		46
		47	Reports an average IBAT current reading for the battery, over
		48	a fixed period. Normally devices will provide a fixed interval
		49	in which they average readings to smooth out the reported
		50	value.
		51
		52	USB:
		53
		54	Reports an average IBUS current reading over a fixed period.
		55	Normally devices will provide a fixed interval in which they
		56	average readings to smooth out the reported value.
		57
		58	Access: Read
		59
		60	Valid values: Represented in microamps. Negative values are
		61	used for discharging batteries, positive values for charging
		62	batteries and for USB IBUS current.
		63
		64	What: /sys/class/power_supply/<supply_name>/current_max
		65	Date: October 2010
		66	Contact: linux-pm@vger.kernel.org
		67	Description:
		68	Battery:
		69
		70	Reports the maximum IBAT current allowed into the battery.
		71
		72	USB:
		73
		74	Reports the maximum IBUS current the supply can support.
		75
		76	Access: Read
		77	Valid values: Represented in microamps
		78
		79	What: /sys/class/power_supply/<supply_name>/current_now
		80	Date: May 2007
		81	Contact: linux-pm@vger.kernel.org
		82	Description:
		83
		84	Battery:
		85
		86	Reports an instant, single IBAT current reading for the
		87	battery. This value is not averaged/smoothed.
		88
		89	Access: Read
		90
		91	USB:
		92
		93	Reports the IBUS current supplied now. This value is generally
		94	read-only reporting, unless the 'online' state of the supply
		95	is set to be programmable, in which case this value can be set
		96	within the reported min/max range.
		97
		98	Access: Read, Write
		99
		100	Valid values: Represented in microamps. Negative values are
		101	used for discharging batteries, positive values for charging
		102	batteries and for USB IBUS current.
		103
		104	What: /sys/class/power_supply/<supply_name>/temp
		105	Date: May 2007
		106	Contact: linux-pm@vger.kernel.org
		107	Description:
		108	Battery:
		109
		110	Reports the current TBAT battery temperature reading.
		111
		112	USB:
		113
		114	Reports the current supply temperature reading. This would
		115	normally be the internal temperature of the device itself
		116	(e.g TJUNC temperature of an IC)
		117
		118	Access: Read
		119
		120	Valid values: Represented in 1/10 Degrees Celsius
		121
		122	What: /sys/class/power_supply/<supply_name>/temp_alert_max
		123	Date: July 2012
		124	Contact: linux-pm@vger.kernel.org
		125	Description:
		126	Battery:
		127
		128	Maximum TBAT temperature trip-wire value where the supply will
		129	notify user-space of the event.
		130
		131	USB:
		132
		133	Maximum supply temperature trip-wire value where the supply
		134	will notify user-space of the event.
		135
		136	This is normally used for the charging scenario where
		137	user-space needs to know if the temperature has crossed an
		138	upper threshold so it can take appropriate action (e.g. warning
		139	user that the temperature is critically high, and charging has
		140	stopped).
		141
		142	Access: Read
		143
		144	Valid values: Represented in 1/10 Degrees Celsius
		145
		146	What: /sys/class/power_supply/<supply_name>/temp_alert_min
		147	Date: July 2012
		148	Contact: linux-pm@vger.kernel.org
		149	Description:
		150
		151	Battery:
		152
		153	Minimum TBAT temperature trip-wire value where the supply will
		154	notify user-space of the event.
		155
		156	USB:
		157
		158	Minimum supply temperature trip-wire value where the supply
		159	will notify user-space of the event.
		160
		161	This is normally used for the charging scenario where user-space
		162	needs to know if the temperature has crossed a lower threshold
		163	so it can take appropriate action (e.g. warning user that
		164	temperature level is high, and charging current has been
		165	reduced accordingly to remedy the situation).
		166
		167	Access: Read
		168
		169	Valid values: Represented in 1/10 Degrees Celsius
		170
		171	What: /sys/class/power_supply/<supply_name>/temp_max
		172	Date: July 2014
		173	Contact: linux-pm@vger.kernel.org
		174	Description:
		175	Battery:
		176
		177	Reports the maximum allowed TBAT battery temperature for
		178	charging.
		179
		180	USB:
		181
		182	Reports the maximum allowed supply temperature for operation.
		183
		184	Access: Read
		185
		186	Valid values: Represented in 1/10 Degrees Celsius
		187
		188	What: /sys/class/power_supply/<supply_name>/temp_min
		189	Date: July 2014
		190	Contact: linux-pm@vger.kernel.org
		191	Description:
		192	Battery:
		193
		194	Reports the minimum allowed TBAT battery temperature for
		195	charging.
		196
		197	USB:
		198
		199	Reports the minimum allowed supply temperature for operation.
		200
		201	Access: Read
		202
		203	Valid values: Represented in 1/10 Degrees Celsius
		204
		205	What: /sys/class/power_supply/<supply_name>/voltage_max,
		206	Date: January 2008
		207	Contact: linux-pm@vger.kernel.org
		208	Description:
		209	Battery:
		210
		211	Reports the maximum safe VBAT voltage permitted for the
		212	battery, during charging.
		213
		214	USB:
		215
		216	Reports the maximum VBUS voltage the supply can support.
		217
		218	Access: Read
		219
		220	Valid values: Represented in microvolts
		221
		222	What: /sys/class/power_supply/<supply_name>/voltage_min,
		223	Date: January 2008
		224	Contact: linux-pm@vger.kernel.org
		225	Description:
		226	Battery:
		227
		228	Reports the minimum safe VBAT voltage permitted for the
		229	battery, during discharging.
		230
		231	USB:
		232
		233	Reports the minimum VBUS voltage the supply can support.
		234
		235	Access: Read
		236
		237	Valid values: Represented in microvolts
		238
		239	What: /sys/class/power_supply/<supply_name>/voltage_now,
		240	Date: May 2007
		241	Contact: linux-pm@vger.kernel.org
		242	Description:
		243	Battery:
		244
		245	Reports an instant, single VBAT voltage reading for the
		246	battery. This value is not averaged/smoothed.
		247
		248	Access: Read
		249
		250	USB:
		251
		252	Reports the VBUS voltage supplied now. This value is generally
		253	read-only reporting, unless the 'online' state of the supply
		254	is set to be programmable, in which case this value can be set
		255	within the reported min/max range.
		256
		257	Access: Read, Write
		258
		259	Valid values: Represented in microvolts
		260
		261	Battery Properties
40		262
41	What: /sys/class/power_supply/<supply_name>/capacity	263	What: /sys/class/power_supply/<supply_name>/capacity
42	Date: May 2007	264	Date: May 2007
43	Contact: linux-pm@vger.kernel.org	265	Contact: linux-pm@vger.kernel.org
44	Description:	266	Description:
45	Fine grain representation of battery capacity.	267	Fine grain representation of battery capacity.
		268
46	Access: Read	269	Access: Read
		270
47	Valid values: 0 - 100 (percent)	271	Valid values: 0 - 100 (percent)
48		272
49	What: /sys/class/power_supply/<supply_name>/capacity_alert_max	273	What: /sys/class/power_supply/<supply_name>/capacity_alert_max
@@ -58,6 +282,7 @@ Description: · 8 unmodified lines
58	low).	282	low).
59		283
60	Access: Read, Write	284	Access: Read, Write
		285
61	Valid values: 0 - 100 (percent)	286	Valid values: 0 - 100 (percent)
62		287
63	What: /sys/class/power_supply/<supply_name>/capacity_alert_min	288	What: /sys/class/power_supply/<supply_name>/capacity_alert_min
@@ -72,6 +297,7 @@ Description: · 8 unmodified lines
72	critically low).	297	critically low).
73		298
74	Access: Read, Write	299	Access: Read, Write
		300
75	Valid values: 0 - 100 (percent)	301	Valid values: 0 - 100 (percent)
76		302
77	What: /sys/class/power_supply/<supply_name>/capacity_error_margin	303	What: /sys/class/power_supply/<supply_name>/capacity_error_margin
@@ -87,6 +313,7 @@ Description: · 9 unmodified lines
87	completely useless.	313	completely useless.
88		314
89	Access: Read	315	Access: Read
		316
90	Valid values: 0 - 100 (percent)	317	Valid values: 0 - 100 (percent)
91		318
92	What: /sys/class/power_supply/<supply_name>/capacity_level	319	What: /sys/class/power_supply/<supply_name>/capacity_level
@@ -96,40 +323,10 @@ Description: · 3 unmodified lines
96	Coarse representation of battery capacity.	323	Coarse representation of battery capacity.
97		324
98	Access: Read	325	Access: Read
99	Valid values: "Unknown", "Critical", "Low", "Normal", "High",
100	"Full"
101
102	What: /sys/class/power_supply/<supply_name>/current_avg
103	Date: May 2007
104	Contact: linux-pm@vger.kernel.org
105	Description:
106	Reports an average IBAT current reading for the battery, over a
107	fixed period. Normally devices will provide a fixed interval in
108	which they average readings to smooth out the reported value.
109
110	Access: Read
111	Valid values: Represented in microamps. Negative values are used
112	for discharging batteries, positive values for charging batteries.
113		326
114	What: /sys/class/power_supply/<supply_name>/current_max	327	Valid values:
115	Date: October 2010	328	"Unknown", "Critical", "Low", "Normal", "High",
116	Contact: linux-pm@vger.kernel.org	329	"Full"
117	Description:
118	Reports the maximum IBAT current allowed into the battery.
119
120	Access: Read
121	Valid values: Represented in microamps
122
123	What: /sys/class/power_supply/<supply_name>/current_now
124	Date: May 2007
125	Contact: linux-pm@vger.kernel.org
126	Description:
127	Reports an instant, single IBAT current reading for the battery.
128	This value is not averaged/smoothed.
129
130	Access: Read
131	Valid values: Represented in microamps. Negative values are used
132	for discharging batteries, positive values for charging batteries.
133		330
134	What: /sys/class/power_supply/<supply_name>/charge_control_limit	331	What: /sys/class/power_supply/<supply_name>/charge_control_limit
135	Date: Oct 2012	332	Date: Oct 2012
@@ -139,6 +336,7 @@ Description: · 3 unmodified lines
139	throttling for thermal cooling or improving battery health.	336	throttling for thermal cooling or improving battery health.
140		337
141	Access: Read, Write	338	Access: Read, Write
		339
142	Valid values: Represented in microamps	340	Valid values: Represented in microamps
143		341
144	What: /sys/class/power_supply/<supply_name>/charge_control_limit_max	342	What: /sys/class/power_supply/<supply_name>/charge_control_limit_max
@@ -148,6 +346,7 @@ Description: · 3 unmodified lines
148	Maximum legal value for the charge_control_limit property.	346	Maximum legal value for the charge_control_limit property.
149		347
150	Access: Read	348	Access: Read
		349
151	Valid values: Represented in microamps	350	Valid values: Represented in microamps
152		351
153	What: /sys/class/power_supply/<supply_name>/charge_control_start_threshold	352	What: /sys/class/power_supply/<supply_name>/charge_control_start_threshold
@@ -168,6 +367,7 @@ Description: · 14 unmodified lines
168	stop.	367	stop.
169		368
170	Access: Read, Write	369	Access: Read, Write
		370
171	Valid values: 0 - 100 (percent)	371	Valid values: 0 - 100 (percent)
172		372
173	What: /sys/class/power_supply/<supply_name>/charge_type	373	What: /sys/class/power_supply/<supply_name>/charge_type
@@ -183,7 +383,9 @@ Description: · 9 unmodified lines
183	different algorithm.	383	different algorithm.
184		384
185	Access: Read, Write	385	Access: Read, Write
186	Valid values: "Unknown", "N/A", "Trickle", "Fast", "Standard",	386
		387	Valid values:
		388	"Unknown", "N/A", "Trickle", "Fast", "Standard",
187	"Adaptive", "Custom"	389	"Adaptive", "Custom"
188		390
189	What: /sys/class/power_supply/<supply_name>/charge_term_current	391	What: /sys/class/power_supply/<supply_name>/charge_term_current
@@ -194,6 +396,7 @@ Description: · 4 unmodified lines
194	when the battery is considered full and charging should end.	396	when the battery is considered full and charging should end.
195		397
196	Access: Read	398	Access: Read
		399
197	Valid values: Represented in microamps	400	Valid values: Represented in microamps
198		401
199	What: /sys/class/power_supply/<supply_name>/health	402	What: /sys/class/power_supply/<supply_name>/health
@@ -204,7 +407,9 @@ Description: · 4 unmodified lines
204	functionality.	407	functionality.
205		408
206	Access: Read	409	Access: Read
207	Valid values: "Unknown", "Good", "Overheat", "Dead",	410
		411	Valid values:
		412	"Unknown", "Good", "Overheat", "Dead",
208	"Over voltage", "Unspecified failure", "Cold",	413	"Over voltage", "Unspecified failure", "Cold",
209	"Watchdog timer expire", "Safety timer expire",	414	"Watchdog timer expire", "Safety timer expire",
210	"Over current", "Calibration required", "Warm",	415	"Over current", "Calibration required", "Warm",
@@ -218,6 +423,7 @@ Description: · 7 unmodified lines
218	for a battery charge cycle.	423	for a battery charge cycle.
219		424
220	Access: Read	425	Access: Read
		426
221	Valid values: Represented in microamps	427	Valid values: Represented in microamps
222		428
223	What: /sys/class/power_supply/<supply_name>/present	429	What: /sys/class/power_supply/<supply_name>/present
@@ -227,9 +433,13 @@ Description: · 3 unmodified lines
227	Reports whether a battery is present or not in the system.	433	Reports whether a battery is present or not in the system.
228		434
229	Access: Read	435	Access: Read
		436
230	Valid values:	437	Valid values:
		438
		439	== =======
231	0: Absent	440	0: Absent
232	1: Present	441	1: Present
		442	== =======
233		443
234	What: /sys/class/power_supply/<supply_name>/status	444	What: /sys/class/power_supply/<supply_name>/status
235	Date: May 2007	445	Date: May 2007
@@ -240,7 +450,9 @@ Description: · 4 unmodified lines
240	used to enable/disable charging to the battery.	450	used to enable/disable charging to the battery.
241		451
242	Access: Read, Write	452	Access: Read, Write
243	Valid values: "Unknown", "Charging", "Discharging",	453
		454	Valid values:
		455	"Unknown", "Charging", "Discharging",
244	"Not charging", "Full"	456	"Not charging", "Full"
245		457
246	What: /sys/class/power_supply/<supply_name>/technology	458	What: /sys/class/power_supply/<supply_name>/technology
@@ -250,66 +462,11 @@ Description: · 3 unmodified lines
250	Describes the battery technology supported by the supply.	462	Describes the battery technology supported by the supply.
251		463
252	Access: Read	464	Access: Read
253	Valid values: "Unknown", "NiMH", "Li-ion", "Li-poly", "LiFe",
254	"NiCd", "LiMn"
255
256	What: /sys/class/power_supply/<supply_name>/temp
257	Date: May 2007
258	Contact: linux-pm@vger.kernel.org
259	Description:
260	Reports the current TBAT battery temperature reading.
261
262	Access: Read
263	Valid values: Represented in 1/10 Degrees Celsius
264
265	What: /sys/class/power_supply/<supply_name>/temp_alert_max
266	Date: July 2012
267	Contact: linux-pm@vger.kernel.org
268	Description:
269	Maximum TBAT temperature trip-wire value where the supply will
270	notify user-space of the event. This is normally used for the
271	battery charging scenario where user-space needs to know the
272	battery temperature has crossed an upper threshold so it can
273	take appropriate action (e.g. warning user that battery level is
274	critically high, and charging has stopped).
275
276	Access: Read
277	Valid values: Represented in 1/10 Degrees Celsius
278
279	What: /sys/class/power_supply/<supply_name>/temp_alert_min
280	Date: July 2012
281	Contact: linux-pm@vger.kernel.org
282	Description:
283	Minimum TBAT temperature trip-wire value where the supply will
284	notify user-space of the event. This is normally used for the
285	battery charging scenario where user-space needs to know the
286	battery temperature has crossed a lower threshold so it can take
287	appropriate action (e.g. warning user that battery level is
288	high, and charging current has been reduced accordingly to
289	remedy the situation).
290
291	Access: Read
292	Valid values: Represented in 1/10 Degrees Celsius
293
294	What: /sys/class/power_supply/<supply_name>/temp_max
295	Date: July 2014
296	Contact: linux-pm@vger.kernel.org
297	Description:
298	Reports the maximum allowed TBAT battery temperature for
299	charging.
300
301	Access: Read
302	Valid values: Represented in 1/10 Degrees Celsius
303		465
304	What: /sys/class/power_supply/<supply_name>/temp_min	466	Valid values:
305	Date: July 2014	467	"Unknown", "NiMH", "Li-ion", "Li-poly", "LiFe",
306	Contact: linux-pm@vger.kernel.org	468	"NiCd", "LiMn"
307	Description:
308	Reports the minimum allowed TBAT battery temperature for
309	charging.
310		469
311	Access: Read
312	Valid values: Represented in 1/10 Degrees Celsius
313		470
314	What: /sys/class/power_supply/<supply_name>/voltage_avg,	471	What: /sys/class/power_supply/<supply_name>/voltage_avg,
315	Date: May 2007	472	Date: May 2007
@@ -320,72 +477,10 @@ Description: · 4 unmodified lines
320	which they average readings to smooth out the reported value.	477	which they average readings to smooth out the reported value.
321		478
322	Access: Read	479	Access: Read
323	Valid values: Represented in microvolts
324
325	What: /sys/class/power_supply/<supply_name>/voltage_max,
326	Date: January 2008
327	Contact: linux-pm@vger.kernel.org
328	Description:
329	Reports the maximum safe VBAT voltage permitted for the battery,
330	during charging.
331
332	Access: Read
333	Valid values: Represented in microvolts
334
335	What: /sys/class/power_supply/<supply_name>/voltage_min,
336	Date: January 2008
337	Contact: linux-pm@vger.kernel.org
338	Description:
339	Reports the minimum safe VBAT voltage permitted for the battery,
340	during discharging.
341		480
342	Access: Read
343	Valid values: Represented in microvolts	481	Valid values: Represented in microvolts
344		482
345	What: /sys/class/power_supply/<supply_name>/voltage_now,	483	USB Properties
346	Date: May 2007
347	Contact: linux-pm@vger.kernel.org
348	Description:
349	Reports an instant, single VBAT voltage reading for the battery.
350	This value is not averaged/smoothed.
351
352	Access: Read
353	Valid values: Represented in microvolts
354
355	===== USB Properties =====
356
357	What: /sys/class/power_supply/<supply_name>/current_avg
358	Date: May 2007
359	Contact: linux-pm@vger.kernel.org
360	Description:
361	Reports an average IBUS current reading over a fixed period.
362	Normally devices will provide a fixed interval in which they
363	average readings to smooth out the reported value.
364
365	Access: Read
366	Valid values: Represented in microamps
367
368
369	What: /sys/class/power_supply/<supply_name>/current_max
370	Date: October 2010
371	Contact: linux-pm@vger.kernel.org
372	Description:
373	Reports the maximum IBUS current the supply can support.
374
375	Access: Read
376	Valid values: Represented in microamps
377
378	What: /sys/class/power_supply/<supply_name>/current_now
379	Date: May 2007
380	Contact: linux-pm@vger.kernel.org
381	Description:
382	Reports the IBUS current supplied now. This value is generally
383	read-only reporting, unless the 'online' state of the supply
384	is set to be programmable, in which case this value can be set
385	within the reported min/max range.
386
387	Access: Read, Write
388	Valid values: Represented in microamps
389		484
390	What: /sys/class/power_supply/<supply_name>/input_current_limit	485	What: /sys/class/power_supply/<supply_name>/input_current_limit
391	Date: July 2014	486	Date: July 2014
@@ -399,6 +494,7 @@ Description: · 7 unmodified lines
399	solved using power limit use input_current_limit.	494	solved using power limit use input_current_limit.
400		495
401	Access: Read, Write	496	Access: Read, Write
		497
402	Valid values: Represented in microamps	498	Valid values: Represented in microamps
403		499
404	What: /sys/class/power_supply/<supply_name>/input_voltage_limit	500	What: /sys/class/power_supply/<supply_name>/input_voltage_limit
@@ -416,6 +512,7 @@ Description: · 11 unmodified lines
416	solved using power limit use input_voltage_limit.	512	solved using power limit use input_voltage_limit.
417		513
418	Access: Read, Write	514	Access: Read, Write
		515
419	Valid values: Represented in microvolts	516	Valid values: Represented in microvolts
420		517
421	What: /sys/class/power_supply/<supply_name>/input_power_limit	518	What: /sys/class/power_supply/<supply_name>/input_power_limit
@@ -429,6 +526,7 @@ Description: · 7 unmodified lines
429	limit only for problems that can be solved using power limit.	526	limit only for problems that can be solved using power limit.
430		527
431	Access: Read, Write	528	Access: Read, Write
		529
432	Valid values: Represented in microwatts	530	Valid values: Represented in microwatts
433		531
434	What: /sys/class/power_supply/<supply_name>/online,	532	What: /sys/class/power_supply/<supply_name>/online,
@@ -441,69 +539,14 @@ Description: · 6 unmodified lines
441	USB supply so voltage and current can be controlled).	539	USB supply so voltage and current can be controlled).
442		540
443	Access: Read, Write	541	Access: Read, Write
		542
444	Valid values:	543	Valid values:
		544
		545	== ==================================================
445	0: Offline	546	0: Offline
446	1: Online Fixed - Fixed Voltage Supply	547	1: Online Fixed - Fixed Voltage Supply
447	2: Online Programmable - Programmable Voltage Supply	548	2: Online Programmable - Programmable Voltage Supply
448		549	== ==================================================
449	What: /sys/class/power_supply/<supply_name>/temp
450	Date: May 2007
451	Contact: linux-pm@vger.kernel.org
452	Description:
453	Reports the current supply temperature reading. This would
454	normally be the internal temperature of the device itself (e.g
455	TJUNC temperature of an IC)
456
457	Access: Read
458	Valid values: Represented in 1/10 Degrees Celsius
459
460	What: /sys/class/power_supply/<supply_name>/temp_alert_max
461	Date: July 2012
462	Contact: linux-pm@vger.kernel.org
463	Description:
464	Maximum supply temperature trip-wire value where the supply will
465	notify user-space of the event. This is normally used for the
466	charging scenario where user-space needs to know the supply
467	temperature has crossed an upper threshold so it can take
468	appropriate action (e.g. warning user that the supply
469	temperature is critically high, and charging has stopped to
470	remedy the situation).
471
472	Access: Read
473	Valid values: Represented in 1/10 Degrees Celsius
474
475	What: /sys/class/power_supply/<supply_name>/temp_alert_min
476	Date: July 2012
477	Contact: linux-pm@vger.kernel.org
478	Description:
479	Minimum supply temperature trip-wire value where the supply will
480	notify user-space of the event. This is normally used for the
481	charging scenario where user-space needs to know the supply
482	temperature has crossed a lower threshold so it can take
483	appropriate action (e.g. warning user that the supply
484	temperature is high, and charging current has been reduced
485	accordingly to remedy the situation).
486
487	Access: Read
488	Valid values: Represented in 1/10 Degrees Celsius
489
490	What: /sys/class/power_supply/<supply_name>/temp_max
491	Date: July 2014
492	Contact: linux-pm@vger.kernel.org
493	Description:
494	Reports the maximum allowed supply temperature for operation.
495
496	Access: Read
497	Valid values: Represented in 1/10 Degrees Celsius
498
499	What: /sys/class/power_supply/<supply_name>/temp_min
500	Date: July 2014
501	Contact: linux-pm@vger.kernel.org
502	Description:
503	Reports the mainimum allowed supply temperature for operation.
504
505	Access: Read
506	Valid values: Represented in 1/10 Degrees Celsius
507		550
508	What: /sys/class/power_supply/<supply_name>/usb_type	551	What: /sys/class/power_supply/<supply_name>/usb_type
509	Date: March 2018	552	Date: March 2018
@@ -514,40 +557,12 @@ Description: · 4 unmodified lines
514	is attached.	557	is attached.
515		558
516	Access: Read-Only	559	Access: Read-Only
517	Valid values: "Unknown", "SDP", "DCP", "CDP", "ACA", "C", "PD",
518	"PD_DRP", "PD_PPS", "BrickID"
519
520	What: /sys/class/power_supply/<supply_name>/voltage_max
521	Date: January 2008
522	Contact: linux-pm@vger.kernel.org
523	Description:
524	Reports the maximum VBUS voltage the supply can support.
525
526	Access: Read
527	Valid values: Represented in microvolts
528
529	What: /sys/class/power_supply/<supply_name>/voltage_min
530	Date: January 2008
531	Contact: linux-pm@vger.kernel.org
532	Description:
533	Reports the minimum VBUS voltage the supply can support.
534		560
535	Access: Read	561	Valid values:
536	Valid values: Represented in microvolts	562	"Unknown", "SDP", "DCP", "CDP", "ACA", "C", "PD",
537		563	"PD_DRP", "PD_PPS", "BrickID"
538	What: /sys/class/power_supply/<supply_name>/voltage_now
539	Date: May 2007
540	Contact: linux-pm@vger.kernel.org
541	Description:
542	Reports the VBUS voltage supplied now. This value is generally
543	read-only reporting, unless the 'online' state of the supply
544	is set to be programmable, in which case this value can be set
545	within the reported min/max range.
546
547	Access: Read, Write
548	Valid values: Represented in microvolts
549		564
550	===== Device Specific Properties =====	565	Device Specific Properties
551		566
552	What: /sys/class/power/ds2760-battery.*/charge_now	567	What: /sys/class/power/ds2760-battery.*/charge_now
553	Date: May 2010	568	Date: May 2010
@@ -581,6 +596,7 @@ Description: · 27 unmodified lines
581	will drop to 0 A) and will trigger interrupt.	596	will drop to 0 A) and will trigger interrupt.
582		597
583	Valid values:	598	Valid values:
		599
584	- 5, 6 or 7 (hours),	600	- 5, 6 or 7 (hours),
585	- 0: disabled.	601	- 0: disabled.
586		602
@@ -595,6 +611,7 @@ Description: · 8 unmodified lines
595	will drop to 0 A) and will trigger interrupt.	611	will drop to 0 A) and will trigger interrupt.
596		612
597	Valid values:	613	Valid values:
		614
598	- 4 - 16 (hours), step by 2 (rounded down)	615	- 4 - 16 (hours), step by 2 (rounded down)
599	- 0: disabled.	616	- 0: disabled.
600		617
@@ -609,6 +626,7 @@ Description: · 8 unmodified lines
609	interrupt and start top-off charging mode.	626	interrupt and start top-off charging mode.
610		627
611	Valid values:	628	Valid values:
		629
612	- 100000 - 200000 (microamps), step by 25000 (rounded down)	630	- 100000 - 200000 (microamps), step by 25000 (rounded down)
613	- 200000 - 350000 (microamps), step by 50000 (rounded down)	631	- 200000 - 350000 (microamps), step by 50000 (rounded down)
614	- 0: disabled.	632	- 0: disabled.
@@ -624,6 +642,7 @@ Description: · 9 unmodified lines
624	will drop to 0 A) and will trigger interrupt.	642	will drop to 0 A) and will trigger interrupt.
625		643
626	Valid values:	644	Valid values:
		645
627	- 0 - 70 (minutes), step by 10 (rounded down)	646	- 0 - 70 (minutes), step by 10 (rounded down)
628		647
629	What: /sys/class/power_supply/bq24257-charger/ovp_voltage	648	What: /sys/class/power_supply/bq24257-charger/ovp_voltage
@@ -637,6 +656,7 @@ Description: · 7 unmodified lines
637	device datasheet for details.	656	device datasheet for details.
638		657
639	Valid values:	658	Valid values:
		659
640	- 6000000, 6500000, 7000000, 8000000, 9000000, 9500000, 10000000,	660	- 6000000, 6500000, 7000000, 8000000, 9000000, 9500000, 10000000,
641	10500000 (all uV)	661	10500000 (all uV)
642		662
@@ -652,6 +672,7 @@ Description: · 9 unmodified lines
652	lower than the set value. See device datasheet for details.	672	lower than the set value. See device datasheet for details.
653		673
654	Valid values:	674	Valid values:
		675
655	- 4200000, 4280000, 4360000, 4440000, 4520000, 4600000, 4680000,	676	- 4200000, 4280000, 4360000, 4440000, 4520000, 4600000, 4680000,
656	4760000 (all uV)	677	4760000 (all uV)
657		678
@@ -666,6 +687,7 @@ Description: · 8 unmodified lines
666	the charger operates normally. See device datasheet for details.	687	the charger operates normally. See device datasheet for details.
667		688
668	Valid values:	689	Valid values:
		690
669	- 1: enabled	691	- 1: enabled
670	- 0: disabled	692	- 0: disabled
671		693
@@ -681,6 +703,7 @@ Description: · 9 unmodified lines
681	from the system. See device datasheet for details.	703	from the system. See device datasheet for details.
682		704
683	Valid values:	705	Valid values:
		706
684	- 1: enabled	707	- 1: enabled
685	- 0: disabled	708	- 0: disabled
686		709
@@ -692,6 +715,7 @@ Description: · 5 unmodified lines
692	manufactured.	715	manufactured.
693		716
694	Access: Read	717	Access: Read
		718
695	Valid values: Reported as integer	719	Valid values: Reported as integer
696		720
697	What: /sys/class/power_supply/<supply_name>/manufacture_month	721	What: /sys/class/power_supply/<supply_name>/manufacture_month
@@ -701,6 +725,7 @@ Description: · 3 unmodified lines
701	Reports the month when the device has been manufactured.	725	Reports the month when the device has been manufactured.
702		726
703	Access: Read	727	Access: Read
		728
704	Valid values: 1-12	729	Valid values: 1-12
705		730
706	What: /sys/class/power_supply/<supply_name>/manufacture_day	731	What: /sys/class/power_supply/<supply_name>/manufacture_day

Documentation/ABI/testing/sysfs-class-power-mp2629+1−0

@@ -5,4 +5,5 @@ Description: · 4 unmodified lines
5	Represents a battery impedance compensation to accelerate charging.	5	Represents a battery impedance compensation to accelerate charging.
6		6
7	Access: Read, Write	7	Access: Read, Write
		8
8	Valid values: Represented in milli-ohms. Valid range is [0, 140].	9	Valid values: Represented in milli-ohms. Valid range is [0, 140].

Documentation/ABI/testing/sysfs-class-power-twl4030+19−14

@@ -4,18 +4,20 @@ Description: · 3 unmodified lines
4	Writing to this can disable charging.	4	Writing to this can disable charging.
5		5
6	Possible values are:	6	Possible values are:
7	"auto" - draw power as appropriate for detected
8	power source and battery status.
9	"off" - do not draw any power.
10	"continuous"
11	- activate mode described as "linear" in
12	TWL data sheets. This uses whatever
13	current is available and doesn't switch off
14	when voltage drops.
15		7
16	This is useful for unstable power sources	8	============= ===========================================
17	such as bicycle dynamo, but care should	9	"auto" draw power as appropriate for detected
18	be taken that battery is not over-charged.	10	power source and battery status.
		11	"off" do not draw any power.
		12	"continuous" activate mode described as "linear" in
		13	TWL data sheets. This uses whatever
		14	current is available and doesn't switch off
		15	when voltage drops.
		16
		17	This is useful for unstable power sources
		18	such as bicycle dynamo, but care should
		19	be taken that battery is not over-charged.
		20	============= ===========================================
19		21
20	What: /sys/class/power_supply/twl4030_ac/mode	22	What: /sys/class/power_supply/twl4030_ac/mode
21	Description:	23	Description:
@@ -23,6 +25,9 @@ Description: · 1 unmodified line
23	Writing to this can disable charging.	25	Writing to this can disable charging.
24		26
25	Possible values are:	27	Possible values are:
26	"auto" - draw power as appropriate for detected	28
27	power source and battery status.	29	====== ===========================================
28	"off" - do not draw any power.	30	"auto" draw power as appropriate for detected
		31	power source and battery status.
		32	"off" do not draw any power.
		33	====== ===========================================

Documentation/ABI/testing/sysfs-class-power-wilco+12−6

 Description:
 		What charging algorithm to use:
-		Standard: Fully charges battery at a standard rate.
+		Standard:
-		Adaptive: Battery settings adaptively optimized based on
+			Fully charges battery at a standard rate.
+		Adaptive:
+			Battery settings adaptively optimized based on
 			typical battery usage pattern.
-		Fast: Battery charges over a shorter period.
+		Fast:
-		Trickle: Extends battery lifespan, intended for users who
+			Battery charges over a shorter period.
+		Trickle:
+			Extends battery lifespan, intended for users who
 			primarily use their Chromebook while connected to AC.
-		Custom: A low and high threshold percentage is specified.
+		Custom:
+			A low and high threshold percentage is specified.
 			Charging begins when level drops below
 			charge_control_start_threshold, and ceases when
 			level is above charge_control_end_threshold.
-		Long Life: Customized charge rate for last longer battery life.
+		Long Life:
+			Customized charge rate for last longer battery life.
 			On Wilco device this mode is pre-configured in the factory
 			through EC's private PID. Swiching to a different mode will
 			be denied by Wilco EC when Long Life mode is enabled.

Documentation/ABI/testing/sysfs-class-rapidio+26−22

Documentation/ABI/testing/sysfs-class-rc+28−2

Documentation/ABI/testing/sysfs-class-regulator+18−18

@@ -35,13 +35,13 @@ Description: · 34 unmodified lines
35		35
36	This will be one of the following strings:	36	This will be one of the following strings:
37		37
38	off	38	- off
39	on	39	- on
40	error	40	- error
41	fast	41	- fast
42	normal	42	- normal
43	idle	43	- idle
44	standby	44	- standby
45		45
46	"off" means the regulator is not supplying power to the	46	"off" means the regulator is not supplying power to the
47	system.	47	system.
@@ -74,9 +74,9 @@ Description: · 26 unmodified lines
74		74
75	This will be one of the following strings:	75	This will be one of the following strings:
76		76
77	'voltage'	77	- 'voltage'
78	'current'	78	- 'current'
79	'unknown'	79	- 'unknown'
80		80
81	'voltage' means the regulator output voltage can be controlled	81	'voltage' means the regulator output voltage can be controlled
82	by software.	82	by software.
@@ -129,11 +129,11 @@ Description: · 46 unmodified lines
129		129
130	The opmode value can be one of the following strings:	130	The opmode value can be one of the following strings:
131		131
132	'fast'	132	- 'fast'
133	'normal'	133	- 'normal'
134	'idle'	134	- 'idle'
135	'standby'	135	- 'standby'
136	'unknown'	136	- 'unknown'
137		137
138	The modes are described in include/linux/regulator/consumer.h	138	The modes are described in include/linux/regulator/consumer.h
139		139
@@ -360,9 +360,9 @@ Description: · 220 unmodified lines
360		360
361	This will be one of the following strings:	361	This will be one of the following strings:
362		362
363	'enabled'	363	- 'enabled'
364	'disabled'	364	- 'disabled'
365	'unknown'	365	- 'unknown'
366		366
367	'enabled' means the regulator is in bypass mode.	367	'enabled' means the regulator is in bypass mode.
368		368

Documentation/ABI/testing/sysfs-class-remoteproc+7−7

@@ -16,11 +16,11 @@ Description: Remote processor state · 15 unmodified lines
16		16
17	Reports the state of the remote processor, which will be one of:	17	Reports the state of the remote processor, which will be one of:
18		18
19	"offline"	19	- "offline"
20	"suspended"	20	- "suspended"
21	"running"	21	- "running"
22	"crashed"	22	- "crashed"
23	"invalid"	23	- "invalid"
24		24
25	"offline" means the remote processor is powered off.	25	"offline" means the remote processor is powered off.
26		26
@@ -38,8 +38,8 @@ Description: Remote processor state · 11 unmodified lines
38	Writing this file controls the state of the remote processor.	38	Writing this file controls the state of the remote processor.
39	The following states can be written:	39	The following states can be written:
40		40
41	"start"	41	- "start"
42	"stop"	42	- "stop"
43		43
44	Writing "start" will attempt to start the processor running the	44	Writing "start" will attempt to start the processor running the
45	firmware indicated by, or written to,	45	firmware indicated by, or written to,

Documentation/ABI/testing/sysfs-class-rnbd-client+51−42

@@ -5,62 +5,70 @@ Contact: Jack Wang <jinpu.wang@cloud.ionos.com> Danil Kipnis <danil.kipnis@cloud · 4 unmodified lines
5	Description: Provide information about RNBD-client.	5	Description: Provide information about RNBD-client.
6	All sysfs files that are not read-only provide the usage information on read:	6	All sysfs files that are not read-only provide the usage information on read:
7		7
8	Example:	8	Example::
9	# cat /sys/class/rnbd-client/ctl/map_device
10		9
11	> Usage: echo "sessname=<name of the rtrs session> path=<[srcaddr,]dstaddr>	10	# cat /sys/class/rnbd-client/ctl/map_device
12	> [path=<[srcaddr,]dstaddr>] device_path=<full path on remote side>	11
13	> [access_mode=<ro\|rw\|migration>] > map_device	12	> Usage: echo "sessname=<name of the rtrs session> path=<[srcaddr,]dstaddr>
14	>	13	> [path=<[srcaddr,]dstaddr>] device_path=<full path on remote side>
15	> addr ::= [ ip:<ipv4> \| ip:<ipv6> \| gid:<gid> ]	14	> [access_mode=<ro\|rw\|migration>] > map_device
		15	>
		16	> addr ::= [ ip:<ipv4> \| ip:<ipv6> \| gid:<gid> ]
16		17
17	What: /sys/class/rnbd-client/ctl/map_device	18	What: /sys/class/rnbd-client/ctl/map_device
18	Date: Feb 2020	19	Date: Feb 2020
19	KernelVersion: 5.7	20	KernelVersion: 5.7
20	Contact: Jack Wang <jinpu.wang@cloud.ionos.com> Danil Kipnis <danil.kipnis@cloud.ionos.com>	21	Contact: Jack Wang <jinpu.wang@cloud.ionos.com> Danil Kipnis <danil.kipnis@cloud.ionos.com>
21	Description: Expected format is the following:	22	Description: Expected format is the following::
22		23
23	sessname=<name of the rtrs session>	24	sessname=<name of the rtrs session>
24	path=<[srcaddr,]dstaddr> [path=<[srcaddr,]dstaddr> ...]	25	path=<[srcaddr,]dstaddr> [path=<[srcaddr,]dstaddr> ...]
25	device_path=<full path on remote side>	26	device_path=<full path on remote side>
26	[access_mode=<ro\|rw\|migration>]	27	[access_mode=<ro\|rw\|migration>]
27		28
28	Where:	29	Where:
29		30
30	sessname: accepts a string not bigger than 256 chars, which identifies	31	sessname:
31	a given session on the client and on the server.	32	accepts a string not bigger than 256 chars, which identifies
32	I.e. "clt_hostname-srv_hostname" could be a natural choice.	33	a given session on the client and on the server.
		34	I.e. "clt_hostname-srv_hostname" could be a natural choice.
		35
		36	path:
		37	describes a connection between the client and the server by
		38	specifying destination and, when required, the source address.
		39	The addresses are to be provided in the following format::
33		40
34	path: describes a connection between the client and the server by	41	ip:<IPv6>
35	specifying destination and, when required, the source address.	42	ip:<IPv4>
36	The addresses are to be provided in the following format:	43	gid:<GID>
37		44
38	ip:<IPv6>	45	for example::
39	ip:<IPv4>
40	gid:<GID>
41		46
42	for example:	47	path=ip:10.0.0.66
43		48
44	path=ip:10.0.0.66
45	The single addr is treated as the destination.	49	The single addr is treated as the destination.
46	The connection will be established to this server from any client IP address.	50	The connection will be established to this server from any client IP address.
47		51
48	path=ip:10.0.0.66,ip:10.0.1.66	52	::
		53
		54	path=ip:10.0.0.66,ip:10.0.1.66
		55
49	First addr is the source address and the second is the destination.	56	First addr is the source address and the second is the destination.
50		57
51	If multiple "path=" options are specified multiple connection	58	If multiple "path=" options are specified multiple connection
52	will be established and data will be sent according to	59	will be established and data will be sent according to
53	the selected multipath policy (see RTRS mp_policy sysfs entry description).	60	the selected multipath policy (see RTRS mp_policy sysfs entry description).
54		61
55	device_path: Path to the block device on the server side. Path is specified	62	device_path:
56	relative to the directory on server side configured in the	63	Path to the block device on the server side. Path is specified
57	'dev_search_path' module parameter of the rnbd_server.	64	relative to the directory on server side configured in the
58	The rnbd_server prepends the <device_path> received from client	65	'dev_search_path' module parameter of the rnbd_server.
59	with <dev_search_path> and tries to open the	66	The rnbd_server prepends the <device_path> received from client
60	<dev_search_path>/<device_path> block device. On success,	67	with <dev_search_path> and tries to open the
61	a /dev/rnbd<N> device file, a /sys/block/rnbd_client/rnbd<N>/	68	<dev_search_path>/<device_path> block device. On success,
62	directory and an entry in /sys/class/rnbd-client/ctl/devices	69	a /dev/rnbd<N> device file, a /sys/block/rnbd_client/rnbd<N>/
63	will be created.	70	directory and an entry in /sys/class/rnbd-client/ctl/devices
		71	will be created.
64		72
65	If 'dev_search_path' contains '%SESSNAME%', then each session can	73	If 'dev_search_path' contains '%SESSNAME%', then each session can
66	have different devices namespace, e.g. server was configured with	74	have different devices namespace, e.g. server was configured with
@@ -68,11 +76,12 @@ Description: Expected format is the following: · 1 unmodified line
68	client has this string "sessname=blya device_path=sda", then server	76	client has this string "sessname=blya device_path=sda", then server
69	will try to open: /run/rnbd-devs/blya/sda.	77	will try to open: /run/rnbd-devs/blya/sda.
70		78
71	access_mode: the access_mode parameter specifies if the device is to be	79	access_mode:
72	mapped as "ro" read-only or "rw" read-write. The server allows	80	the access_mode parameter specifies if the device is to be
73	a device to be exported in rw mode only once. The "migration"	81	mapped as "ro" read-only or "rw" read-write. The server allows
74	access mode has to be specified if a second mapping in read-write	82	a device to be exported in rw mode only once. The "migration"
75	mode is desired.	83	access mode has to be specified if a second mapping in read-write
		84	mode is desired.
76		85
77	By default "rw" is used.	86	By default "rw" is used.
78		87
@@ -91,7 +100,7 @@ Description: Expected format is the following: · 12 unmodified lines
91	is the same as the device name. By extracting the last part of the	100	is the same as the device name. By extracting the last part of the
92	path the path to the device /dev/<dev-name> can be build.	101	path the path to the device /dev/<dev-name> can be build.
93		102
94	o /dev/block/$(cat /sys/class/rnbd-client/ctl/devices/<device_id>/dev)	103	* /dev/block/$(cat /sys/class/rnbd-client/ctl/devices/<device_id>/dev)
95		104
96	How to find the <device_id> of the device is described on the next	105	How to find the <device_id> of the device is described on the next
97	section.	106	section.
@@ -106,6 +115,6 @@ Description: For each device mapped on the client a new symbolic link is created · 8 unmodified lines
106	The <device_id> of each device is created as follows:	115	The <device_id> of each device is created as follows:
107		116
108	- If the 'device_path' provided during mapping contains slashes ("/"),	117	- If the 'device_path' provided during mapping contains slashes ("/"),
109	they are replaced by exclamation mark ("!") and used as as the	118	they are replaced by exclamation mark ("!") and used as as the
110	<device_id>. Otherwise, the <device_id> will be the same as the	119	<device_id>. Otherwise, the <device_id> will be the same as the
111	"device_path" provided.	120	"device_path" provided.

Documentation/ABI/testing/sysfs-class-rtc-rtc0-device-rtc_calibration+1−0

@@ -7,6 +7,7 @@ Description: Attribute for calibrating ST-Ericsson AB8500 Real Time Clock · 6 unmodified lines
7	calibrate the AB8500.s 32KHz Real Time Clock.	7	calibrate the AB8500.s 32KHz Real Time Clock.
8	Every 60 seconds the AB8500 will correct the RTC's value	8	Every 60 seconds the AB8500 will correct the RTC's value
9	by adding to it the value of this attribute.	9	by adding to it the value of this attribute.
		10
10	The range of the attribute is -127 to +127 in units of	11	The range of the attribute is -127 to +127 in units of
11	30.5 micro-seconds (half-parts-per-million of the 32KHz clock)	12	30.5 micro-seconds (half-parts-per-million of the 32KHz clock)
12	Users: The /vendor/st-ericsson/base_utilities/core/rtc_calibration	13	Users: The /vendor/st-ericsson/base_utilities/core/rtc_calibration

Documentation/ABI/testing/sysfs-class-rtrs-client+13−10

@@ -10,10 +10,10 @@ Date: Feb 2020 · 9 unmodified lines
10	KernelVersion: 5.7	10	KernelVersion: 5.7
11	Contact: Jack Wang <jinpu.wang@cloud.ionos.com> Danil Kipnis <danil.kipnis@cloud.ionos.com>	11	Contact: Jack Wang <jinpu.wang@cloud.ionos.com> Danil Kipnis <danil.kipnis@cloud.ionos.com>
12	Description: RW, adds a new path (connection) to an existing session. Expected format is the	12	Description: RW, adds a new path (connection) to an existing session. Expected format is the
13	following:	13	following::
14		14
15	<[source addr,]destination addr>	15	<[source addr,]destination addr>
16	*addr ::= [ ip:<ipv4\|ipv6> \| gid:<gid> ]	16	*addr ::= [ ip:<ipv4\|ipv6> \| gid:<gid> ]
17		17
18	What: /sys/class/rtrs-client/<session-name>/max_reconnect_attempts	18	What: /sys/class/rtrs-client/<session-name>/max_reconnect_attempts
19	Date: Feb 2020	19	Date: Feb 2020
@@ -29,10 +29,10 @@ Contact: Jack Wang <jinpu.wang@cloud.ionos.com> Danil Kipnis <danil.kipnis@cloud · 9 unmodified lines
29	Description: Multipath policy specifies which path should be selected on each IO:	29	Description: Multipath policy specifies which path should be selected on each IO:
30		30
31	round-robin (0):	31	round-robin (0):
32	select path in per CPU round-robin manner.	32	select path in per CPU round-robin manner.
33		33
34	min-inflight (1):	34	min-inflight (1):
35	select path with minimum inflights.	35	select path with minimum inflights.
36		36
37	What: /sys/class/rtrs-client/<session-name>/paths/	37	What: /sys/class/rtrs-client/<session-name>/paths/
38	Date: Feb 2020	38	Date: Feb 2020
@@ -109,8 +109,11 @@ Description: RTRS expects that each HCA IRQ is pinned to a separate CPU. If it's · 70 unmodified lines
109	not the case, the processing of an I/O response could be processed on a	109	not the case, the processing of an I/O response could be processed on a
110	different CPU than where it was originally submitted. This file shows	110	different CPU than where it was originally submitted. This file shows
111	how many interrupts where generated on a non expected CPU.	111	how many interrupts where generated on a non expected CPU.
112	"from:" is the CPU on which the IRQ was expected, but not generated.	112
113	"to:" is the CPU on which the IRQ was generated, but not expected.	113	"from:"
		114	is the CPU on which the IRQ was expected, but not generated.
		115	"to:"
		116	is the CPU on which the IRQ was generated, but not expected.
114		117
115	What: /sys/class/rtrs-client/<session-name>/paths/<src@dst>/stats/reconnects	118	What: /sys/class/rtrs-client/<session-name>/paths/<src@dst>/stats/reconnects
116	Date: Feb 2020	119	Date: Feb 2020
@@ -125,7 +128,7 @@ Date: Feb 2020 · 8 unmodified lines
125	KernelVersion: 5.7	128	KernelVersion: 5.7
126	Contact: Jack Wang <jinpu.wang@cloud.ionos.com> Danil Kipnis <danil.kipnis@cloud.ionos.com>	129	Contact: Jack Wang <jinpu.wang@cloud.ionos.com> Danil Kipnis <danil.kipnis@cloud.ionos.com>
127	Description: Contains statistics regarding rdma operations and inflight operations.	130	Description: Contains statistics regarding rdma operations and inflight operations.
128	The output consists of 6 values:	131	The output consists of 6 values::
129		132
130	<read-count> <read-total-size> <write-count> <write-total-size> \	133	<read-count> <read-total-size> <write-count> \
131	<inflights> <failovered>	134	<write-total-size> <inflights> <failovered>

Documentation/ABI/testing/sysfs-class-scsi_host+4−3

Documentation/ABI/testing/sysfs-class-typec+9−3

@@ -40,10 +40,13 @@ Description: · 39 unmodified lines
40	attribute will not return until the operation has finished.	40	attribute will not return until the operation has finished.
41		41
42	Valid values:	42	Valid values:
43	- source (The port will behave as source only DFP port)	43
44	- sink (The port will behave as sink only UFP port)	44	====== ==============================================
45	- dual (The port will behave as dual-role-data and	45	source (The port will behave as source only DFP port)
		46	sink (The port will behave as sink only UFP port)
		47	dual (The port will behave as dual-role-data and
46	dual-role-power port)	48	dual-role-power port)
		49	====== ==============================================
47		50
48	What: /sys/class/typec/<port>/vconn_source	51	What: /sys/class/typec/<port>/vconn_source
49	Date: April 2017	52	Date: April 2017
@@ -59,6 +62,7 @@ Description: · 9 unmodified lines
59	generates uevent KOBJ_CHANGE.	62	generates uevent KOBJ_CHANGE.
60		63
61	Valid values:	64	Valid values:
		65
62	- "no" when the port is not the VCONN Source	66	- "no" when the port is not the VCONN Source
63	- "yes" when the port is the VCONN Source	67	- "yes" when the port is the VCONN Source
64		68
@@ -72,6 +76,7 @@ Description: · 7 unmodified lines
72	power operation mode should show "usb_power_delivery".	76	power operation mode should show "usb_power_delivery".
73		77
74	Valid values:	78	Valid values:
		79
75	- default	80	- default
76	- 1.5A	81	- 1.5A
77	- 3.0A	82	- 3.0A
@@ -191,6 +196,7 @@ Date: April 2017 · 113 unmodified lines
191	Contact: Heikki Krogerus <heikki.krogerus@linux.intel.com>	196	Contact: Heikki Krogerus <heikki.krogerus@linux.intel.com>
192	Description:	197	Description:
193	Shows type of the plug on the cable:	198	Shows type of the plug on the cable:
		199
194	- type-a - Standard A	200	- type-a - Standard A
195	- type-b - Standard B	201	- type-b - Standard B
196	- type-c	202	- type-c

Documentation/ABI/testing/sysfs-class-uwb_rc+8−5

@@ -66,11 +66,14 @@ Description: · 65 unmodified lines
66	<channel> <type> [<bpst offset>]	66	<channel> <type> [<bpst offset>]
67		67
68	to start (or stop) scanning on a channel. <type> is one of:	68	to start (or stop) scanning on a channel. <type> is one of:
69	0 - scan	69
70	1 - scan outside BP	70	== =======================================
71	2 - scan while inactive	71	0 scan
72	3 - scanning disabled	72	1 scan outside BP
73	4 - scan (with start time of <bpst offset>)	73	2 scan while inactive
		74	3 scanning disabled
		75	4 scan (with start time of <bpst offset>)
		76	== =======================================
74		77
75	What: /sys/class/uwb_rc/uwbN/mac_address	78	What: /sys/class/uwb_rc/uwbN/mac_address
76	Date: July 2008	79	Date: July 2008

Documentation/ABI/testing/sysfs-class-watchdog+5−2

@@ -91,10 +91,13 @@ Description: · 90 unmodified lines
91	h/w strapping (for WDT2 only).	91	h/w strapping (for WDT2 only).
92		92
93	At alternate flash the 'access_cs0' sysfs node provides:	93	At alternate flash the 'access_cs0' sysfs node provides:
94	ast2400: a way to get access to the primary SPI flash	94
		95	ast2400:
		96	a way to get access to the primary SPI flash
95	chip at CS0 after booting from the alternate	97	chip at CS0 after booting from the alternate
96	chip at CS1.	98	chip at CS1.
97	ast2500: a way to restore the normal address mapping	99	ast2500:
		100	a way to restore the normal address mapping
98	from (CS0->CS1, CS1->CS0) to (CS0->CS0,	101	from (CS0->CS1, CS1->CS0) to (CS0->CS0,
99	CS1->CS1).	102	CS1->CS1).
100		103

Documentation/ABI/testing/sysfs-dev+4−3

@@ -9,9 +9,10 @@ Description: The /sys/dev tree provides a method to look up the sysfs · 8 unmodified lines
9	the form "<major>:<minor>". These links point to the	9	the form "<major>:<minor>". These links point to the
10	corresponding sysfs path for the given device.	10	corresponding sysfs path for the given device.
11		11
12	Example:	12	Example::
13	$ readlink /sys/dev/block/8:32	13
14	../../block/sdc	14	$ readlink /sys/dev/block/8:32
		15	../../block/sdc
15		16
16	Entries in /sys/dev/char and /sys/dev/block will be	17	Entries in /sys/dev/char and /sys/dev/block will be
17	dynamically created and destroyed as devices enter and	18	dynamically created and destroyed as devices enter and

Documentation/ABI/testing/sysfs-devices-mapping+21−20

@@ -8,26 +8,27 @@ Description: · 7 unmodified lines
8	block.	8	block.
9	For example, on 4-die Xeon platform with up to 6 IIO stacks per	9	For example, on 4-die Xeon platform with up to 6 IIO stacks per
10	die and, therefore, 6 IIO PMON blocks per die, the mapping of	10	die and, therefore, 6 IIO PMON blocks per die, the mapping of
11	IIO PMON block 0 exposes as the following:	11	IIO PMON block 0 exposes as the following::
12		12
13	$ ls /sys/devices/uncore_iio_0/die*	13	$ ls /sys/devices/uncore_iio_0/die*
14	-r--r--r-- /sys/devices/uncore_iio_0/die0	14	-r--r--r-- /sys/devices/uncore_iio_0/die0
15	-r--r--r-- /sys/devices/uncore_iio_0/die1	15	-r--r--r-- /sys/devices/uncore_iio_0/die1
16	-r--r--r-- /sys/devices/uncore_iio_0/die2	16	-r--r--r-- /sys/devices/uncore_iio_0/die2
17	-r--r--r-- /sys/devices/uncore_iio_0/die3	17	-r--r--r-- /sys/devices/uncore_iio_0/die3
18		18
19	$ tail /sys/devices/uncore_iio_0/die*	19	$ tail /sys/devices/uncore_iio_0/die*
20	==> /sys/devices/uncore_iio_0/die0 <==	20	==> /sys/devices/uncore_iio_0/die0 <==
21	0000:00	21	0000:00
22	==> /sys/devices/uncore_iio_0/die1 <==	22	==> /sys/devices/uncore_iio_0/die1 <==
23	0000:40	23	0000:40
24	==> /sys/devices/uncore_iio_0/die2 <==	24	==> /sys/devices/uncore_iio_0/die2 <==
25	0000:80	25	0000:80
26	==> /sys/devices/uncore_iio_0/die3 <==	26	==> /sys/devices/uncore_iio_0/die3 <==
27	0000:c0	27	0000:c0
28		28
29	Which means:	29	Which means::
30	IIO PMU 0 on die 0 belongs to PCI RP on bus 0x00, domain 0x0000	30
31	IIO PMU 0 on die 1 belongs to PCI RP on bus 0x40, domain 0x0000	31	IIO PMU 0 on die 0 belongs to PCI RP on bus 0x00, domain 0x0000
32	IIO PMU 0 on die 2 belongs to PCI RP on bus 0x80, domain 0x0000	32	IIO PMU 0 on die 1 belongs to PCI RP on bus 0x40, domain 0x0000
33	IIO PMU 0 on die 3 belongs to PCI RP on bus 0xc0, domain 0x0000	33	IIO PMU 0 on die 2 belongs to PCI RP on bus 0x80, domain 0x0000
		34	IIO PMU 0 on die 3 belongs to PCI RP on bus 0xc0, domain 0x0000

Documentation/ABI/testing/sysfs-devices-memory+10−5

Documentation/ABI/testing/sysfs-devices-platform-ACPI-TAD+4−0

 		(RO) Hexadecimal bitmask of the TAD attributes are reported by
 		the platform firmware (see ACPI 6.2, section 9.18.2):
+		======= ======================================================
 		BIT(0): AC wakeup implemented if set
 		BIT(1): DC wakeup implemented if set
 		BIT(2): Get/set real time features implemented if set
 		BIT(6): The AC timer wakes up from S5 if set
 		BIT(7): The DC timer wakes up from S4 if set
 		BIT(8): The DC timer wakes up from S5 if set
+		======= ======================================================
 		The other bits are reserved.
 		timer status with the following meaning of bits (see ACPI 6.2,
 		Section 9.18.5):
+		======= ======================================================
 		Bit(0): The timer has expired if set.
 		Bit(1): The timer has woken up the system from a sleep state
 		        (S3 or S4/S5 if supported) if set.
+		======= ======================================================
 		The other bits are reserved.

Documentation/ABI/testing/sysfs-devices-platform-_UDC_-gadget+6−4

@@ -3,8 +3,9 @@ Date: April 2010 · 2 unmodified lines
3	Contact: Fabien Chouteau <fabien.chouteau@barco.com>	3	Contact: Fabien Chouteau <fabien.chouteau@barco.com>
4	Description:	4	Description:
5	Show the suspend state of an USB composite gadget.	5	Show the suspend state of an USB composite gadget.
6	1 -> suspended	6
7	0 -> resumed	7	- 1 -> suspended
		8	- 0 -> resumed
8		9
9	(_UDC_ is the name of the USB Device Controller driver)	10	(_UDC_ is the name of the USB Device Controller driver)
10		11
@@ -17,5 +18,6 @@ Description: · 6 unmodified lines
17	Storage mode.	18	Storage mode.
18		19
19	Possible values are:	20	Possible values are:
20	1 -> ignore the FUA flag	21
21	0 -> obey the FUA flag	22	- 1 -> ignore the FUA flag
		23	- 0 -> obey the FUA flag

Documentation/ABI/testing/sysfs-devices-platform-docg3+8−2

@@ -9,8 +9,10 @@ Description: · 8 unmodified lines
9	The protection has information embedded whether it blocks reads,	9	The protection has information embedded whether it blocks reads,
10	writes or both.	10	writes or both.
11	The result is:	11	The result is:
12	0 -> the DPS is not keylocked	12
13	1 -> the DPS is keylocked	13	- 0 -> the DPS is not keylocked
		14	- 1 -> the DPS is keylocked
		15
14	Users: None identified so far.	16	Users: None identified so far.
15		17
16	What: /sys/devices/platform/docg3/f[0-3]_dps[01]_protection_key	18	What: /sys/devices/platform/docg3/f[0-3]_dps[01]_protection_key
@@ -27,8 +29,12 @@ Description: · 10 unmodified lines
27	Entering the correct value toggle the lock, and can be observed	29	Entering the correct value toggle the lock, and can be observed
28	through f[0-3]_dps[01]_is_keylocked.	30	through f[0-3]_dps[01]_is_keylocked.
29	Possible values are:	31	Possible values are:
		32
30	- 8 bytes	33	- 8 bytes
		34
31	Typical values are:	35	Typical values are:
		36
32	- "00000000"	37	- "00000000"
33	- "12345678"	38	- "12345678"
		39
34	Users: None identified so far.	40	Users: None identified so far.

Documentation/ABI/testing/sysfs-devices-platform-ipmi+28−24

@@ -123,38 +123,40 @@ KernelVersion: v4.15 · 122 unmodified lines
123	Contact: openipmi-developer@lists.sourceforge.net	123	Contact: openipmi-developer@lists.sourceforge.net
124	Description:	124	Description:
125		125
126	idles: (RO) Number of times the interface was	126	====================== ========================================
		127	idles (RO) Number of times the interface was
127	idle while being polled.	128	idle while being polled.
128		129
129	watchdog_pretimeouts: (RO) Number of watchdog pretimeouts.	130	watchdog_pretimeouts (RO) Number of watchdog pretimeouts.
130		131
131	complete_transactions: (RO) Number of completed messages.	132	complete_transactions (RO) Number of completed messages.
132		133
133	events: (RO) Number of IPMI events received from	134	events (RO) Number of IPMI events received from
134	the hardware.	135	the hardware.
135		136
136	interrupts: (RO) Number of interrupts the driver	137	interrupts (RO) Number of interrupts the driver
137	handled.	138	handled.
138		139
139	hosed_count: (RO) Number of times the hardware didn't	140	hosed_count (RO) Number of times the hardware didn't
140	follow the state machine.	141	follow the state machine.
141		142
142	long_timeouts: (RO) Number of times the driver	143	long_timeouts (RO) Number of times the driver
143	requested a timer while nothing was in	144	requested a timer while nothing was in
144	progress.	145	progress.
145		146
146	flag_fetches: (RO) Number of times the driver	147	flag_fetches (RO) Number of times the driver
147	requested flags from the hardware.	148	requested flags from the hardware.
148		149
149	attentions: (RO) Number of time the driver got an	150	attentions (RO) Number of time the driver got an
150	ATTN from the hardware.	151	ATTN from the hardware.
151		152
152	incoming_messages: (RO) Number of asynchronous messages	153	incoming_messages (RO) Number of asynchronous messages
153	received.	154	received.
154		155
155	short_timeouts: (RO) Number of times the driver	156	short_timeouts (RO) Number of times the driver
156	requested a timer while an operation was	157	requested a timer while an operation was
157	in progress.	158	in progress.
		159	====================== ========================================
158		160
159		161
160	What: /sys/devices/platform/ipmi_si.*/interrupts_enabled	162	What: /sys/devices/platform/ipmi_si.*/interrupts_enabled
@@ -201,38 +203,40 @@ Date: Sep, 2017 · 40 unmodified lines
201	KernelVersion: v4.15	203	KernelVersion: v4.15
202	Contact: openipmi-developer@lists.sourceforge.net	204	Contact: openipmi-developer@lists.sourceforge.net
203	Description:	205	Description:
204	hosed: (RO) Number of times the hardware didn't	206	====================== ========================================
		207	hosed (RO) Number of times the hardware didn't
205	follow the state machine.	208	follow the state machine.
206		209
207	alerts: (RO) Number of alerts received.	210	alerts (RO) Number of alerts received.
208		211
209	sent_messages: (RO) Number of total messages sent.	212	sent_messages (RO) Number of total messages sent.
210		213
211	sent_message_parts: (RO) Number of message parts sent.	214	sent_message_parts (RO) Number of message parts sent.
212	Messages may be broken into parts if	215	Messages may be broken into parts if
213	they are long.	216	they are long.
214		217
215	received_messages: (RO) Number of message responses	218	received_messages (RO) Number of message responses
216	received.	219	received.
217		220
218	received_message_parts: (RO) Number of message fragments	221	received_message_parts (RO) Number of message fragments
219	received.	222	received.
220		223
221	events: (RO) Number of received events.	224	events (RO) Number of received events.
222		225
223	watchdog_pretimeouts: (RO) Number of watchdog pretimeouts.	226	watchdog_pretimeouts (RO) Number of watchdog pretimeouts.
224		227
225	flag_fetches: (RO) Number of times a flag fetch was	228	flag_fetches (RO) Number of times a flag fetch was
226	requested.	229	requested.
227		230
228	send_retries: (RO) Number of time a message was	231	send_retries (RO) Number of time a message was
229	retried.	232	retried.
230		233
231	receive_retries: (RO) Number of times the receive of a	234	receive_retries (RO) Number of times the receive of a
232	message was retried.	235	message was retried.
233		236
234	send_errors: (RO) Number of times the send of a	237	send_errors (RO) Number of times the send of a
235	message failed.	238	message failed.
236		239
237	receive_errors: (RO) Number of errors in receiving	240	receive_errors (RO) Number of errors in receiving
238	messages.	241	messages.
		242	====================== ========================================

Documentation/ABI/testing/sysfs-devices-platform-sh_mobile_lcdc_fb+4−4

@@ -17,10 +17,10 @@ Description: · 16 unmodified lines
17	to overlay planes.	17	to overlay planes.
18		18
19	Selects the composition mode for the overlay. Possible values	19	Selects the composition mode for the overlay. Possible values
20	are	20	are:
21		21
22	0 - Alpha Blending	22	- 0 - Alpha Blending
23	1 - ROP3	23	- 1 - ROP3
24		24
25	What: /sys/devices/platform/sh_mobile_lcdc_fb.[0-3]/graphics/fb[0-9]/ovl_position	25	What: /sys/devices/platform/sh_mobile_lcdc_fb.[0-3]/graphics/fb[0-9]/ovl_position
26	Date: May 2012	26	Date: May 2012
@@ -30,7 +30,7 @@ Description: · 3 unmodified lines
30	to overlay planes.	30	to overlay planes.
31		31
32	Stores the x,y overlay position on the display in pixels. The	32	Stores the x,y overlay position on the display in pixels. The
33	position format is `[0-9]+,[0-9]+'.	33	position format is `[0-9]+,[0-9]+`.
34		34
35	What: /sys/devices/platform/sh_mobile_lcdc_fb.[0-3]/graphics/fb[0-9]/ovl_rop3	35	What: /sys/devices/platform/sh_mobile_lcdc_fb.[0-3]/graphics/fb[0-9]/ovl_rop3
36	Date: May 2012	36	Date: May 2012

Documentation/ABI/testing/sysfs-devices-platform-stratix10-rsu+10−0

 		b[15:0]
 			inform firmware the current software execution
 			stage.
+			==	===========================================
 			0	the first stage bootloader didn't run or
 				didn't reach the point of launching second
 				stage bootloader.
 			2	both first and second stage bootloader ran
 				and the operating system launch was
 				attempted.
+			==	===========================================
 		b[16]
+			==	===========================================
 			1	firmware to reset current image retry
 				counter.
 			0	no action.
+			==	===========================================
 		b[17]
+			==	===========================================
 			1	firmware to clear RSU log
 			0	no action.
+			==	===========================================
 		b[18]
 			this is negative logic
+			==	===========================================
 			1	no action
 			0	firmware record the notify code defined
 				in b[15:0].
+			==	===========================================
 What:		/sys/devices/platform/stratix10-rsu.0/dcmf0
 Date:		June 2020

Documentation/ABI/testing/sysfs-devices-system-cpu+63−38

 		The processor idle states which are available for use have the
 		following attributes:
-		name: (RO) Name of the idle state (string).
+		======== ==== =================================================
+		name:	 (RO) Name of the idle state (string).
 		latency: (RO) The latency to exit out of this idle state (in
-		microseconds).
+			      microseconds).
-		power: (RO) The power consumed while in this idle state (in
+		power:   (RO) The power consumed while in this idle state (in
-		milliwatts).
+			      milliwatts).
-		time: (RO) The total time spent in this idle state (in microseconds).
+		time:    (RO) The total time spent in this idle state
+			      (in microseconds).
-		usage: (RO) Number of times this state was entered (a count).
+		usage:	 (RO) Number of times this state was entered (a count).
-		above: (RO) Number of times this state was entered, but the
+		above:	 (RO) Number of times this state was entered, but the
-		       observed CPU idle duration was too short for it (a count).
+			      observed CPU idle duration was too short for it
+			      (a count).
-		below: (RO) Number of times this state was entered, but the
+		below:	 (RO) Number of times this state was entered, but the
-		       observed CPU idle duration was too long for it (a count).
+			      observed CPU idle duration was too long for it
+			      (a count).
+		======== ==== =================================================
 What:		/sys/devices/system/cpu/cpuX/cpuidle/stateN/desc
 Date:		February 2008
 		This switch controls the boost setting for the whole system.
 		Boosting allows the CPU and the firmware to run at a frequency
 		beyound it's nominal limit.
 		More details can be found in
 		Documentation/admin-guide/pm/cpufreq.rst
 Description:	Parameters for the CPU cache attributes
 		allocation_policy:
-			- WriteAllocate: allocate a memory location to a cache line
+			- WriteAllocate:
-					 on a cache miss because of a write
+					allocate a memory location to a cache line
-			- ReadAllocate: allocate a memory location to a cache line
+					on a cache miss because of a write
+			- ReadAllocate:
+					allocate a memory location to a cache line
 					on a cache miss because of a read
-			- ReadWriteAllocate: both writeallocate and readallocate
+			- ReadWriteAllocate:
+					both writeallocate and readallocate
-		attributes: LEGACY used only on IA64 and is same as write_policy
+		attributes:
+			    LEGACY used only on IA64 and is same as write_policy
-		coherency_line_size: the minimum amount of data in bytes that gets
+		coherency_line_size:
+				     the minimum amount of data in bytes that gets
 				     transferred from memory to cache
-		level: the cache hierarchy in the multi-level cache configuration
+		level:
+			the cache hierarchy in the multi-level cache configuration
-		number_of_sets: total number of sets in the cache, a set is a
+		number_of_sets:
+				total number of sets in the cache, a set is a
 				collection of cache lines with the same cache index
-		physical_line_partition: number of physical cache line per cache tag
+		physical_line_partition:
+				number of physical cache line per cache tag
-		shared_cpu_list: the list of logical cpus sharing the cache
+		shared_cpu_list:
+				the list of logical cpus sharing the cache
-		shared_cpu_map: logical cpu mask containing the list of cpus sharing
+		shared_cpu_map:
+				logical cpu mask containing the list of cpus sharing
 				the cache
-		size: the total cache size in kB
+		size:
+			the total cache size in kB
 		type:
 			- Instruction: cache that only holds instructions
 			- Data: cache that only caches data
 			- Unified: cache that holds both data and instructions
-		ways_of_associativity: degree of freedom in placing a particular block
+		ways_of_associativity:
-					of memory in the cache
+			degree of freedom in placing a particular block
+			of memory in the cache
 		write_policy:
-			- WriteThrough: data is written to both the cache line
+			- WriteThrough:
+					data is written to both the cache line
 					and to the block in the lower-level memory
-			- WriteBack: data is written only to the cache line and
+			- WriteBack:
+				     data is written only to the cache line and
 				     the modified cache line is written to main
 				     memory only when it is replaced
 		throttle attributes exported in the 'throttle_stats' directory:
 		- turbo_stat : This file gives the total number of times the max
-		frequency is throttled to lower frequency in turbo (at and above
+		  frequency is throttled to lower frequency in turbo (at and above
-		nominal frequency) range of frequencies.
+		  nominal frequency) range of frequencies.
 		- sub_turbo_stat : This file gives the total number of times the
-		max frequency is throttled to lower frequency in sub-turbo(below
+		  max frequency is throttled to lower frequency in sub-turbo(below
-		nominal frequency) range of frequencies.
+		  nominal frequency) range of frequencies.
 		- unthrottle : This file gives the total number of times the max
-		frequency is unthrottled after being throttled.
+		  frequency is unthrottled after being throttled.
 		- powercap : This file gives the total number of times the max
-		frequency is throttled due to 'Power Capping'.
+		  frequency is throttled due to 'Power Capping'.
 		- overtemp : This file gives the total number of times the max
-		frequency is throttled due to 'CPU Over Temperature'.
+		  frequency is throttled due to 'CPU Over Temperature'.
 		- supply_fault : This file gives the total number of times the
-		max frequency is throttled due to 'Power Supply Failure'.
+		  max frequency is throttled due to 'Power Supply Failure'.
 		- overcurrent : This file gives the total number of times the
-		max frequency is throttled due to 'Overcurrent'.
+		  max frequency is throttled due to 'Overcurrent'.
 		- occ_reset : This file gives the total number of times the max
-		frequency is throttled due to 'OCC Reset'.
+		  frequency is throttled due to 'OCC Reset'.
 		The sysfs attributes representing different throttle reasons like
 		powercap, overtemp, supply_fault, overcurrent and occ_reset map to
 Date:		June 2016
 Contact:	Linux ARM Kernel Mailing list <linux-arm-kernel@lists.infradead.org>
 Description:	AArch64 CPU registers
 		'identification' directory exposes the CPU ID registers for
-		 identifying model and revision of the CPU.
+		identifying model and revision of the CPU.
 What:		/sys/devices/system/cpu/cpu#/cpu_capacity
 Date:		December 2016
 		vulnerabilities. The output of those files reflects the
 		state of the CPUs in the system. Possible output values:
+		================  ==============================================
 		"Not affected"	  CPU is not affected by the vulnerability
 		"Vulnerable"	  CPU is affected and no mitigation in effect
 		"Mitigation: $M"  CPU is affected and mitigation $M is in effect
+		================  ==============================================
 		See also: Documentation/admin-guide/hw-vuln/index.rst
 		control: Read/write interface to control SMT. Possible
 			 values:
+			 ================ =========================================
 			 "on"		  SMT is enabled
 			 "off"		  SMT is disabled
 			 "forceoff"	  SMT is force disabled. Cannot be changed.
 			 "notsupported"   SMT is not supported by the CPU
 			 "notimplemented" SMT runtime toggling is not
 					  implemented for the architecture
+			 ================ =========================================
 			 If control status is "forceoff" or "notsupported" writes
 			 are rejected.
 		Facility in POWER9 and newer processors. i.e., it is a Secure
 		Virtual Machine.
-What: 		/sys/devices/system/cpu/cpuX/purr
+What:		/sys/devices/system/cpu/cpuX/purr
 Date:		Apr 2005
 Contact:	Linux for PowerPC mailing list <linuxppc-dev@ozlabs.org>
 Description:	PURR ticks for this CPU since the system boot.

Documentation/ABI/testing/sysfs-devices-system-ibm-rtl+4−2

@@ -5,8 +5,10 @@ Contact: Vernon Mauery <vernux@us.ibm.com> · 4 unmodified lines
5	Description: The state file allows a means by which to change in and	5	Description: The state file allows a means by which to change in and
6	out of Premium Real-Time Mode (PRTM), as well as the	6	out of Premium Real-Time Mode (PRTM), as well as the
7	ability to query the current state.	7	ability to query the current state.
8	0 => PRTM off	8
9	1 => PRTM enabled	9	- 0 => PRTM off
		10	- 1 => PRTM enabled
		11
10	Users: The ibm-prtm userspace daemon uses this interface.	12	Users: The ibm-prtm userspace daemon uses this interface.
11		13
12		14

Documentation/ABI/testing/sysfs-driver-bd9571mwv-regulator+4−0

Documentation/ABI/testing/sysfs-driver-genwqe+9−2

@@ -29,8 +29,12 @@ What: /sys/class/genwqe/genwqe<n>_card/reload_bitstream · 28 unmodified lines
29	Date: May 2014	29	Date: May 2014
30	Contact: klebers@linux.vnet.ibm.com	30	Contact: klebers@linux.vnet.ibm.com
31	Description: Interface to trigger a PCIe card reset to reload the bitstream.	31	Description: Interface to trigger a PCIe card reset to reload the bitstream.
		32
		33	::
		34
32	sudo sh -c 'echo 1 > \	35	sudo sh -c 'echo 1 > \
33	/sys/class/genwqe/genwqe0_card/reload_bitstream'	36	/sys/class/genwqe/genwqe0_card/reload_bitstream'
		37
34	If successfully, the card will come back with the bitstream set	38	If successfully, the card will come back with the bitstream set
35	on 'next_bitstream'.	39	on 'next_bitstream'.
36		40
@@ -64,8 +68,11 @@ Description: Base clock frequency of the card. · 27 unmodified lines
64	What: /sys/class/genwqe/genwqe<n>_card/device/sriov_numvfs	68	What: /sys/class/genwqe/genwqe<n>_card/device/sriov_numvfs
65	Date: Oct 2013	69	Date: Oct 2013
66	Contact: haver@linux.vnet.ibm.com	70	Contact: haver@linux.vnet.ibm.com
67	Description: Enable VFs (1..15):	71	Description: Enable VFs (1..15)::
		72
68	sudo sh -c 'echo 15 > \	73	sudo sh -c 'echo 15 > \
69	/sys/bus/pci/devices/0000\:1b\:00.0/sriov_numvfs'	74	/sys/bus/pci/devices/0000\:1b\:00.0/sriov_numvfs'
70	Disable VFs:	75
		76	Disable VFs::
		77
71	Write a 0 into the same sysfs entry.	78	Write a 0 into the same sysfs entry.

Documentation/ABI/testing/sysfs-driver-hid-lenovo+10−0

Documentation/ABI/testing/sysfs-driver-hid-logitech-lg4ff+13−5

@@ -12,7 +12,9 @@ KernelVersion: 4.1 · 11 unmodified lines
12	Contact: Michal Malý <madcatxster@devoid-pointer.net>	12	Contact: Michal Malý <madcatxster@devoid-pointer.net>
13	Description: Displays a set of alternate modes supported by a wheel. Each	13	Description: Displays a set of alternate modes supported by a wheel. Each
14	mode is listed as follows:	14	mode is listed as follows:
		15
15	Tag: Mode Name	16	Tag: Mode Name
		17
16	Currently active mode is marked with an asterisk. List also	18	Currently active mode is marked with an asterisk. List also
17	contains an abstract item "native" which always denotes the	19	contains an abstract item "native" which always denotes the
18	native mode of the wheel. Echoing the mode tag switches the	20	native mode of the wheel. Echoing the mode tag switches the
@@ -24,24 +26,30 @@ Description: Displays a set of alternate modes supported by a wheel. Each · 5 unmodified lines
24	This entry is not created for devices that have only one mode.	26	This entry is not created for devices that have only one mode.
25		27
26	Currently supported mode switches:	28	Currently supported mode switches:
27	Driving Force Pro:	29
		30	Driving Force Pro::
		31
28	DF-EX --> DFP	32	DF-EX --> DFP
29		33
30	G25:	34	G25::
		35
31	DF-EX --> DFP --> G25	36	DF-EX --> DFP --> G25
32		37
33	G27:	38	G27::
		39
34	DF-EX <*> DFP <-> G25 <-> G27	40	DF-EX <*> DFP <-> G25 <-> G27
35	DF-EX <*--------> G25 <-> G27	41	DF-EX <*--------> G25 <-> G27
36	DF-EX <*----------------> G27	42	DF-EX <*----------------> G27
37		43
38	G29:	44	G29::
		45
39	DF-EX <*> DFP <-> G25 <-> G27 <-> G29	46	DF-EX <*> DFP <-> G25 <-> G27 <-> G29
40	DF-EX <*--------> G25 <-> G27 <-> G29	47	DF-EX <*--------> G25 <-> G27 <-> G29
41	DF-EX <*----------------> G27 <-> G29	48	DF-EX <*----------------> G27 <-> G29
42	DF-EX <*------------------------> G29	49	DF-EX <*------------------------> G29
43		50
44	DFGT:	51	DFGT::
		52
45	DF-EX <*> DFP <-> DFGT	53	DF-EX <*> DFP <-> DFGT
46	DF-EX <*--------> DFGT	54	DF-EX <*--------> DFGT
47		55

Documentation/ABI/testing/sysfs-driver-hid-ntrig+8−5

@@ -29,12 +29,13 @@ Contact: linux-input@vger.kernel.org · 28 unmodified lines
29	Description:	29	Description:
30	Threholds to override activation slack.	30	Threholds to override activation slack.
31		31
32	activation_width: (RW) Width threshold to immediately	32	================= =====================================
		33	activation_width (RW) Width threshold to immediately
33	start processing touch events.	34	start processing touch events.
34		35
35	activation_height: (RW) Height threshold to immediately	36	activation_height (RW) Height threshold to immediately
36	start processing touch events.	37	start processing touch events.
37		38	================= =====================================
38		39
39	What: /sys/bus/hid/drivers/ntrig/<dev>/min_width	40	What: /sys/bus/hid/drivers/ntrig/<dev>/min_width
40	What: /sys/bus/hid/drivers/ntrig/<dev>/min_height	41	What: /sys/bus/hid/drivers/ntrig/<dev>/min_height
@@ -44,11 +45,13 @@ Contact: linux-input@vger.kernel.org · 3 unmodified lines
44	Description:	45	Description:
45	Minimum size contact accepted.	46	Minimum size contact accepted.
46		47
47	min_width: (RW) Minimum touch contact width to decide	48	========== ===========================================
		49	min_width (RW) Minimum touch contact width to decide
48	activation and activity.	50	activation and activity.
49		51
50	min_height: (RW) Minimum touch contact height to decide	52	min_height (RW) Minimum touch contact height to decide
51	activation and activity.	53	activation and activity.
		54	========== ===========================================
52		55
53		56
54	What: /sys/bus/hid/drivers/ntrig/<dev>/sensor_physical_width	57	What: /sys/bus/hid/drivers/ntrig/<dev>/sensor_physical_width

Documentation/ABI/testing/sysfs-driver-hid-roccat-kone+19−0

 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
 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
 		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
                 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.
 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.
 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
 		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
 		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

Documentation/ABI/testing/sysfs-driver-hid-wiimote+10−2

@@ -20,6 +20,7 @@ Description: This file contains the currently connected and initialized · 19 unmodified lines
20	the official Nintendo Nunchuck extension and classic is the	20	the official Nintendo Nunchuck extension and classic is the
21	Nintendo Classic Controller extension. The motionp extension can	21	Nintendo Classic Controller extension. The motionp extension can
22	be combined with the other two.	22	be combined with the other two.
		23
23	Starting with kernel-version 3.11 Motion Plus hotplugging is	24	Starting with kernel-version 3.11 Motion Plus hotplugging is
24	supported and if detected, it's no longer reported as static	25	supported and if detected, it's no longer reported as static
25	extension. You will get uevent notifications for the motion-plus	26	extension. You will get uevent notifications for the motion-plus
@@ -39,9 +40,13 @@ Description: While a device is initialized by the wiimote driver, we perform · 13 unmodified lines
39	Other strings for each device-type are available and may be	40	Other strings for each device-type are available and may be
40	added if new device-specific detections are added.	41	added if new device-specific detections are added.
41	Currently supported are:	42	Currently supported are:
42	gen10: First Wii Remote generation	43
43	gen20: Second Wii Remote Plus generation (builtin MP)	44	============= =======================================
		45	gen10: First Wii Remote generation
		46	gen20: Second Wii Remote Plus generation
		47	(builtin MP)
44	balanceboard: Wii Balance Board	48	balanceboard: Wii Balance Board
		49	============= =======================================
45		50
46	What: /sys/bus/hid/drivers/wiimote/<dev>/bboard_calib	51	What: /sys/bus/hid/drivers/wiimote/<dev>/bboard_calib
47	Date: May 2013	52	Date: May 2013
@@ -54,6 +59,7 @@ Description: This attribute is only provided if the device was detected as a · 6 unmodified lines
54	First, 0kg values for all 4 sensors are written, followed by the	59	First, 0kg values for all 4 sensors are written, followed by the
55	17kg values for all 4 sensors and last the 34kg values for all 4	60	17kg values for all 4 sensors and last the 34kg values for all 4
56	sensors.	61	sensors.
		62
57	Calibration data is already applied by the kernel to all input	63	Calibration data is already applied by the kernel to all input
58	values but may be used by user-space to perform other	64	values but may be used by user-space to perform other
59	transformations.	65	transformations.
@@ -68,9 +74,11 @@ Description: This attribute is only provided if the device was detected as a · 8 unmodified lines
68	is prefixed with a +/-. Each value is a signed 16bit number.	74	is prefixed with a +/-. Each value is a signed 16bit number.
69	Data is encoded as decimal numbers and specifies the offsets of	75	Data is encoded as decimal numbers and specifies the offsets of
70	the analog sticks of the pro-controller.	76	the analog sticks of the pro-controller.
		77
71	Calibration data is already applied by the kernel to all input	78	Calibration data is already applied by the kernel to all input
72	values but may be used by user-space to perform other	79	values but may be used by user-space to perform other
73	transformations.	80	transformations.
		81
74	Calibration data is detected by the kernel during device setup.	82	Calibration data is detected by the kernel during device setup.
75	You can write "scan\n" into this file to re-trigger calibration.	83	You can write "scan\n" into this file to re-trigger calibration.
76	You can also write data directly in the form "x1:y1 x2:y2" to	84	You can also write data directly in the form "x1:y1 x2:y2" to

Documentation/ABI/testing/sysfs-driver-input-exc3000+2−0

@@ -4,6 +4,7 @@ Contact: linux-input@vger.kernel.org · 3 unmodified lines
4	Description: Reports the firmware version provided by the touchscreen, for example "00_T6" on a EXC80H60	4	Description: Reports the firmware version provided by the touchscreen, for example "00_T6" on a EXC80H60
5		5
6	Access: Read	6	Access: Read
		7
7	Valid values: Represented as string	8	Valid values: Represented as string
8		9
9	What: /sys/bus/i2c/devices/xxx/model	10	What: /sys/bus/i2c/devices/xxx/model
@@ -12,4 +13,5 @@ Contact: linux-input@vger.kernel.org · 2 unmodified lines
12	Description: Reports the model identification provided by the touchscreen, for example "Orion_1320" on a EXC80H60	13	Description: Reports the model identification provided by the touchscreen, for example "Orion_1320" on a EXC80H60
13		14
14	Access: Read	15	Access: Read
		16
15	Valid values: Represented as string	17	Valid values: Represented as string

Documentation/ABI/testing/sysfs-driver-jz4780-efuse+5−1

 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
+		The segments are:
+		===== ======== =================
 		0x000   64 bit Random Number
 		0x008  128 bit Ingenic Chip ID
 		0x018  128 bit Customer ID
 		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

Documentation/ABI/testing/sysfs-driver-pciback+4−2

@@ -7,8 +7,10 @@ Description: · 6 unmodified lines
7	the format of DDDD:BB:DD.F-REG:SIZE:MASK will allow the guest	7	the format of DDDD:BB:DD.F-REG:SIZE:MASK will allow the guest
8	to write and read from the PCI device. That is Domain:Bus:	8	to write and read from the PCI device. That is Domain:Bus:
9	Device.Function-Register:Size:Mask (Domain is optional).	9	Device.Function-Register:Size:Mask (Domain is optional).
10	For example:	10	For example::
11	#echo 00:19.0-E0:2:FF > /sys/bus/pci/drivers/pciback/quirks	11
		12	#echo 00:19.0-E0:2:FF > /sys/bus/pci/drivers/pciback/quirks
		13
12	will allow the guest to read and write to the configuration	14	will allow the guest to read and write to the configuration
13	register 0x0E.	15	register 0x0E.
14		16

Documentation/ABI/testing/sysfs-driver-samsung-laptop+8−5

@@ -9,10 +9,12 @@ Description: Some Samsung laptops have different "performance levels" · 8 unmodified lines
9	their fans quiet at all costs. Reading from this file	9	their fans quiet at all costs. Reading from this file
10	will show the current performance level. Writing to the	10	will show the current performance level. Writing to the
11	file can change this value.	11	file can change this value.
		12
12	Valid options:	13	Valid options:
13	"silent"	14	- "silent"
14	"normal"	15	- "normal"
15	"overclock"	16	- "overclock"
		17
16	Note that not all laptops support all of these options.	18	Note that not all laptops support all of these options.
17	Specifically, not all support the "overclock" option,	19	Specifically, not all support the "overclock" option,
18	and it's still unknown if this value even changes	20	and it's still unknown if this value even changes
@@ -25,8 +27,9 @@ Contact: Corentin Chary <corentin.chary@gmail.com> · 6 unmodified lines
25	Description: Max battery charge level can be modified, battery cycle	27	Description: Max battery charge level can be modified, battery cycle
26	life can be extended by reducing the max battery charge	28	life can be extended by reducing the max battery charge
27	level.	29	level.
28	0 means normal battery mode (100% charge)	30
29	1 means battery life extender mode (80% charge)	31	- 0 means normal battery mode (100% charge)
		32	- 1 means battery life extender mode (80% charge)
30		33
31	What: /sys/devices/platform/samsung/usb_charge	34	What: /sys/devices/platform/samsung/usb_charge
32	Date: December 1, 2011	35	Date: December 1, 2011

Documentation/ABI/testing/sysfs-driver-toshiba_acpi+26−0

@@ -4,10 +4,12 @@ KernelVersion: 3.15 · 3 unmodified lines
4	Contact: Azael Avalos <coproscefalo@gmail.com>	4	Contact: Azael Avalos <coproscefalo@gmail.com>
5	Description: This file controls the keyboard backlight operation mode, valid	5	Description: This file controls the keyboard backlight operation mode, valid
6	values are:	6	values are:
		7
7	* 0x1 -> FN-Z	8	* 0x1 -> FN-Z
8	* 0x2 -> AUTO (also called TIMER)	9	* 0x2 -> AUTO (also called TIMER)
9	* 0x8 -> ON	10	* 0x8 -> ON
10	* 0x10 -> OFF	11	* 0x10 -> OFF
		12
11	Note that from kernel 3.16 onwards this file accepts all listed	13	Note that from kernel 3.16 onwards this file accepts all listed
12	parameters, kernel 3.15 only accepts the first two (FN-Z and	14	parameters, kernel 3.15 only accepts the first two (FN-Z and
13	AUTO).	15	AUTO).
@@ -41,8 +43,10 @@ KernelVersion: 3.15 · 27 unmodified lines
41	Contact: Azael Avalos <coproscefalo@gmail.com>	43	Contact: Azael Avalos <coproscefalo@gmail.com>
42	Description: This files controls the status of the touchpad and pointing	44	Description: This files controls the status of the touchpad and pointing
43	stick (if available), valid values are:	45	stick (if available), valid values are:
		46
44	* 0 -> OFF	47	* 0 -> OFF
45	* 1 -> ON	48	* 1 -> ON
		49
46	Users: KToshiba	50	Users: KToshiba
47		51
48	What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/available_kbd_modes	52	What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/available_kbd_modes
@@ -51,10 +55,12 @@ KernelVersion: 3.16 · 2 unmodified lines
51	Contact: Azael Avalos <coproscefalo@gmail.com>	55	Contact: Azael Avalos <coproscefalo@gmail.com>
52	Description: This file shows the supported keyboard backlight modes	56	Description: This file shows the supported keyboard backlight modes
53	the system supports, which can be:	57	the system supports, which can be:
		58
54	* 0x1 -> FN-Z	59	* 0x1 -> FN-Z
55	* 0x2 -> AUTO (also called TIMER)	60	* 0x2 -> AUTO (also called TIMER)
56	* 0x8 -> ON	61	* 0x8 -> ON
57	* 0x10 -> OFF	62	* 0x10 -> OFF
		63
58	Note that not all keyboard types support the listed modes.	64	Note that not all keyboard types support the listed modes.
59	See the entry named "available_kbd_modes"	65	See the entry named "available_kbd_modes"
60	Users: KToshiba	66	Users: KToshiba
@@ -65,6 +71,7 @@ KernelVersion: 3.16 · 4 unmodified lines
65	Contact: Azael Avalos <coproscefalo@gmail.com>	71	Contact: Azael Avalos <coproscefalo@gmail.com>
66	Description: This file shows the current keyboard backlight type,	72	Description: This file shows the current keyboard backlight type,
67	which can be:	73	which can be:
		74
68	* 1 -> Type 1, supporting modes FN-Z and AUTO	75	* 1 -> Type 1, supporting modes FN-Z and AUTO
69	* 2 -> Type 2, supporting modes TIMER, ON and OFF	76	* 2 -> Type 2, supporting modes TIMER, ON and OFF
70	Users: KToshiba	77	Users: KToshiba
@@ -75,10 +82,12 @@ KernelVersion: 4.0 · 4 unmodified lines
75	Contact: Azael Avalos <coproscefalo@gmail.com>	82	Contact: Azael Avalos <coproscefalo@gmail.com>
76	Description: This file controls the USB Sleep & Charge charging mode, which	83	Description: This file controls the USB Sleep & Charge charging mode, which
77	can be:	84	can be:
		85
78	* 0 -> Disabled (0x00)	86	* 0 -> Disabled (0x00)
79	* 1 -> Alternate (0x09)	87	* 1 -> Alternate (0x09)
80	* 2 -> Auto (0x21)	88	* 2 -> Auto (0x21)
81	* 3 -> Typical (0x11)	89	* 3 -> Typical (0x11)
		90
82	Note that from kernel 4.1 onwards this file accepts all listed	91	Note that from kernel 4.1 onwards this file accepts all listed
83	values, kernel 4.0 only supports the first three.	92	values, kernel 4.0 only supports the first three.
84	Note that this feature only works when connected to power, if	93	Note that this feature only works when connected to power, if
@@ -93,8 +102,10 @@ Contact: Azael Avalos <coproscefalo@gmail.com> · 8 unmodified lines
93	Description: This file controls the USB Sleep Functions under battery, and	102	Description: This file controls the USB Sleep Functions under battery, and
94	set the level at which point they will be disabled, accepted	103	set the level at which point they will be disabled, accepted
95	values can be:	104	values can be:
		105
96	* 0 -> Disabled	106	* 0 -> Disabled
97	* 1-100 -> Battery level to disable sleep functions	107	* 1-100 -> Battery level to disable sleep functions
		108
98	Currently it prints two values, the first one indicates if the	109	Currently it prints two values, the first one indicates if the
99	feature is enabled or disabled, while the second one shows the	110	feature is enabled or disabled, while the second one shows the
100	current battery level set.	111	current battery level set.
@@ -107,8 +118,10 @@ Date: January 23, 2015 · 6 unmodified lines
107	KernelVersion: 4.0	118	KernelVersion: 4.0
108	Contact: Azael Avalos <coproscefalo@gmail.com>	119	Contact: Azael Avalos <coproscefalo@gmail.com>
109	Description: This file controls the USB Rapid Charge state, which can be:	120	Description: This file controls the USB Rapid Charge state, which can be:
		121
110	* 0 -> Disabled	122	* 0 -> Disabled
111	* 1 -> Enabled	123	* 1 -> Enabled
		124
112	Note that toggling this value requires a reboot for changes to	125	Note that toggling this value requires a reboot for changes to
113	take effect.	126	take effect.
114	Users: KToshiba	127	Users: KToshiba
@@ -118,8 +131,10 @@ Date: January 23, 2015 · 3 unmodified lines
118	KernelVersion: 4.0	131	KernelVersion: 4.0
119	Contact: Azael Avalos <coproscefalo@gmail.com>	132	Contact: Azael Avalos <coproscefalo@gmail.com>
120	Description: This file controls the Sleep & Music state, which values can be:	133	Description: This file controls the Sleep & Music state, which values can be:
		134
121	* 0 -> Disabled	135	* 0 -> Disabled
122	* 1 -> Enabled	136	* 1 -> Enabled
		137
123	Note that this feature only works when connected to power, if	138	Note that this feature only works when connected to power, if
124	you want to use it under battery, see the entry named	139	you want to use it under battery, see the entry named
125	"sleep_functions_on_battery"	140	"sleep_functions_on_battery"
@@ -138,6 +153,7 @@ KernelVersion: 4.0 · 12 unmodified lines
138	Contact: Azael Avalos <coproscefalo@gmail.com>	153	Contact: Azael Avalos <coproscefalo@gmail.com>
139	Description: This file controls the state of the internal fan, valid	154	Description: This file controls the state of the internal fan, valid
140	values are:	155	values are:
		156
141	* 0 -> OFF	157	* 0 -> OFF
142	* 1 -> ON	158	* 1 -> ON
143		159
@@ -147,8 +163,10 @@ KernelVersion: 4.0 · 3 unmodified lines
147	Contact: Azael Avalos <coproscefalo@gmail.com>	163	Contact: Azael Avalos <coproscefalo@gmail.com>
148	Description: This file controls the Special Functions (hotkeys) operation	164	Description: This file controls the Special Functions (hotkeys) operation
149	mode, valid values are:	165	mode, valid values are:
		166
150	* 0 -> Normal Operation	167	* 0 -> Normal Operation
151	* 1 -> Special Functions	168	* 1 -> Special Functions
		169
152	In the "Normal Operation" mode, the F{1-12} keys are as usual	170	In the "Normal Operation" mode, the F{1-12} keys are as usual
153	and the hotkeys are accessed via FN-F{1-12}.	171	and the hotkeys are accessed via FN-F{1-12}.
154	In the "Special Functions" mode, the F{1-12} keys trigger the	172	In the "Special Functions" mode, the F{1-12} keys trigger the
@@ -163,8 +181,10 @@ KernelVersion: 4.0 · 8 unmodified lines
163	Contact: Azael Avalos <coproscefalo@gmail.com>	181	Contact: Azael Avalos <coproscefalo@gmail.com>
164	Description: This file controls whether the laptop should turn ON whenever	182	Description: This file controls whether the laptop should turn ON whenever
165	the LID is opened, valid values are:	183	the LID is opened, valid values are:
		184
166	* 0 -> Disabled	185	* 0 -> Disabled
167	* 1 -> Enabled	186	* 1 -> Enabled
		187
168	Note that toggling this value requires a reboot for changes to	188	Note that toggling this value requires a reboot for changes to
169	take effect.	189	take effect.
170	Users: KToshiba	190	Users: KToshiba
@@ -174,8 +194,10 @@ Date: February 12, 2015 · 3 unmodified lines
174	KernelVersion: 4.0	194	KernelVersion: 4.0
175	Contact: Azael Avalos <coproscefalo@gmail.com>	195	Contact: Azael Avalos <coproscefalo@gmail.com>
176	Description: This file controls the USB 3 functionality, valid values are:	196	Description: This file controls the USB 3 functionality, valid values are:
		197
177	* 0 -> Disabled (Acts as a regular USB 2)	198	* 0 -> Disabled (Acts as a regular USB 2)
178	* 1 -> Enabled (Full USB 3 functionality)	199	* 1 -> Enabled (Full USB 3 functionality)
		200
179	Note that toggling this value requires a reboot for changes to	201	Note that toggling this value requires a reboot for changes to
180	take effect.	202	take effect.
181	Users: KToshiba	203	Users: KToshiba
@@ -188,10 +210,14 @@ Description: This file controls the Cooling Method feature. · 6 unmodified lines
188	Reading this file prints two values, the first is the actual cooling method	210	Reading this file prints two values, the first is the actual cooling method
189	and the second is the maximum cooling method supported.	211	and the second is the maximum cooling method supported.
190	When the maximum cooling method is ONE, valid values are:	212	When the maximum cooling method is ONE, valid values are:
		213
191	* 0 -> Maximum Performance	214	* 0 -> Maximum Performance
192	* 1 -> Battery Optimized	215	* 1 -> Battery Optimized
		216
193	When the maximum cooling method is TWO, valid values are:	217	When the maximum cooling method is TWO, valid values are:
		218
194	* 0 -> Maximum Performance	219	* 0 -> Maximum Performance
195	* 1 -> Performance	220	* 1 -> Performance
196	* 2 -> Battery Optimized	221	* 2 -> Battery Optimized
		222
197	Users: KToshiba	223	Users: KToshiba

Documentation/ABI/testing/sysfs-driver-toshiba_haps+2−0

@@ -4,10 +4,12 @@ KernelVersion: 3.17 · 3 unmodified lines
4	Contact: Azael Avalos <coproscefalo@gmail.com>	4	Contact: Azael Avalos <coproscefalo@gmail.com>
5	Description: This file controls the built-in accelerometer protection level,	5	Description: This file controls the built-in accelerometer protection level,
6	valid values are:	6	valid values are:
		7
7	* 0 -> Disabled	8	* 0 -> Disabled
8	* 1 -> Low	9	* 1 -> Low
9	* 2 -> Medium	10	* 2 -> Medium
10	* 3 -> High	11	* 3 -> High
		12
11	The default potection value is set to 2 (Medium).	13	The default potection value is set to 2 (Medium).
12	Users: KToshiba	14	Users: KToshiba
13		15

Documentation/ABI/testing/sysfs-driver-ufs+181−47

@@ -18,6 +18,7 @@ Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> · 17 unmodified lines
18	Description: This file shows the device type. This is one of the UFS	18	Description: This file shows the device type. This is one of the UFS
19	device descriptor parameters. The full information about	19	device descriptor parameters. The full information about
20	the descriptor could be found at UFS specifications 2.1.	20	the descriptor could be found at UFS specifications 2.1.
		21
21	The file is read only.	22	The file is read only.
22		23
23	What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/device_class	24	What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/device_class
@@ -26,6 +27,7 @@ Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> · 2 unmodified lines
26	Description: This file shows the device class. This is one of the UFS	27	Description: This file shows the device class. This is one of the UFS
27	device descriptor parameters. The full information about	28	device descriptor parameters. The full information about
28	the descriptor could be found at UFS specifications 2.1.	29	the descriptor could be found at UFS specifications 2.1.
		30
29	The file is read only.	31	The file is read only.
30		32
31	What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/device_sub_class	33	What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/device_sub_class
@@ -34,6 +36,7 @@ Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> · 2 unmodified lines
34	Description: This file shows the UFS storage subclass. This is one of	36	Description: This file shows the UFS storage subclass. This is one of
35	the UFS device descriptor parameters. The full information	37	the UFS device descriptor parameters. The full information
36	about the descriptor could be found at UFS specifications 2.1.	38	about the descriptor could be found at UFS specifications 2.1.
		39
37	The file is read only.	40	The file is read only.
38		41
39	What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/protocol	42	What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/protocol
@@ -43,6 +46,7 @@ Description: This file shows the protocol supported by an UFS device. · 3 unmodified lines
43	This is one of the UFS device descriptor parameters.	46	This is one of the UFS device descriptor parameters.
44	The full information about the descriptor could be found	47	The full information about the descriptor could be found
45	at UFS specifications 2.1.	48	at UFS specifications 2.1.
		49
46	The file is read only.	50	The file is read only.
47		51
48	What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/number_of_luns	52	What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/number_of_luns
@@ -51,6 +55,7 @@ Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> · 2 unmodified lines
51	Description: This file shows number of logical units. This is one of	55	Description: This file shows number of logical units. This is one of
52	the UFS device descriptor parameters. The full information	56	the UFS device descriptor parameters. The full information
53	about the descriptor could be found at UFS specifications 2.1.	57	about the descriptor could be found at UFS specifications 2.1.
		58
54	The file is read only.	59	The file is read only.
55		60
56	What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/number_of_wluns	61	What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/number_of_wluns
@@ -60,6 +65,7 @@ Description: This file shows number of well known logical units. · 3 unmodified lines
60	This is one of the UFS device descriptor parameters.	65	This is one of the UFS device descriptor parameters.
61	The full information about the descriptor could be found	66	The full information about the descriptor could be found
62	at UFS specifications 2.1.	67	at UFS specifications 2.1.
		68
63	The file is read only.	69	The file is read only.
64		70
65	What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/boot_enable	71	What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/boot_enable
@@ -69,6 +75,7 @@ Description: This file shows value that indicates whether the device is · 3 unmodified lines
69	enabled for boot. This is one of the UFS device descriptor	75	enabled for boot. This is one of the UFS device descriptor
70	parameters. The full information about the descriptor could	76	parameters. The full information about the descriptor could
71	be found at UFS specifications 2.1.	77	be found at UFS specifications 2.1.
		78
72	The file is read only.	79	The file is read only.
73		80
74	What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/descriptor_access_enable	81	What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/descriptor_access_enable
@@ -79,6 +86,7 @@ Description: This file shows value that indicates whether the device · 4 unmodified lines
79	of the boot sequence. This is one of the UFS device descriptor	86	of the boot sequence. This is one of the UFS device descriptor
80	parameters. The full information about the descriptor could	87	parameters. The full information about the descriptor could
81	be found at UFS specifications 2.1.	88	be found at UFS specifications 2.1.
		89
82	The file is read only.	90	The file is read only.
83		91
84	What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/initial_power_mode	92	What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/initial_power_mode
@@ -88,6 +96,7 @@ Description: This file shows value that defines the power mode after · 3 unmodified lines
88	device initialization or hardware reset. This is one of	96	device initialization or hardware reset. This is one of
89	the UFS device descriptor parameters. The full information	97	the UFS device descriptor parameters. The full information
90	about the descriptor could be found at UFS specifications 2.1.	98	about the descriptor could be found at UFS specifications 2.1.
		99
91	The file is read only.	100	The file is read only.
92		101
93	What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/high_priority_lun	102	What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/high_priority_lun
@@ -96,6 +105,7 @@ Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> · 2 unmodified lines
96	Description: This file shows the high priority lun. This is one of	105	Description: This file shows the high priority lun. This is one of
97	the UFS device descriptor parameters. The full information	106	the UFS device descriptor parameters. The full information
98	about the descriptor could be found at UFS specifications 2.1.	107	about the descriptor could be found at UFS specifications 2.1.
		108
99	The file is read only.	109	The file is read only.
100		110
101	What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/secure_removal_type	111	What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/secure_removal_type
@@ -104,6 +114,7 @@ Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> · 2 unmodified lines
104	Description: This file shows the secure removal type. This is one of	114	Description: This file shows the secure removal type. This is one of
105	the UFS device descriptor parameters. The full information	115	the UFS device descriptor parameters. The full information
106	about the descriptor could be found at UFS specifications 2.1.	116	about the descriptor could be found at UFS specifications 2.1.
		117
107	The file is read only.	118	The file is read only.
108		119
109	What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/support_security_lun	120	What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/support_security_lun
@@ -113,6 +124,7 @@ Description: This file shows whether the security lun is supported. · 3 unmodified lines
113	This is one of the UFS device descriptor parameters.	124	This is one of the UFS device descriptor parameters.
114	The full information about the descriptor could be found	125	The full information about the descriptor could be found
115	at UFS specifications 2.1.	126	at UFS specifications 2.1.
		127
116	The file is read only.	128	The file is read only.
117		129
118	What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/bkops_termination_latency	130	What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/bkops_termination_latency
@@ -122,6 +134,7 @@ Description: This file shows the background operations termination · 3 unmodified lines
122	latency. This is one of the UFS device descriptor parameters.	134	latency. This is one of the UFS device descriptor parameters.
123	The full information about the descriptor could be found	135	The full information about the descriptor could be found
124	at UFS specifications 2.1.	136	at UFS specifications 2.1.
		137
125	The file is read only.	138	The file is read only.
126		139
127	What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/initial_active_icc_level	140	What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/initial_active_icc_level
@@ -130,6 +143,7 @@ Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> · 2 unmodified lines
130	Description: This file shows the initial active ICC level. This is one	143	Description: This file shows the initial active ICC level. This is one
131	of the UFS device descriptor parameters. The full information	144	of the UFS device descriptor parameters. The full information
132	about the descriptor could be found at UFS specifications 2.1.	145	about the descriptor could be found at UFS specifications 2.1.
		146
133	The file is read only.	147	The file is read only.
134		148
135	What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/specification_version	149	What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/specification_version
@@ -138,6 +152,7 @@ Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> · 2 unmodified lines
138	Description: This file shows the specification version. This is one	152	Description: This file shows the specification version. This is one
139	of the UFS device descriptor parameters. The full information	153	of the UFS device descriptor parameters. The full information
140	about the descriptor could be found at UFS specifications 2.1.	154	about the descriptor could be found at UFS specifications 2.1.
		155
141	The file is read only.	156	The file is read only.
142		157
143	What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/manufacturing_date	158	What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/manufacturing_date
@@ -147,6 +162,7 @@ Description: This file shows the manufacturing date in BCD format. · 3 unmodified lines
147	This is one of the UFS device descriptor parameters.	162	This is one of the UFS device descriptor parameters.
148	The full information about the descriptor could be found	163	The full information about the descriptor could be found
149	at UFS specifications 2.1.	164	at UFS specifications 2.1.
		165
150	The file is read only.	166	The file is read only.
151		167
152	What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/manufacturer_id	168	What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/manufacturer_id
@@ -155,6 +171,7 @@ Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> · 2 unmodified lines
155	Description: This file shows the manufacturee ID. This is one of the	171	Description: This file shows the manufacturee ID. This is one of the
156	UFS device descriptor parameters. The full information about	172	UFS device descriptor parameters. The full information about
157	the descriptor could be found at UFS specifications 2.1.	173	the descriptor could be found at UFS specifications 2.1.
		174
158	The file is read only.	175	The file is read only.
159		176
160	What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/rtt_capability	177	What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/rtt_capability
@@ -164,6 +181,7 @@ Description: This file shows the maximum number of outstanding RTTs · 3 unmodified lines
164	supported by the device. This is one of the UFS device	181	supported by the device. This is one of the UFS device
165	descriptor parameters. The full information about	182	descriptor parameters. The full information about
166	the descriptor could be found at UFS specifications 2.1.	183	the descriptor could be found at UFS specifications 2.1.
		184
167	The file is read only.	185	The file is read only.
168		186
169	What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/rtc_update	187	What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/rtc_update
@@ -173,6 +191,7 @@ Description: This file shows the frequency and method of the realtime · 3 unmodified lines
173	clock update. This is one of the UFS device descriptor	191	clock update. This is one of the UFS device descriptor
174	parameters. The full information about the descriptor	192	parameters. The full information about the descriptor
175	could be found at UFS specifications 2.1.	193	could be found at UFS specifications 2.1.
		194
176	The file is read only.	195	The file is read only.
177		196
178	What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/ufs_features	197	What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/ufs_features
@@ -182,6 +201,7 @@ Description: This file shows which features are supported by the device. · 3 unmodified lines
182	This is one of the UFS device descriptor parameters.	201	This is one of the UFS device descriptor parameters.
183	The full information about the descriptor could be	202	The full information about the descriptor could be
184	found at UFS specifications 2.1.	203	found at UFS specifications 2.1.
		204
185	The file is read only.	205	The file is read only.
186		206
187	What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/ffu_timeout	207	What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/ffu_timeout
@@ -190,6 +210,7 @@ Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> · 2 unmodified lines
190	Description: This file shows the FFU timeout. This is one of the	210	Description: This file shows the FFU timeout. This is one of the
191	UFS device descriptor parameters. The full information	211	UFS device descriptor parameters. The full information
192	about the descriptor could be found at UFS specifications 2.1.	212	about the descriptor could be found at UFS specifications 2.1.
		213
193	The file is read only.	214	The file is read only.
194		215
195	What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/queue_depth	216	What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/queue_depth
@@ -198,6 +219,7 @@ Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> · 2 unmodified lines
198	Description: This file shows the device queue depth. This is one of the	219	Description: This file shows the device queue depth. This is one of the
199	UFS device descriptor parameters. The full information	220	UFS device descriptor parameters. The full information
200	about the descriptor could be found at UFS specifications 2.1.	221	about the descriptor could be found at UFS specifications 2.1.
		222
201	The file is read only.	223	The file is read only.
202		224
203	What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/device_version	225	What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/device_version
@@ -206,6 +228,7 @@ Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> · 2 unmodified lines
206	Description: This file shows the device version. This is one of the	228	Description: This file shows the device version. This is one of the
207	UFS device descriptor parameters. The full information	229	UFS device descriptor parameters. The full information
208	about the descriptor could be found at UFS specifications 2.1.	230	about the descriptor could be found at UFS specifications 2.1.
		231
209	The file is read only.	232	The file is read only.
210		233
211	What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/number_of_secure_wpa	234	What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/number_of_secure_wpa
@@ -215,6 +238,7 @@ Description: This file shows number of secure write protect areas · 3 unmodified lines
215	supported by the device. This is one of the UFS device	238	supported by the device. This is one of the UFS device
216	descriptor parameters. The full information about	239	descriptor parameters. The full information about
217	the descriptor could be found at UFS specifications 2.1.	240	the descriptor could be found at UFS specifications 2.1.
		241
218	The file is read only.	242	The file is read only.
219		243
220	What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/psa_max_data_size	244	What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/psa_max_data_size
@@ -225,6 +249,7 @@ Description: This file shows the maximum amount of data that may be · 4 unmodified lines
225	This is one of the UFS device descriptor parameters.	249	This is one of the UFS device descriptor parameters.
226	The full information about the descriptor could be found	250	The full information about the descriptor could be found
227	at UFS specifications 2.1.	251	at UFS specifications 2.1.
		252
228	The file is read only.	253	The file is read only.
229		254
230	What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/psa_state_timeout	255	What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/psa_state_timeout
@@ -234,6 +259,7 @@ Description: This file shows the command maximum timeout for a change · 3 unmodified lines
234	in PSA state. This is one of the UFS device descriptor	259	in PSA state. This is one of the UFS device descriptor
235	parameters. The full information about the descriptor could	260	parameters. The full information about the descriptor could
236	be found at UFS specifications 2.1.	261	be found at UFS specifications 2.1.
		262
237	The file is read only.	263	The file is read only.
238		264
239		265
@@ -244,6 +270,7 @@ Description: This file shows the MIPI UniPro version number in BCD format. · 4 unmodified lines
244	This is one of the UFS interconnect descriptor parameters.	270	This is one of the UFS interconnect descriptor parameters.
245	The full information about the descriptor could be found at	271	The full information about the descriptor could be found at
246	UFS specifications 2.1.	272	UFS specifications 2.1.
		273
247	The file is read only.	274	The file is read only.
248		275
249	What: /sys/bus/platform/drivers/ufshcd/*/interconnect_descriptor/mphy_version	276	What: /sys/bus/platform/drivers/ufshcd/*/interconnect_descriptor/mphy_version
@@ -253,6 +280,7 @@ Description: This file shows the MIPI M-PHY version number in BCD format. · 3 unmodified lines
253	This is one of the UFS interconnect descriptor parameters.	280	This is one of the UFS interconnect descriptor parameters.
254	The full information about the descriptor could be found at	281	The full information about the descriptor could be found at
255	UFS specifications 2.1.	282	UFS specifications 2.1.
		283
256	The file is read only.	284	The file is read only.
257		285
258		286
@@ -264,6 +292,7 @@ Description: This file shows the total memory quantity available to · 5 unmodified lines
264	of the UFS geometry descriptor parameters. The full	292	of the UFS geometry descriptor parameters. The full
265	information about the descriptor could be found at	293	information about the descriptor could be found at
266	UFS specifications 2.1.	294	UFS specifications 2.1.
		295
267	The file is read only.	296	The file is read only.
268		297
269	What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/max_number_of_luns	298	What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/max_number_of_luns
@@ -273,6 +302,7 @@ Description: This file shows the maximum number of logical units · 3 unmodified lines
273	supported by the UFS device. This is one of the UFS	302	supported by the UFS device. This is one of the UFS
274	geometry descriptor parameters. The full information about	303	geometry descriptor parameters. The full information about
275	the descriptor could be found at UFS specifications 2.1.	304	the descriptor could be found at UFS specifications 2.1.
		305
276	The file is read only.	306	The file is read only.
277		307
278	What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/segment_size	308	What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/segment_size
@@ -281,6 +311,7 @@ Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> · 2 unmodified lines
281	Description: This file shows the segment size. This is one of the UFS	311	Description: This file shows the segment size. This is one of the UFS
282	geometry descriptor parameters. The full information about	312	geometry descriptor parameters. The full information about
283	the descriptor could be found at UFS specifications 2.1.	313	the descriptor could be found at UFS specifications 2.1.
		314
284	The file is read only.	315	The file is read only.
285		316
286	What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/allocation_unit_size	317	What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/allocation_unit_size
@@ -289,6 +320,7 @@ Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> · 2 unmodified lines
289	Description: This file shows the allocation unit size. This is one of	320	Description: This file shows the allocation unit size. This is one of
290	the UFS geometry descriptor parameters. The full information	321	the UFS geometry descriptor parameters. The full information
291	about the descriptor could be found at UFS specifications 2.1.	322	about the descriptor could be found at UFS specifications 2.1.
		323
292	The file is read only.	324	The file is read only.
293		325
294	What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/min_addressable_block_size	326	What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/min_addressable_block_size
@@ -298,6 +330,7 @@ Description: This file shows the minimum addressable block size. This · 3 unmodified lines
298	is one of the UFS geometry descriptor parameters. The full	330	is one of the UFS geometry descriptor parameters. The full
299	information about the descriptor could be found at UFS	331	information about the descriptor could be found at UFS
300	specifications 2.1.	332	specifications 2.1.
		333
301	The file is read only.	334	The file is read only.
302		335
303	What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/optimal_read_block_size	336	What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/optimal_read_block_size
@@ -307,6 +340,7 @@ Description: This file shows the optimal read block size. This is one · 3 unmodified lines
307	of the UFS geometry descriptor parameters. The full	340	of the UFS geometry descriptor parameters. The full
308	information about the descriptor could be found at UFS	341	information about the descriptor could be found at UFS
309	specifications 2.1.	342	specifications 2.1.
		343
310	The file is read only.	344	The file is read only.
311		345
312	What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/optimal_write_block_size	346	What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/optimal_write_block_size
@@ -316,6 +350,7 @@ Description: This file shows the optimal write block size. This is one · 3 unmodified lines
316	of the UFS geometry descriptor parameters. The full	350	of the UFS geometry descriptor parameters. The full
317	information about the descriptor could be found at UFS	351	information about the descriptor could be found at UFS
318	specifications 2.1.	352	specifications 2.1.
		353
319	The file is read only.	354	The file is read only.
320		355
321	What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/max_in_buffer_size	356	What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/max_in_buffer_size
@@ -325,6 +360,7 @@ Description: This file shows the maximum data-in buffer size. This · 3 unmodified lines
325	is one of the UFS geometry descriptor parameters. The full	360	is one of the UFS geometry descriptor parameters. The full
326	information about the descriptor could be found at UFS	361	information about the descriptor could be found at UFS
327	specifications 2.1.	362	specifications 2.1.
		363
328	The file is read only.	364	The file is read only.
329		365
330	What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/max_out_buffer_size	366	What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/max_out_buffer_size
@@ -334,6 +370,7 @@ Description: This file shows the maximum data-out buffer size. This · 3 unmodified lines
334	is one of the UFS geometry descriptor parameters. The full	370	is one of the UFS geometry descriptor parameters. The full
335	information about the descriptor could be found at UFS	371	information about the descriptor could be found at UFS
336	specifications 2.1.	372	specifications 2.1.
		373
337	The file is read only.	374	The file is read only.
338		375
339	What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/rpmb_rw_size	376	What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/rpmb_rw_size
@@ -343,6 +380,7 @@ Description: This file shows the maximum number of RPMB frames allowed · 3 unmodified lines
343	in Security Protocol In/Out. This is one of the UFS geometry	380	in Security Protocol In/Out. This is one of the UFS geometry
344	descriptor parameters. The full information about the	381	descriptor parameters. The full information about the
345	descriptor could be found at UFS specifications 2.1.	382	descriptor could be found at UFS specifications 2.1.
		383
346	The file is read only.	384	The file is read only.
347		385
348	What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/dyn_capacity_resource_policy	386	What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/dyn_capacity_resource_policy
@@ -352,6 +390,7 @@ Description: This file shows the dynamic capacity resource policy. This · 3 unmodified lines
352	is one of the UFS geometry descriptor parameters. The full	390	is one of the UFS geometry descriptor parameters. The full
353	information about the descriptor could be found at	391	information about the descriptor could be found at
354	UFS specifications 2.1.	392	UFS specifications 2.1.
		393
355	The file is read only.	394	The file is read only.
356		395
357	What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/data_ordering	396	What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/data_ordering
@@ -361,6 +400,7 @@ Description: This file shows support for out-of-order data transfer. · 3 unmodified lines
361	This is one of the UFS geometry descriptor parameters.	400	This is one of the UFS geometry descriptor parameters.
362	The full information about the descriptor could be found at	401	The full information about the descriptor could be found at
363	UFS specifications 2.1.	402	UFS specifications 2.1.
		403
364	The file is read only.	404	The file is read only.
365		405
366	What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/max_number_of_contexts	406	What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/max_number_of_contexts
@@ -370,6 +410,7 @@ Description: This file shows maximum available number of contexts which · 3 unmodified lines
370	are supported by the device. This is one of the UFS geometry	410	are supported by the device. This is one of the UFS geometry
371	descriptor parameters. The full information about the	411	descriptor parameters. The full information about the
372	descriptor could be found at UFS specifications 2.1.	412	descriptor could be found at UFS specifications 2.1.
		413
373	The file is read only.	414	The file is read only.
374		415
375	What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/sys_data_tag_unit_size	416	What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/sys_data_tag_unit_size
@@ -378,6 +419,7 @@ Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> · 2 unmodified lines
378	Description: This file shows system data tag unit size. This is one of	419	Description: This file shows system data tag unit size. This is one of
379	the UFS geometry descriptor parameters. The full information	420	the UFS geometry descriptor parameters. The full information
380	about the descriptor could be found at UFS specifications 2.1.	421	about the descriptor could be found at UFS specifications 2.1.
		422
381	The file is read only.	423	The file is read only.
382		424
383	What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/sys_data_tag_resource_size	425	What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/sys_data_tag_resource_size
@@ -388,6 +430,7 @@ Description: This file shows maximum storage area size allocated by · 4 unmodified lines
388	This is one of the UFS geometry descriptor parameters.	430	This is one of the UFS geometry descriptor parameters.
389	The full information about the descriptor could be found at	431	The full information about the descriptor could be found at
390	UFS specifications 2.1.	432	UFS specifications 2.1.
		433
391	The file is read only.	434	The file is read only.
392		435
393	What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/secure_removal_types	436	What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/secure_removal_types
@@ -397,6 +440,7 @@ Description: This file shows supported secure removal types. This is · 3 unmodified lines
397	one of the UFS geometry descriptor parameters. The full	440	one of the UFS geometry descriptor parameters. The full
398	information about the descriptor could be found at	441	information about the descriptor could be found at
399	UFS specifications 2.1.	442	UFS specifications 2.1.
		443
400	The file is read only.	444	The file is read only.
401		445
402	What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/memory_types	446	What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/memory_types
@@ -406,6 +450,7 @@ Description: This file shows supported memory types. This is one of · 3 unmodified lines
406	the UFS geometry descriptor parameters. The full	450	the UFS geometry descriptor parameters. The full
407	information about the descriptor could be found at	451	information about the descriptor could be found at
408	UFS specifications 2.1.	452	UFS specifications 2.1.
		453
409	The file is read only.	454	The file is read only.
410		455
411	What: /sys/bus/platform/drivers/ufshcd//geometry_descriptor/_memory_max_alloc_units	456	What: /sys/bus/platform/drivers/ufshcd//geometry_descriptor/_memory_max_alloc_units
@@ -416,6 +461,7 @@ Description: This file shows the maximum number of allocation units for · 4 unmodified lines
416	enhanced type 1-4). This is one of the UFS geometry	461	enhanced type 1-4). This is one of the UFS geometry
417	descriptor parameters. The full information about the	462	descriptor parameters. The full information about the
418	descriptor could be found at UFS specifications 2.1.	463	descriptor could be found at UFS specifications 2.1.
		464
419	The file is read only.	465	The file is read only.
420		466
421	What: /sys/bus/platform/drivers/ufshcd//geometry_descriptor/_memory_capacity_adjustment_factor	467	What: /sys/bus/platform/drivers/ufshcd//geometry_descriptor/_memory_capacity_adjustment_factor
@@ -426,6 +472,7 @@ Description: This file shows the memory capacity adjustment factor for · 4 unmodified lines
426	enhanced type 1-4). This is one of the UFS geometry	472	enhanced type 1-4). This is one of the UFS geometry
427	descriptor parameters. The full information about the	473	descriptor parameters. The full information about the
428	descriptor could be found at UFS specifications 2.1.	474	descriptor could be found at UFS specifications 2.1.
		475
429	The file is read only.	476	The file is read only.
430		477
431		478
@@ -436,6 +483,7 @@ Description: This file shows preend of life information. This is one · 4 unmodified lines
436	of the UFS health descriptor parameters. The full	483	of the UFS health descriptor parameters. The full
437	information about the descriptor could be found at	484	information about the descriptor could be found at
438	UFS specifications 2.1.	485	UFS specifications 2.1.
		486
439	The file is read only.	487	The file is read only.
440		488
441	What: /sys/bus/platform/drivers/ufshcd/*/health_descriptor/life_time_estimation_a	489	What: /sys/bus/platform/drivers/ufshcd/*/health_descriptor/life_time_estimation_a
@@ -445,6 +493,7 @@ Description: This file shows indication of the device life time · 3 unmodified lines
445	(method a). This is one of the UFS health descriptor	493	(method a). This is one of the UFS health descriptor
446	parameters. The full information about the descriptor	494	parameters. The full information about the descriptor
447	could be found at UFS specifications 2.1.	495	could be found at UFS specifications 2.1.
		496
448	The file is read only.	497	The file is read only.
449		498
450	What: /sys/bus/platform/drivers/ufshcd/*/health_descriptor/life_time_estimation_b	499	What: /sys/bus/platform/drivers/ufshcd/*/health_descriptor/life_time_estimation_b
@@ -454,6 +503,7 @@ Description: This file shows indication of the device life time · 3 unmodified lines
454	(method b). This is one of the UFS health descriptor	503	(method b). This is one of the UFS health descriptor
455	parameters. The full information about the descriptor	504	parameters. The full information about the descriptor
456	could be found at UFS specifications 2.1.	505	could be found at UFS specifications 2.1.
		506
457	The file is read only.	507	The file is read only.
458		508
459		509
@@ -464,6 +514,7 @@ Description: This file shows maximum VCC, VCCQ and VCCQ2 value for · 4 unmodified lines
464	active ICC levels from 0 to 15. This is one of the UFS	514	active ICC levels from 0 to 15. This is one of the UFS
465	power descriptor parameters. The full information about	515	power descriptor parameters. The full information about
466	the descriptor could be found at UFS specifications 2.1.	516	the descriptor could be found at UFS specifications 2.1.
		517
467	The file is read only.	518	The file is read only.
468		519
469		520
@@ -473,6 +524,7 @@ Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> · 3 unmodified lines
473	Description: This file contains a device manufactureer name string.	524	Description: This file contains a device manufactureer name string.
474	The full information about the descriptor could be found at	525	The full information about the descriptor could be found at
475	UFS specifications 2.1.	526	UFS specifications 2.1.
		527
476	The file is read only.	528	The file is read only.
477		529
478	What: /sys/bus/platform/drivers/ufshcd/*/string_descriptors/product_name	530	What: /sys/bus/platform/drivers/ufshcd/*/string_descriptors/product_name
@@ -480,6 +532,7 @@ Date: February 2018 · 1 unmodified line
480	Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>	532	Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>
481	Description: This file contains a product name string. The full information	533	Description: This file contains a product name string. The full information
482	about the descriptor could be found at UFS specifications 2.1.	534	about the descriptor could be found at UFS specifications 2.1.
		535
483	The file is read only.	536	The file is read only.
484		537
485	What: /sys/bus/platform/drivers/ufshcd/*/string_descriptors/oem_id	538	What: /sys/bus/platform/drivers/ufshcd/*/string_descriptors/oem_id
@@ -487,6 +540,7 @@ Date: February 2018 · 1 unmodified line
487	Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>	540	Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>
488	Description: This file contains a OEM ID string. The full information	541	Description: This file contains a OEM ID string. The full information
489	about the descriptor could be found at UFS specifications 2.1.	542	about the descriptor could be found at UFS specifications 2.1.
		543
490	The file is read only.	544	The file is read only.
491		545
492	What: /sys/bus/platform/drivers/ufshcd/*/string_descriptors/serial_number	546	What: /sys/bus/platform/drivers/ufshcd/*/string_descriptors/serial_number
@@ -495,6 +549,7 @@ Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> · 2 unmodified lines
495	Description: This file contains a device serial number string. The full	549	Description: This file contains a device serial number string. The full
496	information about the descriptor could be found at	550	information about the descriptor could be found at
497	UFS specifications 2.1.	551	UFS specifications 2.1.
		552
498	The file is read only.	553	The file is read only.
499		554
500	What: /sys/bus/platform/drivers/ufshcd/*/string_descriptors/product_revision	555	What: /sys/bus/platform/drivers/ufshcd/*/string_descriptors/product_revision
@@ -503,6 +558,7 @@ Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> · 2 unmodified lines
503	Description: This file contains a product revision string. The full	558	Description: This file contains a product revision string. The full
504	information about the descriptor could be found at	559	information about the descriptor could be found at
505	UFS specifications 2.1.	560	UFS specifications 2.1.
		561
506	The file is read only.	562	The file is read only.
507		563
508		564
@@ -512,6 +568,7 @@ Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> · 3 unmodified lines
512	Description: This file shows boot LUN information. This is one of	568	Description: This file shows boot LUN information. This is one of
513	the UFS unit descriptor parameters. The full information	569	the UFS unit descriptor parameters. The full information
514	about the descriptor could be found at UFS specifications 2.1.	570	about the descriptor could be found at UFS specifications 2.1.
		571
515	The file is read only.	572	The file is read only.
516		573
517	What: /sys/class/scsi_device/*/device/unit_descriptor/lun_write_protect	574	What: /sys/class/scsi_device/*/device/unit_descriptor/lun_write_protect
@@ -520,6 +577,7 @@ Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> · 2 unmodified lines
520	Description: This file shows LUN write protection status. This is one of	577	Description: This file shows LUN write protection status. This is one of
521	the UFS unit descriptor parameters. The full information	578	the UFS unit descriptor parameters. The full information
522	about the descriptor could be found at UFS specifications 2.1.	579	about the descriptor could be found at UFS specifications 2.1.
		580
523	The file is read only.	581	The file is read only.
524		582
525	What: /sys/class/scsi_device/*/device/unit_descriptor/lun_queue_depth	583	What: /sys/class/scsi_device/*/device/unit_descriptor/lun_queue_depth
@@ -528,6 +586,7 @@ Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> · 2 unmodified lines
528	Description: This file shows LUN queue depth. This is one of the UFS	586	Description: This file shows LUN queue depth. This is one of the UFS
529	unit descriptor parameters. The full information about	587	unit descriptor parameters. The full information about
530	the descriptor could be found at UFS specifications 2.1.	588	the descriptor could be found at UFS specifications 2.1.
		589
531	The file is read only.	590	The file is read only.
532		591
533	What: /sys/class/scsi_device/*/device/unit_descriptor/psa_sensitive	592	What: /sys/class/scsi_device/*/device/unit_descriptor/psa_sensitive
@@ -536,6 +595,7 @@ Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> · 2 unmodified lines
536	Description: This file shows PSA sensitivity. This is one of the UFS	595	Description: This file shows PSA sensitivity. This is one of the UFS
537	unit descriptor parameters. The full information about	596	unit descriptor parameters. The full information about
538	the descriptor could be found at UFS specifications 2.1.	597	the descriptor could be found at UFS specifications 2.1.
		598
539	The file is read only.	599	The file is read only.
540		600
541	What: /sys/class/scsi_device/*/device/unit_descriptor/lun_memory_type	601	What: /sys/class/scsi_device/*/device/unit_descriptor/lun_memory_type
@@ -544,6 +604,7 @@ Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> · 2 unmodified lines
544	Description: This file shows LUN memory type. This is one of the UFS	604	Description: This file shows LUN memory type. This is one of the UFS
545	unit descriptor parameters. The full information about	605	unit descriptor parameters. The full information about
546	the descriptor could be found at UFS specifications 2.1.	606	the descriptor could be found at UFS specifications 2.1.
		607
547	The file is read only.	608	The file is read only.
548		609
549	What: /sys/class/scsi_device/*/device/unit_descriptor/data_reliability	610	What: /sys/class/scsi_device/*/device/unit_descriptor/data_reliability
@@ -553,6 +614,7 @@ Description: This file defines the device behavior when a power failure · 3 unmodified lines
553	occurs during a write operation. This is one of the UFS	614	occurs during a write operation. This is one of the UFS
554	unit descriptor parameters. The full information about	615	unit descriptor parameters. The full information about
555	the descriptor could be found at UFS specifications 2.1.	616	the descriptor could be found at UFS specifications 2.1.
		617
556	The file is read only.	618	The file is read only.
557		619
558	What: /sys/class/scsi_device/*/device/unit_descriptor/logical_block_size	620	What: /sys/class/scsi_device/*/device/unit_descriptor/logical_block_size
@@ -562,6 +624,7 @@ Description: This file shows the size of addressable logical blocks · 3 unmodified lines
562	(calculated as an exponent with base 2). This is one of	624	(calculated as an exponent with base 2). This is one of
563	the UFS unit descriptor parameters. The full information about	625	the UFS unit descriptor parameters. The full information about
564	the descriptor could be found at UFS specifications 2.1.	626	the descriptor could be found at UFS specifications 2.1.
		627
565	The file is read only.	628	The file is read only.
566		629
567	What: /sys/class/scsi_device/*/device/unit_descriptor/logical_block_count	630	What: /sys/class/scsi_device/*/device/unit_descriptor/logical_block_count
@@ -571,6 +634,7 @@ Description: This file shows total number of addressable logical blocks. · 3 unmodified lines
571	This is one of the UFS unit descriptor parameters. The full	634	This is one of the UFS unit descriptor parameters. The full
572	information about the descriptor could be found at	635	information about the descriptor could be found at
573	UFS specifications 2.1.	636	UFS specifications 2.1.
		637
574	The file is read only.	638	The file is read only.
575		639
576	What: /sys/class/scsi_device/*/device/unit_descriptor/erase_block_size	640	What: /sys/class/scsi_device/*/device/unit_descriptor/erase_block_size
@@ -579,6 +643,7 @@ Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> · 2 unmodified lines
579	Description: This file shows the erase block size. This is one of	643	Description: This file shows the erase block size. This is one of
580	the UFS unit descriptor parameters. The full information	644	the UFS unit descriptor parameters. The full information
581	about the descriptor could be found at UFS specifications 2.1.	645	about the descriptor could be found at UFS specifications 2.1.
		646
582	The file is read only.	647	The file is read only.
583		648
584	What: /sys/class/scsi_device/*/device/unit_descriptor/provisioning_type	649	What: /sys/class/scsi_device/*/device/unit_descriptor/provisioning_type
@@ -587,6 +652,7 @@ Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> · 2 unmodified lines
587	Description: This file shows the thin provisioning type. This is one of	652	Description: This file shows the thin provisioning type. This is one of
588	the UFS unit descriptor parameters. The full information	653	the UFS unit descriptor parameters. The full information
589	about the descriptor could be found at UFS specifications 2.1.	654	about the descriptor could be found at UFS specifications 2.1.
		655
590	The file is read only.	656	The file is read only.
591		657
592	What: /sys/class/scsi_device/*/device/unit_descriptor/physical_memory_resourse_count	658	What: /sys/class/scsi_device/*/device/unit_descriptor/physical_memory_resourse_count
@@ -595,6 +661,7 @@ Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> · 2 unmodified lines
595	Description: This file shows the total physical memory resources. This is	661	Description: This file shows the total physical memory resources. This is
596	one of the UFS unit descriptor parameters. The full information	662	one of the UFS unit descriptor parameters. The full information
597	about the descriptor could be found at UFS specifications 2.1.	663	about the descriptor could be found at UFS specifications 2.1.
		664
598	The file is read only.	665	The file is read only.
599		666
600	What: /sys/class/scsi_device/*/device/unit_descriptor/context_capabilities	667	What: /sys/class/scsi_device/*/device/unit_descriptor/context_capabilities
@@ -603,6 +670,7 @@ Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> · 2 unmodified lines
603	Description: This file shows the context capabilities. This is one of	670	Description: This file shows the context capabilities. This is one of
604	the UFS unit descriptor parameters. The full information	671	the UFS unit descriptor parameters. The full information
605	about the descriptor could be found at UFS specifications 2.1.	672	about the descriptor could be found at UFS specifications 2.1.
		673
606	The file is read only.	674	The file is read only.
607		675
608	What: /sys/class/scsi_device/*/device/unit_descriptor/large_unit_granularity	676	What: /sys/class/scsi_device/*/device/unit_descriptor/large_unit_granularity
@@ -611,6 +679,7 @@ Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> · 2 unmodified lines
611	Description: This file shows the granularity of the LUN. This is one of	679	Description: This file shows the granularity of the LUN. This is one of
612	the UFS unit descriptor parameters. The full information	680	the UFS unit descriptor parameters. The full information
613	about the descriptor could be found at UFS specifications 2.1.	681	about the descriptor could be found at UFS specifications 2.1.
		682
614	The file is read only.	683	The file is read only.
615		684
616		685
@@ -619,6 +688,7 @@ Date: February 2018 · 2 unmodified lines
619	Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>	688	Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>
620	Description: This file shows the device init status. The full information	689	Description: This file shows the device init status. The full information
621	about the flag could be found at UFS specifications 2.1.	690	about the flag could be found at UFS specifications 2.1.
		691
622	The file is read only.	692	The file is read only.
623		693
624	What: /sys/bus/platform/drivers/ufshcd/*/flags/permanent_wpe	694	What: /sys/bus/platform/drivers/ufshcd/*/flags/permanent_wpe
@@ -627,6 +697,7 @@ Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> · 2 unmodified lines
627	Description: This file shows whether permanent write protection is enabled.	697	Description: This file shows whether permanent write protection is enabled.
628	The full information about the flag could be found at	698	The full information about the flag could be found at
629	UFS specifications 2.1.	699	UFS specifications 2.1.
		700
630	The file is read only.	701	The file is read only.
631		702
632	What: /sys/bus/platform/drivers/ufshcd/*/flags/power_on_wpe	703	What: /sys/bus/platform/drivers/ufshcd/*/flags/power_on_wpe
@@ -636,6 +707,7 @@ Description: This file shows whether write protection is enabled on all · 3 unmodified lines
636	logical units configured as power on write protected. The	707	logical units configured as power on write protected. The
637	full information about the flag could be found at	708	full information about the flag could be found at
638	UFS specifications 2.1.	709	UFS specifications 2.1.
		710
639	The file is read only.	711	The file is read only.
640		712
641	What: /sys/bus/platform/drivers/ufshcd/*/flags/bkops_enable	713	What: /sys/bus/platform/drivers/ufshcd/*/flags/bkops_enable
@@ -644,6 +716,7 @@ Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> · 2 unmodified lines
644	Description: This file shows whether the device background operations are	716	Description: This file shows whether the device background operations are
645	enabled. The full information about the flag could be	717	enabled. The full information about the flag could be
646	found at UFS specifications 2.1.	718	found at UFS specifications 2.1.
		719
647	The file is read only.	720	The file is read only.
648		721
649	What: /sys/bus/platform/drivers/ufshcd/*/flags/life_span_mode_enable	722	What: /sys/bus/platform/drivers/ufshcd/*/flags/life_span_mode_enable
@@ -652,6 +725,7 @@ Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> · 2 unmodified lines
652	Description: This file shows whether the device life span mode is enabled.	725	Description: This file shows whether the device life span mode is enabled.
653	The full information about the flag could be found at	726	The full information about the flag could be found at
654	UFS specifications 2.1.	727	UFS specifications 2.1.
		728
655	The file is read only.	729	The file is read only.
656		730
657	What: /sys/bus/platform/drivers/ufshcd/*/flags/phy_resource_removal	731	What: /sys/bus/platform/drivers/ufshcd/*/flags/phy_resource_removal
@@ -660,6 +734,7 @@ Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> · 2 unmodified lines
660	Description: This file shows whether physical resource removal is enable.	734	Description: This file shows whether physical resource removal is enable.
661	The full information about the flag could be found at	735	The full information about the flag could be found at
662	UFS specifications 2.1.	736	UFS specifications 2.1.
		737
663	The file is read only.	738	The file is read only.
664		739
665	What: /sys/bus/platform/drivers/ufshcd/*/flags/busy_rtc	740	What: /sys/bus/platform/drivers/ufshcd/*/flags/busy_rtc
@@ -668,6 +743,7 @@ Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> · 2 unmodified lines
668	Description: This file shows whether the device is executing internal	743	Description: This file shows whether the device is executing internal
669	operation related to real time clock. The full information	744	operation related to real time clock. The full information
670	about the flag could be found at UFS specifications 2.1.	745	about the flag could be found at UFS specifications 2.1.
		746
671	The file is read only.	747	The file is read only.
672		748
673	What: /sys/bus/platform/drivers/ufshcd/*/flags/disable_fw_update	749	What: /sys/bus/platform/drivers/ufshcd/*/flags/disable_fw_update
@@ -676,6 +752,7 @@ Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> · 2 unmodified lines
676	Description: This file shows whether the device FW update is permanently	752	Description: This file shows whether the device FW update is permanently
677	disabled. The full information about the flag could be found	753	disabled. The full information about the flag could be found
678	at UFS specifications 2.1.	754	at UFS specifications 2.1.
		755
679	The file is read only.	756	The file is read only.
680		757
681		758
@@ -685,6 +762,7 @@ Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> · 3 unmodified lines
685	Description: This file provides the boot lun enabled UFS device attribute.	762	Description: This file provides the boot lun enabled UFS device attribute.
686	The full information about the attribute could be found at	763	The full information about the attribute could be found at
687	UFS specifications 2.1.	764	UFS specifications 2.1.
		765
688	The file is read only.	766	The file is read only.
689		767
690	What: /sys/bus/platform/drivers/ufshcd/*/attributes/current_power_mode	768	What: /sys/bus/platform/drivers/ufshcd/*/attributes/current_power_mode
@@ -693,6 +771,7 @@ Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> · 2 unmodified lines
693	Description: This file provides the current power mode UFS device attribute.	771	Description: This file provides the current power mode UFS device attribute.
694	The full information about the attribute could be found at	772	The full information about the attribute could be found at
695	UFS specifications 2.1.	773	UFS specifications 2.1.
		774
696	The file is read only.	775	The file is read only.
697		776
698	What: /sys/bus/platform/drivers/ufshcd/*/attributes/active_icc_level	777	What: /sys/bus/platform/drivers/ufshcd/*/attributes/active_icc_level
@@ -701,6 +780,7 @@ Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> · 2 unmodified lines
701	Description: This file provides the active icc level UFS device attribute.	780	Description: This file provides the active icc level UFS device attribute.
702	The full information about the attribute could be found at	781	The full information about the attribute could be found at
703	UFS specifications 2.1.	782	UFS specifications 2.1.
		783
704	The file is read only.	784	The file is read only.
705		785
706	What: /sys/bus/platform/drivers/ufshcd/*/attributes/ooo_data_enabled	786	What: /sys/bus/platform/drivers/ufshcd/*/attributes/ooo_data_enabled
@@ -709,6 +789,7 @@ Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> · 2 unmodified lines
709	Description: This file provides the out of order data transfer enabled UFS	789	Description: This file provides the out of order data transfer enabled UFS
710	device attribute. The full information about the attribute	790	device attribute. The full information about the attribute
711	could be found at UFS specifications 2.1.	791	could be found at UFS specifications 2.1.
		792
712	The file is read only.	793	The file is read only.
713		794
714	What: /sys/bus/platform/drivers/ufshcd/*/attributes/bkops_status	795	What: /sys/bus/platform/drivers/ufshcd/*/attributes/bkops_status
@@ -717,6 +798,7 @@ Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> · 2 unmodified lines
717	Description: This file provides the background operations status UFS device	798	Description: This file provides the background operations status UFS device
718	attribute. The full information about the attribute could	799	attribute. The full information about the attribute could
719	be found at UFS specifications 2.1.	800	be found at UFS specifications 2.1.
		801
720	The file is read only.	802	The file is read only.
721		803
722	What: /sys/bus/platform/drivers/ufshcd/*/attributes/purge_status	804	What: /sys/bus/platform/drivers/ufshcd/*/attributes/purge_status
@@ -725,6 +807,7 @@ Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> · 2 unmodified lines
725	Description: This file provides the purge operation status UFS device	807	Description: This file provides the purge operation status UFS device
726	attribute. The full information about the attribute could	808	attribute. The full information about the attribute could
727	be found at UFS specifications 2.1.	809	be found at UFS specifications 2.1.
		810
728	The file is read only.	811	The file is read only.
729		812
730	What: /sys/bus/platform/drivers/ufshcd/*/attributes/max_data_in_size	813	What: /sys/bus/platform/drivers/ufshcd/*/attributes/max_data_in_size
@@ -733,6 +816,7 @@ Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> · 2 unmodified lines
733	Description: This file shows the maximum data size in a DATA IN	816	Description: This file shows the maximum data size in a DATA IN
734	UPIU. The full information about the attribute could	817	UPIU. The full information about the attribute could
735	be found at UFS specifications 2.1.	818	be found at UFS specifications 2.1.
		819
736	The file is read only.	820	The file is read only.
737		821
738	What: /sys/bus/platform/drivers/ufshcd/*/attributes/max_data_out_size	822	What: /sys/bus/platform/drivers/ufshcd/*/attributes/max_data_out_size
@@ -741,6 +825,7 @@ Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> · 2 unmodified lines
741	Description: This file shows the maximum number of bytes that can be	825	Description: This file shows the maximum number of bytes that can be
742	requested with a READY TO TRANSFER UPIU. The full information	826	requested with a READY TO TRANSFER UPIU. The full information
743	about the attribute could be found at UFS specifications 2.1.	827	about the attribute could be found at UFS specifications 2.1.
		828
744	The file is read only.	829	The file is read only.
745		830
746	What: /sys/bus/platform/drivers/ufshcd/*/attributes/reference_clock_frequency	831	What: /sys/bus/platform/drivers/ufshcd/*/attributes/reference_clock_frequency
@@ -749,6 +834,7 @@ Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> · 2 unmodified lines
749	Description: This file provides the reference clock frequency UFS device	834	Description: This file provides the reference clock frequency UFS device
750	attribute. The full information about the attribute could	835	attribute. The full information about the attribute could
751	be found at UFS specifications 2.1.	836	be found at UFS specifications 2.1.
		837
752	The file is read only.	838	The file is read only.
753		839
754	What: /sys/bus/platform/drivers/ufshcd/*/attributes/configuration_descriptor_lock	840	What: /sys/bus/platform/drivers/ufshcd/*/attributes/configuration_descriptor_lock
@@ -765,6 +851,7 @@ Description: This file provides the maximum current number of · 10 unmodified lines
765	outstanding RTTs in device that is allowed. The full	851	outstanding RTTs in device that is allowed. The full
766	information about the attribute could be found at	852	information about the attribute could be found at
767	UFS specifications 2.1.	853	UFS specifications 2.1.
		854
768	The file is read only.	855	The file is read only.
769		856
770	What: /sys/bus/platform/drivers/ufshcd/*/attributes/exception_event_control	857	What: /sys/bus/platform/drivers/ufshcd/*/attributes/exception_event_control
@@ -773,6 +860,7 @@ Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> · 2 unmodified lines
773	Description: This file provides the exception event control UFS device	860	Description: This file provides the exception event control UFS device
774	attribute. The full information about the attribute could	861	attribute. The full information about the attribute could
775	be found at UFS specifications 2.1.	862	be found at UFS specifications 2.1.
		863
776	The file is read only.	864	The file is read only.
777		865
778	What: /sys/bus/platform/drivers/ufshcd/*/attributes/exception_event_status	866	What: /sys/bus/platform/drivers/ufshcd/*/attributes/exception_event_status
@@ -781,6 +869,7 @@ Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> · 2 unmodified lines
781	Description: This file provides the exception event status UFS device	869	Description: This file provides the exception event status UFS device
782	attribute. The full information about the attribute could	870	attribute. The full information about the attribute could
783	be found at UFS specifications 2.1.	871	be found at UFS specifications 2.1.
		872
784	The file is read only.	873	The file is read only.
785		874
786	What: /sys/bus/platform/drivers/ufshcd/*/attributes/ffu_status	875	What: /sys/bus/platform/drivers/ufshcd/*/attributes/ffu_status
@@ -789,6 +878,7 @@ Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> · 2 unmodified lines
789	Description: This file provides the ffu status UFS device attribute.	878	Description: This file provides the ffu status UFS device attribute.
790	The full information about the attribute could be found at	879	The full information about the attribute could be found at
791	UFS specifications 2.1.	880	UFS specifications 2.1.
		881
792	The file is read only.	882	The file is read only.
793		883
794	What: /sys/bus/platform/drivers/ufshcd/*/attributes/psa_state	884	What: /sys/bus/platform/drivers/ufshcd/*/attributes/psa_state
@@ -796,6 +886,7 @@ Date: February 2018 · 1 unmodified line
796	Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>	886	Contact: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>
797	Description: This file show the PSA feature status. The full information	887	Description: This file show the PSA feature status. The full information
798	about the attribute could be found at UFS specifications 2.1.	888	about the attribute could be found at UFS specifications 2.1.
		889
799	The file is read only.	890	The file is read only.
800		891
801	What: /sys/bus/platform/drivers/ufshcd/*/attributes/psa_data_size	892	What: /sys/bus/platform/drivers/ufshcd/*/attributes/psa_data_size
@@ -805,6 +896,7 @@ Description: This file shows the amount of data that the host plans to · 3 unmodified lines
805	load to all logical units in pre-soldering state.	896	load to all logical units in pre-soldering state.
806	The full information about the attribute could be found at	897	The full information about the attribute could be found at
807	UFS specifications 2.1.	898	UFS specifications 2.1.
		899
808	The file is read only.	900	The file is read only.
809		901
810		902
@@ -815,6 +907,7 @@ Description: This file shows the The amount of physical memory needed · 4 unmodified lines
815	to be removed from the physical memory resources pool of	907	to be removed from the physical memory resources pool of
816	the particular logical unit. The full information about	908	the particular logical unit. The full information about
817	the attribute could be found at UFS specifications 2.1.	909	the attribute could be found at UFS specifications 2.1.
		910
818	The file is read only.	911	The file is read only.
819		912
820		913
@@ -824,24 +917,28 @@ Contact: Subhash Jadavani <subhashj@codeaurora.org> · 3 unmodified lines
824	Description: This entry could be used to set or show the UFS device	917	Description: This entry could be used to set or show the UFS device
825	runtime power management level. The current driver	918	runtime power management level. The current driver
826	implementation supports 6 levels with next target states:	919	implementation supports 6 levels with next target states:
827	0 - an UFS device will stay active, an UIC link will	920
828	stay active	921	== ====================================================
829	1 - an UFS device will stay active, an UIC link will	922	0 an UFS device will stay active, an UIC link will
830	hibernate	923	stay active
831	2 - an UFS device will moved to sleep, an UIC link will	924	1 an UFS device will stay active, an UIC link will
832	stay active	925	hibernate
833	3 - an UFS device will moved to sleep, an UIC link will	926	2 an UFS device will moved to sleep, an UIC link will
834	hibernate	927	stay active
835	4 - an UFS device will be powered off, an UIC link will	928	3 an UFS device will moved to sleep, an UIC link will
836	hibernate	929	hibernate
837	5 - an UFS device will be powered off, an UIC link will	930	4 an UFS device will be powered off, an UIC link will
838	be powered off	931	hibernate
		932	5 an UFS device will be powered off, an UIC link will
		933	be powered off
		934	== ====================================================
839		935
840	What: /sys/bus/platform/drivers/ufshcd/*/rpm_target_dev_state	936	What: /sys/bus/platform/drivers/ufshcd/*/rpm_target_dev_state
841	Date: February 2018	937	Date: February 2018
842	Contact: Subhash Jadavani <subhashj@codeaurora.org>	938	Contact: Subhash Jadavani <subhashj@codeaurora.org>
843	Description: This entry shows the target power mode of an UFS device	939	Description: This entry shows the target power mode of an UFS device
844	for the chosen runtime power management level.	940	for the chosen runtime power management level.
		941
845	The file is read only.	942	The file is read only.
846		943
847	What: /sys/bus/platform/drivers/ufshcd/*/rpm_target_link_state	944	What: /sys/bus/platform/drivers/ufshcd/*/rpm_target_link_state
@@ -849,6 +946,7 @@ Date: February 2018 · 1 unmodified line
849	Contact: Subhash Jadavani <subhashj@codeaurora.org>	946	Contact: Subhash Jadavani <subhashj@codeaurora.org>
850	Description: This entry shows the target state of an UFS UIC link	947	Description: This entry shows the target state of an UFS UIC link
851	for the chosen runtime power management level.	948	for the chosen runtime power management level.
		949
852	The file is read only.	950	The file is read only.
853		951
854	What: /sys/bus/platform/drivers/ufshcd/*/spm_lvl	952	What: /sys/bus/platform/drivers/ufshcd/*/spm_lvl
@@ -857,24 +955,28 @@ Contact: Subhash Jadavani <subhashj@codeaurora.org> · 2 unmodified lines
857	Description: This entry could be used to set or show the UFS device	955	Description: This entry could be used to set or show the UFS device
858	system power management level. The current driver	956	system power management level. The current driver
859	implementation supports 6 levels with next target states:	957	implementation supports 6 levels with next target states:
860	0 - an UFS device will stay active, an UIC link will	958
861	stay active	959	== ====================================================
862	1 - an UFS device will stay active, an UIC link will	960	0 an UFS device will stay active, an UIC link will
863	hibernate	961	stay active
864	2 - an UFS device will moved to sleep, an UIC link will	962	1 an UFS device will stay active, an UIC link will
865	stay active	963	hibernate
866	3 - an UFS device will moved to sleep, an UIC link will	964	2 an UFS device will moved to sleep, an UIC link will
867	hibernate	965	stay active
868	4 - an UFS device will be powered off, an UIC link will	966	3 an UFS device will moved to sleep, an UIC link will
869	hibernate	967	hibernate
870	5 - an UFS device will be powered off, an UIC link will	968	4 an UFS device will be powered off, an UIC link will
871	be powered off	969	hibernate
		970	5 an UFS device will be powered off, an UIC link will
		971	be powered off
		972	== ====================================================
872		973
873	What: /sys/bus/platform/drivers/ufshcd/*/spm_target_dev_state	974	What: /sys/bus/platform/drivers/ufshcd/*/spm_target_dev_state
874	Date: February 2018	975	Date: February 2018
875	Contact: Subhash Jadavani <subhashj@codeaurora.org>	976	Contact: Subhash Jadavani <subhashj@codeaurora.org>
876	Description: This entry shows the target power mode of an UFS device	977	Description: This entry shows the target power mode of an UFS device
877	for the chosen system power management level.	978	for the chosen system power management level.
		979
878	The file is read only.	980	The file is read only.
879		981
880	What: /sys/bus/platform/drivers/ufshcd/*/spm_target_link_state	982	What: /sys/bus/platform/drivers/ufshcd/*/spm_target_link_state
@@ -882,18 +984,21 @@ Date: February 2018 · 1 unmodified line
882	Contact: Subhash Jadavani <subhashj@codeaurora.org>	984	Contact: Subhash Jadavani <subhashj@codeaurora.org>
883	Description: This entry shows the target state of an UFS UIC link	985	Description: This entry shows the target state of an UFS UIC link
884	for the chosen system power management level.	986	for the chosen system power management level.
		987
885	The file is read only.	988	The file is read only.
886		989
887	What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/wb_presv_us_en	990	What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/wb_presv_us_en
888	Date: June 2020	991	Date: June 2020
889	Contact: Asutosh Das <asutoshd@codeaurora.org>	992	Contact: Asutosh Das <asutoshd@codeaurora.org>
890	Description: This entry shows if preserve user-space was configured	993	Description: This entry shows if preserve user-space was configured
		994
891	The file is read only.	995	The file is read only.
892		996
893	What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/wb_shared_alloc_units	997	What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/wb_shared_alloc_units
894	Date: June 2020	998	Date: June 2020
895	Contact: Asutosh Das <asutoshd@codeaurora.org>	999	Contact: Asutosh Das <asutoshd@codeaurora.org>
896	Description: This entry shows the shared allocated units of WB buffer	1000	Description: This entry shows the shared allocated units of WB buffer
		1001
897	The file is read only.	1002	The file is read only.
898		1003
899	What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/wb_type	1004	What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/wb_type
@@ -901,6 +1006,7 @@ Date: June 2020 · 1 unmodified line
901	Contact: Asutosh Das <asutoshd@codeaurora.org>	1006	Contact: Asutosh Das <asutoshd@codeaurora.org>
902	Description: This entry shows the configured WB type.	1007	Description: This entry shows the configured WB type.
903	0x1 for shared buffer mode. 0x0 for dedicated buffer mode.	1008	0x1 for shared buffer mode. 0x0 for dedicated buffer mode.
		1009
904	The file is read only.	1010	The file is read only.
905		1011
906	What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/wb_buff_cap_adj	1012	What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/wb_buff_cap_adj
@@ -910,6 +1016,7 @@ Description: This entry shows the total user-space decrease in shared · 3 unmodified lines
910	buffer mode.	1016	buffer mode.
911	The value of this parameter is 3 for TLC NAND when SLC mode	1017	The value of this parameter is 3 for TLC NAND when SLC mode
912	is used as WriteBooster Buffer. 2 for MLC NAND.	1018	is used as WriteBooster Buffer. 2 for MLC NAND.
		1019
913	The file is read only.	1020	The file is read only.
914		1021
915	What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/wb_max_alloc_units	1022	What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/wb_max_alloc_units
@@ -917,6 +1024,7 @@ Date: June 2020 · 1 unmodified line
917	Contact: Asutosh Das <asutoshd@codeaurora.org>	1024	Contact: Asutosh Das <asutoshd@codeaurora.org>
918	Description: This entry shows the Maximum total WriteBooster Buffer size	1025	Description: This entry shows the Maximum total WriteBooster Buffer size
919	which is supported by the entire device.	1026	which is supported by the entire device.
		1027
920	The file is read only.	1028	The file is read only.
921		1029
922	What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/wb_max_wb_luns	1030	What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/wb_max_wb_luns
@@ -924,6 +1032,7 @@ Date: June 2020 · 1 unmodified line
924	Contact: Asutosh Das <asutoshd@codeaurora.org>	1032	Contact: Asutosh Das <asutoshd@codeaurora.org>
925	Description: This entry shows the maximum number of luns that can support	1033	Description: This entry shows the maximum number of luns that can support
926	WriteBooster.	1034	WriteBooster.
		1035
927	The file is read only.	1036	The file is read only.
928		1037
929	What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/wb_sup_red_type	1038	What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/wb_sup_red_type
@@ -937,46 +1046,59 @@ Description: The supportability of user space reduction mode · 7 unmodified lines
937	preserve user space type.	1046	preserve user space type.
938	02h: Device can be configured in either user space	1047	02h: Device can be configured in either user space
939	reduction type or preserve user space type.	1048	reduction type or preserve user space type.
		1049
940	The file is read only.	1050	The file is read only.
941		1051
942	What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/wb_sup_wb_type	1052	What: /sys/bus/platform/drivers/ufshcd/*/geometry_descriptor/wb_sup_wb_type
943	Date: June 2020	1053	Date: June 2020
944	Contact: Asutosh Das <asutoshd@codeaurora.org>	1054	Contact: Asutosh Das <asutoshd@codeaurora.org>
945	Description: The supportability of WriteBooster Buffer type.	1055	Description: The supportability of WriteBooster Buffer type.
946	00h: LU based WriteBooster Buffer configuration	1056
947	01h: Single shared WriteBooster Buffer	1057	=== ==========================================================
948	configuration	1058	00h LU based WriteBooster Buffer configuration
949	02h: Supporting both LU based WriteBooster	1059	01h Single shared WriteBooster Buffer configuration
950	Buffer and Single shared WriteBooster Buffer	1060	02h Supporting both LU based WriteBooster.
951	configuration	1061	Buffer and Single shared WriteBooster Buffer configuration
		1062	=== ==========================================================
		1063
952	The file is read only.	1064	The file is read only.
953		1065
954	What: /sys/bus/platform/drivers/ufshcd/*/flags/wb_enable	1066	What: /sys/bus/platform/drivers/ufshcd/*/flags/wb_enable
955	Date: June 2020	1067	Date: June 2020
956	Contact: Asutosh Das <asutoshd@codeaurora.org>	1068	Contact: Asutosh Das <asutoshd@codeaurora.org>
957	Description: This entry shows the status of WriteBooster.	1069	Description: This entry shows the status of WriteBooster.
958	0: WriteBooster is not enabled.	1070
959	1: WriteBooster is enabled	1071	== ============================
		1072	0 WriteBooster is not enabled.
		1073	1 WriteBooster is enabled
		1074	== ============================
		1075
960	The file is read only.	1076	The file is read only.
961		1077
962	What: /sys/bus/platform/drivers/ufshcd/*/flags/wb_flush_en	1078	What: /sys/bus/platform/drivers/ufshcd/*/flags/wb_flush_en
963	Date: June 2020	1079	Date: June 2020
964	Contact: Asutosh Das <asutoshd@codeaurora.org>	1080	Contact: Asutosh Das <asutoshd@codeaurora.org>
965	Description: This entry shows if flush is enabled.	1081	Description: This entry shows if flush is enabled.
966	0: Flush operation is not performed.	1082
967	1: Flush operation is performed.	1083	== =================================
		1084	0 Flush operation is not performed.
		1085	1 Flush operation is performed.
		1086	== =================================
		1087
968	The file is read only.	1088	The file is read only.
969		1089
970	What: /sys/bus/platform/drivers/ufshcd/*/flags/wb_flush_during_h8	1090	What: /sys/bus/platform/drivers/ufshcd/*/flags/wb_flush_during_h8
971	Date: June 2020	1091	Date: June 2020
972	Contact: Asutosh Das <asutoshd@codeaurora.org>	1092	Contact: Asutosh Das <asutoshd@codeaurora.org>
973	Description: Flush WriteBooster Buffer during hibernate state.	1093	Description: Flush WriteBooster Buffer during hibernate state.
974	0: Device is not allowed to flush the	1094
975	WriteBooster Buffer during link hibernate	1095	== =================================================
976	state.	1096	0 Device is not allowed to flush the
977	1: Device is allowed to flush the	1097	WriteBooster Buffer during link hibernate state.
978	WriteBooster Buffer during link hibernate	1098	1 Device is allowed to flush the
979	state	1099	WriteBooster Buffer during link hibernate state.
		1100	== =================================================
		1101
980	The file is read only.	1102	The file is read only.
981		1103
982	What: /sys/bus/platform/drivers/ufshcd/*/attributes/wb_avail_buf	1104	What: /sys/bus/platform/drivers/ufshcd/*/attributes/wb_avail_buf
@@ -984,23 +1106,30 @@ Date: June 2020 · 1 unmodified line
984	Contact: Asutosh Das <asutoshd@codeaurora.org>	1106	Contact: Asutosh Das <asutoshd@codeaurora.org>
985	Description: This entry shows the amount of unused WriteBooster buffer	1107	Description: This entry shows the amount of unused WriteBooster buffer
986	available.	1108	available.
		1109
987	The file is read only.	1110	The file is read only.
988		1111
989	What: /sys/bus/platform/drivers/ufshcd/*/attributes/wb_cur_buf	1112	What: /sys/bus/platform/drivers/ufshcd/*/attributes/wb_cur_buf
990	Date: June 2020	1113	Date: June 2020
991	Contact: Asutosh Das <asutoshd@codeaurora.org>	1114	Contact: Asutosh Das <asutoshd@codeaurora.org>
992	Description: This entry shows the amount of unused current buffer.	1115	Description: This entry shows the amount of unused current buffer.
		1116
993	The file is read only.	1117	The file is read only.
994		1118
995	What: /sys/bus/platform/drivers/ufshcd/*/attributes/wb_flush_status	1119	What: /sys/bus/platform/drivers/ufshcd/*/attributes/wb_flush_status
996	Date: June 2020	1120	Date: June 2020
997	Contact: Asutosh Das <asutoshd@codeaurora.org>	1121	Contact: Asutosh Das <asutoshd@codeaurora.org>
998	Description: This entry shows the flush operation status.	1122	Description: This entry shows the flush operation status.
999	00h: idle	1123
1000	01h: Flush operation in progress	1124
1001	02h: Flush operation stopped prematurely.	1125	=== ======================================
1002	03h: Flush operation completed successfully	1126	00h idle
1003	04h: Flush operation general failure	1127	01h Flush operation in progress
		1128	02h Flush operation stopped prematurely.
		1129	03h Flush operation completed successfully
		1130	04h Flush operation general failure
		1131	=== ======================================
		1132
1004	The file is read only.	1133	The file is read only.
1005		1134
1006	What: /sys/bus/platform/drivers/ufshcd/*/attributes/wb_life_time_est	1135	What: /sys/bus/platform/drivers/ufshcd/*/attributes/wb_life_time_est
@@ -1008,9 +1137,13 @@ Date: June 2020 · 1 unmodified line
1008	Contact: Asutosh Das <asutoshd@codeaurora.org>	1137	Contact: Asutosh Das <asutoshd@codeaurora.org>
1009	Description: This entry shows an indication of the WriteBooster Buffer	1138	Description: This entry shows an indication of the WriteBooster Buffer
1010	lifetime based on the amount of performed program/erase cycles	1139	lifetime based on the amount of performed program/erase cycles
1011	01h: 0% - 10% WriteBooster Buffer life time used	1140
		1141	=== =============================================
		1142	01h 0% - 10% WriteBooster Buffer life time used
1012	...	1143	...
1013	0Ah: 90% - 100% WriteBooster Buffer life time used	1144	0Ah 90% - 100% WriteBooster Buffer life time used
		1145	=== =============================================
		1146
1014	The file is read only.	1147	The file is read only.
1015		1148
1016	What: /sys/class/scsi_device/*/device/unit_descriptor/wb_buf_alloc_units	1149	What: /sys/class/scsi_device/*/device/unit_descriptor/wb_buf_alloc_units
@@ -1018,4 +1151,5 @@ Date: June 2020 · 1 unmodified line
1018	Contact: Asutosh Das <asutoshd@codeaurora.org>	1151	Contact: Asutosh Das <asutoshd@codeaurora.org>
1019	Description: This entry shows the configured size of WriteBooster buffer.	1152	Description: This entry shows the configured size of WriteBooster buffer.
1020	0400h corresponds to 4GB.	1153	0400h corresponds to 4GB.
		1154
1021	The file is read only.	1155	The file is read only.

Documentation/ABI/testing/sysfs-driver-w1_ds28e17+3−0

@@ -5,7 +5,9 @@ Contact: Jan Kandziora <jjj@gmx.de> · 4 unmodified lines
5	Description: When written, this file sets the I2C speed on the connected	5	Description: When written, this file sets the I2C speed on the connected
6	DS28E17 chip. When read, it reads the current setting from	6	DS28E17 chip. When read, it reads the current setting from
7	the DS28E17 chip.	7	the DS28E17 chip.
		8
8	Valid values: 100, 400, 900 [kBaud].	9	Valid values: 100, 400, 900 [kBaud].
		10
9	Default 100, can be set by w1_ds28e17.speed= module parameter.	11	Default 100, can be set by w1_ds28e17.speed= module parameter.
10	Users: w1_ds28e17 driver	12	Users: w1_ds28e17 driver
11		13
@@ -17,5 +19,6 @@ Description: When written, this file sets the multiplier used to calculate · 5 unmodified lines
17	the busy timeout for I2C operations on the connected DS28E17	19	the busy timeout for I2C operations on the connected DS28E17
18	chip. When read, returns the current setting.	20	chip. When read, returns the current setting.
19	Valid values: 1 to 9.	21	Valid values: 1 to 9.
		22
20	Default 1, can be set by w1_ds28e17.stretch= module parameter.	23	Default 1, can be set by w1_ds28e17.stretch= module parameter.
21	Users: w1_ds28e17 driver	24	Users: w1_ds28e17 driver

Documentation/ABI/testing/sysfs-driver-w1_therm+51−24

@@ -22,8 +22,10 @@ Description: · 21 unmodified lines
22	device data to its embedded EEPROM, either restore data	22	device data to its embedded EEPROM, either restore data
23	embedded in device EEPROM. Be aware that devices support	23	embedded in device EEPROM. Be aware that devices support
24	limited EEPROM writing cycles (typical 50k)	24	limited EEPROM writing cycles (typical 50k)
		25
25	* 'save': save device RAM to EEPROM	26	* 'save': save device RAM to EEPROM
26	* 'restore': restore EEPROM data in device RAM	27	* 'restore': restore EEPROM data in device RAM
		28
27	Users: any user space application which wants to communicate with	29	Users: any user space application which wants to communicate with
28	w1_term device	30	w1_term device
29		31
@@ -33,9 +35,11 @@ Date: May 2020 · 3 unmodified lines
33	Contact: Akira Shimahara <akira215corp@gmail.com>	35	Contact: Akira Shimahara <akira215corp@gmail.com>
34	Description:	36	Description:
35	(RO) return the power status by asking the device	37	(RO) return the power status by asking the device
		38
36	* '0': device parasite powered	39	* '0': device parasite powered
37	* '1': device externally powered	40	* '1': device externally powered
38	* '-xx': xx is kernel error when reading power status	41	* '-xx': xx is kernel error when reading power status
		42
39	Users: any user space application which wants to communicate with	43	Users: any user space application which wants to communicate with
40	w1_term device	44	w1_term device
41		45
@@ -49,10 +53,12 @@ Description: · 7 unmodified lines
49	will be changed only in device RAM, so it will be cleared when	53	will be changed only in device RAM, so it will be cleared when
50	power is lost. Trigger a 'save' to EEPROM command to keep	54	power is lost. Trigger a 'save' to EEPROM command to keep
51	values after power-on. Read or write are :	55	values after power-on. Read or write are :
		56
52	* '9..14': device resolution in bit	57	* '9..14': device resolution in bit
53	or resolution to set in bit	58	or resolution to set in bit
54	* '-xx': xx is kernel error when reading the resolution	59	* '-xx': xx is kernel error when reading the resolution
55	* Anything else: do nothing	60	* Anything else: do nothing
		61
56	Some DS18B20 clones are fixed in 12-bit resolution, so the	62	Some DS18B20 clones are fixed in 12-bit resolution, so the
57	actual resolution is read back from the chip and verified. Error	63	actual resolution is read back from the chip and verified. Error
58	is reported if the results differ.	64	is reported if the results differ.
@@ -65,16 +71,18 @@ Date: May 2020 · 6 unmodified lines
65	Contact: Akira Shimahara <akira215corp@gmail.com>	71	Contact: Akira Shimahara <akira215corp@gmail.com>
66	Description:	72	Description:
67	(RO) return the temperature in 1/1000 degC.	73	(RO) return the temperature in 1/1000 degC.
		74
68	* If a bulk read has been triggered, it will directly	75	* If a bulk read has been triggered, it will directly
69	return the temperature computed when the bulk read	76	return the temperature computed when the bulk read
70	occurred, if available. If not yet available, nothing	77	occurred, if available. If not yet available, nothing
71	is returned (a debug kernel message is sent), you	78	is returned (a debug kernel message is sent), you
72	should retry later on.	79	should retry later on.
73	* If no bulk read has been triggered, it will trigger	80	* If no bulk read has been triggered, it will trigger
74	a conversion and send the result. Note that the	81	a conversion and send the result. Note that the
75	conversion duration depend on the resolution (if	82	conversion duration depend on the resolution (if
76	device support this feature). It takes 94ms in 9bits	83	device support this feature). It takes 94ms in 9bits
77	resolution, 750ms for 12bits.	84	resolution, 750ms for 12bits.
		85
78	Users: any user space application which wants to communicate with	86	Users: any user space application which wants to communicate with
79	w1_term device	87	w1_term device
80		88
@@ -86,12 +94,14 @@ Description: · 5 unmodified lines
86	(RW) return the temperature in 1/1000 degC.	94	(RW) return the temperature in 1/1000 degC.
87	read: return 2 lines with the hexa output data sent on the	95	read: return 2 lines with the hexa output data sent on the
88	bus, return the CRC check and temperature in 1/1000 degC	96	bus, return the CRC check and temperature in 1/1000 degC
89	write :	97	write:
		98
90	* '0' : save the 2 or 3 bytes to the device EEPROM	99	* '0' : save the 2 or 3 bytes to the device EEPROM
91	(i.e. TH, TL and config register)	100	(i.e. TH, TL and config register)
92	* '9..14' : set the device resolution in RAM	101	* '9..14' : set the device resolution in RAM
93	(if supported)	102	(if supported)
94	* Anything else: do nothing	103	* Anything else: do nothing
		104
95	refer to Documentation/w1/slaves/w1_therm.rst for detailed	105	refer to Documentation/w1/slaves/w1_therm.rst for detailed
96	information.	106	information.
97	Users: any user space application which wants to communicate with	107	Users: any user space application which wants to communicate with
@@ -103,14 +113,21 @@ Date: May 2020 · 5 unmodified lines
103	Contact: Akira Shimahara <akira215corp@gmail.com>	113	Contact: Akira Shimahara <akira215corp@gmail.com>
104	Description:	114	Description:
105	(RW) trigger a bulk read conversion. read the status	115	(RW) trigger a bulk read conversion. read the status
		116
106	read:	117	read:
107	* '-1': conversion in progress on at least 1 sensor	118	* '-1':
108	* '1' : conversion complete but at least one sensor	119	conversion in progress on at least 1 sensor
		120	* '1' :
		121	conversion complete but at least one sensor
109	value has not been read yet	122	value has not been read yet
110	* '0' : no bulk operation. Reading temperature will	123	* '0' :
		124	no bulk operation. Reading temperature will
111	trigger a conversion on each device	125	trigger a conversion on each device
112	write: 'trigger': trigger a bulk read on all supporting	126
		127	write:
		128	'trigger': trigger a bulk read on all supporting
113	devices on the bus	129	devices on the bus
		130
114	Note that if a bulk read is sent but one sensor is not read	131	Note that if a bulk read is sent but one sensor is not read
115	immediately, the next access to temperature on this device	132	immediately, the next access to temperature on this device
116	will return the temperature measured at the time of issue	133	will return the temperature measured at the time of issue
@@ -128,14 +145,19 @@ Description: · 11 unmodified lines
128	reset to default (datasheet) conversion time for a new	145	reset to default (datasheet) conversion time for a new
129	resolution.	146	resolution.
130		147
131	read: Actual conversion time in milliseconds. write:	148	read:
132	'0': Set the default conversion time from the datasheet.	149	Actual conversion time in milliseconds.
133	'1': Measure and set the conversion time. Make a single	150
		151	write:
		152	* '0':
		153	Set the default conversion time from the datasheet.
		154	* '1':
		155	Measure and set the conversion time. Make a single
134	temperature conversion, measure an actual value.	156	temperature conversion, measure an actual value.
135	Increase it by 20% for temperature range. A new	157	Increase it by 20% for temperature range. A new
136	conversion time can be obtained by reading this	158	conversion time can be obtained by reading this
137	same attribute.	159	same attribute.
138	other positive value:	160	* other positive value:
139	Set the conversion time in milliseconds.	161	Set the conversion time in milliseconds.
140		162
141	Users: An application using the w1_term device	163	Users: An application using the w1_term device
@@ -148,16 +170,21 @@ Description: · 6 unmodified lines
148	(RW) Control optional driver settings.	170	(RW) Control optional driver settings.
149	Bit masks to read/write (bitwise OR):	171	Bit masks to read/write (bitwise OR):
150		172
151	1: Enable check for conversion success. If byte 6 of	173	== ============================================================
		174	1 Enable check for conversion success. If byte 6 of
152	scratchpad memory is 0xC after conversion, and	175	scratchpad memory is 0xC after conversion, and
153	temperature reads 85.00 (powerup value) or 127.94	176	temperature reads 85.00 (powerup value) or 127.94
154	(insufficient power) - return a conversion error.	177	(insufficient power) - return a conversion error.
155		178
156	2: Enable poll for conversion completion. Generate read cycles	179	2 Enable poll for conversion completion. Generate read cycles
157	after the conversion start and wait for 1's. In parasite	180	after the conversion start and wait for 1's. In parasite
158	power mode this feature is not available.	181	power mode this feature is not available.
		182	== ============================================================
		183
		184	read:
		185	Currently selected features.
159		186
160	read: Currently selected features.	187	write:
161	write: Select features.	188	Select features.
162		189
163	Users: An application using the w1_term device	190	Users: An application using the w1_term device

Documentation/ABI/testing/sysfs-driver-wacom+3−1

@@ -79,7 +79,9 @@ Description: · 78 unmodified lines
79	When the Wacom Intuos 4 is connected over Bluetooth, the	79	When the Wacom Intuos 4 is connected over Bluetooth, the
80	image has to contain 256 bytes (64x32 px 1 bit colour).	80	image has to contain 256 bytes (64x32 px 1 bit colour).
81	The format is also scrambled, like in the USB mode, and it can	81	The format is also scrambled, like in the USB mode, and it can
82	be summarized by converting 76543210 into GECA6420.	82	be summarized by converting::
		83
		84	76543210 into GECA6420.
83	HGFEDCBA HFDB7531	85	HGFEDCBA HFDB7531
84		86
85	What: /sys/bus/hid/devices/<bus>:<vid>:<pid>.<n>/wacom_remote/unpair_remote	87	What: /sys/bus/hid/devices/<bus>:<vid>:<pid>.<n>/wacom_remote/unpair_remote

Documentation/ABI/testing/sysfs-firmware-acpi+124−113

@@ -12,11 +12,14 @@ Description: · 11 unmodified lines
12	image: The image bitmap. Currently a 32-bit BMP.	12	image: The image bitmap. Currently a 32-bit BMP.
13	status: 1 if the image is valid, 0 if firmware invalidated it.	13	status: 1 if the image is valid, 0 if firmware invalidated it.
14	type: 0 indicates image is in BMP format.	14	type: 0 indicates image is in BMP format.
		15
		16	======== ===================================================
15	version: The version of the BGRT. Currently 1.	17	version: The version of the BGRT. Currently 1.
16	xoffset: The number of pixels between the left of the screen	18	xoffset: The number of pixels between the left of the screen
17	and the left edge of the image.	19	and the left edge of the image.
18	yoffset: The number of pixels between the top of the screen	20	yoffset: The number of pixels between the top of the screen
19	and the top edge of the image.	21	and the top edge of the image.
		22	======== ===================================================
20		23
21	What: /sys/firmware/acpi/hotplug/	24	What: /sys/firmware/acpi/hotplug/
22	Date: February 2013	25	Date: February 2013
@@ -33,12 +36,14 @@ Description: · 10 unmodified lines
33	The following setting is available to user space for each	36	The following setting is available to user space for each
34	hotplug profile:	37	hotplug profile:
35		38
		39	======== =======================================================
36	enabled: If set, the ACPI core will handle notifications of	40	enabled: If set, the ACPI core will handle notifications of
37	hotplug events associated with the given class of	41	hotplug events associated with the given class of
38	devices and will allow those devices to be ejected with	42	devices and will allow those devices to be ejected with
39	the help of the _EJ0 control method. Unsetting it	43	the help of the _EJ0 control method. Unsetting it
40	effectively disables hotplug for the correspoinding	44	effectively disables hotplug for the correspoinding
41	class of devices.	45	class of devices.
		46	======== =======================================================
42		47
43	The value of the above attribute is an integer number: 1 (set)	48	The value of the above attribute is an integer number: 1 (set)
44	or 0 (unset). Attempts to write any other values to it will	49	or 0 (unset). Attempts to write any other values to it will
@@ -71,86 +76,90 @@ Description: · 26 unmodified lines
71	To figure out where all the SCI's are coming from,	76	To figure out where all the SCI's are coming from,
72	/sys/firmware/acpi/interrupts contains a file listing	77	/sys/firmware/acpi/interrupts contains a file listing
73	every possible source, and the count of how many	78	every possible source, and the count of how many
74	times it has triggered.	79	times it has triggered::
75		80
76	$ cd /sys/firmware/acpi/interrupts	81	$ cd /sys/firmware/acpi/interrupts
77	$ grep . *	82	$ grep . *
78	error: 0	83	error: 0
79	ff_gbl_lock: 0 enable	84	ff_gbl_lock: 0 enable
80	ff_pmtimer: 0 invalid	85	ff_pmtimer: 0 invalid
81	ff_pwr_btn: 0 enable	86	ff_pwr_btn: 0 enable
82	ff_rt_clk: 2 disable	87	ff_rt_clk: 2 disable
83	ff_slp_btn: 0 invalid	88	ff_slp_btn: 0 invalid
84	gpe00: 0 invalid	89	gpe00: 0 invalid
85	gpe01: 0 enable	90	gpe01: 0 enable
86	gpe02: 108 enable	91	gpe02: 108 enable
87	gpe03: 0 invalid	92	gpe03: 0 invalid
88	gpe04: 0 invalid	93	gpe04: 0 invalid
89	gpe05: 0 invalid	94	gpe05: 0 invalid
90	gpe06: 0 enable	95	gpe06: 0 enable
91	gpe07: 0 enable	96	gpe07: 0 enable
92	gpe08: 0 invalid	97	gpe08: 0 invalid
93	gpe09: 0 invalid	98	gpe09: 0 invalid
94	gpe0A: 0 invalid	99	gpe0A: 0 invalid
95	gpe0B: 0 invalid	100	gpe0B: 0 invalid
96	gpe0C: 0 invalid	101	gpe0C: 0 invalid
97	gpe0D: 0 invalid	102	gpe0D: 0 invalid
98	gpe0E: 0 invalid	103	gpe0E: 0 invalid
99	gpe0F: 0 invalid	104	gpe0F: 0 invalid
100	gpe10: 0 invalid	105	gpe10: 0 invalid
101	gpe11: 0 invalid	106	gpe11: 0 invalid
102	gpe12: 0 invalid	107	gpe12: 0 invalid
103	gpe13: 0 invalid	108	gpe13: 0 invalid
104	gpe14: 0 invalid	109	gpe14: 0 invalid
105	gpe15: 0 invalid	110	gpe15: 0 invalid
106	gpe16: 0 invalid	111	gpe16: 0 invalid
107	gpe17: 1084 enable	112	gpe17: 1084 enable
108	gpe18: 0 enable	113	gpe18: 0 enable
109	gpe19: 0 invalid	114	gpe19: 0 invalid
110	gpe1A: 0 invalid	115	gpe1A: 0 invalid
111	gpe1B: 0 invalid	116	gpe1B: 0 invalid
112	gpe1C: 0 invalid	117	gpe1C: 0 invalid
113	gpe1D: 0 invalid	118	gpe1D: 0 invalid
114	gpe1E: 0 invalid	119	gpe1E: 0 invalid
115	gpe1F: 0 invalid	120	gpe1F: 0 invalid
116	gpe_all: 1192	121	gpe_all: 1192
117	sci: 1194	122	sci: 1194
118	sci_not: 0	123	sci_not: 0
119		124
120	sci - The number of times the ACPI SCI	125	=========== ==================================================
121	has been called and claimed an interrupt.	126	sci The number of times the ACPI SCI
122		127	has been called and claimed an interrupt.
123	sci_not - The number of times the ACPI SCI	128
124	has been called and NOT claimed an interrupt.	129	sci_not The number of times the ACPI SCI
125		130	has been called and NOT claimed an interrupt.
126	gpe_all - count of SCI caused by GPEs.	131
127		132	gpe_all count of SCI caused by GPEs.
128	gpeXX - count for individual GPE source	133
129		134	gpeXX count for individual GPE source
130	ff_gbl_lock - Global Lock	135
131		136	ff_gbl_lock Global Lock
132	ff_pmtimer - PM Timer	137
133		138	ff_pmtimer PM Timer
134	ff_pwr_btn - Power Button	139
135		140	ff_pwr_btn Power Button
136	ff_rt_clk - Real Time Clock	141
137		142	ff_rt_clk Real Time Clock
138	ff_slp_btn - Sleep Button	143
139		144	ff_slp_btn Sleep Button
140	error - an interrupt that can't be accounted for above.	145
141		146	error an interrupt that can't be accounted for above.
142	invalid: it's either a GPE or a Fixed Event that	147
143	doesn't have an event handler.	148	invalid it's either a GPE or a Fixed Event that
144		149	doesn't have an event handler.
145	disable: the GPE/Fixed Event is valid but disabled.	150
146		151	disable the GPE/Fixed Event is valid but disabled.
147	enable: the GPE/Fixed Event is valid and enabled.	152
148		153	enable the GPE/Fixed Event is valid and enabled.
149	Root has permission to clear any of these counters. Eg.	154	=========== ==================================================
150	# echo 0 > gpe11	155
151		156	Root has permission to clear any of these counters. Eg.::
152	All counters can be cleared by clearing the total "sci":	157
153	# echo 0 > sci	158	# echo 0 > gpe11
		159
		160	All counters can be cleared by clearing the total "sci"::
		161
		162	# echo 0 > sci
154		163
155	None of these counters has an effect on the function	164	None of these counters has an effect on the function
156	of the system, they are simply statistics.	165	of the system, they are simply statistics.
@@ -165,32 +174,34 @@ Description: · 8 unmodified lines
165		174
166	Let's take power button fixed event for example, please kill acpid	175	Let's take power button fixed event for example, please kill acpid
167	and other user space applications so that the machine won't shutdown	176	and other user space applications so that the machine won't shutdown
168	when pressing the power button.	177	when pressing the power button::
169	# cat ff_pwr_btn	178
170	0 enabled	179	# cat ff_pwr_btn
171	# press the power button for 3 times;	180	0 enabled
172	# cat ff_pwr_btn	181	# press the power button for 3 times;
173	3 enabled	182	# cat ff_pwr_btn
174	# echo disable > ff_pwr_btn	183	3 enabled
175	# cat ff_pwr_btn	184	# echo disable > ff_pwr_btn
176	3 disabled	185	# cat ff_pwr_btn
177	# press the power button for 3 times;	186	3 disabled
178	# cat ff_pwr_btn	187	# press the power button for 3 times;
179	3 disabled	188	# cat ff_pwr_btn
180	# echo enable > ff_pwr_btn	189	3 disabled
181	# cat ff_pwr_btn	190	# echo enable > ff_pwr_btn
182	4 enabled	191	# cat ff_pwr_btn
183	/*	192	4 enabled
184	* this is because the status bit is set even if the enable bit is cleared,	193	/*
185	* and it triggers an ACPI fixed event when the enable bit is set again	194	* this is because the status bit is set even if the enable
186	*/	195	* bit is cleared, and it triggers an ACPI fixed event when
187	# press the power button for 3 times;	196	* the enable bit is set again
188	# cat ff_pwr_btn	197	*/
189	7 enabled	198	# press the power button for 3 times;
190	# echo disable > ff_pwr_btn	199	# cat ff_pwr_btn
191	# press the power button for 3 times;	200	7 enabled
192	# echo clear > ff_pwr_btn /* clear the status bit */	201	# echo disable > ff_pwr_btn
193	# echo disable > ff_pwr_btn	202	# press the power button for 3 times;
194	# cat ff_pwr_btn	203	# echo clear > ff_pwr_btn /* clear the status bit */
195	7 enabled	204	# echo disable > ff_pwr_btn
		205	# cat ff_pwr_btn
		206	7 enabled
196		207

Documentation/ABI/testing/sysfs-firmware-dmi-entries+27−23

 		doesn't matter), they will be represented in sysfs as
 		entries "T-0" through "T-(N-1)":
-		Example entry directories:
+		Example entry directories::
 			/sys/firmware/dmi/entries/17-0
 			/sys/firmware/dmi/entries/17-1
 		Each DMI entry in sysfs has the common header values
 		exported as attributes:
-		handle	: The 16bit 'handle' that is assigned to this
+		========  =================================================
+		handle	  The 16bit 'handle' that is assigned to this
 			  entry by the firmware.  This handle may be
 			  referred to by other entries.
-		length	: The length of the entry, as presented in the
+		length	  The length of the entry, as presented in the
 			  entry itself.  Note that this is _not the
 			  total count of bytes associated with the
-			  entry_.  This value represents the length of
+			  entry.  This value represents the length of
 			  the "formatted" portion of the entry.  This
 			  "formatted" region is sometimes followed by
 			  the "unformatted" region composed of nul
 			  terminated strings, with termination signalled
 			  by a two nul characters in series.
-		raw	: The raw bytes of the entry. This includes the
+		raw	  The raw bytes of the entry. This includes the
 			  "formatted" portion of the entry, the
 			  "unformatted" strings portion of the entry,
 			  and the two terminating nul characters.
-		type	: The type of the entry.  This value is the same
+		type	  The type of the entry.  This value is the same
 			  as found in the directory name.  It indicates
 			  how the rest of the entry should be interpreted.
-		instance: The instance ordinal of the entry for the
+		instance  The instance ordinal of the entry for the
 			  given type.  This value is the same as found
 			  in the parent directory name.
-		position: The ordinal position (zero-based) of the entry
+		position  The ordinal position (zero-based) of the entry
 			  within the entirety of the DMI entry table.
+		========  =================================================
-		=== Entry Specialization ===
+		**Entry Specialization**
 		Some entry types may have other information available in
 		sysfs.  Not all types are specialized.
-		--- Type 15 - System Event Log ---
+		**Type 15 - System Event Log**
 		This entry allows the firmware to export a log of
 		events the system has taken.  This information is
 		typically backed by nvram, but the implementation
 		details are abstracted by this table.  This entry's data
-		is exported in the directory:
+		is exported in the directory::
-		/sys/firmware/dmi/entries/15-0/system_event_log
+		  /sys/firmware/dmi/entries/15-0/system_event_log
 		and has the following attributes (documented in the
 		SMBIOS / DMI specification under "System Event Log (Type 15)":
-		area_length
+		- area_length
-		header_start_offset
+		- header_start_offset
-		data_start_offset
+		- data_start_offset
-		access_method
+		- access_method
-		status
+		- status
-		change_token
+		- change_token
-		access_method_address
+		- access_method_address
-		header_format
+		- header_format
-		per_log_type_descriptor_length
+		- per_log_type_descriptor_length
-		type_descriptors_supported_count
+		- type_descriptors_supported_count
 		As well, the kernel exports the binary attribute:
-		raw_event_log	: The raw binary bits of the event log
+		=============	  ====================================
+		raw_event_log	  The raw binary bits of the event log
 				  as described by the DMI entry.
+		=============	  ====================================

Documentation/ABI/testing/sysfs-firmware-efi-esrt+17−11

@@ -35,10 +35,13 @@ What: /sys/firmware/efi/esrt/entries/entry$N/fw_type · 34 unmodified lines
35	Date: February 2015	35	Date: February 2015
36	Contact: Peter Jones <pjones@redhat.com>	36	Contact: Peter Jones <pjones@redhat.com>
37	Description: What kind of firmware entry this is:	37	Description: What kind of firmware entry this is:
38	0 - Unknown	38
39	1 - System Firmware	39	== ===============
40	2 - Device Firmware	40	0 Unknown
41	3 - UEFI Driver	41	1 System Firmware
		42	2 Device Firmware
		43	3 UEFI Driver
		44	== ===============
42		45
43	What: /sys/firmware/efi/esrt/entries/entry$N/fw_class	46	What: /sys/firmware/efi/esrt/entries/entry$N/fw_class
44	Date: February 2015	47	Date: February 2015
@@ -71,11 +74,14 @@ Date: February 2015 · 26 unmodified lines
71	Contact: Peter Jones <pjones@redhat.com>	74	Contact: Peter Jones <pjones@redhat.com>
72	Description: The result of the last firmware update attempt for the	75	Description: The result of the last firmware update attempt for the
73	firmware resource entry.	76	firmware resource entry.
74	0 - Success	77
75	1 - Insufficient resources	78	== ======================
76	2 - Incorrect version	79	0 Success
77	3 - Invalid format	80	1 Insufficient resources
78	4 - Authentication error	81	2 Incorrect version
79	5 - AC power event	82	3 Invalid format
80	6 - Battery power event	83	4 Authentication error
		84	5 AC power event
		85	6 Battery power event
		86	== ======================
81		87

Documentation/ABI/testing/sysfs-firmware-efi-runtime-map+8−6

 		/sys/firmware/efi/runtime-map/ is the directory the kernel
 		exports that information in.
-		subdirectories are named with the number of the memory range:
+		subdirectories are named with the number of the memory range::
 			/sys/firmware/efi/runtime-map/0
 			/sys/firmware/efi/runtime-map/1
 		Each subdirectory contains five files:
-		attribute : The attributes of the memory range.
+		=========   =========================================
-		num_pages : The size of the memory range in pages.
+		attribute   The attributes of the memory range.
-		phys_addr : The physical address of the memory range.
+		num_pages   The size of the memory range in pages.
-		type      : The type of the memory range.
+		phys_addr   The physical address of the memory range.
-		virt_addr : The virtual address of the memory range.
+		type        The type of the memory range.
+		virt_addr   The virtual address of the memory range.
+		=========   =========================================
 		Above values are all hexadecimal numbers with the '0x' prefix.
 Users:		Kexec

Documentation/ABI/testing/sysfs-firmware-gsmi+1−1

@@ -20,7 +20,7 @@ Description: · 19 unmodified lines
20		20
21	This directory has the same layout (and	21	This directory has the same layout (and
22	underlying implementation as /sys/firmware/efi/vars.	22	underlying implementation as /sys/firmware/efi/vars.
23	See Documentation/ABI/*/sysfs-firmware-efi-vars	23	See `Documentation/ABI/*/sysfs-firmware-efi-vars`
24	for more information on how to interact with	24	for more information on how to interact with
25	this structure.	25	this structure.
26		26

Documentation/ABI/testing/sysfs-firmware-memmap+8−8

 		the raw memory map to userspace.
 		The structure is as follows: Under /sys/firmware/memmap there
-		are subdirectories with the number of the entry as their name:
+		are subdirectories with the number of the entry as their name::
 			/sys/firmware/memmap/0
 			/sys/firmware/memmap/1
 		Each directory contains three files:
-		start	: The start address (as hexadecimal number with the
+		========  =====================================================
+		start	  The start address (as hexadecimal number with the
 			  '0x' prefix).
-		end	: The end address, inclusive (regardless whether the
+		end	  The end address, inclusive (regardless whether the
 			  firmware provides inclusive or exclusive ranges).
-		type	: Type of the entry as string. See below for a list of
+		type	  Type of the entry as string. See below for a list of
 			  valid types.
+		========  =====================================================
-		So, for example:
+		So, for example::
 			/sys/firmware/memmap/0/start
 			/sys/firmware/memmap/0/end
 		  - reserved
 		Following shell snippet can be used to display that memory
-		map in a human-readable format:
+		map in a human-readable format::
-		-------------------- 8< ----------------------------------------
 		  #!/bin/bash
 		  cd /sys/firmware/memmap
 		  for dir in * ; do
 		      type=$(cat $dir/type)
 		      printf "%016x-%016x (%s)\n" $start $[ $end +1] "$type"
 		  done
-		-------------------- >8 ----------------------------------------

Documentation/ABI/testing/sysfs-firmware-qemu_fw_cfg+11−9

 		to the fw_cfg device can be found in "docs/specs/fw_cfg.txt"
 		in the QEMU source tree.
-		=== SysFS fw_cfg Interface ===
+		**SysFS fw_cfg Interface**
 		The fw_cfg sysfs interface described in this document is only
 		intended to display discoverable blobs (i.e., those registered
 			/sys/firmware/qemu_fw_cfg/rev
-		--- Discoverable fw_cfg blobs by selector key ---
+		**Discoverable fw_cfg blobs by selector key**
 		All discoverable blobs listed in the fw_cfg file directory are
 		displayed as entries named after their unique selector key
 		Each such fw_cfg sysfs entry has the following values exported
 		as attributes:
-		name  	: The 56-byte nul-terminated ASCII string used as the
+		====	  ====================================================
+		name	  The 56-byte nul-terminated ASCII string used as the
 			  blob's 'file name' in the fw_cfg directory.
-		size  	: The length of the blob, as given in the fw_cfg
+		size	  The length of the blob, as given in the fw_cfg
 			  directory.
-		key	: The value of the blob's selector key as given in the
+		key	  The value of the blob's selector key as given in the
 			  fw_cfg directory. This value is the same as used in
 			  the parent directory name.
-		raw	: The raw bytes of the blob, obtained by selecting the
+		raw	  The raw bytes of the blob, obtained by selecting the
 			  entry via the control register, and reading a number
 			  of bytes equal to the blob size from the data
 			  register.
+		====	  ====================================================
-		--- Listing fw_cfg blobs by file name ---
+		**Listing fw_cfg blobs by file name**
 		While the fw_cfg device does not impose any specific naming
 		convention on the blobs registered in the file directory,
 		QEMU developers have traditionally used path name semantics
-		to give each blob a descriptive name. For example:
+		to give each blob a descriptive name. For example::
 			"bootorder"
 			"genroms/kvmvapic.bin"
 		of directories matching the path name components of fw_cfg
 		blob names, ending in symlinks to the by_key entry for each
 		"basename", as illustrated below (assume current directory is
-		/sys/firmware):
+		/sys/firmware)::
 		    qemu_fw_cfg/by_name/bootorder -> ../by_key/38
 		    qemu_fw_cfg/by_name/etc/e820 -> ../../by_key/35

Documentation/ABI/testing/sysfs-firmware-sfi+3−3

@@ -9,7 +9,7 @@ Description: · 8 unmodified lines
9	http://simplefirmware.org/documentation	9	http://simplefirmware.org/documentation
10		10
11	While the tables are used by the kernel, user-space	11	While the tables are used by the kernel, user-space
12	can observe them this way:	12	can observe them this way::
13		13
14	# cd /sys/firmware/sfi/tables	14	# cd /sys/firmware/sfi/tables
15	# cat $TABLENAME > $TABLENAME.bin	15	# cat $TABLENAME > $TABLENAME.bin

Documentation/ABI/testing/sysfs-firmware-sgi_uv+3−3

Documentation/ABI/testing/sysfs-firmware-turris-mox-rwtm+5−5

@@ -2,21 +2,21 @@ What: /sys/firmware/turris-mox-rwtm/board_version · 1 unmodified line
2	Date: August 2019	2	Date: August 2019
3	KernelVersion: 5.4	3	KernelVersion: 5.4
4	Contact: Marek Behún <marek.behun@nic.cz>	4	Contact: Marek Behún <marek.behun@nic.cz>
5	Description: (R) Board version burned into eFuses of this Turris Mox board.	5	Description: (Read) Board version burned into eFuses of this Turris Mox board.
6	Format: %i	6	Format: %i
7		7
8	What: /sys/firmware/turris-mox-rwtm/mac_address*	8	What: /sys/firmware/turris-mox-rwtm/mac_address*
9	Date: August 2019	9	Date: August 2019
10	KernelVersion: 5.4	10	KernelVersion: 5.4
11	Contact: Marek Behún <marek.behun@nic.cz>	11	Contact: Marek Behún <marek.behun@nic.cz>
12	Description: (R) MAC addresses burned into eFuses of this Turris Mox board.	12	Description: (Read) MAC addresses burned into eFuses of this Turris Mox board.
13	Format: %pM	13	Format: %pM
14		14
15	What: /sys/firmware/turris-mox-rwtm/pubkey	15	What: /sys/firmware/turris-mox-rwtm/pubkey
16	Date: August 2019	16	Date: August 2019
17	KernelVersion: 5.4	17	KernelVersion: 5.4
18	Contact: Marek Behún <marek.behun@nic.cz>	18	Contact: Marek Behún <marek.behun@nic.cz>
19	Description: (R) ECDSA public key (in pubkey hex compressed form) computed	19	Description: (Read) ECDSA public key (in pubkey hex compressed form) computed
20	as pair to the ECDSA private key burned into eFuses of this	20	as pair to the ECDSA private key burned into eFuses of this
21	Turris Mox Board.	21	Turris Mox Board.
22	Format: string	22	Format: string
@@ -25,7 +25,7 @@ What: /sys/firmware/turris-mox-rwtm/ram_size · 2 unmodified lines
25	Date: August 2019	25	Date: August 2019
26	KernelVersion: 5.4	26	KernelVersion: 5.4
27	Contact: Marek Behún <marek.behun@nic.cz>	27	Contact: Marek Behún <marek.behun@nic.cz>
28	Description: (R) RAM size in MiB of this Turris Mox board as was detected	28	Description: (Read) RAM size in MiB of this Turris Mox board as was detected
29	during manufacturing and burned into eFuses. Can be 512 or 1024.	29	during manufacturing and burned into eFuses. Can be 512 or 1024.
30	Format: %i	30	Format: %i
31		31
@@ -33,5 +33,5 @@ What: /sys/firmware/turris-mox-rwtm/serial_number · 1 unmodified line
33	Date: August 2019	33	Date: August 2019
34	KernelVersion: 5.4	34	KernelVersion: 5.4
35	Contact: Marek Behún <marek.behun@nic.cz>	35	Contact: Marek Behún <marek.behun@nic.cz>
36	Description: (R) Serial number burned into eFuses of this Turris Mox device.	36	Description: (Read) Serial number burned into eFuses of this Turris Mox device.
37	Format: %016X	37	Format: %016X

Documentation/ABI/testing/sysfs-fs-ext4+2−2

@@ -45,8 +45,8 @@ Description: · 44 unmodified lines
45	parameter will have their blocks allocated out of a	45	parameter will have their blocks allocated out of a
46	block group specific preallocation pool, so that small	46	block group specific preallocation pool, so that small
47	files are packed closely together. Each large file	47	files are packed closely together. Each large file
48	will have its blocks allocated out of its own unique	48	will have its blocks allocated out of its own unique
49	preallocation pool.	49	preallocation pool.
50		50
51	What: /sys/fs/ext4/<disk>/inode_readahead_blks	51	What: /sys/fs/ext4/<disk>/inode_readahead_blks
52	Date: March 2008	52	Date: March 2008

Documentation/ABI/testing/sysfs-fs-f2fs+34−14

@@ -20,10 +20,13 @@ What: /sys/fs/f2fs/<disk>/gc_idle · 19 unmodified lines
20	Date: July 2013	20	Date: July 2013
21	Contact: "Namjae Jeon" <namjae.jeon@samsung.com>	21	Contact: "Namjae Jeon" <namjae.jeon@samsung.com>
22	Description: Controls the victim selection policy for garbage collection.	22	Description: Controls the victim selection policy for garbage collection.
23	Setting gc_idle = 0(default) will disable this option. Setting	23	Setting gc_idle = 0(default) will disable this option. Setting:
24	gc_idle = 1 will select the Cost Benefit approach & setting	24
25	gc_idle = 2 will select the greedy approach & setting	25	=========== ===============================================
26	gc_idle = 3 will select the age-threshold based approach.	26	gc_idle = 1 will select the Cost Benefit approach & setting
		27	gc_idle = 2 will select the greedy approach & setting
		28	gc_idle = 3 will select the age-threshold based approach.
		29	=========== ===============================================
27		30
28	What: /sys/fs/f2fs/<disk>/reclaim_segments	31	What: /sys/fs/f2fs/<disk>/reclaim_segments
29	Date: October 2013	32	Date: October 2013
@@ -46,10 +49,17 @@ Date: November 2013 · 16 unmodified lines
46	Contact: "Jaegeuk Kim" <jaegeuk.kim@samsung.com>	49	Contact: "Jaegeuk Kim" <jaegeuk.kim@samsung.com>
47	Description: Controls the in-place-update policy.	50	Description: Controls the in-place-update policy.
48	updates in f2fs. User can set:	51	updates in f2fs. User can set:
49	0x01: F2FS_IPU_FORCE, 0x02: F2FS_IPU_SSR,	52
50	0x04: F2FS_IPU_UTIL, 0x08: F2FS_IPU_SSR_UTIL,	53	==== =================
51	0x10: F2FS_IPU_FSYNC, 0x20: F2FS_IPU_ASYNC,	54	0x01 F2FS_IPU_FORCE
52	0x40: F2FS_IPU_NOCACHE.	55	0x02 F2FS_IPU_SSR
		56	0x04 F2FS_IPU_UTIL
		57	0x08 F2FS_IPU_SSR_UTIL
		58	0x10 F2FS_IPU_FSYNC
		59	0x20 F2FS_IPU_ASYNC,
		60	0x40 F2FS_IPU_NOCACHE
		61	==== =================
		62
53	Refer segment.h for details.	63	Refer segment.h for details.
54		64
55	What: /sys/fs/f2fs/<disk>/min_ipu_util	65	What: /sys/fs/f2fs/<disk>/min_ipu_util
@@ -332,18 +342,28 @@ Date: April 2020 · 276 unmodified lines
332	Contact: "Jaegeuk Kim" <jaegeuk@kernel.org>	342	Contact: "Jaegeuk Kim" <jaegeuk@kernel.org>
333	Description: Give a way to attach REQ_META\|FUA to data writes	343	Description: Give a way to attach REQ_META\|FUA to data writes
334	given temperature-based bits. Now the bits indicate:	344	given temperature-based bits. Now the bits indicate:
335	* REQ_META \| REQ_FUA \|	345
336	* 5 \| 4 \| 3 \| 2 \| 1 \| 0 \|	346	+-------------------+-------------------+
337	* Cold \| Warm \| Hot \| Cold \| Warm \| Hot \|	347	\| REQ_META \| REQ_FUA \|
		348	+------+------+-----+------+------+-----+
		349	\| 5 \| 4 \| 3 \| 2 \| 1 \| 0 \|
		350	+------+------+-----+------+------+-----+
		351	\| Cold \| Warm \| Hot \| Cold \| Warm \| Hot \|
		352	+------+------+-----+------+------+-----+
338		353
339	What: /sys/fs/f2fs/<disk>/node_io_flag	354	What: /sys/fs/f2fs/<disk>/node_io_flag
340	Date: June 2020	355	Date: June 2020
341	Contact: "Jaegeuk Kim" <jaegeuk@kernel.org>	356	Contact: "Jaegeuk Kim" <jaegeuk@kernel.org>
342	Description: Give a way to attach REQ_META\|FUA to node writes	357	Description: Give a way to attach REQ_META\|FUA to node writes
343	given temperature-based bits. Now the bits indicate:	358	given temperature-based bits. Now the bits indicate:
344	* REQ_META \| REQ_FUA \|	359
345	* 5 \| 4 \| 3 \| 2 \| 1 \| 0 \|	360	+-------------------+-------------------+
346	* Cold \| Warm \| Hot \| Cold \| Warm \| Hot \|	361	\| REQ_META \| REQ_FUA \|
		362	+------+------+-----+------+------+-----+
		363	\| 5 \| 4 \| 3 \| 2 \| 1 \| 0 \|
		364	+------+------+-----+------+------+-----+
		365	\| Cold \| Warm \| Hot \| Cold \| Warm \| Hot \|
		366	+------+------+-----+------+------+-----+
347		367
348	What: /sys/fs/f2fs/<disk>/iostat_period_ms	368	What: /sys/fs/f2fs/<disk>/iostat_period_ms
349	Date: April 2020	369	Date: April 2020

Documentation/ABI/testing/sysfs-hypervisor-xen+8−5

@@ -15,14 +15,17 @@ KernelVersion: 4.3 · 14 unmodified lines
15	Contact: Boris Ostrovsky <boris.ostrovsky@oracle.com>	15	Contact: Boris Ostrovsky <boris.ostrovsky@oracle.com>
16	Description: If running under Xen:	16	Description: If running under Xen:
17	Describes mode that Xen's performance-monitoring unit (PMU)	17	Describes mode that Xen's performance-monitoring unit (PMU)
18	uses. Accepted values are	18	uses. Accepted values are:
19	"off" -- PMU is disabled	19
20	"self" -- The guest can profile itself	20	====== ============================================
21	"hv" -- The guest can profile itself and, if it is	21	"off" PMU is disabled
		22	"self" The guest can profile itself
		23	"hv" The guest can profile itself and, if it is
22	privileged (e.g. dom0), the hypervisor	24	privileged (e.g. dom0), the hypervisor
23	"all" -- The guest can profile itself, the hypervisor	25	"all" The guest can profile itself, the hypervisor
24	and all other guests. Only available to	26	and all other guests. Only available to
25	privileged guests.	27	privileged guests.
		28	====== ============================================
26		29
27	What: /sys/hypervisor/pmu/pmu_features	30	What: /sys/hypervisor/pmu/pmu_features
28	Date: August 2015	31	Date: August 2015

Documentation/ABI/testing/sysfs-kernel-boot_params+12−11

@@ -23,16 +23,17 @@ Description: The /sys/kernel/boot_params directory contains two · 22 unmodified lines
23	representation of setup_data type. "data" file is the binary	23	representation of setup_data type. "data" file is the binary
24	representation of setup_data payload.	24	representation of setup_data payload.
25		25
26	The whole boot_params directory structure is like below:	26	The whole boot_params directory structure is like below::
27	/sys/kernel/boot_params	27
28	\|__ data	28	/sys/kernel/boot_params
29	\|__ setup_data	29	\|__ data
30	\| \|__ 0	30	\|__ setup_data
31	\| \| \|__ data	31	\| \|__ 0
32	\| \| \|__ type	32	\| \| \|__ data
33	\| \|__ 1	33	\| \| \|__ type
34	\| \|__ data	34	\| \|__ 1
35	\| \|__ type	35	\| \|__ data
36	\|__ version	36	\| \|__ type
		37	\|__ version
37		38
38	Users: Kexec	39	Users: Kexec

Documentation/ABI/testing/sysfs-kernel-mm-hugepages+7−5

@@ -7,9 +7,11 @@ Description: · 6 unmodified lines
7	of the hugepages supported by the kernel/CPU combination.	7	of the hugepages supported by the kernel/CPU combination.
8		8
9	Under these directories are a number of files:	9	Under these directories are a number of files:
10	nr_hugepages	10
11	nr_overcommit_hugepages	11	- nr_hugepages
12	free_hugepages	12	- nr_overcommit_hugepages
13	surplus_hugepages	13	- free_hugepages
14	resv_hugepages	14	- surplus_hugepages
		15	- resv_hugepages
		16
15	See Documentation/admin-guide/mm/hugetlbpage.rst for details.	17	See Documentation/admin-guide/mm/hugetlbpage.rst for details.

Documentation/ABI/testing/sysfs-kernel-mm-ksm+3−2

@@ -34,8 +34,9 @@ Description: Kernel Samepage Merging daemon sysfs interface · 33 unmodified lines
34	in a tree.	34	in a tree.
35		35
36	run: write 0 to disable ksm, read 0 while ksm is disabled.	36	run: write 0 to disable ksm, read 0 while ksm is disabled.
37	write 1 to run ksm, read 1 while ksm is running.	37
38	write 2 to disable ksm and unmerge all its pages.	38	- write 1 to run ksm, read 1 while ksm is running.
		39	- write 2 to disable ksm and unmerge all its pages.
39		40
40	sleep_millisecs: how many milliseconds ksm should sleep between	41	sleep_millisecs: how many milliseconds ksm should sleep between
41	scans.	42	scans.

Documentation/ABI/testing/sysfs-kernel-slab+3−0

Documentation/ABI/testing/sysfs-module+10−7

 Contact:	Kirill Smelkov <kirr@mns.spb.ru>
 Description:	Maximum time allowed for periodic transfers per microframe (μs)
-		[ USB 2.0 sets maximum allowed time for periodic transfers per
+		Note:
+		  USB 2.0 sets maximum allowed time for periodic transfers per
 		  microframe to be 80%, that is 100 microseconds out of 125
 		  microseconds (full microframe).
 		  However there are cases, when 80% max isochronous bandwidth is
 		  too limiting. For example two video streams could require 110
 		  microseconds of isochronous bandwidth per microframe to work
-		  together. ]
+		  together.
 		Through this setting it is possible to raise the limit so that
 		the host controller would allow allocating more than 100
 KernelVersion:»·3.3
 Contact:	Kay Sievers <kay.sievers@vrfy.org>
 Description:	Module taint flags:
-			P - proprietary module
+			==  =====================
-			O - out-of-tree module
+			P   proprietary module
-			F - force-loaded module
+			O   out-of-tree module
-			C - staging driver module
+			F   force-loaded module
-			E - unsigned module
+			C   staging driver module
+			E   unsigned module
+			==  =====================

Documentation/ABI/testing/sysfs-platform-asus-laptop+13−8

@@ -4,13 +4,16 @@ KernelVersion: 2.6.20 · 3 unmodified lines
4	Contact: "Corentin Chary" <corentincj@iksaif.net>	4	Contact: "Corentin Chary" <corentincj@iksaif.net>
5	Description:	5	Description:
6	This file allows display switching. The value	6	This file allows display switching. The value
7	is composed by 4 bits and defined as follow:	7	is composed by 4 bits and defined as follow::
8	4321	8
9	\|\|\|`- LCD	9	4321
10	\|\|`-- CRT	10	\|\|\|`- LCD
11	\|`--- TV	11	\|\|`-- CRT
12	`---- DVI	12	\|`--- TV
13	Ex: - 0 (0000b) means no display	13	`---- DVI
		14
		15	Ex:
		16	- 0 (0000b) means no display
14	- 3 (0011b) CRT+LCD.	17	- 3 (0011b) CRT+LCD.
15		18
16	What: /sys/devices/platform/asus_laptop/gps	19	What: /sys/devices/platform/asus_laptop/gps
@@ -28,8 +31,10 @@ Contact: "Corentin Chary" <corentincj@iksaif.net> · 11 unmodified lines
28	Description:	31	Description:
29	Some models like the W1N have a LED display that can be	32	Some models like the W1N have a LED display that can be
30	used to display several items of information.	33	used to display several items of information.
31	To control the LED display, use the following :	34	To control the LED display, use the following::
		35
32	echo 0x0T000DDD > /sys/devices/platform/asus_laptop/	36	echo 0x0T000DDD > /sys/devices/platform/asus_laptop/
		37
33	where T control the 3 letters display, and DDD the 3 digits display.	38	where T control the 3 letters display, and DDD the 3 digits display.
34	The DDD table can be found in Documentation/admin-guide/laptops/asus-laptop.rst	39	The DDD table can be found in Documentation/admin-guide/laptops/asus-laptop.rst
35		40

Documentation/ABI/testing/sysfs-platform-asus-wmi+1−0

@@ -5,6 +5,7 @@ Contact: "Corentin Chary" <corentincj@iksaif.net> · 4 unmodified lines
5	Description:	5	Description:
6	Change CPU clock configuration (write-only).	6	Change CPU clock configuration (write-only).
7	There are three available clock configuration:	7	There are three available clock configuration:
		8
8	* 0 -> Super Performance Mode	9	* 0 -> Super Performance Mode
9	* 1 -> High Performance Mode	10	* 1 -> High Performance Mode
10	* 2 -> Power Saving Mode	11	* 2 -> Power Saving Mode

Documentation/ABI/testing/sysfs-platform-at91+6−4

@@ -18,8 +18,10 @@ Description: · 17 unmodified lines
18	In order to use an extended can_id add the	18	In order to use an extended can_id add the
19	CAN_EFF_FLAG (0x80000000U) to the can_id. Example:	19	CAN_EFF_FLAG (0x80000000U) to the can_id. Example:
20		20
21	- standard id 0x7ff:	21	- standard id 0x7ff::
22	echo 0x7ff > /sys/class/net/can0/mb0_id
23		22
24	- extended id 0x1fffffff:	23	echo 0x7ff > /sys/class/net/can0/mb0_id
25	echo 0x9fffffff > /sys/class/net/can0/mb0_id	24
		25	- extended id 0x1fffffff::
		26
		27	echo 0x9fffffff > /sys/class/net/can0/mb0_id

Documentation/ABI/testing/sysfs-platform-dell-laptop+7−3

Documentation/ABI/testing/sysfs-platform-dell-smbios+2−2

@@ -13,8 +13,8 @@ Description: · 12 unmodified lines
13	For example the token ID "5" would be available	13	For example the token ID "5" would be available
14	as the following attributes:	14	as the following attributes:
15		15
16	0005_location	16	- 0005_location
17	0005_value	17	- 0005_value
18		18
19	Tokens will vary from machine to machine, and	19	Tokens will vary from machine to machine, and
20	only tokens available on that machine will be	20	only tokens available on that machine will be

Documentation/ABI/testing/sysfs-platform-dfl-fme+10−4

@@ -113,8 +113,11 @@ KernelVersion: 5.5 · 112 unmodified lines
113	Contact: Wu Hao <hao.wu@intel.com>	113	Contact: Wu Hao <hao.wu@intel.com>
114	Description: Read-Only. Read this file to get the name of hwmon device, it	114	Description: Read-Only. Read this file to get the name of hwmon device, it
115	supports values:	115	supports values:
116	'dfl_fme_thermal' - thermal hwmon device name	116
117	'dfl_fme_power' - power hwmon device name	117	================= =========================
		118	'dfl_fme_thermal' thermal hwmon device name
		119	'dfl_fme_power' power hwmon device name
		120	================= =========================
118		121
119	What: /sys/bus/platform/devices/dfl-fme.0/hwmon/hwmonX/temp1_input	122	What: /sys/bus/platform/devices/dfl-fme.0/hwmon/hwmonX/temp1_input
120	Date: October 2019	123	Date: October 2019
@@ -169,8 +172,11 @@ KernelVersion: 5.5 · 48 unmodified lines
169	Contact: Wu Hao <hao.wu@intel.com>	172	Contact: Wu Hao <hao.wu@intel.com>
170	Description: Read-Only. Read this file to get the policy of hardware threshold1	173	Description: Read-Only. Read this file to get the policy of hardware threshold1
171	(see 'temp1_max'). It only supports two values (policies):	174	(see 'temp1_max'). It only supports two values (policies):
172	0 - AP2 state (90% throttling)	175
173	1 - AP1 state (50% throttling)	176	== ==========================
		177	0 AP2 state (90% throttling)
		178	1 AP1 state (50% throttling)
		179	== ==========================
174		180
175	What: /sys/bus/platform/devices/dfl-fme.0/hwmon/hwmonX/power1_input	181	What: /sys/bus/platform/devices/dfl-fme.0/hwmon/hwmonX/power1_input
176	Date: October 2019	182	Date: October 2019

Documentation/ABI/testing/sysfs-platform-dptf+7−4

 Contact:	linux-acpi@vger.kernel.org
 Description:
 		(RO) Display the platform power source
+		========= ============================
 		bits[3:0] Current power source
-			0x00 = DC
+			  - 0x00 = DC
-			0x01 = AC
+			  - 0x01 = AC
-			0x02 = USB
+			  - 0x02 = USB
-			0x03 = Wireless Charger
+			  - 0x03 = Wireless Charger
 		bits[7:4] Power source sequence number
+		========= ============================
 What:		/sys/bus/platform/devices/INT3407:00/dptf_power/battery_steady_power
 Date:		Jul, 2016

Documentation/ABI/testing/sysfs-platform-eeepc-laptop+10−4

@@ -4,9 +4,11 @@ KernelVersion: 2.6.26 · 3 unmodified lines
4	Contact: "Corentin Chary" <corentincj@iksaif.net>	4	Contact: "Corentin Chary" <corentincj@iksaif.net>
5	Description:	5	Description:
6	This file allows display switching.	6	This file allows display switching.
		7
7	- 1 = LCD	8	- 1 = LCD
8	- 2 = CRT	9	- 2 = CRT
9	- 3 = LCD+CRT	10	- 3 = LCD+CRT
		11
10	If you run X11, you should use xrandr instead.	12	If you run X11, you should use xrandr instead.
11		13
12	What: /sys/devices/platform/eeepc/camera	14	What: /sys/devices/platform/eeepc/camera
@@ -30,16 +32,20 @@ Contact: "Corentin Chary" <corentincj@iksaif.net> · 17 unmodified lines
30	Description:	32	Description:
31	Change CPU clock configuration.	33	Change CPU clock configuration.
32	On the Eee PC 1000H there are three available clock configuration:	34	On the Eee PC 1000H there are three available clock configuration:
		35
33	* 0 -> Super Performance Mode	36	* 0 -> Super Performance Mode
34	* 1 -> High Performance Mode	37	* 1 -> High Performance Mode
35	* 2 -> Power Saving Mode	38	* 2 -> Power Saving Mode
		39
36	On Eee PC 701 there is only 2 available clock configurations.	40	On Eee PC 701 there is only 2 available clock configurations.
37	Available configuration are listed in available_cpufv file.	41	Available configuration are listed in available_cpufv file.
38	Reading this file will show the raw hexadecimal value which	42	Reading this file will show the raw hexadecimal value which
39	is defined as follow:	43	is defined as follow::
40	\| 8 bit \| 8 bit \|	44
41	\| `---- Current mode	45	\| 8 bit \| 8 bit \|
42	`------------ Availables modes	46	\| `---- Current mode
		47	`------------ Availables modes
		48
43	For example, 0x301 means: mode 1 selected, 3 available modes.	49	For example, 0x301 means: mode 1 selected, 3 available modes.
44		50
45	What: /sys/devices/platform/eeepc/available_cpufv	51	What: /sys/devices/platform/eeepc/available_cpufv

Documentation/ABI/testing/sysfs-platform-i2c-demux-pinctrl+2−2

@@ -5,9 +5,9 @@ Contact: Wolfram Sang <wsa+renesas@sang-engineering.com> · 4 unmodified lines
5	Description:	5	Description:
6	Reading the file will give you a list of masters which can be	6	Reading the file will give you a list of masters which can be
7	selected for a demultiplexed bus. The format is	7	selected for a demultiplexed bus. The format is
8	"<index>:<name>". Example from a Renesas Lager board:	8	"<index>:<name>". Example from a Renesas Lager board::
9		9
10	0:/i2c@e6500000 1:/i2c@e6508000	10	0:/i2c@e6500000 1:/i2c@e6508000
11		11
12	What: /sys/devices/platform/<i2c-demux-name>/current_master	12	What: /sys/devices/platform/<i2c-demux-name>/current_master
13	Date: January 2016	13	Date: January 2016

Documentation/ABI/testing/sysfs-platform-ideapad-laptop+6−3

@@ -12,6 +12,7 @@ Contact: "Maxim Mikityanskiy <maxtram95@gmail.com>" · 11 unmodified lines
12	Description:	12	Description:
13	Change fan mode	13	Change fan mode
14	There are four available modes:	14	There are four available modes:
		15
15	* 0 -> Super Silent Mode	16	* 0 -> Super Silent Mode
16	* 1 -> Standard Mode	17	* 1 -> Standard Mode
17	* 2 -> Dust Cleaning	18	* 2 -> Dust Cleaning
@@ -32,9 +33,11 @@ KernelVersion: 4.18 · 14 unmodified lines
32	Contact: "Oleg Keri <ezhi99@gmail.com>"	33	Contact: "Oleg Keri <ezhi99@gmail.com>"
33	Description:	34	Description:
34	Control fn-lock mode.	35	Control fn-lock mode.
		36
35	* 1 -> Switched On	37	* 1 -> Switched On
36	* 0 -> Switched Off	38	* 0 -> Switched Off
37		39
38	For example:	40	For example::
39	# echo "0" > \	41
40	/sys/bus/pci/devices/0000:00:1f.0/PNP0C09:00/VPC2004:00/fn_lock	42	# echo "0" > \
		43	/sys/bus/pci/devices/0000:00:1f.0/PNP0C09:00/VPC2004:00/fn_lock

Documentation/ABI/testing/sysfs-platform-intel-wmi-sbl-fw-update+1−0

@@ -8,5 +8,6 @@ Description: · 7 unmodified lines
8	of 0 and userspace can signal SBL to update firmware,	8	of 0 and userspace can signal SBL to update firmware,
9	on next reboot, by writing a value of 1.	9	on next reboot, by writing a value of 1.
10	There are two available states:	10	There are two available states:
		11
11	* 0 -> Skip firmware update while rebooting	12	* 0 -> Skip firmware update while rebooting
12	* 1 -> Attempt firmware update on next reboot	13	* 1 -> Attempt firmware update on next reboot

Documentation/ABI/testing/sysfs-platform-intel-wmi-thunderbolt+1−0

@@ -7,5 +7,6 @@ Description: · 6 unmodified lines
7	Thunderbolt controllers to turn on or off when no	7	Thunderbolt controllers to turn on or off when no
8	devices are connected (write-only)	8	devices are connected (write-only)
9	There are two available states:	9	There are two available states:
		10
10	* 0 -> Force power disabled	11	* 0 -> Force power disabled
11	* 1 -> Force power enabled	12	* 1 -> Force power enabled

Documentation/ABI/testing/sysfs-platform-kim+1−0

@@ -5,6 +5,7 @@ Contact: "Pavan Savoy" <pavan_savoy@ti.com> · 4 unmodified lines
5	Description:	5	Description:
6	Name of the UART device at which the WL128x chip	6	Name of the UART device at which the WL128x chip
7	is connected. example: "/dev/ttyS0".	7	is connected. example: "/dev/ttyS0".
		8
8	The device name flows down to architecture specific board	9	The device name flows down to architecture specific board
9	initialization file from the SFI/ATAGS bootloader	10	initialization file from the SFI/ATAGS bootloader
10	firmware. The name exposed is read from the user-space	11	firmware. The name exposed is read from the user-space

Documentation/ABI/testing/sysfs-platform-mellanox-bootctl+31−19

@@ -5,10 +5,13 @@ Contact: "Liming Sun <lsun@mellanox.com>" · 4 unmodified lines
5	Description:	5	Description:
6	The Life-cycle state of the SoC, which could be one of the	6	The Life-cycle state of the SoC, which could be one of the
7	following values.	7	following values.
8	Production - Production state and can be updated to secure	8
9	GA Secured - Secure chip and not able to change state	9	============== =============================================
10	GA Non-Secured - Non-Secure chip and not able to change state	10	Production Production state and can be updated to secure
11	RMA - Return Merchandise Authorization	11	GA Secured Secure chip and not able to change state
		12	GA Non-Secured Non-Secure chip and not able to change state
		13	RMA Return Merchandise Authorization
		14	============== =============================================
12		15
13	What: /sys/bus/platform/devices/MLNXBF04:00/post_reset_wdog	16	What: /sys/bus/platform/devices/MLNXBF04:00/post_reset_wdog
14	Date: Oct 2019	17	Date: Oct 2019
@@ -25,10 +28,13 @@ KernelVersion: 5.5 · 10 unmodified lines
25	Contact: "Liming Sun <lsun@mellanox.com>"	28	Contact: "Liming Sun <lsun@mellanox.com>"
26	Description:	29	Description:
27	The source of the boot stream for the next reset. It could be	30	The source of the boot stream for the next reset. It could be
28	one of the following values.	31	one of the following values:
29	external - boot from external source (USB or PCIe)	32
30	emmc - boot from the onchip eMMC	33	=========== ===============================================
31	emmc_legacy - boot from the onchip eMMC in legacy (slow) mode	34	external boot from external source (USB or PCIe)
		35	emmc boot from the onchip eMMC
		36	emmc_legacy boot from the onchip eMMC in legacy (slow) mode
		37	=========== ===============================================
32		38
33	What: /sys/bus/platform/devices/MLNXBF04:00/second_reset_action	39	What: /sys/bus/platform/devices/MLNXBF04:00/second_reset_action
34	Date: Oct 2019	40	Date: Oct 2019
@@ -38,11 +44,14 @@ Description: · 3 unmodified lines
38	Update the source of the boot stream after next reset. It could	44	Update the source of the boot stream after next reset. It could
39	be one of the following values and will be applied after next	45	be one of the following values and will be applied after next
40	reset.	46	reset.
41	external - boot from external source (USB or PCIe)	47
42	emmc - boot from the onchip eMMC	48	=========== ===============================================
43	emmc_legacy - boot from the onchip eMMC in legacy (slow) mode	49	external boot from external source (USB or PCIe)
44	swap_emmc - swap the primary / secondary boot partition	50	emmc boot from the onchip eMMC
45	none - cancel the action	51	emmc_legacy boot from the onchip eMMC in legacy (slow) mode
		52	swap_emmc swap the primary / secondary boot partition
		53	none cancel the action
		54	=========== ===============================================
46		55
47	What: /sys/bus/platform/devices/MLNXBF04:00/secure_boot_fuse_state	56	What: /sys/bus/platform/devices/MLNXBF04:00/secure_boot_fuse_state
48	Date: Oct 2019	57	Date: Oct 2019
@@ -50,9 +59,12 @@ KernelVersion: 5.5 · 1 unmodified line
50	Contact: "Liming Sun <lsun@mellanox.com>"	59	Contact: "Liming Sun <lsun@mellanox.com>"
51	Description:	60	Description:
52	The state of eFuse versions with the following values.	61	The state of eFuse versions with the following values.
53	InUse - burnt, valid and currently in use	62
54	Used - burnt and valid	63	======= ===============================================
55	Free - not burnt and free to use	64	InUse burnt, valid and currently in use
56	Skipped - not burnt but not free (skipped)	65	Used burnt and valid
57	Wasted - burnt and invalid	66	Free not burnt and free to use
58	Invalid - not burnt but marked as valid (error state).	67	Skipped not burnt but not free (skipped)
		68	Wasted burnt and invalid
		69	Invalid not burnt but marked as valid (error state).
		70	======= ===============================================

Documentation/ABI/testing/sysfs-platform-phy-rcar-gen3-usb2+6−4

@@ -7,9 +7,11 @@ Description: · 6 unmodified lines
7	The file can show/change the phy mode for role swap of usb.	7	The file can show/change the phy mode for role swap of usb.
8		8
9	Write the following strings to change the mode:	9	Write the following strings to change the mode:
10	"host" - switching mode from peripheral to host.	10
11	"peripheral" - switching mode from host to peripheral.	11	- "host" - switching mode from peripheral to host.
		12	- "peripheral" - switching mode from host to peripheral.
12		13
13	Read the file, then it shows the following strings:	14	Read the file, then it shows the following strings:
14	"host" - The mode is host now.	15
15	"peripheral" - The mode is peripheral now.	16	- "host" - The mode is host now.
		17	- "peripheral" - The mode is peripheral now.

Documentation/ABI/testing/sysfs-platform-renesas_usb3+6−4

@@ -7,9 +7,11 @@ Description: · 6 unmodified lines
7	The file can show/change the drd mode of usb.	7	The file can show/change the drd mode of usb.
8		8
9	Write the following string to change the mode:	9	Write the following string to change the mode:
10	"host" - switching mode from peripheral to host.	10
11	"peripheral" - switching mode from host to peripheral.	11	- "host" - switching mode from peripheral to host.
		12	- "peripheral" - switching mode from host to peripheral.
12		13
13	Read the file, then it shows the following strings:	14	Read the file, then it shows the following strings:
14	"host" - The mode is host now.	15
15	"peripheral" - The mode is peripheral now.	16	- "host" - The mode is host now.
		17	- "peripheral" - The mode is peripheral now.

Documentation/ABI/testing/sysfs-platform-sst-atom+11−2

@@ -5,13 +5,22 @@ Contact: "Sebastien Guiriec" <sebastien.guiriec@intel.com> · 4 unmodified lines
5	Description:	5	Description:
6	LPE Firmware version for SST driver on all atom	6	LPE Firmware version for SST driver on all atom
7	plaforms (BYT/CHT/Merrifield/BSW).	7	plaforms (BYT/CHT/Merrifield/BSW).
8	If the FW has never been loaded it will display:	8	If the FW has never been loaded it will display::
		9
9	"FW not yet loaded"	10	"FW not yet loaded"
10	If FW has been loaded it will display:	11
		12	If FW has been loaded it will display::
		13
11	"v01.aa.bb.cc"	14	"v01.aa.bb.cc"
		15
12	aa: Major version is reflecting SoC version:	16	aa: Major version is reflecting SoC version:
		17
		18	=== =============
13	0d: BYT FW	19	0d: BYT FW
14	0b: BSW FW	20	0b: BSW FW
15	07: Merrifield FW	21	07: Merrifield FW
		22	=== =============
		23
16	bb: Minor version	24	bb: Minor version
		25
17	cc: Build version	26	cc: Build version

Documentation/ABI/testing/sysfs-platform-usbip-vudc+7−4

@@ -16,10 +16,13 @@ Contact: Krzysztof Opasiak <k.opasiak@samsung.com> · 15 unmodified lines
16	Description:	16	Description:
17	Current status of the device.	17	Current status of the device.
18	Allowed values:	18	Allowed values:
19	1 - Device is available and can be exported	19
20	2 - Device is currently exported	20	== ==========================================
21	3 - Fatal error occurred during communication	21	1 Device is available and can be exported
22	with peer	22	2 Device is currently exported
		23	3 Fatal error occurred during communication
		24	with peer
		25	== ==========================================
23		26
24	What: /sys/devices/platform/usbip-vudc.%d/usbip_sockfd	27	What: /sys/devices/platform/usbip-vudc.%d/usbip_sockfd
25	Date: April 2016	28	Date: April 2016

Documentation/ABI/testing/sysfs-platform-wilco-ec+1−0

@@ -39,6 +39,7 @@ Description: · 38 unmodified lines
39	which affects charging via the special USB PowerShare port	39	which affects charging via the special USB PowerShare port
40	(marked with a small lightning bolt or battery icon) when in	40	(marked with a small lightning bolt or battery icon) when in
41	low power states:	41	low power states:
		42
42	- In S0, the port will always provide power.	43	- In S0, the port will always provide power.
43	- In S0ix, if usb_charge is enabled, then power will be	44	- In S0ix, if usb_charge is enabled, then power will be
44	supplied to the port when on AC or if battery is > 50%.	45	supplied to the port when on AC or if battery is > 50%.

Documentation/ABI/testing/sysfs-power+13−8

Documentation/ABI/testing/sysfs-profiling+1−1

@@ -5,7 +5,7 @@ Description: · 4 unmodified lines
5	/sys/kernel/profiling is the runtime equivalent	5	/sys/kernel/profiling is the runtime equivalent
6	of the boot-time profile= option.	6	of the boot-time profile= option.
7		7
8	You can get the same effect running:	8	You can get the same effect running::
9		9
10	echo 2 > /sys/kernel/profiling	10	echo 2 > /sys/kernel/profiling
11		11

Documentation/ABI/testing/sysfs-ptp+1−1

@@ -69,7 +69,7 @@ Description: · 68 unmodified lines
69	pin offered by the PTP hardware clock. The file name	69	pin offered by the PTP hardware clock. The file name
70	is the hardware dependent pin name. Reading from this	70	is the hardware dependent pin name. Reading from this
71	file produces two numbers, the assigned function (see	71	file produces two numbers, the assigned function (see
72	the PTP_PF_ enumeration values in linux/ptp_clock.h)	72	the `PTP_PF_` enumeration values in linux/ptp_clock.h)
73	and the channel number. The function and channel	73	and the channel number. The function and channel
74	assignment may be changed by two writing numbers into	74	assignment may be changed by two writing numbers into
75	the file.	75	the file.

Documentation/ABI/testing/sysfs-uevent+16−12

@@ -6,42 +6,46 @@ Description: · 5 unmodified lines
6	Enable passing additional variables for synthetic uevents that	6	Enable passing additional variables for synthetic uevents that
7	are generated by writing /sys/.../uevent file.	7	are generated by writing /sys/.../uevent file.
8		8
9	Recognized extended format is ACTION [UUID [KEY=VALUE ...].	9	Recognized extended format is::
10		10
11	The ACTION is compulsory - it is the name of the uevent action	11	ACTION [UUID [KEY=VALUE ...]
12	("add", "change", "remove"). There is no change compared to	12
13	previous functionality here. The rest of the extended format	13	The ACTION is compulsory - it is the name of the uevent
14	is optional.	14	action (``add``, ``change``, ``remove``). There is no change
		15	compared to previous functionality here. The rest of the
		16	extended format is optional.
15		17
16	You need to pass UUID first before any KEY=VALUE pairs.	18	You need to pass UUID first before any KEY=VALUE pairs.
17	The UUID must be in "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"	19	The UUID must be in ``xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx``
18	format where 'x' is a hex digit. The UUID is considered to be	20	format where 'x' is a hex digit. The UUID is considered to be
19	a transaction identifier so it's possible to use the same UUID	21	a transaction identifier so it's possible to use the same UUID
20	value for one or more synthetic uevents in which case we	22	value for one or more synthetic uevents in which case we
21	logically group these uevents together for any userspace	23	logically group these uevents together for any userspace
22	listeners. The UUID value appears in uevent as	24	listeners. The UUID value appears in uevent as
23	"SYNTH_UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx" environment	25	``SYNTH_UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx`` environment
24	variable.	26	variable.
25		27
26	If UUID is not passed in, the generated synthetic uevent gains	28	If UUID is not passed in, the generated synthetic uevent gains
27	"SYNTH_UUID=0" environment variable automatically.	29	``SYNTH_UUID=0`` environment variable automatically.
28		30
29	The KEY=VALUE pairs can contain alphanumeric characters only.	31	The KEY=VALUE pairs can contain alphanumeric characters only.
		32
30	It's possible to define zero or more pairs - each pair is then	33	It's possible to define zero or more pairs - each pair is then
31	delimited by a space character ' '. Each pair appears in	34	delimited by a space character ' '. Each pair appears in
32	synthetic uevent as "SYNTH_ARG_KEY=VALUE". That means the KEY	35	synthetic uevent as ``SYNTH_ARG_KEY=VALUE``. That means the KEY
33	name gains "SYNTH_ARG_" prefix to avoid possible collisions	36	name gains ``SYNTH_ARG_`` prefix to avoid possible collisions
34	with existing variables.	37	with existing variables.
35		38
36	Example of valid sequence written to the uevent file:	39	Example of valid sequence written to the uevent file::
37		40
38	add fe4d7c9d-b8c6-4a70-9ef1-3d8a58d18eed A=1 B=abc	41	add fe4d7c9d-b8c6-4a70-9ef1-3d8a58d18eed A=1 B=abc
39		42
40	This generates synthetic uevent including these variables:	43	This generates synthetic uevent including these variables::
41		44
42	ACTION=add	45	ACTION=add
43	SYNTH_ARG_A=1	46	SYNTH_ARG_A=1
44	SYNTH_ARG_B=abc	47	SYNTH_ARG_B=abc
45	SYNTH_UUID=fe4d7c9d-b8c6-4a70-9ef1-3d8a58d18eed	48	SYNTH_UUID=fe4d7c9d-b8c6-4a70-9ef1-3d8a58d18eed
		49
46	Users:	50	Users:
47	udev, userspace tools generating synthetic uevents	51	udev, userspace tools generating synthetic uevents

Documentation/ABI/testing/sysfs-wusb_cbaf+2−1

@@ -45,7 +45,8 @@ Description: · 44 unmodified lines
45	7. Device is unplugged.	45	7. Device is unplugged.
46		46
47	References:	47	References:
48	[WUSB-AM] Association Models Supplement to the	48	[WUSB-AM]
		49	Association Models Supplement to the
49	Certified Wireless Universal Serial Bus	50	Certified Wireless Universal Serial Bus
50	Specification, version 1.0.	51	Specification, version 1.0.
51		52

Documentation/ABI/testing/usb-charger-uevent+46−38

@@ -3,44 +3,52 @@ Date: 2020-01-14 · 2 unmodified lines
3	KernelVersion: 5.6	3	KernelVersion: 5.6
4	Contact: linux-usb@vger.kernel.org	4	Contact: linux-usb@vger.kernel.org
5	Description: There are two USB charger states:	5	Description: There are two USB charger states:
6	USB_CHARGER_ABSENT	6
7	USB_CHARGER_PRESENT	7	- USB_CHARGER_ABSENT
		8	- USB_CHARGER_PRESENT
		9
8	There are five USB charger types:	10	There are five USB charger types:
9	USB_CHARGER_UNKNOWN_TYPE: Charger type is unknown	11
10	USB_CHARGER_SDP_TYPE: Standard Downstream Port	12	======================== ==========================
11	USB_CHARGER_CDP_TYPE: Charging Downstream Port	13	USB_CHARGER_UNKNOWN_TYPE Charger type is unknown
12	USB_CHARGER_DCP_TYPE: Dedicated Charging Port	14	USB_CHARGER_SDP_TYPE Standard Downstream Port
13	USB_CHARGER_ACA_TYPE: Accessory Charging Adapter	15	USB_CHARGER_CDP_TYPE Charging Downstream Port
		16	USB_CHARGER_DCP_TYPE Dedicated Charging Port
		17	USB_CHARGER_ACA_TYPE Accessory Charging Adapter
		18	======================== ==========================
		19
14	https://www.usb.org/document-library/battery-charging-v12-spec-and-adopters-agreement	20	https://www.usb.org/document-library/battery-charging-v12-spec-and-adopters-agreement
15		21
16	Here are two examples taken using udevadm monitor -p when	22	Here are two examples taken using ``udevadm monitor -p`` when
17	USB charger is online:	23	USB charger is online::
18	UDEV change /devices/soc0/usbphynop1 (platform)	24
19	ACTION=change	25	UDEV change /devices/soc0/usbphynop1 (platform)
20	DEVPATH=/devices/soc0/usbphynop1	26	ACTION=change
21	DRIVER=usb_phy_generic	27	DEVPATH=/devices/soc0/usbphynop1
22	MODALIAS=of:Nusbphynop1T(null)Cusb-nop-xceiv	28	DRIVER=usb_phy_generic
23	OF_COMPATIBLE_0=usb-nop-xceiv	29	MODALIAS=of:Nusbphynop1T(null)Cusb-nop-xceiv
24	OF_COMPATIBLE_N=1	30	OF_COMPATIBLE_0=usb-nop-xceiv
25	OF_FULLNAME=/usbphynop1	31	OF_COMPATIBLE_N=1
26	OF_NAME=usbphynop1	32	OF_FULLNAME=/usbphynop1
27	SEQNUM=2493	33	OF_NAME=usbphynop1
28	SUBSYSTEM=platform	34	SEQNUM=2493
29	USB_CHARGER_STATE=USB_CHARGER_PRESENT	35	SUBSYSTEM=platform
30	USB_CHARGER_TYPE=USB_CHARGER_SDP_TYPE	36	USB_CHARGER_STATE=USB_CHARGER_PRESENT
31	USEC_INITIALIZED=227422826	37	USB_CHARGER_TYPE=USB_CHARGER_SDP_TYPE
32		38	USEC_INITIALIZED=227422826
33	USB charger is offline:	39
34	KERNEL change /devices/soc0/usbphynop1 (platform)	40	USB charger is offline::
35	ACTION=change	41
36	DEVPATH=/devices/soc0/usbphynop1	42	KERNEL change /devices/soc0/usbphynop1 (platform)
37	DRIVER=usb_phy_generic	43	ACTION=change
38	MODALIAS=of:Nusbphynop1T(null)Cusb-nop-xceiv	44	DEVPATH=/devices/soc0/usbphynop1
39	OF_COMPATIBLE_0=usb-nop-xceiv	45	DRIVER=usb_phy_generic
40	OF_COMPATIBLE_N=1	46	MODALIAS=of:Nusbphynop1T(null)Cusb-nop-xceiv
41	OF_FULLNAME=/usbphynop1	47	OF_COMPATIBLE_0=usb-nop-xceiv
42	OF_NAME=usbphynop1	48	OF_COMPATIBLE_N=1
43	SEQNUM=2494	49	OF_FULLNAME=/usbphynop1
44	SUBSYSTEM=platform	50	OF_NAME=usbphynop1
45	USB_CHARGER_STATE=USB_CHARGER_ABSENT	51	SEQNUM=2494
46	USB_CHARGER_TYPE=USB_CHARGER_UNKNOWN_TYPE	52	SUBSYSTEM=platform
		53	USB_CHARGER_STATE=USB_CHARGER_ABSENT
		54	USB_CHARGER_TYPE=USB_CHARGER_UNKNOWN_TYPE

Documentation/ABI/testing/usb-uevent+16−16

@@ -6,22 +6,22 @@ Description: When the USB Host Controller has entered a state where it is no · 5 unmodified lines
6	longer functional a uevent will be raised. The uevent will	6	longer functional a uevent will be raised. The uevent will
7	contain ACTION=offline and ERROR=DEAD.	7	contain ACTION=offline and ERROR=DEAD.
8		8
9	Here is an example taken using udevadm monitor -p:	9	Here is an example taken using udevadm monitor -p::
10		10
11	KERNEL[130.428945] offline /devices/pci0000:00/0000:00:10.0/usb2 (usb)	11	KERNEL[130.428945] offline /devices/pci0000:00/0000:00:10.0/usb2 (usb)
12	ACTION=offline	12	ACTION=offline
13	BUSNUM=002	13	BUSNUM=002
14	DEVNAME=/dev/bus/usb/002/001	14	DEVNAME=/dev/bus/usb/002/001
15	DEVNUM=001	15	DEVNUM=001
16	DEVPATH=/devices/pci0000:00/0000:00:10.0/usb2	16	DEVPATH=/devices/pci0000:00/0000:00:10.0/usb2
17	DEVTYPE=usb_device	17	DEVTYPE=usb_device
18	DRIVER=usb	18	DRIVER=usb
19	ERROR=DEAD	19	ERROR=DEAD
20	MAJOR=189	20	MAJOR=189
21	MINOR=128	21	MINOR=128
22	PRODUCT=1d6b/2/414	22	PRODUCT=1d6b/2/414
23	SEQNUM=2168	23	SEQNUM=2168
24	SUBSYSTEM=usb	24	SUBSYSTEM=usb
25	TYPE=9/0/1	25	TYPE=9/0/1
26		26
27	Users: chromium-os-dev@chromium.org	27	Users: chromium-os-dev@chromium.org

Documentation/Kconfig+10−0

@@ -10,4 +10,14 @@ config WARN_MISSING_DOCUMENTS · 9 unmodified lines
10		10
11	If unsure, select 'N'.	11	If unsure, select 'N'.
12		12
		13	config WARN_ABI_ERRORS
		14	bool "Warn if there are errors at ABI files"
		15	depends on COMPILE_TEST
		16	help
		17	The files under Documentation/ABI should follow what's
		18	described at Documentation/ABI/README. Yet, as they're manually
		19	written, it would be possible that some of those files would
		20	have errors that would break them for being parsed by
		21	scripts/get_abi.pl. Add a check to verify them.
13		22
		23	If unsure, select 'N'.

Documentation/Makefile+9−0

 $(shell $(srctree)/scripts/documentation-file-ref-check --warn)
 endif
+# Check for broken ABI files
+ifeq ($(CONFIG_WARN_ABI_ERRORS),y)
+$(shell $(srctree)/scripts/get_abi.pl validate --dir $(srctree)/Documentation/ABI)
+endif
 # You can set these variables from the command line.
 SPHINXBUILD   = sphinx-build
 SPHINXOPTS    =
 PDFLATEX      = xelatex
 LATEXOPTS     = -interaction=batchmode
+ifeq ($(KBUILD_VERBOSE),0)
+SPHINXOPTS    += "-q"
+endif
 # User-friendly check for sphinx-build
 HAVE_SPHINX := $(shell if which $(SPHINXBUILD) >/dev/null 2>&1; then echo 1; else echo 0; fi)

Documentation/admin-guide/LSM/SafeSetID.rst+1−1

@@ -107,7 +107,7 @@ for a UID/GID will prevent that UID/GID from obtaining auxiliary setid · 106 unmodified lines
107	privileges, such as allowing a user to set up user namespace UID/GID mappings.	107	privileges, such as allowing a user to set up user namespace UID/GID mappings.
108		108
109	Note on GID policies and setgroups()	109	Note on GID policies and setgroups()
110	==================	110	====================================
111	In v5.9 we are adding support for limiting CAP_SETGID privileges as was done	111	In v5.9 we are adding support for limiting CAP_SETGID privileges as was done
112	previously for CAP_SETUID. However, for compatibility with common sandboxing	112	previously for CAP_SETUID. However, for compatibility with common sandboxing
113	related code conventions in userspace, we currently allow arbitrary	113	related code conventions in userspace, we currently allow arbitrary

Documentation/admin-guide/abi-obsolete.rst+11−0

@@ -0,0 +1,11 @@
	1	ABI obsolete symbols
	2	====================
	3
	4	Documents interfaces that are still remaining in the kernel, but are
	5	marked to be removed at some later point in time.
	6
	7	The description of the interface will document the reason why it is
	8	obsolete and when it can be expected to be removed.
	9
	10	.. kernel-abi:: $srctree/Documentation/ABI/obsolete
	11	:rst:

Documentation/admin-guide/abi-removed.rst+5−0

@@ -0,0 +1,5 @@
	1	ABI removed symbols
	2	===================
	3
	4	.. kernel-abi:: $srctree/Documentation/ABI/removed
	5	:rst:

Documentation/admin-guide/abi-stable.rst+14−0

@@ -0,0 +1,14 @@
	1	ABI stable symbols
	2	==================
	3
	4	Documents the interfaces that the developer has defined to be stable.
	5
	6	Userspace programs are free to use these interfaces with no
	7	restrictions, and backward compatibility for them will be guaranteed
	8	for at least 2 years.
	9
	10	Most interfaces (like syscalls) are expected to never change and always
	11	be available.
	12
	13	.. kernel-abi:: $srctree/Documentation/ABI/stable
	14	:rst:

Documentation/admin-guide/abi-testing.rst+20−0

@@ -0,0 +1,20 @@
	1	ABI testing symbols
	2	===================
	3
	4	Documents interfaces that are felt to be stable,
	5	as the main development of this interface has been completed.
	6
	7	The interface can be changed to add new features, but the
	8	current interface will not break by doing this, unless grave
	9	errors or security problems are found in them.
	10
	11	Userspace programs can start to rely on these interfaces, but they must
	12	be aware of changes that can occur before these interfaces move to
	13	be marked stable.
	14
	15	Programs that use these interfaces are strongly encouraged to add their
	16	name to the description of these interfaces, so that the kernel
	17	developers can easily notify them if any changes occur.
	18
	19	.. kernel-abi:: $srctree/Documentation/ABI/testing
	20	:rst:

Documentation/admin-guide/abi.rst+11−0

@@ -0,0 +1,11 @@
	1	=====================
	2	Linux ABI description
	3	=====================
	4
	5	.. toctree::
	6	:maxdepth: 2
	7
	8	abi-stable
	9	abi-testing
	10	abi-obsolete
	11	abi-removed

Documentation/admin-guide/index.rst+2−0

@@ -18,6 +18,8 @@ etc. · 17 unmodified lines
18	devices	18	devices
19	sysctl/index	19	sysctl/index
20		20
		21	abi
		22
21	This section describes CPU vulnerabilities and their mitigations.	23	This section describes CPU vulnerabilities and their mitigations.
22		24
23	.. toctree::	25	.. toctree::

Documentation/admin-guide/pm/cpuidle.rst+2−2

@@ -478,7 +478,7 @@ order to ask the hardware to enter that state. Also, for each · 477 unmodified lines
478	statistics of the given idle state. That information is exposed by the kernel	478	statistics of the given idle state. That information is exposed by the kernel
479	via ``sysfs``.	479	via ``sysfs``.
480		480
481	For each CPU in the system, there is a :file:`/sys/devices/system/cpu<N>/cpuidle/`	481	For each CPU in the system, there is a :file:`/sys/devices/system/cpu/cpu<N>/cpuidle/`
482	directory in ``sysfs``, where the number ``<N>`` is assigned to the given	482	directory in ``sysfs``, where the number ``<N>`` is assigned to the given
483	CPU at the initialization time. That directory contains a set of subdirectories	483	CPU at the initialization time. That directory contains a set of subdirectories
484	called :file:`state0`, :file:`state1` and so on, up to the number of idle state	484	called :file:`state0`, :file:`state1` and so on, up to the number of idle state
@@ -494,7 +494,7 @@ object corresponding to it, as follows: · 9 unmodified lines
494	residency.	494	residency.
495		495
496	``below``	496	``below``
497	Total number of times this idle state had been asked for, but cerainly	497	Total number of times this idle state had been asked for, but certainly
498	a deeper idle state would have been a better match for the observed idle	498	a deeper idle state would have been a better match for the observed idle
499	duration.	499	duration.
500		500

Documentation/admin-guide/sysctl/net.rst+1−0

@@ -300,6 +300,7 @@ Note: · 299 unmodified lines
300	0: 0 1 2 3 4 5 6 7	300	0: 0 1 2 3 4 5 6 7
301	RSS hash key:	301	RSS hash key:
302	84:50:f4:00:a8:15:d1:a7:e9:7f:1d:60:35:c7:47:25:42:97:74:ca:56:bb:b6:a1:d8:43:e3:c9:0c:fd:17:55:c2:3a:4d:69:ed:f1:42:89	302	84:50:f4:00:a8:15:d1:a7:e9:7f:1d:60:35:c7:47:25:42:97:74:ca:56:bb:b6:a1:d8:43:e3:c9:0c:fd:17:55:c2:3a:4d:69:ed:f1:42:89
		303
303	netdev_tstamp_prequeue	304	netdev_tstamp_prequeue
304	----------------------	305	----------------------
305		306

Documentation/arm/sunxi.rst+10−0

@@ -148,3 +148,13 @@ SunXi family · 147 unmodified lines
148	* User Manual	148	* User Manual
149		149
150	http://dl.linux-sunxi.org/A64/Allwinner%20A64%20User%20Manual%20v1.0.pdf	150	http://dl.linux-sunxi.org/A64/Allwinner%20A64%20User%20Manual%20v1.0.pdf
		151
		152	- Allwinner H6
		153
		154	* Datasheet
		155
		156	https://linux-sunxi.org/images/5/5c/Allwinner_H6_V200_Datasheet_V1.1.pdf
		157
		158	* User Manual
		159
		160	https://linux-sunxi.org/images/4/46/Allwinner_H6_V200_User_Manual_V1.1.pdf

Documentation/arm64/memory-tagging-extension.rst+3−1

 system call) are not checked if the user thread tag checking mode is
 ``PR_MTE_TCF_NONE`` or ``PR_MTE_TCF_ASYNC``. If the tag checking mode is
 ``PR_MTE_TCF_SYNC``, the kernel makes a best effort to check its user
-address accesses, however it cannot always guarantee it.
+address accesses, however it cannot always guarantee it. Kernel accesses
+to user addresses are always performed with an effective ``PSTATE.TCO``
+value of zero, regardless of the user configuration.
 Excluding Tags in the ``IRG``, ``ADDG`` and ``SUBG`` instructions
 -----------------------------------------------------------------

Documentation/arm64/silicon-errata.rst+2−0

 +----------------+-----------------+-----------------+-----------------------------+
 | ARM            | Cortex-A76      | #1463225        | ARM64_ERRATUM_1463225       |
 +----------------+-----------------+-----------------+-----------------------------+
+| ARM            | Cortex-A77      | #1508412        | ARM64_ERRATUM_1508412       |
++----------------+-----------------+-----------------+-----------------------------+
 | ARM            | Neoverse-N1     | #1188873,1418040| ARM64_ERRATUM_1418040       |
 +----------------+-----------------+-----------------+-----------------------------+
 | ARM            | Neoverse-N1     | #1349291        | N/A                         |

Documentation/conf.py+3−2

 # ones.
 extensions = ['kerneldoc', 'rstFlatTable', 'kernel_include',
               'kfigure', 'sphinx.ext.ifconfig', 'automarkup',
-              'maintainers_include', 'sphinx.ext.autosectionlabel' ]
+              'maintainers_include', 'sphinx.ext.autosectionlabel',
+              'kernel_abi']
 #
 # cdomain is badly broken in Sphinx 3+.  Leaving it out generates *most*
         support for Sphinx v3.0 and above is brand new. Be prepared for
         possible issues in the generated output.
         ''')
-    if minor > 0 or patch >= 2:
+    if (major > 3) or (minor > 0 or patch >= 2):
         # Sphinx c function parser is more pedantic with regards to type
         # checking. Due to that, having macros at c:function cause problems.
         # Those needed to be scaped by using c_id_attributes[] array

Documentation/dev-tools/kasan.rst+2−0

@@ -295,11 +295,13 @@ print the number of the test and the status of the test: · 294 unmodified lines
295	pass::	295	pass::
296		296
297	ok 28 - kmalloc_double_kzfree	297	ok 28 - kmalloc_double_kzfree
		298
298	or, if kmalloc failed::	299	or, if kmalloc failed::
299		300
300	# kmalloc_large_oob_right: ASSERTION FAILED at lib/test_kasan.c:163	301	# kmalloc_large_oob_right: ASSERTION FAILED at lib/test_kasan.c:163
301	Expected ptr is not null, but is	302	Expected ptr is not null, but is
302	not ok 4 - kmalloc_large_oob_right	303	not ok 4 - kmalloc_large_oob_right
		304
303	or, if a KASAN report was expected, but not found::	305	or, if a KASAN report was expected, but not found::
304		306
305	# kmalloc_double_kzfree: EXPECTATION FAILED at lib/test_kasan.c:629	307	# kmalloc_double_kzfree: EXPECTATION FAILED at lib/test_kasan.c:629

Documentation/dev-tools/kunit/start.rst+1−1

@@ -197,7 +197,7 @@ Now add the following to ``drivers/misc/Kconfig``: · 196 unmodified lines
197		197
198	config MISC_EXAMPLE_TEST	198	config MISC_EXAMPLE_TEST
199	bool "Test for my example"	199	bool "Test for my example"
200	depends on MISC_EXAMPLE && KUNIT	200	depends on MISC_EXAMPLE && KUNIT=y
201		201
202	and the following to ``drivers/misc/Makefile``:	202	and the following to ``drivers/misc/Makefile``:
203		203

Documentation/dev-tools/kunit/usage.rst+5−0

@@ -561,6 +561,11 @@ Once the kernel is built and installed, a simple · 560 unmodified lines
561		561
562	...will run the tests.	562	...will run the tests.
563		563
		564	.. note::
		565	Note that you should make sure your test depends on ``KUNIT=y`` in Kconfig
		566	if the test does not support module build. Otherwise, it will trigger
		567	compile errors if ``CONFIG_KUNIT`` is ``m``.
		568
564	Writing new tests for other architectures	569	Writing new tests for other architectures
565	-----------------------------------------	570	-----------------------------------------
566		571

Documentation/devicetree/bindings/clock/hi6220-clock.txt+1−1

@@ -4,7 +4,7 @@ Clock control registers reside in different Hi6220 system controllers, · 3 unmodified lines
4	please refer the following document to know more about the binding rules	4	please refer the following document to know more about the binding rules
5	for these system controllers:	5	for these system controllers:
6		6
7	Documentation/devicetree/bindings/arm/hisilicon/hisilicon.txt	7	Documentation/devicetree/bindings/arm/hisilicon/hisilicon.yaml
8		8
9	Required Properties:	9	Required Properties:
10		10

Documentation/devicetree/bindings/display/panel/mantix,mlaf057we51-x.yaml+4−0

   reset-gpios: true
+  'mantix,tp-rstn-gpios':
+    description: second reset line that triggers DSI config load
   backlight: true
 required:
             avee-supply = <&reg_avee>;
             vddi-supply = <&reg_1v8_p>;
             reset-gpios = <&gpio1 29 GPIO_ACTIVE_LOW>;
+            mantix,tp-rstn-gpios = <&gpio1 24 GPIO_ACTIVE_LOW>;
             backlight = <&backlight>;
         };
     };

Documentation/devicetree/bindings/net/can/can-controller.yaml+18−0

@@ -0,0 +1,18 @@
	1	# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
	2	%YAML 1.2
	3	---
	4	$id: http://devicetree.org/schemas/net/can/can-controller.yaml#
	5	$schema: http://devicetree.org/meta-schemas/core.yaml#
	6
	7	title: CAN Controller Generic Binding
	8
	9	maintainers:
	10	- Marc Kleine-Budde <mkl@pengutronix.de>
	11
	12	properties:
	13	$nodename:
	14	pattern: "^can(@.*)?$"
	15
	16	additionalProperties: true
	17
	18	...

Documentation/devicetree/bindings/net/can/fsl,flexcan.yaml+135−0

@@ -0,0 +1,135 @@
	1	# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
	2	%YAML 1.2
	3	---
	4	$id: http://devicetree.org/schemas/net/can/fsl,flexcan.yaml#
	5	$schema: http://devicetree.org/meta-schemas/core.yaml#
	6
	7	title:
	8	Flexcan CAN controller on Freescale's ARM and PowerPC system-on-a-chip (SOC).
	9
	10	maintainers:
	11	- Marc Kleine-Budde <mkl@pengutronix.de>
	12
	13	allOf:
	14	- $ref: can-controller.yaml#
	15
	16	properties:
	17	compatible:
	18	oneOf:
	19	- enum:
	20	- fsl,imx8qm-flexcan
	21	- fsl,imx8mp-flexcan
	22	- fsl,imx6q-flexcan
	23	- fsl,imx53-flexcan
	24	- fsl,imx35-flexcan
	25	- fsl,imx28-flexcan
	26	- fsl,imx25-flexcan
	27	- fsl,p1010-flexcan
	28	- fsl,vf610-flexcan
	29	- fsl,ls1021ar2-flexcan
	30	- fsl,lx2160ar1-flexcan
	31	- items:
	32	- enum:
	33	- fsl,imx7d-flexcan
	34	- fsl,imx6ul-flexcan
	35	- fsl,imx6sx-flexcan
	36	- const: fsl,imx6q-flexcan
	37	- items:
	38	- enum:
	39	- fsl,ls1028ar1-flexcan
	40	- const: fsl,lx2160ar1-flexcan
	41
	42	reg:
	43	maxItems: 1
	44
	45	interrupts:
	46	maxItems: 1
	47
	48	clocks:
	49	maxItems: 2
	50
	51	clock-names:
	52	items:
	53	- const: ipg
	54	- const: per
	55
	56	clock-frequency:
	57	description: \|
	58	The oscillator frequency driving the flexcan device, filled in by the
	59	boot loader. This property should only be used the used operating system
	60	doesn't support the clocks and clock-names property.
	61
	62	xceiver-supply:
	63	description: Regulator that powers the CAN transceiver.
	64
	65	big-endian:
	66	$ref: /schemas/types.yaml#/definitions/flag
	67	description: \|
	68	This means the registers of FlexCAN controller are big endian. This is
	69	optional property.i.e. if this property is not present in device tree
	70	node then controller is assumed to be little endian. If this property is
	71	present then controller is assumed to be big endian.
	72
	73	fsl,stop-mode:
	74	description: \|
	75	Register bits of stop mode control.
	76
	77	The format should be as follows:
	78	<gpr req_gpr req_bit>
	79	gpr is the phandle to general purpose register node.
	80	req_gpr is the gpr register offset of CAN stop request.
	81	req_bit is the bit offset of CAN stop request.
	82	$ref: /schemas/types.yaml#/definitions/phandle-array
	83	items:
	84	- description: The 'gpr' is the phandle to general purpose register node.
	85	- description: The 'req_gpr' is the gpr register offset of CAN stop request.
	86	maximum: 0xff
	87	- description: The 'req_bit' is the bit offset of CAN stop request.
	88	maximum: 0x1f
	89
	90	fsl,clk-source:
	91	description: \|
	92	Select the clock source to the CAN Protocol Engine (PE). It's SoC
	93	implementation dependent. Refer to RM for detailed definition. If this
	94	property is not set in device tree node then driver selects clock source 1
	95	by default.
	96	0: clock source 0 (oscillator clock)
	97	1: clock source 1 (peripheral clock)
	98	$ref: /schemas/types.yaml#/definitions/uint32
	99	default: 1
	100	minimum: 0
	101	maximum: 1
	102
	103	wakeup-source:
	104	$ref: /schemas/types.yaml#/definitions/flag
	105	description:
	106	Enable CAN remote wakeup.
	107
	108	required:
	109	- compatible
	110	- reg
	111	- interrupts
	112
	113	additionalProperties: false
	114
	115	examples:
	116	- \|
	117	can@1c000 {
	118	compatible = "fsl,p1010-flexcan";
	119	reg = <0x1c000 0x1000>;
	120	interrupts = <48 0x2>;
	121	interrupt-parent = <&mpic>;
	122	clock-frequency = <200000000>;
	123	fsl,clk-source = <0>;
	124	};
	125	- \|
	126	#include <dt-bindings/interrupt-controller/irq.h>
	127
	128	can@2090000 {
	129	compatible = "fsl,imx6q-flexcan";
	130	reg = <0x02090000 0x4000>;
	131	interrupts = <0 110 IRQ_TYPE_LEVEL_HIGH>;
	132	clocks = <&clks 1>, <&clks 2>;
	133	clock-names = "ipg", "per";
	134	fsl,stop-mode = <&gpr 0x34 28>;
	135	};

Documentation/devicetree/bindings/net/can/fsl-flexcan.txt+0−57

@@ -1,57 +0,0 @@
1	Flexcan CAN controller on Freescale's ARM and PowerPC system-on-a-chip (SOC).
2
3	Required properties:
4
5	- compatible : Should be "fsl,<processor>-flexcan"
6
7	where <processor> is imx8qm, imx6q, imx28, imx53, imx35, imx25, p1010,
8	vf610, ls1021ar2, lx2160ar1, ls1028ar1.
9
10	The ls1028ar1 must be followed by lx2160ar1, e.g.
11	- "fsl,ls1028ar1-flexcan", "fsl,lx2160ar1-flexcan"
12
13	An implementation should also claim any of the following compatibles
14	that it is fully backwards compatible with:
15
16	- fsl,p1010-flexcan
17
18	- reg : Offset and length of the register set for this device
19	- interrupts : Interrupt tuple for this device
20
21	Optional properties:
22
23	- clock-frequency : The oscillator frequency driving the flexcan device
24
25	- xceiver-supply: Regulator that powers the CAN transceiver
26
27	- big-endian: This means the registers of FlexCAN controller are big endian.
28	This is optional property.i.e. if this property is not present in
29	device tree node then controller is assumed to be little endian.
30	if this property is present then controller is assumed to be big
31	endian.
32
33	- fsl,stop-mode: register bits of stop mode control, the format is
34	<&gpr req_gpr req_bit>.
35	gpr is the phandle to general purpose register node.
36	req_gpr is the gpr register offset of CAN stop request.
37	req_bit is the bit offset of CAN stop request.
38
39	- fsl,clk-source: Select the clock source to the CAN Protocol Engine (PE).
40	It's SoC Implementation dependent. Refer to RM for detailed
41	definition. If this property is not set in device tree node
42	then driver selects clock source 1 by default.
43	0: clock source 0 (oscillator clock)
44	1: clock source 1 (peripheral clock)
45
46	- wakeup-source: enable CAN remote wakeup
47
48	Example:
49
50	can@1c000 {
51	compatible = "fsl,p1010-flexcan";
52	reg = <0x1c000 0x1000>;
53	interrupts = <48 0x2>;
54	interrupt-parent = <&mpic>;
55	clock-frequency = <200000000>; // filled in by bootloader
56	fsl,clk-source = <0>; // select clock source 0 for PE
57	};

Documentation/devicetree/bindings/sram/allwinner,sun4i-a10-system-control.yaml+3−0

           - const: allwinner,sun4i-a10-system-control
       - const: allwinner,sun8i-a23-system-control
       - const: allwinner,sun8i-h3-system-control
+      - items:
+          - const: allwinner,sun8i-v3s-system-control
+          - const: allwinner,sun8i-h3-system-control
       - items:
           - const: allwinner,sun8i-r40-system-control
           - const: allwinner,sun4i-a10-system-control

Documentation/filesystems/api-summary.rst+0−3

@@ -86,9 +86,6 @@ Other Functions · 85 unmodified lines
86	.. kernel-doc:: fs/dax.c	86	.. kernel-doc:: fs/dax.c
87	:export:	87	:export:
88		88
89	.. kernel-doc:: fs/direct-io.c
90	:export:
91
92	.. kernel-doc:: fs/libfs.c	89	.. kernel-doc:: fs/libfs.c
93	:export:	90	:export:
94		91

Documentation/filesystems/debugfs.rst+1−1

@@ -199,7 +199,7 @@ of its elements. Note: Once array is created its size can not be changed. · 198 unmodified lines
199		199
200	There is a helper function to create device related seq_file::	200	There is a helper function to create device related seq_file::
201		201
202	struct dentry debugfs_create_devm_seqfile(struct device dev,	202	void debugfs_create_devm_seqfile(struct device *dev,
203	const char *name,	203	const char *name,
204	struct dentry *parent,	204	struct dentry *parent,
205	int (read_fn)(struct seq_file s,	205	int (read_fn)(struct seq_file s,

Documentation/gpu/amdgpu.rst+0−7

 ===================
 .. kernel-doc:: drivers/gpu/drm/amd/amdgpu/amdgpu_xgmi.c
-   :doc: AMDGPU XGMI Support
-.. kernel-doc:: drivers/gpu/drm/amd/amdgpu/amdgpu_xgmi.c
-   :internal:
 AMDGPU RAS Support
 ==================
 .. kernel-doc:: drivers/gpu/drm/amd/amdgpu/amdgpu_ras.c
    :doc: AMDGPU RAS sysfs gpu_vram_bad_pages Interface
-.. kernel-doc:: drivers/gpu/drm/amd/amdgpu/amdgpu_ras.c
-   :internal:
 Sample Code
 -----------
 Sample code for testing error injection can be found here:

Documentation/hwmon/adm1266.rst+1−1

@@ -20,7 +20,7 @@ ADM1266 is a sequencer that features voltage readback from 17 channels via an · 19 unmodified lines
20	integrated 12 bit SAR ADC, accessed using a PMBus interface.	20	integrated 12 bit SAR ADC, accessed using a PMBus interface.
21		21
22	The driver is a client driver to the core PMBus driver. Please see	22	The driver is a client driver to the core PMBus driver. Please see
23	Documentation/hwmon/pmbus for details on PMBus client drivers.	23	Documentation/hwmon/pmbus.rst for details on PMBus client drivers.
24		24
25		25
26	Sysfs entries	26	Sysfs entries

Documentation/hwmon/index.rst+1−0

@@ -132,6 +132,7 @@ Hardware Monitoring Kernel Drivers · 131 unmodified lines
132	mcp3021	132	mcp3021
133	menf21bmc	133	menf21bmc
134	mlxreg-fan	134	mlxreg-fan
		135	mp2975
135	nct6683	136	nct6683
136	nct6775	137	nct6775
137	nct7802	138	nct7802

Documentation/hwmon/mp2975.rst+13−1

Documentation/leds/index.rst+1−0

@@ -17,6 +17,7 @@ LEDs · 16 unmodified lines
17	uleds	17	uleds
18		18
19	leds-blinkm	19	leds-blinkm
		20	leds-el15203000
20	leds-lm3556	21	leds-lm3556
21	leds-lp3944	22	leds-lp3944
22	leds-lp5521	23	leds-lp5521

Documentation/leds/leds-el15203000.rst+140−0

@@ -0,0 +1,140 @@
	1	.. SPDX-License-Identifier: GPL-2.0
	2
	3	==================================
	4	Kernel driver for Crane EL15203000
	5	==================================
	6
	7	/sys/class/leds/<led>/hw_pattern
	8	--------------------------------
	9
	10	Specify a hardware pattern for the EL15203000 LED.
	11
	12	The LEDs board supports only predefined patterns by firmware
	13	for specific LEDs.
	14
	15	Breathing mode for Screen frame light tube::
	16
	17	"0 4000 1 4000"
	18
	19	^
	20	\|
	21	Max-\| ---
	22	\| / \
	23	\| / \
	24	\| / \ /
	25	\| / \ /
	26	Min-\|- ---
	27	\|
	28	0------4------8--> time (sec)
	29
	30	Cascade mode for Pipe LED::
	31
	32	"1 800 2 800 4 800 8 800 16 800"
	33
	34	^
	35	\|
	36	0 On -\|----+ +----+ +---
	37	\| \| \| \| \|
	38	Off-\| +-------------------+ +-------------------+
	39	\|
	40	1 On -\| +----+ +----+
	41	\| \| \| \| \|
	42	Off \|----+ +-------------------+ +------------------
	43	\|
	44	2 On -\| +----+ +----+
	45	\| \| \| \| \|
	46	Off-\|---------+ +-------------------+ +-------------
	47	\|
	48	3 On -\| +----+ +----+
	49	\| \| \| \| \|
	50	Off-\|--------------+ +-------------------+ +--------
	51	\|
	52	4 On -\| +----+ +----+
	53	\| \| \| \| \|
	54	Off-\|-------------------+ +-------------------+ +---
	55	\|
	56	0---0.8--1.6--2.4--3.2---4---4.8--5.6--6.4--7.2---8--> time (sec)
	57
	58	Inverted cascade mode for Pipe LED::
	59
	60	"30 800 29 800 27 800 23 800 15 800"
	61
	62	^
	63	\|
	64	0 On -\| +-------------------+ +-------------------+
	65	\| \| \| \| \|
	66	Off-\|----+ +----+ +---
	67	\|
	68	1 On -\|----+ +-------------------+ +------------------
	69	\| \| \| \| \|
	70	Off \| +----+ +----+
	71	\|
	72	2 On -\|---------+ +-------------------+ +-------------
	73	\| \| \| \| \|
	74	Off-\| +----+ +----+
	75	\|
	76	3 On -\|--------------+ +-------------------+ +--------
	77	\| \| \| \| \|
	78	Off-\| +----+ +----+
	79	\|
	80	4 On -\|-------------------+ +-------------------+ +---
	81	\| \| \| \| \|
	82	Off-\| +----+ +----+
	83	\|
	84	0---0.8--1.6--2.4--3.2---4---4.8--5.6--6.4--7.2---8--> time (sec)
	85
	86	Bounce mode for Pipe LED::
	87
	88	"1 800 2 800 4 800 8 800 16 800 16 800 8 800 4 800 2 800 1 800"
	89
	90	^
	91	\|
	92	0 On -\|----+ +--------
	93	\| \| \|
	94	Off-\| +---------------------------------------+
	95	\|
	96	1 On -\| +----+ +----+
	97	\| \| \| \| \|
	98	Off \|----+ +-----------------------------+ +--------
	99	\|
	100	2 On -\| +----+ +----+
	101	\| \| \| \| \|
	102	Off-\|---------+ +-------------------+ +-------------
	103	\|
	104	3 On -\| +----+ +----+
	105	\| \| \| \| \|
	106	Off-\|--------------+ +---------+ +------------------
	107	\|
	108	4 On -\| +---------+
	109	\| \| \|
	110	Off-\|-------------------+ +-----------------------
	111	\|
	112	0---0.8--1.6--2.4--3.2---4---4.8--5.6--6.4--7.2---8--> time (sec)
	113
	114	Inverted bounce mode for Pipe LED::
	115
	116	"30 800 29 800 27 800 23 800 15 800 15 800 23 800 27 800 29 800 30 800"
	117
	118	^
	119	\|
	120	0 On -\| +---------------------------------------+
	121	\| \| \|
	122	Off-\|----+ +--------
	123	\|
	124	1 On -\|----+ +-----------------------------+ +--------
	125	\| \| \| \| \|
	126	Off \| +----+ +----+
	127	\|
	128	2 On -\|---------+ +-------------------+ +-------------
	129	\| \| \| \| \|
	130	Off-\| +----+ +----+
	131	\|
	132	3 On -\|--------------+ +---------+ +------------------
	133	\| \| \| \| \|
	134	Off-\| +----+ +----+
	135	\|
	136	4 On -\|-------------------+ +-----------------------
	137	\| \| \|
	138	Off-\| +---------+
	139	\|
	140	0---0.8--1.6--2.4--3.2---4---4.8--5.6--6.4--7.2---8--> time (sec)

Documentation/leds/leds-sc27xx.rst+27−0

@@ -0,0 +1,27 @@
	1	.. SPDX-License-Identifier: GPL-2.0
	2
	3	===================================
	4	Kernel driver for Spreadtrum SC27XX
	5	===================================
	6
	7	/sys/class/leds/<led>/hw_pattern
	8	--------------------------------
	9
	10	Specify a hardware pattern for the SC27XX LED. For the SC27XX
	11	LED controller, it only supports 4 stages to make a single
	12	hardware pattern, which is used to configure the rise time,
	13	high time, fall time and low time for the breathing mode.
	14
	15	For the breathing mode, the SC27XX LED only expects one brightness
	16	for the high stage. To be compatible with the hardware pattern
	17	format, we should set brightness as 0 for rise stage, fall
	18	stage and low stage.
	19
	20	- Min stage duration: 125 ms
	21	- Max stage duration: 31875 ms
	22
	23	Since the stage duration step is 125 ms, the duration should be
	24	a multiplier of 125, like 125ms, 250ms, 375ms, 500ms ... 31875ms.
	25
	26	Thus the format of the hardware pattern values should be:
	27	"0 rise_duration brightness high_duration 0 fall_duration 0 low_duration".

Documentation/locking/lockdep-design.rst+31−20

 (4 usages * n STATEs + 1) categories:
 where the 4 usages can be:
 - 'ever held in STATE context'
 - 'ever held as readlock in STATE context'
 - 'ever held with STATE enabled'
 where the n STATEs are coded in kernel/locking/lockdep_states.h and as of
 now they include:
 - hardirq
 - softirq
 where the last 1 category is:
 - 'ever used'                                       [ == !unused        ]
 When locking rules are violated, these usage bits are presented in the
   +--------------+-------------+--------------+
   |              | irq enabled | irq disabled |
   +--------------+-------------+--------------+
-  | ever in irq  |      ?      |       -      |
+  | ever in irq  |     '?'     |      '-'     |
   +--------------+-------------+--------------+
-  | never in irq |      +      |       .      |
+  | never in irq |     '+'     |      '.'     |
   +--------------+-------------+--------------+
 The character '-' suggests irq is disabled because if otherwise the
        BD_MUTEX_PARTITION
   };
-mutex_lock_nested(&bdev->bd_contains->bd_mutex, BD_MUTEX_PARTITION);
+  mutex_lock_nested(&bdev->bd_contains->bd_mutex, BD_MUTEX_PARTITION);
 In this case the locking is done on a bdev object that is known to be a
 partition.
 ----------------
 The validator tracks a maximum of MAX_LOCKDEP_KEYS number of lock classes.
-Exceeding this number will trigger the following lockdep warning:
+Exceeding this number will trigger the following lockdep warning::
 	(DEBUG_LOCKS_WARN_ON(id >= MAX_LOCKDEP_KEYS))
 The difference between recursive readers and non-recursive readers is because:
 recursive readers get blocked only by a write lock *holder*, while non-recursive
-readers could get blocked by a write lock *waiter*. Considering the follow example:
+readers could get blocked by a write lock *waiter*. Considering the follow
+example::
 	TASK A:			TASK B:
 Block condition matrix, Y means the row blocks the column, and N means otherwise.
-	    | E | r | R |
 	+---+---+---+---+
-	  E | Y | Y | Y |
+	|   | E | r | R |
+	+---+---+---+---+
+	| E | Y | Y | Y |
+	+---+---+---+---+
+	| r | Y | Y | N |
 	+---+---+---+---+
-	  r | Y | Y | N |
+	| R | Y | Y | N |
 	+---+---+---+---+
-	  R | Y | Y | N |
 	(W: writers, r: non-recursive readers, R: recursive readers)
 acquired recursively. Unlike non-recursive read locks, recursive read locks
 only get blocked by current write lock *holders* other than write lock
-*waiters*, for example:
+*waiters*, for example::
 	TASK A:			TASK B:
 even true for two non-recursive read locks). A non-recursive lock can block the
 corresponding recursive lock, and vice versa.
-A deadlock case with recursive locks involved is as follow:
+A deadlock case with recursive locks involved is as follow::
 	TASK A:			TASK B:
 dependencies, but we can show that 4 types of lock dependencies are enough for
 deadlock detection.
-For each lock dependency:
+For each lock dependency::
 	L1 -> L2
 With the above combination for simplification, there are 4 types of dependency edges
 in the lockdep graph:
-1) -(ER)->: exclusive writer to recursive reader dependency, "X -(ER)-> Y" means
+1) -(ER)->:
+	    exclusive writer to recursive reader dependency, "X -(ER)-> Y" means
 	    X -> Y and X is a writer and Y is a recursive reader.
-2) -(EN)->: exclusive writer to non-recursive locker dependency, "X -(EN)-> Y" means
+2) -(EN)->:
+	    exclusive writer to non-recursive locker dependency, "X -(EN)-> Y" means
 	    X -> Y and X is a writer and Y is either a writer or non-recursive reader.
-3) -(SR)->: shared reader to recursive reader dependency, "X -(SR)-> Y" means
+3) -(SR)->:
+	    shared reader to recursive reader dependency, "X -(SR)-> Y" means
 	    X -> Y and X is a reader (recursive or not) and Y is a recursive reader.
-4) -(SN)->: shared reader to non-recursive locker dependency, "X -(SN)-> Y" means
+4) -(SN)->:
+	    shared reader to non-recursive locker dependency, "X -(SN)-> Y" means
 	    X -> Y and X is a reader (recursive or not) and Y is either a writer or
 	    non-recursive reader.
-Note that given two locks, they may have multiple dependencies between them, for example:
+Note that given two locks, they may have multiple dependencies between them,
+for example::
 	TASK A:
 Proof for sufficiency (Lemma 1):
-Let's say we have a strong circle:
+Let's say we have a strong circle::
 	L1 -> L2 ... -> Ln -> L1
-, which means we have dependencies:
+, which means we have dependencies::
 	L1 -> L2
 	L2 -> L3
 for a lock held by P1. Let's name the lock Px is waiting as Lx, so since P1 is waiting
 for L1 and holding Ln, so we will have Ln -> L1 in the dependency graph. Similarly,
 we have L1 -> L2, L2 -> L3, ..., Ln-1 -> Ln in the dependency graph, which means we
-have a circle:
+have a circle::
 	Ln -> L1 -> L2 -> ... -> Ln

Documentation/misc-devices/mic/index.rst+0−16

@@ -1,16 +0,0 @@
1	=============================================
2	Intel Many Integrated Core (MIC) architecture
3	=============================================
4
5	.. toctree::
6	:maxdepth: 1
7
8	mic_overview
9	scif_overview
10
11	.. only:: subproject and html
12
13	Indices
14	=======
15
16	* :ref:`genindex`

Documentation/misc-devices/mic/mic_overview.rst+0−85

@@ -1,85 +0,0 @@
1	======================================================
2	Intel Many Integrated Core (MIC) architecture overview
3	======================================================
4
5	An Intel MIC X100 device is a PCIe form factor add-in coprocessor
6	card based on the Intel Many Integrated Core (MIC) architecture
7	that runs a Linux OS. It is a PCIe endpoint in a platform and therefore
8	implements the three required standard address spaces i.e. configuration,
9	memory and I/O. The host OS loads a device driver as is typical for
10	PCIe devices. The card itself runs a bootstrap after reset that
11	transfers control to the card OS downloaded from the host driver. The
12	host driver supports OSPM suspend and resume operations. It shuts down
13	the card during suspend and reboots the card OS during resume.
14	The card OS as shipped by Intel is a Linux kernel with modifications
15	for the X100 devices.
16
17	Since it is a PCIe card, it does not have the ability to host hardware
18	devices for networking, storage and console. We provide these devices
19	on X100 coprocessors thus enabling a self-bootable equivalent
20	environment for applications. A key benefit of our solution is that it
21	leverages the standard virtio framework for network, disk and console
22	devices, though in our case the virtio framework is used across a PCIe
23	bus. A Virtio Over PCIe (VOP) driver allows creating user space
24	backends or devices on the host which are used to probe virtio drivers
25	for these devices on the MIC card. The existing VRINGH infrastructure
26	in the kernel is used to access virtio rings from the host. The card
27	VOP driver allows card virtio drivers to communicate with their user
28	space backends on the host via a device page. Ring 3 apps on the host
29	can add, remove and configure virtio devices. A thin MIC specific
30	virtio_config_ops is implemented which is borrowed heavily from
31	previous similar implementations in lguest and s390.
32
33	MIC PCIe card has a dma controller with 8 channels. These channels are
34	shared between the host s/w and the card s/w. 0 to 3 are used by host
35	and 4 to 7 by card. As the dma device doesn't show up as PCIe device,
36	a virtual bus called mic bus is created and virtual dma devices are
37	created on it by the host/card drivers. On host the channels are private
38	and used only by the host driver to transfer data for the virtio devices.
39
40	The Symmetric Communication Interface (SCIF (pronounced as skiff)) is a
41	low level communications API across PCIe currently implemented for MIC.
42	More details are available at scif_overview.txt.
43
44	The Coprocessor State Management (COSM) driver on the host allows for
45	boot, shutdown and reset of Intel MIC devices. It communicates with a COSM
46	"client" driver on the MIC cards over SCIF to perform these functions.
47
48	Here is a block diagram of the various components described above. The
49	virtio backends are situated on the host rather than the card given better
50	single threaded performance for the host compared to MIC, the ability of
51	the host to initiate DMA's to/from the card using the MIC DMA engine and
52	the fact that the virtio block storage backend can only be on the host::
53
54	+----------+ \| +----------+
55	\| Card OS \| \| \| Host OS \|
56	+----------+ \| +----------+
57	\|
58	+-------+ +--------+ +------+ \| +---------+ +--------+ +--------+
59	\| Virtio\| \|Virtio \| \|Virtio\| \| \|Virtio \| \|Virtio \| \|Virtio \|
60	\| Net \| \|Console \| \|Block \| \| \|Net \| \|Console \| \|Block \|
61	\| Driver\| \|Driver \| \|Driver\| \| \|backend \| \|backend \| \|backend \|
62	+---+---+ +---+----+ +--+---+ \| +---------+ +----+---+ +--------+
63	\| \| \| \| \| \| \|
64	\| \| \| \|User \| \| \|
65	\| \| \| \|------\|------------\|--+------\|-------
66	+---------+---------+ \|Kernel \|
67	\| \| \|
68	+---------+ +---+----+ +------+ \| +------+ +------+ +--+---+ +-------+
69	\|MIC DMA \| \| VOP \| \| SCIF \| \| \| SCIF \| \| COSM \| \| VOP \| \|MIC DMA\|
70	+---+-----+ +---+----+ +--+---+ \| +--+---+ +--+---+ +------+ +----+--+
71	\| \| \| \| \| \| \|
72	+---+-----+ +---+----+ +--+---+ \| +--+---+ +--+---+ +------+ +----+--+
73	\|MIC \| \| VOP \| \|SCIF \| \| \|SCIF \| \| COSM \| \| VOP \| \| MIC \|
74	\|HW Bus \| \| HW Bus\| \|HW Bus\| \| \|HW Bus\| \| Bus \| \|HW Bus\| \|HW Bus \|
75	+---------+ +--------+ +--+---+ \| +--+---+ +------+ +------+ +-------+
76	\| \| \| \| \| \| \|
77	\| +-----------+--+ \| \| \| +---------------+ \|
78	\| \|Intel MIC \| \| \| \| \|Intel MIC \| \|
79	\| \|Card Driver \| \| \| \| \|Host Driver \| \|
80	+---+--------------+------+ \| +----+---------------+-----+
81	\| \| \|
82	+-------------------------------------------------------------+
83	\| \|
84	\| PCIe Bus \|
85	+-------------------------------------------------------------+

Documentation/misc-devices/mic/scif_overview.rst+0−108

@@ -1,108 +0,0 @@
1	========================================
2	Symmetric Communication Interface (SCIF)
3	========================================
4
5	The Symmetric Communication Interface (SCIF (pronounced as skiff)) is a low
6	level communications API across PCIe currently implemented for MIC. Currently
7	SCIF provides inter-node communication within a single host platform, where a
8	node is a MIC Coprocessor or Xeon based host. SCIF abstracts the details of
9	communicating over the PCIe bus while providing an API that is symmetric
10	across all the nodes in the PCIe network. An important design objective for SCIF
11	is to deliver the maximum possible performance given the communication
12	abilities of the hardware. SCIF has been used to implement an offload compiler
13	runtime and OFED support for MPI implementations for MIC coprocessors.
14
15	SCIF API Components
16	===================
17
18	The SCIF API has the following parts:
19
20	1. Connection establishment using a client server model
21	2. Byte stream messaging intended for short messages
22	3. Node enumeration to determine online nodes
23	4. Poll semantics for detection of incoming connections and messages
24	5. Memory registration to pin down pages
25	6. Remote memory mapping for low latency CPU accesses via mmap
26	7. Remote DMA (RDMA) for high bandwidth DMA transfers
27	8. Fence APIs for RDMA synchronization
28
29	SCIF exposes the notion of a connection which can be used by peer processes on
30	nodes in a SCIF PCIe "network" to share memory "windows" and to communicate. A
31	process in a SCIF node initiates a SCIF connection to a peer process on a
32	different node via a SCIF "endpoint". SCIF endpoints support messaging APIs
33	which are similar to connection oriented socket APIs. Connected SCIF endpoints
34	can also register local memory which is followed by data transfer using either
35	DMA, CPU copies or remote memory mapping via mmap. SCIF supports both user and
36	kernel mode clients which are functionally equivalent.
37
38	SCIF Performance for MIC
39	========================
40
41	DMA bandwidth comparison between the TCP (over ethernet over PCIe) stack versus
42	SCIF shows the performance advantages of SCIF for HPC applications and
43	runtimes::
44
45	Comparison of TCP and SCIF based BW
46
47	Throughput (GB/sec)
48	8 + PCIe Bandwidth ******
49	+ TCP ######
50	7 + ************************************** SCIF %%%%%%
51	\| %%%%%%%%%%%%%%%%%%%
52	6 + %%%%
53	\| %%
54	\| %%%
55	5 + %%
56	\| %%
57	4 + %%
58	\| %%
59	3 + %%
60	\| %
61	2 + %%
62	\| %%
63	\| %
64	1 +
65	+ ######################################
66	0 +++---+++--+--+-+--+--+-++-+--+-++-+--+-++-+-
67	1 10 100 1000 10000 100000
68	Transfer Size (KBytes)
69
70	SCIF allows memory sharing via mmap(..) between processes on different PCIe
71	nodes and thus provides bare-metal PCIe latency. The round trip SCIF mmap
72	latency from the host to an x100 MIC for an 8 byte message is 0.44 usecs.
73
74	SCIF has a user space library which is a thin IOCTL wrapper providing a user
75	space API similar to the kernel API in scif.h. The SCIF user space library
76	is distributed @ https://software.intel.com/en-us/mic-developer
77
78	Here is some pseudo code for an example of how two applications on two PCIe
79	nodes would typically use the SCIF API::
80
81	Process A (on node A) Process B (on node B)
82
83	/* get online node information */
84	scif_get_node_ids(..) scif_get_node_ids(..)
85	scif_open(..) scif_open(..)
86	scif_bind(..) scif_bind(..)
87	scif_listen(..)
88	scif_accept(..) scif_connect(..)
89	/* SCIF connection established */
90
91	/* Send and receive short messages */
92	scif_send(..)/scif_recv(..) scif_send(..)/scif_recv(..)
93
94	/* Register memory */
95	scif_register(..) scif_register(..)
96
97	/* RDMA */
98	scif_readfrom(..)/scif_writeto(..) scif_readfrom(..)/scif_writeto(..)
99
100	/* Fence DMAs */
101	scif_fence_signal(..) scif_fence_signal(..)
102
103	mmap(..) mmap(..)
104
105	/* Access remote registered memory */
106
107	/* Close the endpoints */
108	scif_close(..) scif_close(..)

Documentation/networking/devlink/ice.rst+1−0

@@ -70,6 +70,7 @@ The ``ice`` driver reports the following versions · 69 unmodified lines
70	that both the name (as reported by ``fw.app.name``) and version are	70	that both the name (as reported by ``fw.app.name``) and version are
71	required to uniquely identify the package.	71	required to uniquely identify the package.
72	* - ``fw.app.bundle_id``	72	* - ``fw.app.bundle_id``
		73	- running
73	- 0xc0000001	74	- 0xc0000001
74	- Unique identifier for the DDP package loaded in the device. Also	75	- Unique identifier for the DDP package loaded in the device. Also
75	referred to as the DDP Track ID. Can be used to uniquely identify	76	referred to as the DDP Track ID. Can be used to uniquely identify

Documentation/networking/j1939.rst+60−60

@@ -10,9 +10,9 @@ Overview / What Is J1939 · 9 unmodified lines
10	SAE J1939 defines a higher layer protocol on CAN. It implements a more	10	SAE J1939 defines a higher layer protocol on CAN. It implements a more
11	sophisticated addressing scheme and extends the maximum packet size above 8	11	sophisticated addressing scheme and extends the maximum packet size above 8
12	bytes. Several derived specifications exist, which differ from the original	12	bytes. Several derived specifications exist, which differ from the original
13	J1939 on the application level, like MilCAN A, NMEA2000 and especially	13	J1939 on the application level, like MilCAN A, NMEA2000, and especially
14	ISO-11783 (ISOBUS). This last one specifies the so-called ETP (Extended	14	ISO-11783 (ISOBUS). This last one specifies the so-called ETP (Extended
15	Transport Protocol) which is has been included in this implementation. This	15	Transport Protocol), which has been included in this implementation. This
16	results in a maximum packet size of ((2 ^ 24) - 1) * 7 bytes == 111 MiB.	16	results in a maximum packet size of ((2 ^ 24) - 1) * 7 bytes == 111 MiB.
17		17
18	Specifications used	18	Specifications used
@@ -32,15 +32,15 @@ sockets, we found some reasons to justify a kernel implementation for the · 13 unmodified lines
32	addressing and transport methods used by J1939.	32	addressing and transport methods used by J1939.
33		33
34	* Addressing: when a process on an ECU communicates via J1939, it should	34	* Addressing: when a process on an ECU communicates via J1939, it should
35	not necessarily know its source address. Although at least one process per	35	not necessarily know its source address. Although, at least one process per
36	ECU should know the source address. Other processes should be able to reuse	36	ECU should know the source address. Other processes should be able to reuse
37	that address. This way, address parameters for different processes	37	that address. This way, address parameters for different processes
38	cooperating for the same ECU, are not duplicated. This way of working is	38	cooperating for the same ECU, are not duplicated. This way of working is
39	closely related to the UNIX concept where programs do just one thing, and do	39	closely related to the UNIX concept, where programs do just one thing and do
40	it well.	40	it well.
41		41
42	* Dynamic addressing: Address Claiming in J1939 is time critical.	42	* Dynamic addressing: Address Claiming in J1939 is time critical.
43	Furthermore data transport should be handled properly during the address	43	Furthermore, data transport should be handled properly during the address
44	negotiation. Putting this functionality in the kernel eliminates it as a	44	negotiation. Putting this functionality in the kernel eliminates it as a
45	requirement for _every_ user space process that communicates via J1939. This	45	requirement for _every_ user space process that communicates via J1939. This
46	results in a consistent J1939 bus with proper addressing.	46	results in a consistent J1939 bus with proper addressing.
@@ -58,7 +58,7 @@ Therefore, these parts are left to user space. · 11 unmodified lines
58		58
59	The J1939 sockets operate on CAN network devices (see SocketCAN). Any J1939	59	The J1939 sockets operate on CAN network devices (see SocketCAN). Any J1939
60	user space library operating on CAN raw sockets will still operate properly.	60	user space library operating on CAN raw sockets will still operate properly.
61	Since such library does not communicate with the in-kernel implementation, care	61	Since such a library does not communicate with the in-kernel implementation, care
62	must be taken that these two do not interfere. In practice, this means they	62	must be taken that these two do not interfere. In practice, this means they
63	cannot share ECU addresses. A single ECU (or virtual ECU) address is used by	63	cannot share ECU addresses. A single ECU (or virtual ECU) address is used by
64	the library exclusively, or by the in-kernel system exclusively.	64	the library exclusively, or by the in-kernel system exclusively.
@@ -77,13 +77,13 @@ is composed as follows: · 12 unmodified lines
77	8 bits : PS (PDU Specific)	77	8 bits : PS (PDU Specific)
78		78
79	In J1939-21 distinction is made between PDU1 format (where PF < 240) and PDU2	79	In J1939-21 distinction is made between PDU1 format (where PF < 240) and PDU2
80	format (where PF >= 240). Furthermore, when using PDU2 format, the PS-field	80	format (where PF >= 240). Furthermore, when using the PDU2 format, the PS-field
81	contains a so-called Group Extension, which is part of the PGN. When using PDU2	81	contains a so-called Group Extension, which is part of the PGN. When using PDU2
82	format, the Group Extension is set in the PS-field.	82	format, the Group Extension is set in the PS-field.
83		83
84	On the other hand, when using PDU1 format, the PS-field contains a so-called	84	On the other hand, when using PDU1 format, the PS-field contains a so-called
85	Destination Address, which is _not_ part of the PGN. When communicating a PGN	85	Destination Address, which is _not_ part of the PGN. When communicating a PGN
86	from user space to kernel (or visa versa) and PDU2 format is used, the PS-field	86	from user space to kernel (or vice versa) and PDU2 format is used, the PS-field
87	of the PGN shall be set to zero. The Destination Address shall be set	87	of the PGN shall be set to zero. The Destination Address shall be set
88	elsewhere.	88	elsewhere.
89		89
@@ -96,15 +96,15 @@ Addressing · 6 unmodified lines
96		96
97	Both static and dynamic addressing methods can be used.	97	Both static and dynamic addressing methods can be used.
98		98
99	For static addresses, no extra checks are made by the kernel, and provided	99	For static addresses, no extra checks are made by the kernel and provided
100	addresses are considered right. This responsibility is for the OEM or system	100	addresses are considered right. This responsibility is for the OEM or system
101	integrator.	101	integrator.
102		102
103	For dynamic addressing, so-called Address Claiming, extra support is foreseen	103	For dynamic addressing, so-called Address Claiming, extra support is foreseen
104	in the kernel. In J1939 any ECU is known by it's 64-bit NAME. At the moment of	104	in the kernel. In J1939 any ECU is known by its 64-bit NAME. At the moment of
105	a successful address claim, the kernel keeps track of both NAME and source	105	a successful address claim, the kernel keeps track of both NAME and source
106	address being claimed. This serves as a base for filter schemes. By default,	106	address being claimed. This serves as a base for filter schemes. By default,
107	packets with a destination that is not locally, will be rejected.	107	packets with a destination that is not locally will be rejected.
108		108
109	Mixed mode packets (from a static to a dynamic address or vice versa) are	109	Mixed mode packets (from a static to a dynamic address or vice versa) are
110	allowed. The BSD sockets define separate API calls for getting/setting the	110	allowed. The BSD sockets define separate API calls for getting/setting the
@@ -131,31 +131,31 @@ API Calls · 20 unmodified lines
131	---------	131	---------
132		132
133	On CAN, you first need to open a socket for communicating over a CAN network.	133	On CAN, you first need to open a socket for communicating over a CAN network.
134	To use J1939, #include <linux/can/j1939.h>. From there, <linux/can.h> will be	134	To use J1939, ``#include <linux/can/j1939.h>``. From there, ``<linux/can.h>`` will be
135	included too. To open a socket, use:	135	included too. To open a socket, use:
136		136
137	.. code-block:: C	137	.. code-block:: C
138		138
139	s = socket(PF_CAN, SOCK_DGRAM, CAN_J1939);	139	s = socket(PF_CAN, SOCK_DGRAM, CAN_J1939);
140		140
141	J1939 does use SOCK_DGRAM sockets. In the J1939 specification, connections are	141	J1939 does use ``SOCK_DGRAM`` sockets. In the J1939 specification, connections are
142	mentioned in the context of transport protocol sessions. These still deliver	142	mentioned in the context of transport protocol sessions. These still deliver
143	packets to the other end (using several CAN packets). SOCK_STREAM is not	143	packets to the other end (using several CAN packets). ``SOCK_STREAM`` is not
144	supported.	144	supported.
145		145
146	After the successful creation of the socket, you would normally use the bind(2)	146	After the successful creation of the socket, you would normally use the ``bind(2)``
147	and/or connect(2) system call to bind the socket to a CAN interface. After	147	and/or ``connect(2)`` system call to bind the socket to a CAN interface. After
148	binding and/or connecting the socket, you can read(2) and write(2) from/to the	148	binding and/or connecting the socket, you can ``read(2)`` and ``write(2)`` from/to the
149	socket or use send(2), sendto(2), sendmsg(2) and the recv*() counterpart	149	socket or use ``send(2)``, ``sendto(2)``, ``sendmsg(2)`` and the ``recv*()`` counterpart
150	operations on the socket as usual. There are also J1939 specific socket options	150	operations on the socket as usual. There are also J1939 specific socket options
151	described below.	151	described below.
152		152
153	In order to send data, a bind(2) must have been successful. bind(2) assigns a	153	In order to send data, a ``bind(2)`` must have been successful. ``bind(2)`` assigns a
154	local address to a socket.	154	local address to a socket.
155		155
156	Different from CAN is that the payload data is just the data that get send,	156	Different from CAN is that the payload data is just the data that get sends,
157	without it's header info. The header info is derived from the sockaddr supplied	157	without its header info. The header info is derived from the sockaddr supplied
158	to bind(2), connect(2), sendto(2) and recvfrom(2). A write(2) with size 4 will	158	to ``bind(2)``, ``connect(2)``, ``sendto(2)`` and ``recvfrom(2)``. A ``write(2)`` with size 4 will
159	result in a packet with 4 bytes.	159	result in a packet with 4 bytes.
160		160
161	The sockaddr structure has extensions for use with J1939 as specified below:	161	The sockaddr structure has extensions for use with J1939 as specified below:
@@ -180,47 +180,47 @@ The sockaddr structure has extensions for use with J1939 as specified below: · 18 unmodified lines
180	} can_addr;	180	} can_addr;
181	}	181	}
182		182
183	can_family & can_ifindex serve the same purpose as for other SocketCAN sockets.	183	``can_family`` & ``can_ifindex`` serve the same purpose as for other SocketCAN sockets.
184		184
185	can_addr.j1939.pgn specifies the PGN (max 0x3ffff). Individual bits are	185	``can_addr.j1939.pgn`` specifies the PGN (max 0x3ffff). Individual bits are
186	specified above.	186	specified above.
187		187
188	can_addr.j1939.name contains the 64-bit J1939 NAME.	188	``can_addr.j1939.name`` contains the 64-bit J1939 NAME.
189		189
190	can_addr.j1939.addr contains the address.	190	``can_addr.j1939.addr`` contains the address.
191		191
192	The bind(2) system call assigns the local address, i.e. the source address when	192	The ``bind(2)`` system call assigns the local address, i.e. the source address when
193	sending packages. If a PGN during bind(2) is set, it's used as a RX filter.	193	sending packages. If a PGN during ``bind(2)`` is set, it's used as a RX filter.
194	I.e. only packets with a matching PGN are received. If an ADDR or NAME is set	194	I.e. only packets with a matching PGN are received. If an ADDR or NAME is set
195	it is used as a receive filter, too. It will match the destination NAME or ADDR	195	it is used as a receive filter, too. It will match the destination NAME or ADDR
196	of the incoming packet. The NAME filter will work only if appropriate Address	196	of the incoming packet. The NAME filter will work only if appropriate Address
197	Claiming for this name was done on the CAN bus and registered/cached by the	197	Claiming for this name was done on the CAN bus and registered/cached by the
198	kernel.	198	kernel.
199		199
200	On the other hand connect(2) assigns the remote address, i.e. the destination	200	On the other hand ``connect(2)`` assigns the remote address, i.e. the destination
201	address. The PGN from connect(2) is used as the default PGN when sending	201	address. The PGN from ``connect(2)`` is used as the default PGN when sending
202	packets. If ADDR or NAME is set it will be used as the default destination ADDR	202	packets. If ADDR or NAME is set it will be used as the default destination ADDR
203	or NAME. Further a set ADDR or NAME during connect(2) is used as a receive	203	or NAME. Further a set ADDR or NAME during ``connect(2)`` is used as a receive
204	filter. It will match the source NAME or ADDR of the incoming packet.	204	filter. It will match the source NAME or ADDR of the incoming packet.
205		205
206	Both write(2) and send(2) will send a packet with local address from bind(2) and	206	Both ``write(2)`` and ``send(2)`` will send a packet with local address from ``bind(2)`` and the
207	the remote address from connect(2). Use sendto(2) to overwrite the destination	207	remote address from ``connect(2)``. Use ``sendto(2)`` to overwrite the destination
208	address.	208	address.
209		209
210	If can_addr.j1939.name is set (!= 0) the NAME is looked up by the kernel and	210	If ``can_addr.j1939.name`` is set (!= 0) the NAME is looked up by the kernel and
211	the corresponding ADDR is used. If can_addr.j1939.name is not set (== 0),	211	the corresponding ADDR is used. If ``can_addr.j1939.name`` is not set (== 0),
212	can_addr.j1939.addr is used.	212	``can_addr.j1939.addr`` is used.
213		213
214	When creating a socket, reasonable defaults are set. Some options can be	214	When creating a socket, reasonable defaults are set. Some options can be
215	modified with setsockopt(2) & getsockopt(2).	215	modified with ``setsockopt(2)`` & ``getsockopt(2)``.
216		216
217	RX path related options:	217	RX path related options:
218		218
219	- SO_J1939_FILTER - configure array of filters	219	- ``SO_J1939_FILTER`` - configure array of filters
220	- SO_J1939_PROMISC - disable filters set by bind(2) and connect(2)	220	- ``SO_J1939_PROMISC`` - disable filters set by ``bind(2)`` and ``connect(2)``
221		221
222	By default no broadcast packets can be send or received. To enable sending or	222	By default no broadcast packets can be send or received. To enable sending or
223	receiving broadcast packets use the socket option SO_BROADCAST:	223	receiving broadcast packets use the socket option ``SO_BROADCAST``:
224		224
225	.. code-block:: C	225	.. code-block:: C
226		226
@@ -261,26 +261,26 @@ The following diagram illustrates the RX path: · 34 unmodified lines
261	+---------------------------+	261	+---------------------------+
262		262
263	TX path related options:	263	TX path related options:
264	SO_J1939_SEND_PRIO - change default send priority for the socket	264	``SO_J1939_SEND_PRIO`` - change default send priority for the socket
265		265
266	Message Flags during send() and Related System Calls	266	Message Flags during send() and Related System Calls
267	^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^	267	^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
268		268
269	send(2), sendto(2) and sendmsg(2) take a 'flags' argument. Currently	269	``send(2)``, ``sendto(2)`` and ``sendmsg(2)`` take a 'flags' argument. Currently
270	supported flags are:	270	supported flags are:
271		271
272	* MSG_DONTWAIT, i.e. non-blocking operation.	272	* ``MSG_DONTWAIT``, i.e. non-blocking operation.
273		273
274	recvmsg(2)	274	recvmsg(2)
275	^^^^^^^^^^	275	^^^^^^^^^^
276		276
277	In most cases recvmsg(2) is needed if you want to extract more information than	277	In most cases ``recvmsg(2)`` is needed if you want to extract more information than
278	recvfrom(2) can provide. For example package priority and timestamp. The	278	``recvfrom(2)`` can provide. For example package priority and timestamp. The
279	Destination Address, name and packet priority (if applicable) are attached to	279	Destination Address, name and packet priority (if applicable) are attached to
280	the msghdr in the recvmsg(2) call. They can be extracted using cmsg(3) macros,	280	the msghdr in the ``recvmsg(2)`` call. They can be extracted using ``cmsg(3)`` macros,
281	with cmsg_level == SOL_J1939 && cmsg_type == SCM_J1939_DEST_ADDR,	281	with ``cmsg_level == SOL_J1939 && cmsg_type == SCM_J1939_DEST_ADDR``,
282	SCM_J1939_DEST_NAME or SCM_J1939_PRIO. The returned data is a uint8_t for	282	``SCM_J1939_DEST_NAME`` or ``SCM_J1939_PRIO``. The returned data is a ``uint8_t`` for
283	priority and dst_addr, and uint64_t for dst_name.	283	``priority`` and ``dst_addr``, and ``uint64_t`` for ``dst_name``.
284		284
285	.. code-block:: C	285	.. code-block:: C
286		286
@@ -305,12 +305,12 @@ Dynamic Addressing · 18 unmodified lines
305		305
306	Distinction has to be made between using the claimed address and doing an	306	Distinction has to be made between using the claimed address and doing an
307	address claim. To use an already claimed address, one has to fill in the	307	address claim. To use an already claimed address, one has to fill in the
308	j1939.name member and provide it to bind(2). If the name had claimed an address	308	``j1939.name`` member and provide it to ``bind(2)``. If the name had claimed an address
309	earlier, all further messages being sent will use that address. And the	309	earlier, all further messages being sent will use that address. And the
310	j1939.addr member will be ignored.	310	``j1939.addr`` member will be ignored.
311		311
312	An exception on this is PGN 0x0ee00. This is the "Address Claim/Cannot Claim	312	An exception on this is PGN 0x0ee00. This is the "Address Claim/Cannot Claim
313	Address" message and the kernel will use the j1939.addr member for that PGN if	313	Address" message and the kernel will use the ``j1939.addr`` member for that PGN if
314	necessary.	314	necessary.
315		315
316	To claim an address following code example can be used:	316	To claim an address following code example can be used:
@@ -371,12 +371,12 @@ NAME can send packets. · 54 unmodified lines
371		371
372	If another ECU claims the address, the kernel will mark the NAME-SA expired.	372	If another ECU claims the address, the kernel will mark the NAME-SA expired.
373	No socket bound to the NAME can send packets (other than address claims). To	373	No socket bound to the NAME can send packets (other than address claims). To
374	claim another address, some socket bound to NAME, must bind(2) again, but with	374	claim another address, some socket bound to NAME, must ``bind(2)`` again, but with
375	only j1939.addr changed to the new SA, and must then send a valid address claim	375	only ``j1939.addr`` changed to the new SA, and must then send a valid address claim
376	packet. This restarts the state machine in the kernel (and any other	376	packet. This restarts the state machine in the kernel (and any other
377	participant on the bus) for this NAME.	377	participant on the bus) for this NAME.
378		378
379	can-utils also include the jacd tool, so it can be used as code example or as	379	``can-utils`` also include the ``j1939acd`` tool, so it can be used as code example or as
380	default Address Claiming daemon.	380	default Address Claiming daemon.
381		381
382	Send Examples	382	Send Examples
@@ -403,8 +403,8 @@ Bind: · 20 unmodified lines
403		403
404	bind(sock, (struct sockaddr *)&baddr, sizeof(baddr));	404	bind(sock, (struct sockaddr *)&baddr, sizeof(baddr));
405		405
406	Now, the socket 'sock' is bound to the SA 0x20. Since no connect(2) was called,	406	Now, the socket 'sock' is bound to the SA 0x20. Since no ``connect(2)`` was called,
407	at this point we can use only sendto(2) or sendmsg(2).	407	at this point we can use only ``sendto(2)`` or ``sendmsg(2)``.
408		408
409	Send:	409	Send:
410		410
@@ -414,8 +414,8 @@ Send: · 3 unmodified lines
414	.can_family = AF_CAN,	414	.can_family = AF_CAN,
415	.can_addr.j1939 = {	415	.can_addr.j1939 = {
416	.name = J1939_NO_NAME;	416	.name = J1939_NO_NAME;
417	.pgn = 0x30,	417	.addr = 0x30,
418	.addr = 0x12300,	418	.pgn = 0x12300,
419	},	419	},
420	};	420	};
421		421

Documentation/networking/statistics.rst+1−2

@@ -175,5 +175,4 @@ The following structures are internal to the kernel, their members are · 174 unmodified lines
175	translated to netlink attributes when dumped. Drivers must not overwrite	175	translated to netlink attributes when dumped. Drivers must not overwrite
176	the statistics they don't report with 0.	176	the statistics they don't report with 0.
177		177
178	.. kernel-doc:: include/linux/ethtool.h	178	- ethtool_pause_stats()
179	:identifiers: ethtool_pause_stats

Documentation/sphinx/automarkup.py+14−6

 import re
 from itertools import chain
+#
+# Python 2 lacks re.ASCII...
+#
+try:
+    ascii_p3 = re.ASCII
+except AttributeError:
+    ascii_p3 = 0
 #
 # Regex nastiness.  Of course.
 # Try to identify "function()" that's not already marked up some
 # :c:func: block (i.e. ":c:func:`mmap()`s" flakes out), so the last
 # bit tries to restrict matches to things that won't create trouble.
 #
-RE_function = re.compile(r'\b(([a-zA-Z_]\w+)\(\))', flags=re.ASCII)
+RE_function = re.compile(r'\b(([a-zA-Z_]\w+)\(\))', flags=ascii_p3)
 #
 # Sphinx 2 uses the same :c:type role for struct, union, enum and typedef
 #
 RE_generic_type = re.compile(r'\b(struct|union|enum|typedef)\s+([a-zA-Z_]\w+)',
-                             flags=re.ASCII)
+                             flags=ascii_p3)
 #
 # Sphinx 3 uses a different C role for each one of struct, union, enum and
 # typedef
 #
-RE_struct = re.compile(r'\b(struct)\s+([a-zA-Z_]\w+)', flags=re.ASCII)
+RE_struct = re.compile(r'\b(struct)\s+([a-zA-Z_]\w+)', flags=ascii_p3)
-RE_union = re.compile(r'\b(union)\s+([a-zA-Z_]\w+)', flags=re.ASCII)
+RE_union = re.compile(r'\b(union)\s+([a-zA-Z_]\w+)', flags=ascii_p3)
-RE_enum = re.compile(r'\b(enum)\s+([a-zA-Z_]\w+)', flags=re.ASCII)
+RE_enum = re.compile(r'\b(enum)\s+([a-zA-Z_]\w+)', flags=ascii_p3)
-RE_typedef = re.compile(r'\b(typedef)\s+([a-zA-Z_]\w+)', flags=re.ASCII)
+RE_typedef = re.compile(r'\b(typedef)\s+([a-zA-Z_]\w+)', flags=ascii_p3)
 #
 # Detects a reference to a documentation page of the form Documentation/... with

Documentation/sphinx/kernel_abi.py+194−0

@@ -0,0 +1,194 @@
	1	# -- coding: utf-8; mode: python --
	2	# coding=utf-8
	3	# SPDX-License-Identifier: GPL-2.0
	4	#
	5	u"""
	6	kernel-abi
	7	~~~~~~~~~~
	8
	9	Implementation of the ``kernel-abi`` reST-directive.
	10
	11	:copyright: Copyright (C) 2016 Markus Heiser
	12	:copyright: Copyright (C) 2016-2020 Mauro Carvalho Chehab
	13	:maintained-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
	14	:license: GPL Version 2, June 1991 see Linux/COPYING for details.
	15
	16	The ``kernel-abi`` (:py:class:`KernelCmd`) directive calls the
	17	scripts/get_abi.pl script to parse the Kernel ABI files.
	18
	19	Overview of directive's argument and options.
	20
	21	.. code-block:: rst
	22
	23	.. kernel-abi:: <ABI directory location>
	24	:debug:
	25
	26	The argument ``<ABI directory location>`` is required. It contains the
	27	location of the ABI files to be parsed.
	28
	29	``debug``
	30	Inserts a code-block with the raw reST. Sometimes it is helpful to see
	31	what reST is generated.
	32
	33	"""
	34
	35	import codecs
	36	import os
	37	import subprocess
	38	import sys
	39	import re
	40	import kernellog
	41
	42	from os import path
	43
	44	from docutils import nodes, statemachine
	45	from docutils.statemachine import ViewList
	46	from docutils.parsers.rst import directives, Directive
	47	from docutils.utils.error_reporting import ErrorString
	48
	49	#
	50	# AutodocReporter is only good up to Sphinx 1.7
	51	#
	52	import sphinx
	53
	54	Use_SSI = sphinx.__version__[:3] >= '1.7'
	55	if Use_SSI:
	56	from sphinx.util.docutils import switch_source_input
	57	else:
	58	from sphinx.ext.autodoc import AutodocReporter
	59
	60	__version__ = '1.0'
	61
	62	def setup(app):
	63
	64	app.add_directive("kernel-abi", KernelCmd)
	65	return dict(
	66	version = __version__
	67	, parallel_read_safe = True
	68	, parallel_write_safe = True
	69	)
	70
	71	class KernelCmd(Directive):
	72
	73	u"""KernelABI (``kernel-abi``) directive"""
	74
	75	required_arguments = 1
	76	optional_arguments = 2
	77	has_content = False
	78	final_argument_whitespace = True
	79
	80	option_spec = {
	81	"debug" : directives.flag,
	82	"rst" : directives.unchanged
	83	}
	84
	85	def run(self):
	86
	87	doc = self.state.document
	88	if not doc.settings.file_insertion_enabled:
	89	raise self.warning("docutils: file insertion disabled")
	90
	91	env = doc.settings.env
	92	cwd = path.dirname(doc.current_source)
	93	cmd = "get_abi.pl rest --enable-lineno --dir "
	94	cmd += self.arguments[0]
	95
	96	if 'rst' in self.options:
	97	cmd += " --rst-source"
	98
	99	srctree = path.abspath(os.environ["srctree"])
	100
	101	fname = cmd
	102
	103	# extend PATH with $(srctree)/scripts
	104	path_env = os.pathsep.join([
	105	srctree + os.sep + "scripts",
	106	os.environ["PATH"]
	107	])
	108	shell_env = os.environ.copy()
	109	shell_env["PATH"] = path_env
	110	shell_env["srctree"] = srctree
	111
	112	lines = self.runCmd(cmd, shell=True, cwd=cwd, env=shell_env)
	113	nodeList = self.nestedParse(lines, self.arguments[0])
	114	return nodeList
	115
	116	def runCmd(self, cmd, **kwargs):
	117	u"""Run command ``cmd`` and return it's stdout as unicode."""
	118
	119	try:
	120	proc = subprocess.Popen(
	121	cmd
	122	, stdout = subprocess.PIPE
	123	, stderr = subprocess.PIPE
	124	, **kwargs
	125	)
	126	out, err = proc.communicate()
	127
	128	out, err = codecs.decode(out, 'utf-8'), codecs.decode(err, 'utf-8')
	129
	130	if proc.returncode != 0:
	131	raise self.severe(
	132	u"command '%s' failed with return code %d"
	133	% (cmd, proc.returncode)
	134	)
	135	except OSError as exc:
	136	raise self.severe(u"problems with '%s' directive: %s."
	137	% (self.name, ErrorString(exc)))
	138	return out
	139
	140	def nestedParse(self, lines, fname):
	141	content = ViewList()
	142	node = nodes.section()
	143
	144	if "debug" in self.options:
	145	code_block = "\n\n.. code-block:: rst\n :linenos:\n"
	146	for l in lines.split("\n"):
	147	code_block += "\n " + l
	148	lines = code_block + "\n\n"
	149
	150	line_regex = re.compile("^#define LINENO (\S+)\#([0-9]+)$")
	151	ln = 0
	152	n = 0
	153	f = fname
	154
	155	for line in lines.split("\n"):
	156	n = n + 1
	157	match = line_regex.search(line)
	158	if match:
	159	new_f = match.group(1)
	160
	161	# Sphinx parser is lazy: it stops parsing contents in the
	162	# middle, if it is too big. So, handle it per input file
	163	if new_f != f and content:
	164	self.do_parse(content, node)
	165	content = ViewList()
	166
	167	f = new_f
	168
	169	# sphinx counts lines from 0
	170	ln = int(match.group(2)) - 1
	171	else:
	172	content.append(line, f, ln)
	173
	174	kernellog.info(self.state.document.settings.env.app, "%s: parsed %i lines" % (fname, n))
	175
	176	if content:
	177	self.do_parse(content, node)
	178
	179	return node.children
	180
	181	def do_parse(self, content, node):
	182	if Use_SSI:
	183	with switch_source_input(self.state, content):
	184	self.state.nested_parse(content, 0, node, match_titles=1)
	185	else:
	186	buf = self.state.memo.title_styles, self.state.memo.section_level, self.state.memo.reporter
	187
	188	self.state.memo.title_styles = []
	189	self.state.memo.section_level = 0
	190	self.state.memo.reporter = AutodocReporter(content, self.state.memo.reporter)
	191	try:
	192	self.state.nested_parse(content, 0, node, match_titles=1)
	193	finally:
	194	self.state.memo.title_styles, self.state.memo.section_level, self.state.memo.reporter = buf

Documentation/sphinx/kernellog.py+5−1

@@ -25,4 +25,8 @@ def verbose(app, message): · 24 unmodified lines
25	else:	25	else:
26	app.verbose(message)	26	app.verbose(message)
27		27
28		28	def info(app, message):
		29	if UseLogging:
		30	logger.info(message)
		31	else:
		32	app.info(message)

Documentation/userspace-api/index.rst+1−0

@@ -22,6 +22,7 @@ place where this information is gathered. · 21 unmodified lines
22	spec_ctrl	22	spec_ctrl
23	accelerators/ocxl	23	accelerators/ocxl
24	ioctl/index	24	ioctl/index
		25	iommu
25	media/index	26	media/index
26		27
27	.. only:: subproject and html	28	.. only:: subproject and html

Documentation/virt/kvm/cpuid.rst+4−0

                                                async pf acknowledgment msr
                                                0x4b564d07.
+KVM_FEATURE_MSI_EXT_DEST_ID        15          guest checks this feature bit
+                                               before using extended destination
+                                               ID bits in MSI address bits 11-5.
 KVM_FEATURE_CLOCKSOURCE_STABLE_BIT 24          host will warn if no guest-side
                                                per-cpu warps are expected in
                                                kvmclock

MAINTAINERS+15−31

 L:	amd-gfx@lists.freedesktop.org
 S:	Supported
 T:	git git://people.freedesktop.org/~agd5f/linux
-F:	drivers/gpu/drm/amd/powerplay/
+F:	drivers/gpu/drm/amd/pm/powerplay/
 AMD SEATTLE DEVICE TREE SUPPORT
 M:	Brijesh Singh <brijeshkumar.singh@amd.com>
 L:	linux-iio@vger.kernel.org
 S:	Supported
 W:	http://ez.analog.com/community/linux-device-drivers
-F:	Documentation/devicetree/bindings/iio/adc/adi,ad7768-1.txt
+F:	Documentation/devicetree/bindings/iio/adc/adi,ad7768-1.yaml
 F:	drivers/iio/adc/ad7768-1.c
 ANALOG DEVICES INC AD7780 DRIVER
 N:	rockchip
 ARM/SAMSUNG EXYNOS ARM ARCHITECTURES
-M:	Kukjin Kim <kgene@kernel.org>
 M:	Krzysztof Kozlowski <krzk@kernel.org>
 L:	linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
 L:	linux-samsung-soc@vger.kernel.org
 N:	visconti
 ARM/UNIPHIER ARCHITECTURE
-M:	Masahiro Yamada <yamada.masahiro@socionext.com>
 L:	linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
-S:	Maintained
+S:	Orphan
-T:	git git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-uniphier.git
 F:	Documentation/devicetree/bindings/arm/socionext/uniphier.yaml
 F:	Documentation/devicetree/bindings/gpio/socionext,uniphier-gpio.yaml
 F:	Documentation/devicetree/bindings/pinctrl/socionext,uniphier-pinctrl.yaml
 L:	linux-usb@vger.kernel.org
 S:	Maintained
 T:	git git://git.kernel.org/pub/scm/linux/kernel/git/peter.chen/usb.git
-F:	Documentation/devicetree/bindings/usb/cdns-usb3.txt
+F:	Documentation/devicetree/bindings/usb/cdns,usb3.yaml
 F:	drivers/usb/cdns3/
 CADET FM/AM RADIO RECEIVER DRIVER
 F:	drivers/media/platform/sti/delta
 DENALI NAND DRIVER
-M:	Masahiro Yamada <yamada.masahiro@socionext.com>
 L:	linux-mtd@lists.infradead.org
-S:	Supported
+S:	Orphan
 F:	drivers/mtd/nand/raw/denali*
 DESIGNWARE EDMA CORE IP DRIVER
 M:	john.garry@huawei.com
 S:	Maintained
 W:	http://www.hisilicon.com
-F:	Documentation/devicetree/bindings/arm/hisilicon/hisilicon-low-pin-count.txt
+F:	Documentation/devicetree/bindings/arm/hisilicon/low-pin-count.yaml
 F:	drivers/bus/hisi_lpc.c
 HISILICON NETWORK SUBSYSTEM 3 DRIVER (HNS3)
 W:	https://01.org/linux-acpi
 F:	drivers/platform/x86/intel_menlow.c
-INTEL MIC DRIVERS (mic)
-M:	Sudeep Dutt <sudeep.dutt@intel.com>
-M:	Ashutosh Dixit <ashutosh.dixit@intel.com>
-S:	Supported
-W:	https://github.com/sudeepdutt/mic
-W:	http://software.intel.com/en-us/mic-developer
-F:	Documentation/misc-devices/mic/
-F:	drivers/dma/mic_x100_dma.c
-F:	drivers/dma/mic_x100_dma.h
-F:	drivers/misc/mic/
-F:	include/linux/mic_bus.h
-F:	include/linux/scif.h
-F:	include/uapi/linux/mic_common.h
-F:	include/uapi/linux/mic_ioctl.h
-F:	include/uapi/linux/scif_ioctl.h
 INTEL P-Unit IPC DRIVER
 M:	Zha Qipeng <qipeng.zha@intel.com>
 L:	platform-driver-x86@vger.kernel.org
 F:	drivers/mailbox/qcom-ipcc.c
 F:	include/dt-bindings/mailbox/qcom-ipcc.h
+QUALCOMM IPQ4019 VQMMC REGULATOR DRIVER
+M:	Robert Marko <robert.marko@sartura.hr>
+M:	Luka Perkov <luka.perkov@sartura.hr>
+L:	linux-arm-msm@vger.kernel.org
+S:	Maintained
+F:	Documentation/devicetree/bindings/regulator/vqmmc-ipq4019-regulator.yaml
+F:	drivers/regulator/vqmmc-ipq4019-regulator.c
 QUALCOMM RMNET DRIVER
 M:	Subash Abhinov Kasiviswanathan <subashab@codeaurora.org>
 M:	Sean Tranchetti <stranche@codeaurora.org>
 R:	Sergei Shtylyov <sergei.shtylyov@gmail.com>
 L:	netdev@vger.kernel.org
 L:	linux-renesas-soc@vger.kernel.org
-F:	Documentation/devicetree/bindings/net/renesas,*.txt
 F:	Documentation/devicetree/bindings/net/renesas,*.yaml
 F:	drivers/net/ethernet/renesas/
 F:	include/linux/sh_eth.h
 SAMSUNG AUDIO (ASoC) DRIVERS
 M:	Krzysztof Kozlowski <krzk@kernel.org>
-M:	Sangbeom Kim <sbkim73@samsung.com>
 M:	Sylwester Nawrocki <s.nawrocki@samsung.com>
 L:	alsa-devel@alsa-project.org (moderated for non-subscribers)
 S:	Supported
 F:	drivers/platform/x86/samsung-laptop.c
 SAMSUNG MULTIFUNCTION PMIC DEVICE DRIVERS
-M:	Sangbeom Kim <sbkim73@samsung.com>
 M:	Krzysztof Kozlowski <krzk@kernel.org>
 M:	Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
 L:	linux-kernel@vger.kernel.org
 F:	include/linux/platform_data/clk-s3c2410.h
 SAMSUNG SPI DRIVERS
-M:	Kukjin Kim <kgene@kernel.org>
 M:	Krzysztof Kozlowski <krzk@kernel.org>
 M:	Andi Shyti <andi@etezian.org>
 L:	linux-spi@vger.kernel.org
 M:	Binghui Wang <wangbinghui@hisilicon.com>
 L:	linux-usb@vger.kernel.org
 S:	Maintained
-F:	Documentation/devicetree/bindings/phy/phy-hi3660-usb3.txt
+F:	Documentation/devicetree/bindings/phy/hisilicon,hi3660-usb3.yaml
 F:	drivers/phy/hisilicon/phy-hi3660-usb3.c
 USB ISP116X DRIVER

Makefile+1−1

@@ -2,7 +2,7 @@ · 1 unmodified line
2	VERSION = 5	2	VERSION = 5
3	PATCHLEVEL = 10	3	PATCHLEVEL = 10
4	SUBLEVEL = 0	4	SUBLEVEL = 0
5	EXTRAVERSION = -rc1	5	EXTRAVERSION = -rc2
6	NAME = Kleptomaniac Octopus	6	NAME = Kleptomaniac Octopus
7		7
8	# DOCUMENTATION	8	# DOCUMENTATION

arch/arc/kernel/head.S+16−1

@@ -67,7 +67,22 @@ · 66 unmodified lines
67	sr r5, [ARC_REG_LPB_CTRL]	67	sr r5, [ARC_REG_LPB_CTRL]
68	1:	68	1:
69	#endif /* CONFIG_ARC_LPB_DISABLE */	69	#endif /* CONFIG_ARC_LPB_DISABLE */
70	#endif	70
		71	/* On HSDK, CCMs need to remapped super early */
		72	#ifdef CONFIG_ARC_SOC_HSDK
		73	mov r6, 0x60000000
		74	lr r5, [ARC_REG_ICCM_BUILD]
		75	breq r5, 0, 1f
		76	sr r6, [ARC_REG_AUX_ICCM]
		77	1:
		78	lr r5, [ARC_REG_DCCM_BUILD]
		79	breq r5, 0, 2f
		80	sr r6, [ARC_REG_AUX_DCCM]
		81	2:
		82	#endif /* CONFIG_ARC_SOC_HSDK */
		83
		84	#endif /* CONFIG_ISA_ARCV2 */
		85
71	; Config DSP_CTRL properly, so kernel may use integer multiply,	86	; Config DSP_CTRL properly, so kernel may use integer multiply,
72	; multiply-accumulate, and divide operations	87	; multiply-accumulate, and divide operations
73	DSP_EARLY_INIT	88	DSP_EARLY_INIT

arch/arc/kernel/stacktrace.c+6−1

 		int (*consumer_fn) (unsigned int, void *), void *arg)
 {
 #ifdef CONFIG_ARC_DW2_UNWIND
-	int ret = 0;
+	int ret = 0, cnt = 0;
 	unsigned int address;
 	struct unwind_frame_info frame_info;
 			break;
 		frame_info.regs.r63 = frame_info.regs.r31;
+		if (cnt++ > 128) {
+			printk("unwinder looping too long, aborting !\n");
+			return 0;
+		}
 	}
 	return address;		/* return the last address it saw */

arch/arc/plat-hsdk/platform.c+0−17

@@ -17,22 +17,6 @@ int arc_hsdk_axi_dmac_coherent __section(".data") = 0; · 16 unmodified lines
17		17
18	#define ARC_CCM_UNUSED_ADDR 0x60000000	18	#define ARC_CCM_UNUSED_ADDR 0x60000000
19		19
20	static void __init hsdk_init_per_cpu(unsigned int cpu)
21	{
22	/*
23	* By default ICCM is mapped to 0x7z while this area is used for
24	* kernel virtual mappings, so move it to currently unused area.
25	*/
26	if (cpuinfo_arc700[cpu].iccm.sz)
27	write_aux_reg(ARC_REG_AUX_ICCM, ARC_CCM_UNUSED_ADDR);
28
29	/*
30	* By default DCCM is mapped to 0x8z while this area is used by kernel,
31	* so move it to currently unused area.
32	*/
33	if (cpuinfo_arc700[cpu].dccm.sz)
34	write_aux_reg(ARC_REG_AUX_DCCM, ARC_CCM_UNUSED_ADDR);
35	}
36		20
37	#define ARC_PERIPHERAL_BASE 0xf0000000	21	#define ARC_PERIPHERAL_BASE 0xf0000000
38	#define CREG_BASE (ARC_PERIPHERAL_BASE + 0x1000)	22	#define CREG_BASE (ARC_PERIPHERAL_BASE + 0x1000)
@@ -339,5 +323,4 @@ static const char *hsdk_compat[] __initconst = { · 300 unmodified lines
339	MACHINE_START(SIMULATION, "hsdk")	323	MACHINE_START(SIMULATION, "hsdk")
340	.dt_compat = hsdk_compat,	324	.dt_compat = hsdk_compat,
341	.init_early = hsdk_init_early,	325	.init_early = hsdk_init_early,
342	.init_per_cpu = hsdk_init_per_cpu,
343	MACHINE_END	326	MACHINE_END

arch/arm/boot/dts/mmp2-olpc-xo-1-75.dts+2−2

@@ -227,12 +227,12 @@ · 226 unmodified lines
227	/delete-property/ #size-cells;	227	/delete-property/ #size-cells;
228	spi-slave;	228	spi-slave;
229	status = "okay";	229	status = "okay";
230	ready-gpio = <&gpio 125 GPIO_ACTIVE_HIGH>;	230	ready-gpios = <&gpio 125 GPIO_ACTIVE_HIGH>;
231		231
232	slave {	232	slave {
233	compatible = "olpc,xo1.75-ec";	233	compatible = "olpc,xo1.75-ec";
234	spi-cpha;	234	spi-cpha;
235	cmd-gpio = <&gpio 155 GPIO_ACTIVE_HIGH>;	235	cmd-gpios = <&gpio 155 GPIO_ACTIVE_HIGH>;
236	};	236	};
237	};	237	};
238		238

arch/arm/boot/dts/mmp3.dtsi+2−0

 				interrupts = <GIC_SPI 42 IRQ_TYPE_LEVEL_HIGH>;
 				clocks = <&soc_clocks MMP2_CLK_CCIC0>;
 				clock-names = "axi";
+				power-domains = <&soc_clocks MMP3_POWER_DOMAIN_CAMERA>;
 				#clock-cells = <0>;
 				clock-output-names = "mclk";
 				status = "disabled";
 				interrupts = <GIC_SPI 30 IRQ_TYPE_LEVEL_HIGH>;
 				clocks = <&soc_clocks MMP2_CLK_CCIC1>;
 				clock-names = "axi";
+				power-domains = <&soc_clocks MMP3_POWER_DOMAIN_CAMERA>;
 				#clock-cells = <0>;
 				clock-output-names = "mclk";
 				status = "disabled";

arch/arm/boot/dts/stm32mp157c-ed1.dts+15−0

 		states = <1800000 0x1>,
 			 <2900000 0x0>;
 	};
+	vin: vin {
+		compatible = "regulator-fixed";
+		regulator-name = "vin";
+		regulator-min-microvolt = <5000000>;
+		regulator-max-microvolt = <5000000>;
+		regulator-always-on;
+	};
 };
 &adc {
 		regulators {
 			compatible = "st,stpmic1-regulators";
+			buck1-supply = <&vin>;
+			buck2-supply = <&vin>;
+			buck3-supply = <&vin>;
+			buck4-supply = <&vin>;
 			ldo1-supply = <&v3v3>;
 			ldo2-supply = <&v3v3>;
 			ldo3-supply = <&vdd_ddr>;
+			ldo4-supply = <&vin>;
 			ldo5-supply = <&v3v3>;
 			ldo6-supply = <&v3v3>;
+			vref_ddr-supply = <&vin>;
+			boost-supply = <&vin>;
 			pwr_sw1-supply = <&bst_out>;
 			pwr_sw2-supply = <&bst_out>;

arch/arm/boot/dts/stm32mp15xx-dkx.dtsi+17−0

@@ -80,6 +80,14 @@ · 79 unmodified lines
80	dais = <&sai2a_port &sai2b_port &i2s2_port>;	80	dais = <&sai2a_port &sai2b_port &i2s2_port>;
81	status = "okay";	81	status = "okay";
82	};	82	};
		83
		84	vin: vin {
		85	compatible = "regulator-fixed";
		86	regulator-name = "vin";
		87	regulator-min-microvolt = <5000000>;
		88	regulator-max-microvolt = <5000000>;
		89	regulator-always-on;
		90	};
83	};	91	};
84		92
85	&adc {	93	&adc {
@@ -240,9 +248,18 @@ · 154 unmodified lines
240		248
241	regulators {	249	regulators {
242	compatible = "st,stpmic1-regulators";	250	compatible = "st,stpmic1-regulators";
		251	buck1-supply = <&vin>;
		252	buck2-supply = <&vin>;
		253	buck3-supply = <&vin>;
		254	buck4-supply = <&vin>;
243	ldo1-supply = <&v3v3>;	255	ldo1-supply = <&v3v3>;
		256	ldo2-supply = <&vin>;
244	ldo3-supply = <&vdd_ddr>;	257	ldo3-supply = <&vdd_ddr>;
		258	ldo4-supply = <&vin>;
		259	ldo5-supply = <&vin>;
245	ldo6-supply = <&v3v3>;	260	ldo6-supply = <&v3v3>;
		261	vref_ddr-supply = <&vin>;
		262	boost-supply = <&vin>;
246	pwr_sw1-supply = <&bst_out>;	263	pwr_sw1-supply = <&bst_out>;
247	pwr_sw2-supply = <&bst_out>;	264	pwr_sw2-supply = <&bst_out>;
248		265

arch/arm/boot/dts/sun4i-a10.dtsi+1−1

@@ -143,7 +143,7 @@ · 142 unmodified lines
143	trips {	143	trips {
144	cpu_alert0: cpu-alert0 {	144	cpu_alert0: cpu-alert0 {
145	/* milliCelsius */	145	/* milliCelsius */
146	temperature = <850000>;	146	temperature = <85000>;
147	hysteresis = <2000>;	147	hysteresis = <2000>;
148	type = "passive";	148	type = "passive";
149	};	149	};

arch/arm/configs/imx_v4_v5_defconfig+1−0

@@ -93,6 +93,7 @@ CONFIG_SPI=y · 92 unmodified lines
93	CONFIG_SPI_IMX=y	93	CONFIG_SPI_IMX=y
94	CONFIG_SPI_SPIDEV=y	94	CONFIG_SPI_SPIDEV=y
95	CONFIG_GPIO_SYSFS=y	95	CONFIG_GPIO_SYSFS=y
		96	CONFIG_GPIO_MXC=y
96	CONFIG_W1=y	97	CONFIG_W1=y
97	CONFIG_W1_MASTER_MXC=y	98	CONFIG_W1_MASTER_MXC=y
98	CONFIG_W1_SLAVE_THERM=y	99	CONFIG_W1_SLAVE_THERM=y

arch/arm/configs/imx_v6_v7_defconfig+1−0

@@ -217,6 +217,7 @@ CONFIG_GPIO_PCA953X=y · 216 unmodified lines
217	CONFIG_GPIO_PCF857X=y	217	CONFIG_GPIO_PCF857X=y
218	CONFIG_GPIO_STMPE=y	218	CONFIG_GPIO_STMPE=y
219	CONFIG_GPIO_74X164=y	219	CONFIG_GPIO_74X164=y
		220	CONFIG_GPIO_MXC=y
220	CONFIG_POWER_RESET=y	221	CONFIG_POWER_RESET=y
221	CONFIG_POWER_RESET_SYSCON=y	222	CONFIG_POWER_RESET_SYSCON=y
222	CONFIG_POWER_RESET_SYSCON_POWEROFF=y	223	CONFIG_POWER_RESET_SYSCON_POWEROFF=y

arch/arm/configs/multi_v5_defconfig+1−0

@@ -166,6 +166,7 @@ CONFIG_SPI_IMX=y · 165 unmodified lines
166	CONFIG_SPI_ORION=y	166	CONFIG_SPI_ORION=y
167	CONFIG_GPIO_ASPEED=m	167	CONFIG_GPIO_ASPEED=m
168	CONFIG_GPIO_ASPEED_SGPIO=y	168	CONFIG_GPIO_ASPEED_SGPIO=y
		169	CONFIG_GPIO_MXC=y
169	CONFIG_POWER_RESET=y	170	CONFIG_POWER_RESET=y
170	CONFIG_POWER_RESET_GPIO=y	171	CONFIG_POWER_RESET_GPIO=y
171	CONFIG_POWER_RESET_QNAP=y	172	CONFIG_POWER_RESET_QNAP=y

arch/arm/configs/multi_v7_defconfig+1−0

@@ -465,6 +465,7 @@ CONFIG_GPIO_PALMAS=y · 464 unmodified lines
465	CONFIG_GPIO_TPS6586X=y	465	CONFIG_GPIO_TPS6586X=y
466	CONFIG_GPIO_TPS65910=y	466	CONFIG_GPIO_TPS65910=y
467	CONFIG_GPIO_TWL4030=y	467	CONFIG_GPIO_TWL4030=y
		468	CONFIG_GPIO_MXC=y
468	CONFIG_POWER_AVS=y	469	CONFIG_POWER_AVS=y
469	CONFIG_ROCKCHIP_IODOMAIN=y	470	CONFIG_ROCKCHIP_IODOMAIN=y
470	CONFIG_POWER_RESET_AS3722=y	471	CONFIG_POWER_RESET_AS3722=y

arch/arm/mach-mvebu/coherency_ll.S+1−6

 	/*
 	 * MMU is disabled, use the physical address of the coherency
-	 * base address. However, if the coherency fabric isn't mapped
+	 * base address, (or 0x0 if the coherency fabric is not mapped)
-	 * (i.e its virtual address is zero), it means coherency is
-	 * not enabled, so we return 0.
 	 */
-	ldr	r1, =coherency_base
-	cmp	r1, #0
-	beq	2f
 	adr	r1, 3f
 	ldr	r3, [r1]
 	ldr	r1, [r1, r3]

arch/arm/mm/init.c+2−2

@@ -354,8 +354,8 @@ static void __init free_highpages(void) · 353 unmodified lines
354	/* set highmem page free */	354	/* set highmem page free */
355	for_each_free_mem_range(i, NUMA_NO_NODE, MEMBLOCK_NONE,	355	for_each_free_mem_range(i, NUMA_NO_NODE, MEMBLOCK_NONE,
356	&range_start, &range_end, NULL) {	356	&range_start, &range_end, NULL) {
357	unsigned long start = PHYS_PFN(range_start);	357	unsigned long start = PFN_UP(range_start);
358	unsigned long end = PHYS_PFN(range_end);	358	unsigned long end = PFN_DOWN(range_end);
359		359
360	/* Ignore complete lowmem entries */	360	/* Ignore complete lowmem entries */
361	if (end <= max_low)	361	if (end <= max_low)

arch/arm64/Kconfig+21−1

@@ -636,6 +636,26 @@ config ARM64_ERRATUM_1542419 · 635 unmodified lines
636		636
637	If unsure, say Y.	637	If unsure, say Y.
638		638
		639	config ARM64_ERRATUM_1508412
		640	bool "Cortex-A77: 1508412: workaround deadlock on sequence of NC/Device load and store exclusive or PAR read"
		641	default y
		642	help
		643	This option adds a workaround for Arm Cortex-A77 erratum 1508412.
		644
		645	Affected Cortex-A77 cores (r0p0, r1p0) could deadlock on a sequence
		646	of a store-exclusive or read of PAR_EL1 and a load with device or
		647	non-cacheable memory attributes. The workaround depends on a firmware
		648	counterpart.
		649
		650	KVM guests must also have the workaround implemented or they can
		651	deadlock the system.
		652
		653	Work around the issue by inserting DMB SY barriers around PAR_EL1
		654	register reads and warning KVM users. The DMB barrier is sufficient
		655	to prevent a speculative PAR_EL1 read.
		656
		657	If unsure, say Y.
		658
639	config CAVIUM_ERRATUM_22375	659	config CAVIUM_ERRATUM_22375
640	bool "Cavium erratum 22375, 24313"	660	bool "Cavium erratum 22375, 24313"
641	default y	661	default y
@@ -982,7 +1002,7 @@ config NUMA · 340 unmodified lines
982	config NODES_SHIFT	1002	config NODES_SHIFT
983	int "Maximum NUMA Nodes (as a power of 2)"	1003	int "Maximum NUMA Nodes (as a power of 2)"
984	range 1 10	1004	range 1 10
985	default "2"	1005	default "4"
986	depends on NEED_MULTIPLE_NODES	1006	depends on NEED_MULTIPLE_NODES
987	help	1007	help
988	Specify the maximum number of NUMA Nodes available on the target	1008	Specify the maximum number of NUMA Nodes available on the target

arch/arm64/Kconfig.platforms+1−0

@@ -54,6 +54,7 @@ config ARCH_BCM_IPROC · 53 unmodified lines
54	config ARCH_BERLIN	54	config ARCH_BERLIN
55	bool "Marvell Berlin SoC Family"	55	bool "Marvell Berlin SoC Family"
56	select DW_APB_ICTL	56	select DW_APB_ICTL
		57	select DW_APB_TIMER_OF
57	select GPIOLIB	58	select GPIOLIB
58	select PINCTRL	59	select PINCTRL
59	help	60	help

arch/arm64/boot/dts/amlogic/meson-axg-s400.dts+6−0

@@ -584,3 +584,9 @@ · 583 unmodified lines
584	pinctrl-0 = <&uart_ao_a_pins>;	584	pinctrl-0 = <&uart_ao_a_pins>;
585	pinctrl-names = "default";	585	pinctrl-names = "default";
586	};	586	};
		587
		588	&usb {
		589	status = "okay";
		590	dr_mode = "otg";
		591	vbus-supply = <&usb_pwr>;
		592	};

arch/arm64/boot/dts/amlogic/meson-axg.dtsi+52−0

@@ -171,6 +171,46 @@ · 170 unmodified lines
171	#size-cells = <2>;	171	#size-cells = <2>;
172	ranges;	172	ranges;
173		173
		174	usb: usb@ffe09080 {
		175	compatible = "amlogic,meson-axg-usb-ctrl";
		176	reg = <0x0 0xffe09080 0x0 0x20>;
		177	interrupts = <GIC_SPI 16 IRQ_TYPE_LEVEL_HIGH>;
		178	#address-cells = <2>;
		179	#size-cells = <2>;
		180	ranges;
		181
		182	clocks = <&clkc CLKID_USB>, <&clkc CLKID_USB1_DDR_BRIDGE>;
		183	clock-names = "usb_ctrl", "ddr";
		184	resets = <&reset RESET_USB_OTG>;
		185
		186	dr_mode = "otg";
		187
		188	phys = <&usb2_phy1>;
		189	phy-names = "usb2-phy1";
		190
		191	dwc2: usb@ff400000 {
		192	compatible = "amlogic,meson-g12a-usb", "snps,dwc2";
		193	reg = <0x0 0xff400000 0x0 0x40000>;
		194	interrupts = <GIC_SPI 31 IRQ_TYPE_LEVEL_HIGH>;
		195	clocks = <&clkc CLKID_USB1>;
		196	clock-names = "otg";
		197	phys = <&usb2_phy1>;
		198	dr_mode = "peripheral";
		199	g-rx-fifo-size = <192>;
		200	g-np-tx-fifo-size = <128>;
		201	g-tx-fifo-size = <128 128 16 16 16>;
		202	};
		203
		204	dwc3: usb@ff500000 {
		205	compatible = "snps,dwc3";
		206	reg = <0x0 0xff500000 0x0 0x100000>;
		207	interrupts = <GIC_SPI 30 IRQ_TYPE_LEVEL_HIGH>;
		208	dr_mode = "host";
		209	maximum-speed = "high-speed";
		210	snps,dis_u2_susphy_quirk;
		211	};
		212	};
		213
174	ethmac: ethernet@ff3f0000 {	214	ethmac: ethernet@ff3f0000 {
175	compatible = "amlogic,meson-axg-dwmac",	215	compatible = "amlogic,meson-axg-dwmac",
176	"snps,dwmac-3.70a",	216	"snps,dwmac-3.70a",
@@ -187,6 +227,8 @@ · 10 unmodified lines
187	"timing-adjustment";	227	"timing-adjustment";
188	rx-fifo-depth = <4096>;	228	rx-fifo-depth = <4096>;
189	tx-fifo-depth = <2048>;	229	tx-fifo-depth = <2048>;
		230	resets = <&reset RESET_ETHERNET>;
		231	reset-names = "stmmaceth";
190	status = "disabled";	232	status = "disabled";
191	};	233	};
192		234
@@ -1734,6 +1776,16 @@ · 1541 unmodified lines
1734	clock-names = "core", "clkin0", "clkin1";	1776	clock-names = "core", "clkin0", "clkin1";
1735	resets = <&reset RESET_SD_EMMC_C>;	1777	resets = <&reset RESET_SD_EMMC_C>;
1736	};	1778	};
		1779
		1780	usb2_phy1: phy@9020 {
		1781	compatible = "amlogic,meson-gxl-usb2-phy";
		1782	#phy-cells = <0>;
		1783	reg = <0x0 0x9020 0x0 0x20>;
		1784	clocks = <&clkc CLKID_USB>;
		1785	clock-names = "phy";
		1786	resets = <&reset RESET_USB_OTG>;
		1787	reset-names = "phy";
		1788	};
1737	};	1789	};
1738		1790
1739	sram: sram@fffc0000 {	1791	sram: sram@fffc0000 {

arch/arm64/boot/dts/amlogic/meson-g12-common.dtsi+5−1

 		};
 		ethmac: ethernet@ff3f0000 {
-			compatible = "amlogic,meson-axg-dwmac",
+			compatible = "amlogic,meson-g12a-dwmac",
 				     "snps,dwmac-3.70a",
 				     "snps,dwmac";
 			reg = <0x0 0xff3f0000 0x0 0x10000>,
 				      "timing-adjustment";
 			rx-fifo-depth = <4096>;
 			tx-fifo-depth = <2048>;
+			resets = <&reset RESET_ETHERNET>;
+			reset-names = "stmmaceth";
 			status = "disabled";
 			mdio0: mdio {
 				hwrng: rng@218 {
 					compatible = "amlogic,meson-rng";
 					reg = <0x0 0x218 0x0 0x4>;
+					clocks = <&clkc CLKID_RNG0>;
+					clock-names = "core";
 				};
 			};

arch/arm64/boot/dts/amlogic/meson-g12b-odroid-n2-plus.dts+1−1

@@ -19,7 +19,7 @@ · 18 unmodified lines
19	regulator-min-microvolt = <680000>;	19	regulator-min-microvolt = <680000>;
20	regulator-max-microvolt = <1040000>;	20	regulator-max-microvolt = <1040000>;
21		21
22	pwms = <&pwm_AO_cd 1 1500 0>;	22	pwms = <&pwm_ab 0 1500 0>;
23	};	23	};
24		24
25	&vddcpu_b {	25	&vddcpu_b {

arch/arm64/boot/dts/amlogic/meson-gx.dtsi+3−0

 #include <dt-bindings/interrupt-controller/irq.h>
 #include <dt-bindings/interrupt-controller/arm-gic.h>
 #include <dt-bindings/power/meson-gxbb-power.h>
+#include <dt-bindings/reset/amlogic,meson-gxbb-reset.h>
 #include <dt-bindings/thermal/thermal.h>
 / {
 			interrupt-names = "macirq";
 			rx-fifo-depth = <4096>;
 			tx-fifo-depth = <2048>;
+			resets = <&reset RESET_ETHERNET>;
+			reset-names = "stmmaceth";
 			power-domains = <&pwrc PWRC_GXBB_ETHERNET_MEM_ID>;
 			status = "disabled";
 		};

arch/arm64/boot/dts/marvell/armada-3720-espressobin-v7-emmc.dts+8−2

 	compatible = "globalscale,espressobin-v7-emmc", "globalscale,espressobin-v7",
 		     "globalscale,espressobin", "marvell,armada3720",
 		     "marvell,armada3710";
+	aliases {
+		/* ethernet1 is wan port */
+		ethernet1 = &switch0port3;
+		ethernet3 = &switch0port1;
+	};
 };
 &switch0 {
 	ports {
-		port@1 {
+		switch0port1: port@1 {
 			reg = <1>;
 			label = "lan1";
 			phy-handle = <&switch0phy0>;
 		};
-		port@3 {
+		switch0port3: port@3 {
 			reg = <3>;
 			label = "wan";
 			phy-handle = <&switch0phy2>;

arch/arm64/boot/dts/marvell/armada-3720-espressobin-v7.dts+8−2

 	model = "Globalscale Marvell ESPRESSOBin Board V7";
 	compatible = "globalscale,espressobin-v7", "globalscale,espressobin",
 		     "marvell,armada3720", "marvell,armada3710";
+	aliases {
+		/* ethernet1 is wan port */
+		ethernet1 = &switch0port3;
+		ethernet3 = &switch0port1;
+	};
 };
 &switch0 {
 	ports {
-		port@1 {
+		switch0port1: port@1 {
 			reg = <1>;
 			label = "lan1";
 			phy-handle = <&switch0phy0>;
 		};
-		port@3 {
+		switch0port3: port@3 {
 			reg = <3>;
 			label = "wan";
 			phy-handle = <&switch0phy2>;

arch/arm64/boot/dts/marvell/armada-3720-espressobin.dtsi+8−4

 / {
 	aliases {
 		ethernet0 = &eth0;
+		/* for dsa slave device */
+		ethernet1 = &switch0port1;
+		ethernet2 = &switch0port2;
+		ethernet3 = &switch0port3;
 		serial0 = &uart0;
 		serial1 = &uart1;
 	};
 			#address-cells = <1>;
 			#size-cells = <0>;
-			port@0 {
+			switch0port0: port@0 {
 				reg = <0>;
 				label = "cpu";
 				ethernet = <&eth0>;
 				};
 			};
-			port@1 {
+			switch0port1: port@1 {
 				reg = <1>;
 				label = "wan";
 				phy-handle = <&switch0phy0>;
 			};
-			port@2 {
+			switch0port2: port@2 {
 				reg = <2>;
 				label = "lan0";
 				phy-handle = <&switch0phy1>;
 			};
-			port@3 {
+			switch0port3: port@3 {
 				reg = <3>;
 				label = "lan1";
 				phy-handle = <&switch0phy2>;

arch/arm64/configs/defconfig+1−0

@@ -500,6 +500,7 @@ CONFIG_GPIO_ALTERA=m · 499 unmodified lines
500	CONFIG_GPIO_DWAPB=y	500	CONFIG_GPIO_DWAPB=y
501	CONFIG_GPIO_MB86S7X=y	501	CONFIG_GPIO_MB86S7X=y
502	CONFIG_GPIO_MPC8XXX=y	502	CONFIG_GPIO_MPC8XXX=y
		503	CONFIG_GPIO_MXC=y
503	CONFIG_GPIO_PL061=y	504	CONFIG_GPIO_PL061=y
504	CONFIG_GPIO_RCAR=y	505	CONFIG_GPIO_RCAR=y
505	CONFIG_GPIO_UNIPHIER=y	506	CONFIG_GPIO_UNIPHIER=y

arch/arm64/include/asm/brk-imm.h+2−0

  * #imm16 values used for BRK instruction generation
  * 0x004: for installing kprobes
  * 0x005: for installing uprobes
+ * 0x006: for kprobe software single-step
  * Allowed values for kgdb are 0x400 - 0x7ff
  * 0x100: for triggering a fault on purpose (reserved)
  * 0x400: for dynamic BRK instruction
  */
 #define KPROBES_BRK_IMM			0x004
 #define UPROBES_BRK_IMM			0x005
+#define KPROBES_BRK_SS_IMM		0x006
 #define FAULT_BRK_IMM			0x100
 #define KGDB_DYN_DBG_BRK_IMM		0x400
 #define KGDB_COMPILED_DBG_BRK_IMM	0x401

arch/arm64/include/asm/cache.h+1−0

@@ -24,6 +24,7 @@ · 23 unmodified lines
24	#define CTR_L1IP(ctr) (((ctr) >> CTR_L1IP_SHIFT) & CTR_L1IP_MASK)	24	#define CTR_L1IP(ctr) (((ctr) >> CTR_L1IP_SHIFT) & CTR_L1IP_MASK)
25		25
26	#define ICACHE_POLICY_VPIPT 0	26	#define ICACHE_POLICY_VPIPT 0
		27	#define ICACHE_POLICY_RESERVED 1
27	#define ICACHE_POLICY_VIPT 2	28	#define ICACHE_POLICY_VIPT 2
28	#define ICACHE_POLICY_PIPT 3	29	#define ICACHE_POLICY_PIPT 3
29		30

arch/arm64/include/asm/cpucaps.h+2−1

@@ -65,7 +65,8 @@ · 64 unmodified lines
65	#define ARM64_HAS_ARMv8_4_TTL 55	65	#define ARM64_HAS_ARMv8_4_TTL 55
66	#define ARM64_HAS_TLB_RANGE 56	66	#define ARM64_HAS_TLB_RANGE 56
67	#define ARM64_MTE 57	67	#define ARM64_MTE 57
		68	#define ARM64_WORKAROUND_1508412 58
68		69
69	#define ARM64_NCAPS 58	70	#define ARM64_NCAPS 59
70		71
71	#endif /* __ASM_CPUCAPS_H */	72	#endif /* __ASM_CPUCAPS_H */

arch/arm64/include/asm/cpufeature.h+31−9

 	return false;
 }
+static __always_inline bool is_vhe_hyp_code(void)
+{
+	/* Only defined for code run in VHE hyp context */
+	return __is_defined(__KVM_VHE_HYPERVISOR__);
+}
+static __always_inline bool is_nvhe_hyp_code(void)
+{
+	/* Only defined for code run in NVHE hyp context */
+	return __is_defined(__KVM_NVHE_HYPERVISOR__);
+}
+static __always_inline bool is_hyp_code(void)
+{
+	return is_vhe_hyp_code() || is_nvhe_hyp_code();
+}
 extern DECLARE_BITMAP(cpu_hwcaps, ARM64_NCAPS);
 extern struct static_key_false cpu_hwcap_keys[ARM64_NCAPS];
 extern struct static_key_false arm64_const_caps_ready;
 }
 /*
- * Test for a capability, possibly with a runtime check.
+ * Test for a capability without a runtime check.
  *
- * Before capabilities are finalized, this behaves as cpus_have_cap().
+ * Before capabilities are finalized, this will BUG().
  * After capabilities are finalized, this is patched to avoid a runtime check.
  *
  * @num must be a compile-time constant.
  */
-static __always_inline bool cpus_have_const_cap(int num)
+static __always_inline bool cpus_have_final_cap(int num)
 {
 	if (system_capabilities_finalized())
 		return __cpus_have_const_cap(num);
 	else
-		return cpus_have_cap(num);
+		BUG();
 }
 /*
- * Test for a capability without a runtime check.
+ * Test for a capability, possibly with a runtime check for non-hyp code.
  *
- * Before capabilities are finalized, this will BUG().
+ * For hyp code, this behaves the same as cpus_have_final_cap().
+ *
+ * For non-hyp code:
+ * Before capabilities are finalized, this behaves as cpus_have_cap().
  * After capabilities are finalized, this is patched to avoid a runtime check.
  *
  * @num must be a compile-time constant.
  */
-static __always_inline bool cpus_have_final_cap(int num)
+static __always_inline bool cpus_have_const_cap(int num)
 {
-	if (system_capabilities_finalized())
+	if (is_hyp_code())
+		return cpus_have_final_cap(num);
+	else if (system_capabilities_finalized())
 		return __cpus_have_const_cap(num);
 	else
-		BUG();
+		return cpus_have_cap(num);
 }
 static inline void cpus_set_cap(unsigned int num)

arch/arm64/include/asm/cputype.h+2−0

 #define ARM_CPU_PART_CORTEX_A55		0xD05
 #define ARM_CPU_PART_CORTEX_A76		0xD0B
 #define ARM_CPU_PART_NEOVERSE_N1	0xD0C
+#define ARM_CPU_PART_CORTEX_A77		0xD0D
 #define APM_CPU_PART_POTENZA		0x000
 #define MIDR_CORTEX_A55 MIDR_CPU_MODEL(ARM_CPU_IMP_ARM, ARM_CPU_PART_CORTEX_A55)
 #define MIDR_CORTEX_A76	MIDR_CPU_MODEL(ARM_CPU_IMP_ARM, ARM_CPU_PART_CORTEX_A76)
 #define MIDR_NEOVERSE_N1 MIDR_CPU_MODEL(ARM_CPU_IMP_ARM, ARM_CPU_PART_NEOVERSE_N1)
+#define MIDR_CORTEX_A77	MIDR_CPU_MODEL(ARM_CPU_IMP_ARM, ARM_CPU_PART_CORTEX_A77)
 #define MIDR_THUNDERX	MIDR_CPU_MODEL(ARM_CPU_IMP_CAVIUM, CAVIUM_CPU_PART_THUNDERX)
 #define MIDR_THUNDERX_81XX MIDR_CPU_MODEL(ARM_CPU_IMP_CAVIUM, CAVIUM_CPU_PART_THUNDERX_81XX)
 #define MIDR_THUNDERX_83XX MIDR_CPU_MODEL(ARM_CPU_IMP_CAVIUM, CAVIUM_CPU_PART_THUNDERX_83XX)

arch/arm64/include/asm/debug-monitors.h+1−0

@@ -53,6 +53,7 @@ · 52 unmodified lines
53		53
54	/* kprobes BRK opcodes with ESR encoding */	54	/* kprobes BRK opcodes with ESR encoding */
55	#define BRK64_OPCODE_KPROBES (AARCH64_BREAK_MON \| (KPROBES_BRK_IMM << 5))	55	#define BRK64_OPCODE_KPROBES (AARCH64_BREAK_MON \| (KPROBES_BRK_IMM << 5))
		56	#define BRK64_OPCODE_KPROBES_SS (AARCH64_BREAK_MON \| (KPROBES_BRK_SS_IMM << 5))
56	/* uprobes BRK opcodes with ESR encoding */	57	/* uprobes BRK opcodes with ESR encoding */
57	#define BRK64_OPCODE_UPROBES (AARCH64_BREAK_MON \| (UPROBES_BRK_IMM << 5))	58	#define BRK64_OPCODE_UPROBES (AARCH64_BREAK_MON \| (UPROBES_BRK_IMM << 5))
58		59

arch/arm64/include/asm/kprobes.h+1−1

@@ -16,7 +16,7 @@ · 15 unmodified lines
16	#include <linux/percpu.h>	16	#include <linux/percpu.h>
17		17
18	#define __ARCH_WANT_KPROBES_INSN_SLOT	18	#define __ARCH_WANT_KPROBES_INSN_SLOT
19	#define MAX_INSN_SIZE 1	19	#define MAX_INSN_SIZE 2
20		20
21	#define flush_insn_slot(p) do { } while (0)	21	#define flush_insn_slot(p) do { } while (0)
22	#define kretprobe_blacklist_size 0	22	#define kretprobe_blacklist_size 0

arch/arm64/include/asm/kvm_host.h+1−0

@@ -239,6 +239,7 @@ enum vcpu_sysreg { · 238 unmodified lines
239	#define cp14_DBGWCR0 (DBGWCR0_EL1 * 2)	239	#define cp14_DBGWCR0 (DBGWCR0_EL1 * 2)
240	#define cp14_DBGWVR0 (DBGWVR0_EL1 * 2)	240	#define cp14_DBGWVR0 (DBGWVR0_EL1 * 2)
241	#define cp14_DBGDCCINT (MDCCINT_EL1 * 2)	241	#define cp14_DBGDCCINT (MDCCINT_EL1 * 2)
		242	#define cp14_DBGVCR (DBGVCR32_EL2 * 2)
242		243
243	#define NR_COPRO_REGS (NR_SYS_REGS * 2)	244	#define NR_COPRO_REGS (NR_SYS_REGS * 2)
244		245

arch/arm64/include/asm/sysreg.h+9−0

 #include <linux/build_bug.h>
 #include <linux/types.h>
+#include <asm/alternative.h>
 #define __DEFINE_MRS_MSR_S_REGNUM				\
 "	.irp	num,0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30\n" \
 		write_sysreg_s(__scs_new, sysreg);			\
 } while (0)
+#define read_sysreg_par() ({						\
+	u64 par;							\
+	asm(ALTERNATIVE("nop", "dmb sy", ARM64_WORKAROUND_1508412));	\
+	par = read_sysreg(par_el1);					\
+	asm(ALTERNATIVE("nop", "dmb sy", ARM64_WORKAROUND_1508412));	\
+	par;								\
+})
 #endif
 #endif	/* __ASM_SYSREG_H */

arch/arm64/include/asm/virt.h+4−5

 static __always_inline bool has_vhe(void)
 {
 	/*
-	 * The following macros are defined for code specic to VHE/nVHE.
+	 * Code only run in VHE/NVHE hyp context can assume VHE is present or
-	 * If has_vhe() is inlined into those compilation units, it can
+	 * absent. Otherwise fall back to caps.
-	 * be determined statically. Otherwise fall back to caps.
 	 */
-	if (__is_defined(__KVM_VHE_HYPERVISOR__))
+	if (is_vhe_hyp_code())
 		return true;
-	else if (__is_defined(__KVM_NVHE_HYPERVISOR__))
+	else if (is_nvhe_hyp_code())
 		return false;
 	else
 		return cpus_have_final_cap(ARM64_HAS_VIRT_HOST_EXTN);

arch/arm64/kernel/cpu_errata.c+10−0

@@ -522,6 +522,16 @@ const struct arm64_cpu_capabilities arm64_errata[] = { · 521 unmodified lines
522	.matches = has_neoverse_n1_erratum_1542419,	522	.matches = has_neoverse_n1_erratum_1542419,
523	.cpu_enable = cpu_enable_trap_ctr_access,	523	.cpu_enable = cpu_enable_trap_ctr_access,
524	},	524	},
		525	#endif
		526	#ifdef CONFIG_ARM64_ERRATUM_1508412
		527	{
		528	/* we depend on the firmware portion for correctness */
		529	.desc = "ARM erratum 1508412 (kernel portion)",
		530	.capability = ARM64_WORKAROUND_1508412,
		531	ERRATA_MIDR_RANGE(MIDR_CORTEX_A77,
		532	0, 0,
		533	1, 0),
		534	},
525	#endif	535	#endif
526	{	536	{
527	}	537	}

arch/arm64/kernel/cpuinfo.c+4−3

 static struct cpuinfo_arm64 boot_cpu_data;
 static const char *icache_policy_str[] = {
-	[0 ... ICACHE_POLICY_PIPT]	= "RESERVED/UNKNOWN",
+	[ICACHE_POLICY_VPIPT]		= "VPIPT",
+	[ICACHE_POLICY_RESERVED]	= "RESERVED/UNKNOWN",
 	[ICACHE_POLICY_VIPT]		= "VIPT",
 	[ICACHE_POLICY_PIPT]		= "PIPT",
-	[ICACHE_POLICY_VPIPT]		= "VPIPT",
 };
 unsigned long __icache_flags;
 	case ICACHE_POLICY_VPIPT:
 		set_bit(ICACHEF_VPIPT, &__icache_flags);
 		break;
-	default:
+	case ICACHE_POLICY_RESERVED:
 	case ICACHE_POLICY_VIPT:
 		/* Assume aliasing */
 		set_bit(ICACHEF_ALIASING, &__icache_flags);
+		break;
 	}
 	pr_info("Detected %s I-cache on CPU%d\n", icache_policy_str[l1ip], cpu);

arch/arm64/kernel/efi-header.S+1−1

@@ -147,6 +147,6 @@ efi_debug_entry: · 146 unmodified lines
147	* correctly at this alignment, we must ensure that .text is	147	* correctly at this alignment, we must ensure that .text is
148	* placed at a 4k boundary in the Image to begin with.	148	* placed at a 4k boundary in the Image to begin with.
149	*/	149	*/
150	.align 12	150	.balign SEGMENT_ALIGN
151	efi_header_end:	151	efi_header_end:
152	.endm	152	.endm

arch/arm64/kernel/entry.S+3−0

 	br	x30
 #endif
 	.else
+	/* Ensure any device/NC reads complete */
+	alternative_insn nop, "dmb sy", ARM64_WORKAROUND_1508412
 	eret
 	.endif
 	sb

arch/arm64/kernel/image-vars.h+0−1

@@ -87,7 +87,6 @@ KVM_NVHE_ALIAS(__icache_flags); · 86 unmodified lines
87	/* Kernel symbols needed for cpus_have_final/const_caps checks. */	87	/* Kernel symbols needed for cpus_have_final/const_caps checks. */
88	KVM_NVHE_ALIAS(arm64_const_caps_ready);	88	KVM_NVHE_ALIAS(arm64_const_caps_ready);
89	KVM_NVHE_ALIAS(cpu_hwcap_keys);	89	KVM_NVHE_ALIAS(cpu_hwcap_keys);
90	KVM_NVHE_ALIAS(cpu_hwcaps);
91		90
92	/* Static keys which are set if a vGIC trap should be handled in hyp. */	91	/* Static keys which are set if a vGIC trap should be handled in hyp. */
93	KVM_NVHE_ALIAS(vgic_v2_cpuif_trap);	92	KVM_NVHE_ALIAS(vgic_v2_cpuif_trap);

arch/arm64/kernel/kexec_image.c+31−10

@@ -43,7 +43,7 @@ static void image_load(struct kimage image, · 42 unmodified lines
43	u64 flags, value;	43	u64 flags, value;
44	bool be_image, be_kernel;	44	bool be_image, be_kernel;
45	struct kexec_buf kbuf;	45	struct kexec_buf kbuf;
46	unsigned long text_offset;	46	unsigned long text_offset, kernel_segment_number;
47	struct kexec_segment *kernel_segment;	47	struct kexec_segment *kernel_segment;
48	int ret;	48	int ret;
49		49
@@ -88,11 +88,37 @@ static void image_load(struct kimage image, · 38 unmodified lines
88	/* Adjust kernel segment with TEXT_OFFSET */	88	/* Adjust kernel segment with TEXT_OFFSET */
89	kbuf.memsz += text_offset;	89	kbuf.memsz += text_offset;
90		90
91	ret = kexec_add_buffer(&kbuf);	91	kernel_segment_number = image->nr_segments;
92	if (ret)	92
		93	/*
		94	* The location of the kernel segment may make it impossible to satisfy
		95	* the other segment requirements, so we try repeatedly to find a
		96	* location that will work.
		97	*/
		98	while ((ret = kexec_add_buffer(&kbuf)) == 0) {
		99	/* Try to load additional data */
		100	kernel_segment = &image->segment[kernel_segment_number];
		101	ret = load_other_segments(image, kernel_segment->mem,
		102	kernel_segment->memsz, initrd,
		103	initrd_len, cmdline);
		104	if (!ret)
		105	break;
		106
		107	/*
		108	* We couldn't find space for the other segments; erase the
		109	* kernel segment and try the next available hole.
		110	*/
		111	image->nr_segments -= 1;
		112	kbuf.buf_min = kernel_segment->mem + kernel_segment->memsz;
		113	kbuf.mem = KEXEC_BUF_MEM_UNKNOWN;
		114	}
		115
		116	if (ret) {
		117	pr_err("Could not find any suitable kernel location!");
93	return ERR_PTR(ret);	118	return ERR_PTR(ret);
		119	}
94		120
95	kernel_segment = &image->segment[image->nr_segments - 1];	121	kernel_segment = &image->segment[kernel_segment_number];
96	kernel_segment->mem += text_offset;	122	kernel_segment->mem += text_offset;
97	kernel_segment->memsz -= text_offset;	123	kernel_segment->memsz -= text_offset;
98	image->start = kernel_segment->mem;	124	image->start = kernel_segment->mem;
@@ -101,12 +127,7 @@ static void image_load(struct kimage image, · 2 unmodified lines
101	kernel_segment->mem, kbuf.bufsz,	127	kernel_segment->mem, kbuf.bufsz,
102	kernel_segment->memsz);	128	kernel_segment->memsz);
103		129
104	/* Load additional data */	130	return 0;
105	ret = load_other_segments(image,
106	kernel_segment->mem, kernel_segment->memsz,
107	initrd, initrd_len, cmdline);
108
109	return ERR_PTR(ret);
110	}	131	}
111		132
112	#ifdef CONFIG_KEXEC_IMAGE_VERIFY_SIG	133	#ifdef CONFIG_KEXEC_IMAGE_VERIFY_SIG

arch/arm64/kernel/machine_kexec_file.c+8−1

 	return ret;
 }
+/*
+ * Tries to add the initrd and DTB to the image. If it is not possible to find
+ * valid locations, this function will undo changes to the image and return non
+ * zero.
+ */
 int load_other_segments(struct kimage *image,
 			unsigned long kernel_load_addr,
 			unsigned long kernel_size,
 {
 	struct kexec_buf kbuf;
 	void *headers, *dtb = NULL;
-	unsigned long headers_sz, initrd_load_addr = 0, dtb_len;
+	unsigned long headers_sz, initrd_load_addr = 0, dtb_len,
+		      orig_segments = image->nr_segments;
 	int ret = 0;
 	kbuf.image = image;
 	return 0;
 out_err:
+	image->nr_segments = orig_segments;
 	vfree(dtb);
 	return ret;
 }

arch/arm64/kernel/probes/kprobes.c+23−46

 static void __kprobes
 post_kprobe_handler(struct kprobe_ctlblk *, struct pt_regs *);
-static int __kprobes patch_text(kprobe_opcode_t *addr, u32 opcode)
-{
-	void *addrs[1];
-	u32 insns[1];
-	addrs[0] = addr;
-	insns[0] = opcode;
-	return aarch64_insn_patch_text(addrs, insns, 1);
-}
 static void __kprobes arch_prepare_ss_slot(struct kprobe *p)
 {
+	kprobe_opcode_t *addr = p->ainsn.api.insn;
+	void *addrs[] = {addr, addr + 1};
+	u32 insns[] = {p->opcode, BRK64_OPCODE_KPROBES_SS};
 	/* prepare insn slot */
-	patch_text(p->ainsn.api.insn, p->opcode);
+	aarch64_insn_patch_text(addrs, insns, 2);
-	flush_icache_range((uintptr_t) (p->ainsn.api.insn),
+	flush_icache_range((uintptr_t)addr, (uintptr_t)(addr + MAX_INSN_SIZE));
-			   (uintptr_t) (p->ainsn.api.insn) +
-			   MAX_INSN_SIZE * sizeof(kprobe_opcode_t));
 	/*
 	 * Needs restoring of return address after stepping xol.
 /* arm kprobe: install breakpoint in text */
 void __kprobes arch_arm_kprobe(struct kprobe *p)
 {
-	patch_text(p->addr, BRK64_OPCODE_KPROBES);
+	void *addr = p->addr;
+	u32 insn = BRK64_OPCODE_KPROBES;
+	aarch64_insn_patch_text(&addr, &insn, 1);
 }
 /* disarm kprobe: remove breakpoint from text */
 void __kprobes arch_disarm_kprobe(struct kprobe *p)
 {
-	patch_text(p->addr, p->opcode);
+	void *addr = p->addr;
+	aarch64_insn_patch_text(&addr, &p->opcode, 1);
 }
 void __kprobes arch_remove_kprobe(struct kprobe *p)
 }
 /*
- * Interrupts need to be disabled before single-step mode is set, and not
+ * Mask all of DAIF while executing the instruction out-of-line, to keep things
- * reenabled until after single-step mode ends.
+ * simple and avoid nesting exceptions. Interrupts do have to be disabled since
- * Without disabling interrupt on local CPU, there is a chance of
+ * the kprobe state is per-CPU and doesn't get migrated.
- * interrupt occurrence in the period of exception return and  start of
- * out-of-line single-step, that result in wrongly single stepping
- * into the interrupt handler.
  */
 static void __kprobes kprobes_save_local_irqflag(struct kprobe_ctlblk *kcb,
 						struct pt_regs *regs)
 {
 	kcb->saved_irqflag = regs->pstate & DAIF_MASK;
-	regs->pstate |= PSR_I_BIT;
+	regs->pstate |= DAIF_MASK;
-	/* Unmask PSTATE.D for enabling software step exceptions. */
-	regs->pstate &= ~PSR_D_BIT;
 }
 static void __kprobes kprobes_restore_local_irqflag(struct kprobe_ctlblk *kcb,
 		slot = (unsigned long)p->ainsn.api.insn;
 		set_ss_context(kcb, slot);	/* mark pending ss */
-		/* IRQs and single stepping do not mix well. */
 		kprobes_save_local_irqflag(kcb, regs);
-		kernel_enable_single_step(regs);
 		instruction_pointer_set(regs, slot);
 	} else {
 		/* insn simulation */
 	}
 	/* call post handler */
 	kcb->kprobe_status = KPROBE_HIT_SSDONE;
-	if (cur->post_handler)	{
+	if (cur->post_handler)
-		/* post_handler can hit breakpoint and single step
-		 * again, so we enable D-flag for recursive exception.
-		 */
 		cur->post_handler(cur, regs, 0);
-	}
 	reset_current_kprobe();
 }
 		if (!instruction_pointer(regs))
 			BUG();
-		kernel_disable_single_step();
 		if (kcb->kprobe_status == KPROBE_REENTER)
 			restore_previous_kprobe(kcb);
 		else
 			 * pre-handler and it returned non-zero, it will
 			 * modify the execution path and no need to single
 			 * stepping. Let's just reset current kprobe and exit.
-			 *
-			 * pre_handler can hit a breakpoint and can step thru
-			 * before return, keep PSTATE D-flag enabled until
-			 * pre_handler return back.
 			 */
 			if (!p->pre_handler || !p->pre_handler(p, regs)) {
 				setup_singlestep(p, regs, kcb, 0);
 }
 static int __kprobes
-kprobe_single_step_handler(struct pt_regs *regs, unsigned int esr)
+kprobe_breakpoint_ss_handler(struct pt_regs *regs, unsigned int esr)
 {
 	struct kprobe_ctlblk *kcb = get_kprobe_ctlblk();
 	int retval;
 	if (retval == DBG_HOOK_HANDLED) {
 		kprobes_restore_local_irqflag(kcb, regs);
-		kernel_disable_single_step();
 		post_kprobe_handler(kcb, regs);
 	}
 	return retval;
 }
-static struct step_hook kprobes_step_hook = {
+static struct break_hook kprobes_break_ss_hook = {
-	.fn = kprobe_single_step_handler,
+	.imm = KPROBES_BRK_SS_IMM,
+	.fn = kprobe_breakpoint_ss_handler,
 };
 static int __kprobes
 int __init arch_init_kprobes(void)
 {
 	register_kernel_break_hook(&kprobes_break_hook);
-	register_kernel_step_hook(&kprobes_step_hook);
+	register_kernel_break_hook(&kprobes_break_ss_hook);
 	return 0;
 }

arch/arm64/kernel/proton-pack.c+0−2

@@ -135,8 +135,6 @@ static enum mitigation_state spectre_v2_get_cpu_hw_mitigation_state(void) · 134 unmodified lines
135	return SPECTRE_VULNERABLE;	135	return SPECTRE_VULNERABLE;
136	}	136	}
137		137
138	#define SMCCC_ARCH_WORKAROUND_RET_UNAFFECTED (1)
139
140	static enum mitigation_state spectre_v2_get_cpu_fw_mitigation_state(void)	138	static enum mitigation_state spectre_v2_get_cpu_fw_mitigation_state(void)
141	{	139	{
142	int ret;	140	int ret;

arch/arm64/kernel/smp.c+1−0

@@ -222,6 +222,7 @@ asmlinkage notrace void secondary_start_kernel(void) · 221 unmodified lines
222	if (system_uses_irq_prio_masking())	222	if (system_uses_irq_prio_masking())
223	init_gic_priority_masking();	223	init_gic_priority_masking();
224		224
		225	rcu_cpu_starting(cpu);
225	preempt_disable();	226	preempt_disable();
226	trace_hardirqs_off();	227	trace_hardirqs_off();
227		228

arch/arm64/kernel/vdso32/Makefile+12−11

 CC_COMPAT ?= $(CC)
 CC_COMPAT += $(CC_COMPAT_CLANG_FLAGS)
+ifneq ($(LLVM),)
+LD_COMPAT ?= $(LD)
+else
+LD_COMPAT ?= $(CROSS_COMPILE_COMPAT)ld
+endif
 else
 CC_COMPAT ?= $(CROSS_COMPILE_COMPAT)gcc
+LD_COMPAT ?= $(CROSS_COMPILE_COMPAT)ld
 endif
 cc32-option = $(call try-run,\
         $(CC_COMPAT) $(1) -c -x c /dev/null -o "$$TMP",$(1),$(2))
 cc32-disable-warning = $(call try-run,\
 	$(CC_COMPAT) -W$(strip $(1)) -c -x c /dev/null -o "$$TMP",-Wno-$(strip $(1)))
-cc32-ldoption = $(call try-run,\
-        $(CC_COMPAT) $(1) -nostdlib -x c /dev/null -o "$$TMP",$(1),$(2))
 cc32-as-instr = $(call try-run,\
 	printf "%b\n" "$(1)" | $(CC_COMPAT) $(VDSO_AFLAGS) -c -x assembler -o "$$TMP" -,$(2),$(3))
 VDSO_CFLAGS += $(dmbinstr)
 VDSO_AFLAGS += $(dmbinstr)
-VDSO_LDFLAGS := $(VDSO_CPPFLAGS)
 # From arm vDSO Makefile
-VDSO_LDFLAGS += -Wl,-Bsymbolic -Wl,--no-undefined -Wl,-soname=linux-vdso.so.1
+VDSO_LDFLAGS += -Bsymbolic --no-undefined -soname=linux-vdso.so.1
-VDSO_LDFLAGS += -Wl,-z,max-page-size=4096 -Wl,-z,common-page-size=4096
+VDSO_LDFLAGS += -z max-page-size=4096 -z common-page-size=4096
-VDSO_LDFLAGS += -nostdlib -shared -mfloat-abi=soft
+VDSO_LDFLAGS += -nostdlib -shared --hash-style=sysv --build-id=sha1
-VDSO_LDFLAGS += -Wl,--hash-style=sysv
-VDSO_LDFLAGS += -Wl,--build-id=sha1
-VDSO_LDFLAGS += $(call cc32-ldoption,-fuse-ld=bfd)
 # Borrow vdsomunge.c from the arm vDSO
       cmd_vdsold_and_vdso_check = $(cmd_vdsold); $(cmd_vdso_check)
 quiet_cmd_vdsold = LD32    $@
-      cmd_vdsold = $(CC_COMPAT) -Wp,-MD,$(depfile) $(VDSO_LDFLAGS) \
+      cmd_vdsold = $(LD_COMPAT) $(VDSO_LDFLAGS) \
-                   -Wl,-T $(filter %.lds,$^) $(filter %.o,$^) -o $@
+                   -T $(filter %.lds,$^) $(filter %.o,$^) -o $@
 quiet_cmd_vdsocc = CC32    $@
       cmd_vdsocc = $(CC_COMPAT) -Wp,-MD,$(depfile) $(VDSO_CFLAGS) -c -o $@ $<
 quiet_cmd_vdsocc_gettimeofday = CC32    $@

arch/arm64/kernel/vmlinux.lds.S+1−1

@@ -278,7 +278,7 @@ SECTIONS · 277 unmodified lines
278	* explicitly check instead of blindly discarding.	278	* explicitly check instead of blindly discarding.
279	*/	279	*/
280	.plt : {	280	.plt : {
281	(.plt) (.plt.) (.iplt) *(.igot)	281	(.plt) (.plt.) (.iplt) *(.igot .igot.plt)
282	}	282	}
283	ASSERT(SIZEOF(.plt) == 0, "Unexpected run-time procedure linkages detected!")	283	ASSERT(SIZEOF(.plt) == 0, "Unexpected run-time procedure linkages detected!")
284		284

arch/arm64/kvm/arm.c+21−1

@@ -808,6 +808,25 @@ int kvm_arch_vcpu_ioctl_run(struct kvm_vcpu *vcpu) · 807 unmodified lines
808		808
809	preempt_enable();	809	preempt_enable();
810		810
		811	/*
		812	* The ARMv8 architecture doesn't give the hypervisor
		813	* a mechanism to prevent a guest from dropping to AArch32 EL0
		814	* if implemented by the CPU. If we spot the guest in such
		815	* state and that we decided it wasn't supposed to do so (like
		816	* with the asymmetric AArch32 case), return to userspace with
		817	* a fatal error.
		818	*/
		819	if (!system_supports_32bit_el0() && vcpu_mode_is_32bit(vcpu)) {
		820	/*
		821	* As we have caught the guest red-handed, decide that
		822	* it isn't fit for purpose anymore by making the vcpu
		823	* invalid. The VMM can try and fix it by issuing a
		824	* KVM_ARM_VCPU_INIT if it really wants to.
		825	*/
		826	vcpu->arch.target = -1;
		827	ret = ARM_EXCEPTION_IL;
		828	}
		829
811	ret = handle_exit(vcpu, ret);	830	ret = handle_exit(vcpu, ret);
812	}	831	}
813		832
@@ -1719,7 +1738,8 @@ int kvm_arch_init(void *opaque) · 905 unmodified lines
1719	return -ENODEV;	1738	return -ENODEV;
1720	}	1739	}
1721		1740
1722	if (cpus_have_final_cap(ARM64_WORKAROUND_DEVICE_LOAD_ACQUIRE))	1741	if (cpus_have_final_cap(ARM64_WORKAROUND_DEVICE_LOAD_ACQUIRE) \|\|
		1742	cpus_have_final_cap(ARM64_WORKAROUND_1508412))
1723	kvm_info("Guests without required CPU erratum workarounds can deadlock system!\n" \	1743	kvm_info("Guests without required CPU erratum workarounds can deadlock system!\n" \
1724	"Only trusted guests should be used on this system.\n");	1744	"Only trusted guests should be used on this system.\n");
1725		1745

arch/arm64/kvm/hyp/include/hyp/switch.h+13−8

 	 * We do need to save/restore PAR_EL1 though, as we haven't
 	 * saved the guest context yet, and we may return early...
 	 */
-	par = read_sysreg(par_el1);
+	par = read_sysreg_par();
 	if (!__kvm_at("s1e1r", far))
-		tmp = read_sysreg(par_el1);
+		tmp = read_sysreg_par();
 	else
 		tmp = SYS_PAR_EL1_F; /* back to the guest */
 	write_sysreg(par, par_el1);
 	if (cpus_have_final_cap(ARM64_WORKAROUND_CAVIUM_TX2_219_TVM) &&
 	    kvm_vcpu_trap_get_class(vcpu) == ESR_ELx_EC_SYS64 &&
 	    handle_tx2_tvm(vcpu))
-		return true;
+		goto guest;
 	/*
 	 * We trap the first access to the FP/SIMD to save the host context
 	 * Similarly for trapped SVE accesses.
 	 */
 	if (__hyp_handle_fpsimd(vcpu))
-		return true;
+		goto guest;
 	if (__hyp_handle_ptrauth(vcpu))
-		return true;
+		goto guest;
 	if (!__populate_fault_info(vcpu))
-		return true;
+		goto guest;
 	if (static_branch_unlikely(&vgic_v2_cpuif_trap)) {
 		bool valid;
 			int ret = __vgic_v2_perform_cpuif_access(vcpu);
 			if (ret == 1)
-				return true;
+				goto guest;
 			/* Promote an illegal access to an SError.*/
 			if (ret == -1)
 		int ret = __vgic_v3_perform_cpuif_access(vcpu);
 		if (ret == 1)
-			return true;
+			goto guest;
 	}
 exit:
 	/* Return to the host kernel and handle the exit */
 	return false;
+guest:
+	/* Re-enter the guest */
+	asm(ALTERNATIVE("nop", "dmb sy", ARM64_WORKAROUND_1508412));
+	return true;
 }
 static inline void __kvm_unexpected_el2_exception(void)

arch/arm64/kvm/hyp/include/hyp/sysreg-sr.h+1−1

@@ -43,7 +43,7 @@ static inline void __sysreg_save_el1_state(struct kvm_cpu_context *ctxt) · 42 unmodified lines
43	ctxt_sys_reg(ctxt, CONTEXTIDR_EL1) = read_sysreg_el1(SYS_CONTEXTIDR);	43	ctxt_sys_reg(ctxt, CONTEXTIDR_EL1) = read_sysreg_el1(SYS_CONTEXTIDR);
44	ctxt_sys_reg(ctxt, AMAIR_EL1) = read_sysreg_el1(SYS_AMAIR);	44	ctxt_sys_reg(ctxt, AMAIR_EL1) = read_sysreg_el1(SYS_AMAIR);
45	ctxt_sys_reg(ctxt, CNTKCTL_EL1) = read_sysreg_el1(SYS_CNTKCTL);	45	ctxt_sys_reg(ctxt, CNTKCTL_EL1) = read_sysreg_el1(SYS_CNTKCTL);
46	ctxt_sys_reg(ctxt, PAR_EL1) = read_sysreg(par_el1);	46	ctxt_sys_reg(ctxt, PAR_EL1) = read_sysreg_par();
47	ctxt_sys_reg(ctxt, TPIDR_EL1) = read_sysreg(tpidr_el1);	47	ctxt_sys_reg(ctxt, TPIDR_EL1) = read_sysreg(tpidr_el1);
48		48
49	ctxt_sys_reg(ctxt, SP_EL1) = read_sysreg(sp_el1);	49	ctxt_sys_reg(ctxt, SP_EL1) = read_sysreg(sp_el1);

arch/arm64/kvm/hyp/nvhe/host.S+0−2

@@ -17,8 +17,6 @@ SYM_FUNC_START(__host_exit) · 16 unmodified lines
17		17
18	get_host_ctxt x0, x1	18	get_host_ctxt x0, x1
19		19
20	ALTERNATIVE(nop, SET_PSTATE_PAN(1), ARM64_HAS_PAN, CONFIG_ARM64_PAN)
21
22	/* Store the host regs x2 and x3 */	20	/* Store the host regs x2 and x3 */
23	stp x2, x3, [x0, #CPU_XREG_OFFSET(2)]	21	stp x2, x3, [x0, #CPU_XREG_OFFSET(2)]
24		22

arch/arm64/kvm/hyp/nvhe/hyp-init.S+16−7

@@ -57,16 +57,25 @@ __do_hyp_init: · 56 unmodified lines
57	cmp x0, #HVC_STUB_HCALL_NR	57	cmp x0, #HVC_STUB_HCALL_NR
58	b.lo __kvm_handle_stub_hvc	58	b.lo __kvm_handle_stub_hvc
59		59
60	/* Set tpidr_el2 for use by HYP to free a register */	60	// We only actively check bits [24:31], and everything
61	msr tpidr_el2, x2	61	// else has to be zero, which we check at build time.
62		62	#if (KVM_HOST_SMCCC_FUNC(__kvm_hyp_init) & 0xFFFFFFFF00FFFFFF)
63	mov x2, #KVM_HOST_SMCCC_FUNC(__kvm_hyp_init)	63	#error Unexpected __KVM_HOST_SMCCC_FUNC___kvm_hyp_init value
64	cmp x0, x2	64	#endif
65	b.eq 1f	65
		66	ror x0, x0, #24
		67	eor x0, x0, #((KVM_HOST_SMCCC_FUNC(__kvm_hyp_init) >> 24) & 0xF)
		68	ror x0, x0, #4
		69	eor x0, x0, #((KVM_HOST_SMCCC_FUNC(__kvm_hyp_init) >> 28) & 0xF)
		70	cbz x0, 1f
66	mov x0, #SMCCC_RET_NOT_SUPPORTED	71	mov x0, #SMCCC_RET_NOT_SUPPORTED
67	eret	72	eret
68		73
69	1: phys_to_ttbr x0, x1	74	1:
		75	/* Set tpidr_el2 for use by HYP to free a register */
		76	msr tpidr_el2, x2
		77
		78	phys_to_ttbr x0, x1
70	alternative_if ARM64_HAS_CNP	79	alternative_if ARM64_HAS_CNP
71	orr x0, x0, #TTBR_CNP_BIT	80	orr x0, x0, #TTBR_CNP_BIT
72	alternative_else_nop_endif	81	alternative_else_nop_endif

arch/arm64/kvm/hyp/nvhe/switch.c+1−1

@@ -250,7 +250,7 @@ void __noreturn hyp_panic(void) · 249 unmodified lines
250	{	250	{
251	u64 spsr = read_sysreg_el2(SYS_SPSR);	251	u64 spsr = read_sysreg_el2(SYS_SPSR);
252	u64 elr = read_sysreg_el2(SYS_ELR);	252	u64 elr = read_sysreg_el2(SYS_ELR);
253	u64 par = read_sysreg(par_el1);	253	u64 par = read_sysreg_par();
254	bool restore_host = true;	254	bool restore_host = true;
255	struct kvm_cpu_context *host_ctxt;	255	struct kvm_cpu_context *host_ctxt;
256	struct kvm_vcpu *vcpu;	256	struct kvm_vcpu *vcpu;

arch/arm64/kvm/hyp/nvhe/tlb.c+0−1

@@ -128,7 +128,6 @@ void __kvm_tlb_flush_local_vmid(struct kvm_s2_mmu *mmu) · 127 unmodified lines
128	struct tlb_inv_context cxt;	128	struct tlb_inv_context cxt;
129		129
130	/* Switch to requested VMID */	130	/* Switch to requested VMID */
131	mmu = kern_hyp_va(mmu);
132	__tlb_switch_to_guest(mmu, &cxt);	131	__tlb_switch_to_guest(mmu, &cxt);
133		132
134	__tlbi(vmalle1);	133	__tlbi(vmalle1);

arch/arm64/kvm/hyp/pgtable.c+2−2

@@ -635,7 +635,7 @@ static void stage2_flush_dcache(void *addr, u64 size) · 634 unmodified lines
635		635
636	static bool stage2_pte_cacheable(kvm_pte_t pte)	636	static bool stage2_pte_cacheable(kvm_pte_t pte)
637	{	637	{
638	u64 memattr = FIELD_GET(KVM_PTE_LEAF_ATTR_LO_S2_MEMATTR, pte);	638	u64 memattr = pte & KVM_PTE_LEAF_ATTR_LO_S2_MEMATTR;
639	return memattr == PAGE_S2_MEMATTR(NORMAL);	639	return memattr == PAGE_S2_MEMATTR(NORMAL);
640	}	640	}
641		641
@@ -846,7 +846,7 @@ int kvm_pgtable_stage2_init(struct kvm_pgtable pgt, struct kvm kvm) · 204 unmodified lines
846	u32 start_level = VTCR_EL2_TGRAN_SL0_BASE - sl0;	846	u32 start_level = VTCR_EL2_TGRAN_SL0_BASE - sl0;
847		847
848	pgd_sz = kvm_pgd_pages(ia_bits, start_level) * PAGE_SIZE;	848	pgd_sz = kvm_pgd_pages(ia_bits, start_level) * PAGE_SIZE;
849	pgt->pgd = alloc_pages_exact(pgd_sz, GFP_KERNEL \| __GFP_ZERO);	849	pgt->pgd = alloc_pages_exact(pgd_sz, GFP_KERNEL_ACCOUNT \| __GFP_ZERO);
850	if (!pgt->pgd)	850	if (!pgt->pgd)
851	return -ENOMEM;	851	return -ENOMEM;
852		852

arch/arm64/kvm/hyp/vhe/switch.c+1−1

@@ -215,7 +215,7 @@ void __noreturn hyp_panic(void) · 214 unmodified lines
215	{	215	{
216	u64 spsr = read_sysreg_el2(SYS_SPSR);	216	u64 spsr = read_sysreg_el2(SYS_SPSR);
217	u64 elr = read_sysreg_el2(SYS_ELR);	217	u64 elr = read_sysreg_el2(SYS_ELR);
218	u64 par = read_sysreg(par_el1);	218	u64 par = read_sysreg_par();
219		219
220	__hyp_call_panic(spsr, elr, par);	220	__hyp_call_panic(spsr, elr, par);
221	unreachable();	221	unreachable();

arch/arm64/kvm/hypercalls.c+1−1

@@ -31,7 +31,7 @@ int kvm_hvc_call_handler(struct kvm_vcpu *vcpu) · 30 unmodified lines
31	val = SMCCC_RET_SUCCESS;	31	val = SMCCC_RET_SUCCESS;
32	break;	32	break;
33	case SPECTRE_UNAFFECTED:	33	case SPECTRE_UNAFFECTED:
34	val = SMCCC_RET_NOT_REQUIRED;	34	val = SMCCC_ARCH_WORKAROUND_RET_UNAFFECTED;
35	break;	35	break;
36	}	36	}
37	break;	37	break;

arch/arm64/kvm/mmu.c+20−7

@@ -787,14 +787,26 @@ static int user_mem_abort(struct kvm_vcpu *vcpu, phys_addr_t fault_ipa, · 786 unmodified lines
787	vma_shift = PAGE_SHIFT;	787	vma_shift = PAGE_SHIFT;
788	}	788	}
789		789
790	if (vma_shift == PUD_SHIFT &&	790	switch (vma_shift) {
791	!fault_supports_stage2_huge_mapping(memslot, hva, PUD_SIZE))	791	case PUD_SHIFT:
792	vma_shift = PMD_SHIFT;	792	if (fault_supports_stage2_huge_mapping(memslot, hva, PUD_SIZE))
793		793	break;
794	if (vma_shift == PMD_SHIFT &&	794	fallthrough;
795	!fault_supports_stage2_huge_mapping(memslot, hva, PMD_SIZE)) {	795	case CONT_PMD_SHIFT:
796	force_pte = true;	796	vma_shift = PMD_SHIFT;
		797	fallthrough;
		798	case PMD_SHIFT:
		799	if (fault_supports_stage2_huge_mapping(memslot, hva, PMD_SIZE))
		800	break;
		801	fallthrough;
		802	case CONT_PTE_SHIFT:
797	vma_shift = PAGE_SHIFT;	803	vma_shift = PAGE_SHIFT;
		804	force_pte = true;
		805	fallthrough;
		806	case PAGE_SHIFT:
		807	break;
		808	default:
		809	WARN_ONCE(1, "Unknown vma_shift %d", vma_shift);
798	}	810	}
799		811
800	vma_pagesize = 1UL << vma_shift;	812	vma_pagesize = 1UL << vma_shift;
@@ -839,6 +851,7 @@ static int user_mem_abort(struct kvm_vcpu *vcpu, phys_addr_t fault_ipa, · 38 unmodified lines
839		851
840	if (kvm_is_device_pfn(pfn)) {	852	if (kvm_is_device_pfn(pfn)) {
841	device = true;	853	device = true;
		854	force_pte = true;
842	} else if (logging_active && !write_fault) {	855	} else if (logging_active && !write_fault) {
843	/*	856	/*
844	* Only actually map the page as writable if this was a write	857	* Only actually map the page as writable if this was a write

arch/arm64/kvm/sys_regs.c+4−4

@@ -95,7 +95,7 @@ static bool __vcpu_read_sys_reg_from_cpu(int reg, u64 *val) · 94 unmodified lines
95	case AMAIR_EL1: *val = read_sysreg_s(SYS_AMAIR_EL12); break;	95	case AMAIR_EL1: *val = read_sysreg_s(SYS_AMAIR_EL12); break;
96	case CNTKCTL_EL1: *val = read_sysreg_s(SYS_CNTKCTL_EL12); break;	96	case CNTKCTL_EL1: *val = read_sysreg_s(SYS_CNTKCTL_EL12); break;
97	case ELR_EL1: *val = read_sysreg_s(SYS_ELR_EL12); break;	97	case ELR_EL1: *val = read_sysreg_s(SYS_ELR_EL12); break;
98	case PAR_EL1: *val = read_sysreg_s(SYS_PAR_EL1); break;	98	case PAR_EL1: *val = read_sysreg_par(); break;
99	case DACR32_EL2: *val = read_sysreg_s(SYS_DACR32_EL2); break;	99	case DACR32_EL2: *val = read_sysreg_s(SYS_DACR32_EL2); break;
100	case IFSR32_EL2: *val = read_sysreg_s(SYS_IFSR32_EL2); break;	100	case IFSR32_EL2: *val = read_sysreg_s(SYS_IFSR32_EL2); break;
101	case DBGVCR32_EL2: *val = read_sysreg_s(SYS_DBGVCR32_EL2); break;	101	case DBGVCR32_EL2: *val = read_sysreg_s(SYS_DBGVCR32_EL2); break;
@@ -1897,9 +1897,9 @@ static const struct sys_reg_desc cp14_regs[] = { · 1795 unmodified lines
1897	{ Op1( 0), CRn( 0), CRm( 1), Op2( 0), trap_raz_wi },	1897	{ Op1( 0), CRn( 0), CRm( 1), Op2( 0), trap_raz_wi },
1898	DBG_BCR_BVR_WCR_WVR(1),	1898	DBG_BCR_BVR_WCR_WVR(1),
1899	/* DBGDCCINT */	1899	/* DBGDCCINT */
1900	{ Op1( 0), CRn( 0), CRm( 2), Op2( 0), trap_debug32 },	1900	{ Op1( 0), CRn( 0), CRm( 2), Op2( 0), trap_debug32, NULL, cp14_DBGDCCINT },
1901	/* DBGDSCRext */	1901	/* DBGDSCRext */
1902	{ Op1( 0), CRn( 0), CRm( 2), Op2( 2), trap_debug32 },	1902	{ Op1( 0), CRn( 0), CRm( 2), Op2( 2), trap_debug32, NULL, cp14_DBGDSCRext },
1903	DBG_BCR_BVR_WCR_WVR(2),	1903	DBG_BCR_BVR_WCR_WVR(2),
1904	/* DBGDTR[RT]Xint */	1904	/* DBGDTR[RT]Xint */
1905	{ Op1( 0), CRn( 0), CRm( 3), Op2( 0), trap_raz_wi },	1905	{ Op1( 0), CRn( 0), CRm( 3), Op2( 0), trap_raz_wi },
@@ -1914,7 +1914,7 @@ static const struct sys_reg_desc cp14_regs[] = { · 8 unmodified lines
1914	{ Op1( 0), CRn( 0), CRm( 6), Op2( 2), trap_raz_wi },	1914	{ Op1( 0), CRn( 0), CRm( 6), Op2( 2), trap_raz_wi },
1915	DBG_BCR_BVR_WCR_WVR(6),	1915	DBG_BCR_BVR_WCR_WVR(6),
1916	/* DBGVCR */	1916	/* DBGVCR */
1917	{ Op1( 0), CRn( 0), CRm( 7), Op2( 0), trap_debug32 },	1917	{ Op1( 0), CRn( 0), CRm( 7), Op2( 0), trap_debug32, NULL, cp14_DBGVCR },
1918	DBG_BCR_BVR_WCR_WVR(7),	1918	DBG_BCR_BVR_WCR_WVR(7),
1919	DBG_BCR_BVR_WCR_WVR(8),	1919	DBG_BCR_BVR_WCR_WVR(8),
1920	DBG_BCR_BVR_WCR_WVR(9),	1920	DBG_BCR_BVR_WCR_WVR(9),

arch/arm64/lib/memcpy.S+1−2

 	stp \reg1, \reg2, [\ptr], \val
 	.endm
-	.weak memcpy
 SYM_FUNC_START_ALIAS(__memcpy)
-SYM_FUNC_START_PI(memcpy)
+SYM_FUNC_START_WEAK_PI(memcpy)
 #include "copy_template.S"
 	ret
 SYM_FUNC_END_PI(memcpy)

arch/arm64/lib/memmove.S+1−2

 D_l	.req	x13
 D_h	.req	x14
-	.weak memmove
 SYM_FUNC_START_ALIAS(__memmove)
-SYM_FUNC_START_PI(memmove)
+SYM_FUNC_START_WEAK_PI(memmove)
 	cmp	dstin, src
 	b.lo	__memcpy
 	add	tmp1, src, count

arch/arm64/lib/memset.S+1−2

 tmp3w		.req	w9
 tmp3		.req	x9
-	.weak memset
 SYM_FUNC_START_ALIAS(__memset)
-SYM_FUNC_START_PI(memset)
+SYM_FUNC_START_WEAK_PI(memset)
 	mov	dst, dstin	/* Preserve return value.  */
 	and	A_lw, val, #255
 	orr	A_lw, A_lw, A_lw, lsl #8

arch/arm64/mm/fault.c+1−1

@@ -262,7 +262,7 @@ static bool __kprobes is_spurious_el1_translation_fault(unsigned long addr, · 261 unmodified lines
262	local_irq_save(flags);	262	local_irq_save(flags);
263	asm volatile("at s1e1r, %0" :: "r" (addr));	263	asm volatile("at s1e1r, %0" :: "r" (addr));
264	isb();	264	isb();
265	par = read_sysreg(par_el1);	265	par = read_sysreg_par();
266	local_irq_restore(flags);	266	local_irq_restore(flags);
267		267
268	/*	268	/*

arch/s390/configs/debug_defconfig+6−4

 CONFIG_FRONTSWAP=y
 CONFIG_CMA_DEBUG=y
 CONFIG_CMA_DEBUGFS=y
+CONFIG_CMA_AREAS=7
 CONFIG_MEM_SOFT_DIRTY=y
 CONFIG_ZSWAP=y
-CONFIG_ZSMALLOC=m
+CONFIG_ZSMALLOC=y
 CONFIG_ZSMALLOC_STAT=y
 CONFIG_DEFERRED_STRUCT_PAGE_INIT=y
 CONFIG_IDLE_PAGE_TRACKING=y
 CONFIG_CGROUP_NET_PRIO=y
 CONFIG_BPF_JIT=y
 CONFIG_NET_PKTGEN=m
-# CONFIG_NET_DROP_MONITOR is not set
 CONFIG_PCI=y
 # CONFIG_PCIEASPM is not set
 CONFIG_PCI_DEBUG=y
 CONFIG_HOTPLUG_PCI_S390=y
 CONFIG_DEVTMPFS=y
 CONFIG_CONNECTOR=y
-CONFIG_ZRAM=m
+CONFIG_ZRAM=y
 CONFIG_BLK_DEV_LOOP=m
 CONFIG_BLK_DEV_CRYPTOLOOP=m
 CONFIG_BLK_DEV_DRBD=m
 CONFIG_CRYPTO_DH=m
 CONFIG_CRYPTO_ECDH=m
 CONFIG_CRYPTO_ECRDSA=m
+CONFIG_CRYPTO_SM2=m
 CONFIG_CRYPTO_CURVE25519=m
 CONFIG_CRYPTO_GCM=y
 CONFIG_CRYPTO_CHACHA20POLY1305=m
 CONFIG_CRYPTO_RMD256=m
 CONFIG_CRYPTO_RMD320=m
 CONFIG_CRYPTO_SHA3=m
-CONFIG_CRYPTO_SM3=m
 CONFIG_CRYPTO_TGR192=m
 CONFIG_CRYPTO_WP512=m
 CONFIG_CRYPTO_AES_TI=m
 CONFIG_CRYPTO_AES_S390=m
 CONFIG_CRYPTO_GHASH_S390=m
 CONFIG_CRYPTO_CRC32_S390=y
+CONFIG_CRYPTO_DEV_VIRTIO=m
 CONFIG_CORDIC=m
 CONFIG_CRC32_SELFTEST=y
 CONFIG_CRC4=m
 CONFIG_FAULT_INJECTION=y
 CONFIG_FAILSLAB=y
 CONFIG_FAIL_PAGE_ALLOC=y
+CONFIG_FAULT_INJECTION_USERCOPY=y
 CONFIG_FAIL_MAKE_REQUEST=y
 CONFIG_FAIL_IO_TIMEOUT=y
 CONFIG_FAIL_FUTEX=y

arch/s390/configs/defconfig+5−4

 CONFIG_TRANSPARENT_HUGEPAGE=y
 CONFIG_CLEANCACHE=y
 CONFIG_FRONTSWAP=y
+CONFIG_CMA_AREAS=7
 CONFIG_MEM_SOFT_DIRTY=y
 CONFIG_ZSWAP=y
-CONFIG_ZSMALLOC=m
+CONFIG_ZSMALLOC=y
 CONFIG_ZSMALLOC_STAT=y
 CONFIG_DEFERRED_STRUCT_PAGE_INIT=y
 CONFIG_IDLE_PAGE_TRACKING=y
 CONFIG_CGROUP_NET_PRIO=y
 CONFIG_BPF_JIT=y
 CONFIG_NET_PKTGEN=m
-# CONFIG_NET_DROP_MONITOR is not set
 CONFIG_PCI=y
 # CONFIG_PCIEASPM is not set
 CONFIG_HOTPLUG_PCI=y
 CONFIG_UEVENT_HELPER=y
 CONFIG_DEVTMPFS=y
 CONFIG_CONNECTOR=y
-CONFIG_ZRAM=m
+CONFIG_ZRAM=y
 CONFIG_BLK_DEV_LOOP=m
 CONFIG_BLK_DEV_CRYPTOLOOP=m
 CONFIG_BLK_DEV_DRBD=m
 CONFIG_CRYPTO_DH=m
 CONFIG_CRYPTO_ECDH=m
 CONFIG_CRYPTO_ECRDSA=m
+CONFIG_CRYPTO_SM2=m
 CONFIG_CRYPTO_CURVE25519=m
 CONFIG_CRYPTO_GCM=y
 CONFIG_CRYPTO_CHACHA20POLY1305=m
 CONFIG_CRYPTO_RMD256=m
 CONFIG_CRYPTO_RMD320=m
 CONFIG_CRYPTO_SHA3=m
-CONFIG_CRYPTO_SM3=m
 CONFIG_CRYPTO_TGR192=m
 CONFIG_CRYPTO_WP512=m
 CONFIG_CRYPTO_AES_TI=m
 CONFIG_CRYPTO_AES_S390=m
 CONFIG_CRYPTO_GHASH_S390=m
 CONFIG_CRYPTO_CRC32_S390=y
+CONFIG_CRYPTO_DEV_VIRTIO=m
 CONFIG_CORDIC=m
 CONFIG_PRIME_NUMBERS=m
 CONFIG_CRC4=m

arch/s390/configs/zfcpdump_defconfig+1−1

 # CONFIG_CHSC_SCH is not set
 # CONFIG_SCM_BUS is not set
 CONFIG_CRASH_DUMP=y
-# CONFIG_SECCOMP is not set
 # CONFIG_PFAULT is not set
 # CONFIG_S390_HYPFS_FS is not set
 # CONFIG_VIRTUALIZATION is not set
 # CONFIG_S390_GUEST is not set
+# CONFIG_SECCOMP is not set
 CONFIG_PARTITION_ADVANCED=y
 CONFIG_IBM_PARTITION=y
 # CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS is not set

arch/s390/include/asm/pgtable.h+30−22

 	return !!(pud_val(pud) & _REGION3_ENTRY_LARGE);
 }
-static inline unsigned long pud_pfn(pud_t pud)
-{
-	unsigned long origin_mask;
-	origin_mask = _REGION_ENTRY_ORIGIN;
-	if (pud_large(pud))
-		origin_mask = _REGION3_ENTRY_ORIGIN_LARGE;
-	return (pud_val(pud) & origin_mask) >> PAGE_SHIFT;
-}
 #define pmd_leaf	pmd_large
 static inline int pmd_large(pmd_t pmd)
 {
 	return pmd_val(pmd) == _SEGMENT_ENTRY_EMPTY;
 }
-static inline unsigned long pmd_pfn(pmd_t pmd)
-{
-	unsigned long origin_mask;
-	origin_mask = _SEGMENT_ENTRY_ORIGIN;
-	if (pmd_large(pmd))
-		origin_mask = _SEGMENT_ENTRY_ORIGIN_LARGE;
-	return (pmd_val(pmd) & origin_mask) >> PAGE_SHIFT;
-}
 #define pmd_write pmd_write
 static inline int pmd_write(pmd_t pmd)
 {
 #define pud_index(address) (((address) >> PUD_SHIFT) & (PTRS_PER_PUD-1))
 #define pmd_index(address) (((address) >> PMD_SHIFT) & (PTRS_PER_PMD-1))
-#define pmd_deref(pmd) (pmd_val(pmd) & _SEGMENT_ENTRY_ORIGIN)
-#define pud_deref(pud) (pud_val(pud) & _REGION_ENTRY_ORIGIN)
 #define p4d_deref(pud) (p4d_val(pud) & _REGION_ENTRY_ORIGIN)
 #define pgd_deref(pgd) (pgd_val(pgd) & _REGION_ENTRY_ORIGIN)
+static inline unsigned long pmd_deref(pmd_t pmd)
+{
+	unsigned long origin_mask;
+	origin_mask = _SEGMENT_ENTRY_ORIGIN;
+	if (pmd_large(pmd))
+		origin_mask = _SEGMENT_ENTRY_ORIGIN_LARGE;
+	return pmd_val(pmd) & origin_mask;
+}
+static inline unsigned long pmd_pfn(pmd_t pmd)
+{
+	return pmd_deref(pmd) >> PAGE_SHIFT;
+}
+static inline unsigned long pud_deref(pud_t pud)
+{
+	unsigned long origin_mask;
+	origin_mask = _REGION_ENTRY_ORIGIN;
+	if (pud_large(pud))
+		origin_mask = _REGION3_ENTRY_ORIGIN_LARGE;
+	return pud_val(pud) & origin_mask;
+}
+static inline unsigned long pud_pfn(pud_t pud)
+{
+	return pud_deref(pud) >> PAGE_SHIFT;
+}
 /*
  * The pgd_offset function *always* adds the index for the top-level
  * region/segment table. This is done to get a sequence like the

arch/s390/include/asm/vdso/vdso.h+0−0

Empty file deleted.

arch/s390/kernel/asm-offsets.c+0−8

@@ -61,14 +61,6 @@ int main(void) · 60 unmodified lines
61	BLANK();	61	BLANK();
62	OFFSET(__VDSO_GETCPU_VAL, vdso_per_cpu_data, getcpu_val);	62	OFFSET(__VDSO_GETCPU_VAL, vdso_per_cpu_data, getcpu_val);
63	BLANK();	63	BLANK();
64	/* constants used by the vdso */
65	DEFINE(__CLOCK_REALTIME, CLOCK_REALTIME);
66	DEFINE(__CLOCK_MONOTONIC, CLOCK_MONOTONIC);
67	DEFINE(__CLOCK_REALTIME_COARSE, CLOCK_REALTIME_COARSE);
68	DEFINE(__CLOCK_MONOTONIC_COARSE, CLOCK_MONOTONIC_COARSE);
69	DEFINE(__CLOCK_THREAD_CPUTIME_ID, CLOCK_THREAD_CPUTIME_ID);
70	DEFINE(__CLOCK_COARSE_RES, LOW_RES_NSEC);
71	BLANK();
72	/* idle data offsets */	64	/* idle data offsets */
73	OFFSET(__CLOCK_IDLE_ENTER, s390_idle_data, clock_idle_enter);	65	OFFSET(__CLOCK_IDLE_ENTER, s390_idle_data, clock_idle_enter);
74	OFFSET(__CLOCK_IDLE_EXIT, s390_idle_data, clock_idle_exit);	66	OFFSET(__CLOCK_IDLE_EXIT, s390_idle_data, clock_idle_exit);

arch/s390/kernel/smp.c+2−1

 static void smp_init_secondary(void)
 {
-	int cpu = smp_processor_id();
+	int cpu = raw_smp_processor_id();
 	S390_lowcore.last_update_clock = get_tod_clock();
 	restore_access_regs(S390_lowcore.access_regs_save_area);
 	set_cpu_flag(CIF_ASCE_PRIMARY);
 	set_cpu_flag(CIF_ASCE_SECONDARY);
 	cpu_init();
+	rcu_cpu_starting(cpu);
 	preempt_disable();
 	init_cpu_timer();
 	vtime_init();

arch/s390/pci/pci_event.c+4−0

 		if (ret)
 			break;
+		/* the PCI function will be scanned once function 0 appears */
+		if (!zdev->zbus->bus)
+			break;
 		pdev = pci_scan_single_device(zdev->zbus->bus, zdev->devfn);
 		if (!pdev)
 			break;

arch/x86/boot/compressed/ident_map_64.c+1−0

@@ -164,6 +164,7 @@ void initialize_identity_maps(void *rmode) · 163 unmodified lines
164	add_identity_map(cmdline, cmdline + COMMAND_LINE_SIZE);	164	add_identity_map(cmdline, cmdline + COMMAND_LINE_SIZE);
165		165
166	/* Load the new page-table. */	166	/* Load the new page-table. */
		167	sev_verify_cbit(top_level_pgt);
167	write_cr3(top_level_pgt);	168	write_cr3(top_level_pgt);
168	}	169	}
169		170

arch/x86/boot/compressed/mem_encrypt.S+19−1

@@ -68,6 +68,9 @@ SYM_FUNC_START(get_sev_encryption_bit) · 67 unmodified lines
68	SYM_FUNC_END(get_sev_encryption_bit)	68	SYM_FUNC_END(get_sev_encryption_bit)
69		69
70	.code64	70	.code64
		71
		72	#include "../../kernel/sev_verify_cbit.S"
		73
71	SYM_FUNC_START(set_sev_encryption_mask)	74	SYM_FUNC_START(set_sev_encryption_mask)
72	#ifdef CONFIG_AMD_MEM_ENCRYPT	75	#ifdef CONFIG_AMD_MEM_ENCRYPT
73	push %rbp	76	push %rbp
@@ -81,6 +84,19 @@ SYM_FUNC_START(set_sev_encryption_mask) · 7 unmodified lines
81		84
82	bts %rax, sme_me_mask(%rip) /* Create the encryption mask */	85	bts %rax, sme_me_mask(%rip) /* Create the encryption mask */
83		86
		87	/*
		88	* Read MSR_AMD64_SEV again and store it to sev_status. Can't do this in
		89	* get_sev_encryption_bit() because this function is 32-bit code and
		90	* shared between 64-bit and 32-bit boot path.
		91	*/
		92	movl $MSR_AMD64_SEV, %ecx /* Read the SEV MSR */
		93	rdmsr
		94
		95	/* Store MSR value in sev_status */
		96	shlq $32, %rdx
		97	orq %rdx, %rax
		98	movq %rax, sev_status(%rip)
		99
84	.Lno_sev_mask:	100	.Lno_sev_mask:
85	movq %rbp, %rsp /* Restore original stack pointer */	101	movq %rbp, %rsp /* Restore original stack pointer */
86		102
@@ -96,5 +112,7 @@ SYM_FUNC_END(set_sev_encryption_mask) · 9 unmodified lines
96		112
97	#ifdef CONFIG_AMD_MEM_ENCRYPT	113	#ifdef CONFIG_AMD_MEM_ENCRYPT
98	.balign 8	114	.balign 8
99	SYM_DATA(sme_me_mask, .quad 0)	115	SYM_DATA(sme_me_mask, .quad 0)
		116	SYM_DATA(sev_status, .quad 0)
		117	SYM_DATA(sev_check_data, .quad 0)
100	#endif	118	#endif

arch/x86/boot/compressed/misc.h+2−0

@@ -159,4 +159,6 @@ void boot_page_fault(void); · 158 unmodified lines
159	void boot_stage1_vc(void);	159	void boot_stage1_vc(void);
160	void boot_stage2_vc(void);	160	void boot_stage2_vc(void);
161		161
		162	unsigned long sev_verify_cbit(unsigned long cr3);
		163
162	#endif /* BOOT_COMPRESSED_MISC_H */	164	#endif /* BOOT_COMPRESSED_MISC_H */

arch/x86/hyperv/hv_apic.c+9−5

 		pr_info("Hyper-V: Using enlightened APIC (%s mode)",
 			x2apic_enabled() ? "x2apic" : "xapic");
 		/*
-		 * With x2apic, architectural x2apic MSRs are equivalent to the
+		 * When in x2apic mode, don't use the Hyper-V specific APIC
-		 * respective synthetic MSRs, so there's no need to override
+		 * accessors since the field layout in the ICR register is
-		 * the apic accessors.  The only exception is
+		 * different in x2apic mode. Furthermore, the architectural
-		 * hv_apic_eoi_write, because it benefits from lazy EOI when
+		 * x2apic MSRs function just as well as the Hyper-V
-		 * available, but it works for both xapic and x2apic modes.
+		 * synthetic APIC MSRs, so there's no benefit in having
+		 * separate Hyper-V accessors for x2apic mode. The only
+		 * exception is hv_apic_eoi_write, because it benefits from
+		 * lazy EOI when available, but the same accessor works for
+		 * both xapic and x2apic because the field layout is the same.
 		 */
 		apic_set_eoi_write(hv_apic_eoi_write);
 		if (!x2apic_enabled()) {

arch/x86/include/uapi/asm/kvm_para.h+1−0

@@ -32,6 +32,7 @@ · 31 unmodified lines
32	#define KVM_FEATURE_POLL_CONTROL 12	32	#define KVM_FEATURE_POLL_CONTROL 12
33	#define KVM_FEATURE_PV_SCHED_YIELD 13	33	#define KVM_FEATURE_PV_SCHED_YIELD 13
34	#define KVM_FEATURE_ASYNC_PF_INT 14	34	#define KVM_FEATURE_ASYNC_PF_INT 14
		35	#define KVM_FEATURE_MSI_EXT_DEST_ID 15
35		36
36	#define KVM_HINTS_REALTIME 0	37	#define KVM_HINTS_REALTIME 0
37		38

arch/x86/kernel/head_64.S+16−0

@@ -161,6 +161,21 @@ SYM_INNER_LABEL(secondary_startup_64_no_verify, SYM_L_GLOBAL) · 160 unmodified lines
161		161
162	/* Setup early boot stage 4-/5-level pagetables. */	162	/* Setup early boot stage 4-/5-level pagetables. */
163	addq phys_base(%rip), %rax	163	addq phys_base(%rip), %rax
		164
		165	/*
		166	* For SEV guests: Verify that the C-bit is correct. A malicious
		167	* hypervisor could lie about the C-bit position to perform a ROP
		168	* attack on the guest by writing to the unencrypted stack and wait for
		169	* the next RET instruction.
		170	* %rsi carries pointer to realmode data and is callee-clobbered. Save
		171	* and restore it.
		172	*/
		173	pushq %rsi
		174	movq %rax, %rdi
		175	call sev_verify_cbit
		176	popq %rsi
		177
		178	/* Switch to new page-table */
164	movq %rax, %cr3	179	movq %rax, %cr3
165		180
166	/* Ensure I am executing from virtual addresses */	181	/* Ensure I am executing from virtual addresses */
@@ -279,6 +294,7 @@ SYM_INNER_LABEL(secondary_startup_64_no_verify, SYM_L_GLOBAL) · 112 unmodified lines
279	SYM_CODE_END(secondary_startup_64)	294	SYM_CODE_END(secondary_startup_64)
280		295
281	#include "verify_cpu.S"	296	#include "verify_cpu.S"
		297	#include "sev_verify_cbit.S"
282		298
283	#ifdef CONFIG_HOTPLUG_CPU	299	#ifdef CONFIG_HOTPLUG_CPU
284	/*	300	/*

arch/x86/kernel/sev-es-shared.c+26−0

@@ -178,6 +178,32 @@ void __init do_vc_no_ghcb(struct pt_regs *regs, unsigned long exit_code) · 177 unmodified lines
178	goto fail;	178	goto fail;
179	regs->dx = val >> 32;	179	regs->dx = val >> 32;
180		180
		181	/*
		182	* This is a VC handler and the #VC is only raised when SEV-ES is
		183	* active, which means SEV must be active too. Do sanity checks on the
		184	* CPUID results to make sure the hypervisor does not trick the kernel
		185	* into the no-sev path. This could map sensitive data unencrypted and
		186	* make it accessible to the hypervisor.
		187	*
		188	* In particular, check for:
		189	* - Hypervisor CPUID bit
		190	* - Availability of CPUID leaf 0x8000001f
		191	* - SEV CPUID bit.
		192	*
		193	* The hypervisor might still report the wrong C-bit position, but this
		194	* can't be checked here.
		195	*/
		196
		197	if ((fn == 1 && !(regs->cx & BIT(31))))
		198	/* Hypervisor bit */
		199	goto fail;
		200	else if (fn == 0x80000000 && (regs->ax < 0x8000001f))
		201	/* SEV leaf check */
		202	goto fail;
		203	else if ((fn == 0x8000001f && !(regs->ax & BIT(1))))
		204	/* SEV bit */
		205	goto fail;
		206
181	/* Skip over the CPUID two-byte opcode */	207	/* Skip over the CPUID two-byte opcode */
182	regs->ip += 2;	208	regs->ip += 2;
183		209

arch/x86/kernel/sev-es.c+13−7

 	return ES_EXCEPTION;
 }
-static bool vc_slow_virt_to_phys(struct ghcb *ghcb, struct es_em_ctxt *ctxt,
+static enum es_result vc_slow_virt_to_phys(struct ghcb *ghcb, struct es_em_ctxt *ctxt,
-				 unsigned long vaddr, phys_addr_t *paddr)
+					   unsigned long vaddr, phys_addr_t *paddr)
 {
 	unsigned long va = (unsigned long)vaddr;
 	unsigned int level;
 		if (user_mode(ctxt->regs))
 			ctxt->fi.error_code |= X86_PF_USER;
-		return false;
+		return ES_EXCEPTION;
 	}
+	if (WARN_ON_ONCE(pte_val(*pte) & _PAGE_ENC))
+		/* Emulated MMIO to/from encrypted memory not supported */
+		return ES_UNSUPPORTED;
 	pa = (phys_addr_t)pte_pfn(*pte) << PAGE_SHIFT;
 	pa |= va & ~page_level_mask(level);
 	*paddr = pa;
-	return true;
+	return ES_OK;
 }
 /* Include code shared with pre-decompression boot stage */
 {
 	u64 exit_code, exit_info_1, exit_info_2;
 	unsigned long ghcb_pa = __pa(ghcb);
+	enum es_result res;
 	phys_addr_t paddr;
 	void __user *ref;
 	exit_code = read ? SVM_VMGEXIT_MMIO_READ : SVM_VMGEXIT_MMIO_WRITE;
-	if (!vc_slow_virt_to_phys(ghcb, ctxt, (unsigned long)ref, &paddr)) {
+	res = vc_slow_virt_to_phys(ghcb, ctxt, (unsigned long)ref, &paddr);
-		if (!read)
+	if (res != ES_OK) {
+		if (res == ES_EXCEPTION && !read)
 			ctxt->fi.error_code |= X86_PF_WRITE;
-		return ES_EXCEPTION;
+		return res;
 	}
 	exit_info_1 = paddr;

arch/x86/kernel/sev_verify_cbit.S+89−0

@@ -0,0 +1,89 @@
	1	/* SPDX-License-Identifier: GPL-2.0-only */
	2	/*
	3	* sev_verify_cbit.S - Code for verification of the C-bit position reported
	4	* by the Hypervisor when running with SEV enabled.
	5	*
	6	* Copyright (c) 2020 Joerg Roedel (jroedel@suse.de)
	7	*
	8	* sev_verify_cbit() is called before switching to a new long-mode page-table
	9	* at boot.
	10	*
	11	* Verify that the C-bit position is correct by writing a random value to
	12	* an encrypted memory location while on the current page-table. Then it
	13	* switches to the new page-table to verify the memory content is still the
	14	* same. After that it switches back to the current page-table and when the
	15	* check succeeded it returns. If the check failed the code invalidates the
	16	* stack pointer and goes into a hlt loop. The stack-pointer is invalidated to
	17	* make sure no interrupt or exception can get the CPU out of the hlt loop.
	18	*
	19	* New page-table pointer is expected in %rdi (first parameter)
	20	*
	21	*/
	22	SYM_FUNC_START(sev_verify_cbit)
	23	#ifdef CONFIG_AMD_MEM_ENCRYPT
	24	/* First check if a C-bit was detected */
	25	movq sme_me_mask(%rip), %rsi
	26	testq %rsi, %rsi
	27	jz 3f
	28
	29	/* sme_me_mask != 0 could mean SME or SEV - Check also for SEV */
	30	movq sev_status(%rip), %rsi
	31	testq %rsi, %rsi
	32	jz 3f
	33
	34	/* Save CR4 in %rsi */
	35	movq %cr4, %rsi
	36
	37	/* Disable Global Pages */
	38	movq %rsi, %rdx
	39	andq $(~X86_CR4_PGE), %rdx
	40	movq %rdx, %cr4
	41
	42	/*
	43	* Verified that running under SEV - now get a random value using
	44	* RDRAND. This instruction is mandatory when running as an SEV guest.
	45	*
	46	* Don't bail out of the loop if RDRAND returns errors. It is better to
	47	* prevent forward progress than to work with a non-random value here.
	48	*/
	49	1: rdrand %rdx
	50	jnc 1b
	51
	52	/* Store value to memory and keep it in %rdx */
	53	movq %rdx, sev_check_data(%rip)
	54
	55	/* Backup current %cr3 value to restore it later */
	56	movq %cr3, %rcx
	57
	58	/* Switch to new %cr3 - This might unmap the stack */
	59	movq %rdi, %cr3
	60
	61	/*
	62	* Compare value in %rdx with memory location. If C-bit is incorrect
	63	* this would read the encrypted data and make the check fail.
	64	*/
	65	cmpq %rdx, sev_check_data(%rip)
	66
	67	/* Restore old %cr3 */
	68	movq %rcx, %cr3
	69
	70	/* Restore previous CR4 */
	71	movq %rsi, %cr4
	72
	73	/* Check CMPQ result */
	74	je 3f
	75
	76	/*
	77	* The check failed, prevent any forward progress to prevent ROP
	78	* attacks, invalidate the stack and go into a hlt loop.
	79	*/
	80	xorq %rsp, %rsp
	81	subq $0x1000, %rsp
	82	2: hlt
	83	jmp 2b
	84	3:
	85	#endif
	86	/* Return page-table pointer */
	87	movq %rdi, %rax
	88	ret
	89	SYM_FUNC_END(sev_verify_cbit)

arch/x86/kernel/traps.c+30−13

 	set_debugreg(DR6_RESERVED, 6);
 	dr6 ^= DR6_RESERVED; /* Flip to positive polarity */
-	/*
-	 * Clear the virtual DR6 value, ptrace routines will set bits here for
-	 * things we want signals for.
-	 */
-	current->thread.virtual_dr6 = 0;
-	/*
-	 * The SDM says "The processor clears the BTF flag when it
-	 * generates a debug exception."  Clear TIF_BLOCKSTEP to keep
-	 * TIF_BLOCKSTEP in sync with the hardware BTF flag.
-	 */
-	clear_thread_flag(TIF_BLOCKSTEP);
 	return dr6;
 }
 	 */
 	WARN_ON_ONCE(user_mode(regs));
+	if (test_thread_flag(TIF_BLOCKSTEP)) {
+		/*
+		 * The SDM says "The processor clears the BTF flag when it
+		 * generates a debug exception." but PTRACE_BLOCKSTEP requested
+		 * it for userspace, but we just took a kernel #DB, so re-set
+		 * BTF.
+		 */
+		unsigned long debugctl;
+		rdmsrl(MSR_IA32_DEBUGCTLMSR, debugctl);
+		debugctl |= DEBUGCTLMSR_BTF;
+		wrmsrl(MSR_IA32_DEBUGCTLMSR, debugctl);
+	}
 	/*
 	 * Catch SYSENTER with TF set and clear DR_STEP. If this hit a
 	 * watchpoint at the same time then that will still be handled.
 	irqentry_enter_from_user_mode(regs);
 	instrumentation_begin();
+	/*
+	 * Start the virtual/ptrace DR6 value with just the DR_STEP mask
+	 * of the real DR6. ptrace_triggered() will set the DR_TRAPn bits.
+	 *
+	 * Userspace expects DR_STEP to be visible in ptrace_get_debugreg(6)
+	 * even if it is not the result of PTRACE_SINGLESTEP.
+	 */
+	current->thread.virtual_dr6 = (dr6 & DR_STEP);
+	/*
+	 * The SDM says "The processor clears the BTF flag when it
+	 * generates a debug exception."  Clear TIF_BLOCKSTEP to keep
+	 * TIF_BLOCKSTEP in sync with the hardware BTF flag.
+	 */
+	clear_thread_flag(TIF_BLOCKSTEP);
 	/*
 	 * If dr6 has no reason to give us about the origin of this trap,
 	 * then it's very likely the result of an icebp/int01 trap.

arch/x86/kvm/mmu/mmu.c+5−5

@@ -225,7 +225,7 @@ static gfn_t get_mmio_spte_gfn(u64 spte) · 224 unmodified lines
225	{	225	{
226	u64 gpa = spte & shadow_nonpresent_or_rsvd_lower_gfn_mask;	226	u64 gpa = spte & shadow_nonpresent_or_rsvd_lower_gfn_mask;
227		227
228	gpa \|= (spte >> shadow_nonpresent_or_rsvd_mask_len)	228	gpa \|= (spte >> SHADOW_NONPRESENT_OR_RSVD_MASK_LEN)
229	& shadow_nonpresent_or_rsvd_mask;	229	& shadow_nonpresent_or_rsvd_mask;
230		230
231	return gpa >> PAGE_SHIFT;	231	return gpa >> PAGE_SHIFT;
@@ -591,15 +591,15 @@ static u64 mmu_spte_get_lockless(u64 *sptep) · 359 unmodified lines
591	static u64 restore_acc_track_spte(u64 spte)	591	static u64 restore_acc_track_spte(u64 spte)
592	{	592	{
593	u64 new_spte = spte;	593	u64 new_spte = spte;
594	u64 saved_bits = (spte >> shadow_acc_track_saved_bits_shift)	594	u64 saved_bits = (spte >> SHADOW_ACC_TRACK_SAVED_BITS_SHIFT)
595	& shadow_acc_track_saved_bits_mask;	595	& SHADOW_ACC_TRACK_SAVED_BITS_MASK;
596		596
597	WARN_ON_ONCE(spte_ad_enabled(spte));	597	WARN_ON_ONCE(spte_ad_enabled(spte));
598	WARN_ON_ONCE(!is_access_track_spte(spte));	598	WARN_ON_ONCE(!is_access_track_spte(spte));
599		599
600	new_spte &= ~shadow_acc_track_mask;	600	new_spte &= ~shadow_acc_track_mask;
601	new_spte &= ~(shadow_acc_track_saved_bits_mask <<	601	new_spte &= ~(SHADOW_ACC_TRACK_SAVED_BITS_MASK <<
602	shadow_acc_track_saved_bits_shift);	602	SHADOW_ACC_TRACK_SAVED_BITS_SHIFT);
603	new_spte \|= saved_bits;	603	new_spte \|= saved_bits;
604		604
605	return new_spte;	605	return new_spte;

arch/x86/kvm/mmu/spte.c+8−8

@@ -55,7 +55,7 @@ u64 make_mmio_spte(struct kvm_vcpu *vcpu, u64 gfn, unsigned int access) · 54 unmodified lines
55	mask \|= shadow_mmio_value \| access;	55	mask \|= shadow_mmio_value \| access;
56	mask \|= gpa \| shadow_nonpresent_or_rsvd_mask;	56	mask \|= gpa \| shadow_nonpresent_or_rsvd_mask;
57	mask \|= (gpa & shadow_nonpresent_or_rsvd_mask)	57	mask \|= (gpa & shadow_nonpresent_or_rsvd_mask)
58	<< shadow_nonpresent_or_rsvd_mask_len;	58	<< SHADOW_NONPRESENT_OR_RSVD_MASK_LEN;
59		59
60	return mask;	60	return mask;
61	}	61	}
@@ -231,12 +231,12 @@ u64 mark_spte_for_access_track(u64 spte) · 169 unmodified lines
231	!spte_can_locklessly_be_made_writable(spte),	231	!spte_can_locklessly_be_made_writable(spte),
232	"kvm: Writable SPTE is not locklessly dirty-trackable\n");	232	"kvm: Writable SPTE is not locklessly dirty-trackable\n");
233		233
234	WARN_ONCE(spte & (shadow_acc_track_saved_bits_mask <<	234	WARN_ONCE(spte & (SHADOW_ACC_TRACK_SAVED_BITS_MASK <<
235	shadow_acc_track_saved_bits_shift),	235	SHADOW_ACC_TRACK_SAVED_BITS_SHIFT),
236	"kvm: Access Tracking saved bit locations are not zero\n");	236	"kvm: Access Tracking saved bit locations are not zero\n");
237		237
238	spte \|= (spte & shadow_acc_track_saved_bits_mask) <<	238	spte \|= (spte & SHADOW_ACC_TRACK_SAVED_BITS_MASK) <<
239	shadow_acc_track_saved_bits_shift;	239	SHADOW_ACC_TRACK_SAVED_BITS_SHIFT;
240	spte &= ~shadow_acc_track_mask;	240	spte &= ~shadow_acc_track_mask;
241		241
242	return spte;	242	return spte;
@@ -245,7 +245,7 @@ u64 mark_spte_for_access_track(u64 spte) · 2 unmodified lines
245	void kvm_mmu_set_mmio_spte_mask(u64 mmio_value, u64 access_mask)	245	void kvm_mmu_set_mmio_spte_mask(u64 mmio_value, u64 access_mask)
246	{	246	{
247	BUG_ON((u64)(unsigned)access_mask != access_mask);	247	BUG_ON((u64)(unsigned)access_mask != access_mask);
248	WARN_ON(mmio_value & (shadow_nonpresent_or_rsvd_mask << shadow_nonpresent_or_rsvd_mask_len));	248	WARN_ON(mmio_value & (shadow_nonpresent_or_rsvd_mask << SHADOW_NONPRESENT_OR_RSVD_MASK_LEN));
249	WARN_ON(mmio_value & shadow_nonpresent_or_rsvd_lower_gfn_mask);	249	WARN_ON(mmio_value & shadow_nonpresent_or_rsvd_lower_gfn_mask);
250	shadow_mmio_value = mmio_value \| SPTE_MMIO_MASK;	250	shadow_mmio_value = mmio_value \| SPTE_MMIO_MASK;
251	shadow_mmio_access_mask = access_mask;	251	shadow_mmio_access_mask = access_mask;
@@ -306,9 +306,9 @@ void kvm_mmu_reset_all_pte_masks(void) · 54 unmodified lines
306	low_phys_bits = boot_cpu_data.x86_phys_bits;	306	low_phys_bits = boot_cpu_data.x86_phys_bits;
307	if (boot_cpu_has_bug(X86_BUG_L1TF) &&	307	if (boot_cpu_has_bug(X86_BUG_L1TF) &&
308	!WARN_ON_ONCE(boot_cpu_data.x86_cache_bits >=	308	!WARN_ON_ONCE(boot_cpu_data.x86_cache_bits >=
309	52 - shadow_nonpresent_or_rsvd_mask_len)) {	309	52 - SHADOW_NONPRESENT_OR_RSVD_MASK_LEN)) {
310	low_phys_bits = boot_cpu_data.x86_cache_bits	310	low_phys_bits = boot_cpu_data.x86_cache_bits
311	- shadow_nonpresent_or_rsvd_mask_len;	311	- SHADOW_NONPRESENT_OR_RSVD_MASK_LEN;
312	shadow_nonpresent_or_rsvd_mask =	312	shadow_nonpresent_or_rsvd_mask =
313	rsvd_bits(low_phys_bits, boot_cpu_data.x86_cache_bits - 1);	313	rsvd_bits(low_phys_bits, boot_cpu_data.x86_cache_bits - 1);
314	}	314	}

arch/x86/kvm/mmu/spte.h+8−8

  */
 extern u64 __read_mostly shadow_nonpresent_or_rsvd_mask;
+/*
+ * The number of high-order 1 bits to use in the mask above.
+ */
+#define SHADOW_NONPRESENT_OR_RSVD_MASK_LEN 5
 /*
  * The mask/shift to use for saving the original R/X bits when marking the PTE
  * as not-present for access tracking purposes. We do not save the W bit as the
  * PTEs being access tracked also need to be dirty tracked, so the W bit will be
  * restored only when a write is attempted to the page.
  */
-static const u64 shadow_acc_track_saved_bits_mask = PT64_EPT_READABLE_MASK |
+#define SHADOW_ACC_TRACK_SAVED_BITS_MASK (PT64_EPT_READABLE_MASK | \
-						    PT64_EPT_EXECUTABLE_MASK;
+					  PT64_EPT_EXECUTABLE_MASK)
-static const u64 shadow_acc_track_saved_bits_shift = PT64_SECOND_AVAIL_BITS_SHIFT;
+#define SHADOW_ACC_TRACK_SAVED_BITS_SHIFT PT64_SECOND_AVAIL_BITS_SHIFT
-/*
- * The number of high-order 1 bits to use in the mask above.
- */
-static const u64 shadow_nonpresent_or_rsvd_mask_len = 5;
 /*
  * In some cases, we need to preserve the GFN of a non-present or reserved

arch/x86/kvm/vmx/evmcs.c+1−2

@@ -297,14 +297,13 @@ const struct evmcs_field vmcs_field_to_evmcs_1[] = { · 296 unmodified lines
297	};	297	};
298	const unsigned int nr_evmcs_1_fields = ARRAY_SIZE(vmcs_field_to_evmcs_1);	298	const unsigned int nr_evmcs_1_fields = ARRAY_SIZE(vmcs_field_to_evmcs_1);
299		299
300	void evmcs_sanitize_exec_ctrls(struct vmcs_config *vmcs_conf)	300	__init void evmcs_sanitize_exec_ctrls(struct vmcs_config *vmcs_conf)
301	{	301	{
302	vmcs_conf->pin_based_exec_ctrl &= ~EVMCS1_UNSUPPORTED_PINCTRL;	302	vmcs_conf->pin_based_exec_ctrl &= ~EVMCS1_UNSUPPORTED_PINCTRL;
303	vmcs_conf->cpu_based_2nd_exec_ctrl &= ~EVMCS1_UNSUPPORTED_2NDEXEC;	303	vmcs_conf->cpu_based_2nd_exec_ctrl &= ~EVMCS1_UNSUPPORTED_2NDEXEC;
304		304
305	vmcs_conf->vmexit_ctrl &= ~EVMCS1_UNSUPPORTED_VMEXIT_CTRL;	305	vmcs_conf->vmexit_ctrl &= ~EVMCS1_UNSUPPORTED_VMEXIT_CTRL;
306	vmcs_conf->vmentry_ctrl &= ~EVMCS1_UNSUPPORTED_VMENTRY_CTRL;	306	vmcs_conf->vmentry_ctrl &= ~EVMCS1_UNSUPPORTED_VMENTRY_CTRL;
307
308	}	307	}
309	#endif	308	#endif
310		309

arch/x86/kvm/vmx/evmcs.h+1−2

 	vp_ap->enlighten_vmentry = 1;
 }
-void evmcs_sanitize_exec_ctrls(struct vmcs_config *vmcs_conf);
+__init void evmcs_sanitize_exec_ctrls(struct vmcs_config *vmcs_conf);
 #else /* !IS_ENABLED(CONFIG_HYPERV) */
 static inline void evmcs_write64(unsigned long field, u64 value) {}
 static inline void evmcs_write32(unsigned long field, u32 value) {}
 static inline u32 evmcs_read32(unsigned long field) { return 0; }
 static inline u16 evmcs_read16(unsigned long field) { return 0; }
 static inline void evmcs_load(u64 phys_addr) {}
-static inline void evmcs_sanitize_exec_ctrls(struct vmcs_config *vmcs_conf) {}
 static inline void evmcs_touch_msr_bitmap(void) {}
 #endif /* IS_ENABLED(CONFIG_HYPERV) */

arch/x86/kvm/vmx/vmx.c+3−3

 	vmcs_conf->vmexit_ctrl         = _vmexit_control;
 	vmcs_conf->vmentry_ctrl        = _vmentry_control;
-	if (static_branch_unlikely(&enable_evmcs))
+#if IS_ENABLED(CONFIG_HYPERV)
+	if (enlightened_vmcs)
 		evmcs_sanitize_exec_ctrls(vmcs_conf);
+#endif
 	return 0;
 }
 static int vmx_create_vcpu(struct kvm_vcpu *vcpu)
 {
 	struct vcpu_vmx *vmx;
-	unsigned long *msr_bitmap;
 	int i, cpu, err;
 	BUILD_BUG_ON(offsetof(struct vcpu_vmx, vcpu) != 0);
 	bitmap_fill(vmx->shadow_msr_intercept.read, MAX_POSSIBLE_PASSTHROUGH_MSRS);
 	bitmap_fill(vmx->shadow_msr_intercept.write, MAX_POSSIBLE_PASSTHROUGH_MSRS);
-	msr_bitmap = vmx->vmcs01.msr_bitmap;
 	vmx_disable_intercept_for_msr(vcpu, MSR_IA32_TSC, MSR_TYPE_R);
 	vmx_disable_intercept_for_msr(vcpu, MSR_FS_BASE, MSR_TYPE_RW);
 	vmx_disable_intercept_for_msr(vcpu, MSR_GS_BASE, MSR_TYPE_RW);

arch/x86/kvm/x86.c+4−4

@@ -265,13 +265,13 @@ static int kvm_msr_ignored_check(struct kvm_vcpu *vcpu, u32 msr, · 264 unmodified lines
265		265
266	if (ignore_msrs) {	266	if (ignore_msrs) {
267	if (report_ignored_msrs)	267	if (report_ignored_msrs)
268	vcpu_unimpl(vcpu, "ignored %s: 0x%x data 0x%llx\n",	268	kvm_pr_unimpl("ignored %s: 0x%x data 0x%llx\n",
269	op, msr, data);	269	op, msr, data);
270	/* Mask the error */	270	/* Mask the error */
271	return 0;	271	return 0;
272	} else {	272	} else {
273	vcpu_debug_ratelimited(vcpu, "unhandled %s: 0x%x data 0x%llx\n",	273	kvm_debug_ratelimited("unhandled %s: 0x%x data 0x%llx\n",
274	op, msr, data);	274	op, msr, data);
275	return -ENOENT;	275	return -ENOENT;
276	}	276	}
277	}	277	}

arch/x86/mm/mem_encrypt.c+1−0

@@ -39,6 +39,7 @@ · 38 unmodified lines
39	*/	39	*/
40	u64 sme_me_mask __section(".data") = 0;	40	u64 sme_me_mask __section(".data") = 0;
41	u64 sev_status __section(".data") = 0;	41	u64 sev_status __section(".data") = 0;
		42	u64 sev_check_data __section(".data") = 0;
42	EXPORT_SYMBOL(sme_me_mask);	43	EXPORT_SYMBOL(sme_me_mask);
43	DEFINE_STATIC_KEY_FALSE(sev_enable_key);	44	DEFINE_STATIC_KEY_FALSE(sev_enable_key);
44	EXPORT_SYMBOL_GPL(sev_enable_key);	45	EXPORT_SYMBOL_GPL(sev_enable_key);

arch/xtensa/mm/init.c+2−2

@@ -89,8 +89,8 @@ static void __init free_highpages(void) · 88 unmodified lines
89	/* set highmem page free */	89	/* set highmem page free */
90	for_each_free_mem_range(i, NUMA_NO_NODE, MEMBLOCK_NONE,	90	for_each_free_mem_range(i, NUMA_NO_NODE, MEMBLOCK_NONE,
91	&range_start, &range_end, NULL) {	91	&range_start, &range_end, NULL) {
92	unsigned long start = PHYS_PFN(range_start);	92	unsigned long start = PFN_UP(range_start);
93	unsigned long end = PHYS_PFN(range_end);	93	unsigned long end = PFN_DOWN(range_end);
94		94
95	/* Ignore complete lowmem entries */	95	/* Ignore complete lowmem entries */
96	if (end <= max_low)	96	if (end <= max_low)

block/bio.c+7−4

 	ssize_t size, left;
 	unsigned len, i;
 	size_t offset;
+	int ret = 0;
 	if (WARN_ON_ONCE(!max_append_sectors))
 		return 0;
 		len = min_t(size_t, PAGE_SIZE - offset, left);
 		if (bio_add_hw_page(q, bio, page, len, offset,
-				max_append_sectors, &same_page) != len)
+				max_append_sectors, &same_page) != len) {
-			return -EINVAL;
+			ret = -EINVAL;
+			break;
+		}
 		if (same_page)
 			put_page(page);
 		offset = 0;
 	}
-	iov_iter_advance(iter, size);
+	iov_iter_advance(iter, size - left);
-	return 0;
+	return ret;
 }
 /**

block/blk-cgroup.c+13−2

 			goto fail;
 		}
+		if (radix_tree_preload(GFP_KERNEL)) {
+			blkg_free(new_blkg);
+			ret = -ENOMEM;
+			goto fail;
+		}
 		rcu_read_lock();
 		spin_lock_irq(&q->queue_lock);
 		blkg = blkg_lookup_check(pos, pol, q);
 		if (IS_ERR(blkg)) {
 			ret = PTR_ERR(blkg);
-			goto fail_unlock;
+			blkg_free(new_blkg);
+			goto fail_preloaded;
 		}
 		if (blkg) {
 			blkg = blkg_create(pos, q, new_blkg);
 			if (IS_ERR(blkg)) {
 				ret = PTR_ERR(blkg);
-				goto fail_unlock;
+				goto fail_preloaded;
 			}
 		}
+		radix_tree_preload_end();
 		if (pos == blkcg)
 			goto success;
 	}
 	ctx->body = input;
 	return 0;
+fail_preloaded:
+	radix_tree_preload_end();
 fail_unlock:
 	spin_unlock_irq(&q->queue_lock);
 	rcu_read_unlock();

block/blk-flush.c+1−0

@@ -225,6 +225,7 @@ static void flush_end_io(struct request *flush_rq, blk_status_t error) · 224 unmodified lines
225	/* release the tag's ownership to the req cloned from */	225	/* release the tag's ownership to the req cloned from */
226	spin_lock_irqsave(&fq->mq_flush_lock, flags);	226	spin_lock_irqsave(&fq->mq_flush_lock, flags);
227		227
		228	WRITE_ONCE(flush_rq->state, MQ_RQ_IDLE);
228	if (!refcount_dec_and_test(&flush_rq->ref)) {	229	if (!refcount_dec_and_test(&flush_rq->ref)) {
229	fq->rq_status = error;	230	fq->rq_status = error;
230	spin_unlock_irqrestore(&fq->mq_flush_lock, flags);	231	spin_unlock_irqrestore(&fq->mq_flush_lock, flags);

drivers/acpi/button.c+0−13

@@ -73,19 +73,6 @@ MODULE_DEVICE_TABLE(acpi, button_device_ids); · 72 unmodified lines
73		73
74	/* Please keep this list sorted alphabetically by vendor and model */	74	/* Please keep this list sorted alphabetically by vendor and model */
75	static const struct dmi_system_id dmi_lid_quirks[] = {	75	static const struct dmi_system_id dmi_lid_quirks[] = {
76	{
77	/*
78	* Acer Switch 10 SW5-012. _LID method messes with home and
79	* power button GPIO IRQ settings causing an interrupt storm on
80	* both GPIOs. This is unfixable without a DSDT override, so we
81	* have to disable the lid-switch functionality altogether :\|
82	*/
83	.matches = {
84	DMI_MATCH(DMI_SYS_VENDOR, "Acer"),
85	DMI_MATCH(DMI_PRODUCT_NAME, "Aspire SW5-012"),
86	},
87	.driver_data = (void *)(long)ACPI_BUTTON_LID_INIT_DISABLED,
88	},
89	{	76	{
90	/* GP-electronic T701, _LID method points to a floating GPIO */	77	/* GP-electronic T701, _LID method points to a floating GPIO */
91	.matches = {	78	.matches = {

drivers/acpi/dock.c+2−1

@@ -231,7 +231,8 @@ static void hot_remove_dock_devices(struct dock_station *ds) · 230 unmodified lines
231	* between them).	231	* between them).
232	*/	232	*/
233	list_for_each_entry_reverse(dd, &ds->dependent_devices, list)	233	list_for_each_entry_reverse(dd, &ds->dependent_devices, list)
234	dock_hotplug_event(dd, ACPI_NOTIFY_EJECT_REQUEST, false);	234	dock_hotplug_event(dd, ACPI_NOTIFY_EJECT_REQUEST,
		235	DOCK_CALL_HANDLER);
235		236
236	list_for_each_entry_reverse(dd, &ds->dependent_devices, list)	237	list_for_each_entry_reverse(dd, &ds->dependent_devices, list)
237	acpi_bus_trim(dd->adev);	238	acpi_bus_trim(dd->adev);

drivers/acpi/nfit/core.c+1−1

@@ -1564,7 +1564,7 @@ static ssize_t format1_show(struct device *dev, · 1563 unmodified lines
1564	le16_to_cpu(nfit_dcr->dcr->code));	1564	le16_to_cpu(nfit_dcr->dcr->code));
1565	break;	1565	break;
1566	}	1566	}
1567	if (rc != ENXIO)	1567	if (rc != -ENXIO)
1568	break;	1568	break;
1569	}	1569	}
1570	mutex_unlock(&acpi_desc->init_mutex);	1570	mutex_unlock(&acpi_desc->init_mutex);

drivers/ata/sata_nv.c+1−1

@@ -2100,7 +2100,7 @@ static int nv_swncq_sdbfis(struct ata_port *ap) · 2099 unmodified lines
2100	pp->dhfis_bits &= ~done_mask;	2100	pp->dhfis_bits &= ~done_mask;
2101	pp->dmafis_bits &= ~done_mask;	2101	pp->dmafis_bits &= ~done_mask;
2102	pp->sdbfis_bits \|= done_mask;	2102	pp->sdbfis_bits \|= done_mask;
2103	ata_qc_complete_multiple(ap, ap->qc_active ^ done_mask);	2103	ata_qc_complete_multiple(ap, ata_qc_get_active(ap) ^ done_mask);
2104		2104
2105	if (!ap->qc_active) {	2105	if (!ap->qc_active) {
2106	DPRINTK("over\n");	2106	DPRINTK("over\n");

drivers/base/core.c+5−5

 	dev_dbg(link->consumer, "Dropping the link to %s\n",
 		dev_name(link->supplier));
-	if (link->flags & DL_FLAG_PM_RUNTIME)
+	pm_runtime_drop_link(link);
-		pm_runtime_drop_link(link->consumer);
 	list_del_rcu(&link->s_node);
 	list_del_rcu(&link->c_node);
 	dev_info(link->consumer, "Dropping the link to %s\n",
 		 dev_name(link->supplier));
-	if (link->flags & DL_FLAG_PM_RUNTIME)
+	pm_runtime_drop_link(link);
-		pm_runtime_drop_link(link->consumer);
 	list_del(&link->s_node);
 	list_del(&link->c_node);
  */
 void set_primary_fwnode(struct device *dev, struct fwnode_handle *fwnode)
 {
+	struct device *parent = dev->parent;
 	struct fwnode_handle *fn = dev->fwnode;
 	if (fwnode) {
 	} else {
 		if (fwnode_is_primary(fn)) {
 			dev->fwnode = fn->secondary;
-			fn->secondary = NULL;
+			if (!(parent && fn == parent->fwnode))
+				fn->secondary = ERR_PTR(-ENODEV);
 		} else {
 			dev->fwnode = NULL;
 		}

drivers/base/dd.c+5−4

 	drv = dev->driver;
 	if (drv) {
+		pm_runtime_get_sync(dev);
 		while (device_links_busy(dev)) {
 			__device_driver_unlock(dev, parent);
 			 * have released the driver successfully while this one
 			 * was waiting, so check for that.
 			 */
-			if (dev->driver != drv)
+			if (dev->driver != drv) {
+				pm_runtime_put(dev);
 				return;
+			}
 		}
-		pm_runtime_get_sync(dev);
-		pm_runtime_clean_up_links(dev);
 		driver_sysfs_remove(dev);
 		if (dev->bus)

drivers/base/power/runtime.c+20−37

 	pm_runtime_reinit(dev);
 }
-/**
- * pm_runtime_clean_up_links - Prepare links to consumers for driver removal.
- * @dev: Device whose driver is going to be removed.
- *
- * Check links from this device to any consumers and if any of them have active
- * runtime PM references to the device, drop the usage counter of the device
- * (as many times as needed).
- *
- * Links with the DL_FLAG_MANAGED flag unset are ignored.
- *
- * Since the device is guaranteed to be runtime-active at the point this is
- * called, nothing else needs to be done here.
- *
- * Moreover, this is called after device_links_busy() has returned 'false', so
- * the status of each link is guaranteed to be DL_STATE_SUPPLIER_UNBIND and
- * therefore rpm_active can't be manipulated concurrently.
- */
-void pm_runtime_clean_up_links(struct device *dev)
-{
-	struct device_link *link;
-	int idx;
-	idx = device_links_read_lock();
-	list_for_each_entry_rcu(link, &dev->links.consumers, s_node,
-				device_links_read_lock_held()) {
-		if (!(link->flags & DL_FLAG_MANAGED))
-			continue;
-		while (refcount_dec_not_one(&link->rpm_active))
-			pm_runtime_put_noidle(dev);
-	}
-	device_links_read_unlock(idx);
-}
 /**
  * pm_runtime_get_suppliers - Resume and reference-count supplier devices.
  * @dev: Consumer device.
 	spin_unlock_irq(&dev->power.lock);
 }
-void pm_runtime_drop_link(struct device *dev)
+static void pm_runtime_drop_link_count(struct device *dev)
 {
 	spin_lock_irq(&dev->power.lock);
 	WARN_ON(dev->power.links_count == 0);
 	spin_unlock_irq(&dev->power.lock);
 }
+/**
+ * pm_runtime_drop_link - Prepare for device link removal.
+ * @link: Device link going away.
+ *
+ * Drop the link count of the consumer end of @link and decrement the supplier
+ * device's runtime PM usage counter as many times as needed to drop all of the
+ * PM runtime reference to it from the consumer.
+ */
+void pm_runtime_drop_link(struct device_link *link)
+{
+	if (!(link->flags & DL_FLAG_PM_RUNTIME))
+		return;
+	pm_runtime_drop_link_count(link->consumer);
+	while (refcount_dec_not_one(&link->rpm_active))
+		pm_runtime_put(link->supplier);
+}
 static bool pm_runtime_need_not_resume(struct device *dev)
 {
 	return atomic_read(&dev->power.usage_count) <= 1 &&

drivers/block/nbd.c+5−4

 	}
 }
-static void nbd_size_update(struct nbd_device *nbd)
+static void nbd_size_update(struct nbd_device *nbd, bool start)
 {
 	struct nbd_config *config = nbd->config;
 	struct block_device *bdev = bdget_disk(nbd->disk, 0);
 	if (bdev) {
 		if (bdev->bd_disk) {
 			bd_set_nr_sectors(bdev, nr_sectors);
-			set_blocksize(bdev, config->blksize);
+			if (start)
+				set_blocksize(bdev, config->blksize);
 		} else
 			set_bit(GD_NEED_PART_SCAN, &nbd->disk->state);
 		bdput(bdev);
 	config->blksize = blocksize;
 	config->bytesize = blocksize * nr_blocks;
 	if (nbd->task_recv != NULL)
-		nbd_size_update(nbd);
+		nbd_size_update(nbd, false);
 }
 static void nbd_complete_rq(struct request *req)
 		args->index = i;
 		queue_work(nbd->recv_workq, &args->work);
 	}
-	nbd_size_update(nbd);
+	nbd_size_update(nbd, true);
 	return error;
 }

drivers/block/null_blk.h+2−0

@@ -47,6 +47,8 @@ struct nullb_device { · 46 unmodified lines
47	unsigned int nr_zones_closed;	47	unsigned int nr_zones_closed;
48	struct blk_zone *zones;	48	struct blk_zone *zones;
49	sector_t zone_size_sects;	49	sector_t zone_size_sects;
		50	spinlock_t zone_dev_lock;
		51	unsigned long *zone_locks;
50		52
51	unsigned long size; /* device size in MB */	53	unsigned long size; /* device size in MB */
52	unsigned long completion_nsec; /* time in ns to complete a request */	54	unsigned long completion_nsec; /* time in ns to complete a request */

drivers/block/null_blk_zoned.c+99−24

 // SPDX-License-Identifier: GPL-2.0
 #include <linux/vmalloc.h>
+#include <linux/bitmap.h>
 #include "null_blk.h"
 #define CREATE_TRACE_POINTS
 	if (!dev->zones)
 		return -ENOMEM;
+	spin_lock_init(&dev->zone_dev_lock);
+	dev->zone_locks = bitmap_zalloc(dev->nr_zones, GFP_KERNEL);
+	if (!dev->zone_locks) {
+		kvfree(dev->zones);
+		return -ENOMEM;
+	}
 	if (dev->zone_nr_conv >= dev->nr_zones) {
 		dev->zone_nr_conv = dev->nr_zones - 1;
 		pr_info("changed the number of conventional zones to %u",
 void null_free_zoned_dev(struct nullb_device *dev)
 {
+	bitmap_free(dev->zone_locks);
 	kvfree(dev->zones);
 }
+static inline void null_lock_zone(struct nullb_device *dev, unsigned int zno)
+{
+	wait_on_bit_lock_io(dev->zone_locks, zno, TASK_UNINTERRUPTIBLE);
+}
+static inline void null_unlock_zone(struct nullb_device *dev, unsigned int zno)
+{
+	clear_and_wake_up_bit(zno, dev->zone_locks);
+}
 int null_report_zones(struct gendisk *disk, sector_t sector,
 		unsigned int nr_zones, report_zones_cb cb, void *data)
 {
 	struct nullb *nullb = disk->private_data;
 	struct nullb_device *dev = nullb->dev;
-	unsigned int first_zone, i;
+	unsigned int first_zone, i, zno;
 	struct blk_zone zone;
 	int error;
 	nr_zones = min(nr_zones, dev->nr_zones - first_zone);
 	trace_nullb_report_zones(nullb, nr_zones);
-	for (i = 0; i < nr_zones; i++) {
+	zno = first_zone;
+	for (i = 0; i < nr_zones; i++, zno++) {
 		/*
 		 * Stacked DM target drivers will remap the zone information by
 		 * modifying the zone information passed to the report callback.
 		 * So use a local copy to avoid corruption of the device zone
 		 * array.
 		 */
-		memcpy(&zone, &dev->zones[first_zone + i],
+		null_lock_zone(dev, zno);
-		       sizeof(struct blk_zone));
+		memcpy(&zone, &dev->zones[zno], sizeof(struct blk_zone));
+		null_unlock_zone(dev, zno);
 		error = cb(&zone, i, data);
 		if (error)
 			return error;
 	return nr_zones;
 }
+/*
+ * This is called in the case of memory backing from null_process_cmd()
+ * with the target zone already locked.
+ */
 size_t null_zone_valid_read_len(struct nullb *nullb,
 				sector_t sector, unsigned int len)
 {
 	if (zone->type == BLK_ZONE_TYPE_CONVENTIONAL)
 		return null_process_cmd(cmd, REQ_OP_WRITE, sector, nr_sectors);
+	null_lock_zone(dev, zno);
+	spin_lock(&dev->zone_dev_lock);
 	switch (zone->cond) {
 	case BLK_ZONE_COND_FULL:
 		/* Cannot write to a full zone */
-		return BLK_STS_IOERR;
+		ret = BLK_STS_IOERR;
+		goto unlock;
 	case BLK_ZONE_COND_EMPTY:
 	case BLK_ZONE_COND_CLOSED:
 		ret = null_check_zone_resources(dev, zone);
 		if (ret != BLK_STS_OK)
-			return ret;
+			goto unlock;
 		break;
 	case BLK_ZONE_COND_IMP_OPEN:
 	case BLK_ZONE_COND_EXP_OPEN:
 		break;
 	default:
 		/* Invalid zone condition */
-		return BLK_STS_IOERR;
+		ret = BLK_STS_IOERR;
+		goto unlock;
 	}
 	/*
 		else
 			cmd->rq->__sector = sector;
 	} else if (sector != zone->wp) {
-		return BLK_STS_IOERR;
+		ret = BLK_STS_IOERR;
+		goto unlock;
 	}
-	if (zone->wp + nr_sectors > zone->start + zone->capacity)
+	if (zone->wp + nr_sectors > zone->start + zone->capacity) {
-		return BLK_STS_IOERR;
+		ret = BLK_STS_IOERR;
+		goto unlock;
+	}
 	if (zone->cond == BLK_ZONE_COND_CLOSED) {
 		dev->nr_zones_closed--;
 	if (zone->cond != BLK_ZONE_COND_EXP_OPEN)
 		zone->cond = BLK_ZONE_COND_IMP_OPEN;
+	spin_unlock(&dev->zone_dev_lock);
 	ret = null_process_cmd(cmd, REQ_OP_WRITE, sector, nr_sectors);
+	spin_lock(&dev->zone_dev_lock);
 	if (ret != BLK_STS_OK)
-		return ret;
+		goto unlock;
 	zone->wp += nr_sectors;
 	if (zone->wp == zone->start + zone->capacity) {
 			dev->nr_zones_imp_open--;
 		zone->cond = BLK_ZONE_COND_FULL;
 	}
-	return BLK_STS_OK;
+	ret = BLK_STS_OK;
+unlock:
+	spin_unlock(&dev->zone_dev_lock);
+	null_unlock_zone(dev, zno);
+	return ret;
 }
 static blk_status_t null_open_zone(struct nullb_device *dev, struct blk_zone *zone)
 				   sector_t sector)
 {
 	struct nullb_device *dev = cmd->nq->dev;
-	unsigned int zone_no = null_zone_no(dev, sector);
+	unsigned int zone_no;
-	struct blk_zone *zone = &dev->zones[zone_no];
+	struct blk_zone *zone;
-	blk_status_t ret = BLK_STS_OK;
+	blk_status_t ret;
 	size_t i;
+	if (op == REQ_OP_ZONE_RESET_ALL) {
+		for (i = dev->zone_nr_conv; i < dev->nr_zones; i++) {
+			null_lock_zone(dev, i);
+			zone = &dev->zones[i];
+			if (zone->cond != BLK_ZONE_COND_EMPTY) {
+				spin_lock(&dev->zone_dev_lock);
+				null_reset_zone(dev, zone);
+				spin_unlock(&dev->zone_dev_lock);
+				trace_nullb_zone_op(cmd, i, zone->cond);
+			}
+			null_unlock_zone(dev, i);
+		}
+		return BLK_STS_OK;
+	}
+	zone_no = null_zone_no(dev, sector);
+	zone = &dev->zones[zone_no];
+	null_lock_zone(dev, zone_no);
+	spin_lock(&dev->zone_dev_lock);
 	switch (op) {
-	case REQ_OP_ZONE_RESET_ALL:
-		for (i = dev->zone_nr_conv; i < dev->nr_zones; i++)
-			null_reset_zone(dev, &dev->zones[i]);
-		break;
 	case REQ_OP_ZONE_RESET:
 		ret = null_reset_zone(dev, zone);
 		break;
 		ret = null_finish_zone(dev, zone);
 		break;
 	default:
-		return BLK_STS_NOTSUPP;
+		ret = BLK_STS_NOTSUPP;
+		break;
 	}
+	spin_unlock(&dev->zone_dev_lock);
 	if (ret == BLK_STS_OK)
 		trace_nullb_zone_op(cmd, zone_no, zone->cond);
+	null_unlock_zone(dev, zone_no);
 	return ret;
 }
 blk_status_t null_process_zoned_cmd(struct nullb_cmd *cmd, enum req_opf op,
 				    sector_t sector, sector_t nr_sectors)
 {
+	struct nullb_device *dev = cmd->nq->dev;
+	unsigned int zno = null_zone_no(dev, sector);
+	blk_status_t sts;
 	switch (op) {
 	case REQ_OP_WRITE:
-		return null_zone_write(cmd, sector, nr_sectors, false);
+		sts = null_zone_write(cmd, sector, nr_sectors, false);
+		break;
 	case REQ_OP_ZONE_APPEND:
-		return null_zone_write(cmd, sector, nr_sectors, true);
+		sts = null_zone_write(cmd, sector, nr_sectors, true);
+		break;
 	case REQ_OP_ZONE_RESET:
 	case REQ_OP_ZONE_RESET_ALL:
 	case REQ_OP_ZONE_OPEN:
 	case REQ_OP_ZONE_CLOSE:
 	case REQ_OP_ZONE_FINISH:
-		return null_zone_mgmt(cmd, op, sector);
+		sts = null_zone_mgmt(cmd, op, sector);
+		break;
 	default:
-		return null_process_cmd(cmd, op, sector, nr_sectors);
+		null_lock_zone(dev, zno);
+		sts = null_process_cmd(cmd, op, sector, nr_sectors);
+		null_unlock_zone(dev, zno);
 	}
+	return sts;
 }

drivers/block/xsysace.c+26−23

@@ -443,22 +443,27 @@ static void ace_fix_driveid(u16 *id) · 442 unmodified lines
443	#define ACE_FSM_NUM_STATES 11	443	#define ACE_FSM_NUM_STATES 11
444		444
445	/* Set flag to exit FSM loop and reschedule tasklet */	445	/* Set flag to exit FSM loop and reschedule tasklet */
446	static inline void ace_fsm_yield(struct ace_device *ace)	446	static inline void ace_fsm_yieldpoll(struct ace_device *ace)
447	{	447	{
448	dev_dbg(ace->dev, "ace_fsm_yield()\n");
449	tasklet_schedule(&ace->fsm_tasklet);	448	tasklet_schedule(&ace->fsm_tasklet);
450	ace->fsm_continue_flag = 0;	449	ace->fsm_continue_flag = 0;
451	}	450	}
452		451
		452	static inline void ace_fsm_yield(struct ace_device *ace)
		453	{
		454	dev_dbg(ace->dev, "%s()\n", __func__);
		455	ace_fsm_yieldpoll(ace);
		456	}
		457
453	/* Set flag to exit FSM loop and wait for IRQ to reschedule tasklet */	458	/* Set flag to exit FSM loop and wait for IRQ to reschedule tasklet */
454	static inline void ace_fsm_yieldirq(struct ace_device *ace)	459	static inline void ace_fsm_yieldirq(struct ace_device *ace)
455	{	460	{
456	dev_dbg(ace->dev, "ace_fsm_yieldirq()\n");	461	dev_dbg(ace->dev, "ace_fsm_yieldirq()\n");
457		462
458	if (!ace->irq)	463	if (ace->irq > 0)
459	/* No IRQ assigned, so need to poll */	464	ace->fsm_continue_flag = 0;
460	tasklet_schedule(&ace->fsm_tasklet);	465	else
461	ace->fsm_continue_flag = 0;	466	ace_fsm_yieldpoll(ace);
462	}	467	}
463		468
464	static bool ace_has_next_request(struct request_queue *q)	469	static bool ace_has_next_request(struct request_queue *q)
@@ -1053,12 +1058,12 @@ static int ace_setup(struct ace_device *ace) · 588 unmodified lines
1053	ACE_CTRL_DATABUFRDYIRQ \| ACE_CTRL_ERRORIRQ);	1058	ACE_CTRL_DATABUFRDYIRQ \| ACE_CTRL_ERRORIRQ);
1054		1059
1055	/* Now we can hook up the irq handler */	1060	/* Now we can hook up the irq handler */
1056	if (ace->irq) {	1061	if (ace->irq > 0) {
1057	rc = request_irq(ace->irq, ace_interrupt, 0, "systemace", ace);	1062	rc = request_irq(ace->irq, ace_interrupt, 0, "systemace", ace);
1058	if (rc) {	1063	if (rc) {
1059	/* Failure - fall back to polled mode */	1064	/* Failure - fall back to polled mode */
1060	dev_err(ace->dev, "request_irq failed\n");	1065	dev_err(ace->dev, "request_irq failed\n");
1061	ace->irq = 0;	1066	ace->irq = rc;
1062	}	1067	}
1063	}	1068	}
1064		1069
@@ -1110,7 +1115,7 @@ static void ace_teardown(struct ace_device *ace) · 45 unmodified lines
1110		1115
1111	tasklet_kill(&ace->fsm_tasklet);	1116	tasklet_kill(&ace->fsm_tasklet);
1112		1117
1113	if (ace->irq)	1118	if (ace->irq > 0)
1114	free_irq(ace->irq, ace);	1119	free_irq(ace->irq, ace);
1115		1120
1116	iounmap(ace->baseaddr);	1121	iounmap(ace->baseaddr);
@@ -1123,11 +1128,6 @@ static int ace_alloc(struct device *dev, int id, resource_size_t physaddr, · 6 unmodified lines
1123	int rc;	1128	int rc;
1124	dev_dbg(dev, "ace_alloc(%p)\n", dev);	1129	dev_dbg(dev, "ace_alloc(%p)\n", dev);
1125		1130
1126	if (!physaddr) {
1127	rc = -ENODEV;
1128	goto err_noreg;
1129	}
1130
1131	/* Allocate and initialize the ace device structure */	1131	/* Allocate and initialize the ace device structure */
1132	ace = kzalloc(sizeof(struct ace_device), GFP_KERNEL);	1132	ace = kzalloc(sizeof(struct ace_device), GFP_KERNEL);
1133	if (!ace) {	1133	if (!ace) {
@@ -1153,7 +1153,6 @@ err_setup: · 19 unmodified lines
1153	dev_set_drvdata(dev, NULL);	1153	dev_set_drvdata(dev, NULL);
1154	kfree(ace);	1154	kfree(ace);
1155	err_alloc:	1155	err_alloc:
1156	err_noreg:
1157	dev_err(dev, "could not initialize device, err=%i\n", rc);	1156	dev_err(dev, "could not initialize device, err=%i\n", rc);
1158	return rc;	1157	return rc;
1159	}	1158	}
@@ -1176,10 +1175,11 @@ static void ace_free(struct device *dev) · 16 unmodified lines
1176		1175
1177	static int ace_probe(struct platform_device *dev)	1176	static int ace_probe(struct platform_device *dev)
1178	{	1177	{
1179	resource_size_t physaddr = 0;
1180	int bus_width = ACE_BUS_WIDTH_16; /* FIXME: should not be hard coded */	1178	int bus_width = ACE_BUS_WIDTH_16; /* FIXME: should not be hard coded */
		1179	resource_size_t physaddr;
		1180	struct resource *res;
1181	u32 id = dev->id;	1181	u32 id = dev->id;
1182	int irq = 0;	1182	int irq;
1183	int i;	1183	int i;
1184		1184
1185	dev_dbg(&dev->dev, "ace_probe(%p)\n", dev);	1185	dev_dbg(&dev->dev, "ace_probe(%p)\n", dev);
@@ -1190,12 +1190,15 @@ static int ace_probe(struct platform_device *dev) · 4 unmodified lines
1190	if (of_find_property(dev->dev.of_node, "8-bit", NULL))	1190	if (of_find_property(dev->dev.of_node, "8-bit", NULL))
1191	bus_width = ACE_BUS_WIDTH_8;	1191	bus_width = ACE_BUS_WIDTH_8;
1192		1192
1193	for (i = 0; i < dev->num_resources; i++) {	1193	res = platform_get_resource(dev, IORESOURCE_MEM, 0);
1194	if (dev->resource[i].flags & IORESOURCE_MEM)	1194	if (!res)
1195	physaddr = dev->resource[i].start;	1195	return -EINVAL;
1196	if (dev->resource[i].flags & IORESOURCE_IRQ)	1196
1197	irq = dev->resource[i].start;	1197	physaddr = res->start;
1198	}	1198	if (!physaddr)
		1199	return -ENODEV;
		1200
		1201	irq = platform_get_irq_optional(dev, 0);
1199		1202
1200	/* Call the bus-independent setup code */	1203	/* Call the bus-independent setup code */
1201	return ace_alloc(&dev->dev, id, physaddr, irq, bus_width);	1204	return ace_alloc(&dev->dev, id, physaddr, irq, bus_width);

drivers/bluetooth/btintel.h+1−1

@@ -47,7 +47,7 @@ enum { · 46 unmodified lines
47	struct intel_tlv {	47	struct intel_tlv {
48	u8 type;	48	u8 type;
49	u8 len;	49	u8 len;
50	u8 val[0];	50	u8 val[];
51	} __packed;	51	} __packed;
52		52
53	struct intel_version_tlv {	53	struct intel_version_tlv {

drivers/char/tpm/eventlog/efi.c+5−0

 	log_size = log_tbl->size;
 	memunmap(log_tbl);
+	if (!log_size) {
+		pr_warn("UEFI TPM log area empty\n");
+		return -EIO;
+	}
 	log_tbl = memremap(efi.tpm_log, sizeof(*log_tbl) + log_size,
 			   MEMREMAP_WB);
 	if (!log_tbl) {

drivers/char/tpm/tpm_tis.c+27−2

 #include <linux/of.h>
 #include <linux/of_device.h>
 #include <linux/kernel.h>
+#include <linux/dmi.h>
 #include "tpm.h"
 #include "tpm_tis_core.h"
 	return container_of(data, struct tpm_tis_tcg_phy, priv);
 }
-static bool interrupts = true;
+static int interrupts = -1;
-module_param(interrupts, bool, 0444);
+module_param(interrupts, int, 0444);
 MODULE_PARM_DESC(interrupts, "Enable interrupts");
 static bool itpm;
 MODULE_PARM_DESC(force, "Force device probe rather than using ACPI entry");
 #endif
+static int tpm_tis_disable_irq(const struct dmi_system_id *d)
+{
+	if (interrupts == -1) {
+		pr_notice("tpm_tis: %s detected: disabling interrupts.\n", d->ident);
+		interrupts = 0;
+	}
+	return 0;
+}
+static const struct dmi_system_id tpm_tis_dmi_table[] = {
+	{
+		.callback = tpm_tis_disable_irq,
+		.ident = "ThinkPad T490s",
+		.matches = {
+			DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
+			DMI_MATCH(DMI_PRODUCT_VERSION, "ThinkPad T490s"),
+		},
+	},
+	{}
+};
 #if defined(CONFIG_PNP) && defined(CONFIG_ACPI)
 static int has_hid(struct acpi_device *dev, const char *hid)
 {
 	int irq = -1;
 	int rc;
+	dmi_check_system(tpm_tis_dmi_table);
 	rc = check_acpi_tpm2(dev);
 	if (rc)
 		return rc;

drivers/cpufreq/Kconfig+2−0

 config CPU_FREQ_DEFAULT_GOV_ONDEMAND
 	bool "ondemand"
+	depends on !(X86_INTEL_PSTATE && SMP)
 	select CPU_FREQ_GOV_ONDEMAND
 	select CPU_FREQ_GOV_PERFORMANCE
 	help
 config CPU_FREQ_DEFAULT_GOV_CONSERVATIVE
 	bool "conservative"
+	depends on !(X86_INTEL_PSTATE && SMP)
 	select CPU_FREQ_GOV_CONSERVATIVE
 	select CPU_FREQ_GOV_PERFORMANCE
 	help

drivers/cpufreq/cpufreq.c+14−1

 	}
 }
+/**
+ * cpufreq_driver_test_flags - Test cpufreq driver's flags against given ones.
+ * @flags: Flags to test against the current cpufreq driver's flags.
+ *
+ * Assumes that the driver is there, so callers must ensure that this is the
+ * case.
+ */
+bool cpufreq_driver_test_flags(u16 flags)
+{
+	return !!(cpufreq_driver->flags & flags);
+}
 /**
  *	cpufreq_get_current_driver - return current driver's name
  *
 	 * exactly same freq is called again and so we can save on few function
 	 * calls.
 	 */
-	if (target_freq == policy->cur)
+	if (target_freq == policy->cur &&
+	    !(cpufreq_driver->flags & CPUFREQ_NEED_UPDATE_LIMITS))
 		return 0;
 	/* Save last value to restore later on errors */

drivers/cpufreq/e_powersaver.c+0−1

@@ -223,7 +223,6 @@ static int eps_cpu_init(struct cpufreq_policy *policy) · 222 unmodified lines
223	case EPS_BRAND_C3:	223	case EPS_BRAND_C3:
224	pr_cont("C3\n");	224	pr_cont("C3\n");
225	return -ENODEV;	225	return -ENODEV;
226	break;
227	}	226	}
228	/* Enable Enhanced PowerSaver */	227	/* Enable Enhanced PowerSaver */
229	rdmsrl(MSR_IA32_MISC_ENABLE, val);	228	rdmsrl(MSR_IA32_MISC_ENABLE, val);

drivers/cpufreq/intel_pstate.c+6−7

 	int old_pstate = cpu->pstate.current_pstate;
 	target_pstate = intel_pstate_prepare_request(cpu, target_pstate);
-	if (target_pstate != old_pstate) {
+	if (hwp_active) {
+		intel_cpufreq_adjust_hwp(cpu, target_pstate, fast_switch);
+		cpu->pstate.current_pstate = target_pstate;
+	} else if (target_pstate != old_pstate) {
+		intel_cpufreq_adjust_perf_ctl(cpu, target_pstate, fast_switch);
 		cpu->pstate.current_pstate = target_pstate;
-		if (hwp_active)
-			intel_cpufreq_adjust_hwp(cpu, target_pstate,
-						 fast_switch);
-		else
-			intel_cpufreq_adjust_perf_ctl(cpu, target_pstate,
-						      fast_switch);
 	}
 	intel_cpufreq_trace(cpu, fast_switch ? INTEL_PSTATE_TRACE_FAST_SWITCH :
 			hwp_mode_bdw = id->driver_data;
 			intel_pstate.attr = hwp_cpufreq_attrs;
 			intel_cpufreq.attr = hwp_cpufreq_attrs;
+			intel_cpufreq.flags |= CPUFREQ_NEED_UPDATE_LIMITS;
 			if (!default_driver)
 				default_driver = &intel_pstate;

drivers/cpufreq/longhaul.c+0−1

@@ -593,7 +593,6 @@ static void longhaul_setup_voltagescaling(void) · 592 unmodified lines
593	break;	593	break;
594	default:	594	default:
595	return;	595	return;
596	break;
597	}	596	}
598	if (min_vid_speed >= highest_speed)	597	if (min_vid_speed >= highest_speed)
599	return;	598	return;

drivers/cpufreq/speedstep-lib.c+1−1

@@ -240,7 +240,7 @@ unsigned int speedstep_get_frequency(enum speedstep_processor processor) · 239 unmodified lines
240	return pentium3_get_frequency(processor);	240	return pentium3_get_frequency(processor);
241	default:	241	default:
242	return 0;	242	return 0;
243	};	243	}
244	return 0;	244	return 0;
245	}	245	}
246	EXPORT_SYMBOL_GPL(speedstep_get_frequency);	246	EXPORT_SYMBOL_GPL(speedstep_get_frequency);

drivers/crypto/allwinner/sun8i-ce/sun8i-ce-hash.c+1−1

@@ -7,7 +7,7 @@ · 6 unmodified lines
7	*	7	*
8	* This file add support for MD5 and SHA1/SHA224/SHA256/SHA384/SHA512.	8	* This file add support for MD5 and SHA1/SHA224/SHA256/SHA384/SHA512.
9	*	9	*
10	* You could find the datasheet in Documentation/arm/sunxi/README	10	* You could find the datasheet in Documentation/arm/sunxi.rst
11	*/	11	*/
12	#include <linux/dma-mapping.h>	12	#include <linux/dma-mapping.h>
13	#include <linux/pm_runtime.h>	13	#include <linux/pm_runtime.h>

drivers/crypto/allwinner/sun8i-ce/sun8i-ce-prng.c+1−1

@@ -7,7 +7,7 @@ · 6 unmodified lines
7	*	7	*
8	* This file handle the PRNG	8	* This file handle the PRNG
9	*	9	*
10	* You could find a link for the datasheet in Documentation/arm/sunxi/README	10	* You could find a link for the datasheet in Documentation/arm/sunxi.rst
11	*/	11	*/
12	#include "sun8i-ce.h"	12	#include "sun8i-ce.h"
13	#include <linux/dma-mapping.h>	13	#include <linux/dma-mapping.h>

drivers/crypto/allwinner/sun8i-ce/sun8i-ce-trng.c+1−1

@@ -7,7 +7,7 @@ · 6 unmodified lines
7	*	7	*
8	* This file handle the TRNG	8	* This file handle the TRNG
9	*	9	*
10	* You could find a link for the datasheet in Documentation/arm/sunxi/README	10	* You could find a link for the datasheet in Documentation/arm/sunxi.rst
11	*/	11	*/
12	#include "sun8i-ce.h"	12	#include "sun8i-ce.h"
13	#include <linux/dma-mapping.h>	13	#include <linux/dma-mapping.h>

drivers/dma/Kconfig+0−18

@@ -318,24 +318,6 @@ config INTEL_IOP_ADMA · 317 unmodified lines
318	help	318	help
319	Enable support for the Intel(R) IOP Series RAID engines.	319	Enable support for the Intel(R) IOP Series RAID engines.
320		320
321	config INTEL_MIC_X100_DMA
322	tristate "Intel MIC X100 DMA Driver"
323	depends on 64BIT && X86 && INTEL_MIC_BUS
324	select DMA_ENGINE
325	help
326	This enables DMA support for the Intel Many Integrated Core
327	(MIC) family of PCIe form factor coprocessor X100 devices that
328	run a 64 bit Linux OS. This driver will be used by both MIC
329	host and card drivers.
330
331	If you are building host kernel with a MIC device or a card
332	kernel for a MIC device, then say M (recommended) or Y, else
333	say N. If unsure say N.
334
335	More information about the Intel MIC family as well as the Linux
336	OS and tools for MIC to use with this driver are available from
337	<http://software.intel.com/en-us/mic-developer>.
338
339	config K3_DMA	321	config K3_DMA
340	tristate "Hisilicon K3 DMA support"	322	tristate "Hisilicon K3 DMA support"
341	depends on ARCH_HI3xxx \|\| ARCH_HISI \|\| COMPILE_TEST	323	depends on ARCH_HI3xxx \|\| ARCH_HISI \|\| COMPILE_TEST

drivers/dma/Makefile+0−1

@@ -44,7 +44,6 @@ obj-$(CONFIG_INTEL_IDMA64) += idma64.o · 43 unmodified lines
44	obj-$(CONFIG_INTEL_IOATDMA) += ioat/	44	obj-$(CONFIG_INTEL_IOATDMA) += ioat/
45	obj-$(CONFIG_INTEL_IDXD) += idxd/	45	obj-$(CONFIG_INTEL_IDXD) += idxd/
46	obj-$(CONFIG_INTEL_IOP_ADMA) += iop-adma.o	46	obj-$(CONFIG_INTEL_IOP_ADMA) += iop-adma.o
47	obj-$(CONFIG_INTEL_MIC_X100_DMA) += mic_x100_dma.o
48	obj-$(CONFIG_K3_DMA) += k3dma.o	47	obj-$(CONFIG_K3_DMA) += k3dma.o
49	obj-$(CONFIG_LPC18XX_DMAMUX) += lpc18xx-dmamux.o	48	obj-$(CONFIG_LPC18XX_DMAMUX) += lpc18xx-dmamux.o
50	obj-$(CONFIG_MILBEAUT_HDMAC) += milbeaut-hdmac.o	49	obj-$(CONFIG_MILBEAUT_HDMAC) += milbeaut-hdmac.o

drivers/dma/mic_x100_dma.c+0−770

@@ -1,770 +0,0 @@
1	// SPDX-License-Identifier: GPL-2.0-only
2	/*
3	* Intel MIC Platform Software Stack (MPSS)
4	*
5	* Copyright(c) 2014 Intel Corporation.
6	*
7	* Intel MIC X100 DMA Driver.
8	*
9	* Adapted from IOAT dma driver.
10	*/
11	#include <linux/module.h>
12	#include <linux/io.h>
13	#include <linux/seq_file.h>
14	#include <linux/vmalloc.h>
15
16	#include "mic_x100_dma.h"
17
18	#define MIC_DMA_MAX_XFER_SIZE_CARD (1 * 1024 * 1024 -\
19	MIC_DMA_ALIGN_BYTES)
20	#define MIC_DMA_MAX_XFER_SIZE_HOST (1 * 1024 * 1024 >> 1)
21	#define MIC_DMA_DESC_TYPE_SHIFT 60
22	#define MIC_DMA_MEMCPY_LEN_SHIFT 46
23	#define MIC_DMA_STAT_INTR_SHIFT 59
24
25	/* high-water mark for pushing dma descriptors */
26	static int mic_dma_pending_level = 4;
27
28	/* Status descriptor is used to write a 64 bit value to a memory location */
29	enum mic_dma_desc_format_type {
30	MIC_DMA_MEMCPY = 1,
31	MIC_DMA_STATUS,
32	};
33
34	static inline u32 mic_dma_hw_ring_inc(u32 val)
35	{
36	return (val + 1) % MIC_DMA_DESC_RX_SIZE;
37	}
38
39	static inline u32 mic_dma_hw_ring_dec(u32 val)
40	{
41	return val ? val - 1 : MIC_DMA_DESC_RX_SIZE - 1;
42	}
43
44	static inline void mic_dma_hw_ring_inc_head(struct mic_dma_chan *ch)
45	{
46	ch->head = mic_dma_hw_ring_inc(ch->head);
47	}
48
49	/* Prepare a memcpy desc */
50	static inline void mic_dma_memcpy_desc(struct mic_dma_desc *desc,
51	dma_addr_t src_phys, dma_addr_t dst_phys, u64 size)
52	{
53	u64 qw0, qw1;
54
55	qw0 = src_phys;
56	qw0 \|= (size >> MIC_DMA_ALIGN_SHIFT) << MIC_DMA_MEMCPY_LEN_SHIFT;
57	qw1 = MIC_DMA_MEMCPY;
58	qw1 <<= MIC_DMA_DESC_TYPE_SHIFT;
59	qw1 \|= dst_phys;
60	desc->qw0 = qw0;
61	desc->qw1 = qw1;
62	}
63
64	/* Prepare a status desc. with @data to be written at @dst_phys */
65	static inline void mic_dma_prep_status_desc(struct mic_dma_desc *desc, u64 data,
66	dma_addr_t dst_phys, bool generate_intr)
67	{
68	u64 qw0, qw1;
69
70	qw0 = data;
71	qw1 = (u64) MIC_DMA_STATUS << MIC_DMA_DESC_TYPE_SHIFT \| dst_phys;
72	if (generate_intr)
73	qw1 \|= (1ULL << MIC_DMA_STAT_INTR_SHIFT);
74	desc->qw0 = qw0;
75	desc->qw1 = qw1;
76	}
77
78	static void mic_dma_cleanup(struct mic_dma_chan *ch)
79	{
80	struct dma_async_tx_descriptor *tx;
81	u32 tail;
82	u32 last_tail;
83
84	spin_lock(&ch->cleanup_lock);
85	tail = mic_dma_read_cmp_cnt(ch);
86	/*
87	* This is the barrier pair for smp_wmb() in fn.
88	* mic_dma_tx_submit_unlock. It's required so that we read the
89	* updated cookie value from tx->cookie.
90	*/
91	smp_rmb();
92	for (last_tail = ch->last_tail; tail != last_tail;) {
93	tx = &ch->tx_array[last_tail];
94	if (tx->cookie) {
95	dma_cookie_complete(tx);
96	dmaengine_desc_get_callback_invoke(tx, NULL);
97	tx->callback = NULL;
98	}
99	last_tail = mic_dma_hw_ring_inc(last_tail);
100	}
101	/* finish all completion callbacks before incrementing tail */
102	smp_mb();
103	ch->last_tail = last_tail;
104	spin_unlock(&ch->cleanup_lock);
105	}
106
107	static u32 mic_dma_ring_count(u32 head, u32 tail)
108	{
109	u32 count;
110
111	if (head >= tail)
112	count = (tail - 0) + (MIC_DMA_DESC_RX_SIZE - head);
113	else
114	count = tail - head;
115	return count - 1;
116	}
117
118	/* Returns the num. of free descriptors on success, -ENOMEM on failure */
119	static int mic_dma_avail_desc_ring_space(struct mic_dma_chan *ch, int required)
120	{
121	struct device *dev = mic_dma_ch_to_device(ch);
122	u32 count;
123
124	count = mic_dma_ring_count(ch->head, ch->last_tail);
125	if (count < required) {
126	mic_dma_cleanup(ch);
127	count = mic_dma_ring_count(ch->head, ch->last_tail);
128	}
129
130	if (count < required) {
131	dev_dbg(dev, "Not enough desc space");
132	dev_dbg(dev, "%s %d required=%u, avail=%u\n",
133	__func__, __LINE__, required, count);
134	return -ENOMEM;
135	} else {
136	return count;
137	}
138	}
139
140	/* Program memcpy descriptors into the descriptor ring and update s/w head ptr*/
141	static int mic_dma_prog_memcpy_desc(struct mic_dma_chan *ch, dma_addr_t src,
142	dma_addr_t dst, size_t len)
143	{
144	size_t current_transfer_len;
145	size_t max_xfer_size = to_mic_dma_dev(ch)->max_xfer_size;
146	/* 3 is added to make sure we have enough space for status desc */
147	int num_desc = len / max_xfer_size + 3;
148	int ret;
149
150	if (len % max_xfer_size)
151	num_desc++;
152
153	ret = mic_dma_avail_desc_ring_space(ch, num_desc);
154	if (ret < 0)
155	return ret;
156	do {
157	current_transfer_len = min(len, max_xfer_size);
158	mic_dma_memcpy_desc(&ch->desc_ring[ch->head],
159	src, dst, current_transfer_len);
160	mic_dma_hw_ring_inc_head(ch);
161	len -= current_transfer_len;
162	dst = dst + current_transfer_len;
163	src = src + current_transfer_len;
164	} while (len > 0);
165	return 0;
166	}
167
168	/* It's a h/w quirk and h/w needs 2 status descriptors for every status desc */
169	static void mic_dma_prog_intr(struct mic_dma_chan *ch)
170	{
171	mic_dma_prep_status_desc(&ch->desc_ring[ch->head], 0,
172	ch->status_dest_micpa, false);
173	mic_dma_hw_ring_inc_head(ch);
174	mic_dma_prep_status_desc(&ch->desc_ring[ch->head], 0,
175	ch->status_dest_micpa, true);
176	mic_dma_hw_ring_inc_head(ch);
177	}
178
179	/* Wrapper function to program memcpy descriptors/status descriptors */
180	static int mic_dma_do_dma(struct mic_dma_chan *ch, int flags, dma_addr_t src,
181	dma_addr_t dst, size_t len)
182	{
183	if (len && -ENOMEM == mic_dma_prog_memcpy_desc(ch, src, dst, len)) {
184	return -ENOMEM;
185	} else {
186	/* 3 is the maximum number of status descriptors */
187	int ret = mic_dma_avail_desc_ring_space(ch, 3);
188
189	if (ret < 0)
190	return ret;
191	}
192
193	/* Above mic_dma_prog_memcpy_desc() makes sure we have enough space */
194	if (flags & DMA_PREP_FENCE) {
195	mic_dma_prep_status_desc(&ch->desc_ring[ch->head], 0,
196	ch->status_dest_micpa, false);
197	mic_dma_hw_ring_inc_head(ch);
198	}
199
200	if (flags & DMA_PREP_INTERRUPT)
201	mic_dma_prog_intr(ch);
202
203	return 0;
204	}
205
206	static inline void mic_dma_issue_pending(struct dma_chan *ch)
207	{
208	struct mic_dma_chan *mic_ch = to_mic_dma_chan(ch);
209
210	spin_lock(&mic_ch->issue_lock);
211	/*
212	* Write to head triggers h/w to act on the descriptors.
213	* On MIC, writing the same head value twice causes
214	* a h/w error. On second write, h/w assumes we filled
215	* the entire ring & overwrote some of the descriptors.
216	*/
217	if (mic_ch->issued == mic_ch->submitted)
218	goto out;
219	mic_ch->issued = mic_ch->submitted;
220	/*
221	* make descriptor updates visible before advancing head,
222	* this is purposefully not smp_wmb() since we are also
223	* publishing the descriptor updates to a dma device
224	*/
225	wmb();
226	mic_dma_write_reg(mic_ch, MIC_DMA_REG_DHPR, mic_ch->issued);
227	out:
228	spin_unlock(&mic_ch->issue_lock);
229	}
230
231	static inline void mic_dma_update_pending(struct mic_dma_chan *ch)
232	{
233	if (mic_dma_ring_count(ch->issued, ch->submitted)
234	> mic_dma_pending_level)
235	mic_dma_issue_pending(&ch->api_ch);
236	}
237
238	static dma_cookie_t mic_dma_tx_submit_unlock(struct dma_async_tx_descriptor *tx)
239	{
240	struct mic_dma_chan *mic_ch = to_mic_dma_chan(tx->chan);
241	dma_cookie_t cookie;
242
243	dma_cookie_assign(tx);
244	cookie = tx->cookie;
245	/*
246	* We need an smp write barrier here because another CPU might see
247	* an update to submitted and update h/w head even before we
248	* assigned a cookie to this tx.
249	*/
250	smp_wmb();
251	mic_ch->submitted = mic_ch->head;
252	spin_unlock(&mic_ch->prep_lock);
253	mic_dma_update_pending(mic_ch);
254	return cookie;
255	}
256
257	static inline struct dma_async_tx_descriptor *
258	allocate_tx(struct mic_dma_chan *ch)
259	{
260	u32 idx = mic_dma_hw_ring_dec(ch->head);
261	struct dma_async_tx_descriptor *tx = &ch->tx_array[idx];
262
263	dma_async_tx_descriptor_init(tx, &ch->api_ch);
264	tx->tx_submit = mic_dma_tx_submit_unlock;
265	return tx;
266	}
267
268	/* Program a status descriptor with dst as address and value to be written */
269	static struct dma_async_tx_descriptor *
270	mic_dma_prep_status_lock(struct dma_chan *ch, dma_addr_t dst, u64 src_val,
271	unsigned long flags)
272	{
273	struct mic_dma_chan *mic_ch = to_mic_dma_chan(ch);
274	int result;
275
276	spin_lock(&mic_ch->prep_lock);
277	result = mic_dma_avail_desc_ring_space(mic_ch, 4);
278	if (result < 0)
279	goto error;
280	mic_dma_prep_status_desc(&mic_ch->desc_ring[mic_ch->head], src_val, dst,
281	false);
282	mic_dma_hw_ring_inc_head(mic_ch);
283	result = mic_dma_do_dma(mic_ch, flags, 0, 0, 0);
284	if (result < 0)
285	goto error;
286
287	return allocate_tx(mic_ch);
288	error:
289	dev_err(mic_dma_ch_to_device(mic_ch),
290	"Error enqueueing dma status descriptor, error=%d\n", result);
291	spin_unlock(&mic_ch->prep_lock);
292	return NULL;
293	}
294
295	/*
296	* Prepare a memcpy descriptor to be added to the ring.
297	* Note that the temporary descriptor adds an extra overhead of copying the
298	* descriptor to ring. So, we copy directly to the descriptor ring
299	*/
300	static struct dma_async_tx_descriptor *
301	mic_dma_prep_memcpy_lock(struct dma_chan *ch, dma_addr_t dma_dest,
302	dma_addr_t dma_src, size_t len, unsigned long flags)
303	{
304	struct mic_dma_chan *mic_ch = to_mic_dma_chan(ch);
305	struct device *dev = mic_dma_ch_to_device(mic_ch);
306	int result;
307
308	if (!len && !flags)
309	return NULL;
310
311	spin_lock(&mic_ch->prep_lock);
312	result = mic_dma_do_dma(mic_ch, flags, dma_src, dma_dest, len);
313	if (result >= 0)
314	return allocate_tx(mic_ch);
315	dev_err(dev, "Error enqueueing dma, error=%d\n", result);
316	spin_unlock(&mic_ch->prep_lock);
317	return NULL;
318	}
319
320	static struct dma_async_tx_descriptor *
321	mic_dma_prep_interrupt_lock(struct dma_chan *ch, unsigned long flags)
322	{
323	struct mic_dma_chan *mic_ch = to_mic_dma_chan(ch);
324	int ret;
325
326	spin_lock(&mic_ch->prep_lock);
327	ret = mic_dma_do_dma(mic_ch, flags, 0, 0, 0);
328	if (!ret)
329	return allocate_tx(mic_ch);
330	spin_unlock(&mic_ch->prep_lock);
331	return NULL;
332	}
333
334	/* Return the status of the transaction */
335	static enum dma_status
336	mic_dma_tx_status(struct dma_chan *ch, dma_cookie_t cookie,
337	struct dma_tx_state *txstate)
338	{
339	struct mic_dma_chan *mic_ch = to_mic_dma_chan(ch);
340
341	if (DMA_COMPLETE != dma_cookie_status(ch, cookie, txstate))
342	mic_dma_cleanup(mic_ch);
343
344	return dma_cookie_status(ch, cookie, txstate);
345	}
346
347	static irqreturn_t mic_dma_thread_fn(int irq, void *data)
348	{
349	mic_dma_cleanup((struct mic_dma_chan *)data);
350	return IRQ_HANDLED;
351	}
352
353	static irqreturn_t mic_dma_intr_handler(int irq, void *data)
354	{
355	struct mic_dma_chan ch = ((struct mic_dma_chan )data);
356
357	mic_dma_ack_interrupt(ch);
358	return IRQ_WAKE_THREAD;
359	}
360
361	static int mic_dma_alloc_desc_ring(struct mic_dma_chan *ch)
362	{
363	u64 desc_ring_size = MIC_DMA_DESC_RX_SIZE * sizeof(*ch->desc_ring);
364	struct device *dev = &to_mbus_device(ch)->dev;
365
366	desc_ring_size = ALIGN(desc_ring_size, MIC_DMA_ALIGN_BYTES);
367	ch->desc_ring = kzalloc(desc_ring_size, GFP_KERNEL);
368
369	if (!ch->desc_ring)
370	return -ENOMEM;
371
372	ch->desc_ring_micpa = dma_map_single(dev, ch->desc_ring,
373	desc_ring_size, DMA_BIDIRECTIONAL);
374	if (dma_mapping_error(dev, ch->desc_ring_micpa))
375	goto map_error;
376
377	ch->tx_array = vzalloc(array_size(MIC_DMA_DESC_RX_SIZE,
378	sizeof(*ch->tx_array)));
379	if (!ch->tx_array)
380	goto tx_error;
381	return 0;
382	tx_error:
383	dma_unmap_single(dev, ch->desc_ring_micpa, desc_ring_size,
384	DMA_BIDIRECTIONAL);
385	map_error:
386	kfree(ch->desc_ring);
387	return -ENOMEM;
388	}
389
390	static void mic_dma_free_desc_ring(struct mic_dma_chan *ch)
391	{
392	u64 desc_ring_size = MIC_DMA_DESC_RX_SIZE * sizeof(*ch->desc_ring);
393
394	vfree(ch->tx_array);
395	desc_ring_size = ALIGN(desc_ring_size, MIC_DMA_ALIGN_BYTES);
396	dma_unmap_single(&to_mbus_device(ch)->dev, ch->desc_ring_micpa,
397	desc_ring_size, DMA_BIDIRECTIONAL);
398	kfree(ch->desc_ring);
399	ch->desc_ring = NULL;
400	}
401
402	static void mic_dma_free_status_dest(struct mic_dma_chan *ch)
403	{
404	dma_unmap_single(&to_mbus_device(ch)->dev, ch->status_dest_micpa,
405	L1_CACHE_BYTES, DMA_BIDIRECTIONAL);
406	kfree(ch->status_dest);
407	}
408
409	static int mic_dma_alloc_status_dest(struct mic_dma_chan *ch)
410	{
411	struct device *dev = &to_mbus_device(ch)->dev;
412
413	ch->status_dest = kzalloc(L1_CACHE_BYTES, GFP_KERNEL);
414	if (!ch->status_dest)
415	return -ENOMEM;
416	ch->status_dest_micpa = dma_map_single(dev, ch->status_dest,
417	L1_CACHE_BYTES, DMA_BIDIRECTIONAL);
418	if (dma_mapping_error(dev, ch->status_dest_micpa)) {
419	kfree(ch->status_dest);
420	ch->status_dest = NULL;
421	return -ENOMEM;
422	}
423	return 0;
424	}
425
426	static int mic_dma_check_chan(struct mic_dma_chan *ch)
427	{
428	if (mic_dma_read_reg(ch, MIC_DMA_REG_DCHERR) \|\|
429	mic_dma_read_reg(ch, MIC_DMA_REG_DSTAT) & MIC_DMA_CHAN_QUIESCE) {
430	mic_dma_disable_chan(ch);
431	mic_dma_chan_mask_intr(ch);
432	dev_err(mic_dma_ch_to_device(ch),
433	"%s %d error setting up mic dma chan %d\n",
434	__func__, __LINE__, ch->ch_num);
435	return -EBUSY;
436	}
437	return 0;
438	}
439
440	static int mic_dma_chan_setup(struct mic_dma_chan *ch)
441	{
442	if (MIC_DMA_CHAN_MIC == ch->owner)
443	mic_dma_chan_set_owner(ch);
444	mic_dma_disable_chan(ch);
445	mic_dma_chan_mask_intr(ch);
446	mic_dma_write_reg(ch, MIC_DMA_REG_DCHERRMSK, 0);
447	mic_dma_chan_set_desc_ring(ch);
448	ch->last_tail = mic_dma_read_reg(ch, MIC_DMA_REG_DTPR);
449	ch->head = ch->last_tail;
450	ch->issued = 0;
451	mic_dma_chan_unmask_intr(ch);
452	mic_dma_enable_chan(ch);
453	return mic_dma_check_chan(ch);
454	}
455
456	static void mic_dma_chan_destroy(struct mic_dma_chan *ch)
457	{
458	mic_dma_disable_chan(ch);
459	mic_dma_chan_mask_intr(ch);
460	}
461
462	static int mic_dma_setup_irq(struct mic_dma_chan *ch)
463	{
464	ch->cookie =
465	to_mbus_hw_ops(ch)->request_threaded_irq(to_mbus_device(ch),
466	mic_dma_intr_handler, mic_dma_thread_fn,
467	"mic dma_channel", ch, ch->ch_num);
468	return PTR_ERR_OR_ZERO(ch->cookie);
469	}
470
471	static inline void mic_dma_free_irq(struct mic_dma_chan *ch)
472	{
473	to_mbus_hw_ops(ch)->free_irq(to_mbus_device(ch), ch->cookie, ch);
474	}
475
476	static int mic_dma_chan_init(struct mic_dma_chan *ch)
477	{
478	int ret = mic_dma_alloc_desc_ring(ch);
479
480	if (ret)
481	goto ring_error;
482	ret = mic_dma_alloc_status_dest(ch);
483	if (ret)
484	goto status_error;
485	ret = mic_dma_chan_setup(ch);
486	if (ret)
487	goto chan_error;
488	return ret;
489	chan_error:
490	mic_dma_free_status_dest(ch);
491	status_error:
492	mic_dma_free_desc_ring(ch);
493	ring_error:
494	return ret;
495	}
496
497	static int mic_dma_drain_chan(struct mic_dma_chan *ch)
498	{
499	struct dma_async_tx_descriptor *tx;
500	int err = 0;
501	dma_cookie_t cookie;
502
503	tx = mic_dma_prep_memcpy_lock(&ch->api_ch, 0, 0, 0, DMA_PREP_FENCE);
504	if (!tx) {
505	err = -ENOMEM;
506	goto error;
507	}
508
509	cookie = tx->tx_submit(tx);
510	if (dma_submit_error(cookie))
511	err = -ENOMEM;
512	else
513	err = dma_sync_wait(&ch->api_ch, cookie);
514	if (err) {
515	dev_err(mic_dma_ch_to_device(ch), "%s %d TO chan 0x%x\n",
516	__func__, __LINE__, ch->ch_num);
517	err = -EIO;
518	}
519	error:
520	mic_dma_cleanup(ch);
521	return err;
522	}
523
524	static inline void mic_dma_chan_uninit(struct mic_dma_chan *ch)
525	{
526	mic_dma_chan_destroy(ch);
527	mic_dma_cleanup(ch);
528	mic_dma_free_status_dest(ch);
529	mic_dma_free_desc_ring(ch);
530	}
531
532	static int mic_dma_init(struct mic_dma_device *mic_dma_dev,
533	enum mic_dma_chan_owner owner)
534	{
535	int i, first_chan = mic_dma_dev->start_ch;
536	struct mic_dma_chan *ch;
537	int ret;
538
539	for (i = first_chan; i < first_chan + MIC_DMA_NUM_CHAN; i++) {
540	ch = &mic_dma_dev->mic_ch[i];
541	ch->ch_num = i;
542	ch->owner = owner;
543	spin_lock_init(&ch->cleanup_lock);
544	spin_lock_init(&ch->prep_lock);
545	spin_lock_init(&ch->issue_lock);
546	ret = mic_dma_setup_irq(ch);
547	if (ret)
548	goto error;
549	}
550	return 0;
551	error:
552	for (i = i - 1; i >= first_chan; i--)
553	mic_dma_free_irq(ch);
554	return ret;
555	}
556
557	static void mic_dma_uninit(struct mic_dma_device *mic_dma_dev)
558	{
559	int i, first_chan = mic_dma_dev->start_ch;
560	struct mic_dma_chan *ch;
561
562	for (i = first_chan; i < first_chan + MIC_DMA_NUM_CHAN; i++) {
563	ch = &mic_dma_dev->mic_ch[i];
564	mic_dma_free_irq(ch);
565	}
566	}
567
568	static int mic_dma_alloc_chan_resources(struct dma_chan *ch)
569	{
570	int ret = mic_dma_chan_init(to_mic_dma_chan(ch));
571	if (ret)
572	return ret;
573	return MIC_DMA_DESC_RX_SIZE;
574	}
575
576	static void mic_dma_free_chan_resources(struct dma_chan *ch)
577	{
578	struct mic_dma_chan *mic_ch = to_mic_dma_chan(ch);
579	mic_dma_drain_chan(mic_ch);
580	mic_dma_chan_uninit(mic_ch);
581	}
582
583	/* Set the fn. handlers and register the dma device with dma api */
584	static int mic_dma_register_dma_device(struct mic_dma_device *mic_dma_dev,
585	enum mic_dma_chan_owner owner)
586	{
587	int i, first_chan = mic_dma_dev->start_ch;
588
589	dma_cap_zero(mic_dma_dev->dma_dev.cap_mask);
590	/*
591	* This dma engine is not capable of host memory to host memory
592	* transfers
593	*/
594	dma_cap_set(DMA_MEMCPY, mic_dma_dev->dma_dev.cap_mask);
595
596	if (MIC_DMA_CHAN_HOST == owner)
597	dma_cap_set(DMA_PRIVATE, mic_dma_dev->dma_dev.cap_mask);
598	mic_dma_dev->dma_dev.device_alloc_chan_resources =
599	mic_dma_alloc_chan_resources;
600	mic_dma_dev->dma_dev.device_free_chan_resources =
601	mic_dma_free_chan_resources;
602	mic_dma_dev->dma_dev.device_tx_status = mic_dma_tx_status;
603	mic_dma_dev->dma_dev.device_prep_dma_memcpy = mic_dma_prep_memcpy_lock;
604	mic_dma_dev->dma_dev.device_prep_dma_imm_data =
605	mic_dma_prep_status_lock;
606	mic_dma_dev->dma_dev.device_prep_dma_interrupt =
607	mic_dma_prep_interrupt_lock;
608	mic_dma_dev->dma_dev.device_issue_pending = mic_dma_issue_pending;
609	mic_dma_dev->dma_dev.copy_align = MIC_DMA_ALIGN_SHIFT;
610	INIT_LIST_HEAD(&mic_dma_dev->dma_dev.channels);
611	for (i = first_chan; i < first_chan + MIC_DMA_NUM_CHAN; i++) {
612	mic_dma_dev->mic_ch[i].api_ch.device = &mic_dma_dev->dma_dev;
613	dma_cookie_init(&mic_dma_dev->mic_ch[i].api_ch);
614	list_add_tail(&mic_dma_dev->mic_ch[i].api_ch.device_node,
615	&mic_dma_dev->dma_dev.channels);
616	}
617	return dmaenginem_async_device_register(&mic_dma_dev->dma_dev);
618	}
619
620	/*
621	* Initializes dma channels and registers the dma device with the
622	* dma engine api.
623	*/
624	static struct mic_dma_device mic_dma_dev_reg(struct mbus_device mbdev,
625	enum mic_dma_chan_owner owner)
626	{
627	struct mic_dma_device *mic_dma_dev;
628	int ret;
629	struct device *dev = &mbdev->dev;
630
631	mic_dma_dev = devm_kzalloc(dev, sizeof(*mic_dma_dev), GFP_KERNEL);
632	if (!mic_dma_dev) {
633	ret = -ENOMEM;
634	goto alloc_error;
635	}
636	mic_dma_dev->mbdev = mbdev;
637	mic_dma_dev->dma_dev.dev = dev;
638	mic_dma_dev->mmio = mbdev->mmio_va;
639	if (MIC_DMA_CHAN_HOST == owner) {
640	mic_dma_dev->start_ch = 0;
641	mic_dma_dev->max_xfer_size = MIC_DMA_MAX_XFER_SIZE_HOST;
642	} else {
643	mic_dma_dev->start_ch = 4;
644	mic_dma_dev->max_xfer_size = MIC_DMA_MAX_XFER_SIZE_CARD;
645	}
646	ret = mic_dma_init(mic_dma_dev, owner);
647	if (ret)
648	goto init_error;
649	ret = mic_dma_register_dma_device(mic_dma_dev, owner);
650	if (ret)
651	goto reg_error;
652	return mic_dma_dev;
653	reg_error:
654	mic_dma_uninit(mic_dma_dev);
655	init_error:
656	mic_dma_dev = NULL;
657	alloc_error:
658	dev_err(dev, "Error at %s %d ret=%d\n", __func__, __LINE__, ret);
659	return mic_dma_dev;
660	}
661
662	static void mic_dma_dev_unreg(struct mic_dma_device *mic_dma_dev)
663	{
664	mic_dma_uninit(mic_dma_dev);
665	}
666
667	/* DEBUGFS CODE */
668	static int mic_dma_reg_show(struct seq_file s, void pos)
669	{
670	struct mic_dma_device *mic_dma_dev = s->private;
671	int i, chan_num, first_chan = mic_dma_dev->start_ch;
672	struct mic_dma_chan *ch;
673
674	seq_printf(s, "SBOX_DCR: %#x\n",
675	mic_dma_mmio_read(&mic_dma_dev->mic_ch[first_chan],
676	MIC_DMA_SBOX_BASE + MIC_DMA_SBOX_DCR));
677	seq_puts(s, "DMA Channel Registers\n");
678	seq_printf(s, "%-10s\| %-10s %-10s %-10s %-10s %-10s",
679	"Channel", "DCAR", "DTPR", "DHPR", "DRAR_HI", "DRAR_LO");
680	seq_printf(s, " %-11s %-14s %-10s\n", "DCHERR", "DCHERRMSK", "DSTAT");
681	for (i = first_chan; i < first_chan + MIC_DMA_NUM_CHAN; i++) {
682	ch = &mic_dma_dev->mic_ch[i];
683	chan_num = ch->ch_num;
684	seq_printf(s, "%-10i\| %-#10x %-#10x %-#10x %-#10x",
685	chan_num,
686	mic_dma_read_reg(ch, MIC_DMA_REG_DCAR),
687	mic_dma_read_reg(ch, MIC_DMA_REG_DTPR),
688	mic_dma_read_reg(ch, MIC_DMA_REG_DHPR),
689	mic_dma_read_reg(ch, MIC_DMA_REG_DRAR_HI));
690	seq_printf(s, " %-#10x %-#10x %-#14x %-#10x\n",
691	mic_dma_read_reg(ch, MIC_DMA_REG_DRAR_LO),
692	mic_dma_read_reg(ch, MIC_DMA_REG_DCHERR),
693	mic_dma_read_reg(ch, MIC_DMA_REG_DCHERRMSK),
694	mic_dma_read_reg(ch, MIC_DMA_REG_DSTAT));
695	}
696	return 0;
697	}
698
699	DEFINE_SHOW_ATTRIBUTE(mic_dma_reg);
700
701	/* Debugfs parent dir */
702	static struct dentry *mic_dma_dbg;
703
704	static int mic_dma_driver_probe(struct mbus_device *mbdev)
705	{
706	struct mic_dma_device *mic_dma_dev;
707	enum mic_dma_chan_owner owner;
708
709	if (MBUS_DEV_DMA_MIC == mbdev->id.device)
710	owner = MIC_DMA_CHAN_MIC;
711	else
712	owner = MIC_DMA_CHAN_HOST;
713
714	mic_dma_dev = mic_dma_dev_reg(mbdev, owner);
715	dev_set_drvdata(&mbdev->dev, mic_dma_dev);
716
717	if (mic_dma_dbg) {
718	mic_dma_dev->dbg_dir = debugfs_create_dir(dev_name(&mbdev->dev),
719	mic_dma_dbg);
720	debugfs_create_file("mic_dma_reg", 0444, mic_dma_dev->dbg_dir,
721	mic_dma_dev, &mic_dma_reg_fops);
722	}
723	return 0;
724	}
725
726	static void mic_dma_driver_remove(struct mbus_device *mbdev)
727	{
728	struct mic_dma_device *mic_dma_dev;
729
730	mic_dma_dev = dev_get_drvdata(&mbdev->dev);
731	debugfs_remove_recursive(mic_dma_dev->dbg_dir);
732	mic_dma_dev_unreg(mic_dma_dev);
733	}
734
735	static struct mbus_device_id id_table[] = {
736	{MBUS_DEV_DMA_MIC, MBUS_DEV_ANY_ID},
737	{MBUS_DEV_DMA_HOST, MBUS_DEV_ANY_ID},
738	{0},
739	};
740
741	static struct mbus_driver mic_dma_driver = {
742	.driver.name = KBUILD_MODNAME,
743	.driver.owner = THIS_MODULE,
744	.id_table = id_table,
745	.probe = mic_dma_driver_probe,
746	.remove = mic_dma_driver_remove,
747	};
748
749	static int __init mic_x100_dma_init(void)
750	{
751	int rc = mbus_register_driver(&mic_dma_driver);
752	if (rc)
753	return rc;
754	mic_dma_dbg = debugfs_create_dir(KBUILD_MODNAME, NULL);
755	return 0;
756	}
757
758	static void __exit mic_x100_dma_exit(void)
759	{
760	debugfs_remove_recursive(mic_dma_dbg);
761	mbus_unregister_driver(&mic_dma_driver);
762	}
763
764	module_init(mic_x100_dma_init);
765	module_exit(mic_x100_dma_exit);
766
767	MODULE_DEVICE_TABLE(mbus, id_table);
768	MODULE_AUTHOR("Intel Corporation");
769	MODULE_DESCRIPTION("Intel(R) MIC X100 DMA Driver");
770	MODULE_LICENSE("GPL v2");

drivers/dma/mic_x100_dma.h+0−275

@@ -1,275 +0,0 @@
1	/* SPDX-License-Identifier: GPL-2.0-only */
2	/*
3	* Intel MIC Platform Software Stack (MPSS)
4	*
5	* Copyright(c) 2014 Intel Corporation.
6	*
7	* Intel MIC X100 DMA Driver.
8	*
9	* Adapted from IOAT dma driver.
10	*/
11	#ifndef _MIC_X100_DMA_H_
12	#define _MIC_X100_DMA_H_
13
14	#include <linux/kernel.h>
15	#include <linux/delay.h>
16	#include <linux/sched.h>
17	#include <linux/debugfs.h>
18	#include <linux/slab.h>
19	#include <linux/interrupt.h>
20	#include <linux/mic_bus.h>
21
22	#include "dmaengine.h"
23
24	/*
25	* MIC has a total of 8 dma channels.
26	* Four channels are assigned for host SW use & the remaining for MIC SW.
27	* MIC DMA transfer size & addresses need to be 64 byte aligned.
28	*/
29	#define MIC_DMA_MAX_NUM_CHAN 8
30	#define MIC_DMA_NUM_CHAN 4
31	#define MIC_DMA_ALIGN_SHIFT DMAENGINE_ALIGN_64_BYTES
32	#define MIC_DMA_ALIGN_BYTES (1 << MIC_DMA_ALIGN_SHIFT)
33	#define MIC_DMA_DESC_RX_SIZE (128 * 1024 - 4)
34
35	/*
36	* Register descriptions
37	* All the registers are 32 bit registers.
38	* DCR is a global register and all others are per-channel.
39	* DCR - bits 0, 2, 4, 6, 8, 10, 12, 14 - enable bits for channels 0 to 7
40	* bits 1, 3, 5, 7, 9, 11, 13, 15 - owner bits for channels 0 to 7
41	* DCAR - bit 24 & 25 interrupt masks for mic owned & host owned channels
42	* DHPR - head of the descriptor ring updated by s/w
43	* DTPR - tail of the descriptor ring updated by h/w
44	* DRAR_LO - lower 32 bits of descriptor ring's mic address
45	* DRAR_HI - 3:0 - remaining 4 bits of descriptor ring's mic address
46	* 20:4 descriptor ring size
47	* 25:21 mic smpt entry number
48	* DSTAT - 16:0 h/w completion count; 31:28 dma engine status
49	* DCHERR - this register is non-zero on error
50	* DCHERRMSK - interrupt mask register
51	*/
52	#define MIC_DMA_HW_CMP_CNT_MASK 0x1ffff
53	#define MIC_DMA_CHAN_QUIESCE 0x20000000
54	#define MIC_DMA_SBOX_BASE 0x00010000
55	#define MIC_DMA_SBOX_DCR 0x0000A280
56	#define MIC_DMA_SBOX_CH_BASE 0x0001A000
57	#define MIC_DMA_SBOX_CHAN_OFF 0x40
58	#define MIC_DMA_SBOX_DCAR_IM0 (0x1 << 24)
59	#define MIC_DMA_SBOX_DCAR_IM1 (0x1 << 25)
60	#define MIC_DMA_SBOX_DRARHI_SYS_MASK (0x1 << 26)
61	#define MIC_DMA_REG_DCAR 0
62	#define MIC_DMA_REG_DHPR 4
63	#define MIC_DMA_REG_DTPR 8
64	#define MIC_DMA_REG_DRAR_LO 20
65	#define MIC_DMA_REG_DRAR_HI 24
66	#define MIC_DMA_REG_DSTAT 32
67	#define MIC_DMA_REG_DCHERR 44
68	#define MIC_DMA_REG_DCHERRMSK 48
69
70	/* HW dma desc */
71	struct mic_dma_desc {
72	u64 qw0;
73	u64 qw1;
74	};
75
76	enum mic_dma_chan_owner {
77	MIC_DMA_CHAN_MIC = 0,
78	MIC_DMA_CHAN_HOST
79	};
80
81	/*
82	* mic_dma_chan - channel specific information
83	* @ch_num: channel number
84	* @owner: owner of this channel
85	* @last_tail: cached value of descriptor ring tail
86	* @head: index of next descriptor in desc_ring
87	* @issued: hardware notification point
88	* @submitted: index that will be used to submit descriptors to h/w
89	* @api_ch: dma engine api channel
90	* @desc_ring: dma descriptor ring
91	* @desc_ring_micpa: mic physical address of desc_ring
92	* @status_dest: destination for status (fence) descriptor
93	* @status_dest_micpa: mic address for status_dest,
94	* DMA controller uses this address
95	* @tx_array: array of async_tx
96	* @cleanup_lock: lock held when processing completed tx
97	* @prep_lock: lock held in prep_memcpy & released in tx_submit
98	* @issue_lock: lock used to synchronize writes to head
99	* @cookie: mic_irq cookie used with mic irq request
100	*/
101	struct mic_dma_chan {
102	int ch_num;
103	enum mic_dma_chan_owner owner;
104	u32 last_tail;
105	u32 head;
106	u32 issued;
107	u32 submitted;
108	struct dma_chan api_ch;
109	struct mic_dma_desc *desc_ring;
110	dma_addr_t desc_ring_micpa;
111	u64 *status_dest;
112	dma_addr_t status_dest_micpa;
113	struct dma_async_tx_descriptor *tx_array;
114	spinlock_t cleanup_lock;
115	spinlock_t prep_lock;
116	spinlock_t issue_lock;
117	struct mic_irq *cookie;
118	};
119
120	/*
121	* struct mic_dma_device - per mic device
122	* @mic_ch: dma channels
123	* @dma_dev: underlying dma device
124	* @mbdev: mic bus dma device
125	* @mmio: virtual address of the mmio space
126	* @dbg_dir: debugfs directory
127	* @start_ch: first channel number that can be used
128	* @max_xfer_size: maximum transfer size per dma descriptor
129	*/
130	struct mic_dma_device {
131	struct mic_dma_chan mic_ch[MIC_DMA_MAX_NUM_CHAN];
132	struct dma_device dma_dev;
133	struct mbus_device *mbdev;
134	void __iomem *mmio;
135	struct dentry *dbg_dir;
136	int start_ch;
137	size_t max_xfer_size;
138	};
139
140	static inline struct mic_dma_chan to_mic_dma_chan(struct dma_chan ch)
141	{
142	return container_of(ch, struct mic_dma_chan, api_ch);
143	}
144
145	static inline struct mic_dma_device to_mic_dma_dev(struct mic_dma_chan ch)
146	{
147	return
148	container_of((const typeof(((struct mic_dma_device )0)->mic_ch))
149	(ch - ch->ch_num), struct mic_dma_device, mic_ch);
150	}
151
152	static inline struct mbus_device to_mbus_device(struct mic_dma_chan ch)
153	{
154	return to_mic_dma_dev(ch)->mbdev;
155	}
156
157	static inline struct mbus_hw_ops to_mbus_hw_ops(struct mic_dma_chan ch)
158	{
159	return to_mbus_device(ch)->hw_ops;
160	}
161
162	static inline struct device mic_dma_ch_to_device(struct mic_dma_chan ch)
163	{
164	return to_mic_dma_dev(ch)->dma_dev.dev;
165	}
166
167	static inline void __iomem mic_dma_chan_to_mmio(struct mic_dma_chan ch)
168	{
169	return to_mic_dma_dev(ch)->mmio;
170	}
171
172	static inline u32 mic_dma_read_reg(struct mic_dma_chan *ch, u32 reg)
173	{
174	return ioread32(mic_dma_chan_to_mmio(ch) + MIC_DMA_SBOX_CH_BASE +
175	ch->ch_num * MIC_DMA_SBOX_CHAN_OFF + reg);
176	}
177
178	static inline void mic_dma_write_reg(struct mic_dma_chan *ch, u32 reg, u32 val)
179	{
180	iowrite32(val, mic_dma_chan_to_mmio(ch) + MIC_DMA_SBOX_CH_BASE +
181	ch->ch_num * MIC_DMA_SBOX_CHAN_OFF + reg);
182	}
183
184	static inline u32 mic_dma_mmio_read(struct mic_dma_chan *ch, u32 offset)
185	{
186	return ioread32(mic_dma_chan_to_mmio(ch) + offset);
187	}
188
189	static inline void mic_dma_mmio_write(struct mic_dma_chan *ch, u32 val,
190	u32 offset)
191	{
192	iowrite32(val, mic_dma_chan_to_mmio(ch) + offset);
193	}
194
195	static inline u32 mic_dma_read_cmp_cnt(struct mic_dma_chan *ch)
196	{
197	return mic_dma_read_reg(ch, MIC_DMA_REG_DSTAT) &
198	MIC_DMA_HW_CMP_CNT_MASK;
199	}
200
201	static inline void mic_dma_chan_set_owner(struct mic_dma_chan *ch)
202	{
203	u32 dcr = mic_dma_mmio_read(ch, MIC_DMA_SBOX_BASE + MIC_DMA_SBOX_DCR);
204	u32 chan_num = ch->ch_num;
205
206	dcr = (dcr & ~(0x1 << (chan_num * 2))) \| (ch->owner << (chan_num * 2));
207	mic_dma_mmio_write(ch, dcr, MIC_DMA_SBOX_BASE + MIC_DMA_SBOX_DCR);
208	}
209
210	static inline void mic_dma_enable_chan(struct mic_dma_chan *ch)
211	{
212	u32 dcr = mic_dma_mmio_read(ch, MIC_DMA_SBOX_BASE + MIC_DMA_SBOX_DCR);
213
214	dcr \|= 2 << (ch->ch_num << 1);
215	mic_dma_mmio_write(ch, dcr, MIC_DMA_SBOX_BASE + MIC_DMA_SBOX_DCR);
216	}
217
218	static inline void mic_dma_disable_chan(struct mic_dma_chan *ch)
219	{
220	u32 dcr = mic_dma_mmio_read(ch, MIC_DMA_SBOX_BASE + MIC_DMA_SBOX_DCR);
221
222	dcr &= ~(2 << (ch->ch_num << 1));
223	mic_dma_mmio_write(ch, dcr, MIC_DMA_SBOX_BASE + MIC_DMA_SBOX_DCR);
224	}
225
226	static void mic_dma_chan_set_desc_ring(struct mic_dma_chan *ch)
227	{
228	u32 drar_hi;
229	dma_addr_t desc_ring_micpa = ch->desc_ring_micpa;
230
231	drar_hi = (MIC_DMA_DESC_RX_SIZE & 0x1ffff) << 4;
232	if (MIC_DMA_CHAN_MIC == ch->owner) {
233	drar_hi \|= (desc_ring_micpa >> 32) & 0xf;
234	} else {
235	drar_hi \|= MIC_DMA_SBOX_DRARHI_SYS_MASK;
236	drar_hi \|= ((desc_ring_micpa >> 34)
237	& 0x1f) << 21;
238	drar_hi \|= (desc_ring_micpa >> 32) & 0x3;
239	}
240	mic_dma_write_reg(ch, MIC_DMA_REG_DRAR_LO, (u32) desc_ring_micpa);
241	mic_dma_write_reg(ch, MIC_DMA_REG_DRAR_HI, drar_hi);
242	}
243
244	static inline void mic_dma_chan_mask_intr(struct mic_dma_chan *ch)
245	{
246	u32 dcar = mic_dma_read_reg(ch, MIC_DMA_REG_DCAR);
247
248	if (MIC_DMA_CHAN_MIC == ch->owner)
249	dcar \|= MIC_DMA_SBOX_DCAR_IM0;
250	else
251	dcar \|= MIC_DMA_SBOX_DCAR_IM1;
252	mic_dma_write_reg(ch, MIC_DMA_REG_DCAR, dcar);
253	}
254
255	static inline void mic_dma_chan_unmask_intr(struct mic_dma_chan *ch)
256	{
257	u32 dcar = mic_dma_read_reg(ch, MIC_DMA_REG_DCAR);
258
259	if (MIC_DMA_CHAN_MIC == ch->owner)
260	dcar &= ~MIC_DMA_SBOX_DCAR_IM0;
261	else
262	dcar &= ~MIC_DMA_SBOX_DCAR_IM1;
263	mic_dma_write_reg(ch, MIC_DMA_REG_DCAR, dcar);
264	}
265
266	static void mic_dma_ack_interrupt(struct mic_dma_chan *ch)
267	{
268	if (MIC_DMA_CHAN_MIC == ch->owner) {
269	/* HW errata */
270	mic_dma_chan_mask_intr(ch);
271	mic_dma_chan_unmask_intr(ch);
272	}
273	to_mbus_hw_ops(ch)->ack_interrupt(to_mbus_device(ch), ch->ch_num);
274	}
275	#endif

drivers/firmware/arm_scmi/base.c+2−0

@@ -197,6 +197,8 @@ static int scmi_base_implementation_list_get(const struct scmi_handle *handle, · 196 unmodified lines
197	protocols_imp[tot_num_ret + loop] = *(list + loop);	197	protocols_imp[tot_num_ret + loop] = *(list + loop);
198		198
199	tot_num_ret += loop_num_ret;	199	tot_num_ret += loop_num_ret;
		200
		201	scmi_reset_rx_to_maxsz(handle, t);
200	} while (loop_num_ret);	202	} while (loop_num_ret);
201		203
202	scmi_xfer_put(handle, t);	204	scmi_xfer_put(handle, t);

drivers/firmware/arm_scmi/clock.c+2−0

@@ -192,6 +192,8 @@ scmi_clock_describe_rates_get(const struct scmi_handle *handle, u32 clk_id, · 191 unmodified lines
192	}	192	}
193		193
194	tot_rate_cnt += num_returned;	194	tot_rate_cnt += num_returned;
		195
		196	scmi_reset_rx_to_maxsz(handle, t);
195	/*	197	/*
196	* check for both returned and remaining to avoid infinite	198	* check for both returned and remaining to avoid infinite
197	* loop due to buggy firmware	199	* loop due to buggy firmware

drivers/firmware/arm_scmi/common.h+2−0

 			       struct scmi_xfer *xfer);
 int scmi_xfer_get_init(const struct scmi_handle *h, u8 msg_id, u8 prot_id,
 		       size_t tx_size, size_t rx_size, struct scmi_xfer **p);
+void scmi_reset_rx_to_maxsz(const struct scmi_handle *handle,
+			    struct scmi_xfer *xfer);
 int scmi_handle_put(const struct scmi_handle *handle);
 struct scmi_handle *scmi_handle_get(struct device *dev);
 void scmi_set_handle(struct scmi_device *scmi_dev);

drivers/firmware/arm_scmi/driver.c+8−0

@@ -402,6 +402,14 @@ int scmi_do_xfer(const struct scmi_handle handle, struct scmi_xfer xfer) · 401 unmodified lines
402	return ret;	402	return ret;
403	}	403	}
404		404
		405	void scmi_reset_rx_to_maxsz(const struct scmi_handle *handle,
		406	struct scmi_xfer *xfer)
		407	{
		408	struct scmi_info *info = handle_to_scmi_info(handle);
		409
		410	xfer->rx.len = info->desc->max_msg_size;
		411	}
		412
405	#define SCMI_MAX_RESPONSE_TIMEOUT (2 * MSEC_PER_SEC)	413	#define SCMI_MAX_RESPONSE_TIMEOUT (2 * MSEC_PER_SEC)
406		414
407	/**	415	/**

drivers/firmware/arm_scmi/notify.c+14−8

 				"finalized PENDING handler - key:%X\n",
 				hndl->key);
 			ret = scmi_event_handler_enable_events(hndl);
+			if (ret) {
+				dev_dbg(ni->handle->dev,
+					"purging INVALID handler - key:%X\n",
+					hndl->key);
+				scmi_put_active_handler(ni, hndl);
+			}
 		} else {
 			ret = scmi_valid_pending_handler(ni, hndl);
-		}
+			if (ret) {
-		if (ret) {
+				dev_dbg(ni->handle->dev,
-			dev_dbg(ni->handle->dev,
+					"purging PENDING handler - key:%X\n",
-				"purging PENDING handler - key:%X\n",
+					hndl->key);
-				hndl->key);
+				/* this hndl can be only a pending one */
-			/* this hndl can be only a pending one */
+				scmi_put_handler_unlocked(ni, hndl);
-			scmi_put_handler_unlocked(ni, hndl);
+			}
 		}
 	}
 	mutex_unlock(&ni->pending_mtx);
 	ni->gid = gid;
 	ni->handle = handle;
-	ni->notify_wq = alloc_workqueue("scmi_notify",
+	ni->notify_wq = alloc_workqueue(dev_name(handle->dev),
 					WQ_UNBOUND | WQ_FREEZABLE | WQ_SYSFS,
 					0);
 	if (!ni->notify_wq)

drivers/firmware/arm_scmi/perf.c+2−0

@@ -304,6 +304,8 @@ scmi_perf_describe_levels_get(const struct scmi_handle *handle, u32 domain, · 303 unmodified lines
304	}	304	}
305		305
306	tot_opp_cnt += num_returned;	306	tot_opp_cnt += num_returned;
		307
		308	scmi_reset_rx_to_maxsz(handle, t);
307	/*	309	/*
308	* check for both returned and remaining to avoid infinite	310	* check for both returned and remaining to avoid infinite
309	* loop due to buggy firmware	311	* loop due to buggy firmware

drivers/firmware/arm_scmi/reset.c+1−3

 #define EXPLICIT_RESET_ASSERT	BIT(1)
 #define ASYNCHRONOUS_RESET	BIT(2)
 	__le32 reset_state;
-#define ARCH_RESET_TYPE		BIT(31)
+#define ARCH_COLD_RESET		0
-#define COLD_RESET_STATE	BIT(0)
-#define ARCH_COLD_RESET		(ARCH_RESET_TYPE | COLD_RESET_STATE)
 };
 struct scmi_msg_reset_notify {

drivers/firmware/arm_scmi/sensors.c+2−0

@@ -166,6 +166,8 @@ static int scmi_sensor_description_get(const struct scmi_handle *handle, · 165 unmodified lines
166	}	166	}
167		167
168	desc_index += num_returned;	168	desc_index += num_returned;
		169
		170	scmi_reset_rx_to_maxsz(handle, t);
169	/*	171	/*
170	* check for both returned and remaining to avoid infinite	172	* check for both returned and remaining to avoid infinite
171	* loop due to buggy firmware	173	* loop due to buggy firmware

drivers/firmware/arm_scmi/smc.c+1−1

@@ -149,6 +149,6 @@ static const struct scmi_transport_ops scmi_smc_ops = { · 148 unmodified lines
149	const struct scmi_desc scmi_smc_desc = {	149	const struct scmi_desc scmi_smc_desc = {
150	.ops = &scmi_smc_ops,	150	.ops = &scmi_smc_ops,
151	.max_rx_timeout_ms = 30,	151	.max_rx_timeout_ms = 30,
152	.max_msg = 1,	152	.max_msg = 20,
153	.max_msg_size = 128,	153	.max_msg_size = 128,
154	};	154	};

drivers/gpu/drm/amd/amdgpu/amdgpu_device.c+24−18

 MODULE_FIRMWARE("amdgpu/navi10_gpu_info.bin");
 MODULE_FIRMWARE("amdgpu/navi14_gpu_info.bin");
 MODULE_FIRMWARE("amdgpu/navi12_gpu_info.bin");
+MODULE_FIRMWARE("amdgpu/green_sardine_gpu_info.bin");
 #define AMDGPU_RESUME_MS		2000
 	return amdgpu_asic_supports_baco(adev);
 }
+/*
+ * VRAM access helper functions
+ */
 /**
- * VRAM access helper functions.
- *
  * amdgpu_device_vram_access - read/write a buffer in vram
  *
  * @adev: amdgpu_device pointer
 /**
  * amdgpu_invalid_rreg - dummy reg read function
  *
- * @adev: amdgpu device pointer
+ * @adev: amdgpu_device pointer
  * @reg: offset of register
  *
  * Dummy register read function.  Used for register blocks
 /**
  * amdgpu_invalid_wreg - dummy reg write function
  *
- * @adev: amdgpu device pointer
+ * @adev: amdgpu_device pointer
  * @reg: offset of register
  * @v: value to write to the register
  *
 /**
  * amdgpu_invalid_rreg64 - dummy 64 bit reg read function
  *
- * @adev: amdgpu device pointer
+ * @adev: amdgpu_device pointer
  * @reg: offset of register
  *
  * Dummy register read function.  Used for register blocks
 /**
  * amdgpu_invalid_wreg64 - dummy reg write function
  *
- * @adev: amdgpu device pointer
+ * @adev: amdgpu_device pointer
  * @reg: offset of register
  * @v: value to write to the register
  *
 /**
  * amdgpu_block_invalid_rreg - dummy reg read function
  *
- * @adev: amdgpu device pointer
+ * @adev: amdgpu_device pointer
  * @block: offset of instance
  * @reg: offset of register
  *
 /**
  * amdgpu_block_invalid_wreg - dummy reg write function
  *
- * @adev: amdgpu device pointer
+ * @adev: amdgpu_device pointer
  * @block: offset of instance
  * @reg: offset of register
  * @v: value to write to the register
 /**
  * amdgpu_device_asic_init - Wrapper for atom asic_init
  *
- * @dev: drm_device pointer
+ * @adev: amdgpu_device pointer
  *
  * Does any asic specific work and then calls atom asic init.
  */
 /**
  * amdgpu_device_vram_scratch_init - allocate the VRAM scratch page
  *
- * @adev: amdgpu device pointer
+ * @adev: amdgpu_device pointer
  *
  * Allocates a scratch page of VRAM for use by various things in the
  * driver.
 /**
  * amdgpu_device_vram_scratch_fini - Free the VRAM scratch page
  *
- * @adev: amdgpu device pointer
+ * @adev: amdgpu_device pointer
  *
  * Frees the VRAM scratch page.
  */
 		chip_name = "arcturus";
 		break;
 	case CHIP_RENOIR:
-		chip_name = "renoir";
+		if (adev->apu_flags & AMD_APU_IS_RENOIR)
+			chip_name = "renoir";
+		else
+			chip_name = "green_sardine";
 		break;
 	case CHIP_NAVI10:
 		chip_name = "navi10";
 /**
  * amdgpu_device_has_dc_support - check if dc is supported
  *
- * @adev: amdgpu_device_pointer
+ * @adev: amdgpu_device pointer
  *
  * Returns true for supported, false for not supported
  */
 /**
  * amdgpu_device_reset_sriov - reset ASIC for SR-IOV vf
  *
- * @adev: amdgpu device pointer
+ * @adev: amdgpu_device pointer
  * @from_hypervisor: request from hypervisor
  *
  * do VF FLR and reinitialize Asic
 /**
  * amdgpu_device_has_job_running - check if there is any job in mirror list
  *
- * @adev: amdgpu device pointer
+ * @adev: amdgpu_device pointer
  *
  * check if there is any job in mirror list
  */
 /**
  * amdgpu_device_should_recover_gpu - check if we should try GPU recovery
  *
- * @adev: amdgpu device pointer
+ * @adev: amdgpu_device pointer
  *
  * Check amdgpu_gpu_recovery and SRIOV status to see if we should try to recover
  * a hung GPU.
 /**
  * amdgpu_device_gpu_recover - reset the asic and recover scheduler
  *
- * @adev: amdgpu device pointer
+ * @adev: amdgpu_device pointer
  * @job: which job trigger hang
  *
  * Attempt to reset the GPU if it has hung (all asics).
 	bool need_emergency_restart = false;
 	bool audio_suspended = false;
-	/**
+	/*
 	 * Special case: RAS triggered and full reset isn't supported
 	 */
 	need_emergency_restart = amdgpu_ras_need_emergency_restart(adev);

drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c+1−0

@@ -1066,6 +1066,7 @@ static const struct pci_device_id pciidlist[] = { · 1065 unmodified lines
1066	{0x1002, 0x7319, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_NAVI10},	1066	{0x1002, 0x7319, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_NAVI10},
1067	{0x1002, 0x731A, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_NAVI10},	1067	{0x1002, 0x731A, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_NAVI10},
1068	{0x1002, 0x731B, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_NAVI10},	1068	{0x1002, 0x731B, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_NAVI10},
		1069	{0x1002, 0x731E, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_NAVI10},
1069	{0x1002, 0x731F, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_NAVI10},	1070	{0x1002, 0x731F, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_NAVI10},
1070	/* Navi14 */	1071	/* Navi14 */
1071	{0x1002, 0x7340, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_NAVI14},	1072	{0x1002, 0x7340, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_NAVI14},

drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c+10−0

 	struct ww_acquire_ctx ticket;
 	struct list_head list, duplicates;
 	uint64_t va_flags;
+	uint64_t vm_size;
 	int r = 0;
 	if (args->va_address < AMDGPU_VA_RESERVED_SIZE) {
 	args->va_address &= AMDGPU_GMC_HOLE_MASK;
+	vm_size = adev->vm_manager.max_pfn * AMDGPU_GPU_PAGE_SIZE;
+	vm_size -= AMDGPU_VA_RESERVED_SIZE;
+	if (args->va_address + args->map_size > vm_size) {
+		dev_dbg(&dev->pdev->dev,
+			"va_address 0x%llx is in top reserved area 0x%llx\n",
+			args->va_address + args->map_size, vm_size);
+		return -EINVAL;
+	}
 	if ((args->flags & ~valid_flags) && (args->flags & ~prt_flags)) {
 		dev_dbg(&dev->pdev->dev, "invalid flags combination 0x%08X\n",
 			args->flags);

drivers/gpu/drm/amd/amdgpu/amdgpu_gtt_mgr.c+3−3

@@ -81,8 +81,8 @@ static const struct ttm_resource_manager_func amdgpu_gtt_mgr_func; · 80 unmodified lines
81	/**	81	/**
82	* amdgpu_gtt_mgr_init - init GTT manager and DRM MM	82	* amdgpu_gtt_mgr_init - init GTT manager and DRM MM
83	*	83	*
84	* @man: TTM memory type manager	84	* @adev: amdgpu_device pointer
85	* @p_size: maximum size of GTT	85	* @gtt_size: maximum size of GTT
86	*	86	*
87	* Allocate and initialize the GTT manager.	87	* Allocate and initialize the GTT manager.
88	*/	88	*/
@@ -123,7 +123,7 @@ int amdgpu_gtt_mgr_init(struct amdgpu_device *adev, uint64_t gtt_size) · 34 unmodified lines
123	/**	123	/**
124	* amdgpu_gtt_mgr_fini - free and destroy GTT manager	124	* amdgpu_gtt_mgr_fini - free and destroy GTT manager
125	*	125	*
126	* @man: TTM memory type manager	126	* @adev: amdgpu_device pointer
127	*	127	*
128	* Destroy and free the GTT manager, returns -EBUSY if ranges are still	128	* Destroy and free the GTT manager, returns -EBUSY if ranges are still
129	* allocated inside it.	129	* allocated inside it.

drivers/gpu/drm/amd/amdgpu/amdgpu_psp.c+1−0

@@ -2524,6 +2524,7 @@ int parse_ta_bin_descriptor(struct psp_context *psp, · 2523 unmodified lines
2524	psp->asd_feature_version = le32_to_cpu(desc->fw_version);	2524	psp->asd_feature_version = le32_to_cpu(desc->fw_version);
2525	psp->asd_ucode_size = le32_to_cpu(desc->size_bytes);	2525	psp->asd_ucode_size = le32_to_cpu(desc->size_bytes);
2526	psp->asd_start_addr = ucode_start_addr;	2526	psp->asd_start_addr = ucode_start_addr;
		2527	psp->asd_fw = psp->ta_fw;
2527	break;	2528	break;
2528	case TA_FW_TYPE_PSP_XGMI:	2529	case TA_FW_TYPE_PSP_XGMI:
2529	psp->ta_xgmi_ucode_version = le32_to_cpu(desc->fw_version);	2530	psp->ta_xgmi_ucode_version = le32_to_cpu(desc->fw_version);

drivers/gpu/drm/amd/amdgpu/amdgpu_vcn.c+7−1

 #define FIRMWARE_RAVEN2		"amdgpu/raven2_vcn.bin"
 #define FIRMWARE_ARCTURUS 	"amdgpu/arcturus_vcn.bin"
 #define FIRMWARE_RENOIR 	"amdgpu/renoir_vcn.bin"
+#define FIRMWARE_GREEN_SARDINE 	"amdgpu/green_sardine_vcn.bin"
 #define FIRMWARE_NAVI10 	"amdgpu/navi10_vcn.bin"
 #define FIRMWARE_NAVI14 	"amdgpu/navi14_vcn.bin"
 #define FIRMWARE_NAVI12 	"amdgpu/navi12_vcn.bin"
 MODULE_FIRMWARE(FIRMWARE_RAVEN2);
 MODULE_FIRMWARE(FIRMWARE_ARCTURUS);
 MODULE_FIRMWARE(FIRMWARE_RENOIR);
+MODULE_FIRMWARE(FIRMWARE_GREEN_SARDINE);
 MODULE_FIRMWARE(FIRMWARE_NAVI10);
 MODULE_FIRMWARE(FIRMWARE_NAVI14);
 MODULE_FIRMWARE(FIRMWARE_NAVI12);
 			adev->vcn.indirect_sram = true;
 		break;
 	case CHIP_RENOIR:
-		fw_name = FIRMWARE_RENOIR;
+		if (adev->apu_flags & AMD_APU_IS_RENOIR)
+			fw_name = FIRMWARE_RENOIR;
+		else
+			fw_name = FIRMWARE_GREEN_SARDINE;
 		if ((adev->firmware.load_type == AMDGPU_FW_LOAD_PSP) &&
 		    (adev->pg_flags & AMD_PG_SUPPORT_VCN_DPG))
 			adev->vcn.indirect_sram = true;

drivers/gpu/drm/amd/amdgpu/amdgpu_vm.h+2−2

@@ -112,8 +112,8 @@ struct amdgpu_bo_list_entry; · 111 unmodified lines
112	#define AMDGPU_MMHUB_0 1	112	#define AMDGPU_MMHUB_0 1
113	#define AMDGPU_MMHUB_1 2	113	#define AMDGPU_MMHUB_1 2
114		114
115	/* hardcode that limit for now */	115	/* Reserve 2MB at top/bottom of address space for kernel use */
116	#define AMDGPU_VA_RESERVED_SIZE (1ULL << 20)	116	#define AMDGPU_VA_RESERVED_SIZE (2ULL << 20)
117		117
118	/* max vmids dedicated for process */	118	/* max vmids dedicated for process */
119	#define AMDGPU_VM_MAX_RESERVED_VMID 1	119	#define AMDGPU_VM_MAX_RESERVED_VMID 1

drivers/gpu/drm/amd/amdgpu/amdgpu_vram_mgr.c+3−4

 /**
  * amdgpu_vram_mgr_init - init VRAM manager and DRM MM
  *
- * @man: TTM memory type manager
+ * @adev: amdgpu_device pointer
- * @p_size: maximum size of VRAM
  *
  * Allocate and initialize the VRAM manager.
  */
 /**
  * amdgpu_vram_mgr_fini - free and destroy VRAM manager
  *
- * @man: TTM memory type manager
+ * @adev: amdgpu_device pointer
  *
  * Destroy and free the VRAM manager, returns -EBUSY if ranges are still
  * allocated inside it.
 /**
  * amdgpu_vram_mgr_vis_size - Calculate visible node size
  *
- * @adev: amdgpu device structure
+ * @adev: amdgpu_device pointer
  * @node: MM node structure
  *
  * Calculate how many bytes of the MM node are inside visible VRAM

drivers/gpu/drm/amd/amdgpu/cik.c+3−1

 	switch (adev->asic_type) {
 	case CHIP_BONAIRE:
-	case CHIP_HAWAII:
 		/* disable baco reset until it works */
 		/* smu7_asic_get_baco_capability(adev, &baco_reset); */
 		baco_reset = false;
 		break;
+	case CHIP_HAWAII:
+		baco_reset = cik_asic_supports_baco(adev);
+		break;
 	default:
 		baco_reset = false;
 		break;

drivers/gpu/drm/amd/amdgpu/cik_sdma.c+12−15

@@ -1071,22 +1071,19 @@ static int cik_sdma_soft_reset(void *handle) · 1070 unmodified lines
1071	{	1071	{
1072	u32 srbm_soft_reset = 0;	1072	u32 srbm_soft_reset = 0;
1073	struct amdgpu_device adev = (struct amdgpu_device )handle;	1073	struct amdgpu_device adev = (struct amdgpu_device )handle;
1074	u32 tmp = RREG32(mmSRBM_STATUS2);	1074	u32 tmp;
1075		1075
1076	if (tmp & SRBM_STATUS2__SDMA_BUSY_MASK) {	1076	/* sdma0 */
1077	/* sdma0 */	1077	tmp = RREG32(mmSDMA0_F32_CNTL + SDMA0_REGISTER_OFFSET);
1078	tmp = RREG32(mmSDMA0_F32_CNTL + SDMA0_REGISTER_OFFSET);	1078	tmp \|= SDMA0_F32_CNTL__HALT_MASK;
1079	tmp \|= SDMA0_F32_CNTL__HALT_MASK;	1079	WREG32(mmSDMA0_F32_CNTL + SDMA0_REGISTER_OFFSET, tmp);
1080	WREG32(mmSDMA0_F32_CNTL + SDMA0_REGISTER_OFFSET, tmp);	1080	srbm_soft_reset \|= SRBM_SOFT_RESET__SOFT_RESET_SDMA_MASK;
1081	srbm_soft_reset \|= SRBM_SOFT_RESET__SOFT_RESET_SDMA_MASK;	1081
1082	}	1082	/* sdma1 */
1083	if (tmp & SRBM_STATUS2__SDMA1_BUSY_MASK) {	1083	tmp = RREG32(mmSDMA0_F32_CNTL + SDMA1_REGISTER_OFFSET);
1084	/* sdma1 */	1084	tmp \|= SDMA0_F32_CNTL__HALT_MASK;
1085	tmp = RREG32(mmSDMA0_F32_CNTL + SDMA1_REGISTER_OFFSET);	1085	WREG32(mmSDMA0_F32_CNTL + SDMA1_REGISTER_OFFSET, tmp);
1086	tmp \|= SDMA0_F32_CNTL__HALT_MASK;	1086	srbm_soft_reset \|= SRBM_SOFT_RESET__SOFT_RESET_SDMA1_MASK;
1087	WREG32(mmSDMA0_F32_CNTL + SDMA1_REGISTER_OFFSET, tmp);
1088	srbm_soft_reset \|= SRBM_SOFT_RESET__SOFT_RESET_SDMA1_MASK;
1089	}
1090		1087
1091	if (srbm_soft_reset) {	1088	if (srbm_soft_reset) {
1092	tmp = RREG32(mmSRBM_SOFT_RESET);	1089	tmp = RREG32(mmSRBM_SOFT_RESET);

drivers/gpu/drm/amd/amdgpu/gfx_v10_0.c+4−0

 #define PA_SC_ENHANCE_3__FORCE_PBB_WORKLOAD_MODE_TO_ZERO__SHIFT 0x3
 #define PA_SC_ENHANCE_3__FORCE_PBB_WORKLOAD_MODE_TO_ZERO_MASK   0x00000008L
+#define mmCGTT_SPI_CS_CLK_CTRL			0x507c
+#define mmCGTT_SPI_CS_CLK_CTRL_BASE_IDX         1
 MODULE_FIRMWARE("amdgpu/navi10_ce.bin");
 MODULE_FIRMWARE("amdgpu/navi10_pfp.bin");
 MODULE_FIRMWARE("amdgpu/navi10_me.bin");
 static const struct soc15_reg_golden golden_settings_gc_10_3[] =
 {
+	SOC15_REG_GOLDEN_VALUE(GC, 0, mmCGTT_SPI_CS_CLK_CTRL, 0x78000000, 0x78000100),
 	SOC15_REG_GOLDEN_VALUE(GC, 0, mmCGTT_SPI_PS_CLK_CTRL, 0xff7f0fff, 0x78000100),
 	SOC15_REG_GOLDEN_VALUE(GC, 0, mmCGTT_SPI_RA0_CLK_CTRL, 0xff7f0fff, 0x30000100),
 	SOC15_REG_GOLDEN_VALUE(GC, 0, mmCGTT_SPI_RA1_CLK_CTRL, 0xff7f0fff, 0x7e000100),

drivers/gpu/drm/amd/amdgpu/gfx_v9_0.c+11−1

 MODULE_FIRMWARE("amdgpu/renoir_mec2.bin");
 MODULE_FIRMWARE("amdgpu/renoir_rlc.bin");
+MODULE_FIRMWARE("amdgpu/green_sardine_ce.bin");
+MODULE_FIRMWARE("amdgpu/green_sardine_pfp.bin");
+MODULE_FIRMWARE("amdgpu/green_sardine_me.bin");
+MODULE_FIRMWARE("amdgpu/green_sardine_mec.bin");
+MODULE_FIRMWARE("amdgpu/green_sardine_mec2.bin");
+MODULE_FIRMWARE("amdgpu/green_sardine_rlc.bin");
 #define mmTCP_CHAN_STEER_0_ARCT								0x0b03
 #define mmTCP_CHAN_STEER_0_ARCT_BASE_IDX							0
 #define mmTCP_CHAN_STEER_1_ARCT								0x0b04
 		chip_name = "arcturus";
 		break;
 	case CHIP_RENOIR:
-		chip_name = "renoir";
+		if (adev->apu_flags & AMD_APU_IS_RENOIR)
+			chip_name = "renoir";
+		else
+			chip_name = "green_sardine";
 		break;
 	default:
 		BUG();

drivers/gpu/drm/amd/amdgpu/nv.c+13−2

 	adev->virt.ops = &xgpu_nv_virt_ops;
 }
+static bool nv_is_headless_sku(struct pci_dev *pdev)
+{
+	if ((pdev->device == 0x731E &&
+	    (pdev->revision == 0xC6 || pdev->revision == 0xC7)) ||
+	    (pdev->device == 0x7340 && pdev->revision == 0xC9))
+		return true;
+	return false;
+}
 int nv_set_ip_blocks(struct amdgpu_device *adev)
 {
 	int r;
 		if (adev->enable_virtual_display || amdgpu_sriov_vf(adev))
 			amdgpu_device_ip_block_add(adev, &dce_virtual_ip_block);
 #if defined(CONFIG_DRM_AMD_DC)
-		else if (amdgpu_device_has_dc_support(adev))
+		else if (amdgpu_device_has_dc_support(adev) &&
+			 !nv_is_headless_sku(adev->pdev))
 			amdgpu_device_ip_block_add(adev, &dm_ip_block);
 #endif
 		amdgpu_device_ip_block_add(adev, &gfx_v10_0_ip_block);
 		if (adev->firmware.load_type == AMDGPU_FW_LOAD_DIRECT &&
 		    !amdgpu_sriov_vf(adev))
 			amdgpu_device_ip_block_add(adev, &smu_v11_0_ip_block);
-		amdgpu_device_ip_block_add(adev, &vcn_v2_0_ip_block);
+		if (!nv_is_headless_sku(adev->pdev))
+			amdgpu_device_ip_block_add(adev, &vcn_v2_0_ip_block);
 		amdgpu_device_ip_block_add(adev, &jpeg_v2_0_ip_block);
 		if (adev->enable_mes)
 			amdgpu_device_ip_block_add(adev, &mes_v10_1_ip_block);

drivers/gpu/drm/amd/amdgpu/psp_v12_0.c+5−1

 MODULE_FIRMWARE("amdgpu/renoir_asd.bin");
 MODULE_FIRMWARE("amdgpu/renoir_ta.bin");
+MODULE_FIRMWARE("amdgpu/green_sardine_asd.bin");
 /* address block */
 #define smnMP1_FIRMWARE_FLAGS		0x3010024
 	switch (adev->asic_type) {
 	case CHIP_RENOIR:
-		chip_name = "renoir";
+		if (adev->apu_flags & AMD_APU_IS_RENOIR)
+			chip_name = "renoir";
+		else
+			chip_name = "green_sardine";
 		break;
 	default:
 		BUG();

drivers/gpu/drm/amd/amdgpu/sdma_v4_0.c+5−1

 MODULE_FIRMWARE("amdgpu/raven2_sdma.bin");
 MODULE_FIRMWARE("amdgpu/arcturus_sdma.bin");
 MODULE_FIRMWARE("amdgpu/renoir_sdma.bin");
+MODULE_FIRMWARE("amdgpu/green_sardine_sdma.bin");
 #define SDMA0_POWER_CNTL__ON_OFF_CONDITION_HOLD_TIME_MASK  0x000000F8L
 #define SDMA0_POWER_CNTL__ON_OFF_STATUS_DURATION_TIME_MASK 0xFC000000L
 		chip_name = "arcturus";
 		break;
 	case CHIP_RENOIR:
-		chip_name = "renoir";
+		if (adev->apu_flags & AMD_APU_IS_RENOIR)
+			chip_name = "renoir";
+		else
+			chip_name = "green_sardine";
 		break;
 	default:
 		BUG();

drivers/gpu/drm/amd/amdgpu/soc15.c+10−4

 			adev->pg_flags = AMD_PG_SUPPORT_SDMA |
 				AMD_PG_SUPPORT_MMHUB |
-				AMD_PG_SUPPORT_VCN |
+				AMD_PG_SUPPORT_VCN;
-				AMD_PG_SUPPORT_VCN_DPG;
 		} else {
 			adev->cg_flags = AMD_CG_SUPPORT_GFX_MGCG |
 				AMD_CG_SUPPORT_GFX_MGLS |
 		break;
 	case CHIP_RENOIR:
 		adev->asic_funcs = &soc15_asic_funcs;
-		adev->apu_flags |= AMD_APU_IS_RENOIR;
+		if (adev->pdev->device == 0x1636)
+			adev->apu_flags |= AMD_APU_IS_RENOIR;
+		else
+			adev->apu_flags |= AMD_APU_IS_GREEN_SARDINE;
+		if (adev->apu_flags & AMD_APU_IS_RENOIR)
+			adev->external_rev_id = adev->rev_id + 0x91;
+		else
+			adev->external_rev_id = adev->rev_id + 0xa1;
 		adev->cg_flags = AMD_CG_SUPPORT_GFX_MGCG |
 				 AMD_CG_SUPPORT_GFX_MGLS |
 				 AMD_CG_SUPPORT_GFX_3D_CGCG |
 				 AMD_PG_SUPPORT_VCN |
 				 AMD_PG_SUPPORT_JPEG |
 				 AMD_PG_SUPPORT_VCN_DPG;
-		adev->external_rev_id = adev->rev_id + 0x91;
 		break;
 	default:
 		/* FIXME: not supported yet */

drivers/gpu/drm/amd/amdkfd/kfd_crat.c+1−1

 	}
 	pcrat_image = kvmalloc(crat_table->length, GFP_KERNEL);
-	memcpy(pcrat_image, crat_table, crat_table->length);
 	if (!pcrat_image)
 		return -ENOMEM;
+	memcpy(pcrat_image, crat_table, crat_table->length);
 	*crat_image = pcrat_image;
 	*size = crat_table->length;

drivers/gpu/drm/amd/display/Kconfig+1−0

@@ -42,6 +42,7 @@ config DRM_AMD_DC_SI · 41 unmodified lines
42	config DEBUG_KERNEL_DC	42	config DEBUG_KERNEL_DC
43	bool "Enable kgdb break in DC"	43	bool "Enable kgdb break in DC"
44	depends on DRM_AMD_DC	44	depends on DRM_AMD_DC
		45	depends on KGDB
45	help	46	help
46	Choose this option if you want to hit kdgb_break in assert.	47	Choose this option if you want to hit kdgb_break in assert.
47		48

drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c+7−1

 #define FIRMWARE_NAVY_FLOUNDER_DMUB "amdgpu/navy_flounder_dmcub.bin"
 MODULE_FIRMWARE(FIRMWARE_NAVY_FLOUNDER_DMUB);
 #endif
+#define FIRMWARE_GREEN_SARDINE_DMUB "amdgpu/green_sardine_dmcub.bin"
+MODULE_FIRMWARE(FIRMWARE_GREEN_SARDINE_DMUB);
 #define FIRMWARE_RAVEN_DMCU		"amdgpu/raven_dmcu.bin"
 MODULE_FIRMWARE(FIRMWARE_RAVEN_DMCU);
 {
 	struct drm_device *dev = connector->dev;
 	struct amdgpu_device *adev = drm_to_adev(dev);
-	struct dm_comressor_info *compressor = &adev->dm.compressor;
+	struct dm_compressor_info *compressor = &adev->dm.compressor;
 	struct amdgpu_dm_connector *aconn = to_amdgpu_dm_connector(connector);
 	struct drm_display_mode *mode;
 	unsigned long max_size = 0;
 	case CHIP_RAVEN:
 	case CHIP_RENOIR:
 		init_data.flags.gpu_vm_support = true;
+		if (ASICREV_IS_GREEN_SARDINE(adev->external_rev_id))
+			init_data.flags.disable_dmcu = true;
 		break;
 	default:
 		break;
 	case CHIP_RENOIR:
 		dmub_asic = DMUB_ASIC_DCN21;
 		fw_name_dmub = FIRMWARE_RENOIR_DMUB;
+		if (ASICREV_IS_GREEN_SARDINE(adev->external_rev_id))
+			fw_name_dmub = FIRMWARE_GREEN_SARDINE_DMUB;
 		break;
 #if defined(CONFIG_DRM_AMD_DC_DCN3_0)
 	case CHIP_SIENNA_CICHLID:

drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.h+3−3

@@ -86,7 +86,7 @@ struct irq_list_head { · 85 unmodified lines
86	* @bo_ptr: Pointer to the buffer object	86	* @bo_ptr: Pointer to the buffer object
87	* @gpu_addr: MMIO gpu addr	87	* @gpu_addr: MMIO gpu addr
88	*/	88	*/
89	struct dm_comressor_info {	89	struct dm_compressor_info {
90	void *cpu_addr;	90	void *cpu_addr;
91	struct amdgpu_bo *bo_ptr;	91	struct amdgpu_bo *bo_ptr;
92	uint64_t gpu_addr;	92	uint64_t gpu_addr;
@@ -148,7 +148,7 @@ struct amdgpu_dm_backlight_caps { · 55 unmodified lines
148	* @soc_bounding_box: SOC bounding box values provided by gpu_info FW	148	* @soc_bounding_box: SOC bounding box values provided by gpu_info FW
149	* @cached_state: Caches device atomic state for suspend/resume	149	* @cached_state: Caches device atomic state for suspend/resume
150	* @cached_dc_state: Cached state of content streams	150	* @cached_dc_state: Cached state of content streams
151	* @compressor: Frame buffer compression buffer. See &struct dm_comressor_info	151	* @compressor: Frame buffer compression buffer. See &struct dm_compressor_info
152	* @force_timing_sync: set via debugfs. When set, indicates that all connected	152	* @force_timing_sync: set via debugfs. When set, indicates that all connected
153	* displays will be forced to synchronize.	153	* displays will be forced to synchronize.
154	*/	154	*/
@@ -324,7 +324,7 @@ struct amdgpu_display_manager { · 169 unmodified lines
324	struct drm_atomic_state *cached_state;	324	struct drm_atomic_state *cached_state;
325	struct dc_state *cached_dc_state;	325	struct dc_state *cached_dc_state;
326		326
327	struct dm_comressor_info compressor;	327	struct dm_compressor_info compressor;
328		328
329	const struct firmware *fw_dmcu;	329	const struct firmware *fw_dmcu;
330	uint32_t dmcu_fw_version;	330	uint32_t dmcu_fw_version;

drivers/gpu/drm/amd/display/dc/clk_mgr/clk_mgr.c+5−0

 			rn_clk_mgr_construct(ctx, clk_mgr, pp_smu, dccg);
 			break;
 		}
+		if (ASICREV_IS_GREEN_SARDINE(asic_id.hw_internal_rev)) {
+			rn_clk_mgr_construct(ctx, clk_mgr, pp_smu, dccg);
+			break;
+		}
 		if (ASICREV_IS_RAVEN2(asic_id.hw_internal_rev)) {
 			rv2_clk_mgr_construct(ctx, clk_mgr, pp_smu);
 			break;

drivers/gpu/drm/amd/display/dc/core/dc.c+2−2

@@ -1571,8 +1571,8 @@ static void init_state(struct dc dc, struct dc_state context) · 1570 unmodified lines
1571		1571
1572	struct dc_state dc_create_state(struct dc dc)	1572	struct dc_state dc_create_state(struct dc dc)
1573	{	1573	{
1574	struct dc_state *context = kzalloc(sizeof(struct dc_state),	1574	struct dc_state *context = kvzalloc(sizeof(struct dc_state),
1575	GFP_KERNEL);	1575	GFP_KERNEL);
1576		1576
1577	if (!context)	1577	if (!context)
1578	return NULL;	1578	return NULL;

drivers/gpu/drm/amd/display/dc/core/dc_resource.c+2−0

@@ -120,6 +120,8 @@ enum dce_version resource_parse_asic_id(struct hw_asic_id asic_id) · 119 unmodified lines
120	dc_version = DCN_VERSION_1_01;	120	dc_version = DCN_VERSION_1_01;
121	if (ASICREV_IS_RENOIR(asic_id.hw_internal_rev))	121	if (ASICREV_IS_RENOIR(asic_id.hw_internal_rev))
122	dc_version = DCN_VERSION_2_1;	122	dc_version = DCN_VERSION_2_1;
		123	if (ASICREV_IS_GREEN_SARDINE(asic_id.hw_internal_rev))
		124	dc_version = DCN_VERSION_2_1;
123	break;	125	break;
124	#endif	126	#endif
125		127

drivers/gpu/drm/amd/display/dc/dce/dce_clock_source.c+2−1

 static const struct clock_source_funcs dcn3_clk_src_funcs = {
 	.cs_power_down = dce110_clock_source_power_down,
 	.program_pix_clk = dcn3_program_pix_clk,
-	.get_pix_clk_dividers = dcn3_get_pix_clk_dividers
+	.get_pix_clk_dividers = dcn3_get_pix_clk_dividers,
+	.get_pixel_clk_frequency_100hz = get_pixel_clk_frequency_100hz
 };
 #endif
 /*****************************************/

drivers/gpu/drm/amd/display/dc/dcn30/dcn30_resource.c+7−5

 		if (split[i]) {
 			if (odm) {
-				if (split[i] == 4 && old_pipe->next_odm_pipe->next_odm_pipe)
+				if (split[i] == 4 && old_pipe->next_odm_pipe && old_pipe->next_odm_pipe->next_odm_pipe)
 					old_index = old_pipe->next_odm_pipe->next_odm_pipe->pipe_idx;
 				else if (old_pipe->next_odm_pipe)
 					old_index = old_pipe->next_odm_pipe->pipe_idx;
 			} else {
-				if (split[i] == 4 && old_pipe->bottom_pipe->bottom_pipe &&
+				if (split[i] == 4 && old_pipe->bottom_pipe && old_pipe->bottom_pipe->bottom_pipe &&
 						old_pipe->bottom_pipe->bottom_pipe->plane_state == old_pipe->plane_state)
 					old_index = old_pipe->bottom_pipe->bottom_pipe->pipe_idx;
 				else if (old_pipe->bottom_pipe &&
 				goto validate_fail;
 			newly_split[pipe_4to1->pipe_idx] = true;
-			if (odm && old_pipe->next_odm_pipe->next_odm_pipe->next_odm_pipe)
+			if (odm && old_pipe->next_odm_pipe && old_pipe->next_odm_pipe->next_odm_pipe
+					&& old_pipe->next_odm_pipe->next_odm_pipe->next_odm_pipe)
 				old_index = old_pipe->next_odm_pipe->next_odm_pipe->next_odm_pipe->pipe_idx;
-			else if (!odm && old_pipe->bottom_pipe->bottom_pipe->bottom_pipe &&
+			else if (!odm && old_pipe->bottom_pipe && old_pipe->bottom_pipe->bottom_pipe &&
-						old_pipe->bottom_pipe->bottom_pipe->bottom_pipe->plane_state == old_pipe->plane_state)
+					old_pipe->bottom_pipe->bottom_pipe->bottom_pipe &&
+					old_pipe->bottom_pipe->bottom_pipe->bottom_pipe->plane_state == old_pipe->plane_state)
 				old_index = old_pipe->bottom_pipe->bottom_pipe->bottom_pipe->pipe_idx;
 			else
 				old_index = -1;

drivers/gpu/drm/amd/display/dc/gpio/dcn30/hw_factory_dcn30.c+12−0

 	ddc_data_regs_dcn2(4),
 	ddc_data_regs_dcn2(5),
 	ddc_data_regs_dcn2(6),
+	{
+			DDC_GPIO_VGA_REG_LIST(DATA),
+			.ddc_setup = 0,
+			.phy_aux_cntl = 0,
+			.dc_gpio_aux_ctrl_5 = 0
+	}
 };
 static const struct ddc_registers ddc_clk_regs_dcn[] = {
 	ddc_clk_regs_dcn2(4),
 	ddc_clk_regs_dcn2(5),
 	ddc_clk_regs_dcn2(6),
+	{
+			DDC_GPIO_VGA_REG_LIST(CLK),
+			.ddc_setup = 0,
+			.phy_aux_cntl = 0,
+			.dc_gpio_aux_ctrl_5 = 0
+	}
 };
 static const struct ddc_sh_mask ddc_shift[] = {

drivers/gpu/drm/amd/display/dc/gpio/gpio_base.c+2−2

@@ -63,13 +63,13 @@ enum gpio_result dal_gpio_open_ex( · 62 unmodified lines
63	enum gpio_mode mode)	63	enum gpio_mode mode)
64	{	64	{
65	if (gpio->pin) {	65	if (gpio->pin) {
66	ASSERT_CRITICAL(false);	66	BREAK_TO_DEBUGGER();
67	return GPIO_RESULT_ALREADY_OPENED;	67	return GPIO_RESULT_ALREADY_OPENED;
68	}	68	}
69		69
70	// No action if allocation failed during gpio construct	70	// No action if allocation failed during gpio construct
71	if (!gpio->hw_container.ddc) {	71	if (!gpio->hw_container.ddc) {
72	ASSERT_CRITICAL(false);	72	BREAK_TO_DEBUGGER();
73	return GPIO_RESULT_NON_SPECIFIC_ERROR;	73	return GPIO_RESULT_NON_SPECIFIC_ERROR;
74	}	74	}
75	gpio->mode = mode;	75	gpio->mode = mode;

drivers/gpu/drm/amd/display/dc/os_types.h+12−21

  * general debug capabilities
  *
  */
-#if defined(CONFIG_HAVE_KGDB) || defined(CONFIG_KGDB)
+#ifdef CONFIG_DEBUG_KERNEL_DC
-#define ASSERT_CRITICAL(expr) do {	\
+#define dc_breakpoint()		kgdb_breakpoint()
-	if (WARN_ON(!(expr))) { \
-		kgdb_breakpoint(); \
-	} \
-} while (0)
 #else
-#define ASSERT_CRITICAL(expr) do {	\
+#define dc_breakpoint()		do {} while (0)
-	if (WARN_ON(!(expr))) { \
-		; \
-	} \
-} while (0)
 #endif
-#if defined(CONFIG_DEBUG_KERNEL_DC)
+#define ASSERT_CRITICAL(expr) do {		\
-#define ASSERT(expr) ASSERT_CRITICAL(expr)
+		if (WARN_ON(!(expr)))		\
+			dc_breakpoint();	\
+	} while (0)
-#else
+#define ASSERT(expr) do {			\
-#define ASSERT(expr) WARN_ON_ONCE(!(expr))
+		if (WARN_ON_ONCE(!(expr)))	\
-#endif
+			dc_breakpoint();	\
+	} while (0)
-#if defined(CONFIG_DEBUG_KERNEL_DC) && (defined(CONFIG_HAVE_KGDB) || defined(CONFIG_KGDB))
 #define BREAK_TO_DEBUGGER() \
 	do { \
 		DRM_DEBUG_DRIVER("%s():%d\n", __func__, __LINE__); \
-		kgdb_breakpoint(); \
+		dc_breakpoint(); \
 	} while (0)
-#else
-#define BREAK_TO_DEBUGGER() DRM_DEBUG_DRIVER("%s():%d\n", __func__, __LINE__)
-#endif
 #define DC_ERR(...)  do { \
 	dm_error(__VA_ARGS__); \

drivers/gpu/drm/amd/display/include/dal_asic_id.h+4−0

 #if defined(CONFIG_DRM_AMD_DC_DCN3_0)
 #define ASICREV_IS_SIENNA_CICHLID_P(eChipRev)        ((eChipRev >= NV_SIENNA_CICHLID_P_A0))
 #endif
+#define GREEN_SARDINE_A0 0xA1
+#ifndef ASICREV_IS_GREEN_SARDINE
+#define ASICREV_IS_GREEN_SARDINE(eChipRev) ((eChipRev >= GREEN_SARDINE_A0) && (eChipRev < 0xFF))
+#endif
 /*
  * ASIC chip ID

drivers/gpu/drm/amd/include/amd_shared.h+1−0

@@ -45,6 +45,7 @@ enum amd_apu_flags { · 44 unmodified lines
45	AMD_APU_IS_RAVEN2 = 0x00000002UL,	45	AMD_APU_IS_RAVEN2 = 0x00000002UL,
46	AMD_APU_IS_PICASSO = 0x00000004UL,	46	AMD_APU_IS_PICASSO = 0x00000004UL,
47	AMD_APU_IS_RENOIR = 0x00000008UL,	47	AMD_APU_IS_RENOIR = 0x00000008UL,
		48	AMD_APU_IS_GREEN_SARDINE = 0x00000010UL,
48	};	49	};
49		50
50	/**	51	/**

drivers/gpu/drm/amd/pm/inc/hwmgr.h+1−0

@@ -229,6 +229,7 @@ struct pp_smumgr_func { · 228 unmodified lines
229	bool (is_hw_avfs_present)(struct pp_hwmgr hwmgr);	229	bool (is_hw_avfs_present)(struct pp_hwmgr hwmgr);
230	int (update_dpm_settings)(struct pp_hwmgr hwmgr, void *profile_setting);	230	int (update_dpm_settings)(struct pp_hwmgr hwmgr, void *profile_setting);
231	int (smc_table_manager)(struct pp_hwmgr hwmgr, uint8_t table, uint16_t table_id, bool rw); /rw: true for read, false for write */	231	int (smc_table_manager)(struct pp_hwmgr hwmgr, uint8_t table, uint16_t table_id, bool rw); /rw: true for read, false for write */
		232	int (stop_smc)(struct pp_hwmgr hwmgr);
232	};	233	};
233		234
234	struct pp_hwmgr_func {	235	struct pp_hwmgr_func {

drivers/gpu/drm/amd/pm/inc/smumgr.h+2−0

@@ -113,4 +113,6 @@ extern int smum_update_dpm_settings(struct pp_hwmgr hwmgr, void profile_settin · 112 unmodified lines
113		113
114	extern int smum_smc_table_manager(struct pp_hwmgr hwmgr, uint8_t table, uint16_t table_id, bool rw);	114	extern int smum_smc_table_manager(struct pp_hwmgr hwmgr, uint8_t table, uint16_t table_id, bool rw);
115		115
		116	extern int smum_stop_smc(struct pp_hwmgr *hwmgr);
		117
116	#endif	118	#endif

drivers/gpu/drm/amd/pm/powerplay/hwmgr/ci_baco.c+4−3

 	{ CMD_READMODIFYWRITE, mmBACO_CNTL, BACO_CNTL__BACO_BCLK_OFF_MASK,           BACO_CNTL__BACO_BCLK_OFF__SHIFT, 0, 0x00 },
 	{ CMD_READMODIFYWRITE, mmBACO_CNTL, BACO_CNTL__BACO_POWER_OFF_MASK,          BACO_CNTL__BACO_POWER_OFF__SHIFT, 0, 0x00 },
 	{ CMD_DELAY_MS, 0, 0, 0, 20, 0 },
-	{ CMD_WAITFOR, mmBACO_CNTL, BACO_CNTL__PWRGOOD_BF_MASK, 0, 0xffffffff, 0x20 },
+	{ CMD_WAITFOR, mmBACO_CNTL, BACO_CNTL__PWRGOOD_BF_MASK, 0, 0xffffffff, 0x200 },
 	{ CMD_READMODIFYWRITE, mmBACO_CNTL, BACO_CNTL__BACO_ISO_DIS_MASK, BACO_CNTL__BACO_ISO_DIS__SHIFT, 0, 0x01 },
-	{ CMD_WAITFOR, mmBACO_CNTL, BACO_CNTL__PWRGOOD_MASK, 0, 5, 0x1c },
+	{ CMD_WAITFOR, mmBACO_CNTL, BACO_CNTL__PWRGOOD_MASK, 0, 5, 0x1c00 },
 	{ CMD_READMODIFYWRITE, mmBACO_CNTL, BACO_CNTL__BACO_ANA_ISO_DIS_MASK, BACO_CNTL__BACO_ANA_ISO_DIS__SHIFT, 0, 0x01 },
 	{ CMD_READMODIFYWRITE, mmBACO_CNTL, BACO_CNTL__BACO_RESET_EN_MASK, BACO_CNTL__BACO_RESET_EN__SHIFT, 0, 0x00 },
-	{ CMD_WAITFOR, mmBACO_CNTL, BACO_CNTL__RCU_BIF_CONFIG_DONE_MASK, 0, 5, 0x10 },
+	{ CMD_WAITFOR, mmBACO_CNTL, BACO_CNTL__RCU_BIF_CONFIG_DONE_MASK, 0, 5, 0x100 },
 	{ CMD_READMODIFYWRITE, mmBACO_CNTL, BACO_CNTL__BACO_EN_MASK, BACO_CNTL__BACO_EN__SHIFT, 0, 0x00 },
 	{ CMD_WAITFOR, mmBACO_CNTL, BACO_CNTL__BACO_MODE_MASK, 0, 0xffffffff, 0x00 }
 };
 static const struct baco_cmd_entry clean_baco_tbl[] =
 {
 	{ CMD_WRITE, mmBIOS_SCRATCH_6, 0, 0, 0, 0 },
+	{ CMD_WRITE, mmBIOS_SCRATCH_7, 0, 0, 0, 0 },
 	{ CMD_WRITE, mmCP_PFP_UCODE_ADDR, 0, 0, 0, 0 }
 };

drivers/gpu/drm/amd/pm/powerplay/hwmgr/smu7_hwmgr.c+22−12

 	PP_ASSERT_WITH_CODE((tmp_result == 0),
 			"Failed to reset to default!", result = tmp_result);
+	tmp_result = smum_stop_smc(hwmgr);
+	PP_ASSERT_WITH_CODE((tmp_result == 0),
+			"Failed to stop smc!", result = tmp_result);
 	tmp_result = smu7_force_switch_to_arbf0(hwmgr);
 	PP_ASSERT_WITH_CODE((tmp_result == 0),
 			"Failed to force to switch arbf0!", result = tmp_result);
 	data->current_profile_setting.sclk_down_hyst = 100;
 	data->current_profile_setting.sclk_activity = SMU7_SCLK_TARGETACTIVITY_DFLT;
 	data->current_profile_setting.bupdate_mclk = 1;
-	if (adev->gmc.vram_width == 256) {
+	if (hwmgr->chip_id >= CHIP_POLARIS10) {
-		data->current_profile_setting.mclk_up_hyst = 10;
+		if (adev->gmc.vram_width == 256) {
-		data->current_profile_setting.mclk_down_hyst = 60;
+			data->current_profile_setting.mclk_up_hyst = 10;
-		data->current_profile_setting.mclk_activity = 25;
+			data->current_profile_setting.mclk_down_hyst = 60;
-	} else if (adev->gmc.vram_width == 128) {
+			data->current_profile_setting.mclk_activity = 25;
-		data->current_profile_setting.mclk_up_hyst = 5;
+		} else if (adev->gmc.vram_width == 128) {
-		data->current_profile_setting.mclk_down_hyst = 16;
+			data->current_profile_setting.mclk_up_hyst = 5;
-		data->current_profile_setting.mclk_activity = 20;
+			data->current_profile_setting.mclk_down_hyst = 16;
-	} else if (adev->gmc.vram_width == 64) {
+			data->current_profile_setting.mclk_activity = 20;
-		data->current_profile_setting.mclk_up_hyst = 3;
+		} else if (adev->gmc.vram_width == 64) {
-		data->current_profile_setting.mclk_down_hyst = 16;
+			data->current_profile_setting.mclk_up_hyst = 3;
-		data->current_profile_setting.mclk_activity = 20;
+			data->current_profile_setting.mclk_down_hyst = 16;
+			data->current_profile_setting.mclk_activity = 20;
+		}
+	} else {
+		data->current_profile_setting.mclk_up_hyst = 0;
+		data->current_profile_setting.mclk_down_hyst = 100;
+		data->current_profile_setting.mclk_activity = SMU7_MCLK_TARGETACTIVITY_DFLT;
 	}
 	hwmgr->workload_mask = 1 << hwmgr->workload_prority[PP_SMC_POWER_PROFILE_FULLSCREEN3D];
 	hwmgr->power_profile_mode = PP_SMC_POWER_PROFILE_FULLSCREEN3D;

drivers/gpu/drm/amd/pm/powerplay/smumgr/ci_smumgr.c+25−4

@@ -2726,10 +2726,7 @@ static int ci_initialize_mc_reg_table(struct pp_hwmgr *hwmgr) · 2725 unmodified lines
2726		2726
2727	static bool ci_is_dpm_running(struct pp_hwmgr *hwmgr)	2727	static bool ci_is_dpm_running(struct pp_hwmgr *hwmgr)
2728	{	2728	{
2729	return (1 == PHM_READ_INDIRECT_FIELD(hwmgr->device,	2729	return ci_is_smc_ram_running(hwmgr);
2730	CGS_IND_REG__SMC, FEATURE_STATUS,
2731	VOLTAGE_CONTROLLER_ON))
2732	? true : false;
2733	}	2730	}
2734		2731
2735	static int ci_smu_init(struct pp_hwmgr *hwmgr)	2732	static int ci_smu_init(struct pp_hwmgr *hwmgr)
@@ -2939,6 +2936,29 @@ static int ci_update_smc_table(struct pp_hwmgr *hwmgr, uint32_t type) · 203 unmodified lines
2939	return 0;	2936	return 0;
2940	}	2937	}
2941		2938
		2939	static void ci_reset_smc(struct pp_hwmgr *hwmgr)
		2940	{
		2941	PHM_WRITE_INDIRECT_FIELD(hwmgr->device, CGS_IND_REG__SMC,
		2942	SMC_SYSCON_RESET_CNTL,
		2943	rst_reg, 1);
		2944	}
		2945
		2946
		2947	static void ci_stop_smc_clock(struct pp_hwmgr *hwmgr)
		2948	{
		2949	PHM_WRITE_INDIRECT_FIELD(hwmgr->device, CGS_IND_REG__SMC,
		2950	SMC_SYSCON_CLOCK_CNTL_0,
		2951	ck_disable, 1);
		2952	}
		2953
		2954	static int ci_stop_smc(struct pp_hwmgr *hwmgr)
		2955	{
		2956	ci_reset_smc(hwmgr);
		2957	ci_stop_smc_clock(hwmgr);
		2958
		2959	return 0;
		2960	}
		2961
2942	const struct pp_smumgr_func ci_smu_funcs = {	2962	const struct pp_smumgr_func ci_smu_funcs = {
2943	.name = "ci_smu",	2963	.name = "ci_smu",
2944	.smu_init = ci_smu_init,	2964	.smu_init = ci_smu_init,
@@ -2964,4 +2984,5 @@ const struct pp_smumgr_func ci_smu_funcs = { · 19 unmodified lines
2964	.is_dpm_running = ci_is_dpm_running,	2984	.is_dpm_running = ci_is_dpm_running,
2965	.update_dpm_settings = ci_update_dpm_settings,	2985	.update_dpm_settings = ci_update_dpm_settings,
2966	.update_smc_table = ci_update_smc_table,	2986	.update_smc_table = ci_update_smc_table,
		2987	.stop_smc = ci_stop_smc,
2967	};	2988	};

drivers/gpu/drm/amd/pm/powerplay/smumgr/smumgr.c+8−0

@@ -245,3 +245,11 @@ int smum_smc_table_manager(struct pp_hwmgr hwmgr, uint8_t table, uint16_t tabl · 244 unmodified lines
245		245
246	return -EINVAL;	246	return -EINVAL;
247	}	247	}
		248
		249	int smum_stop_smc(struct pp_hwmgr *hwmgr)
		250	{
		251	if (hwmgr->smumgr_funcs->stop_smc)
		252	return hwmgr->smumgr_funcs->stop_smc(hwmgr);
		253
		254	return 0;
		255	}

drivers/gpu/drm/amd/pm/swsmu/amdgpu_smu.c+0−11

@@ -1029,17 +1029,6 @@ static int smu_smc_hw_setup(struct smu_context *smu) · 1028 unmodified lines
1029	return ret;	1029	return ret;
1030	}	1030	}
1031		1031
1032	/*
1033	* Set initialized values (get from vbios) to dpm tables context such as
1034	* gfxclk, memclk, dcefclk, and etc. And enable the DPM feature for each
1035	* type of clks.
1036	*/
1037	ret = smu_set_default_dpm_table(smu);
1038	if (ret) {
1039	dev_err(adev->dev, "Failed to setup default dpm clock tables!\n");
1040	return ret;
1041	}
1042
1043	ret = smu_notify_display_change(smu);	1032	ret = smu_notify_display_change(smu);
1044	if (ret)	1033	if (ret)
1045	return ret;	1034	return ret;

drivers/gpu/drm/amd/pm/swsmu/smu11/navi10_ppt.c+3−33

@@ -1361,14 +1361,9 @@ static int navi10_get_fan_speed_rpm(struct smu_context *smu, · 1360 unmodified lines
1361	if (!speed)	1361	if (!speed)
1362	return -EINVAL;	1362	return -EINVAL;
1363		1363
1364	switch (smu_v11_0_get_fan_control_mode(smu)) {	1364	return navi10_get_smu_metrics_data(smu,
1365	case AMD_FAN_CTRL_AUTO:	1365	METRICS_CURR_FANSPEED,
1366	return navi10_get_smu_metrics_data(smu,	1366	speed);
1367	METRICS_CURR_FANSPEED,
1368	speed);
1369	default:
1370	return smu_v11_0_get_fan_speed_rpm(smu, speed);
1371	}
1372	}	1367	}
1373		1368
1374	static int navi10_get_fan_parameters(struct smu_context *smu)	1369	static int navi10_get_fan_parameters(struct smu_context *smu)
@@ -2534,29 +2529,6 @@ static const struct i2c_algorithm navi10_i2c_algo = { · 1159 unmodified lines
2534	.functionality = navi10_i2c_func,	2529	.functionality = navi10_i2c_func,
2535	};	2530	};
2536		2531
2537	static int navi10_i2c_control_init(struct smu_context smu, struct i2c_adapter control)
2538	{
2539	struct amdgpu_device *adev = to_amdgpu_device(control);
2540	int res;
2541
2542	control->owner = THIS_MODULE;
2543	control->class = I2C_CLASS_SPD;
2544	control->dev.parent = &adev->pdev->dev;
2545	control->algo = &navi10_i2c_algo;
2546	snprintf(control->name, sizeof(control->name), "AMDGPU SMU");
2547
2548	res = i2c_add_adapter(control);
2549	if (res)
2550	DRM_ERROR("Failed to register hw i2c, err: %d\n", res);
2551
2552	return res;
2553	}
2554
2555	static void navi10_i2c_control_fini(struct smu_context smu, struct i2c_adapter control)
2556	{
2557	i2c_del_adapter(control);
2558	}
2559
2560	static ssize_t navi10_get_gpu_metrics(struct smu_context *smu,	2532	static ssize_t navi10_get_gpu_metrics(struct smu_context *smu,
2561	void **table)	2533	void **table)
2562	{	2534	{
@@ -2687,8 +2659,6 @@ static const struct pptable_funcs navi10_ppt_funcs = { · 124 unmodified lines
2687	.set_default_dpm_table = navi10_set_default_dpm_table,	2659	.set_default_dpm_table = navi10_set_default_dpm_table,
2688	.dpm_set_vcn_enable = navi10_dpm_set_vcn_enable,	2660	.dpm_set_vcn_enable = navi10_dpm_set_vcn_enable,
2689	.dpm_set_jpeg_enable = navi10_dpm_set_jpeg_enable,	2661	.dpm_set_jpeg_enable = navi10_dpm_set_jpeg_enable,
2690	.i2c_init = navi10_i2c_control_init,
2691	.i2c_fini = navi10_i2c_control_fini,
2692	.print_clk_levels = navi10_print_clk_levels,	2662	.print_clk_levels = navi10_print_clk_levels,
2693	.force_clk_levels = navi10_force_clk_levels,	2663	.force_clk_levels = navi10_force_clk_levels,
2694	.populate_umd_state_clk = navi10_populate_umd_state_clk,	2664	.populate_umd_state_clk = navi10_populate_umd_state_clk,

drivers/gpu/drm/amd/pm/swsmu/smu11/sienna_cichlid_ppt.c+3−8

 	if (!speed)
 		return -EINVAL;
-	switch (smu_v11_0_get_fan_control_mode(smu)) {
+	return sienna_cichlid_get_smu_metrics_data(smu,
-	case AMD_FAN_CTRL_AUTO:
+						METRICS_CURR_FANSPEED,
-		return sienna_cichlid_get_smu_metrics_data(smu,
+						speed);
-							   METRICS_CURR_FANSPEED,
-							   speed);
-	default:
-		return smu_v11_0_get_fan_speed_rpm(smu, speed);
-	}
 }
 static int sienna_cichlid_get_fan_parameters(struct smu_context *smu)

drivers/gpu/drm/drm_dp_helper.c+11−1

  * drm_dp_downstream_is_type() - is the downstream facing port of certain type?
  * @dpcd: DisplayPort configuration data
  * @port_cap: port capabilities
+ * @type: port type to be checked. Can be:
+ * 	  %DP_DS_PORT_TYPE_DP, %DP_DS_PORT_TYPE_VGA, %DP_DS_PORT_TYPE_DVI,
+ * 	  %DP_DS_PORT_TYPE_HDMI, %DP_DS_PORT_TYPE_NON_EDID,
+ *	  %DP_DS_PORT_TYPE_DP_DUALMODE or %DP_DS_PORT_TYPE_WIRELESS.
  *
  * Caveat: Only works with DPCD 1.1+ port caps.
  *
 /**
  * drm_dp_downstream_mode() - return a mode for downstream facing port
+ * @dev: DRM device
  * @dpcd: DisplayPort configuration data
  * @port_cap: port capabilities
  *
 /**
  * drm_dp_subconnector_type() - get DP branch device type
- *
+ * @dpcd: DisplayPort configuration data
+ * @port_cap: port capabilities
  */
 enum drm_mode_subconnector
 drm_dp_subconnector_type(const u8 dpcd[DP_RECEIVER_CAP_SIZE],
 /**
  * drm_mode_set_dp_subconnector_property - set subconnector for DP connector
+ * @connector: connector to set property on
+ * @status: connector status
+ * @dpcd: DisplayPort configuration data
+ * @port_cap: port capabilities
  *
  * Called by a driver on every detect event.
  */

drivers/gpu/drm/drm_edid.c+1−1

@@ -3741,7 +3741,7 @@ drm_add_cmdb_modes(struct drm_connector *connector, u8 svd) · 3740 unmodified lines
3741	/**	3741	/**
3742	* drm_display_mode_from_cea_vic() - return a mode for CEA VIC	3742	* drm_display_mode_from_cea_vic() - return a mode for CEA VIC
3743	* @dev: DRM device	3743	* @dev: DRM device
3744	* @vic: CEA VIC of the mode	3744	* @video_code: CEA VIC of the mode
3745	*	3745	*
3746	* Creates a new mode matching the specified CEA VIC.	3746	* Creates a new mode matching the specified CEA VIC.
3747	*	3747	*

drivers/gpu/drm/drm_gem.c+2−2

 	 */
 	drm_gem_object_get(obj);
+	vma->vm_private_data = obj;
 	if (obj->funcs && obj->funcs->mmap) {
 		ret = obj->funcs->mmap(obj, vma);
 		if (ret) {
 		vma->vm_page_prot = pgprot_decrypted(vma->vm_page_prot);
 	}
-	vma->vm_private_data = obj;
 	return 0;
 }
 EXPORT_SYMBOL(drm_gem_mmap_obj);

drivers/gpu/drm/drm_gem_shmem_helper.c+6−1

 	/* Remove the fake offset */
 	vma->vm_pgoff -= drm_vma_node_start(&obj->vma_node);
-	if (obj->import_attach)
+	if (obj->import_attach) {
+		/* Drop the reference drm_gem_mmap_obj() acquired.*/
+		drm_gem_object_put(obj);
+		vma->vm_private_data = NULL;
 		return dma_buf_mmap(obj->dma_buf, vma, 0);
+	}
 	shmem = to_drm_gem_shmem_obj(obj);

drivers/gpu/drm/drm_prime.c+1−0

@@ -794,6 +794,7 @@ static const struct dma_buf_ops drm_gem_prime_dmabuf_ops = { · 793 unmodified lines
794		794
795	/**	795	/**
796	* drm_prime_pages_to_sg - converts a page array into an sg list	796	* drm_prime_pages_to_sg - converts a page array into an sg list
		797	* @dev: DRM device
797	* @pages: pointer to the array of page pointers to convert	798	* @pages: pointer to the array of page pointers to convert
798	* @nr_pages: length of the page vector	799	* @nr_pages: length of the page vector
799	*	800	*

drivers/gpu/drm/i915/display/intel_display.c+4−0

@@ -10636,6 +10636,10 @@ skl_get_initial_plane_config(struct intel_crtc *crtc, · 10635 unmodified lines
10636	val & PLANE_CTL_FLIP_HORIZONTAL)	10636	val & PLANE_CTL_FLIP_HORIZONTAL)
10637	plane_config->rotation \|= DRM_MODE_REFLECT_X;	10637	plane_config->rotation \|= DRM_MODE_REFLECT_X;
10638		10638
		10639	/* 90/270 degree rotation would require extra work */
		10640	if (drm_rotation_90_or_270(plane_config->rotation))
		10641	goto error;
		10642
10639	base = intel_de_read(dev_priv, PLANE_SURF(pipe, plane_id)) & 0xfffff000;	10643	base = intel_de_read(dev_priv, PLANE_SURF(pipe, plane_id)) & 0xfffff000;
10640	plane_config->base = base;	10644	plane_config->base = base;
10641		10645

drivers/gpu/drm/i915/display/intel_psr.c+1−1

@@ -1754,7 +1754,7 @@ void intel_psr_atomic_check(struct drm_connector *connector, · 1753 unmodified lines
1754	return;	1754	return;
1755		1755
1756	intel_connector = to_intel_connector(connector);	1756	intel_connector = to_intel_connector(connector);
1757	dig_port = enc_to_dig_port(intel_attached_encoder(intel_connector));	1757	dig_port = enc_to_dig_port(to_intel_encoder(new_state->best_encoder));
1758	if (dev_priv->psr.dp != &dig_port->dp)	1758	if (dev_priv->psr.dp != &dig_port->dp)
1759	return;	1759	return;
1760		1760

drivers/gpu/drm/i915/gem/i915_gem_domain.c+13−15

 	if (!obj)
 		return -ENOENT;
-	/*
-	 * Already in the desired write domain? Nothing for us to do!
-	 *
-	 * We apply a little bit of cunning here to catch a broader set of
-	 * no-ops. If obj->write_domain is set, we must be in the same
-	 * obj->read_domains, and only that domain. Therefore, if that
-	 * obj->write_domain matches the request read_domains, we are
-	 * already in the same read/write domain and can skip the operation,
-	 * without having to further check the requested write_domain.
-	 */
-	if (READ_ONCE(obj->write_domain) == read_domains) {
-		err = 0;
-		goto out;
-	}
 	/*
 	 * Try to flush the object off the GPU without holding the lock.
 	 * We will repeat the flush holding the lock in the normal manner
 	if (err)
 		goto out;
+	/*
+	 * Already in the desired write domain? Nothing for us to do!
+	 *
+	 * We apply a little bit of cunning here to catch a broader set of
+	 * no-ops. If obj->write_domain is set, we must be in the same
+	 * obj->read_domains, and only that domain. Therefore, if that
+	 * obj->write_domain matches the request read_domains, we are
+	 * already in the same read/write domain and can skip the operation,
+	 * without having to further check the requested write_domain.
+	 */
+	if (READ_ONCE(obj->write_domain) == read_domains)
+		goto out_unpin;
 	err = i915_gem_object_lock_interruptible(obj, NULL);
 	if (err)
 		goto out_unpin;

drivers/gpu/drm/i915/gt/intel_engine.h+35−20

 }
 static inline u32 *
-__gen8_emit_ggtt_write_rcs(u32 *cs, u32 value, u32 gtt_offset, u32 flags0, u32 flags1)
+__gen8_emit_write_rcs(u32 *cs, u32 value, u32 offset, u32 flags0, u32 flags1)
 {
-	/* We're using qword write, offset should be aligned to 8 bytes. */
-	GEM_BUG_ON(!IS_ALIGNED(gtt_offset, 8));
-	/* w/a for post sync ops following a GPGPU operation we
-	 * need a prior CS_STALL, which is emitted by the flush
-	 * following the batch.
-	 */
 	*cs++ = GFX_OP_PIPE_CONTROL(6) | flags0;
-	*cs++ = flags1 | PIPE_CONTROL_QW_WRITE | PIPE_CONTROL_GLOBAL_GTT_IVB;
+	*cs++ = flags1 | PIPE_CONTROL_QW_WRITE;
-	*cs++ = gtt_offset;
+	*cs++ = offset;
 	*cs++ = 0;
 	*cs++ = value;
-	/* We're thrashing one dword of HWS. */
+	*cs++ = 0; /* We're thrashing one extra dword. */
-	*cs++ = 0;
 	return cs;
 }
 static inline u32*
 gen8_emit_ggtt_write_rcs(u32 *cs, u32 value, u32 gtt_offset, u32 flags)
 {
-	return __gen8_emit_ggtt_write_rcs(cs, value, gtt_offset, 0, flags);
+	/* We're using qword write, offset should be aligned to 8 bytes. */
+	GEM_BUG_ON(!IS_ALIGNED(gtt_offset, 8));
+	return __gen8_emit_write_rcs(cs,
+				     value,
+				     gtt_offset,
+				     0,
+				     flags | PIPE_CONTROL_GLOBAL_GTT_IVB);
 }
 static inline u32*
 gen12_emit_ggtt_write_rcs(u32 *cs, u32 value, u32 gtt_offset, u32 flags0, u32 flags1)
 {
-	return __gen8_emit_ggtt_write_rcs(cs, value, gtt_offset, flags0, flags1);
+	/* We're using qword write, offset should be aligned to 8 bytes. */
+	GEM_BUG_ON(!IS_ALIGNED(gtt_offset, 8));
+	return __gen8_emit_write_rcs(cs,
+				     value,
+				     gtt_offset,
+				     flags0,
+				     flags1 | PIPE_CONTROL_GLOBAL_GTT_IVB);
+}
+static inline u32 *
+__gen8_emit_flush_dw(u32 *cs, u32 value, u32 gtt_offset, u32 flags)
+{
+	*cs++ = (MI_FLUSH_DW + 1) | flags;
+	*cs++ = gtt_offset;
+	*cs++ = 0;
+	*cs++ = value;
+	return cs;
 }
 static inline u32 *
 	/* Offset should be aligned to 8 bytes for both (QW/DW) write types */
 	GEM_BUG_ON(!IS_ALIGNED(gtt_offset, 8));
-	*cs++ = (MI_FLUSH_DW + 1) | MI_FLUSH_DW_OP_STOREDW | flags;
+	return __gen8_emit_flush_dw(cs,
-	*cs++ = gtt_offset | MI_FLUSH_DW_USE_GTT;
+				    value,
-	*cs++ = 0;
+				    gtt_offset | MI_FLUSH_DW_USE_GTT,
-	*cs++ = value;
+				    flags | MI_FLUSH_DW_OP_STOREDW);
-	return cs;
 }
 static inline void __intel_engine_reset(struct intel_engine_cs *engine,

drivers/gpu/drm/i915/gt/intel_lrc.c+22−9

 	.destroy = execlists_context_destroy,
 };
+static u32 hwsp_offset(const struct i915_request *rq)
+{
+	const struct intel_timeline_cacheline *cl;
+	/* Before the request is executed, the timeline/cachline is fixed */
+	cl = rcu_dereference_protected(rq->hwsp_cacheline, 1);
+	if (cl)
+		return cl->ggtt_offset;
+	return rcu_dereference_protected(rq->timeline, 1)->hwsp_offset;
+}
 static int gen8_emit_init_breadcrumb(struct i915_request *rq)
 {
 	u32 *cs;
 	*cs++ = MI_NOOP;
 	*cs++ = MI_STORE_DWORD_IMM_GEN4 | MI_USE_GGTT;
-	*cs++ = i915_request_timeline(rq)->hwsp_offset;
+	*cs++ = hwsp_offset(rq);
 	*cs++ = 0;
 	*cs++ = rq->fence.seqno - 1;
 	return gen8_emit_wa_tail(request, cs);
 }
-static u32 *emit_xcs_breadcrumb(struct i915_request *request, u32 *cs)
+static u32 *emit_xcs_breadcrumb(struct i915_request *rq, u32 *cs)
 {
-	u32 addr = i915_request_active_timeline(request)->hwsp_offset;
+	return gen8_emit_ggtt_write(cs, rq->fence.seqno, hwsp_offset(rq), 0);
-	return gen8_emit_ggtt_write(cs, request->fence.seqno, addr, 0);
 }
 static u32 *gen8_emit_fini_breadcrumb(struct i915_request *rq, u32 *cs)
 	/* XXX flush+write+CS_STALL all in one upsets gem_concurrent_blt:kbl */
 	cs = gen8_emit_ggtt_write_rcs(cs,
 				      request->fence.seqno,
-				      i915_request_active_timeline(request)->hwsp_offset,
+				      hwsp_offset(request),
 				      PIPE_CONTROL_FLUSH_ENABLE |
 				      PIPE_CONTROL_CS_STALL);
 {
 	cs = gen8_emit_ggtt_write_rcs(cs,
 				      request->fence.seqno,
-				      i915_request_active_timeline(request)->hwsp_offset,
+				      hwsp_offset(request),
 				      PIPE_CONTROL_CS_STALL |
 				      PIPE_CONTROL_TILE_CACHE_FLUSH |
 				      PIPE_CONTROL_RENDER_TARGET_CACHE_FLUSH |
 static u32 *gen12_emit_fini_breadcrumb(struct i915_request *rq, u32 *cs)
 {
-	return gen12_emit_fini_breadcrumb_tail(rq, emit_xcs_breadcrumb(rq, cs));
+	/* XXX Stalling flush before seqno write; post-sync not */
+	cs = emit_xcs_breadcrumb(rq, __gen8_emit_flush_dw(cs, 0, 0, 0));
+	return gen12_emit_fini_breadcrumb_tail(rq, cs);
 }
 static u32 *
 {
 	cs = gen12_emit_ggtt_write_rcs(cs,
 				       request->fence.seqno,
-				       i915_request_active_timeline(request)->hwsp_offset,
+				       hwsp_offset(request),
 				       PIPE_CONTROL0_HDC_PIPELINE_FLUSH,
 				       PIPE_CONTROL_CS_STALL |
 				       PIPE_CONTROL_TILE_CACHE_FLUSH |

drivers/gpu/drm/i915/gt/intel_timeline.c+10−8

 	return cl;
 }
-static void cacheline_acquire(struct intel_timeline_cacheline *cl)
+static void cacheline_acquire(struct intel_timeline_cacheline *cl,
+			      u32 ggtt_offset)
 {
-	if (cl)
+	if (!cl)
-		i915_active_acquire(&cl->active);
+		return;
+	cl->ggtt_offset = ggtt_offset;
+	i915_active_acquire(&cl->active);
 }
 static void cacheline_release(struct intel_timeline_cacheline *cl)
 	GT_TRACE(tl->gt, "timeline:%llx using HWSP offset:%x\n",
 		 tl->fence_context, tl->hwsp_offset);
-	cacheline_acquire(tl->hwsp_cacheline);
+	cacheline_acquire(tl->hwsp_cacheline, tl->hwsp_offset);
 	if (atomic_fetch_inc(&tl->pin_count)) {
 		cacheline_release(tl->hwsp_cacheline);
 		__i915_vma_unpin(tl->hwsp_ggtt);
 	GT_TRACE(tl->gt, "timeline:%llx using HWSP offset:%x\n",
 		 tl->fence_context, tl->hwsp_offset);
-	cacheline_acquire(cl);
+	cacheline_acquire(cl, tl->hwsp_offset);
 	tl->hwsp_cacheline = cl;
 	*seqno = timeline_advance(tl);
 	if (err)
 		goto out;
-	*hwsp = i915_ggtt_offset(cl->hwsp->vma) +
+	*hwsp = cl->ggtt_offset;
-		ptr_unmask_bits(cl->vaddr, CACHELINE_BITS) * CACHELINE_BYTES;
 out:
 	i915_active_release(&cl->active);
 	return err;

drivers/gpu/drm/i915/gt/intel_timeline_types.h+2−0

@@ -94,6 +94,8 @@ struct intel_timeline_cacheline { · 93 unmodified lines
94	struct intel_timeline_hwsp *hwsp;	94	struct intel_timeline_hwsp *hwsp;
95	void *vaddr;	95	void *vaddr;
96		96
		97	u32 ggtt_offset;
		98
97	struct rcu_head rcu;	99	struct rcu_head rcu;
98	};	100	};
99		101

drivers/gpu/drm/i915/gvt/handlers.c+44−3

@@ -1489,7 +1489,8 @@ static int hws_pga_write(struct intel_vgpu *vgpu, unsigned int offset, · 1488 unmodified lines
1489	const struct intel_engine_cs *engine =	1489	const struct intel_engine_cs *engine =
1490	intel_gvt_render_mmio_to_engine(vgpu->gvt, offset);	1490	intel_gvt_render_mmio_to_engine(vgpu->gvt, offset);
1491		1491
1492	if (!intel_gvt_ggtt_validate_range(vgpu, value, I915_GTT_PAGE_SIZE)) {	1492	if (value != 0 &&
		1493	!intel_gvt_ggtt_validate_range(vgpu, value, I915_GTT_PAGE_SIZE)) {
1493	gvt_vgpu_err("write invalid HWSP address, reg:0x%x, value:0x%x\n",	1494	gvt_vgpu_err("write invalid HWSP address, reg:0x%x, value:0x%x\n",
1494	offset, value);	1495	offset, value);
1495	return -EINVAL;	1496	return -EINVAL;
@@ -1650,6 +1651,34 @@ static int edp_psr_imr_iir_write(struct intel_vgpu *vgpu, · 154 unmodified lines
1650	return 0;	1651	return 0;
1651	}	1652	}
1652		1653
		1654	/**
		1655	* FixMe:
		1656	* If guest fills non-priv batch buffer on ApolloLake/Broxton as Mesa i965 did:
		1657	* 717e7539124d (i965: Use a WC map and memcpy for the batch instead of pwrite.)
		1658	* Due to the missing flush of bb filled by VM vCPU, host GPU hangs on executing
		1659	* these MI_BATCH_BUFFER.
		1660	* Temporarily workaround this by setting SNOOP bit for PAT3 used by PPGTT
		1661	* PML4 PTE: PAT(0) PCD(1) PWT(1).
		1662	* The performance is still expected to be low, will need further improvement.
		1663	*/
		1664	static int bxt_ppat_low_write(struct intel_vgpu *vgpu, unsigned int offset,
		1665	void *p_data, unsigned int bytes)
		1666	{
		1667	u64 pat =
		1668	GEN8_PPAT(0, CHV_PPAT_SNOOP) \|
		1669	GEN8_PPAT(1, 0) \|
		1670	GEN8_PPAT(2, 0) \|
		1671	GEN8_PPAT(3, CHV_PPAT_SNOOP) \|
		1672	GEN8_PPAT(4, CHV_PPAT_SNOOP) \|
		1673	GEN8_PPAT(5, CHV_PPAT_SNOOP) \|
		1674	GEN8_PPAT(6, CHV_PPAT_SNOOP) \|
		1675	GEN8_PPAT(7, CHV_PPAT_SNOOP);
		1676
		1677	vgpu_vreg(vgpu, offset) = lower_32_bits(pat);
		1678
		1679	return 0;
		1680	}
		1681
1653	static int guc_status_read(struct intel_vgpu *vgpu,	1682	static int guc_status_read(struct intel_vgpu *vgpu,
1654	unsigned int offset, void *p_data,	1683	unsigned int offset, void *p_data,
1655	unsigned int bytes)	1684	unsigned int bytes)
@@ -2812,7 +2841,7 @@ static int init_bdw_mmio_info(struct intel_gvt *gvt) · 1156 unmodified lines
2812		2841
2813	MMIO_DH(GEN6_PCODE_MAILBOX, D_BDW_PLUS, NULL, mailbox_write);	2842	MMIO_DH(GEN6_PCODE_MAILBOX, D_BDW_PLUS, NULL, mailbox_write);
2814		2843
2815	MMIO_D(GEN8_PRIVATE_PAT_LO, D_BDW_PLUS);	2844	MMIO_D(GEN8_PRIVATE_PAT_LO, D_BDW_PLUS & ~D_BXT);
2816	MMIO_D(GEN8_PRIVATE_PAT_HI, D_BDW_PLUS);	2845	MMIO_D(GEN8_PRIVATE_PAT_HI, D_BDW_PLUS);
2817		2846
2818	MMIO_D(GAMTARBMODE, D_BDW_PLUS);	2847	MMIO_D(GAMTARBMODE, D_BDW_PLUS);
@@ -3139,7 +3168,7 @@ static int init_skl_mmio_info(struct intel_gvt *gvt) · 320 unmodified lines
3139	NULL, NULL);	3168	NULL, NULL);
3140		3169
3141	MMIO_DFH(GAMT_CHKN_BIT_REG, D_KBL \| D_CFL, F_CMD_ACCESS, NULL, NULL);	3170	MMIO_DFH(GAMT_CHKN_BIT_REG, D_KBL \| D_CFL, F_CMD_ACCESS, NULL, NULL);
3142	MMIO_D(GEN9_CTX_PREEMPT_REG, D_SKL_PLUS);	3171	MMIO_D(GEN9_CTX_PREEMPT_REG, D_SKL_PLUS & ~D_BXT);
3143		3172
3144	return 0;	3173	return 0;
3145	}	3174	}
@@ -3313,9 +3342,21 @@ static int init_bxt_mmio_info(struct intel_gvt *gvt) · 167 unmodified lines
3313	MMIO_D(GEN8_PUSHBUS_SHIFT, D_BXT);	3342	MMIO_D(GEN8_PUSHBUS_SHIFT, D_BXT);
3314	MMIO_D(GEN6_GFXPAUSE, D_BXT);	3343	MMIO_D(GEN6_GFXPAUSE, D_BXT);
3315	MMIO_DFH(GEN8_L3SQCREG1, D_BXT, F_CMD_ACCESS, NULL, NULL);	3344	MMIO_DFH(GEN8_L3SQCREG1, D_BXT, F_CMD_ACCESS, NULL, NULL);
		3345	MMIO_DFH(GEN8_L3CNTLREG, D_BXT, F_CMD_ACCESS, NULL, NULL);
		3346	MMIO_DFH(_MMIO(0x20D8), D_BXT, F_CMD_ACCESS, NULL, NULL);
		3347	MMIO_F(GEN8_RING_CS_GPR(RENDER_RING_BASE, 0), 0x40, F_CMD_ACCESS,
		3348	0, 0, D_BXT, NULL, NULL);
		3349	MMIO_F(GEN8_RING_CS_GPR(GEN6_BSD_RING_BASE, 0), 0x40, F_CMD_ACCESS,
		3350	0, 0, D_BXT, NULL, NULL);
		3351	MMIO_F(GEN8_RING_CS_GPR(BLT_RING_BASE, 0), 0x40, F_CMD_ACCESS,
		3352	0, 0, D_BXT, NULL, NULL);
		3353	MMIO_F(GEN8_RING_CS_GPR(VEBOX_RING_BASE, 0), 0x40, F_CMD_ACCESS,
		3354	0, 0, D_BXT, NULL, NULL);
3316		3355
3317	MMIO_DFH(GEN9_CTX_PREEMPT_REG, D_BXT, F_CMD_ACCESS, NULL, NULL);	3356	MMIO_DFH(GEN9_CTX_PREEMPT_REG, D_BXT, F_CMD_ACCESS, NULL, NULL);
3318		3357
		3358	MMIO_DH(GEN8_PRIVATE_PAT_LO, D_BXT, NULL, bxt_ppat_low_write);
		3359
3319	return 0;	3360	return 0;
3320	}	3361	}
3321		3362

drivers/gpu/drm/i915/gvt/scheduler.c+8−7

 	i915_context_ppgtt_root_restore(s, i915_vm_to_ppgtt(s->shadow[0]->vm));
 	for_each_engine(engine, vgpu->gvt->gt, id)
-		intel_context_unpin(s->shadow[id]);
+		intel_context_put(s->shadow[id]);
 	kmem_cache_destroy(s->workloads);
 }
 			ce->ring = __intel_context_ring_size(ring_size);
 		}
-		ret = intel_context_pin(ce);
-		intel_context_put(ce);
-		if (ret)
-			goto out_shadow_ctx;
 		s->shadow[i] = ce;
 	}
 		if (IS_ERR(s->shadow[i]))
 			break;
-		intel_context_unpin(s->shadow[i]);
 		intel_context_put(s->shadow[i]);
 	}
 	i915_vm_put(&ppgtt->vm);
 {
 	struct intel_vgpu_submission *s = &workload->vgpu->submission;
+	intel_context_unpin(s->shadow[workload->engine->id]);
 	release_shadow_batch_buffer(workload);
 	release_shadow_wa_ctx(&workload->wa_ctx);
 		return ERR_PTR(ret);
 	}
+	ret = intel_context_pin(s->shadow[engine->id]);
+	if (ret) {
+		intel_vgpu_destroy_workload(workload);
+		return ERR_PTR(ret);
+	}
 	return workload;
 }

drivers/gpu/drm/i915/i915_pci.c+1−0

@@ -389,6 +389,7 @@ static const struct intel_device_info ilk_m_info = { · 388 unmodified lines
389	GEN5_FEATURES,	389	GEN5_FEATURES,
390	PLATFORM(INTEL_IRONLAKE),	390	PLATFORM(INTEL_IRONLAKE),
391	.is_mobile = 1,	391	.is_mobile = 1,
		392	.has_rps = true,
392	.display.has_fbc = 1,	393	.display.has_fbc = 1,
393	};	394	};
394		395

drivers/gpu/drm/i915/i915_vma.c+4−2

 {
 	struct i915_vma_work *vw = container_of(work, typeof(*vw), base);
-	if (vw->pinned)
+	if (vw->pinned) {
 		__i915_gem_object_unpin_pages(vw->pinned);
+		i915_gem_object_put(vw->pinned);
+	}
 	i915_vm_free_pt_stash(vw->vm, &vw->stash);
 	i915_vm_put(vw->vm);
 		if (vma->obj) {
 			__i915_gem_object_pin_pages(vma->obj);
-			work->pinned = vma->obj;
+			work->pinned = i915_gem_object_get(vma->obj);
 		}
 	} else {
 		vma->ops->bind_vma(vma->vm, NULL, vma, cache_level, bind_flags);

drivers/gpu/drm/i915/intel_memory_region.c+1−1

@@ -87,7 +87,7 @@ __intel_memory_region_get_pages_buddy(struct intel_memory_region *mem, · 86 unmodified lines
87	min_order = ilog2(size) - ilog2(mem->mm.chunk_size);	87	min_order = ilog2(size) - ilog2(mem->mm.chunk_size);
88	}	88	}
89		89
90	if (size > BIT(mem->mm.max_order) * mem->mm.chunk_size)	90	if (size > mem->mm.size)
91	return -E2BIG;	91	return -E2BIG;
92		92
93	n_pages = size >> ilog2(mem->mm.chunk_size);	93	n_pages = size >> ilog2(mem->mm.chunk_size);

drivers/gpu/drm/i915/selftests/intel_memory_region.c+77−0

@@ -261,6 +261,82 @@ err_close_objects: · 260 unmodified lines
261	return err;	261	return err;
262	}	262	}
263		263
		264	static int igt_mock_splintered_region(void *arg)
		265	{
		266	struct intel_memory_region *mem = arg;
		267	struct drm_i915_private *i915 = mem->i915;
		268	struct drm_i915_gem_object *obj;
		269	unsigned int expected_order;
		270	LIST_HEAD(objects);
		271	u64 size;
		272	int err = 0;
		273
		274	/*
		275	* Sanity check we can still allocate everything even if the
		276	* mm.max_order != mm.size. i.e our starting address space size is not a
		277	* power-of-two.
		278	*/
		279
		280	size = (SZ_4G - 1) & PAGE_MASK;
		281	mem = mock_region_create(i915, 0, size, PAGE_SIZE, 0);
		282	if (IS_ERR(mem))
		283	return PTR_ERR(mem);
		284
		285	if (mem->mm.size != size) {
		286	pr_err("%s size mismatch(%llu != %llu)\n",
		287	__func__, mem->mm.size, size);
		288	err = -EINVAL;
		289	goto out_put;
		290	}
		291
		292	expected_order = get_order(rounddown_pow_of_two(size));
		293	if (mem->mm.max_order != expected_order) {
		294	pr_err("%s order mismatch(%u != %u)\n",
		295	__func__, mem->mm.max_order, expected_order);
		296	err = -EINVAL;
		297	goto out_put;
		298	}
		299
		300	obj = igt_object_create(mem, &objects, size, 0);
		301	if (IS_ERR(obj)) {
		302	err = PTR_ERR(obj);
		303	goto out_close;
		304	}
		305
		306	close_objects(mem, &objects);
		307
		308	/*
		309	* While we should be able allocate everything without any flag
		310	* restrictions, if we consider I915_BO_ALLOC_CONTIGUOUS then we are
		311	* actually limited to the largest power-of-two for the region size i.e
		312	* max_order, due to the inner workings of the buddy allocator. So make
		313	* sure that does indeed hold true.
		314	*/
		315
		316	obj = igt_object_create(mem, &objects, size, I915_BO_ALLOC_CONTIGUOUS);
		317	if (!IS_ERR(obj)) {
		318	pr_err("%s too large contiguous allocation was not rejected\n",
		319	__func__);
		320	err = -EINVAL;
		321	goto out_close;
		322	}
		323
		324	obj = igt_object_create(mem, &objects, rounddown_pow_of_two(size),
		325	I915_BO_ALLOC_CONTIGUOUS);
		326	if (IS_ERR(obj)) {
		327	pr_err("%s largest possible contiguous allocation failed\n",
		328	__func__);
		329	err = PTR_ERR(obj);
		330	goto out_close;
		331	}
		332
		333	out_close:
		334	close_objects(mem, &objects);
		335	out_put:
		336	intel_memory_region_put(mem);
		337	return err;
		338	}
		339
264	static int igt_gpu_write_dw(struct intel_context *ce,	340	static int igt_gpu_write_dw(struct intel_context *ce,
265	struct i915_vma *vma,	341	struct i915_vma *vma,
266	u32 dword,	342	u32 dword,
@@ -771,6 +847,7 @@ int intel_memory_region_mock_selftests(void) · 504 unmodified lines
771	static const struct i915_subtest tests[] = {	847	static const struct i915_subtest tests[] = {
772	SUBTEST(igt_mock_fill),	848	SUBTEST(igt_mock_fill),
773	SUBTEST(igt_mock_contiguous),	849	SUBTEST(igt_mock_contiguous),
		850	SUBTEST(igt_mock_splintered_region),
774	};	851	};
775	struct intel_memory_region *mem;	852	struct intel_memory_region *mem;
776	struct drm_i915_private *i915;	853	struct drm_i915_private *i915;

drivers/gpu/drm/i915/selftests/mock_region.c+1−1

@@ -24,7 +24,7 @@ mock_object_create(struct intel_memory_region *mem, · 23 unmodified lines
24	struct drm_i915_private *i915 = mem->i915;	24	struct drm_i915_private *i915 = mem->i915;
25	struct drm_i915_gem_object *obj;	25	struct drm_i915_gem_object *obj;
26		26
27	if (size > BIT(mem->mm.max_order) * mem->mm.chunk_size)	27	if (size > mem->mm.size)
28	return ERR_PTR(-E2BIG);	28	return ERR_PTR(-E2BIG);
29		29
30	obj = i915_gem_object_alloc();	30	obj = i915_gem_object_alloc();

drivers/gpu/drm/imx/dw_hdmi-imx.c+3−14

 	return 0;
 }
-static void dw_hdmi_imx_encoder_disable(struct drm_encoder *encoder)
-{
-}
 static void dw_hdmi_imx_encoder_enable(struct drm_encoder *encoder)
 {
 	struct imx_hdmi *hdmi = enc_to_imx_hdmi(encoder);
 static const struct drm_encoder_helper_funcs dw_hdmi_imx_encoder_helper_funcs = {
 	.enable     = dw_hdmi_imx_encoder_enable,
-	.disable    = dw_hdmi_imx_encoder_disable,
 	.atomic_check = dw_hdmi_imx_atomic_check,
 };
 	hdmi->dev = &pdev->dev;
 	encoder = &hdmi->encoder;
-	encoder->possible_crtcs = drm_of_find_possible_crtcs(drm, dev->of_node);
+	ret = imx_drm_encoder_parse_of(drm, encoder, dev->of_node);
-	/*
+	if (ret)
-	 * If we failed to find the CRTC(s) which this encoder is
+		return ret;
-	 * supposed to be connected to, it's because the CRTC has
-	 * not been registered yet.  Defer probing, and hope that
-	 * the required CRTC is added later.
-	 */
-	if (encoder->possible_crtcs == 0)
-		return -EPROBE_DEFER;
 	ret = dw_hdmi_imx_parse_dt(hdmi);
 	if (ret < 0)

drivers/gpu/drm/imx/imx-drm-core.c+5−5

 #include <drm/drm_fb_helper.h>
 #include <drm/drm_gem_cma_helper.h>
 #include <drm/drm_gem_framebuffer_helper.h>
+#include <drm/drm_managed.h>
 #include <drm/drm_of.h>
 #include <drm/drm_plane_helper.h>
 #include <drm/drm_probe_helper.h>
 	drm->mode_config.allow_fb_modifiers = true;
 	drm->mode_config.normalize_zpos = true;
-	drm_mode_config_init(drm);
+	ret = drmm_mode_config_init(drm);
+	if (ret)
+		return ret;
 	ret = drm_vblank_init(drm, MAX_CRTC);
 	if (ret)
 	drm_kms_helper_poll_fini(drm);
 	component_unbind_all(drm->dev, drm);
 err_kms:
-	drm_mode_config_cleanup(drm);
 	drm_dev_put(drm);
 	return ret;
 	component_unbind_all(drm->dev, drm);
-	drm_mode_config_cleanup(drm);
+	drm_dev_put(drm);
 	dev_set_drvdata(dev, NULL);
-	drm_dev_put(drm);
 }
 static const struct component_master_ops imx_drm_ops = {

drivers/gpu/drm/imx/imx-ldb.c+4−6

 	struct i2c_adapter *ddc;
 	int chno;
 	void *edid;
-	int edid_len;
 	struct drm_display_mode mode;
 	int mode_valid;
 	u32 bus_format;
 	}
 	if (!channel->ddc) {
+		int edid_len;
 		/* if no DDC available, fallback to hardcoded EDID */
 		dev_dbg(dev, "no ddc available\n");
-		edidp = of_get_property(child, "edid",
+		edidp = of_get_property(child, "edid", &edid_len);
-					&channel->edid_len);
 		if (edidp) {
-			channel->edid = kmemdup(edidp,
+			channel->edid = kmemdup(edidp, edid_len, GFP_KERNEL);
-						channel->edid_len,
-						GFP_KERNEL);
 		} else if (!channel->panel) {
 			/* fallback to display-timings node */
 			ret = of_get_drm_display_mode(child,

drivers/gpu/drm/imx/imx-tve.c+6−34

 #include <linux/platform_device.h>
 #include <linux/regmap.h>
 #include <linux/regulator/consumer.h>
-#include <linux/spinlock.h>
 #include <linux/videodev2.h>
 #include <video/imx-ipu-v3.h>
 	struct drm_connector connector;
 	struct drm_encoder encoder;
 	struct device *dev;
-	spinlock_t lock;	/* register lock */
-	bool enabled;
 	int mode;
 	int di_hsync_pin;
 	int di_vsync_pin;
 	return container_of(e, struct imx_tve, encoder);
 }
-static void tve_lock(void *__tve)
-__acquires(&tve->lock)
-{
-	struct imx_tve *tve = __tve;
-	spin_lock(&tve->lock);
-}
-static void tve_unlock(void *__tve)
-__releases(&tve->lock)
-{
-	struct imx_tve *tve = __tve;
-	spin_unlock(&tve->lock);
-}
 static void tve_enable(struct imx_tve *tve)
 {
-	if (!tve->enabled) {
+	clk_prepare_enable(tve->clk);
-		tve->enabled = true;
+	regmap_update_bits(tve->regmap, TVE_COM_CONF_REG, TVE_EN, TVE_EN);
-		clk_prepare_enable(tve->clk);
-		regmap_update_bits(tve->regmap, TVE_COM_CONF_REG,
-				   TVE_EN, TVE_EN);
-	}
 	/* clear interrupt status register */
 	regmap_write(tve->regmap, TVE_STAT_REG, 0xffffffff);
 static void tve_disable(struct imx_tve *tve)
 {
-	if (tve->enabled) {
+	regmap_update_bits(tve->regmap, TVE_COM_CONF_REG, TVE_EN, 0);
-		tve->enabled = false;
+	clk_disable_unprepare(tve->clk);
-		regmap_update_bits(tve->regmap, TVE_COM_CONF_REG, TVE_EN, 0);
-		clk_disable_unprepare(tve->clk);
-	}
 }
 static int tve_setup_tvout(struct imx_tve *tve)
 	.readable_reg = imx_tve_readable_reg,
-	.lock = tve_lock,
+	.fast_io = true,
-	.unlock = tve_unlock,
 	.max_register = 0xdc,
 };
 	[TVE_MODE_VGA] = "vga",
 };
-static const int of_get_tve_mode(struct device_node *np)
+static int of_get_tve_mode(struct device_node *np)
 {
 	const char *bm;
 	int ret, i;
 	memset(tve, 0, sizeof(*tve));
 	tve->dev = dev;
-	spin_lock_init(&tve->lock);
 	ddc_node = of_parse_phandle(np, "ddc-i2c-bus", 0);
 	if (ddc_node) {

drivers/gpu/drm/imx/parallel-display.c+3−17

 	struct drm_bridge bridge;
 	struct device *dev;
 	void *edid;
-	int edid_len;
 	u32 bus_format;
 	u32 bus_flags;
 	struct drm_display_mode mode;
 	return container_of(c, struct imx_parallel_display, connector);
 }
-static inline struct imx_parallel_display *enc_to_imxpd(struct drm_encoder *e)
-{
-	return container_of(e, struct imx_parallel_display, encoder);
-}
 static inline struct imx_parallel_display *bridge_to_imxpd(struct drm_bridge *b)
 {
 	return container_of(b, struct imx_parallel_display, bridge);
 	struct device_node *np = dev->of_node;
 	const u8 *edidp;
 	struct imx_parallel_display *imxpd;
+	int edid_len;
 	int ret;
 	u32 bus_format = 0;
 	const char *fmt;
 	if (ret && ret != -ENODEV)
 		return ret;
-	edidp = of_get_property(np, "edid", &imxpd->edid_len);
+	edidp = of_get_property(np, "edid", &edid_len);
 	if (edidp)
-		imxpd->edid = kmemdup(edidp, imxpd->edid_len, GFP_KERNEL);
+		imxpd->edid = devm_kmemdup(dev, edidp, edid_len, GFP_KERNEL);
 	ret = of_property_read_string(np, "interface-pix-fmt", &fmt);
 	if (!ret) {
 	return 0;
 }
-static void imx_pd_unbind(struct device *dev, struct device *master,
-	void *data)
-{
-	struct imx_parallel_display *imxpd = dev_get_drvdata(dev);
-	kfree(imxpd->edid);
-}
 static const struct component_ops imx_pd_ops = {
 	.bind	= imx_pd_bind,
-	.unbind	= imx_pd_unbind,
 };
 static int imx_pd_probe(struct platform_device *pdev)

drivers/gpu/drm/nouveau/dispnv50/core.h+2−0

@@ -44,6 +44,7 @@ int core507d_new_(const struct nv50_core_func , struct nouveau_drm , s32, · 43 unmodified lines
44	struct nv50_core **);	44	struct nv50_core **);

14 more lines aren’t shown here.

drivers/gpu/drm/nouveau/dispnv50/core507d.c+39−2

This diff is large: its 58 lines aren’t shown here.

drivers/gpu/drm/nouveau/dispnv50/core907d.c+35−1

This diff is large: its 47 lines aren’t shown here.

drivers/gpu/drm/nouveau/dispnv50/core917d.c+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/gpu/drm/nouveau/include/nvhw/class/cl507d.h+4−1

This diff is large: its 12 lines aren’t shown here.

drivers/gpu/drm/nouveau/include/nvhw/class/cl907d.h+4−0

This diff is large: its 11 lines aren’t shown here.

drivers/gpu/drm/nouveau/nouveau_connector.c+10−26

This diff is large: its 57 lines aren’t shown here.

drivers/gpu/drm/nouveau/nouveau_dp.c+19−12

This diff is large: its 43 lines aren’t shown here.

drivers/gpu/drm/nouveau/nouveau_gem.c+2−1

This diff is large: its 10 lines aren’t shown here.

drivers/gpu/drm/nouveau/nouveau_svm.c+3−11

This diff is large: its 45 lines aren’t shown here.

drivers/gpu/drm/nouveau/nvkm/engine/device/base.c+26−13

This diff is large: its 59 lines aren’t shown here.

drivers/gpu/drm/panel/panel-mantix-mlaf057we51.c+17−8

This diff is large: its 67 lines aren’t shown here.

drivers/gpu/drm/panfrost/panfrost_drv.c+3−2

This diff is large: its 20 lines aren’t shown here.

drivers/gpu/drm/panfrost/panfrost_gem.c+1−3

This diff is large: its 16 lines aren’t shown here.

drivers/gpu/drm/panfrost/panfrost_gem.h+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/gpu/drm/panfrost/panfrost_gem_shrinker.c+11−3

This diff is large: its 30 lines aren’t shown here.

drivers/gpu/drm/sun4i/sun4i_frontend.c+10−26

This diff is large: its 67 lines aren’t shown here.

drivers/gpu/drm/sun4i/sun4i_frontend.h+1−5

This diff is large: its 13 lines aren’t shown here.

drivers/gpu/drm/v3d/v3d_gem.c+0−1

This diff is large: its 8 lines aren’t shown here.

drivers/gpu/drm/vc4/vc4_bo.c+5−4

This diff is large: its 39 lines aren’t shown here.

drivers/gpu/drm/vc4/vc4_drv.c+14−26

This diff is large: its 82 lines aren’t shown here.

drivers/gpu/drm/vc4/vc4_drv.h+10−11

This diff is large: its 98 lines aren’t shown here.

drivers/gpu/drm/vc4/vc4_gem.c+10−9

This diff is large: its 60 lines aren’t shown here.

drivers/gpu/drm/vc4/vc4_hdmi.c+4−2

This diff is large: its 37 lines aren’t shown here.

drivers/gpu/drm/vc4/vc4_hvs.c+2−2

This diff is large: its 18 lines aren’t shown here.

drivers/gpu/drm/vc4/vc4_kms.c+58−22

This diff is large: its 116 lines aren’t shown here.

drivers/gpu/drm/vc4/vc4_v3d.c+6−6

This diff is large: its 42 lines aren’t shown here.

drivers/gpu/ipu-v3/ipu-common.c+0−67

This diff is large: its 74 lines aren’t shown here.

drivers/hv/hv_balloon.c+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/hwtracing/coresight/coresight-core.c+1−0

This diff is large: its 8 lines aren’t shown here.

drivers/hwtracing/coresight/coresight-cti-sysfs.c+7−0

This diff is large: its 14 lines aren’t shown here.

drivers/hwtracing/coresight/coresight-etm-perf.c+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/idle/intel_idle.c+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/infiniband/hw/vmw_pvrdma/pvrdma_verbs.h+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/infiniband/sw/rdmavt/vt.c+5−2

This diff is large: its 21 lines aren’t shown here.

drivers/infiniband/sw/rxe/rxe_verbs.c+5−1

This diff is large: its 20 lines aren’t shown here.

drivers/infiniband/sw/siw/siw_main.c+5−2

This diff is large: its 21 lines aren’t shown here.

drivers/infiniband/ulp/srpt/ib_srpt.c+8−5

This diff is large: its 51 lines aren’t shown here.

drivers/infiniband/ulp/srpt/ib_srpt.h+1−0

This diff is large: its 8 lines aren’t shown here.

drivers/interconnect/core.c+3−0

This diff is large: its 10 lines aren’t shown here.

drivers/interconnect/qcom/icc-rpmh.c+7−0

This diff is large: its 21 lines aren’t shown here.

drivers/interconnect/qcom/sc7180.c+3−3

This diff is large: its 20 lines aren’t shown here.

drivers/interconnect/qcom/sdm845.c+4−4

This diff is large: its 29 lines aren’t shown here.

drivers/interconnect/qcom/sm8150.c+4−3

This diff is large: its 28 lines aren’t shown here.

drivers/interconnect/qcom/sm8250.c+4−3

This diff is large: its 28 lines aren’t shown here.

drivers/iommu/amd/amd_iommu_types.h+5−1

This diff is large: its 13 lines aren’t shown here.

drivers/iommu/intel/iommu.c+3−0

This diff is large: its 10 lines aren’t shown here.

drivers/iommu/intel/svm.c+7−1

This diff is large: its 36 lines aren’t shown here.

drivers/iommu/iommu.c+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/message/fusion/mptscsih.c+8−5

This diff is large: its 32 lines aren’t shown here.

drivers/misc/Kconfig+0−1

This diff is large: its 8 lines aren’t shown here.

drivers/misc/Makefile+0−1

This diff is large: its 8 lines aren’t shown here.

drivers/misc/mei/hw.h+3−3

This diff is large: its 27 lines aren’t shown here.

drivers/misc/mic/Kconfig+0−141

This diff is large: its 142 lines aren’t shown here.

drivers/misc/mic/Makefile+0−12

This diff is large: its 13 lines aren’t shown here.

drivers/misc/mic/bus/Makefile+0−9

This diff is large: its 10 lines aren’t shown here.

drivers/misc/mic/bus/cosm_bus.c+0−130

This diff is large: its 131 lines aren’t shown here.

drivers/misc/mic/bus/cosm_bus.h+0−125

This diff is large: its 126 lines aren’t shown here.

drivers/misc/mic/bus/mic_bus.c+0−194

This diff is large: its 195 lines aren’t shown here.

drivers/misc/mic/bus/scif_bus.c+0−201

This diff is large: its 202 lines aren’t shown here.

drivers/misc/mic/bus/scif_bus.h+0−125

This diff is large: its 126 lines aren’t shown here.

drivers/misc/mic/bus/vop_bus.c+0−194

This diff is large: its 195 lines aren’t shown here.

drivers/misc/mic/bus/vop_bus.h+0−129

This diff is large: its 130 lines aren’t shown here.

drivers/misc/mic/card/Makefile+0−11

This diff is large: its 12 lines aren’t shown here.

drivers/misc/mic/card/mic_debugfs.c+0−85

This diff is large: its 86 lines aren’t shown here.

drivers/misc/mic/card/mic_device.c+0−417

This diff is large: its 418 lines aren’t shown here.

drivers/misc/mic/card/mic_device.h+0−137

This diff is large: its 138 lines aren’t shown here.

drivers/misc/mic/card/mic_x100.c+0−347

This diff is large: its 348 lines aren’t shown here.

drivers/misc/mic/card/mic_x100.h+0−37

This diff is large: its 38 lines aren’t shown here.

drivers/misc/mic/common/mic_dev.h+0−55

This diff is large: its 56 lines aren’t shown here.

drivers/misc/mic/cosm/Makefile+0−11

This diff is large: its 12 lines aren’t shown here.

drivers/misc/mic/cosm/cosm_debugfs.c+0−116

This diff is large: its 117 lines aren’t shown here.

drivers/misc/mic/cosm/cosm_main.c+0−382

This diff is large: its 383 lines aren’t shown here.

drivers/misc/mic/cosm/cosm_main.h+0−61

This diff is large: its 62 lines aren’t shown here.

drivers/misc/mic/cosm/cosm_scif_server.c+0−399

This diff is large: its 400 lines aren’t shown here.

drivers/misc/mic/cosm/cosm_sysfs.c+0−449

This diff is large: its 450 lines aren’t shown here.

drivers/misc/mic/cosm_client/Makefile+0−8

This diff is large: its 9 lines aren’t shown here.

drivers/misc/mic/cosm_client/cosm_scif_client.c+0−269

This diff is large: its 270 lines aren’t shown here.

drivers/misc/mic/host/Makefile+0−12

This diff is large: its 13 lines aren’t shown here.

drivers/misc/mic/host/mic_boot.c+0−588

This diff is large: its 589 lines aren’t shown here.

drivers/misc/mic/host/mic_debugfs.c+0−149

This diff is large: its 150 lines aren’t shown here.

drivers/misc/mic/host/mic_device.h+0−157

This diff is large: its 158 lines aren’t shown here.

drivers/misc/mic/host/mic_intr.c+0−635

This diff is large: its 636 lines aren’t shown here.

drivers/misc/mic/host/mic_intr.h+0−137

This diff is large: its 138 lines aren’t shown here.

drivers/misc/mic/host/mic_main.c+0−335

This diff is large: its 336 lines aren’t shown here.

drivers/misc/mic/host/mic_smpt.c+0−427

This diff is large: its 428 lines aren’t shown here.

drivers/misc/mic/host/mic_smpt.h+0−87

This diff is large: its 88 lines aren’t shown here.

drivers/misc/mic/host/mic_x100.c+0−585

This diff is large: its 586 lines aren’t shown here.

drivers/misc/mic/host/mic_x100.h+0−77

This diff is large: its 78 lines aren’t shown here.

drivers/misc/mic/scif/Makefile+0−21

This diff is large: its 22 lines aren’t shown here.

drivers/misc/mic/scif/scif_api.c+0−1485

This diff is large: its 1486 lines aren’t shown here.

drivers/misc/mic/scif/scif_debugfs.c+0−116

This diff is large: its 117 lines aren’t shown here.

drivers/misc/mic/scif/scif_dma.c+0−1940

This diff is large: its 1941 lines aren’t shown here.

drivers/misc/mic/scif/scif_epd.c+0−357

This diff is large: its 358 lines aren’t shown here.

drivers/misc/mic/scif/scif_epd.h+0−200

This diff is large: its 201 lines aren’t shown here.

drivers/misc/mic/scif/scif_fd.c+0−462

This diff is large: its 463 lines aren’t shown here.

drivers/misc/mic/scif/scif_fence.c+0−783

This diff is large: its 784 lines aren’t shown here.

drivers/misc/mic/scif/scif_main.c+0−351

This diff is large: its 352 lines aren’t shown here.

drivers/misc/mic/scif/scif_main.h+0−274

This diff is large: its 275 lines aren’t shown here.

drivers/misc/mic/scif/scif_map.h+0−127

This diff is large: its 128 lines aren’t shown here.

drivers/misc/mic/scif/scif_mmap.c+0−690

This diff is large: its 691 lines aren’t shown here.

drivers/misc/mic/scif/scif_nm.c+0−229

This diff is large: its 230 lines aren’t shown here.

drivers/misc/mic/scif/scif_nodeqp.c+0−1349

This diff is large: its 1350 lines aren’t shown here.

drivers/misc/mic/scif/scif_nodeqp.h+0−221

This diff is large: its 222 lines aren’t shown here.

drivers/misc/mic/scif/scif_peer_bus.c+0−175

This diff is large: its 176 lines aren’t shown here.

drivers/misc/mic/scif/scif_peer_bus.h+0−23

This diff is large: its 24 lines aren’t shown here.

drivers/misc/mic/scif/scif_ports.c+0−116

This diff is large: its 117 lines aren’t shown here.

drivers/misc/mic/scif/scif_rb.c+0−240

This diff is large: its 241 lines aren’t shown here.

drivers/misc/mic/scif/scif_rb.h+0−100

This diff is large: its 101 lines aren’t shown here.

drivers/misc/mic/scif/scif_rma.c+0−1760

This diff is large: its 1761 lines aren’t shown here.

drivers/misc/mic/scif/scif_rma.h+0−477

This diff is large: its 478 lines aren’t shown here.

drivers/misc/mic/scif/scif_rma_list.c+0−282

This diff is large: its 283 lines aren’t shown here.

drivers/misc/mic/scif/scif_rma_list.h+0−48

This diff is large: its 49 lines aren’t shown here.

drivers/misc/mic/vop/Makefile+0−10

This diff is large: its 11 lines aren’t shown here.

drivers/misc/mic/vop/vop_debugfs.c+0−184

This diff is large: its 185 lines aren’t shown here.

drivers/misc/mic/vop/vop_main.c+0−784

This diff is large: its 785 lines aren’t shown here.

drivers/misc/mic/vop/vop_main.h+0−158

This diff is large: its 159 lines aren’t shown here.

drivers/misc/mic/vop/vop_vringh.c+0−1166

This diff is large: its 1167 lines aren’t shown here.

drivers/mmc/host/sdhci-esdhc.h+2−0

This diff is large: its 16 lines aren’t shown here.

drivers/mmc/host/sdhci-of-esdhc.c+28−0

This diff is large: its 56 lines aren’t shown here.

drivers/mmc/host/sdhci.c+4−2

This diff is large: its 14 lines aren’t shown here.

drivers/mtd/nand/raw/fsl_ifc_nand.c+24−19

This diff is large: its 57 lines aren’t shown here.

drivers/mtd/nand/raw/mxc_nand.c+5−12

This diff is large: its 32 lines aren’t shown here.

drivers/mtd/nand/raw/stm32_fmc2_nand.c+8−7

This diff is large: its 36 lines aren’t shown here.

drivers/mtd/spi-nor/core.c+7−6

This diff is large: its 33 lines aren’t shown here.

drivers/net/can/dev.c+11−3

This diff is large: its 29 lines aren’t shown here.

drivers/net/can/flexcan.c+7−5

This diff is large: its 42 lines aren’t shown here.

drivers/net/can/peak_canfd/peak_canfd.c+8−3

This diff is large: its 25 lines aren’t shown here.

drivers/net/can/rx-offload.c+2−2

This diff is large: its 18 lines aren’t shown here.

drivers/net/can/spi/mcp251xfd/mcp251xfd-core.c+11−11

This diff is large: its 45 lines aren’t shown here.

drivers/net/can/spi/mcp251xfd/mcp251xfd-regmap.c+9−9

This diff is large: its 35 lines aren’t shown here.

drivers/net/can/ti_hecc.c+5−3

This diff is large: its 29 lines aren’t shown here.

drivers/net/can/usb/peak_usb/pcan_usb_core.c+46−5

This diff is large: its 61 lines aren’t shown here.

drivers/net/can/usb/peak_usb/pcan_usb_fd.c+37−11

This diff is large: its 95 lines aren’t shown here.

drivers/net/can/xilinx_can.c+3−3

This diff is large: its 34 lines aren’t shown here.

drivers/net/dsa/qca8k.c+2−2

This diff is large: its 11 lines aren’t shown here.

drivers/net/ethernet/cadence/macb_main.c+2−1

This diff is large: its 10 lines aren’t shown here.

drivers/net/ethernet/chelsio/inline_crypto/chtls/chtls_cm.c+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/net/ethernet/chelsio/inline_crypto/chtls/chtls_hw.c+3−0

This diff is large: its 10 lines aren’t shown here.

drivers/net/ethernet/freescale/dpaa/dpaa_eth.c+18−10

This diff is large: its 59 lines aren’t shown here.

drivers/net/ethernet/freescale/enetc/enetc_qos.c+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/net/ethernet/freescale/fec.h+6−0

This diff is large: its 13 lines aren’t shown here.

drivers/net/ethernet/freescale/fec_main.c+16−13

This diff is large: its 63 lines aren’t shown here.

drivers/net/ethernet/freescale/gianfar.c+3−11

This diff is large: its 32 lines aren’t shown here.

drivers/net/ethernet/google/gve/gve_adminq.h+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/net/ethernet/google/gve/gve_main.c+2−3

This diff is large: its 12 lines aren’t shown here.

drivers/net/ethernet/ibm/ibmvnic.c+32−4

This diff is large: its 83 lines aren’t shown here.

drivers/net/ethernet/pensando/ionic/ionic_ethtool.c+5−0

This diff is large: its 12 lines aren’t shown here.

drivers/net/ethernet/realtek/r8169_main.c+11−3

This diff is large: its 29 lines aren’t shown here.

drivers/net/ethernet/stmicro/stmmac/dwmac-intel.c+7−7

This diff is large: its 28 lines aren’t shown here.

drivers/net/ethernet/stmicro/stmmac/stmmac_main.c+1−0

This diff is large: its 8 lines aren’t shown here.

drivers/net/ethernet/ti/cpsw_ethtool.c+0−1

This diff is large: its 8 lines aren’t shown here.

drivers/net/ethernet/ti/cpsw_priv.c+1−4

This diff is large: its 15 lines aren’t shown here.

drivers/net/phy/sfp.c+2−1

This diff is large: its 10 lines aren’t shown here.

drivers/net/usb/qmi_wwan.c+1−0

This diff is large: its 8 lines aren’t shown here.

drivers/nvme/host/core.c+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/nvme/host/fc.c+109−161

This diff is large: its 394 lines aren’t shown here.

drivers/nvme/host/rdma.c+8−0

This diff is large: its 15 lines aren’t shown here.

drivers/nvme/target/core.c+2−2

This diff is large: its 18 lines aren’t shown here.

drivers/nvme/target/trace.h+7−14

This diff is large: its 43 lines aren’t shown here.

drivers/of/device.c+3−3

This diff is large: its 22 lines aren’t shown here.

drivers/opp/core.c+5−4

This diff is large: its 31 lines aren’t shown here.

drivers/opp/of.c+2−0

This diff is large: its 9 lines aren’t shown here.

drivers/pci/controller/dwc/pcie-designware-host.c+6−2

This diff is large: its 15 lines aren’t shown here.

drivers/pci/controller/pci-mvebu.c+10−13

This diff is large: its 53 lines aren’t shown here.

drivers/pci/pci.c+7−2

This diff is large: its 16 lines aren’t shown here.

drivers/pnp/core.c+2−2

This diff is large: its 18 lines aren’t shown here.

drivers/powercap/intel_rapl_common.c+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/regulator/core.c+2−0

This diff is large: its 9 lines aren’t shown here.

drivers/s390/crypto/ap_bus.c+12−2

This diff is large: its 49 lines aren’t shown here.

drivers/s390/crypto/pkey_api.c+16−14

This diff is large: its 69 lines aren’t shown here.

drivers/s390/crypto/zcrypt_card.c+8−5

This diff is large: its 27 lines aren’t shown here.

drivers/s390/crypto/zcrypt_queue.c+1−5

This diff is large: its 30 lines aren’t shown here.

drivers/scsi/hisi_sas/hisi_sas_main.c+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/scsi/ibmvscsi/ibmvscsi.c+26−10

This diff is large: its 106 lines aren’t shown here.

drivers/scsi/qla2xxx/qla_nvme.c+4−2

This diff is large: its 15 lines aren’t shown here.

drivers/scsi/scsi_scan.c+4−3

This diff is large: its 35 lines aren’t shown here.

drivers/soc/ti/ti_sci_pm_domains.c+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/spi/spi-bcm2835.c+1−14

This diff is large: its 31 lines aren’t shown here.

drivers/spi/spi-fsl-dspi.c+4−6

This diff is large: its 34 lines aren’t shown here.

drivers/spi/spi-imx.c+15−8

This diff is large: its 40 lines aren’t shown here.

drivers/staging/comedi/drivers/cb_pcidas.c+1−0

This diff is large: its 8 lines aren’t shown here.

drivers/staging/fieldbus/anybuss/arcx-anybus.c+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/staging/octeon/ethernet-mdio.c+0−6

This diff is large: its 13 lines aren’t shown here.

drivers/staging/octeon/ethernet-rx.c+19−15

This diff is large: its 65 lines aren’t shown here.

drivers/staging/octeon/ethernet.c+9−0

This diff is large: its 23 lines aren’t shown here.

drivers/staging/vc04_services/vchiq-mmal/mmal-vchiq.c+15−4

This diff is large: its 62 lines aren’t shown here.

drivers/staging/wfx/Documentation/devicetree/bindings/net/wireless/silabs,wfx.yaml+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/staging/wfx/bh.c+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/staging/wfx/data_tx.c+3−3

This diff is large: its 17 lines aren’t shown here.

drivers/target/target_core_user.c+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/tee/tee_core.c+2−1

This diff is large: its 10 lines aren’t shown here.

drivers/tty/serial/21285.c+6−6

This diff is large: its 32 lines aren’t shown here.

drivers/tty/serial/fsl_lpuart.c+7−6

This diff is large: its 29 lines aren’t shown here.

drivers/tty/vt/keyboard.c+19−20

This diff is large: its 66 lines aren’t shown here.

drivers/tty/vt/vt_ioctl.c+24−23

This diff is large: its 165 lines aren’t shown here.

drivers/usb/cdns3/ep0.c+35−30

This diff is large: its 123 lines aren’t shown here.

drivers/usb/cdns3/gadget.c+64−51

This diff is large: its 249 lines aren’t shown here.

drivers/usb/cdns3/gadget.h+3−2

This diff is large: its 26 lines aren’t shown here.

drivers/usb/class/cdc-acm.c+5−7

This diff is large: its 66 lines aren’t shown here.

drivers/usb/class/cdc-acm.h+1−2

This diff is large: its 10 lines aren’t shown here.

drivers/usb/core/driver.c+21−9

This diff is large: its 55 lines aren’t shown here.

drivers/usb/core/generic.c+1−3

This diff is large: its 11 lines aren’t shown here.

drivers/usb/core/usb.h+2−0

This diff is large: its 9 lines aren’t shown here.

drivers/usb/dwc3/core.c+1−1

This diff is large: its 7 lines aren’t shown here.

drivers/usb/dwc3/core.h+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/usb/gadget/composite.c+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/usb/host/ehci-tegra.c+2−2

This diff is large: its 11 lines aren’t shown here.

drivers/usb/host/fsl-mph-dr-of.c+6−3

This diff is large: its 17 lines aren’t shown here.

drivers/usb/host/xhci-mem.c+2−2

This diff is large: its 11 lines aren’t shown here.

drivers/usb/host/xhci-pci.c+17−0

This diff is large: its 45 lines aren’t shown here.

drivers/usb/host/xhci.c+4−1

This diff is large: its 16 lines aren’t shown here.

drivers/usb/host/xhci.h+1−0

This diff is large: its 8 lines aren’t shown here.

drivers/usb/misc/apple-mfi-fastcharge.c+12−5

This diff is large: its 37 lines aren’t shown here.

drivers/usb/typec/mux.c+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/usb/typec/stusb160x.c+11−13

This diff is large: its 55 lines aren’t shown here.

drivers/usb/typec/tcpm/tcpm.c+3−3

This diff is large: its 20 lines aren’t shown here.

drivers/vdpa/mlx5/core/mr.c+2−3

This diff is large: its 19 lines aren’t shown here.

drivers/vdpa/vdpa_sim/vdpa_sim.c+30−3

This diff is large: its 82 lines aren’t shown here.

drivers/vfio/fsl-mc/vfio_fsl_mc.c+7−3

This diff is large: its 31 lines aren’t shown here.

drivers/vfio/fsl-mc/vfio_fsl_mc_intr.c+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/vfio/pci/vfio_pci.c+1−1

This diff is large: its 9 lines aren’t shown here.

drivers/vfio/pci/vfio_pci_rdwr.c+35−8

This diff is large: its 78 lines aren’t shown here.

drivers/vfio/platform/vfio_platform_common.c+1−2

This diff is large: its 17 lines aren’t shown here.

drivers/vfio/vfio_iommu_type1.c+5−12

This diff is large: its 31 lines aren’t shown here.

drivers/vhost/vdpa.c+97−76

This diff is large: its 260 lines aren’t shown here.

fs/afs/xattr.c+1−6

This diff is large: its 21 lines aren’t shown here.

fs/afs/yfsclient.c+1−0

This diff is large: its 8 lines aren’t shown here.

fs/binfmt_elf.c+1−1

This diff is large: its 9 lines aren’t shown here.

fs/btrfs/backref.c+12−1

This diff is large: its 20 lines aren’t shown here.

fs/btrfs/block-group.c+1−0

This diff is large: its 8 lines aren’t shown here.

fs/btrfs/ctree.h+2−0

This diff is large: its 9 lines aren’t shown here.

fs/btrfs/dev-replace.c+5−0

This diff is large: its 26 lines aren’t shown here.

fs/btrfs/disk-io.c+99−40

This diff is large: its 194 lines aren’t shown here.

fs/btrfs/disk-io.h+3−0

This diff is large: its 10 lines aren’t shown here.

fs/btrfs/extent-tree.c+1−1

This diff is large: its 9 lines aren’t shown here.

fs/btrfs/file.c+2−1

This diff is large: its 10 lines aren’t shown here.

fs/btrfs/inode.c+7−1

This diff is large: its 18 lines aren’t shown here.

fs/btrfs/qgroup.c+18−0

This diff is large: its 32 lines aren’t shown here.

fs/btrfs/reada.c+47−0

This diff is large: its 65 lines aren’t shown here.

fs/btrfs/tree-checker.c+18−0

This diff is large: its 37 lines aren’t shown here.

fs/btrfs/volumes.c+4−1

This diff is large: its 26 lines aren’t shown here.

fs/btrfs/volumes.h+6−6

This diff is large: its 44 lines aren’t shown here.

fs/debugfs/file.c+7−8

This diff is large: its 32 lines aren’t shown here.

fs/gfs2/glock.c+2−1

This diff is large: its 10 lines aren’t shown here.

fs/gfs2/glops.c+45−11

This diff is large: its 92 lines aren’t shown here.

fs/gfs2/glops.h+1−0

This diff is large: its 8 lines aren’t shown here.

fs/gfs2/inode.c+2−1

This diff is large: its 10 lines aren’t shown here.

fs/gfs2/lops.c+5−26

This diff is large: its 69 lines aren’t shown here.

fs/gfs2/lops.h+0−2

This diff is large: its 9 lines aren’t shown here.

fs/gfs2/ops_fstype.c+9−5

This diff is large: its 42 lines aren’t shown here.

fs/gfs2/recovery.c+1−1

This diff is large: its 9 lines aren’t shown here.

fs/gfs2/rgrp.c+4−1

This diff is large: its 21 lines aren’t shown here.

fs/gfs2/super.c+1−0

This diff is large: its 8 lines aren’t shown here.

fs/hfs/btree.h+1−1

This diff is large: its 9 lines aren’t shown here.

fs/hfsplus/hfsplus_fs.h+1−1

This diff is large: its 9 lines aren’t shown here.

fs/io_uring.c+38−70

This diff is large: its 178 lines aren’t shown here.

fs/isofs/rock.h+4−4

This diff is large: its 36 lines aren’t shown here.

fs/proc/base.c+2−0

This diff is large: its 9 lines aren’t shown here.

fs/select.c+2−2

This diff is large: its 18 lines aren’t shown here.

include/asm-generic/uaccess.h+4−2

This diff is large: its 20 lines aren’t shown here.

include/drm/drm_dp_helper.h+1−1

This diff is large: its 9 lines aren’t shown here.

include/drm/drm_edid.h+0−7

This diff is large: its 14 lines aren’t shown here.

include/drm/drm_print.h+17−3

This diff is large: its 52 lines aren’t shown here.

include/kunit/test.h+8−8

This diff is large: its 49 lines aren’t shown here.

include/linux/arm-smccc.h+2−0

This diff is large: its 9 lines aren’t shown here.

include/linux/blk-mq.h+2−0

This diff is large: its 9 lines aren’t shown here.

include/linux/can/skb.h+8−12

This diff is large: its 30 lines aren’t shown here.

include/linux/cpufreq.h+10−1

This diff is large: its 28 lines aren’t shown here.

include/linux/debugfs.h+8−10

This diff is large: its 33 lines aren’t shown here.

include/linux/dma/ti-cppi5.h+2−2

This diff is large: its 18 lines aren’t shown here.

include/linux/fs.h+1−1

This diff is large: its 9 lines aren’t shown here.

include/linux/mailbox/zynqmp-ipi-message.h+1−1

This diff is large: its 9 lines aren’t shown here.

include/linux/mic_bus.h+0−100

This diff is large: its 101 lines aren’t shown here.

include/linux/mlx5/mlx5_ifc.h+2−2

This diff is large: its 18 lines aren’t shown here.

include/linux/mm.h+9−0

This diff is large: its 16 lines aren’t shown here.

include/linux/module.h+1−1

This diff is large: its 9 lines aren’t shown here.

include/linux/netfilter/nfnetlink.h+8−1

This diff is large: its 23 lines aren’t shown here.

include/linux/netfilter_ipv4.h+1−1

This diff is large: its 9 lines aren’t shown here.

include/linux/netfilter_ipv6.h+5−5

This diff is large: its 33 lines aren’t shown here.

include/linux/pagemap.h+4−4

This diff is large: its 24 lines aren’t shown here.

include/linux/pgtable.h+0−4

This diff is large: its 11 lines aren’t shown here.

include/linux/phy.h+5−35

This diff is large: its 76 lines aren’t shown here.

include/linux/platform_data/cros_ec_commands.h+7−7

This diff is large: its 60 lines aren’t shown here.

include/linux/platform_data/cros_ec_proto.h+1−1

This diff is large: its 9 lines aren’t shown here.

include/linux/pm_runtime.h+2−4

This diff is large: its 26 lines aren’t shown here.

include/linux/refcount.h+65−65

This diff is large: its 220 lines aren’t shown here.

include/linux/scif.h+0−1339

This diff is large: its 1340 lines aren’t shown here.

include/linux/time64.h+4−0

This diff is large: its 11 lines aren’t shown here.

include/linux/usb/composite.h+1−1

This diff is large: its 9 lines aren’t shown here.

include/linux/vdpa.h+15−0

This diff is large: its 36 lines aren’t shown here.

include/net/cfg80211.h+5−4

This diff is large: its 37 lines aren’t shown here.

include/net/mac80211.h+4−3

This diff is large: its 28 lines aren’t shown here.

include/sound/control.h+1−1

This diff is large: its 9 lines aren’t shown here.

include/sound/core.h+2−1

This diff is large: its 10 lines aren’t shown here.

include/sound/pcm.h+2−2

This diff is large: its 11 lines aren’t shown here.

include/uapi/linux/icmpv6.h+1−0

This diff is large: its 8 lines aren’t shown here.

include/uapi/linux/mic_common.h+0−235

This diff is large: its 236 lines aren’t shown here.

include/uapi/linux/mic_ioctl.h+0−77

This diff is large: its 78 lines aren’t shown here.

include/uapi/linux/vhost.h+4−0

This diff is large: its 9 lines aren’t shown here.

include/uapi/linux/vhost_types.h+9−0

This diff is large: its 16 lines aren’t shown here.

include/uapi/sound/compress_offload.h+1−1

This diff is large: its 9 lines aren’t shown here.

include/video/imx-ipu-v3.h+0−3

This diff is large: its 10 lines aren’t shown here.

kernel/futex.c+3−1

This diff is large: its 12 lines aren’t shown here.

kernel/hung_task.c+1−2

This diff is large: its 10 lines aren’t shown here.

kernel/kprobes.c+21−4

This diff is large: its 53 lines aren’t shown here.

kernel/kthread.c+2−1

This diff is large: its 10 lines aren’t shown here.

kernel/locking/lockdep.c+7−13

This diff is large: its 58 lines aren’t shown here.

kernel/params.c+1−1

This diff is large: its 9 lines aren’t shown here.

kernel/power/process.c+1−1

This diff is large: its 9 lines aren’t shown here.

kernel/printk/printk_ringbuffer.c+1−1

This diff is large: its 9 lines aren’t shown here.

kernel/rcu/tree.c+1−1

This diff is large: its 9 lines aren’t shown here.

kernel/sched/cpufreq_schedutil.c+9−9

This diff is large: its 62 lines aren’t shown here.

kernel/signal.c+10−9

This diff is large: its 27 lines aren’t shown here.

kernel/stop_machine.c+1−1

This diff is large: its 9 lines aren’t shown here.

kernel/time/hrtimer.c+0−5

This diff is large: its 12 lines aren’t shown here.

kernel/time/itimer.c+0−4

This diff is large: its 11 lines aren’t shown here.

kernel/time/sched_clock.c+2−2

This diff is large: its 16 lines aren’t shown here.

kernel/time/timer.c+0−5

This diff is large: its 12 lines aren’t shown here.

kernel/trace/ring_buffer.c+46−12

This diff is large: its 97 lines aren’t shown here.

kernel/trace/trace.c+3−3

This diff is large: its 27 lines aren’t shown here.

kernel/trace/trace.h+23−3

This diff is large: its 52 lines aren’t shown here.

kernel/trace/trace_events_synth.c+7−10

This diff is large: its 55 lines aren’t shown here.

kernel/trace/trace_selftest.c+7−2

This diff is large: its 16 lines aren’t shown here.

kernel/tracepoint.c+1−1

This diff is large: its 9 lines aren’t shown here.

lib/Kconfig.debug+2−0

This diff is large: its 7 lines aren’t shown here.

lib/crc32test.c+0−4

This diff is large: its 32 lines aren’t shown here.

lib/fonts/font_10x18.c+1−1

This diff is large: its 9 lines aren’t shown here.

lib/fonts/font_6x10.c+1−1

This diff is large: its 9 lines aren’t shown here.

lib/fonts/font_6x11.c+1−1

This diff is large: its 9 lines aren’t shown here.

lib/fonts/font_6x8.c+1−1

This diff is large: its 9 lines aren’t shown here.

lib/fonts/font_7x14.c+1−1

This diff is large: its 9 lines aren’t shown here.

lib/fonts/font_8x16.c+1−1

This diff is large: its 9 lines aren’t shown here.

lib/fonts/font_8x8.c+1−1

This diff is large: its 9 lines aren’t shown here.

lib/fonts/font_acorn_8x8.c+1−1

This diff is large: its 9 lines aren’t shown here.

lib/fonts/font_mini_4x6.c+1−1

This diff is large: its 9 lines aren’t shown here.

lib/fonts/font_pearl_8x8.c+1−1

This diff is large: its 9 lines aren’t shown here.

lib/fonts/font_sun12x22.c+1−1

This diff is large: its 9 lines aren’t shown here.

lib/fonts/font_sun8x16.c+1−1

This diff is large: its 9 lines aren’t shown here.

lib/fonts/font_ter16x32.c+1−1

This diff is large: its 9 lines aren’t shown here.

lib/scatterlist.c+1−1

This diff is large: its 9 lines aren’t shown here.

lib/test_kasan.c+107−42

This diff is large: its 241 lines aren’t shown here.

mm/hugetlb.c+11−9

This diff is large: its 53 lines aren’t shown here.

mm/memcontrol.c+18−7

This diff is large: its 48 lines aren’t shown here.

mm/mempolicy.c+3−3

This diff is large: its 27 lines aren’t shown here.

mm/memremap.c+16−23

This diff is large: its 92 lines aren’t shown here.

mm/truncate.c+1−1

This diff is large: its 9 lines aren’t shown here.

net/atm/lec.c+2−3

This diff is large: its 12 lines aren’t shown here.

net/bluetooth/msft.c+2−1

This diff is large: its 15 lines aren’t shown here.

net/can/Kconfig+3−2

This diff is large: its 12 lines aren’t shown here.

net/can/isotp.c+14−12

This diff is large: its 47 lines aren’t shown here.

net/can/j1939/socket.c+6−0

This diff is large: its 13 lines aren’t shown here.

net/can/proc.c+4−2

This diff is large: its 18 lines aren’t shown here.

net/ipv4/ip_tunnel.c+0−3

This diff is large: its 10 lines aren’t shown here.

net/ipv4/netfilter.c+5−3

This diff is large: its 23 lines aren’t shown here.

net/ipv4/netfilter/iptable_mangle.c+1−1

This diff is large: its 9 lines aren’t shown here.

net/ipv4/netfilter/nf_reject_ipv4.c+1−1

This diff is large: its 9 lines aren’t shown here.

net/ipv4/xfrm4_tunnel.c+2−2

This diff is large: its 17 lines aren’t shown here.

net/ipv6/icmp.c+7−1

This diff is large: its 15 lines aren’t shown here.

net/ipv6/ip6_tunnel.c+2−2

This diff is large: its 18 lines aren’t shown here.

net/ipv6/netfilter.c+3−3

This diff is large: its 22 lines aren’t shown here.

net/ipv6/netfilter/ip6table_mangle.c+1−1

This diff is large: its 9 lines aren’t shown here.

net/ipv6/reassembly.c+32−1

This diff is large: its 54 lines aren’t shown here.

net/ipv6/xfrm6_tunnel.c+2−2

This diff is large: its 16 lines aren’t shown here.

net/mac80211/mlme.c+2−1

This diff is large: its 17 lines aren’t shown here.

net/mac80211/sta_info.c+18−0

This diff is large: its 25 lines aren’t shown here.

net/mac80211/sta_info.h+8−1

This diff is large: its 23 lines aren’t shown here.

net/mac80211/tx.c+28−16

This diff is large: its 102 lines aren’t shown here.

net/mptcp/token.c+1−1

This diff is large: its 9 lines aren’t shown here.

net/netfilter/ipset/ip_set_core.c+2−1

This diff is large: its 16 lines aren’t shown here.

net/netfilter/ipvs/ip_vs_core.c+2−2

This diff is large: its 15 lines aren’t shown here.

net/netfilter/nf_nat_proto.c+2−2

This diff is large: its 18 lines aren’t shown here.

net/netfilter/nf_synproxy_core.c+1−1

This diff is large: its 9 lines aren’t shown here.

net/netfilter/nf_tables_api.c+12−7

This diff is large: its 67 lines aren’t shown here.

net/netfilter/nfnetlink.c+18−4

This diff is large: its 46 lines aren’t shown here.

net/netfilter/nft_chain_route.c+2−2

This diff is large: its 18 lines aren’t shown here.

net/netfilter/utils.c+2−2

This diff is large: its 11 lines aren’t shown here.

net/openvswitch/datapath.c+7−7

This diff is large: its 38 lines aren’t shown here.

net/openvswitch/flow_table.c+1−1

This diff is large: its 9 lines aren’t shown here.

net/sctp/sm_sideeffect.c+2−2

This diff is large: its 15 lines aren’t shown here.

net/smc/smc_clc.h+2−2

This diff is large: its 18 lines aren’t shown here.

net/wireless/core.c+31−26

This diff is large: its 90 lines aren’t shown here.

net/wireless/core.h+3−2

This diff is large: its 12 lines aren’t shown here.

net/wireless/nl80211.c+2−1

This diff is large: its 10 lines aren’t shown here.

net/wireless/reg.c+1−1

This diff is large: its 9 lines aren’t shown here.

net/xfrm/xfrm_interface.c+4−4

This diff is large: its 34 lines aren’t shown here.

net/xfrm/xfrm_state.c+5−3

This diff is large: its 34 lines aren’t shown here.

samples/mic/mpssd/.gitignore+0−2

This diff is large: its 3 lines aren’t shown here.

samples/mic/mpssd/Makefile+0−28

This diff is large: its 29 lines aren’t shown here.

samples/mic/mpssd/micctrl+0−162

This diff is large: its 163 lines aren’t shown here.

samples/mic/mpssd/mpss+0−189

This diff is large: its 190 lines aren’t shown here.

samples/mic/mpssd/mpssd.c+0−1815

This diff is large: its 1816 lines aren’t shown here.

samples/mic/mpssd/mpssd.h+0−89

This diff is large: its 90 lines aren’t shown here.

samples/mic/mpssd/sysfs.c+0−91

This diff is large: its 92 lines aren’t shown here.

scripts/get_abi.pl+251−114

This diff is large: its 574 lines aren’t shown here.

scripts/kernel-doc+15−6

This diff is large: its 44 lines aren’t shown here.

security/integrity/ima/ima.h+1−1

This diff is large: its 9 lines aren’t shown here.

sound/core/control.c+2−2

This diff is large: its 11 lines aren’t shown here.

sound/core/pcm_dmaengine.c+2−1

This diff is large: its 10 lines aren’t shown here.

sound/core/pcm_lib.c+1−1

This diff is large: its 9 lines aren’t shown here.

sound/core/pcm_native.c+2−2

This diff is large: its 18 lines aren’t shown here.

sound/hda/ext/hdac_ext_controller.c+2−0

This diff is large: its 9 lines aren’t shown here.

sound/pci/hda/hda_codec.c+29−16

This diff is large: its 103 lines aren’t shown here.

sound/pci/hda/hda_controller.h+2−1

This diff is large: its 17 lines aren’t shown here.

sound/pci/hda/hda_intel.c+35−28

This diff is large: its 139 lines aren’t shown here.

sound/pci/hda/patch_realtek.c+56−11

This diff is large: its 123 lines aren’t shown here.

sound/soc/atmel/mchp-spdiftx.c+0−1

This diff is large: its 8 lines aren’t shown here.

sound/soc/codecs/cs42l51.c+21−1

This diff is large: its 30 lines aren’t shown here.

sound/soc/codecs/wcd9335.c+1−1

This diff is large: its 9 lines aren’t shown here.

sound/soc/codecs/wcd934x.c+1−1

This diff is large: its 9 lines aren’t shown here.

sound/soc/codecs/wsa881x.c+2−0

This diff is large: its 9 lines aren’t shown here.

sound/soc/intel/Kconfig+0−18

This diff is large: its 39 lines aren’t shown here.

sound/soc/intel/atom/Makefile+1−1

This diff is large: its 6 lines aren’t shown here.

sound/soc/intel/atom/sst/Makefile+3−3

This diff is large: its 10 lines aren’t shown here.

sound/soc/intel/boards/kbl_rt5663_max98927.c+31−8

This diff is large: its 57 lines aren’t shown here.

sound/soc/intel/catpt/dsp.c+6−3

This diff is large: its 16 lines aren’t shown here.

sound/soc/intel/catpt/pcm.c+10−0

This diff is large: its 18 lines aren’t shown here.

sound/soc/mediatek/mt8183/mt8183-da7219-max98357.c+25−6

This diff is large: its 41 lines aren’t shown here.

sound/soc/qcom/lpass-cpu.c+10−4

This diff is large: its 45 lines aren’t shown here.

sound/soc/qcom/lpass-sc7180.c+1−1

This diff is large: its 9 lines aren’t shown here.

sound/soc/qcom/sdm845.c+2−0

This diff is large: its 16 lines aren’t shown here.

sound/soc/soc-core.c+1−1

This diff is large: its 9 lines aren’t shown here.

sound/soc/soc-dapm.c+1−1

This diff is large: its 9 lines aren’t shown here.

sound/soc/sof/loader.c+5−0

This diff is large: its 12 lines aren’t shown here.

sound/usb/pcm.c+6−0

This diff is large: its 27 lines aren’t shown here.

sound/usb/quirks.c+1−0

This diff is large: its 8 lines aren’t shown here.

tools/arch/arm64/include/uapi/asm/kvm.h+25−0

This diff is large: its 46 lines aren’t shown here.

tools/arch/s390/include/uapi/asm/sie.h+1−1

This diff is large: its 9 lines aren’t shown here.

tools/arch/x86/include/asm/cpufeatures.h+5−1

This diff is large: its 41 lines aren’t shown here.

tools/arch/x86/include/asm/disabled-features.h+8−1

This diff is large: its 23 lines aren’t shown here.

tools/arch/x86/include/asm/msr-index.h+10−0

This diff is large: its 41 lines aren’t shown here.

tools/arch/x86/include/asm/required-features.h+1−1

This diff is large: its 9 lines aren’t shown here.

tools/arch/x86/include/uapi/asm/kvm.h+20−0

This diff is large: its 27 lines aren’t shown here.

tools/arch/x86/include/uapi/asm/svm.h+13−0

This diff is large: its 38 lines aren’t shown here.

tools/build/feature/test-all.c+0−1

This diff is large: its 8 lines aren’t shown here.

tools/include/linux/compiler-gcc.h+0−12

This diff is large: its 19 lines aren’t shown here.

tools/include/linux/compiler.h+0−3

This diff is large: its 10 lines aren’t shown here.

tools/include/uapi/asm-generic/unistd.h+3−1

This diff is large: its 13 lines aren’t shown here.

tools/include/uapi/drm/i915_drm.h+56−3

This diff is large: its 87 lines aren’t shown here.

tools/include/uapi/linux/fscrypt.h+3−3

This diff is large: its 28 lines aren’t shown here.

tools/include/uapi/linux/kvm.h+19−0

This diff is large: its 47 lines aren’t shown here.

tools/include/uapi/linux/mman.h+1−0

This diff is large: its 8 lines aren’t shown here.

tools/include/uapi/linux/mount.h+1−0

This diff is large: its 8 lines aren’t shown here.

tools/include/uapi/linux/perf_event.h+1−1

This diff is large: its 9 lines aren’t shown here.

tools/include/uapi/linux/prctl.h+9−0

This diff is large: its 16 lines aren’t shown here.

tools/include/uapi/linux/vhost.h+4−0

This diff is large: its 9 lines aren’t shown here.

tools/perf/Makefile.config+1−0

This diff is large: its 8 lines aren’t shown here.

tools/perf/arch/x86/entry/syscalls/syscall_64.tbl+7−4

This diff is large: its 24 lines aren’t shown here.

tools/perf/builtin-trace.c+9−6

This diff is large: its 29 lines aren’t shown here.

tools/perf/pmu-events/arch/x86/cascadelakex/clx-metrics.json+1−1

This diff is large: its 9 lines aren’t shown here.

tools/perf/pmu-events/arch/x86/skylakex/skx-metrics.json+1−1

This diff is large: its 9 lines aren’t shown here.

tools/perf/tests/dwarf-unwind.c+5−5

This diff is large: its 42 lines aren’t shown here.

tools/perf/ui/browsers/hists.c+1−1

This diff is large: its 9 lines aren’t shown here.

tools/perf/util/build-id.c+2−0

This diff is large: its 9 lines aren’t shown here.

tools/perf/util/hashmap.c+3−0

This diff is large: its 10 lines aren’t shown here.

tools/perf/util/hashmap.h+12−0

This diff is large: its 19 lines aren’t shown here.

tools/perf/util/machine.c+10−1

This diff is large: its 22 lines aren’t shown here.

tools/perf/util/scripting-engines/trace-event-python.c+2−5

This diff is large: its 31 lines aren’t shown here.

tools/perf/util/session.c+14−0

This diff is large: its 35 lines aren’t shown here.

tools/perf/util/symbol.c+7−0

This diff is large: its 14 lines aren’t shown here.

tools/perf/util/symbol.h+2−0

This diff is large: its 9 lines aren’t shown here.

tools/testing/kunit/kunit_parser.py+1−2

This diff is large: its 17 lines aren’t shown here.

tools/testing/kunit/kunit_tool_test.py+25−7

This diff is large: its 73 lines aren’t shown here.

tools/testing/kunit/test_data/test_config_printk_time.log+2−1

This diff is large: its 14 lines aren’t shown here.

tools/testing/kunit/test_data/test_interrupted_tap_output.log+2−1

This diff is large: its 14 lines aren’t shown here.

tools/testing/kunit/test_data/test_kernel_panic_interrupt.log+2−1

This diff is large: its 14 lines aren’t shown here.

tools/testing/kunit/test_data/test_multiple_prefixes.log+2−1

This diff is large: its 14 lines aren’t shown here.

tools/testing/kunit/test_data/test_pound_no_prefix.log+2−1

This diff is large: its 14 lines aren’t shown here.

tools/testing/kunit/test_data/test_pound_sign.log+1−0

This diff is large: its 8 lines aren’t shown here.

tools/testing/selftests/arm64/mte/check_buffer_fill.c+3−0

This diff is large: its 10 lines aren’t shown here.

tools/testing/selftests/arm64/mte/check_child_memory.c+3−0

This diff is large: its 10 lines aren’t shown here.

tools/testing/selftests/arm64/mte/check_ksm_options.c+4−0

This diff is large: its 11 lines aren’t shown here.

tools/testing/selftests/arm64/mte/check_mmap_options.c+4−0

This diff is large: its 12 lines aren’t shown here.

tools/testing/selftests/arm64/mte/check_tags_inclusion.c+3−0

This diff is large: its 10 lines aren’t shown here.

tools/testing/selftests/arm64/mte/check_user_mem.c+4−0

This diff is large: its 14 lines aren’t shown here.

tools/testing/selftests/filesystems/epoll/epoll_wakeup_test.c+95−0

This diff is large: its 100 lines aren’t shown here.

tools/testing/selftests/kselftest_harness.h+22−22

This diff is large: its 198 lines aren’t shown here.

tools/testing/selftests/kvm/.gitignore+1−0

This diff is large: its 8 lines aren’t shown here.

tools/testing/selftests/kvm/Makefile+1−0

This diff is large: its 8 lines aren’t shown here.

tools/testing/selftests/kvm/include/x86_64/vmx.h+6−0

This diff is large: its 19 lines aren’t shown here.

tools/testing/selftests/kvm/lib/kvm_util.c+16−7

This diff is large: its 37 lines aren’t shown here.

tools/testing/selftests/kvm/lib/x86_64/vmx.c+9−0

This diff is large: its 13 lines aren’t shown here.

tools/testing/selftests/kvm/x86_64/vmx_apic_access_test.c+142−0

This diff is large: its 143 lines aren’t shown here.

tools/testing/selftests/wireguard/netns.sh+8−0

This diff is large: its 15 lines aren’t shown here.

tools/testing/selftests/wireguard/qemu/kernel.config+2−0

This diff is large: its 13 lines aren’t shown here.

Merge git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net

Keyboard shortcuts

General

Issues and pull requests

Issues, pull requests and Inbox

Repository code

@@ -14,13 +14,17 @@ Description: · 13 unmodified lines
14	Each /dev/fw* is associated with one IEEE 1394 node, which can	14	Each /dev/fw* is associated with one IEEE 1394 node, which can
15	be remote or local nodes. Operations on a /dev/fw* file have	15	be remote or local nodes. Operations on a /dev/fw* file have
16	different scope:	16	different scope:
		17
17	- The 1394 node which is associated with the file:	18	- The 1394 node which is associated with the file:
		19
18	- Asynchronous request transmission	20	- Asynchronous request transmission
19	- Get the Configuration ROM	21	- Get the Configuration ROM
20	- Query node ID	22	- Query node ID
21	- Query maximum speed of the path between this node	23	- Query maximum speed of the path between this node
22	and local node	24	and local node
		25
23	- The 1394 bus (i.e. "card") to which the node is attached to:	26	- The 1394 bus (i.e. "card") to which the node is attached to:
		27
24	- Isochronous stream transmission and reception	28	- Isochronous stream transmission and reception
25	- Asynchronous stream transmission and reception	29	- Asynchronous stream transmission and reception
26	- Asynchronous broadcast request transmission	30	- Asynchronous broadcast request transmission
@@ -31,7 +35,9 @@ Description: · 4 unmodified lines
31	manager	35	manager
32	- Query cycle time	36	- Query cycle time
33	- Bus reset initiation, bus reset event reception	37	- Bus reset initiation, bus reset event reception
		38
34	- All 1394 buses:	39	- All 1394 buses:
		40
35	- Allocation of IEEE 1212 address ranges on the local	41	- Allocation of IEEE 1212 address ranges on the local
36	link layers, reception of inbound requests to such	42	link layers, reception of inbound requests to such
37	an address range, asynchronous response transmission	43	an address range, asynchronous response transmission
@@ -43,6 +49,7 @@ Description: · 5 unmodified lines
43	userland implement different access permission models, some	49	userland implement different access permission models, some
44	operations are restricted to /dev/fw* files that are associated	50	operations are restricted to /dev/fw* files that are associated
45	with a local node:	51	with a local node:
		52
46	- Addition of descriptors or directories to the local	53	- Addition of descriptors or directories to the local
47	nodes' Configuration ROM	54	nodes' Configuration ROM
48	- PHY packet transmission and reception	55	- PHY packet transmission and reception
@@ -55,50 +62,50 @@ Description: · 6 unmodified lines
55	The following file operations are supported:	62	The following file operations are supported:
56		63
57	open(2)	64	open(2)
58	Currently the only useful flags are O_RDWR.	65	Currently the only useful flags are O_RDWR.
59		66
60	ioctl(2)	67	ioctl(2)
61	Initiate various actions. Some take immediate effect, others	68	Initiate various actions. Some take immediate effect, others
62	are performed asynchronously while or after the ioctl returns.	69	are performed asynchronously while or after the ioctl returns.
63	See the inline documentation in <linux/firewire-cdev.h> for	70	See the inline documentation in <linux/firewire-cdev.h> for
64	descriptions of all ioctls.	71	descriptions of all ioctls.
65		72
66	poll(2), select(2), epoll_wait(2) etc.	73	poll(2), select(2), epoll_wait(2) etc.
67	Watch for events to become available to be read.	74	Watch for events to become available to be read.
68		75
69	read(2)	76	read(2)
70	Receive various events. There are solicited events like	77	Receive various events. There are solicited events like
71	outbound asynchronous transaction completion or isochronous	78	outbound asynchronous transaction completion or isochronous
72	buffer completion, and unsolicited events such as bus resets,	79	buffer completion, and unsolicited events such as bus resets,
73	request reception, or PHY packet reception. Always use a read	80	request reception, or PHY packet reception. Always use a read
74	buffer which is large enough to receive the largest event that	81	buffer which is large enough to receive the largest event that
75	could ever arrive. See <linux/firewire-cdev.h> for descriptions	82	could ever arrive. See <linux/firewire-cdev.h> for descriptions
76	of all event types and for which ioctls affect reception of	83	of all event types and for which ioctls affect reception of
77	events.	84	events.
78		85
79	mmap(2)	86	mmap(2)
80	Allocate a DMA buffer for isochronous reception or transmission	87	Allocate a DMA buffer for isochronous reception or transmission
81	and map it into the process address space. The arguments should	88	and map it into the process address space. The arguments should
82	be used as follows: addr = NULL, length = the desired buffer	89	be used as follows: addr = NULL, length = the desired buffer
83	size, i.e. number of packets times size of largest packet,	90	size, i.e. number of packets times size of largest packet,
84	prot = at least PROT_READ for reception and at least PROT_WRITE	91	prot = at least PROT_READ for reception and at least PROT_WRITE
85	for transmission, flags = MAP_SHARED, fd = the handle to the	92	for transmission, flags = MAP_SHARED, fd = the handle to the
86	/dev/fw*, offset = 0.	93	/dev/fw*, offset = 0.
87		94
88	Isochronous reception works in packet-per-buffer fashion except	95	Isochronous reception works in packet-per-buffer fashion except
89	for multichannel reception which works in buffer-fill mode.	96	for multichannel reception which works in buffer-fill mode.
90		97
91	munmap(2)	98	munmap(2)
92	Unmap the isochronous I/O buffer from the process address space.	99	Unmap the isochronous I/O buffer from the process address space.
93		100
94	close(2)	101	close(2)
95	Besides stopping and freeing I/O contexts that were associated	102	Besides stopping and freeing I/O contexts that were associated
96	with the file descriptor, back out any changes to the local	103	with the file descriptor, back out any changes to the local
97	nodes' Configuration ROM. Deallocate isochronous channels and	104	nodes' Configuration ROM. Deallocate isochronous channels and
98	bandwidth at the IRM that were marked for kernel-assisted	105	bandwidth at the IRM that were marked for kernel-assisted
99	re- and deallocation.	106	re- and deallocation.
100		107
101	Users: libraw1394	108	Users: libraw1394;
102	libdc1394	109	libdc1394;
103	libhinawa	110	libhinawa;
104	tools like linux-firewire-utils, fwhack, ...	111	tools like linux-firewire-utils, fwhack, ...

@@ -69,6 +69,7 @@ Description: Controls if typing interrupts output from speakup. With · 68 unmodified lines
69	speakup if for example	69	speakup if for example
70	the say screen command is used before the	70	the say screen command is used before the
71	entire screen is read.	71	entire screen is read.
		72
72	With no_interrupt set to one, if the say	73	With no_interrupt set to one, if the say
73	screen command is used, and one then types on the keyboard,	74	screen command is used, and one then types on the keyboard,
74	speakup will continue to say the whole screen regardless until	75	speakup will continue to say the whole screen regardless until
@@ -215,8 +216,10 @@ Description: This file contains names for key states. · 140 unmodified lines
215	Again, these are part of the help system. For instance, if you	216	Again, these are part of the help system. For instance, if you
216	had pressed speakup + keypad 3, you would hear:	217	had pressed speakup + keypad 3, you would hear:
217	"speakup keypad 3 is go to bottom edge."	218	"speakup keypad 3 is go to bottom edge."
		219
218	The speakup key is depressed, so the name of the key state is	220	The speakup key is depressed, so the name of the key state is
219	speakup.	221	speakup.
		222
220	This part of the message comes from the states collection.	223	This part of the message comes from the states collection.
221		224
222	What: /sys/accessibility/speakup/i18n/characters	225	What: /sys/accessibility/speakup/i18n/characters
@@ -297,6 +300,7 @@ KernelVersion: 2.6 · 74 unmodified lines
297	Contact: speakup@linux-speakup.org	300	Contact: speakup@linux-speakup.org
298	Description: Controls if punctuation is spoken by speakup, or by the	301	Description: Controls if punctuation is spoken by speakup, or by the
299	synthesizer.	302	synthesizer.
		303
300	For example, speakup speaks ">" as "greater", while	304	For example, speakup speaks ">" as "greater", while
301	the espeak synthesizer used by the soft driver speaks "greater	305	the espeak synthesizer used by the soft driver speaks "greater
302	than". Zero lets speakup speak the punctuation. One lets the	306	than". Zero lets speakup speak the punctuation. One lets the

@@ -20,9 +20,13 @@ Description: Allow the root user to disable/enable in runtime the clock · 19 unmodified lines
20	The user can supply a bitmask value, each bit represents	20	The user can supply a bitmask value, each bit represents
21	a different engine to disable/enable its clock gating feature.	21	a different engine to disable/enable its clock gating feature.
22	The bitmask is composed of 20 bits:	22	The bitmask is composed of 20 bits:
23	0 - 7 : DMA channels	23
24	8 - 11 : MME engines	24	======= ============
25	12 - 19 : TPC engines	25	0 - 7 DMA channels
		26	8 - 11 MME engines
		27	12 - 19 TPC engines
		28	======= ============
		29
26	The bit's location of a specific engine can be determined	30	The bit's location of a specific engine can be determined
27	using (1 << GAUDI_ENGINE_ID_). GAUDI_ENGINE_ID_ values	31	using (1 << GAUDI_ENGINE_ID_). GAUDI_ENGINE_ID_ values
28	are defined in uapi habanalabs.h file in enum gaudi_engine_id	32	are defined in uapi habanalabs.h file in enum gaudi_engine_id
@@ -59,6 +63,7 @@ Description: Allows the root user to read or write directly through the · 30 unmodified lines
59	the generic Linux user-space PCI mapping) because the DDR bar	63	the generic Linux user-space PCI mapping) because the DDR bar
60	is very small compared to the DDR memory and only the driver can	64	is very small compared to the DDR memory and only the driver can
61	move the bar before and after the transaction.	65	move the bar before and after the transaction.
		66
62	If the IOMMU is disabled, it also allows the root user to read	67	If the IOMMU is disabled, it also allows the root user to read
63	or write from the host a device VA of a host mapped memory	68	or write from the host a device VA of a host mapped memory
64		69
@@ -73,6 +78,7 @@ Description: Allows the root user to read or write 64 bit data directly · 8 unmodified lines
73	the generic Linux user-space PCI mapping) because the DDR bar	78	the generic Linux user-space PCI mapping) because the DDR bar
74	is very small compared to the DDR memory and only the driver can	79	is very small compared to the DDR memory and only the driver can
75	move the bar before and after the transaction.	80	move the bar before and after the transaction.
		81
76	If the IOMMU is disabled, it also allows the root user to read	82	If the IOMMU is disabled, it also allows the root user to read
77	or write from the host a device VA of a host mapped memory	83	or write from the host a device VA of a host mapped memory
78		84

@@ -10,29 +10,29 @@ Description: · 9 unmodified lines
10	<uapi/linux/wmi.h>	10	<uapi/linux/wmi.h>
11		11
12	1) To perform an SMBIOS call from userspace, you'll need to	12	1) To perform an SMBIOS call from userspace, you'll need to
13	first determine the minimum size of the calling interface	13	first determine the minimum size of the calling interface
14	buffer for your machine.	14	buffer for your machine.
15	Platforms that contain larger buffers can return larger	15	Platforms that contain larger buffers can return larger
16	objects from the system firmware.	16	objects from the system firmware.
17	Commonly this size is either 4k or 32k.	17	Commonly this size is either 4k or 32k.
18		18
19	To determine the size of the buffer read() a u64 dword from	19	To determine the size of the buffer read() a u64 dword from
20	the WMI character device /dev/wmi/dell-smbios.	20	the WMI character device /dev/wmi/dell-smbios.
21		21
22	2) After you've determined the minimum size of the calling	22	2) After you've determined the minimum size of the calling
23	interface buffer, you can allocate a structure that represents	23	interface buffer, you can allocate a structure that represents
24	the structure documented above.	24	the structure documented above.
25		25
26	3) In the 'length' object store the size of the buffer you	26	3) In the 'length' object store the size of the buffer you
27	determined above and allocated.	27	determined above and allocated.
28		28
29	4) In this buffer object, prepare as necessary for the SMBIOS	29	4) In this buffer object, prepare as necessary for the SMBIOS
30	call you're interested in. Typically SMBIOS buffers have	30	call you're interested in. Typically SMBIOS buffers have
31	"class", "select", and "input" defined to values that coincide	31	"class", "select", and "input" defined to values that coincide
32	with the data you are interested in.	32	with the data you are interested in.
33	Documenting class/select/input values is outside of the scope	33	Documenting class/select/input values is outside of the scope
34	of this documentation. Check with the libsmbios project for	34	of this documentation. Check with the libsmbios project for
35	further documentation on these values.	35	further documentation on these values.
36		36
37	6) Run the call by using ioctl() as described in the header.	37	6) Run the call by using ioctl() as described in the header.
38		38

@@ -9,25 +9,25 @@ Description: Generic interface to platform dependent persistent storage. · 8 unmodified lines
9	provide a generic interface to show records captured in	9	provide a generic interface to show records captured in
10	the dying moments. In the case of a panic the last part	10	the dying moments. In the case of a panic the last part
11	of the console log is captured, but other interesting	11	of the console log is captured, but other interesting
12	data can also be saved.	12	data can also be saved::
13		13
14	# mount -t pstore -o kmsg_bytes=8000 - /sys/fs/pstore	14	# mount -t pstore -o kmsg_bytes=8000 - /sys/fs/pstore
15		15
16	$ ls -l /sys/fs/pstore/	16	$ ls -l /sys/fs/pstore/
17	total 0	17	total 0
18	-r--r--r-- 1 root root 7896 Nov 30 15:38 dmesg-erst-1	18	-r--r--r-- 1 root root 7896 Nov 30 15:38 dmesg-erst-1
19		19
20	Different users of this interface will result in different	20	Different users of this interface will result in different
21	filename prefixes. Currently two are defined:	21	filename prefixes. Currently two are defined:
22		22
23	"dmesg" - saved console log	23	- "dmesg" - saved console log
24	"mce" - architecture dependent data from fatal h/w error	24	- "mce" - architecture dependent data from fatal h/w error
25		25
26	Once the information in a file has been read, removing	26	Once the information in a file has been read, removing
27	the file will signal to the underlying persistent storage	27	the file will signal to the underlying persistent storage
28	device that it can reclaim the space for later re-use.	28	device that it can reclaim the space for later re-use::
29		29
30	$ rm /sys/fs/pstore/dmesg-erst-1	30	$ rm /sys/fs/pstore/dmesg-erst-1
31		31
32	The expectation is that all files in /sys/fs/pstore/	32	The expectation is that all files in /sys/fs/pstore/
33	will be saved elsewhere and erased from persistent store	33	will be saved elsewhere and erased from persistent store
@@ -44,4 +44,3 @@ Description: Generic interface to platform dependent persistent storage. · 10 unmodified lines
44	backends are available, the preferred backend may be	44	backends are available, the preferred backend may be
45	set by passing the pstore.backend= argument to the kernel at	45	set by passing the pstore.backend= argument to the kernel at
46	boot time.	46	boot time.
47

@@ -20,6 +20,7 @@ Contact: Cornelia Huck <cornelia.huck@de.ibm.com> · 19 unmodified lines
20	Description: Contains the ids of the channel paths used by this	20	Description: Contains the ids of the channel paths used by this
21	subchannel, as reported by the channel subsystem	21	subchannel, as reported by the channel subsystem
22	during subchannel recognition.	22	during subchannel recognition.
		23
23	Note: This is an I/O-subchannel specific attribute.	24	Note: This is an I/O-subchannel specific attribute.
24	Users: s390-tools, HAL	25	Users: s390-tools, HAL
25		26
@@ -31,6 +32,7 @@ Description: Contains the PIM/PAM/POM values, as reported by the · 5 unmodified lines
31	channel subsystem when last queried by the common I/O	32	channel subsystem when last queried by the common I/O
32	layer (this implies that this attribute is not necessarily	33	layer (this implies that this attribute is not necessarily
33	in sync with the values current in the channel subsystem).	34	in sync with the values current in the channel subsystem).
		35
34	Note: This is an I/O-subchannel specific attribute.	36	Note: This is an I/O-subchannel specific attribute.
35	Users: s390-tools, HAL	37	Users: s390-tools, HAL
36		38
@@ -53,6 +55,7 @@ Description: This file allows the driver for a device to be specified. When · 16 unmodified lines
53	opt-out of driver binding using a driver_override name such as	55	opt-out of driver binding using a driver_override name such as
54	"none". Only a single driver may be specified in the override,	56	"none". Only a single driver may be specified in the override,
55	there is no support for parsing delimiters.	57	there is no support for parsing delimiters.
		58
56	Note that unlike the mechanism of the same name for pci, this	59	Note that unlike the mechanism of the same name for pci, this
57	file does not allow to override basic matching rules. I.e.,	60	file does not allow to override basic matching rules. I.e.,
58	the driver must still match the subchannel type of the device.	61	the driver must still match the subchannel type of the device.

@@ -8,13 +8,13 @@ Description: Read-only. Attribute group to describe the magic bits · 7 unmodified lines
8		8
9	Each attribute under this group defines a bit range of the	9	Each attribute under this group defines a bit range of the
10	perf_event_attr.config. All supported attributes are listed	10	perf_event_attr.config. All supported attributes are listed
11	below.	11	below::
12		12
13	event = "config:0-11" - event ID	13	event = "config:0-11" - event ID
14	evtype = "config:12-15" - event type	14	evtype = "config:12-15" - event type
15	portid = "config:16-23" - event source	15	portid = "config:16-23" - event source
16		16
17	For example,	17	For example::
18		18
19	fab_mmio_read = "event=0x06,evtype=0x02,portid=0xff"	19	fab_mmio_read = "event=0x06,evtype=0x02,portid=0xff"
20		20
@@ -40,11 +40,11 @@ Description: Read-only. Attribute group to describe performance monitoring · 19 unmodified lines
40		40
41	All supported performance monitoring events are listed below.	41	All supported performance monitoring events are listed below.
42		42
43	Basic events (evtype=0x00)	43	Basic events (evtype=0x00)::
44		44
45	clock = "event=0x00,evtype=0x00,portid=0xff"	45	clock = "event=0x00,evtype=0x00,portid=0xff"
46		46
47	Cache events (evtype=0x01)	47	Cache events (evtype=0x01)::
48		48
49	cache_read_hit = "event=0x00,evtype=0x01,portid=0xff"	49	cache_read_hit = "event=0x00,evtype=0x01,portid=0xff"
50	cache_read_miss = "event=0x01,evtype=0x01,portid=0xff"	50	cache_read_miss = "event=0x01,evtype=0x01,portid=0xff"
@@ -59,7 +59,7 @@ Description: Read-only. Attribute group to describe performance monitoring · 8 unmodified lines
59	cache_rx_req_stall = "event=0x09,evtype=0x01,portid=0xff"	59	cache_rx_req_stall = "event=0x09,evtype=0x01,portid=0xff"
60	cache_eviction = "event=0x0a,evtype=0x01,portid=0xff"	60	cache_eviction = "event=0x0a,evtype=0x01,portid=0xff"
61		61
62	Fabric events (evtype=0x02)	62	Fabric events (evtype=0x02)::
63		63
64	fab_pcie0_read = "event=0x00,evtype=0x02,portid=0xff"	64	fab_pcie0_read = "event=0x00,evtype=0x02,portid=0xff"
65	fab_pcie0_write = "event=0x01,evtype=0x02,portid=0xff"	65	fab_pcie0_write = "event=0x01,evtype=0x02,portid=0xff"
@@ -78,7 +78,7 @@ Description: Read-only. Attribute group to describe performance monitoring · 12 unmodified lines
78	fab_port_mmio_read = "event=0x06,evtype=0x02,portid=?"	78	fab_port_mmio_read = "event=0x06,evtype=0x02,portid=?"
79	fab_port_mmio_write = "event=0x07,evtype=0x02,portid=?"	79	fab_port_mmio_write = "event=0x07,evtype=0x02,portid=?"
80		80
81	VTD events (evtype=0x03)	81	VTD events (evtype=0x03)::
82		82
83	vtd_port_read_transaction = "event=0x00,evtype=0x03,portid=?"	83	vtd_port_read_transaction = "event=0x00,evtype=0x03,portid=?"
84	vtd_port_write_transaction = "event=0x01,evtype=0x03,portid=?"	84	vtd_port_write_transaction = "event=0x01,evtype=0x03,portid=?"
@@ -88,7 +88,7 @@ Description: Read-only. Attribute group to describe performance monitoring · 3 unmodified lines
88	vtd_port_devtlb_2m_fill = "event=0x05,evtype=0x03,portid=?"	88	vtd_port_devtlb_2m_fill = "event=0x05,evtype=0x03,portid=?"
89	vtd_port_devtlb_1g_fill = "event=0x06,evtype=0x03,portid=?"	89	vtd_port_devtlb_1g_fill = "event=0x06,evtype=0x03,portid=?"
90		90
91	VTD SIP events (evtype=0x04)	91	VTD SIP events (evtype=0x04)::
92		92
93	vtd_sip_iotlb_4k_hit = "event=0x00,evtype=0x04,portid=0xff"	93	vtd_sip_iotlb_4k_hit = "event=0x00,evtype=0x04,portid=0xff"
94	vtd_sip_iotlb_2m_hit = "event=0x01,evtype=0x04,portid=0xff"	94	vtd_sip_iotlb_2m_hit = "event=0x01,evtype=0x04,portid=0xff"

@@ -15,6 +15,7 @@ Description: · 14 unmodified lines
15	based on hardware generated events (e.g. data ready) or	15	based on hardware generated events (e.g. data ready) or
16	provided by a separate driver for other hardware (e.g.	16	provided by a separate driver for other hardware (e.g.
17	periodic timer, GPIO or high resolution timer).	17	periodic timer, GPIO or high resolution timer).
		18
18	Contains trigger type specific elements. These do not	19	Contains trigger type specific elements. These do not
19	generalize well and hence are not documented in this file.	20	generalize well and hence are not documented in this file.
20	X is the IIO index of the trigger.	21	X is the IIO index of the trigger.
@@ -65,6 +66,7 @@ Contact: linux-iio@vger.kernel.org · 44 unmodified lines
65	Description:	66	Description:
66	When the internal sampling clock can only take a specific set of	67	When the internal sampling clock can only take a specific set of
67	frequencies, we can specify the available values with:	68	frequencies, we can specify the available values with:
		69
68	- a small discrete set of values like "0 2 4 6 8"	70	- a small discrete set of values like "0 2 4 6 8"
69	- a range with minimum, step and maximum frequencies like	71	- a range with minimum, step and maximum frequencies like
70	"[min step max]"	72	"[min step max]"
@@ -665,6 +667,7 @@ Description: · 594 unmodified lines
665	<type>[Y][_name]_<raw\|input>_thresh_falling_value may take	667	<type>[Y][_name]_<raw\|input>_thresh_falling_value may take
666	different values, but the device can only enable both thresholds	668	different values, but the device can only enable both thresholds
667	or neither.	669	or neither.
		670
668	Note the driver will assume the last p events requested are	671	Note the driver will assume the last p events requested are
669	to be enabled where p is how many it supports (which may vary	672	to be enabled where p is how many it supports (which may vary
670	depending on the exact set requested. So if you want to be	673	depending on the exact set requested. So if you want to be
@@ -719,6 +722,7 @@ Description: · 48 unmodified lines
719	<type>[Y][_name]_<raw\|input>_roc_falling_value may take	722	<type>[Y][_name]_<raw\|input>_roc_falling_value may take
720	different values, but the device can only enable both rate of	723	different values, but the device can only enable both rate of
721	change thresholds or neither.	724	change thresholds or neither.
		725
722	Note the driver will assume the last p events requested are	726	Note the driver will assume the last p events requested are
723	to be enabled where p is however many it supports (which may	727	to be enabled where p is however many it supports (which may
724	vary depending on the exact set requested. So if you want to be	728	vary depending on the exact set requested. So if you want to be
@@ -774,9 +778,11 @@ Description: · 49 unmodified lines
774	Specifies the value of threshold that the device is comparing	778	Specifies the value of threshold that the device is comparing
775	against for the events enabled by	779	against for the events enabled by
776	<type>Y[_name]_thresh[_rising\|falling]_en.	780	<type>Y[_name]_thresh[_rising\|falling]_en.
		781
777	If separate attributes exist for the two directions, but	782	If separate attributes exist for the two directions, but
778	direction is not specified for this attribute, then a single	783	direction is not specified for this attribute, then a single
779	threshold value applies to both directions.	784	threshold value applies to both directions.
		785
780	The raw or input element of the name indicates whether the	786	The raw or input element of the name indicates whether the
781	value is in raw device units or in processed units (as _raw	787	value is in raw device units or in processed units (as _raw
782	and _input do on sysfs direct channel read attributes).	788	and _input do on sysfs direct channel read attributes).
@@ -859,6 +865,7 @@ Description: · 76 unmodified lines
859	If separate attributes exist for the two directions, but	865	If separate attributes exist for the two directions, but
860	direction is not specified for this attribute, then a single	866	direction is not specified for this attribute, then a single
861	hysteresis value applies to both directions.	867	hysteresis value applies to both directions.
		868
862	For falling events the hysteresis is added to the _value attribute for	869	For falling events the hysteresis is added to the _value attribute for
863	this event to get the upper threshold for when the event goes back to	870	this event to get the upper threshold for when the event goes back to
864	normal, for rising events the hysteresis is subtracted from the _value	871	normal, for rising events the hysteresis is subtracted from the _value
@@ -905,6 +912,7 @@ Description: · 40 unmodified lines
905	Specifies the value of rate of change threshold that the	912	Specifies the value of rate of change threshold that the
906	device is comparing against for the events enabled by	913	device is comparing against for the events enabled by
907	<type>[Y][_name]_roc[_rising\|falling]_en.	914	<type>[Y][_name]_roc[_rising\|falling]_en.
		915
908	If separate attributes exist for the two directions,	916	If separate attributes exist for the two directions,
909	but direction is not specified for this attribute,	917	but direction is not specified for this attribute,
910	then a single threshold value applies to both directions.	918	then a single threshold value applies to both directions.
@@ -1304,6 +1312,7 @@ Description: · 393 unmodified lines
1304	Proximity measurement indicating that some	1312	Proximity measurement indicating that some
1305	object is near the sensor, usually by observing	1313	object is near the sensor, usually by observing
1306	reflectivity of infrared or ultrasound emitted.	1314	reflectivity of infrared or ultrasound emitted.
		1315
1307	Often these sensors are unit less and as such conversion	1316	Often these sensors are unit less and as such conversion
1308	to SI units is not possible. Higher proximity measurements	1317	to SI units is not possible. Higher proximity measurements
1309	indicate closer objects, and vice versa. Units after	1318	indicate closer objects, and vice versa. Units after
@@ -1449,9 +1458,12 @@ Contact: linux-iio@vger.kernel.org · 139 unmodified lines
1449	Description:	1458	Description:
1450	A single positive integer specifying the maximum number of scan	1459	A single positive integer specifying the maximum number of scan
1451	elements to wait for.	1460	elements to wait for.
		1461
1452	Poll will block until the watermark is reached.	1462	Poll will block until the watermark is reached.
		1463
1453	Blocking read will wait until the minimum between the requested	1464	Blocking read will wait until the minimum between the requested
1454	read amount or the low water mark is available.	1465	read amount or the low water mark is available.
		1466
1455	Non-blocking read will retrieve the available samples from the	1467	Non-blocking read will retrieve the available samples from the
1456	buffer even if there are less samples then watermark level. This	1468	buffer even if there are less samples then watermark level. This
1457	allows the application to block on poll with a timeout and read	1469	allows the application to block on poll with a timeout and read
@@ -1480,11 +1492,13 @@ Description: · 22 unmodified lines
1480	device settings allows it (e.g. if a trigger is set that samples	1492	device settings allows it (e.g. if a trigger is set that samples
1481	data differently that the hardware fifo does then hardware fifo	1493	data differently that the hardware fifo does then hardware fifo
1482	will not enabled).	1494	will not enabled).
		1495
1483	If the hardware fifo is enabled and the level of the hardware	1496	If the hardware fifo is enabled and the level of the hardware
1484	fifo reaches the hardware fifo watermark level the device will	1497	fifo reaches the hardware fifo watermark level the device will
1485	flush its hardware fifo to the device buffer. Doing a non	1498	flush its hardware fifo to the device buffer. Doing a non
1486	blocking read on the device when no samples are present in the	1499	blocking read on the device when no samples are present in the
1487	device buffer will also force a flush.	1500	device buffer will also force a flush.
		1501
1488	When the hardware fifo is enabled there is no need to use a	1502	When the hardware fifo is enabled there is no need to use a
1489	trigger to use buffer mode since the watermark settings	1503	trigger to use buffer mode since the watermark settings
1490	guarantees that the hardware fifo is flushed to the device	1504	guarantees that the hardware fifo is flushed to the device
@@ -1522,6 +1536,7 @@ Description: · 31 unmodified lines
1522	A single positive integer specifying the minimum watermark level	1536	A single positive integer specifying the minimum watermark level
1523	for the hardware fifo of this device. If the device does not	1537	for the hardware fifo of this device. If the device does not
1524	have a hardware fifo this entry is not present.	1538	have a hardware fifo this entry is not present.
		1539
1525	If the user sets buffer/watermark to a value less than this one,	1540	If the user sets buffer/watermark to a value less than this one,
1526	then the hardware watermark will remain unset.	1541	then the hardware watermark will remain unset.
1527		1542
@@ -1532,6 +1547,7 @@ Description: · 4 unmodified lines
1532	A single positive integer specifying the maximum watermark level	1547	A single positive integer specifying the maximum watermark level
1533	for the hardware fifo of this device. If the device does not	1548	for the hardware fifo of this device. If the device does not
1534	have a hardware fifo this entry is not present.	1549	have a hardware fifo this entry is not present.
		1550
1535	If the user sets buffer/watermark to a value greater than this	1551	If the user sets buffer/watermark to a value greater than this
1536	one, then the hardware watermark will be capped at this value.	1552	one, then the hardware watermark will be capped at this value.
1537		1553
@@ -1543,6 +1559,7 @@ Description: · 5 unmodified lines
1543	levels for the hardware fifo. This entry is optional and if it	1559	levels for the hardware fifo. This entry is optional and if it
1544	is not present it means that all the values between	1560	is not present it means that all the values between
1545	hwfifo_watermark_min and hwfifo_watermark_max are supported.	1561	hwfifo_watermark_min and hwfifo_watermark_max are supported.
		1562
1546	If the user sets buffer/watermark to a value greater than	1563	If the user sets buffer/watermark to a value greater than
1547	hwfifo_watermak_min but not equal to any of the values in this	1564	hwfifo_watermak_min but not equal to any of the values in this
1548	list, the driver will chose an appropriate value for the	1565	list, the driver will chose an appropriate value for the
@@ -1604,7 +1621,8 @@ KernelVersion: 4.1.0 · 55 unmodified lines
1604	Contact: linux-iio@vger.kernel.org	1621	Contact: linux-iio@vger.kernel.org
1605	Description:	1622	Description:
1606	'1' (enable) or '0' (disable) specifying the enable	1623	'1' (enable) or '0' (disable) specifying the enable
1607	of heater function. Same reading values apply	1624	of heater function. Same reading values apply.
		1625
1608	This ABI is especially applicable for humidity sensors	1626	This ABI is especially applicable for humidity sensors
1609	to heatup the device and get rid of any condensation	1627	to heatup the device and get rid of any condensation
1610	in some humidity environment	1628	in some humidity environment
@@ -1627,17 +1645,21 @@ Description: · 16 unmodified lines
1627	Mounting matrix for IIO sensors. This is a rotation matrix which	1645	Mounting matrix for IIO sensors. This is a rotation matrix which
1628	informs userspace about sensor chip's placement relative to the	1646	informs userspace about sensor chip's placement relative to the
1629	main hardware it is mounted on.	1647	main hardware it is mounted on.
		1648
1630	Main hardware placement is defined according to the local	1649	Main hardware placement is defined according to the local
1631	reference frame related to the physical quantity the sensor	1650	reference frame related to the physical quantity the sensor
1632	measures.	1651	measures.
		1652
1633	Given that the rotation matrix is defined in a board specific	1653	Given that the rotation matrix is defined in a board specific
1634	way (platform data and / or device-tree), the main hardware	1654	way (platform data and / or device-tree), the main hardware
1635	reference frame definition is left to the implementor's choice	1655	reference frame definition is left to the implementor's choice
1636	(see below for a magnetometer example).	1656	(see below for a magnetometer example).
		1657
1637	Applications should apply this rotation matrix to samples so	1658	Applications should apply this rotation matrix to samples so
1638	that when main hardware reference frame is aligned onto local	1659	that when main hardware reference frame is aligned onto local
1639	reference frame, then sensor chip reference frame is also	1660	reference frame, then sensor chip reference frame is also
1640	perfectly aligned with it.	1661	perfectly aligned with it.
		1662
1641	Matrix is a 3x3 unitary matrix and typically looks like	1663	Matrix is a 3x3 unitary matrix and typically looks like
1642	[0, 1, 0; 1, 0, 0; 0, 0, -1]. Identity matrix	1664	[0, 1, 0; 1, 0, 0; 0, 0, -1]. Identity matrix
1643	[1, 0, 0; 0, 1, 0; 0, 0, 1] means sensor chip and main hardware	1665	[1, 0, 0; 0, 1, 0; 0, 0, 1] means sensor chip and main hardware
@@ -1646,8 +1668,10 @@ Description: · 2 unmodified lines
1646	For example, a mounting matrix for a magnetometer sensor informs	1668	For example, a mounting matrix for a magnetometer sensor informs
1647	userspace about sensor chip's ORIENTATION relative to the main	1669	userspace about sensor chip's ORIENTATION relative to the main
1648	hardware.	1670	hardware.
		1671
1649	More specifically, main hardware orientation is defined with	1672	More specifically, main hardware orientation is defined with
1650	respect to the LOCAL EARTH GEOMAGNETIC REFERENCE FRAME where :	1673	respect to the LOCAL EARTH GEOMAGNETIC REFERENCE FRAME where :
		1674
1651	* Y is in the ground plane and positive towards magnetic North ;	1675	* Y is in the ground plane and positive towards magnetic North ;
1652	* X is in the ground plane, perpendicular to the North axis and	1676	* X is in the ground plane, perpendicular to the North axis and
1653	positive towards the East ;	1677	positive towards the East ;
@@ -1656,13 +1680,16 @@ Description: · 2 unmodified lines
1656	An implementor might consider that for a hand-held device, a	1680	An implementor might consider that for a hand-held device, a
1657	'natural' orientation would be 'front facing camera at the top'.	1681	'natural' orientation would be 'front facing camera at the top'.
1658	The main hardware reference frame could then be described as :	1682	The main hardware reference frame could then be described as :
		1683
1659	* Y is in the plane of the screen and is positive towards the	1684	* Y is in the plane of the screen and is positive towards the
1660	top of the screen ;	1685	top of the screen ;
1661	* X is in the plane of the screen, perpendicular to Y axis, and	1686	* X is in the plane of the screen, perpendicular to Y axis, and
1662	positive towards the right hand side of the screen ;	1687	positive towards the right hand side of the screen ;
1663	* Z is perpendicular to the screen plane and positive out of the	1688	* Z is perpendicular to the screen plane and positive out of the
1664	screen.	1689	screen.
		1690
1665	Another example for a quadrotor UAV might be :	1691	Another example for a quadrotor UAV might be :
		1692
1666	* Y is in the plane of the propellers and positive towards the	1693	* Y is in the plane of the propellers and positive towards the
1667	front-view camera;	1694	front-view camera;
1668	* X is in the plane of the propellers, perpendicular to Y axis,	1695	* X is in the plane of the propellers, perpendicular to Y axis,
@@ -1704,6 +1731,7 @@ Description: · 35 unmodified lines
1704	This interface is deprecated; please use the Counter subsystem.	1731	This interface is deprecated; please use the Counter subsystem.
1705		1732
1706	A list of possible counting directions which are:	1733	A list of possible counting directions which are:
		1734
1707	- "up" : counter device is increasing.	1735	- "up" : counter device is increasing.
1708	- "down": counter device is decreasing.	1736	- "down": counter device is decreasing.
1709		1737

@@ -19,9 +19,11 @@ Description: · 18 unmodified lines
19	is separately set for "GND-Open" and "Supply-Open" modes.	19	is separately set for "GND-Open" and "Supply-Open" modes.
20	Channels 0..31 have common low threshold values, but could have different	20	Channels 0..31 have common low threshold values, but could have different
21	sensing_modes.	21	sensing_modes.
		22
22	The low voltage threshold range is between 2..21V.	23	The low voltage threshold range is between 2..21V.
23	Hysteresis between low and high thresholds can not be lower then 2 and	24	Hysteresis between low and high thresholds can not be lower then 2 and
24	can not be odd.	25	can not be odd.
		26
25	If falling threshold results hysteresis to odd value then rising	27	If falling threshold results hysteresis to odd value then rising
26	threshold is automatically subtracted by one.	28	threshold is automatically subtracted by one.
27		29
@@ -34,10 +36,13 @@ Description: · 6 unmodified lines
34	this value then the threshold rising event is pushed.	36	this value then the threshold rising event is pushed.
35	Depending on in_voltageY_sensing_mode the high voltage threshold	37	Depending on in_voltageY_sensing_mode the high voltage threshold
36	is separately set for "GND-Open" and "Supply-Open" modes.	38	is separately set for "GND-Open" and "Supply-Open" modes.
		39
37	Channels 0..31 have common high threshold values, but could have different	40	Channels 0..31 have common high threshold values, but could have different
38	sensing_modes.	41	sensing_modes.
		42
39	The high voltage threshold range is between 3..22V.	43	The high voltage threshold range is between 3..22V.
40	Hysteresis between low and high thresholds can not be lower then 2 and	44	Hysteresis between low and high thresholds can not be lower then 2 and
41	can not be odd.	45	can not be odd.
		46
42	If rising threshold results hysteresis to odd value then falling	47	If rising threshold results hysteresis to odd value then falling
43	threshold is automatically appended by one.	48	threshold is automatically appended by one.

@@ -9,11 +9,13 @@ Date: June 2015 · 8 unmodified lines
9	KernelVersion: 4.3	9	KernelVersion: 4.3
10	Contact: Alexander Shishkin <alexander.shishkin@linux.intel.com>	10	Contact: Alexander Shishkin <alexander.shishkin@linux.intel.com>
11	Description: (RW) Configure MSC operating mode:	11	Description: (RW) Configure MSC operating mode:
		12
12	- "single", for contiguous buffer mode (high-order alloc);	13	- "single", for contiguous buffer mode (high-order alloc);
13	- "multi", for multiblock mode;	14	- "multi", for multiblock mode;
14	- "ExI", for DCI handler mode;	15	- "ExI", for DCI handler mode;
15	- "debug", for debug mode;	16	- "debug", for debug mode;
16	- any of the currently loaded buffer sinks.	17	- any of the currently loaded buffer sinks.
		18
17	If operating mode changes, existing buffer is deallocated,	19	If operating mode changes, existing buffer is deallocated,
18	provided there are no active users and tracing is not enabled,	20	provided there are no active users and tracing is not enabled,
19	otherwise the write will fail.	21	otherwise the write will fail.
@@ -23,10 +25,12 @@ Date: June 2015 · 3 unmodified lines
23	KernelVersion: 4.3	25	KernelVersion: 4.3
24	Contact: Alexander Shishkin <alexander.shishkin@linux.intel.com>	26	Contact: Alexander Shishkin <alexander.shishkin@linux.intel.com>
25	Description: (RW) Configure MSC buffer size for "single" or "multi" modes.	27	Description: (RW) Configure MSC buffer size for "single" or "multi" modes.
		28
26	In single mode, this is a single number of pages, has to be	29	In single mode, this is a single number of pages, has to be
27	power of 2. In multiblock mode, this is a comma-separated list	30	power of 2. In multiblock mode, this is a comma-separated list
28	of numbers of pages for each window to be allocated. Number of	31	of numbers of pages for each window to be allocated. Number of
29	windows is not limited.	32	windows is not limited.
		33
30	Writing to this file deallocates existing buffer (provided	34	Writing to this file deallocates existing buffer (provided
31	there are no active users and tracing is not enabled) and then	35	there are no active users and tracing is not enabled) and then
32	allocates a new one.	36	allocates a new one.

@@ -12,8 +12,11 @@ KernelVersion: 2.6.26 · 11 unmodified lines
12	Contact: Harrison Metzger <harrisonmetz@gmail.com>	12	Contact: Harrison Metzger <harrisonmetz@gmail.com>
13	Description: Controls the devices display mode.	13	Description: Controls the devices display mode.
14	For a 6 character display the values are	14	For a 6 character display the values are
		15
15	MSB 0x06; LSB 0x3F, and	16	MSB 0x06; LSB 0x3F, and
		17
16	for an 8 character display the values are	18	for an 8 character display the values are
		19
17	MSB 0x08; LSB 0xFF.	20	MSB 0x08; LSB 0xFF.
18		21
19	What: /sys/bus/usb/.../textmode	22	What: /sys/bus/usb/.../textmode
@@ -37,7 +40,7 @@ KernelVersion: 2.6.26 · 17 unmodified lines
37	Contact: Harrison Metzger <harrisonmetz@gmail.com>	40	Contact: Harrison Metzger <harrisonmetz@gmail.com>
38	Description: Controls the decimal places on the device.	41	Description: Controls the decimal places on the device.
39	To set the nth decimal place, give this field	42	To set the nth decimal place, give this field
40	the value of 10 ** n. Assume this field has	43	the value of ``10 ** n``. Assume this field has
41	the value k and has 1 or more decimal places set,	44	the value k and has 1 or more decimal places set,
42	to set the mth place (where m is not already set),	45	to set the mth place (where m is not already set),
43	change this fields value to k + 10 ** m.	46	change this fields value to ``k + 10 ** m``.

@@ -19,18 +19,23 @@ KernelVersion: 4.16 · 18 unmodified lines
19	Contact: linux-leds@vger.kernel.org	19	Contact: linux-leds@vger.kernel.org
20	Description:	20	Description:
21	Signal the link state of the named network device.	21	Signal the link state of the named network device.
		22
22	If set to 0 (default), the LED's normal state is off.	23	If set to 0 (default), the LED's normal state is off.
		24
23	If set to 1, the LED's normal state reflects the link state	25	If set to 1, the LED's normal state reflects the link state
24	of the named network device.	26	of the named network device.
25	Setting this value also immediately changes the LED state.	27	Setting this value also immediately changes the LED state.
26		28
		29
27	What: /sys/class/leds/<led>/tx	30	What: /sys/class/leds/<led>/tx
28	Date: Dec 2017	31	Date: Dec 2017
29	KernelVersion: 4.16	32	KernelVersion: 4.16
30	Contact: linux-leds@vger.kernel.org	33	Contact: linux-leds@vger.kernel.org
31	Description:	34	Description:
32	Signal transmission of data on the named network device.	35	Signal transmission of data on the named network device.
		36
33	If set to 0 (default), the LED will not blink on transmission.	37	If set to 0 (default), the LED will not blink on transmission.
		38
34	If set to 1, the LED will blink for the milliseconds specified	39	If set to 1, the LED will blink for the milliseconds specified
35	in interval to signal transmission.	40	in interval to signal transmission.
36		41
@@ -40,6 +45,8 @@ KernelVersion: 4.16 · 3 unmodified lines
40	Contact: linux-leds@vger.kernel.org	45	Contact: linux-leds@vger.kernel.org
41	Description:	46	Description:
42	Signal reception of data on the named network device.	47	Signal reception of data on the named network device.
		48
43	If set to 0 (default), the LED will not blink on reception.	49	If set to 0 (default), the LED will not blink on reception.
		50
44	If set to 1, the LED will blink for the milliseconds specified	51	If set to 1, the LED will blink for the milliseconds specified
45	in interval to signal reception.	52	in interval to signal reception.

@@ -11,15 +11,17 @@ KernelVersion: 2.6.20 · 10 unmodified lines
11	Contact: Thomas Maier <balagi@justmail.de>	11	Contact: Thomas Maier <balagi@justmail.de>
12	Description:	12	Description:
13		13
14	add: (WO) Write a block device id (major:minor) to	14	========== ==============================================
		15	add (WO) Write a block device id (major:minor) to
15	create a new pktcdvd device and map it to the	16	create a new pktcdvd device and map it to the
16	block device.	17	block device.
17		18
18	remove: (WO) Write the pktcdvd device id (major:minor)	19	remove (WO) Write the pktcdvd device id (major:minor)
19	to remove the pktcdvd device.	20	to remove the pktcdvd device.
20		21
21	device_map: (RO) Shows the device mapping in format:	22	device_map (RO) Shows the device mapping in format:
22	pktcdvd[0-7] <pktdevid> <blkdevid>	23	pktcdvd[0-7] <pktdevid> <blkdevid>
		24	========== ==============================================
23		25
24		26
25	What: /sys/class/pktcdvd/pktcdvd[0-7]/dev	27	What: /sys/class/pktcdvd/pktcdvd[0-7]/dev
@@ -65,29 +67,31 @@ Date: Oct. 2006 · 39 unmodified lines
65	KernelVersion: 2.6.20	67	KernelVersion: 2.6.20
66	Contact: Thomas Maier <balagi@justmail.de>	68	Contact: Thomas Maier <balagi@justmail.de>
67	Description:	69	Description:
68	size: (RO) Contains the size of the bio write queue.	70	============== ================================================
		71	size (RO) Contains the size of the bio write queue.
69		72
70	congestion_off: (RW) If bio write queue size is below this mark,	73	congestion_off (RW) If bio write queue size is below this mark,
71	accept new bio requests from the block layer.	74	accept new bio requests from the block layer.
72		75
73	congestion_on: (RW) If bio write queue size is higher as this	76	congestion_on (RW) If bio write queue size is higher as this
74	mark, do no longer accept bio write requests	77	mark, do no longer accept bio write requests
75	from the block layer and wait till the pktcdvd	78	from the block layer and wait till the pktcdvd
76	device has processed enough bio's so that bio	79	device has processed enough bio's so that bio
77	write queue size is below congestion off mark.	80	write queue size is below congestion off mark.
78	A value of <= 0 disables congestion control.	81	A value of <= 0 disables congestion control.
		82	============== ================================================
79		83
80		84
81	Example:	85	Example:
82	--------	86	--------
83	To use the pktcdvd sysfs interface directly, you can do:	87	To use the pktcdvd sysfs interface directly, you can do::
84		88
85	# create a new pktcdvd device mapped to /dev/hdc	89	# create a new pktcdvd device mapped to /dev/hdc
86	echo "22:0" >/sys/class/pktcdvd/add	90	echo "22:0" >/sys/class/pktcdvd/add
87	cat /sys/class/pktcdvd/device_map	91	cat /sys/class/pktcdvd/device_map
88	# assuming device pktcdvd0 was created, look at stat's	92	# assuming device pktcdvd0 was created, look at stat's
89	cat /sys/class/pktcdvd/pktcdvd0/stat/kb_written	93	cat /sys/class/pktcdvd/pktcdvd0/stat/kb_written
90	# print the device id of the mapped block device	94	# print the device id of the mapped block device
91	fgrep pktcdvd0 /sys/class/pktcdvd/device_map	95	fgrep pktcdvd0 /sys/class/pktcdvd/device_map
92	# remove device, using pktcdvd0 device id 253:0	96	# remove device, using pktcdvd0 device id 253:0
93	echo "253:0" >/sys/class/pktcdvd/remove	97	echo "253:0" >/sys/class/pktcdvd/remove

@@ -6,6 +6,7 @@ Description: · 5 unmodified lines
6	The /sys/class/rapidio_port subdirectory contains individual	6	The /sys/class/rapidio_port subdirectory contains individual
7	subdirectories named as "rapidioN" where N = mport ID registered	7	subdirectories named as "rapidioN" where N = mport ID registered
8	with RapidIO subsystem.	8	with RapidIO subsystem.
		9
9	NOTE: An mport ID is not a RapidIO destination ID assigned to a	10	NOTE: An mport ID is not a RapidIO destination ID assigned to a
10	given local mport device.	11	given local mport device.
11		12
@@ -16,7 +17,9 @@ Contact: Matt Porter <mporter@kernel.crashing.org>, · 4 unmodified lines
16	Alexandre Bounine <alexandre.bounine@idt.com>	17	Alexandre Bounine <alexandre.bounine@idt.com>
17	Description:	18	Description:
18	(RO) reports RapidIO common transport system size:	19	(RO) reports RapidIO common transport system size:
		20
19	0 = small (8-bit destination ID, max. 256 devices),	21	0 = small (8-bit destination ID, max. 256 devices),
		22
20	1 = large (16-bit destination ID, max. 65536 devices).	23	1 = large (16-bit destination ID, max. 65536 devices).
21		24
22	What: /sys/class/rapidio_port/rapidioN/port_destid	25	What: /sys/class/rapidio_port/rapidioN/port_destid
@@ -25,31 +28,32 @@ KernelVersion: v3.15 · 2 unmodified lines
25	Contact: Matt Porter <mporter@kernel.crashing.org>,	28	Contact: Matt Porter <mporter@kernel.crashing.org>,
26	Alexandre Bounine <alexandre.bounine@idt.com>	29	Alexandre Bounine <alexandre.bounine@idt.com>
27	Description:	30	Description:
28	(RO) reports RapidIO destination ID assigned to the given	31
29	RapidIO mport device. If value 0xFFFFFFFF is returned this means	32	(RO) reports RapidIO destination ID assigned to the given
30	that no valid destination ID have been assigned to the mport	33	RapidIO mport device. If value 0xFFFFFFFF is returned this means
31	(yet). Normally, before enumeration/discovery have been executed	34	that no valid destination ID have been assigned to the mport
32	only fabric enumerating mports have a valid destination ID	35	(yet). Normally, before enumeration/discovery have been executed
33	assigned to them using "hdid=..." rapidio module parameter.	36	only fabric enumerating mports have a valid destination ID
		37	assigned to them using "hdid=..." rapidio module parameter.
34		38
35	After enumeration or discovery was performed for a given mport device,	39	After enumeration or discovery was performed for a given mport device,
36	the corresponding subdirectory will also contain subdirectories for each	40	the corresponding subdirectory will also contain subdirectories for each
37	child RapidIO device connected to the mport.	41	child RapidIO device connected to the mport.
38		42
39	The example below shows mport device subdirectory with several child RapidIO	43	The example below shows mport device subdirectory with several child RapidIO
40	devices attached to it.	44	devices attached to it::
41		45
42	[rio@rapidio ~]$ ls /sys/class/rapidio_port/rapidio0/ -l	46	[rio@rapidio ~]$ ls /sys/class/rapidio_port/rapidio0/ -l
43	total 0	47	total 0
44	drwxr-xr-x 3 root root 0 Feb 11 15:10 00:e:0001	48	drwxr-xr-x 3 root root 0 Feb 11 15:10 00:e:0001
45	drwxr-xr-x 3 root root 0 Feb 11 15:10 00:e:0004	49	drwxr-xr-x 3 root root 0 Feb 11 15:10 00:e:0004
46	drwxr-xr-x 3 root root 0 Feb 11 15:10 00:e:0007	50	drwxr-xr-x 3 root root 0 Feb 11 15:10 00:e:0007
47	drwxr-xr-x 3 root root 0 Feb 11 15:10 00:s:0002	51	drwxr-xr-x 3 root root 0 Feb 11 15:10 00:s:0002
48	drwxr-xr-x 3 root root 0 Feb 11 15:10 00:s:0003	52	drwxr-xr-x 3 root root 0 Feb 11 15:10 00:s:0003
49	drwxr-xr-x 3 root root 0 Feb 11 15:10 00:s:0005	53	drwxr-xr-x 3 root root 0 Feb 11 15:10 00:s:0005
50	lrwxrwxrwx 1 root root 0 Feb 11 15:11 device -> ../../../0000:01:00.0	54	lrwxrwxrwx 1 root root 0 Feb 11 15:11 device -> ../../../0000:01:00.0
51	-r--r--r-- 1 root root 4096 Feb 11 15:11 port_destid	55	-r--r--r-- 1 root root 4096 Feb 11 15:11 port_destid
52	drwxr-xr-x 2 root root 0 Feb 11 15:11 power	56	drwxr-xr-x 2 root root 0 Feb 11 15:11 power
53	lrwxrwxrwx 1 root root 0 Feb 11 15:04 subsystem -> ../../../../../../class/rapidio_port	57	lrwxrwxrwx 1 root root 0 Feb 11 15:04 subsystem -> ../../../../../../class/rapidio_port
54	-r--r--r-- 1 root root 4096 Feb 11 15:11 sys_size	58	-r--r--r-- 1 root root 4096 Feb 11 15:11 sys_size
55	-rw-r--r-- 1 root root 4096 Feb 11 15:04 uevent	59	-rw-r--r-- 1 root root 4096 Feb 11 15:04 uevent

@@ -21,15 +21,22 @@ KernelVersion: 2.6.36 · 20 unmodified lines
21	Contact: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>	21	Contact: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
22	Description:	22	Description:
23	Reading this file returns a list of available protocols,	23	Reading this file returns a list of available protocols,
24	something like:	24	something like::
		25
25	"rc5 [rc6] nec jvc [sony]"	26	"rc5 [rc6] nec jvc [sony]"
		27
26	Enabled protocols are shown in [] brackets.	28	Enabled protocols are shown in [] brackets.
		29
27	Writing "+proto" will add a protocol to the list of enabled	30	Writing "+proto" will add a protocol to the list of enabled
28	protocols.	31	protocols.
		32
29	Writing "-proto" will remove a protocol from the list of enabled	33	Writing "-proto" will remove a protocol from the list of enabled
30	protocols.	34	protocols.
		35
31	Writing "proto" will enable only "proto".	36	Writing "proto" will enable only "proto".
		37
32	Writing "none" will disable all protocols.	38	Writing "none" will disable all protocols.
		39
33	Write fails with EINVAL if an invalid protocol combination or	40	Write fails with EINVAL if an invalid protocol combination or
34	unknown protocol name is used.	41	unknown protocol name is used.
35		42
@@ -39,11 +46,13 @@ KernelVersion: 3.15 · 3 unmodified lines
39	Contact: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>	46	Contact: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
40	Description:	47	Description:
41	Sets the scancode filter expected value.	48	Sets the scancode filter expected value.
		49
42	Use in combination with /sys/class/rc/rcN/filter_mask to set the	50	Use in combination with /sys/class/rc/rcN/filter_mask to set the
43	expected value of the bits set in the filter mask.	51	expected value of the bits set in the filter mask.
44	If the hardware supports it then scancodes which do not match	52	If the hardware supports it then scancodes which do not match
45	the filter will be ignored. Otherwise the write will fail with	53	the filter will be ignored. Otherwise the write will fail with
46	an error.	54	an error.
		55
47	This value may be reset to 0 if the current protocol is altered.	56	This value may be reset to 0 if the current protocol is altered.
48		57
49	What: /sys/class/rc/rcN/filter_mask	58	What: /sys/class/rc/rcN/filter_mask
@@ -56,9 +65,11 @@ Description: · 6 unmodified lines
56	of the scancode which should be compared against the expected	65	of the scancode which should be compared against the expected
57	value. A value of 0 disables the filter to allow all valid	66	value. A value of 0 disables the filter to allow all valid
58	scancodes to be processed.	67	scancodes to be processed.
		68
59	If the hardware supports it then scancodes which do not match	69	If the hardware supports it then scancodes which do not match
60	the filter will be ignored. Otherwise the write will fail with	70	the filter will be ignored. Otherwise the write will fail with
61	an error.	71	an error.
		72
62	This value may be reset to 0 if the current protocol is altered.	73	This value may be reset to 0 if the current protocol is altered.
63		74
64	What: /sys/class/rc/rcN/wakeup_protocols	75	What: /sys/class/rc/rcN/wakeup_protocols
@@ -67,15 +78,22 @@ KernelVersion: 4.11 · 2 unmodified lines
67	Contact: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>	78	Contact: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
68	Description:	79	Description:
69	Reading this file returns a list of available protocols to use	80	Reading this file returns a list of available protocols to use
70	for the wakeup filter, something like:	81	for the wakeup filter, something like::
		82
71	"rc-5 nec nec-x rc-6-0 rc-6-6a-24 [rc-6-6a-32] rc-6-mce"	83	"rc-5 nec nec-x rc-6-0 rc-6-6a-24 [rc-6-6a-32] rc-6-mce"
		84
72	Note that protocol variants are listed, so "nec", "sony",	85	Note that protocol variants are listed, so "nec", "sony",
73	"rc-5", "rc-6" have their different bit length encodings	86	"rc-5", "rc-6" have their different bit length encodings
74	listed if available.	87	listed if available.
		88
75	The enabled wakeup protocol is shown in [] brackets.	89	The enabled wakeup protocol is shown in [] brackets.
		90
76	Only one protocol can be selected at a time.	91	Only one protocol can be selected at a time.
		92
77	Writing "proto" will use "proto" for wakeup events.	93	Writing "proto" will use "proto" for wakeup events.
		94
78	Writing "none" will disable wakeup.	95	Writing "none" will disable wakeup.
		96
79	Write fails with EINVAL if an invalid protocol combination or	97	Write fails with EINVAL if an invalid protocol combination or
80	unknown protocol name is used, or if wakeup is not supported by	98	unknown protocol name is used, or if wakeup is not supported by
81	the hardware.	99	the hardware.
@@ -86,13 +104,17 @@ KernelVersion: 3.15 · 4 unmodified lines
86	Contact: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>	104	Contact: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
87	Description:	105	Description:
88	Sets the scancode wakeup filter expected value.	106	Sets the scancode wakeup filter expected value.
		107
89	Use in combination with /sys/class/rc/rcN/wakeup_filter_mask to	108	Use in combination with /sys/class/rc/rcN/wakeup_filter_mask to
90	set the expected value of the bits set in the wakeup filter mask	109	set the expected value of the bits set in the wakeup filter mask
91	to trigger a system wake event.	110	to trigger a system wake event.
		111
92	If the hardware supports it and wakeup_filter_mask is not 0 then	112	If the hardware supports it and wakeup_filter_mask is not 0 then
93	scancodes which match the filter will wake the system from e.g.	113	scancodes which match the filter will wake the system from e.g.
94	suspend to RAM or power off.	114	suspend to RAM or power off.
		115
95	Otherwise the write will fail with an error.	116	Otherwise the write will fail with an error.
		117
96	This value may be reset to 0 if the wakeup protocol is altered.	118	This value may be reset to 0 if the wakeup protocol is altered.
97		119
98	What: /sys/class/rc/rcN/wakeup_filter_mask	120	What: /sys/class/rc/rcN/wakeup_filter_mask
@@ -101,11 +123,15 @@ KernelVersion: 3.15 · 2 unmodified lines
101	Contact: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>	123	Contact: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
102	Description:	124	Description:
103	Sets the scancode wakeup filter mask of bits to compare.	125	Sets the scancode wakeup filter mask of bits to compare.
		126
104	Use in combination with /sys/class/rc/rcN/wakeup_filter to set	127	Use in combination with /sys/class/rc/rcN/wakeup_filter to set
105	the bits of the scancode which should be compared against the	128	the bits of the scancode which should be compared against the
106	expected value to trigger a system wake event.	129	expected value to trigger a system wake event.
		130
107	If the hardware supports it and wakeup_filter_mask is not 0 then	131	If the hardware supports it and wakeup_filter_mask is not 0 then
108	scancodes which match the filter will wake the system from e.g.	132	scancodes which match the filter will wake the system from e.g.
109	suspend to RAM or power off.	133	suspend to RAM or power off.
		134
110	Otherwise the write will fail with an error.	135	Otherwise the write will fail with an error.
		136
111	This value may be reset to 0 if the wakeup protocol is altered.	137	This value may be reset to 0 if the wakeup protocol is altered.

@@ -56,8 +56,9 @@ Description: · 55 unmodified lines
56	management) on top, which makes it match the Windows IRST (Intel	56	management) on top, which makes it match the Windows IRST (Intel
57	Rapid Storage Technology) driver settings. This setting is also	57	Rapid Storage Technology) driver settings. This setting is also
58	close to min_power, except that:	58	close to min_power, except that:
		59
59	a) It does not use host-initiated slumber mode, but it does	60	a) It does not use host-initiated slumber mode, but it does
60	allow device-initiated slumber	61	allow device-initiated slumber
61	b) It does not enable low power device sleep mode (DevSlp).	62	b) It does not enable low power device sleep mode (DevSlp).
62		63
63	What: /sys/class/scsi_host/hostX/em_message	64	What: /sys/class/scsi_host/hostX/em_message
@@ -70,8 +71,8 @@ Description: · 6 unmodified lines
70	protocol, writes and reads correspond to the LED message format	71	protocol, writes and reads correspond to the LED message format
71	as defined in the AHCI spec.	72	as defined in the AHCI spec.
72		73
73	The user must turn sw_activity (under /sys/block/*/device/) OFF	74	The user must turn sw_activity (under `/sys/block/*/device/`)
74	it they wish to control the activity LED via the em_message	75	OFF it they wish to control the activity LED via the em_message
75	file.	76	file.
76		77
77	em_message_type: (RO) Displays the current enclosure management	78	em_message_type: (RO) Displays the current enclosure management

@@ -47,16 +47,19 @@ Description: · 46 unmodified lines
47	online/offline state of the memory section. When written,	47	online/offline state of the memory section. When written,
48	root can toggle the the online/offline state of a removable	48	root can toggle the the online/offline state of a removable
49	memory section (see removable file description above)	49	memory section (see removable file description above)
50	using the following commands.	50	using the following commands::
51	# echo online > /sys/devices/system/memory/memoryX/state	51
52	# echo offline > /sys/devices/system/memory/memoryX/state	52	# echo online > /sys/devices/system/memory/memoryX/state
		53	# echo offline > /sys/devices/system/memory/memoryX/state
53		54
54	For example, if /sys/devices/system/memory/memory22/removable	55	For example, if /sys/devices/system/memory/memory22/removable
55	contains a value of 1 and	56	contains a value of 1 and
56	/sys/devices/system/memory/memory22/state contains the	57	/sys/devices/system/memory/memory22/state contains the
57	string "online" the following command can be executed by	58	string "online" the following command can be executed by
58	by root to offline that section.	59	by root to offline that section::
59	# echo offline > /sys/devices/system/memory/memory22/state	60
		61	# echo offline > /sys/devices/system/memory/memory22/state
		62
60	Users: hotplug memory remove tools	63	Users: hotplug memory remove tools
61	http://www.ibm.com/developerworks/wikis/display/LinuxP/powerpc-utils	64	http://www.ibm.com/developerworks/wikis/display/LinuxP/powerpc-utils
62		65
@@ -78,6 +81,7 @@ Description: · 15 unmodified lines
78		81
79	For example, the following symbolic link is created for	82	For example, the following symbolic link is created for
80	memory section 9 on node0:	83	memory section 9 on node0:
		84
81	/sys/devices/system/memory/memory9/node0 -> ../../node/node0	85	/sys/devices/system/memory/memory9/node0 -> ../../node/node0
82		86
83		87
@@ -90,4 +94,5 @@ Description: · 6 unmodified lines
90	points to the corresponding /sys/devices/system/memory/memoryY	94	points to the corresponding /sys/devices/system/memory/memoryY
91	memory section directory. For example, the following symbolic	95	memory section directory. For example, the following symbolic
92	link is created for memory section 9 on node0.	96	link is created for memory section 9 on node0.
		97
93	/sys/devices/system/node/node0/memory9 -> ../../memory/memory9	98	/sys/devices/system/node/node0/memory9 -> ../../memory/memory9

@@ -6,11 +6,13 @@ Description: Read/write the current state of DDR Backup Mode, which controls · 5 unmodified lines
6	if DDR power rails will be kept powered during system suspend.	6	if DDR power rails will be kept powered during system suspend.
7	("on"/"1" = enabled, "off"/"0" = disabled).	7	("on"/"1" = enabled, "off"/"0" = disabled).
8	Two types of power switches (or control signals) can be used:	8	Two types of power switches (or control signals) can be used:
		9
9	A. With a momentary power switch (or pulse signal), DDR	10	A. With a momentary power switch (or pulse signal), DDR
10	Backup Mode is enabled by default when available, as the	11	Backup Mode is enabled by default when available, as the
11	PMIC will be configured only during system suspend.	12	PMIC will be configured only during system suspend.
12	B. With a toggle power switch (or level signal), the	13	B. With a toggle power switch (or level signal), the
13	following steps must be followed exactly:	14	following steps must be followed exactly:
		15
14	1. Configure PMIC for backup mode, to change the role of	16	1. Configure PMIC for backup mode, to change the role of
15	the accessory power switch from a power switch to a	17	the accessory power switch from a power switch to a
16	wake-up switch,	18	wake-up switch,
@@ -20,8 +22,10 @@ Description: Read/write the current state of DDR Backup Mode, which controls · 3 unmodified lines
20	3. Suspend system,	22	3. Suspend system,
21	4. Switch accessory power switch on, to resume the	23	4. Switch accessory power switch on, to resume the
22	system.	24	system.
		25
23	DDR Backup Mode must be explicitly enabled by the user,	26	DDR Backup Mode must be explicitly enabled by the user,
24	to invoke step 1.	27	to invoke step 1.
		28
25	See also Documentation/devicetree/bindings/mfd/bd9571mwv.txt.	29	See also Documentation/devicetree/bindings/mfd/bd9571mwv.txt.
26	Users: User space applications for embedded boards equipped with a	30	Users: User space applications for embedded boards equipped with a
27	BD9571MWV PMIC.	31	BD9571MWV PMIC.

@@ -3,14 +3,18 @@ Date: July 2011 · 2 unmodified lines
3	Contact: linux-input@vger.kernel.org	3	Contact: linux-input@vger.kernel.org
4	Description: This controls if mouse clicks should be generated if the trackpoint is quickly pressed. How fast this press has to be	4	Description: This controls if mouse clicks should be generated if the trackpoint is quickly pressed. How fast this press has to be
5	is being controlled by press_speed.	5	is being controlled by press_speed.
		6
6	Values are 0 or 1.	7	Values are 0 or 1.
		8
7	Applies to Thinkpad USB Keyboard with TrackPoint.	9	Applies to Thinkpad USB Keyboard with TrackPoint.
8		10
9	What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/dragging	11	What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/dragging
10	Date: July 2011	12	Date: July 2011
11	Contact: linux-input@vger.kernel.org	13	Contact: linux-input@vger.kernel.org
12	Description: If this setting is enabled, it is possible to do dragging by pressing the trackpoint. This requires press_to_select to be enabled.	14	Description: If this setting is enabled, it is possible to do dragging by pressing the trackpoint. This requires press_to_select to be enabled.
		15
13	Values are 0 or 1.	16	Values are 0 or 1.
		17
14	Applies to Thinkpad USB Keyboard with TrackPoint.	18	Applies to Thinkpad USB Keyboard with TrackPoint.
15		19
16	What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/release_to_select	20	What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/release_to_select
@@ -25,7 +29,9 @@ Date: July 2011 · 8 unmodified lines
25	Contact: linux-input@vger.kernel.org	29	Contact: linux-input@vger.kernel.org
26	Description: This setting controls if the mouse click events generated by pressing the trackpoint (if press_to_select is enabled) generate	30	Description: This setting controls if the mouse click events generated by pressing the trackpoint (if press_to_select is enabled) generate
27	a left or right mouse button click.	31	a left or right mouse button click.
		32
28	Values are 0 or 1.	33	Values are 0 or 1.
		34
29	Applies to Thinkpad USB Keyboard with TrackPoint.	35	Applies to Thinkpad USB Keyboard with TrackPoint.
30		36
31	What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/sensitivity	37	What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/sensitivity
@@ -39,12 +45,16 @@ What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid- · 7 unmodified lines
39	Date: July 2011	45	Date: July 2011
40	Contact: linux-input@vger.kernel.org	46	Contact: linux-input@vger.kernel.org
41	Description: This setting controls how fast the trackpoint needs to be pressed to generate a mouse click if press_to_select is enabled.	47	Description: This setting controls how fast the trackpoint needs to be pressed to generate a mouse click if press_to_select is enabled.
		48
42	Values are decimal integers from 1 (slowest) to 255 (fastest).	49	Values are decimal integers from 1 (slowest) to 255 (fastest).
		50
43	Applies to Thinkpad USB Keyboard with TrackPoint.	51	Applies to Thinkpad USB Keyboard with TrackPoint.
44		52
45	What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/fn_lock	53	What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/fn_lock
46	Date: July 2014	54	Date: July 2014
47	Contact: linux-input@vger.kernel.org	55	Contact: linux-input@vger.kernel.org
48	Description: This setting controls whether Fn Lock is enabled on the keyboard (i.e. if F1 is Mute or F1)	56	Description: This setting controls whether Fn Lock is enabled on the keyboard (i.e. if F1 is Mute or F1)
		57
49	Values are 0 or 1	58	Values are 0 or 1
		59
50	Applies to ThinkPad Compact (USB\|Bluetooth) Keyboard with TrackPoint.	60	Applies to ThinkPad Compact (USB\|Bluetooth) Keyboard with TrackPoint.

@@ -5,7 +5,7 @@ Description: · 4 unmodified lines
5	The /sys/firmware/sgi_uv directory contains information	5	The /sys/firmware/sgi_uv directory contains information
6	about the SGI UV platform.	6	about the SGI UV platform.
7		7
8	Under that directory are a number of files:	8	Under that directory are a number of files::
9		9
10	partition_id	10	partition_id
11	coherence_id	11	coherence_id
@@ -14,7 +14,7 @@ Description: · 2 unmodified lines
14	SGI UV systems can be partitioned into multiple physical	14	SGI UV systems can be partitioned into multiple physical
15	machines, which each partition running a unique copy	15	machines, which each partition running a unique copy
16	of the operating system. Each partition will have a unique	16	of the operating system. Each partition will have a unique
17	partition id. To display the partition id, use the command:	17	partition id. To display the partition id, use the command::
18		18
19	cat /sys/firmware/sgi_uv/partition_id	19	cat /sys/firmware/sgi_uv/partition_id
20		20
@@ -22,6 +22,6 @@ Description: · 1 unmodified line
22	A partitioned SGI UV system can have one or more coherence	22	A partitioned SGI UV system can have one or more coherence
23	domain. The coherence id indicates which coherence domain	23	domain. The coherence id indicates which coherence domain
24	this partition is in. To display the coherence id, use the	24	this partition is in. To display the coherence id, use the
25	command:	25	command::
26		26
27	cat /sys/firmware/sgi_uv/coherence_id	27	cat /sys/firmware/sgi_uv/coherence_id

@@ -346,6 +346,7 @@ Description: · 345 unmodified lines
346	number of objects per slab. If a slab cannot be allocated	346	number of objects per slab. If a slab cannot be allocated
347	because of fragmentation, SLUB will retry with the minimum order	347	because of fragmentation, SLUB will retry with the minimum order
348	possible depending on its characteristics.	348	possible depending on its characteristics.
		349
349	When debug_guardpage_minorder=N (N > 0) parameter is specified	350	When debug_guardpage_minorder=N (N > 0) parameter is specified
350	(see Documentation/admin-guide/kernel-parameters.rst), the minimum possible	351	(see Documentation/admin-guide/kernel-parameters.rst), the minimum possible
351	order is used and this sysfs entry can not be used to change	352	order is used and this sysfs entry can not be used to change
@@ -361,6 +362,7 @@ Description: · 9 unmodified lines
361	new slab has not been possible at the cache's order and instead	362	new slab has not been possible at the cache's order and instead
362	fallen back to its minimum possible order. It can be written to	363	fallen back to its minimum possible order. It can be written to
363	clear the current count.	364	clear the current count.
		365
364	Available when CONFIG_SLUB_STATS is enabled.	366	Available when CONFIG_SLUB_STATS is enabled.
365		367
366	What: /sys/kernel/slab/cache/partial	368	What: /sys/kernel/slab/cache/partial
@@ -410,6 +412,7 @@ Description: · 43 unmodified lines
410	slab from a remote node as opposed to allocating a new slab on	412	slab from a remote node as opposed to allocating a new slab on
411	the local node. This reduces the amount of wasted memory over	413	the local node. This reduces the amount of wasted memory over
412	the entire system but can be expensive.	414	the entire system but can be expensive.
		415
413	Available when CONFIG_NUMA is enabled.	416	Available when CONFIG_NUMA is enabled.
414		417
415	What: /sys/kernel/slab/cache/sanity_checks	418	What: /sys/kernel/slab/cache/sanity_checks

@@ -34,9 +34,12 @@ Description: · 33 unmodified lines
34	this file. To disable a trigger, write its name preceded	34	this file. To disable a trigger, write its name preceded
35	by '-' instead.	35	by '-' instead.
36		36
37	For example, to enable the keyboard as trigger run:	37	For example, to enable the keyboard as trigger run::
		38
38	echo +keyboard > /sys/class/leds/dell::kbd_backlight/start_triggers	39	echo +keyboard > /sys/class/leds/dell::kbd_backlight/start_triggers
39	To disable it:	40
		41	To disable it::
		42
40	echo -keyboard > /sys/class/leds/dell::kbd_backlight/start_triggers	43	echo -keyboard > /sys/class/leds/dell::kbd_backlight/start_triggers
41		44
42	Note that not all the available triggers can be configured.	45	Note that not all the available triggers can be configured.
@@ -57,7 +60,8 @@ Description: · 14 unmodified lines
57	with any the above units. If no unit is specified, the value	60	with any the above units. If no unit is specified, the value
58	is assumed to be expressed in seconds.	61	is assumed to be expressed in seconds.
59		62
60	For example, to set the timeout to 10 minutes run:	63	For example, to set the timeout to 10 minutes run::
		64
61	echo 10m > /sys/class/leds/dell::kbd_backlight/stop_timeout	65	echo 10m > /sys/class/leds/dell::kbd_backlight/stop_timeout
62		66
63	Note that when this file is read, the returned value might be	67	Note that when this file is read, the returned value might be

@@ -47,14 +47,18 @@ Description: · 46 unmodified lines
47	suspend-to-disk mechanism. Reading from this file returns	47	suspend-to-disk mechanism. Reading from this file returns
48	the name of the method by which the system will be put to	48	the name of the method by which the system will be put to
49	sleep on the next suspend. There are four methods supported:	49	sleep on the next suspend. There are four methods supported:
		50
50	'firmware' - means that the memory image will be saved to disk	51	'firmware' - means that the memory image will be saved to disk
51	by some firmware, in which case we also assume that the	52	by some firmware, in which case we also assume that the
52	firmware will handle the system suspend.	53	firmware will handle the system suspend.
		54
53	'platform' - the memory image will be saved by the kernel and	55	'platform' - the memory image will be saved by the kernel and
54	the system will be put to sleep by the platform driver (e.g.	56	the system will be put to sleep by the platform driver (e.g.
55	ACPI or other PM registers).	57	ACPI or other PM registers).
		58
56	'shutdown' - the memory image will be saved by the kernel and	59	'shutdown' - the memory image will be saved by the kernel and
57	the system will be powered off.	60	the system will be powered off.
		61
58	'reboot' - the memory image will be saved by the kernel and	62	'reboot' - the memory image will be saved by the kernel and
59	the system will be rebooted.	63	the system will be rebooted.
60		64
@@ -74,12 +78,12 @@ Description: · 13 unmodified lines
74	The suspend-to-disk method may be chosen by writing to this	78	The suspend-to-disk method may be chosen by writing to this
75	file one of the accepted strings:	79	file one of the accepted strings:
76		80
77	'firmware'	81	- 'firmware'
78	'platform'	82	- 'platform'
79	'shutdown'	83	- 'shutdown'
80	'reboot'	84	- 'reboot'
81	'testproc'	85	- 'testproc'
82	'test'	86	- 'test'
83		87
84	It will only change to 'firmware' or 'platform' if the system	88	It will only change to 'firmware' or 'platform' if the system
85	supports that.	89	supports that.
@@ -114,9 +118,9 @@ Description: · 28 unmodified lines
114	string representing a nonzero integer into it.	118	string representing a nonzero integer into it.
115		119
116	To use this debugging feature you should attempt to suspend	120	To use this debugging feature you should attempt to suspend
117	the machine, then reboot it and run	121	the machine, then reboot it and run::
118		122
119	dmesg -s 1000000 \| grep 'hash matches'	123	dmesg -s 1000000 \| grep 'hash matches'
120		124
121	If you do not get any matches (or they appear to be false	125	If you do not get any matches (or they appear to be false
122	positives), it is possible that the last PM event point	126	positives), it is possible that the last PM event point
@@ -244,6 +248,7 @@ Description: · 121 unmodified lines
244	wakeup sources created with the help of /sys/power/wake_lock.	248	wakeup sources created with the help of /sys/power/wake_lock.
245	When a string is written to /sys/power/wake_unlock, it will be	249	When a string is written to /sys/power/wake_unlock, it will be
246	assumed to represent the name of a wakeup source to deactivate.	250	assumed to represent the name of a wakeup source to deactivate.
		251
247	If a wakeup source object of that name exists and is active at	252	If a wakeup source object of that name exists and is active at
248	the moment, it will be deactivated.	253	the moment, it will be deactivated.
249		254

@@ -20,6 +20,7 @@ This driver implements support for Monolithic Power Systems, Inc. (MPS) · 19 unmodified lines
20	vendor dual-loop, digital, multi-phase controller MP2975.	20	vendor dual-loop, digital, multi-phase controller MP2975.
21		21
22	This device:	22	This device:
		23
23	- Supports up to two power rail.	24	- Supports up to two power rail.
24	- Provides 8 pulse-width modulations (PWMs), and can be configured up	25	- Provides 8 pulse-width modulations (PWMs), and can be configured up
25	to 8-phase operation for rail 1 and up to 4-phase operation for rail	26	to 8-phase operation for rail 1 and up to 4-phase operation for rail
@@ -32,10 +33,12 @@ This device: · 6 unmodified lines
32	10-mV DAC, IMVP9 mode with 5-mV DAC.	33	10-mV DAC, IMVP9 mode with 5-mV DAC.
33		34
34	Device supports:	35	Device supports:
		36
35	- SVID interface.	37	- SVID interface.
36	- AVSBus interface.	38	- AVSBus interface.
37		39
38	Device complaint with:	40	Device complaint with:
		41
39	- PMBus rev 1.3 interface.	42	- PMBus rev 1.3 interface.
40		43
41	Device supports direct format for reading output current, output voltage,	44	Device supports direct format for reading output current, output voltage,
@@ -45,11 +48,14 @@ Device supports VID and direct formats for reading output voltage. · 3 unmodified lines
45	The below VID modes are supported: VR12, VR13, IMVP9.	48	The below VID modes are supported: VR12, VR13, IMVP9.
46		49
47	The driver provides the next attributes for the current:	50	The driver provides the next attributes for the current:
		51
48	- for current in: input, maximum alarm;	52	- for current in: input, maximum alarm;
49	- for current out input, maximum alarm and highest values;	53	- for current out input, maximum alarm and highest values;
50	- for phase current: input and label.	54	- for phase current: input and label.
51	attributes.	55	attributes.
		56
52	The driver exports the following attributes via the 'sysfs' files, where	57	The driver exports the following attributes via the 'sysfs' files, where
		58
53	- 'n' is number of telemetry pages (from 1 to 2);	59	- 'n' is number of telemetry pages (from 1 to 2);
54	- 'k' is number of configured phases (from 1 to 8);	60	- 'k' is number of configured phases (from 1 to 8);
55	- indexes 1, 1*n for "iin";	61	- indexes 1, 1*n for "iin";
@@ -65,11 +71,14 @@ The driver exports the following attributes via the 'sysfs' files, where · 9 unmodified lines
65	curr[1-{2n+k}]_label	71	curr[1-{2n+k}]_label
66		72
67	The driver provides the next attributes for the voltage:	73	The driver provides the next attributes for the voltage:
		74
68	- for voltage in: input, high critical threshold, high critical alarm, all only	75	- for voltage in: input, high critical threshold, high critical alarm, all only
69	from page 0;	76	from page 0;
70	- for voltage out: input, low and high critical thresholds, low and high	77	- for voltage out: input, low and high critical thresholds, low and high
71	critical alarms, from pages 0 and 1;	78	critical alarms, from pages 0 and 1;
		79
72	The driver exports the following attributes via the 'sysfs' files, where	80	The driver exports the following attributes via the 'sysfs' files, where
		81
73	- 'n' is number of telemetry pages (from 1 to 2);	82	- 'n' is number of telemetry pages (from 1 to 2);
74	- indexes 1 for "iin";	83	- indexes 1 for "iin";
75	- indexes n+1, n+2 for "vout";	84	- indexes n+1, n+2 for "vout";
@@ -87,9 +96,12 @@ The driver exports the following attributes via the 'sysfs' files, where · 11 unmodified lines
87	in[2-{n+1}1_lcrit_alarm	96	in[2-{n+1}1_lcrit_alarm
88		97
89	The driver provides the next attributes for the power:	98	The driver provides the next attributes for the power:
		99
90	- for power in alarm and input.	100	- for power in alarm and input.
91	- for power out: highest and input.	101	- for power out: highest and input.
		102
92	The driver exports the following attributes via the 'sysfs' files, where	103	The driver exports the following attributes via the 'sysfs' files, where
		104
93	- 'n' is number of telemetry pages (from 1 to 2);	105	- 'n' is number of telemetry pages (from 1 to 2);
94	- indexes 1 for "pin";	106	- indexes 1 for "pin";
95	- indexes n+1, n+2 for "pout";	107	- indexes n+1, n+2 for "pout";