Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings
forked fromtorvalds/linux

Commit6dee6ae

Browse files
committed
Merge tag 'irqchip-4.16-2' of git://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms into irq/urgent
Pull irqchip updates for 4.16-rc2 from Marc Zyngier - A MIPS GIC fix for spurious, masked interrupts - A fix for a subtle IPI bug in GICv3 - Do not probe GICv3 ITSs that are marked as disabled - Multi-MSI support for GICv2m - Various cleanups
2 parents1beaeac +0b24a0b commit6dee6ae

File tree

11,407 files changed

+511166
-324972
lines changed

Some content is hidden

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

11,407 files changed

+511166
-324972
lines changed

‎.gitignore‎

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -65,6 +65,11 @@ modules.builtin
6565
#
6666
/debian/
6767

68+
#
69+
# Snap directory (make snap-pkg)
70+
#
71+
/snap/
72+
6873
#
6974
# tar directory (make tar*-pkg)
7075
#

‎Documentation/00-INDEX‎

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -228,8 +228,6 @@ isdn/
228228
- directory with info on the Linux ISDN support, and supported cards.
229229
kbuild/
230230
- directory with info about the kernel build process.
231-
kernel-doc-nano-HOWTO.txt
232-
- outdated info about kernel-doc documentation.
233231
kdump/
234232
- directory with mini HowTo on getting the crash dump code to work.
235233
doc-guide/
@@ -346,8 +344,6 @@ prctl/
346344
- directory with info on the priveledge control subsystem
347345
preempt-locking.txt
348346
- info on locking under a preemptive kernel.
349-
printk-formats.txt
350-
- how to get printk format specifiers right
351347
process/
352348
- how to work with the mainline kernel development process.
353349
pps/

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

Lines changed: 37 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -42,72 +42,93 @@ Contact:K. Y. Srinivasan <kys@microsoft.com>
4242
Description:The 16 bit vendor ID of the device
4343
Users:tools/hv/lsvmbus and user level RDMA libraries
4444

45-
What:/sys/bus/vmbus/devices/vmbus_*/channels/relid/cpu
45+
What:/sys/bus/vmbus/devices/vmbus_*/channels/NN
46+
Date:September. 2017
47+
KernelVersion:4.14
48+
Contact:Stephen Hemminger <sthemmin@microsoft.com>
49+
Description:Directory for per-channel information
50+
NN is the VMBUS relid associtated with the channel.
51+
52+
What:/sys/bus/vmbus/devices/vmbus_*/channels/NN/cpu
4653
Date:September. 2017
4754
KernelVersion:4.14
4855
Contact:Stephen Hemminger <sthemmin@microsoft.com>
4956
Description:VCPU (sub)channel is affinitized to
50-
Users:tools/hv/lsvmbus and otherdebuggig tools
57+
Users:tools/hv/lsvmbus and otherdebugging tools
5158

52-
What:/sys/bus/vmbus/devices/vmbus_*/channels/relid/cpu
59+
What:/sys/bus/vmbus/devices/vmbus_*/channels/NN/cpu
5360
Date:September. 2017
5461
KernelVersion:4.14
5562
Contact:Stephen Hemminger <sthemmin@microsoft.com>
5663
Description:VCPU (sub)channel is affinitized to
57-
Users:tools/hv/lsvmbus and otherdebuggig tools
64+
Users:tools/hv/lsvmbus and otherdebugging tools
5865

59-
What:/sys/bus/vmbus/devices/vmbus_*/channels/relid/in_mask
66+
What:/sys/bus/vmbus/devices/vmbus_*/channels/NN/in_mask
6067
Date:September. 2017
6168
KernelVersion:4.14
6269
Contact:Stephen Hemminger <sthemmin@microsoft.com>
63-
Description:Inboundchannelsignaling state
70+
Description:Host to guestchannelinterrupt mask
6471
Users:Debugging tools
6572

66-
What:/sys/bus/vmbus/devices/vmbus_*/channels/relid/latency
73+
What:/sys/bus/vmbus/devices/vmbus_*/channels/NN/latency
6774
Date:September. 2017
6875
KernelVersion:4.14
6976
Contact:Stephen Hemminger <sthemmin@microsoft.com>
7077
Description:Channel signaling latency
7178
Users:Debugging tools
7279

