-
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.
yaml --- r: 332488 b: refs/heads/master c: 9e2d865 h: refs/heads/master v: v3
- Loading branch information
Linus Torvalds
committed
Oct 9, 2012
1 parent
270bf52
commit 0641a20
Showing
299 changed files
with
55,260 additions
and
7,134 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,2 +1,2 @@ | ||
--- | ||
refs/heads/master: 9e695d2ecc8451cc2c1603d60b5c8e7f5581923a | ||
refs/heads/master: 9e2d8656f5e8aa214e66b462680cf86b210b74a8 |
83 changes: 83 additions & 0 deletions
83
trunk/Documentation/devicetree/bindings/pinctrl/lantiq,falcon-pinumx.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,83 @@ | ||
Lantiq FALCON pinmux controller | ||
|
||
Required properties: | ||
- compatible: "lantiq,pinctrl-falcon" | ||
- reg: Should contain the physical address and length of the gpio/pinmux | ||
register range | ||
|
||
Please refer to pinctrl-bindings.txt in this directory for details of the | ||
common pinctrl bindings used by client devices, including the meaning of the | ||
phrase "pin configuration node". | ||
|
||
Lantiq's pin configuration nodes act as a container for an abitrary number of | ||
subnodes. Each of these subnodes represents some desired configuration for a | ||
pin, a group, or a list of pins or groups. This configuration can include the | ||
mux function to select on those group(s), and two pin configuration parameters: | ||
pull-up and open-drain | ||
|
||
The name of each subnode is not important as long as it is unique; all subnodes | ||
should be enumerated and processed purely based on their content. | ||
|
||
Each subnode only affects those parameters that are explicitly listed. In | ||
other words, a subnode that lists a mux function but no pin configuration | ||
parameters implies no information about any pin configuration parameters. | ||
Similarly, a pin subnode that describes a pullup parameter implies no | ||
information about e.g. the mux function. | ||
|
||
We support 2 types of nodes. | ||
|
||
Definition of mux function groups: | ||
|
||
Required subnode-properties: | ||
- lantiq,groups : An array of strings. Each string contains the name of a group. | ||
Valid values for these names are listed below. | ||
- lantiq,function: A string containing the name of the function to mux to the | ||
group. Valid values for function names are listed below. | ||
|
||
Valid values for group and function names: | ||
|
||
mux groups: | ||
por, ntr, ntr8k, hrst, mdio, bootled, asc0, spi, spi cs0, spi cs1, i2c, | ||
jtag, slic, pcm, asc1 | ||
|
||
functions: | ||
rst, ntr, mdio, led, asc, spi, i2c, jtag, slic, pcm | ||
|
||
|
||
Definition of pin configurations: | ||
|
||
Required subnode-properties: | ||
- lantiq,pins : An array of strings. Each string contains the name of a pin. | ||
Valid values for these names are listed below. | ||
|
||
Optional subnode-properties: | ||
- lantiq,pull: Integer, representing the pull-down/up to apply to the pin. | ||
0: none, 1: down | ||
- lantiq,drive-current: Boolean, enables drive-current | ||
- lantiq,slew-rate: Boolean, enables slew-rate | ||
|
||
Example: | ||
pinmux0 { | ||
compatible = "lantiq,pinctrl-falcon"; | ||
pinctrl-names = "default"; | ||
pinctrl-0 = <&state_default>; | ||
|
||
state_default: pinmux { | ||
asc0 { | ||
lantiq,groups = "asc0"; | ||
lantiq,function = "asc"; | ||
}; | ||
ntr { | ||
lantiq,groups = "ntr8k"; | ||
lantiq,function = "ntr"; | ||
}; | ||
i2c { | ||
lantiq,groups = "i2c"; | ||
lantiq,function = "i2c"; | ||
}; | ||
hrst { | ||
lantiq,groups = "hrst"; | ||
lantiq,function = "rst"; | ||
}; | ||
}; | ||
}; |
97 changes: 97 additions & 0 deletions
97
trunk/Documentation/devicetree/bindings/pinctrl/lantiq,xway-pinumx.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,97 @@ | ||
Lantiq XWAY pinmux controller | ||
|
||
Required properties: | ||
- compatible: "lantiq,pinctrl-xway" or "lantiq,pinctrl-xr9" | ||
- reg: Should contain the physical address and length of the gpio/pinmux | ||
register range | ||
|
||
Please refer to pinctrl-bindings.txt in this directory for details of the | ||
common pinctrl bindings used by client devices, including the meaning of the | ||
phrase "pin configuration node". | ||
|
||
Lantiq's pin configuration nodes act as a container for an abitrary number of | ||
subnodes. Each of these subnodes represents some desired configuration for a | ||
pin, a group, or a list of pins or groups. This configuration can include the | ||
mux function to select on those group(s), and two pin configuration parameters: | ||
pull-up and open-drain | ||
|
||
The name of each subnode is not important as long as it is unique; all subnodes | ||
should be enumerated and processed purely based on their content. | ||
|
||
Each subnode only affects those parameters that are explicitly listed. In | ||
other words, a subnode that lists a mux function but no pin configuration | ||
parameters implies no information about any pin configuration parameters. | ||
Similarly, a pin subnode that describes a pullup parameter implies no | ||
information about e.g. the mux function. | ||
|
||
We support 2 types of nodes. | ||
|
||
Definition of mux function groups: | ||
|
||
Required subnode-properties: | ||
- lantiq,groups : An array of strings. Each string contains the name of a group. | ||
Valid values for these names are listed below. | ||
- lantiq,function: A string containing the name of the function to mux to the | ||
group. Valid values for function names are listed below. | ||
|
||
Valid values for group and function names: | ||
|
||
mux groups: | ||
exin0, exin1, exin2, jtag, ebu a23, ebu a24, ebu a25, ebu clk, ebu cs1, | ||
ebu wait, nand ale, nand cs1, nand cle, spi, spi_cs1, spi_cs2, spi_cs3, | ||
spi_cs4, spi_cs5, spi_cs6, asc0, asc0 cts rts, stp, nmi , gpt1, gpt2, | ||
gpt3, clkout0, clkout1, clkout2, clkout3, gnt1, gnt2, gnt3, req1, req2, | ||
req3 | ||
|
||
additional mux groups (XR9 only): | ||
mdio, nand rdy, nand rd, exin3, exin4, gnt4, req4 | ||
|
||
functions: | ||
spi, asc, cgu, jtag, exin, stp, gpt, nmi, pci, ebu, mdio | ||
|
||
|
||
|
||
Definition of pin configurations: | ||
|
||
Required subnode-properties: | ||
- lantiq,pins : An array of strings. Each string contains the name of a pin. | ||
Valid values for these names are listed below. | ||
|
||
Optional subnode-properties: | ||
- lantiq,pull: Integer, representing the pull-down/up to apply to the pin. | ||
0: none, 1: down, 2: up. | ||
- lantiq,open-drain: Boolean, enables open-drain on the defined pin. | ||
|
||
Valid values for XWAY pin names: | ||
Pinconf pins can be referenced via the names io0-io31. | ||
|
||
Valid values for XR9 pin names: | ||
Pinconf pins can be referenced via the names io0-io55. | ||
|
||
Example: | ||
gpio: pinmux@E100B10 { | ||
compatible = "lantiq,pinctrl-xway"; | ||
pinctrl-names = "default"; | ||
pinctrl-0 = <&state_default>; | ||
|
||
#gpio-cells = <2>; | ||
gpio-controller; | ||
reg = <0xE100B10 0xA0>; | ||
|
||
state_default: pinmux { | ||
stp { | ||
lantiq,groups = "stp"; | ||
lantiq,function = "stp"; | ||
}; | ||
pci { | ||
lantiq,groups = "gnt1"; | ||
lantiq,function = "pci"; | ||
}; | ||
conf_out { | ||
lantiq,pins = "io4", "io5", "io6"; /* stp */ | ||
lantiq,open-drain; | ||
lantiq,pull = <0>; | ||
}; | ||
}; | ||
}; | ||
|
33 changes: 33 additions & 0 deletions
33
trunk/Documentation/devicetree/bindings/spi/spi-octeon.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,33 @@ | ||
Cavium, Inc. OCTEON SOC SPI master controller. | ||
|
||
Required properties: | ||
- compatible : "cavium,octeon-3010-spi" | ||
- reg : The register base for the controller. | ||
- interrupts : One interrupt, used by the controller. | ||
- #address-cells : <1>, as required by generic SPI binding. | ||
- #size-cells : <0>, also as required by generic SPI binding. | ||
|
||
Child nodes as per the generic SPI binding. | ||
|
||
Example: | ||
|
||
spi@1070000001000 { | ||
compatible = "cavium,octeon-3010-spi"; | ||
reg = <0x10700 0x00001000 0x0 0x100>; | ||
interrupts = <0 58>; | ||
#address-cells = <1>; | ||
#size-cells = <0>; | ||
|
||
eeprom@0 { | ||
compatible = "st,m95256", "atmel,at25"; | ||
reg = <0>; | ||
spi-max-frequency = <5000000>; | ||
spi-cpha; | ||
spi-cpol; | ||
|
||
pagesize = <64>; | ||
size = <32768>; | ||
address-width = <16>; | ||
}; | ||
}; | ||
|
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 |
---|---|---|
@@ -1,3 +1,5 @@ | ||
include include/asm-generic/Kbuild.asm | ||
|
||
generic-y += clkdev.h | ||
|
||
header-y += cachectl.h |
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
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.