p71924506
/
linux_old1
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

pinctrl: cygnus: Optional DT property to support pin mappings 

If GPIO controller's pins are muxed, pin-controller subsystem
need to be intimated by defining mapping between gpio and
pinmux controller. This patch adds required properties to
define this mapping via DT.

Signed-off-by: Pramod Kumar <pramodku@broadcom.com>
Reviewed-by: Ray Jui <rjui@broadcom.com>
Reviewed-by: Scott Branden <sbranden@broadcom.com>
Acked-by: Rob Herring <robh@kernel.org>
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
This commit is contained in:
Pramod Kumar 2015-10-19 11:13:08 +05:30 committed by Linus Walleij
parent 10af309a86
commit 03e09bc185
1 changed files with 9 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
Documentation/devicetree/bindings/pinctrl/brcm,cygnus-gpio.txt
View File

@ -26,9 +26,13 @@ Optional properties:
- interrupt-controller: - interrupt-controller:
Specifies that the node is an interrupt controller Specifies that the node is an interrupt controller
- pinmux: - gpio-ranges:
Specifies the phandle to the IOMUX device, where pins can be individually Specifies the mapping between gpio controller and pin-controllers pins.
muxed to GPIO This requires 4 fields in cells defined as -
1. Phandle of pin-controller.
2. GPIO base pin offset.
3 Pin-control base pin offset.
4. number of gpio pins which are linearly mapped from pin base.
Supported generic PINCONF properties in child nodes: Supported generic PINCONF properties in child nodes:
@ -78,6 +82,8 @@ Example:
gpio-controller; gpio-controller;
interrupts = <GIC_SPI 174 IRQ_TYPE_LEVEL_HIGH>; interrupts = <GIC_SPI 174 IRQ_TYPE_LEVEL_HIGH>;
interrupt-controller; interrupt-controller;
gpio-ranges = <&pinctrl 0 42 1>,
<&pinctrl 1 44 3>;
}; };
/* /*