73-
What:/sys/bus/vmbus/devices/vmbus_*/channels/relid/out_mask
80+
What:/sys/bus/vmbus/devices/vmbus_*/channels/NN/out_mask
7481
Date:September. 2017
7582
KernelVersion:4.14
7683
Contact:Stephen Hemminger <sthemmin@microsoft.com>
77-
Description:Outboundchannelsignaling state
84+
Description:Guest to hostchannelinterrupt mask
7885
Users:Debugging tools
7986

80-
What:/sys/bus/vmbus/devices/vmbus_*/channels/relid/pending
87+
What:/sys/bus/vmbus/devices/vmbus_*/channels/NN/pending
8188
Date:September. 2017
8289
KernelVersion:4.14
8390
Contact:Stephen Hemminger <sthemmin@microsoft.com>
8491
Description:Channel interrupt pending state
8592
Users:Debugging tools
8693

87-
What:/sys/bus/vmbus/devices/vmbus_*/channels/relid/read_avail
94+
What:/sys/bus/vmbus/devices/vmbus_*/channels/NN/read_avail
8895
Date:September. 2017
8996
KernelVersion:4.14
9097
Contact:Stephen Hemminger <sthemmin@microsoft.com>
91-
Description:Bytesavailabble to read
98+
Description:Bytesavailable to read
9299
Users:Debugging tools
93100

94-
What:/sys/bus/vmbus/devices/vmbus_*/channels/relid/write_avail
101+
What:/sys/bus/vmbus/devices/vmbus_*/channels/NN/write_avail
95102
Date:September. 2017
96103
KernelVersion:4.14
97104
Contact:Stephen Hemminger <sthemmin@microsoft.com>
98-
Description:Bytesavailabble to write
105+
Description:Bytesavailable to write
99106
Users:Debugging tools
100107

101-
What:/sys/bus/vmbus/devices/vmbus_*/channels/relid/events
108+
What:/sys/bus/vmbus/devices/vmbus_*/channels/NN/events
102109
Date:September. 2017
103110
KernelVersion:4.14
104111
Contact:Stephen Hemminger <sthemmin@microsoft.com>
105112
Description:Number of times we have signaled the host
106113
Users:Debugging tools
107114

108-
What:/sys/bus/vmbus/devices/vmbus_*/channels/relid/interrupts
115+
What:/sys/bus/vmbus/devices/vmbus_*/channels/NN/interrupts
109116
Date:September. 2017
110117
KernelVersion:4.14
111118
Contact:Stephen Hemminger <sthemmin@microsoft.com>
112119
Description:Number of times we have taken an interrupt (incoming)
113120
Users:Debugging tools
121+
122+
What:/sys/bus/vmbus/devices/vmbus_*/channels/NN/subchannel_id
123+
Date:January. 2018
124+
KernelVersion:4.16
125+
Contact:Stephen Hemminger <sthemmin@microsoft.com>
126+
Description:Subchannel ID associated with VMBUS channel
127+
Users:Debugging tools and userspace drivers
128+
129+
What:/sys/bus/vmbus/devices/vmbus_*/channels/NN/monitor_id
130+
Date:January. 2018
131+
KernelVersion:4.16
132+
Contact:Stephen Hemminger <sthemmin@microsoft.com>
133+
Description:Monitor bit associated with channel
134+
Users:Debugging tools and userspace drivers
Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,33 @@
1+
What: /kvd/
2+
Date:08-Jan-2018
3+
KernelVersion:v4.16
4+
Contact:mlxsw@mellanox.com
5+
Description:The main database in the Spectrum device is a centralized
6+
KVD database used for many of the tables used to configure
7+
the chip including L2 FDB, L3 LPM, ECMP and more. The KVD
8+
is divided into two sections, the first is hash-based table
9+
and the second is a linear access table. The division
10+
between the linear and hash-based sections is static and
11+
require reload before the changes take effect.
12+
13+
What: /kvd/linear
14+
Date:08-Jan-2018
15+
KernelVersion:v4.16
16+
Contact:mlxsw@mellanox.com
17+
Description:The linear section of the KVD is managed by software as a
18+
flat memory accessed using an index.
19+
20+
What: /kvd/hash_single
21+
Date:08-Jan-2018
22+
KernelVersion:v4.16
23+
Contact:mlxsw@mellanox.com
24+
Description:The hash based section of the KVD is managed by the switch
25+
device. Used in case the key size is smaller or equal to
26+
64bit.
27+
28+
What: /kvd/hash_double
29+
Date:08-Jan-2018
30+
KernelVersion:v4.16
31+
Contact:mlxsw@mellanox.com
32+
Description:The hash based section of the KVD is managed by the switch
33+
device. Used in case the key is larger than 64 bit.

