Skip to content

Commit ba08cf4

Browse files
committed
Merge 5.6-rc3 into tty-next
We want the tty fixes in here as well. Signed-off-by: Greg Kroah-Hartman <[email protected]>
2 parents e24cd4e + f8788d8 commit ba08cf4

File tree

756 files changed

+13239
-9765
lines changed

Some content is hidden

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

756 files changed

+13239
-9765
lines changed

COPYING

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,3 +16,5 @@ In addition, other licenses may also apply. Please see:
1616
Documentation/process/license-rules.rst
1717

1818
for more details.
19+
20+
All contributions to the Linux Kernel are subject to this COPYING file.

Documentation/arm64/memory.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -129,7 +129,7 @@ this logic.
129129

130130
As a single binary will need to support both 48-bit and 52-bit VA
131131
spaces, the VMEMMAP must be sized large enough for 52-bit VAs and
132-
also must be sized large enought to accommodate a fixed PAGE_OFFSET.
132+
also must be sized large enough to accommodate a fixed PAGE_OFFSET.
133133

134134
Most code in the kernel should not need to consider the VA_BITS, for
135135
code that does need to know the VA size the variables are

Documentation/arm64/tagged-address-abi.rst

Lines changed: 9 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -44,8 +44,15 @@ The AArch64 Tagged Address ABI has two stages of relaxation depending
4444
how the user addresses are used by the kernel:
4545

4646
1. User addresses not accessed by the kernel but used for address space
47-
management (e.g. ``mmap()``, ``mprotect()``, ``madvise()``). The use
48-
of valid tagged pointers in this context is always allowed.
47+
management (e.g. ``mprotect()``, ``madvise()``). The use of valid
48+
tagged pointers in this context is allowed with the exception of
49+
``brk()``, ``mmap()`` and the ``new_address`` argument to
50+
``mremap()`` as these have the potential to alias with existing
51+
user addresses.
52+
53+
NOTE: This behaviour changed in v5.6 and so some earlier kernels may
54+
incorrectly accept valid tagged pointers for the ``brk()``,
55+
``mmap()`` and ``mremap()`` system calls.
4956

5057
2. User addresses accessed by the kernel (e.g. ``write()``). This ABI
5158
relaxation is disabled by default and the application thread needs to

Documentation/devicetree/bindings/display/allwinner,sun4i-a10-tcon.yaml

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -43,9 +43,13 @@ properties:
4343
- enum:
4444
- allwinner,sun8i-h3-tcon-tv
4545
- allwinner,sun50i-a64-tcon-tv
46-
- allwinner,sun50i-h6-tcon-tv
4746
- const: allwinner,sun8i-a83t-tcon-tv
4847

48+
- items:
49+
- enum:
50+
- allwinner,sun50i-h6-tcon-tv
51+
- const: allwinner,sun8i-r40-tcon-tv
52+
4953
reg:
5054
maxItems: 1
5155

Documentation/devicetree/bindings/input/ilitek,ili2xxx.txt

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,10 @@
1-
Ilitek ILI210x/ILI2117/ILI251x touchscreen controller
1+
Ilitek ILI210x/ILI2117/ILI2120/ILI251x touchscreen controller
22

33
Required properties:
44
- compatible:
55
ilitek,ili210x for ILI210x
66
ilitek,ili2117 for ILI2117
7+
ilitek,ili2120 for ILI2120
78
ilitek,ili251x for ILI251x
89

910
- reg: The I2C address of the device

Documentation/devicetree/bindings/media/allwinner,sun4i-a10-csi.yaml

Lines changed: 28 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -33,24 +33,40 @@ properties:
3333
maxItems: 1
3434

3535
clocks:
36-
minItems: 2
37-
maxItems: 3
38-
items:
39-
- description: The CSI interface clock
40-
- description: The CSI ISP clock
41-
- description: The CSI DRAM clock
36+
oneOf:
37+
- items:
38+
- description: The CSI interface clock
39+
- description: The CSI DRAM clock
40+
41+
- items:
42+
- description: The CSI interface clock
43+
- description: The CSI ISP clock
44+
- description: The CSI DRAM clock
4245

4346
clock-names:
44-
minItems: 2
45-
maxItems: 3
46-
items:
47-
- const: bus
48-
- const: isp
49-
- const: ram
47+
oneOf:
48+
- items:
49+
- const: bus
50+
- const: ram
51+
52+
- items:
53+
- const: bus
54+
- const: isp
55+
- const: ram
5056

