Skip to content

Commit f950f23

Browse files
PlaidCatPlaidCat
committed
Rebuild rocky8_8 with kernel-4.18.0-477.10.1.el8_8
Rebuild_History BUILDABLERebuilding Kernel from rpm changelog with Fuzz Limit: 87.50% Number of commits in upstream range v4.18~1..master: 488125 Number of commits in rpm: 2541 Number of commits matched with upstream: 2506 (98.62%) Number of commits in upstream but not in rpm: 485635 Number of commits NOT found in upstream: 35 (1.38%) Rebuilding Kernel on Branch rocky8_8_rebuild_kernel-4.18.0-477.10.1.el8_8 for kernel-4.18.0-477.10.1.el8_8 Clean Cherry Picks: 2008 (80.13%) Empty Cherry Picks: 462 (18.44%) _______________________________ Full Details Located here: ciq/ciq_backports/kernel-4.18.0-477.10.1.el8_8/rebuild.details.txt Includes: * git commit header above * Empty Commits with upstream SHA * RPM ChangeLog Entries that could not be matched Individual Empty Commit failures contained in the same containing directory. The git message for empty commits will have the path for the failed commit. File names are the first 8 characters of the upstream SHA
1 parent 81210fc commit f950f23

File tree

800 files changed

+23987
-14340
lines changed

Some content is hidden

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

800 files changed

+23987
-14340
lines changed

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

Lines changed: 77 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,77 @@
1+
What: /sys/class/firmware/.../data
2+
Date: July 2022
3+
KernelVersion: 5.19
4+
Contact: Russ Weight <[email protected]>
5+
Description: The data sysfs file is used for firmware-fallback and for
6+
firmware uploads. Cat a firmware image to this sysfs file
7+
after you echo 1 to the loading sysfs file. When the firmware
8+
image write is complete, echo 0 to the loading sysfs file. This
9+
sequence will signal the completion of the firmware write and
10+
signal the lower-level driver that the firmware data is
11+
available.
12+
13+
What: /sys/class/firmware/.../cancel
14+
Date: July 2022
15+
KernelVersion: 5.19
16+
Contact: Russ Weight <[email protected]>
17+
Description: Write-only. For firmware uploads, write a "1" to this file to
18+
request that the transfer of firmware data to the lower-level
19+
device be canceled. This request will be rejected (EBUSY) if
20+
the update cannot be canceled (e.g. a FLASH write is in
21+
progress) or (ENODEV) if there is no firmware update in progress.
22+
23+
What: /sys/class/firmware/.../error
24+
Date: July 2022
25+
KernelVersion: 5.19
26+
Contact: Russ Weight <[email protected]>
27+
Description: Read-only. Returns a string describing a failed firmware
28+
upload. This string will be in the form of <STATUS>:<ERROR>,
29+
where <STATUS> will be one of the status strings described
30+
for the status sysfs file and <ERROR> will be one of the
31+
following: "hw-error", "timeout", "user-abort", "device-busy",
32+
"invalid-file-size", "read-write-error", "flash-wearout". The
33+
error sysfs file is only meaningful when the current firmware
34+
upload status is "idle". If this file is read while a firmware
35+
transfer is in progress, then the read will fail with EBUSY.
36+
37+
What: /sys/class/firmware/.../loading
38+
Date: July 2022
39+
KernelVersion: 5.19
40+
Contact: Russ Weight <[email protected]>
41+
Description: The loading sysfs file is used for both firmware-fallback and
42+
for firmware uploads. Echo 1 onto the loading file to indicate
43+
you are writing a firmware file to the data sysfs node. Echo
44+
-1 onto this file to abort the data write or echo 0 onto this
45+
file to indicate that the write is complete. For firmware
46+
uploads, the zero value also triggers the transfer of the
47+
firmware data to the lower-level device driver.
48+
49+
What: /sys/class/firmware/.../remaining_size
50+
Date: July 2022
51+
KernelVersion: 5.19
52+
Contact: Russ Weight <[email protected]>
53+
Description: Read-only. For firmware upload, this file contains the size
54+
of the firmware data that remains to be transferred to the
55+
lower-level device driver. The size value is initialized to
56+
the full size of the firmware image that was previously
57+
written to the data sysfs file. This value is periodically
58+
updated during the "transferring" phase of the firmware
59+
upload.
60+
Format: "%u".
61+
62+
What: /sys/class/firmware/.../status
63+
Date: July 2022
64+
KernelVersion: 5.19
65+
Contact: Russ Weight <[email protected]>
66+
Description: Read-only. Returns a string describing the current status of
67+
a firmware upload. The string will be one of the following:
68+
idle, "receiving", "preparing", "transferring", "programming".
69+
70+
What: /sys/class/firmware/.../timeout
71+
Date: July 2022
72+
KernelVersion: 5.19
73+
Contact: Russ Weight <[email protected]>
74+
Description: This file supports the timeout mechanism for firmware
75+
fallback. This file has no affect on firmware uploads. For
76+
more information on timeouts please see the documentation
77+
for firmware fallback.

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

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -136,6 +136,14 @@ Description:
136136
- "reverse": CC2 orientation
137137
- "unknown": Orientation cannot be determined.
138138