‎Documentation/ABI/testing/evm‎

Lines changed: 35 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -14,30 +14,46 @@ Description:
1414
generated either locally or remotely using an
1515
asymmetric key. These keys are loaded onto root's
1616
keyring using keyctl, and EVM is then enabled by
17-
echoing a value to <securityfs>/evm:
17+
echoing a value to <securityfs>/evm made up of the
18+
following bits:
1819

19-
1: enable HMAC validation and creation
20-
2: enable digital signature validation
21-
3: enable HMAC and digital signature validation and HMAC
22-
creation
20+
Bit Effect
21+
0 Enable HMAC validation and creation
22+
1 Enable digital signature validation
23+
2 Permit modification of EVM-protected metadata at
24+
runtime. Not supported if HMAC validation and
25+
creation is enabled.
26+
31 Disable further runtime modification of EVM policy
2327

24-
Further writes will be blocked if HMAC support is enabled or
25-
if bit 32 is set:
28+
For example:
2629

27-
echo0x80000002 ><securityfs>/evm
30+
echo1 ><securityfs>/evm
2831

29-
will enable digital signature validation and block
30-
further writes to <securityfs>/evm.
32+
will enable HMAC validation and creation
3133

32-
Until this is done, EVM can not create or validate the
33-
'security.evm' xattr, but returns INTEGRITY_UNKNOWN.
34-
Loading keys and signaling EVM should be done as early
35-
as possible. Normally this is done in the initramfs,
36-
which has already been measured as part of the trusted
37-
boot. For more information on creating and loading
38-
existing trusted/encrypted keys, refer to:
34+
echo 0x80000003 ><securityfs>/evm
3935

