summaryrefslogtreecommitdiff
path: root/Documentation/devicetree/bindings/mtd/brcm,brcmnand.txt
diff options
context:
space:
mode:
authorRob Herring <robh@kernel.org>2018-07-24 00:59:44 +0300
committerRob Herring <robh@kernel.org>2018-07-25 23:09:39 +0300
commit791d3ef2e11100449837dc0b6fe884e60ca3a484 (patch)
tree7797383556224291dd8e8b33f47808d50bb23653 /Documentation/devicetree/bindings/mtd/brcm,brcmnand.txt
parent13d6753f1d250885749386867c4a4e8c06c905da (diff)
downloadlinux-791d3ef2e11100449837dc0b6fe884e60ca3a484.tar.xz
dt-bindings: remove 'interrupt-parent' from bindings
'interrupt-parent' is often documented as part of define bindings, but it is really outside the scope of a device binding. It's never required in a given node as it is often inherited from a parent node. Or it can be implicit if a parent node is an 'interrupt-controller' node. So remove it from all the binding files. Cc: Mark Rutland <mark.rutland@arm.com> Cc: devicetree@vger.kernel.org Signed-off-by: Rob Herring <robh@kernel.org>
Diffstat (limited to 'Documentation/devicetree/bindings/mtd/brcm,brcmnand.txt')
-rw-r--r--Documentation/devicetree/bindings/mtd/brcm,brcmnand.txt1
1 files changed, 0 insertions, 1 deletions
diff --git a/Documentation/devicetree/bindings/mtd/brcm,brcmnand.txt b/Documentation/devicetree/bindings/mtd/brcm,brcmnand.txt
index b40f3a492800..bcda1dfc4bac 100644
--- a/Documentation/devicetree/bindings/mtd/brcm,brcmnand.txt
+++ b/Documentation/devicetree/bindings/mtd/brcm,brcmnand.txt
@@ -42,7 +42,6 @@ Required properties:
May be "nand", if the SoC has the individual NAND
interrupts multiplexed behind another custom piece of
hardware
-- interrupt-parent : See standard interrupt bindings
- #address-cells : <1> - subnodes give the chip-select number
- #size-cells : <0>