aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/devicetree/bindings/arm/marvell,berlin.txt
diff options
context:
space:
mode:
authorAntoine Tenart <antoine.tenart@free-electrons.com>2015-04-27 21:39:48 +0200
committerSebastian Hesselbarth <sebastian.hesselbarth@gmail.com>2015-05-16 00:07:33 +0200
commit66fa300e60728ddbf7f9e8291c94c6c6691b00de (patch)
tree42802a05abaa5db261845f335447d75d1081e2e0 /Documentation/devicetree/bindings/arm/marvell,berlin.txt
parentDocumentation: bindings: move the Berlin reset documentation (diff)
downloadlinux-dev-66fa300e60728ddbf7f9e8291c94c6c6691b00de.tar.xz
linux-dev-66fa300e60728ddbf7f9e8291c94c6c6691b00de.zip
Documentation: bindings: move the Berlin pinctrl documentation
The Berlin pinctrl documentation was part of the Marvell Berlin SoC documentation because the Berlin pinctrl configuration was inside the chip and the system controllers. With the recent rework of the chip and system controller handling (now an MFD driver registers all sub-devices of the two soc and system controller nodes and each device has its own sub-node), the documentation of the Berlin pinctrl driver can be moved to the generic pinctrl documentation directory. Signed-off-by: Antoine Tenart <antoine.tenart@free-electrons.com> Signed-off-by: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Diffstat (limited to 'Documentation/devicetree/bindings/arm/marvell,berlin.txt')
-rw-r--r--Documentation/devicetree/bindings/arm/marvell,berlin.txt37
1 files changed, 0 insertions, 37 deletions
diff --git a/Documentation/devicetree/bindings/arm/marvell,berlin.txt b/Documentation/devicetree/bindings/arm/marvell,berlin.txt
index 6b7c21079bea..e8d9111a9852 100644
--- a/Documentation/devicetree/bindings/arm/marvell,berlin.txt
+++ b/Documentation/devicetree/bindings/arm/marvell,berlin.txt
@@ -107,23 +107,6 @@ Clocks provided by core clocks shall be referenced by a clock specifier
indexing one of the provided clocks. Refer to dt-bindings/clock/berlin<soc>.h
for the corresponding index mapping.
-* Pin controller binding
-
-Pin control registers are part of both register sets, chip control and system
-control. The pins controlled are organized in groups, so no actual pin
-information is needed.
-
-A pin-controller node should contain subnodes representing the pin group
-configurations, one per function. Each subnode has the group name and the muxing
-function used.
-
-Be aware the Marvell Berlin datasheets use the keyword 'mode' for what is called
-a 'function' in the pin-controller subsystem.
-
-Required subnode-properties:
-- groups: a list of strings describing the group names.
-- function: a string describing the function used to mux the groups.
-
Example:
chip: chip-control@ea0000 {
@@ -132,29 +115,9 @@ chip: chip-control@ea0000 {
reg = <0xea0000 0x400>;
clocks = <&refclk>, <&externaldev 0>;
clock-names = "refclk", "video_ext0";
-
- spi1_pmux: spi1-pmux {
- groups = "G0";
- function = "spi1";
- };
};
sysctrl: system-controller@d000 {
compatible = "marvell,berlin2-system-ctrl", "simple-mfd", "syscon";
reg = <0xd000 0x100>;
-
- uart0_pmux: uart0-pmux {
- groups = "GSM4";
- function = "uart0";
- };
-
- uart1_pmux: uart1-pmux {
- groups = "GSM5";
- function = "uart1";
- };
-
- uart2_pmux: uart2-pmux {
- groups = "GSM3";
- function = "uart2";
- };
};