Skip to content

Commit f0718d7

Browse files
author
Ingo Molnar
committed
Merge branch 'linus' into perf/urgent, to pick up fixes
Signed-off-by: Ingo Molnar <mingo@kernel.org>
2 parents efe8eaf + b59dfda commit f0718d7

File tree

4,923 files changed

+250353
-126663
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

4,923 files changed

+250353
-126663
lines changed

‎Documentation/00-INDEX

Lines changed: 0 additions & 428 deletions
This file was deleted.

‎Documentation/ABI/stable/sysfs-driver-usb-usbtmc

Lines changed: 0 additions & 35 deletions
Original file line numberDiff line numberDiff line change
@@ -25,38 +25,3 @@ Description:
2525
4.2.2.
2626

2727
The files are read only.
28-
29-
30-
What: /sys/bus/usb/drivers/usbtmc/*/TermChar
31-
Date: August 2008
32-
Contact: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
33-
Description:
34-
This file is the TermChar value to be sent to the USB TMC
35-
device as described by the document, "Universal Serial Bus Test
36-
and Measurement Class Specification
37-
(USBTMC) Revision 1.0" as published by the USB-IF.
38-
39-
Note that the TermCharEnabled file determines if this value is
40-
sent to the device or not.
41-
42-
43-
What: /sys/bus/usb/drivers/usbtmc/*/TermCharEnabled
44-
Date: August 2008
45-
Contact: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
46-
Description:
47-
This file determines if the TermChar is to be sent to the
48-
device on every transaction or not. For more details about
49-
this, please see the document, "Universal Serial Bus Test and
50-
Measurement Class Specification (USBTMC) Revision 1.0" as
51-
published by the USB-IF.
52-
53-
54-
What: /sys/bus/usb/drivers/usbtmc/*/auto_abort
55-
Date: August 2008
56-
Contact: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
57-
Description:
58-
This file determines if the transaction of the USB TMC
59-
device is to be automatically aborted if there is any error.
60-
For more details about this, please see the document,
61-
"Universal Serial Bus Test and Measurement Class Specification
62-
(USBTMC) Revision 1.0" as published by the USB-IF.

‎Documentation/ABI/testing/configfs-stp-policy-p_sys-t

Lines changed: 41 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,41 @@
1+
What: /config/stp-policy/<device>:p_sys-t.<policy>/<node>/uuid
2+
Date: June 2018
3+
KernelVersion: 4.19
4+
Description:
5+
UUID source identifier string, RW.
6+
Default value is randomly generated at the mkdir <node> time.
7+
Data coming from trace sources that use this <node> will be
8+
tagged with this UUID in the MIPI SyS-T packet stream, to
9+
allow the decoder to discern between different sources
10+
within the same master/channel range, and identify the
11+
higher level decoders that may be needed for each source.
12+
13+
What: /config/stp-policy/<device>:p_sys-t.<policy>/<node>/do_len
14+
Date: June 2018
15+
KernelVersion: 4.19
16+
Description:
17+
Include payload length in the MIPI SyS-T header, boolean.
18+
If enabled, the SyS-T protocol encoder will include payload
19+
length in each packet's metadata. This is normally redundant
20+
if the underlying transport protocol supports marking message
21+
boundaries (which STP does), so this is off by default.
22+
23+
What: /config/stp-policy/<device>:p_sys-t.<policy>/<node>/ts_interval
24+
Date: June 2018
25+
KernelVersion: 4.19
26+
Description:
27+
Time interval in milliseconds. Include a timestamp in the
28+
MIPI SyS-T packet metadata, if this many milliseconds have
29+
passed since the previous packet from this source. Zero is
30+
the default and stands for "never send the timestamp".
31+
32+
What: /config/stp-policy/<device>:p_sys-t.<policy>/<node>/clocksync_interval
33+
Date: June 2018
34+
KernelVersion: 4.19
35+
Description:
36+
Time interval in milliseconds. Send a CLOCKSYNC packet if
37+
this many milliseconds have passed since the previous
38+
CLOCKSYNC packet from this source. Zero is the default and
39+
stands for "never send the CLOCKSYNC". It makes sense to
40+
use this option with sources that generate constant and/or
41+
periodic data, like stm_heartbeat.

‎Documentation/ABI/testing/configfs-usb-gadget-uvc

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,10 @@ Date: Dec 2014
1212
KernelVersion: 4.0
1313
Description: Control descriptors
1414

15+
All attributes read only:
16+
bInterfaceNumber - USB interface number for this
17+
streaming interface
18+
1519
What: /config/usb-gadget/gadget/functions/uvc.name/control/class
1620
Date: Dec 2014
1721
KernelVersion: 4.0
@@ -109,6 +113,10 @@ Date: Dec 2014
109113
KernelVersion: 4.0
110114
Description: Streaming descriptors
111115

116+
All attributes read only:
117+
bInterfaceNumber - USB interface number for this
118+
streaming interface
119+
112120
What: /config/usb-gadget/gadget/functions/uvc.name/streaming/class
113121
Date: Dec 2014
114122
KernelVersion: 4.0
@@ -160,6 +168,10 @@ Description: Specific MJPEG format descriptors
160168

161169
All attributes read only,
162170
except bmaControls and bDefaultFrameIndex:
171+
bFormatIndex - unique id for this format descriptor;
172+
only defined after parent header is
173+
linked into the streaming class;
174+
read-only
163175
bmaControls - this format's data for bmaControls in
164176
the streaming header
165177
bmInterfaceFlags - specifies interlace information,
@@ -177,6 +189,10 @@ Date: Dec 2014
177189
KernelVersion: 4.0
178190
Description: Specific MJPEG frame descriptors
179191

192+
bFrameIndex - unique id for this framedescriptor;
193+
only defined after parent format is
194+
linked into the streaming header;
195+
read-only
180196
dwFrameInterval - indicates how frame interval can be
181197
programmed; a number of values
182198
separated by newline can be specified
@@ -204,6 +220,10 @@ Date: Dec 2014
204220
KernelVersion: 4.0
205221
Description: Specific uncompressed format descriptors
206222

223+
bFormatIndex - unique id for this format descriptor;
224+
only defined after parent header is
225+
linked into the streaming class;
226+
read-only
207227
bmaControls - this format's data for bmaControls in
208228
the streaming header
209229
bmInterfaceFlags - specifies interlace information,
@@ -224,6 +244,10 @@ Date: Dec 2014
224244
KernelVersion: 4.0
225245
Description: Specific uncompressed frame descriptors
226246

247+
bFrameIndex - unique id for this framedescriptor;
248+
only defined after parent format is
249+
linked into the streaming header;
250+
read-only
227251
dwFrameInterval - indicates how frame interval can be
228252
programmed; a number of values
229253
separated by newline can be specified

‎Documentation/ABI/testing/sysfs-bus-pci

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -323,3 +323,27 @@ Description:
323323

324324
This is similar to /sys/bus/pci/drivers_autoprobe, but
325325
affects only the VFs associated with a specific PF.
326+
327+
What: /sys/bus/pci/devices/.../p2pmem/size
328+
Date: November 2017
329+
Contact: Logan Gunthorpe <logang@deltatee.com>
330+
Description:
331+
If the device has any Peer-to-Peer memory registered, this
332+
file contains the total amount of memory that the device
333+
provides (in decimal).
334+
335+
What: /sys/bus/pci/devices/.../p2pmem/available
336+
Date: November 2017
337+
Contact: Logan Gunthorpe <logang@deltatee.com>
338+
Description:
339+
If the device has any Peer-to-Peer memory registered, this
340+
file contains the amount of memory that has not been
341+
allocated (in decimal).
342+
343+
What: /sys/bus/pci/devices/.../p2pmem/published
344+
Date: November 2017
345+
Contact: Logan Gunthorpe <logang@deltatee.com>
346+
Description:
347+
If the device has any Peer-to-Peer memory registered, this
348+
file contains a '1' if the memory has been published for
349+
use outside the driver that owns the device.

‎Documentation/ABI/testing/sysfs-bus-usb

Lines changed: 18 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -189,6 +189,16 @@ Description:
189189
The file will read "hotplug", "wired" and "not used" if the
190190
information is available, and "unknown" otherwise.
191191

192+
What: /sys/bus/usb/devices/.../(hub interface)/portX/location
193+
Date: October 2018
194+
Contact: Bjørn Mork <bjorn@mork.no>
195+
Description:
196+
Some platforms provide usb port physical location through
197+
firmware. This is used by the kernel to pair up logical ports
198+
mapping to the same physical connector. The attribute exposes the
199+
raw location value as a hex integer.
200+
201+
192202
What: /sys/bus/usb/devices/.../(hub interface)/portX/quirks
193203
Date: May 2018
194204
Contact: Nicolas Boichat <drinkcat@chromium.org>
@@ -219,7 +229,14 @@ Description:
219229
ports and report them to the kernel. This attribute is to expose
220230
the number of over-current situation occurred on a specific port
221231
to user space. This file will contain an unsigned 32 bit value
222-
which wraps to 0 after its maximum is reached.
232+
which wraps to 0 after its maximum is reached. This file supports
233+
poll() for monitoring changes to this value in user space.
234+
235+
Any time this value changes the corresponding hub device will send a
236+
udev event with the following attributes:
237+
238+
OVER_CURRENT_PORT=/sys/bus/usb/devices/.../(hub interface)/portX
239+
OVER_CURRENT_COUNT=[current value of this sysfs attribute]
223240

224241
What: /sys/bus/usb/devices/.../(hub interface)/portX/usb3_lpm_permit
225242
Date: November 2015

‎Documentation/ABI/testing/sysfs-bus-vmbus

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
What: /sys/bus/vmbus/devices/.../driver_override
2+
Date: August 2019
3+
Contact: Stephen Hemminger <sthemmin@microsoft.com>
4+
Description:
5+
This file allows the driver for a device to be specified which
6+
will override standard static and dynamic ID matching. When
7+
specified, only a driver with a name matching the value written
8+
to driver_override will have an opportunity to bind to the
9+
device. The override is specified by writing a string to the
10+
driver_override file (echo uio_hv_generic > driver_override) and
11+
may be cleared with an empty string (echo > driver_override).
12+
This returns the device to standard matching rules binding.
13+
Writing to driver_override does not automatically unbind the
14+
device from its current driver or make any attempt to
15+
automatically load the specified driver. If no driver with a
16+
matching name is currently loaded in the kernel, the device
17+
will not bind to any driver. This also allows devices to
18+
opt-out of driver binding using a driver_override name such as
19+
"none". Only a single driver may be specified in the override,
20+
there is no support for parsing delimiters.
21+

‎Documentation/ABI/testing/sysfs-class-lcd-s6e63m0

Lines changed: 0 additions & 27 deletions
This file was deleted.

‎Documentation/ABI/testing/sysfs-class-net

Lines changed: 20 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -91,6 +91,24 @@ Description:
9191
stacked (e.g: VLAN interfaces) but still have the same MAC
9292
address as their parent device.
9393

94+
What: /sys/class/net/<iface>/dev_port
95+
Date: February 2014
96+
KernelVersion: 3.15
97+
Contact: netdev@vger.kernel.org
98+
Description:
99+
Indicates the port number of this network device, formatted
100+
as a decimal value. Some NICs have multiple independent ports
101+
on the same PCI bus, device and function. This attribute allows
102+
userspace to distinguish the respective interfaces.
103+
104+
Note: some device drivers started to use 'dev_id' for this
105+
purpose since long before 3.15 and have not adopted the new
106+
attribute ever since. To query the port number, some tools look
107+
exclusively at 'dev_port', while others only consult 'dev_id'.
108+
If a network device has multiple client adapter ports as
109+
described in the previous paragraph and does not set this
110+
attribute to its port number, it's a kernel bug.
111+
94112
What: /sys/class/net/<iface>/dormant
95113
Date: March 2006
96114
KernelVersion: 2.6.17
@@ -117,7 +135,7 @@ Description:
117135
full: full duplex
118136

119137
Note: This attribute is only valid for interfaces that implement
120-
the ethtool get_settings method (mostly Ethernet).
138+
the ethtool get_link_ksettings method (mostly Ethernet).
121139

122140
What: /sys/class/net/<iface>/flags
123141
Date: April 2005
@@ -224,7 +242,7 @@ Description:
224242
an integer representing the link speed in Mbits/sec.
225243

226244
Note: this attribute is only valid for interfaces that implement
227-
the ethtool get_settings method (mostly Ethernet ).
245+
the ethtool get_link_ksettings method (mostly Ethernet).
228246

229247
What: /sys/class/net/<iface>/tx_queue_len
230248
Date: April 2005

‎Documentation/ABI/testing/sysfs-class-net-dsa

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
What: /sys/class/net/<iface>/tagging
2+
Date: August 2018
3+
KernelVersion: 4.20
4+
Contact: netdev@vger.kernel.org
5+
Description:
6+
String indicating the type of tagging protocol used by the
7+
DSA slave network device.

‎Documentation/ABI/testing/sysfs-fs-f2fs

Lines changed: 16 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -121,7 +121,22 @@ What: /sys/fs/f2fs/<disk>/idle_interval
121121
Date: January 2016
122122
Contact: "Jaegeuk Kim" <jaegeuk@kernel.org>
123123
Description:
124-
Controls the idle timing.
124+
Controls the idle timing for all paths other than
125+
discard and gc path.
126+
127+
What: /sys/fs/f2fs/<disk>/discard_idle_interval
128+
Date: September 2018
129+
Contact: "Chao Yu" <yuchao0@huawei.com>
130+
Contact: "Sahitya Tummala" <stummala@codeaurora.org>
131+
Description:
132+
Controls the idle timing for discard path.
133+
134+
What: /sys/fs/f2fs/<disk>/gc_idle_interval
135+
Date: September 2018
136+
Contact: "Chao Yu" <yuchao0@huawei.com>
137+
Contact: "Sahitya Tummala" <stummala@codeaurora.org>
138+
Description:
139+
Controls the idle timing for gc path.
125140

126141
What: /sys/fs/f2fs/<disk>/iostat_enable
127142
Date: August 2017

‎Documentation/PCI/00-INDEX

Lines changed: 0 additions & 26 deletions
This file was deleted.

‎Documentation/PCI/endpoint/pci-test-howto.txt

Lines changed: 11 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -99,17 +99,20 @@ Note that the devices listed here correspond to the value populated in 1.4 above
9999
2.2 Using Endpoint Test function Device
100100

101101
pcitest.sh added in tools/pci/ can be used to run all the default PCI endpoint
102-
tests. Before pcitest.sh can be used pcitest.c should be compiled using the
103-
following commands.
102+
tests. To compile this tool the following commands should be used:
104103

105-
cd <kernel-dir>
106-
make headers_install ARCH=arm
107-
arm-linux-gnueabihf-gcc -Iusr/include tools/pci/pcitest.c -o pcitest
108-
cp pcitest <rootfs>/usr/sbin/
109-
cp tools/pci/pcitest.sh <rootfs>
104+
# cd <kernel-dir>
105+
# make -C tools/pci
106+
107+
or if you desire to compile and install in your system:
108+
109+
# cd <kernel-dir>
110+
# make -C tools/pci install
111+
112+
The tool and script will be located in <rootfs>/usr/bin/
110113

111114
2.2.1 pcitest.sh Output
112-
# ./pcitest.sh
115+
# pcitest.sh
113116
BAR tests
114117

115118
BAR0: OKAY

0 commit comments

Comments
 (0)