On 27 September 2014 00:03, Arnd Bergmann a...@arndb.de wrote:
On Friday 26 September 2014 16:28:53 Rafał Miłecki wrote:
+The top-level axi bus may contain following children:
+
+- gpio: GPIO chip on the SoC
+
+ Required properties:
+ - compatible: brcm,bus-gpio
+ - gpio-controller :
On 09/27/2014 10:05 AM, Rafał Miłecki wrote:
On 27 September 2014 00:03, Arnd Bergmann a...@arndb.de wrote:
On Friday 26 September 2014 16:28:53 Rafał Miłecki wrote:
+The top-level axi bus may contain following children:
+
+- gpio: GPIO chip on the SoC
+
+ Required properties:
+ -
On 27 September 2014 10:33, Hauke Mehrtens ha...@hauke-m.de wrote:
I would make GPIO a subdevive of chipcommon. The chipcommon core has an
own IRQ which is also used for GPIO.
Which ChipCommon do yo mean?
1) chipcommonA (compatible = simple-bus)
2) chipcommon@0 (child of axi@1800 AKA
On 09/27/2014 12:37 PM, Rafał Miłecki wrote:
On 27 September 2014 10:33, Hauke Mehrtens ha...@hauke-m.de wrote:
I would make GPIO a subdevive of chipcommon. The chipcommon core has an
own IRQ which is also used for GPIO.
Which ChipCommon do yo mean?
1) chipcommonA (compatible = simple-bus)
This will allow us to define GPIO-attached devices (LEDs, buttons) in
the the device tree.
Signed-off-by: Rafał Miłecki zaj...@gmail.com
---
This is based on top of
[PATCH v6] bcma: register bcma as device tree driver
that I hope will reach wireless-next git tree.
---
On Friday 26 September 2014 16:28:53 Rafał Miłecki wrote:
+The top-level axi bus may contain following children:
+
+- gpio: GPIO chip on the SoC
+
+ Required properties:
+ - compatible: brcm,bus-gpio
+ - gpio-controller : makes the node a GPIO controller
+ - #gpio-cells : size of the