| Message ID | 20160811184013.2499-1-afd@ti.com |
|---|---|
| State | Accepted |
| Commit | ccb3611f5ac7db5e350a00e80d1b64d87789c984 |
| Headers | show |
On Thu, Aug 11, 2016 at 8:40 PM, Andrew F. Davis <afd@ti.com> wrote: > This binding is no longer correct, the GPIO information can should be > added to the parent node and not into this child node. See > Documentation/devicetree/bindings/mfd/tps65086.txt for the correct usage. > > Signed-off-by: Andrew F. Davis <afd@ti.com> Patch applied. Thanks for helping to keep the kernel clean! Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe devicetree" 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-tps65086.txt b/Documentation/devicetree/bindings/gpio/gpio-tps65086.txt deleted file mode 100644 index ba05107..0000000 --- a/Documentation/devicetree/bindings/gpio/gpio-tps65086.txt +++ /dev/null @@ -1,16 +0,0 @@ -* TPS65086 GPO Controller bindings - -Required properties: - - compatible : Should be "ti,tps65086-gpio". - - gpio-controller : Marks the device node as a GPIO Controller. - - #gpio-cells : Should be two. The first cell is the pin number - and the second cell is used to specify flags. - See ../gpio/gpio.txt for possible values. - -Example: - - gpio4: gpio { - compatible = "ti,tps65086-gpio"; - gpio-controller; - #gpio-cells = <2>; - };
This binding is no longer correct, the GPIO information can should be added to the parent node and not into this child node. See Documentation/devicetree/bindings/mfd/tps65086.txt for the correct usage. Signed-off-by: Andrew F. Davis <afd@ti.com> --- Documentation/devicetree/bindings/gpio/gpio-tps65086.txt | 16 ---------------- 1 file changed, 16 deletions(-) delete mode 100644 Documentation/devicetree/bindings/gpio/gpio-tps65086.txt -- 2.9.2 -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html