139+
What: /sys/class/typec/<port>/select_usb_power_delivery
140+
Date: May 2022
141+
Contact: Heikki Krogerus <[email protected]>
142+
Description:
143+
Lists the USB Power Delivery Capabilities that the port can
144+
advertise to the partner. The currently used capabilities are in
145+
brackets. Selection happens by writing to the file.
146+
139147
USB Type-C partner devices (eg. /sys/class/typec/port0-partner/)
140148

141149
What: /sys/class/typec/<port>-partner/accessory_mode

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

Lines changed: 240 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,240 @@
1+
What: /sys/class/usb_power_delivery
2+
Date: May 2022
3+
Contact: Heikki Krogerus <[email protected]>
4+
Description:
5+
Directory for USB Power Delivery devices.
6+
7+
What: /sys/class/usb_power_delivery/.../revision
8+
Date: May 2022
9+
Contact: Heikki Krogerus <[email protected]>
10+
Description:
11+
File showing the USB Power Delivery Specification Revision used
12+
in communication.
13+
14+
What: /sys/class/usb_power_delivery/.../version
15+
Date: May 2022
16+
Contact: Heikki Krogerus <[email protected]>
17+
Description:
18+
This is an optional attribute file showing the version of the
19+
specific revision of the USB Power Delivery Specification. In
20+
most cases the specification version is not known and the file
21+
is not available.
22+
23+
What: /sys/class/usb_power_delivery/.../source-capabilities
24+
Date: May 2022
25+
Contact: Heikki Krogerus <[email protected]>
26+
Description:
27+
The source capabilities message "Source_Capabilities" contains a
28+
set of Power Data Objects (PDO), each representing a type of
29+
power supply. The order of the PDO objects is defined in the USB
30+
Power Delivery Specification. Each PDO - power supply - will
31+
have its own device, and the PDO device name will start with the
32+
object position number as the first character followed by the
33+
power supply type name (":" as delimiter).
34+
35+
/sys/class/usb_power_delivery/.../source_capabilities/<position>:<type>
36+
37+
What: /sys/class/usb_power_delivery/.../sink-capabilities
38+
Date: May 2022
39+
Contact: Heikki Krogerus <[email protected]>
40+
Description:
41+
The sink capability message "Sink_Capabilities" contains a set
42+
of Power Data Objects (PDO) just like with source capabilities,
43+
but instead of describing the power capabilities, these objects
44+
describe the power requirements.
45+
46+
The order of the objects in the sink capability message is the
47+
same as with the source capabilities message.
48+
49+
Fixed Supplies
50+
51+
What: /sys/class/usb_power_delivery/.../<capability>/<position>:fixed_supply
52+
Date: May 2022
53+
Contact: Heikki Krogerus <[email protected]>
54+
Description:
55+
Devices containing the attributes (the bit fields) defined for
56+
Fixed Supplies.
57+
58+
The device "1:fixed_supply" is special. USB Power Delivery
59+
Specification dictates that the first PDO (at object position
60+
1), and the only mandatory PDO, is always the vSafe5V Fixed
61+
Supply Object. vSafe5V Object has additional fields defined for
62+
it that the other Fixed Supply Objects do not have and that are
63+
related to the USB capabilities rather than power capabilities.
64+
65+
What: /sys/class/usb_power_delivery/.../<capability>/1:fixed_supply/dual_role_power
66+
Date: May 2022
67+
Contact: Heikki Krogerus <[email protected]>
68+
Description:
69+
This file contains boolean value that tells does the device
70+
support both source and sink power roles.
71+
72+
What: /sys/class/usb_power_delivery/.../<capability>/1:fixed_supply/usb_suspend_supported
73+
Date: May 2022
74+
Contact: Heikki Krogerus <[email protected]>
75+
Description:
76+
This file shows the value of the USB Suspend Supported bit in
77+
vSafe5V Fixed Supply Object. If the bit is set then the device
78+
will follow the USB 2.0 and USB 3.2 rules for suspend and
79+
resume.
80+
81+
What: /sys/class/usb_power_delivery/.../<capability>/1:fixed_supply/unconstrained_power
82+
Date: May 2022
83+
Contact: Heikki Krogerus <[email protected]>
84+
Description:
85+
This file shows the value of the Unconstrained Power bit in
86+
vSafe5V Fixed Supply Object. The bit is set when an external
87+
source of power, powerful enough to power the entire system on
88+
its own, is available for the device.
89+
90+
What: /sys/class/usb_power_delivery/.../<capability>/1:fixed_supply/usb_communication_capable
91+
Date: May 2022
92+
Contact: Heikki Krogerus <[email protected]>
93+
Description:
94+
This file shows the value of the USB Communication Capable bit in
95+
vSafe5V Fixed Supply Object.
96+
97+
What: /sys/class/usb_power_delivery/.../<capability>/1:fixed_supply/dual_role_data
98+
Date: May 2022
99+
Contact: Heikki Krogerus <[email protected]>
100+
Description:
101+
This file shows the value of the Dual-Role Data bit in vSafe5V
102+
Fixed Supply Object. Dual role data means ability act as both
103+
USB host and USB device.
104+
105+
What: /sys/class/usb_power_delivery/.../<capability>/1:fixed_supply/unchunked_extended_messages_supported
106+
Date: May 2022
107+
Contact: Heikki Krogerus <[email protected]>
108+
Description:
109+
This file shows the value of the Unchunked Extended Messages
110+
Supported bit in vSafe5V Fixed Supply Object.
111+
112+
What: /sys/class/usb_power_delivery/.../<capability>/<position>:fixed_supply/voltage
113+
Date: May 2022
114+
Contact: Heikki Krogerus <[email protected]>
115+
Description:
116+
The voltage the supply supports in millivolts.
117+
118+
What: /sys/class/usb_power_delivery/.../source-capabilities/<position>:fixed_supply/maximum_current
119+
Date: May 2022
120+
Contact: Heikki Krogerus <[email protected]>
121+
Description:
122+
Maximum current of the fixed source supply in milliamperes.
123+
124+
What: /sys/class/usb_power_delivery/.../sink-capabilities/<position>:fixed_supply/operational_current
125+
Date: May 2022
126+
Contact: Heikki Krogerus <[email protected]>
127+
Description:
128+
Operational current of the sink in milliamperes.
129+
130+
What: /sys/class/usb_power_delivery/.../sink-capabilities/<position>:fixed_supply/fast_role_swap_current
131+
Date: May 2022
132+
Contact: Heikki Krogerus <[email protected]>
133+
Description:
134+
This file contains the value of the "Fast Role Swap USB Type-C
135+
Current" field that tells the current level the sink requires
136+
after a Fast Role Swap.
137+
0 - Fast Swap not supported"
138+
1 - Default USB Power"
139+
2 - 1.5A@5V"
140+
3 - 3.0A@5V"
141+
142+
Variable Supplies
143+
144+
What: /sys/class/usb_power_delivery/.../<capability>/<position>:variable_supply
145+
Date: May 2022
146+
Contact: Heikki Krogerus <[email protected]>
147+
Description:
148+
Variable Power Supply PDO.
149+
150+
What: /sys/class/usb_power_delivery/.../<capability>/<position>:variable_supply/maximum_voltage
151+
Date: May 2022
152+
Contact: Heikki Krogerus <[email protected]>
153+
Description:
154+
Maximum Voltage in millivolts.
155+
156+
What: /sys/class/usb_power_delivery/.../<capability>/<position>:variable_supply/minimum_voltage
157+
Date: May 2022
158+
Contact: Heikki Krogerus <[email protected]>
159+
Description:
160+
Minimum Voltage in millivolts.
161+
162+
What: /sys/class/usb_power_delivery/.../source-capabilities/<position>:variable_supply/maximum_current
163+
Date: May 2022
164+
Contact: Heikki Krogerus <[email protected]>
165+
Description:
166+
The maximum current in milliamperes that the source can supply
167+
at the given Voltage range.
168+
169+
What: /sys/class/usb_power_delivery/.../sink-capabilities/<position>:variable_supply/operational_current
170+
Date: May 2022
171+
Contact: Heikki Krogerus <[email protected]>
172+
Description:
173+
The operational current in milliamperes that the sink requires
174+
at the given Voltage range.
175+
176+
Battery Supplies
177+
178+
What: /sys/class/usb_power_delivery/.../<capability>/<position>:battery
179+
Date: May 2022
180+
Contact: Heikki Krogerus <[email protected]>
181+
Description:
182+
Battery PDO.
183+
184+
What: /sys/class/usb_power_delivery/.../<capability>/<position>:battery/maximum_voltage
185+
Date: May 2022
186+
Contact: Heikki Krogerus <[email protected]>
187+
Description:
188+
Maximum Voltage in millivolts.
189+
190+
What: /sys/class/usb_power_delivery/.../<capability>/<position>:battery/minimum_voltage
191+
Date: May 2022
192+
Contact: Heikki Krogerus <[email protected]>
193+
Description:
194+
Minimum Voltage in millivolts.
195+
196+
What: /sys/class/usb_power_delivery/.../source-capabilities/<position>:battery/maximum_power
197+
Date: May 2022
198+
Contact: Heikki Krogerus <[email protected]>
199+
Description:
200+
Maximum allowable Power in milliwatts.
201+
202+
What: /sys/class/usb_power_delivery/.../sink-capabilities/<position>:battery/operational_power
203+
Date: May 2022
204+
Contact: Heikki Krogerus <[email protected]>
205+
Description:
206+
The operational power that the sink requires at the given
207+
voltage range.
208+
209+
Standard Power Range (SPR) Programmable Power Supplies
210+
211+
What: /sys/class/usb_power_delivery/.../<capability>/<position>:programmable_supply
212+
Date: May 2022
213+
Contact: Heikki Krogerus <[email protected]>
214+
Description:
215+
Programmable Power Supply (PPS) Augmented PDO (APDO).
216+
217+
What: /sys/class/usb_power_delivery/.../<capability>/<position>:programmable_supply/maximum_voltage
218+
Date: May 2022
219+
Contact: Heikki Krogerus <[email protected]>
220+
Description:
221+
Maximum Voltage in millivolts.
222+
223+
What: /sys/class/usb_power_delivery/.../<capability>/<position>:programmable_supply/minimum_voltage
224+
Date: May 2022
225+
Contact: Heikki Krogerus <[email protected]>
226+
Description:
227+
Minimum Voltage in millivolts.
228+
229+
What: /sys/class/usb_power_delivery/.../<capability>/<position>:programmable_supply/maximum_current
230+
Date: May 2022
231+
Contact: Heikki Krogerus <[email protected]>
232+
Description:
233+
Maximum Current in milliamperes.
234+
235+
What: /sys/class/usb_power_delivery/.../source-capabilities/<position>:programmable_supply/pps_power_limited
236+
Date: May 2022
237+
Contact: Heikki Krogerus <[email protected]>
238+
Description:
239+
The PPS Power Limited bit indicates whether or not the source
240+
supply will exceed the rated output power if requested.