5157
resets:
5258
maxItems: 1
5359

60+
# FIXME: This should be made required eventually once every SoC will
61+
# have the MBUS declared.
62+
interconnects:
63+
maxItems: 1
64+
65+
# FIXME: This should be made required eventually once every SoC will
66+
# have the MBUS declared.
67+
interconnect-names:
68+
const: dma-mem
69+
5470
# See ./video-interfaces.txt for details
5571
port:
5672
type: object

Documentation/devicetree/bindings/memory-controllers/nvidia,tegra124-emc.yaml

Lines changed: 12 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -347,6 +347,7 @@ examples:
347347
interrupts = <GIC_SPI 77 IRQ_TYPE_LEVEL_HIGH>;
348348
349349
#iommu-cells = <1>;
350+
#reset-cells = <1>;
350351
};
351352
352353
external-memory-controller@7001b000 {
@@ -363,20 +364,23 @@ examples:
363364
timing-0 {
364365
clock-frequency = <12750000>;
365366
366-
nvidia,emc-zcal-cnt-long = <0x00000042>;
367-
nvidia,emc-auto-cal-interval = <0x001fffff>;
368-
nvidia,emc-ctt-term-ctrl = <0x00000802>;
369-
nvidia,emc-cfg = <0x73240000>;
370-
nvidia,emc-cfg-2 = <0x000008c5>;
371-
nvidia,emc-sel-dpd-ctrl = <0x00040128>;
372-
nvidia,emc-bgbias-ctl0 = <0x00000008>;
373367
nvidia,emc-auto-cal-config = <0xa1430000>;
374368
nvidia,emc-auto-cal-config2 = <0x00000000>;
375369
nvidia,emc-auto-cal-config3 = <0x00000000>;
376-
nvidia,emc-mode-reset = <0x80001221>;
370+
nvidia,emc-auto-cal-interval = <0x001fffff>;
371+
nvidia,emc-bgbias-ctl0 = <0x00000008>;
372+
nvidia,emc-cfg = <0x73240000>;
373+
nvidia,emc-cfg-2 = <0x000008c5>;
374+
nvidia,emc-ctt-term-ctrl = <0x00000802>;
377375
nvidia,emc-mode-1 = <0x80100003>;
378376
nvidia,emc-mode-2 = <0x80200008>;
379377
nvidia,emc-mode-4 = <0x00000000>;
378+
nvidia,emc-mode-reset = <0x80001221>;
379+
nvidia,emc-mrs-wait-cnt = <0x000e000e>;
380+
nvidia,emc-sel-dpd-ctrl = <0x00040128>;
381+
nvidia,emc-xm2dqspadctrl2 = <0x0130b118>;
382+
nvidia,emc-zcal-cnt-long = <0x00000042>;
383+
nvidia,emc-zcal-interval = <0x00000000>;
380384
381385
nvidia,emc-configuration = <
382386
0x00000000 /* EMC_RC */

Documentation/devicetree/bindings/mmc/ti-omap-hsmmc.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -124,7 +124,7 @@ not every application needs SDIO irq, e.g. MMC cards.
124124
pinctrl-1 = <&mmc1_idle>;
125125
pinctrl-2 = <&mmc1_sleep>;
126126
...
127-
interrupts-extended = <&intc 64 &gpio2 28 GPIO_ACTIVE_LOW>;
127+
interrupts-extended = <&intc 64 &gpio2 28 IRQ_TYPE_LEVEL_LOW>;
128128
};
129129

130130
mmc1_idle : pinmux_cirq_pin {

Documentation/devicetree/bindings/net/mdio.yaml

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -56,7 +56,6 @@ patternProperties:
5656
examples:
5757
- |
5858
davinci_mdio: mdio@5c030000 {
59-
compatible = "ti,davinci_mdio";
6059
reg = <0x5c030000 0x1000>;
6160
#address-cells = <1>;
6261
#size-cells = <0>;

Documentation/driver-api/ipmb.rst

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -71,9 +71,13 @@ b) Example for device tree::
7171
ipmb@10 {
7272
compatible = "ipmb-dev";
7373
reg = <0x10>;
74+
i2c-protocol;
7475
};
7576
};
7677

78+
If xmit of data to be done using raw i2c block vs smbus
79+
then "i2c-protocol" needs to be defined as above.
80+
7781
2) Manually from Linux::
7882

7983
modprobe ipmb-dev-int

0 commit comments

Comments
 (0)