| Message ID | 1488332932-2691-5-git-send-email-david.daney@cavium.com |
|---|---|
| State | New |
| Headers | show |
On Wed, Mar 1, 2017 at 2:48 AM, David Daney <david.daney@cavium.com> wrote: > Signed-off-by: David Daney <david.daney@cavium.com> > Acked-by: Rob Herring <robh@kernel.org> This patch applied to the GPIO tree, really simplistic so why not merge it. Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-gpio" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On 03/14/2017 07:53 AM, Linus Walleij wrote: > On Wed, Mar 1, 2017 at 2:48 AM, David Daney <david.daney@cavium.com> wrote: > >> Signed-off-by: David Daney <david.daney@cavium.com> >> Acked-by: Rob Herring <robh@kernel.org> > > This patch applied to the GPIO tree, really simplistic so why not > merge it. I think the idea is that with Rob's Acked-by, it could be merged via the GPIO tree when and if the other patches in the set are merged. Since I don't maintain any trees pulled by Linus Torvalds, I am at the mercy of the various maintainers. David Daney. -- To unsubscribe from this list: send the line "unsubscribe linux-gpio" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Tue, Mar 14, 2017 at 5:45 PM, David Daney <ddaney@caviumnetworks.com> wrote: > On 03/14/2017 07:53 AM, Linus Walleij wrote: >> >> On Wed, Mar 1, 2017 at 2:48 AM, David Daney <david.daney@cavium.com> >> wrote: >> >>> Signed-off-by: David Daney <david.daney@cavium.com> >>> Acked-by: Rob Herring <robh@kernel.org> >> >> >> This patch applied to the GPIO tree, really simplistic so why not >> merge it. > > > I think the idea is that with Rob's Acked-by, it could be merged via the > GPIO tree when and if the other patches in the set are merged. Since I > don't maintain any trees pulled by Linus Torvalds, I am at the mercy of the > various maintainers. I agree that the code changes need to go in together. But DT bindings are sort of decoupled from the kernel i general (they are theoretically also used by other OSes such as *BSD) so they can be merged in an orthogonal manner once they are considered finished. No biggie for me though, if you prefer, I can pull it out. Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-gpio" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
diff --git a/Documentation/devicetree/bindings/gpio/gpio-thunderx.txt b/Documentation/devicetree/bindings/gpio/gpio-thunderx.txt new file mode 100644 index 0000000..3f883ae --- /dev/null +++ b/Documentation/devicetree/bindings/gpio/gpio-thunderx.txt @@ -0,0 +1,27 @@ +Cavium ThunderX/OCTEON-TX GPIO controller bindings + +Required Properties: +- reg: The controller bus address. +- gpio-controller: Marks the device node as a GPIO controller. +- #gpio-cells: Must be 2. + - First cell is the GPIO pin number relative to the controller. + - Second cell is a standard generic flag bitfield as described in gpio.txt. + +Optional Properties: +- compatible: "cavium,thunder-8890-gpio", unused as PCI driver binding is used. +- interrupt-controller: Marks the device node as an interrupt controller. +- #interrupt-cells: Must be present and have value of 2 if + "interrupt-controller" is present. + - First cell is the GPIO pin number relative to the controller. + - Second cell is triggering flags as defined in interrupts.txt. + +Example: + +gpio_6_0: gpio@6,0 { + compatible = "cavium,thunder-8890-gpio"; + reg = <0x3000 0 0 0 0>; /* DEVFN = 0x30 (6:0) */ + gpio-controller; + #gpio-cells = <2>; + interrupt-controller; + #interrupt-cells = <2>; +};