‎Documentation/ABI/testing/sysfs-devices-mapping‎

Lines changed: 29 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
What: /sys/devices/uncore_iio_x/dieX
22
Date: February 2020
3-
Contact: Roman Sudarikov <roman.sudarikov@linux.intel.com>
3+
Contact: Alexander Antonov <alexander.antonov@linux.intel.com>
44
Description:
55
Each IIO stack (PCIe root port) has its own IIO PMON block, so
66
each dieX file (where X is die number) holds "Segment:Root Bus"
@@ -31,3 +31,31 @@ Description:
3131
IIO PMU 0 on die 1 belongs to PCI RP on bus 0x40, domain 0x0000
3232
IIO PMU 0 on die 2 belongs to PCI RP on bus 0x80, domain 0x0000
3333
IIO PMU 0 on die 3 belongs to PCI RP on bus 0xc0, domain 0x0000
34+
35+
What: /sys/devices/uncore_upi_x/dieX
36+
Date: March 2022
37+
Contact: Alexander Antonov <[email protected]>
38+
Description:
39+
Each /sys/devices/uncore_upi_X/dieY file holds "upi_Z,die_W"
40+
value that means UPI link number X on die Y is connected to UPI
41+
link Z on die W and this link between sockets can be monitored
42+
by UPI PMON block.
43+
For example, 4-die Sapphire Rapids platform has the following
44+
UPI 0 topology::
45+
46+
# tail /sys/devices/uncore_upi_0/die*
47+
==> /sys/devices/uncore_upi_0/die0 <==
48+
upi_1,die_1
49+
==> /sys/devices/uncore_upi_0/die1 <==
50+
upi_0,die_3
51+
==> /sys/devices/uncore_upi_0/die2 <==
52+
upi_1,die_3
53+
==> /sys/devices/uncore_upi_0/die3 <==
54+
upi_0,die_1
55+
56+
Which means::
57+
58+
UPI link 0 on die 0 is connected to UPI link 1 on die 1
59+
UPI link 0 on die 1 is connected to UPI link 0 on die 3
60+
UPI link 0 on die 2 is connected to UPI link 1 on die 3
61+
UPI link 0 on die 3 is connected to UPI link 0 on die 1

0 commit comments

Comments
 (0)