-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'linus' into x86/urgent
Pick up Linus's latest, to fix a bug. Signed-off-by: Ingo Molnar <mingo@kernel.org>
- Loading branch information
Showing
415 changed files
with
7,486 additions
and
4,729 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,76 @@ | ||
* APM X-Gene 6.0 Gb/s SATA host controller nodes | ||
|
||
SATA host controller nodes are defined to describe on-chip Serial ATA | ||
controllers. Each SATA controller (pair of ports) have its own node. | ||
|
||
Required properties: | ||
- compatible : Shall contain: | ||
* "apm,xgene-ahci" | ||
- reg : First memory resource shall be the AHCI memory | ||
resource. | ||
Second memory resource shall be the host controller | ||
core memory resource. | ||
Third memory resource shall be the host controller | ||
diagnostic memory resource. | ||
4th memory resource shall be the host controller | ||
AXI memory resource. | ||
5th optional memory resource shall be the host | ||
controller MUX memory resource if required. | ||
- interrupts : Interrupt-specifier for SATA host controller IRQ. | ||
- clocks : Reference to the clock entry. | ||
- phys : A list of phandles + phy-specifiers, one for each | ||
entry in phy-names. | ||
- phy-names : Should contain: | ||
* "sata-phy" for the SATA 6.0Gbps PHY | ||
|
||
Optional properties: | ||
- status : Shall be "ok" if enabled or "disabled" if disabled. | ||
Default is "ok". | ||
|
||
Example: | ||
sataclk: sataclk { | ||
compatible = "fixed-clock"; | ||
#clock-cells = <1>; | ||
clock-frequency = <100000000>; | ||
clock-output-names = "sataclk"; | ||
}; | ||
|
||
phy2: phy@1f22a000 { | ||
compatible = "apm,xgene-phy"; | ||
reg = <0x0 0x1f22a000 0x0 0x100>; | ||
#phy-cells = <1>; | ||
}; | ||
|
||
phy3: phy@1f23a000 { | ||
compatible = "apm,xgene-phy"; | ||
reg = <0x0 0x1f23a000 0x0 0x100>; | ||
#phy-cells = <1>; | ||
}; | ||
|
||
sata2: sata@1a400000 { | ||
compatible = "apm,xgene-ahci"; | ||
reg = <0x0 0x1a400000 0x0 0x1000>, | ||
<0x0 0x1f220000 0x0 0x1000>, | ||
<0x0 0x1f22d000 0x0 0x1000>, | ||
<0x0 0x1f22e000 0x0 0x1000>, | ||
<0x0 0x1f227000 0x0 0x1000>; | ||
interrupts = <0x0 0x87 0x4>; | ||
status = "ok"; | ||
clocks = <&sataclk 0>; | ||
phys = <&phy2 0>; | ||
phy-names = "sata-phy"; | ||
}; | ||
|
||
sata3: sata@1a800000 { | ||
compatible = "apm,xgene-ahci-pcie"; | ||
reg = <0x0 0x1a800000 0x0 0x1000>, | ||
<0x0 0x1f230000 0x0 0x1000>, | ||
<0x0 0x1f23d000 0x0 0x1000>, | ||
<0x0 0x1f23e000 0x0 0x1000>, | ||
<0x0 0x1f237000 0x0 0x1000>; | ||
interrupts = <0x0 0x88 0x4>; | ||
status = "ok"; | ||
clocks = <&sataclk 0>; | ||
phys = <&phy3 0>; | ||
phy-names = "sata-phy"; | ||
}; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
27 changes: 27 additions & 0 deletions
27
Documentation/devicetree/bindings/interrupt-controller/allwinner,sun67i-sc-nmi.txt
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,27 @@ | ||
Allwinner Sunxi NMI Controller | ||
============================== | ||
|
||
Required properties: | ||
|
||
- compatible : should be "allwinner,sun7i-a20-sc-nmi" or | ||
"allwinner,sun6i-a31-sc-nmi" | ||
- reg : Specifies base physical address and size of the registers. | ||
- interrupt-controller : Identifies the node as an interrupt controller | ||
- #interrupt-cells : Specifies the number of cells needed to encode an | ||
interrupt source. The value shall be 2. The first cell is the IRQ number, the | ||
second cell the trigger type as defined in interrupt.txt in this directory. | ||
- interrupt-parent: Specifies the parent interrupt controller. | ||
- interrupts: Specifies the interrupt line (NMI) which is handled by | ||
the interrupt controller in the parent controller's notation. This value | ||
shall be the NMI. | ||
|
||
Example: | ||
|
||
sc-nmi-intc@01c00030 { | ||
compatible = "allwinner,sun7i-a20-sc-nmi"; | ||
interrupt-controller; | ||
#interrupt-cells = <2>; | ||
reg = <0x01c00030 0x0c>; | ||
interrupt-parent = <&gic>; | ||
interrupts = <0 0 4>; | ||
}; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
29 changes: 29 additions & 0 deletions
29
Documentation/devicetree/bindings/timer/ti,keystone-timer.txt
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,29 @@ | ||
* Device tree bindings for Texas instruments Keystone timer | ||
|
||
This document provides bindings for the 64-bit timer in the KeyStone | ||
architecture devices. The timer can be configured as a general-purpose 64-bit | ||
timer, dual general-purpose 32-bit timers. When configured as dual 32-bit | ||
timers, each half can operate in conjunction (chain mode) or independently | ||
(unchained mode) of each other. | ||
|
||
It is global timer is a free running up-counter and can generate interrupt | ||
when the counter reaches preset counter values. | ||
|
||
Documentation: | ||
http://www.ti.com/lit/ug/sprugv5a/sprugv5a.pdf | ||
|
||
Required properties: | ||
|
||
- compatible : should be "ti,keystone-timer". | ||
- reg : specifies base physical address and count of the registers. | ||
- interrupts : interrupt generated by the timer. | ||
- clocks : the clock feeding the timer clock. | ||
|
||
Example: | ||
|
||
timer@22f0000 { | ||
compatible = "ti,keystone-timer"; | ||
reg = <0x022f0000 0x80>; | ||
interrupts = <GIC_SPI 110 IRQ_TYPE_EDGE_RISING>; | ||
clocks = <&clktimer15>; | ||
}; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.