aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/devicetree/bindings/bus
diff options
context:
space:
mode:
authorRafał Miłecki <zajec5@gmail.com>2014-09-30 12:55:48 +0200
committerJohn W. Linville <linville@tuxdriver.com>2014-09-30 13:17:14 -0400
commita0196d111707d8b79196a40295f3935c5fa339eb (patch)
tree212133ad4f485b3ca9352d8638316b2485644e33 /Documentation/devicetree/bindings/bus
parentbcma: register bcma as device tree driver (diff)
downloadlinux-dev-a0196d111707d8b79196a40295f3935c5fa339eb.tar.xz
linux-dev-a0196d111707d8b79196a40295f3935c5fa339eb.zip
bcma: use chipcommon node from DT for SoC GPIO chip
This will allow us to define GPIO-attached devices (LEDs, buttons) in the the device tree. Signed-off-by: Rafał Miłecki <zajec5@gmail.com> Acked-by: Arnd Bergmann <arnd@arndb.de> Signed-off-by: John W. Linville <linville@tuxdriver.com>
Diffstat (limited to 'Documentation/devicetree/bindings/bus')
-rw-r--r--Documentation/devicetree/bindings/bus/bcma.txt12
1 files changed, 12 insertions, 0 deletions
diff --git a/Documentation/devicetree/bindings/bus/bcma.txt b/Documentation/devicetree/bindings/bus/bcma.txt
index e9070c161172..62a48348ac15 100644
--- a/Documentation/devicetree/bindings/bus/bcma.txt
+++ b/Documentation/devicetree/bindings/bus/bcma.txt
@@ -9,6 +9,11 @@ Required properties:
The cores on the AXI bus are automatically detected by bcma with the
memory ranges they are using and they get registered afterwards.
+The top-level axi bus may contain children representing attached cores
+(devices). This is needed since some hardware details can't be auto
+detected (e.g. IRQ numbers). Also some of the cores may be responsible
+for extra things, e.g. ChipCommon providing access to the GPIO chip.
+
Example:
axi@18000000 {
@@ -17,4 +22,11 @@ Example:
ranges = <0x00000000 0x18000000 0x00100000>;
#address-cells = <1>;
#size-cells = <1>;
+
+ chipcommon {
+ reg = <0x00000000 0x1000>;
+
+ gpio-controller;
+ #gpio-cells = <2>;
+ };
};