40-
Documentation/security/keys/trusted-encrypted.rst. Both dracut
41-
(via 97masterkey and 98integrity) and systemd (via
36+
will enable HMAC and digital signature validation and
37+
HMAC creation and disable all further modification of policy.
38+
39+
echo 0x80000006 ><securityfs>/evm
40+
41+
will enable digital signature validation, permit
42+
modification of EVM-protected metadata and
43+
disable all further modification of policy
44+
45+
Note that once a key has been loaded, it will no longer be
46+
possible to enable metadata modification.
47+
48+
Until key loading has been signaled EVM can not create
49+
or validate the 'security.evm' xattr, but returns
50+
INTEGRITY_UNKNOWN. Loading keys and signaling EVM
51+
should be done as early as possible. Normally this is
52+
done in the initramfs, which has already been measured
53+
as part of the trusted boot. For more information on
54+
creating and loading existing trusted/encrypted keys,
55+
refer to:
56+
Documentation/security/keys/trusted-encrypted.rst. Both
57+
dracut (via 97masterkey and 98integrity) and systemd (via
4258
core/ima-setup) have support for loading keys at boot
4359
time.

‎Documentation/ABI/testing/ima_policy‎

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,8 @@ Description:
1717

1818
rule format: action [condition ...]
1919

20-
action: measure | dont_measure | appraise | dont_appraise | audit
20+
action: measure | dont_measure | appraise | dont_appraise |
21+
audit | hash | dont_hash
2122
condition:= base | lsm [option]
2223
base:[[func=] [mask=] [fsmagic=] [fsuuid=] [uid=]
2324
[euid=] [fowner=]]

‎Documentation/ABI/testing/rtc-cdev‎

Lines changed: 42 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,42 @@
1+
What:/dev/rtcX
2+
Date:April 2005
3+
KernelVersion:2.6.12
4+
Contact:linux-rtc@vger.kernel.org
5+
Description:
6+
The ioctl interface to drivers for real-time clocks (RTCs).
7+
Following actions are supported:
8+
9+
* RTC_RD_TIME, RTC_SET_TIME: Read or set the RTC time. Time
10+
format is a Gregorian calendar date and 24 hour wall clock
11+
time.
12+
13+
* RTC_AIE_ON, RTC_AIE_OFF: Enable or disable the alarm interrupt
14+
for RTCs that support alarms
15+
16+
* RTC_ALM_READ, RTC_ALM_SET: Read or set the alarm time for
17+
RTCs that support alarms. Can be set upto 24 hours in the
18+
future. Requires a separate RTC_AIE_ON call to enable the
19+
alarm interrupt. (Prefer to use RTC_WKALM_*)
20+
21+
* RTC_WKALM_RD, RTC_WKALM_SET: For RTCs that support a more
22+
powerful interface, which can issue alarms beyond 24 hours and
23+
enable IRQs in the same request.
24+
25+
* RTC_PIE_ON, RTC_PIE_OFF: Enable or disable the periodic
26+
interrupt for RTCs that support periodic interrupts.
27+
28+
* RTC_UIE_ON, RTC_UIE_OFF: Enable or disable the update
29+
interrupt for RTCs that support it.
30+
31+
* RTC_IRQP_READ, RTC_IRQP_SET: Read or set the frequency for
32+
periodic interrupts for RTCs that support periodic interrupts.
33+
Requires a separate RTC_PIE_ON call to enable the periodic
34+
interrupts.
35+
36+
The ioctl() calls supported by the older /dev/rtc interface are
37+
also supported by the newer RTC class framework. However,
38+
because the chips and systems are not standardized, some PC/AT
39+
functionality might not be provided. And in the same way, some
40+
newer features -- including those enabled by ACPI -- are exposed
41+
by the RTC class framework, but can't be supported by the older
42+
driver.

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

Lines changed: 12 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ Description:
3232
Description of the physical chip / device for device X.
3333
Typically a part number.
3434

35-
What:/sys/bus/iio/devices/iio:deviceX/timestamp_clock
35+
What:/sys/bus/iio/devices/iio:deviceX/current_timestamp_clock
3636
KernelVersion:4.5
3737
Contact:linux-iio@vger.kernel.org
3838
Description:
@@ -1290,7 +1290,7 @@ KernelVersion:3.4
12901290
Contact:linux-iio@vger.kernel.org
12911291
Description:
12921292
Unit-less light intensity. Modifiers both and ir indicate
1293-
that measurementscontains visible and infrared light
1293+
that measurementscontain visible and infrared light
12941294
components or just infrared light, respectively. Modifier uv indicates
12951295
that measurements contain ultraviolet light components.
12961296

@@ -1413,6 +1413,16 @@ Description:
14131413
the available samples after the timeout expires and thus have a
14141414
maximum delay guarantee.
14151415

1416+
What:/sys/bus/iio/devices/iio:deviceX/buffer/data_available
1417+
KernelVersion: 4.16
1418+
Contact:linux-iio@vger.kernel.org
1419+
Description:
1420+
A read-only value indicating the bytes of data available in the
1421+
buffer. In the case of an output buffer, this indicates the
1422+
amount of empty space available to write data to. In the case of
1423+
an input buffer, this indicates the amount of data available for
1424+
reading.
1425+
14161426
What:/sys/bus/iio/devices/iio:deviceX/buffer/hwfifo_enabled
14171427
KernelVersion: 4.2
14181428
Contact:linux-iio@vger.kernel.org
Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
What:/sys/bus/iio/devices/iio:deviceX/in_voltage_spi_clk_freq
2+
KernelVersion:4.14
3+
Contact:arnaud.pouliquen@st.com
4+
Description:
5+
For audio purpose only.
6+
Used by audio driver to set/get the spi input frequency.
7+
This is mandatory if DFSDM is slave on SPI bus, to
8+
provide information on the SPI clock frequency during runtime
9+
Notice that the SPI frequency should be a multiple of sample
10+
frequency to ensure the precision.
11+
if DFSDM input is SPI master
12+
Reading SPI clkout frequency,
13+
error on writing
14+
If DFSDM input is SPI Slave:
15+
Reading returns value previously set.
16+
Writing value before starting conversions.
Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,25 @@
1+
What:/sys/bus/pci/drivers/xhci_hcd/.../dbc
2+
Date:June 2017
3+
Contact:Lu Baolu <baolu.lu@linux.intel.com>
4+
Description:
5+
xHCI compatible USB host controllers (i.e. super-speed
6+
USB3 controllers) are often implemented with the Debug
7+
Capability (DbC). It can present a debug device which
8+
is fully compliant with the USB framework and provides
9+
the equivalent of a very high performance full-duplex
10+
serial link for debug purpose.
11+
12+
The DbC debug device shares a root port with xHCI host.
13+
When the DbC is enabled, the root port will be assigned
14+
to the Debug Capability. Otherwise, it will be assigned
15+
to xHCI.
16+
17+
Writing "enable" to this attribute will enable the DbC
18+
functionality and the shared root port will be assigned
19+
to the DbC device. Writing "disable" to this attribute
20+
will disable the DbC functionality and the shared root
21+
port will roll back to the xHCI.
22+
23+
Reading this attribute gives the state of the DbC. It
24+
can be one of the following states: disabled, enabled,
25+
initialized, connected, configured and stalled.

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp