/openbmc/linux/Documentation/devicetree/bindings/input/touchscreen/ |
H A D | tsc2007.txt | 791d3ef2 Mon Jul 23 16:59:44 CDT 2018 Rob Herring <robh@kernel.org> 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> 791d3ef2 Mon Jul 23 16:59:44 CDT 2018 Rob Herring <robh@kernel.org> 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>
|
H A D | ektf2127.txt | 791d3ef2 Mon Jul 23 16:59:44 CDT 2018 Rob Herring <robh@kernel.org> 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> 791d3ef2 Mon Jul 23 16:59:44 CDT 2018 Rob Herring <robh@kernel.org> 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>
|
H A D | colibri-vf50-ts.txt | 791d3ef2 Mon Jul 23 16:59:44 CDT 2018 Rob Herring <robh@kernel.org> 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> 791d3ef2 Mon Jul 23 16:59:44 CDT 2018 Rob Herring <robh@kernel.org> 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>
|
H A D | egalax-ts.txt | 791d3ef2 Mon Jul 23 16:59:44 CDT 2018 Rob Herring <robh@kernel.org> 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> 791d3ef2 Mon Jul 23 16:59:44 CDT 2018 Rob Herring <robh@kernel.org> 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>
|
/openbmc/linux/Documentation/devicetree/bindings/timer/ |
H A D | snps,arc-timer.txt | 791d3ef2 Mon Jul 23 16:59:44 CDT 2018 Rob Herring <robh@kernel.org> 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> 791d3ef2 Mon Jul 23 16:59:44 CDT 2018 Rob Herring <robh@kernel.org> 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>
|
/openbmc/linux/Documentation/devicetree/bindings/cpufreq/ |
H A D | brcm,stb-avs-cpu-freq.txt | 791d3ef2 Mon Jul 23 16:59:44 CDT 2018 Rob Herring <robh@kernel.org> 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> 791d3ef2 Mon Jul 23 16:59:44 CDT 2018 Rob Herring <robh@kernel.org> 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>
|
/openbmc/linux/Documentation/devicetree/bindings/powerpc/fsl/ |
H A D | dcsr.txt | 791d3ef2 Mon Jul 23 16:59:44 CDT 2018 Rob Herring <robh@kernel.org> 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> 791d3ef2 Mon Jul 23 16:59:44 CDT 2018 Rob Herring <robh@kernel.org> 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>
|
/openbmc/linux/Documentation/devicetree/bindings/infiniband/ |
H A D | hisilicon-hns-roce.txt | 791d3ef2 Mon Jul 23 16:59:44 CDT 2018 Rob Herring <robh@kernel.org> 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> 791d3ef2 Mon Jul 23 16:59:44 CDT 2018 Rob Herring <robh@kernel.org> 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>
|
/openbmc/linux/Documentation/devicetree/bindings/gpio/ |
H A D | gpio-xgene-sb.txt | 791d3ef2 Mon Jul 23 16:59:44 CDT 2018 Rob Herring <robh@kernel.org> 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> 791d3ef2 Mon Jul 23 16:59:44 CDT 2018 Rob Herring <robh@kernel.org> 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>
|
/openbmc/linux/Documentation/devicetree/bindings/rtc/ |
H A D | rtc-cmos.txt | 791d3ef2 Mon Jul 23 16:59:44 CDT 2018 Rob Herring <robh@kernel.org> 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> 791d3ef2 Mon Jul 23 16:59:44 CDT 2018 Rob Herring <robh@kernel.org> 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>
|
/openbmc/linux/Documentation/devicetree/bindings/net/ |
H A D | samsung-sxgbe.txt | 791d3ef2 Mon Jul 23 16:59:44 CDT 2018 Rob Herring <robh@kernel.org> 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> 791d3ef2 Mon Jul 23 16:59:44 CDT 2018 Rob Herring <robh@kernel.org> 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>
|
H A D | snps,dwc-qos-ethernet.txt | 791d3ef2 Mon Jul 23 16:59:44 CDT 2018 Rob Herring <robh@kernel.org> 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> 791d3ef2 Mon Jul 23 16:59:44 CDT 2018 Rob Herring <robh@kernel.org> 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>
|
H A D | btusb.txt | 791d3ef2 Mon Jul 23 16:59:44 CDT 2018 Rob Herring <robh@kernel.org> 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> 791d3ef2 Mon Jul 23 16:59:44 CDT 2018 Rob Herring <robh@kernel.org> 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>
|
/openbmc/linux/Documentation/devicetree/bindings/iio/adc/ |
H A D | xilinx-xadc.txt | 791d3ef2 Mon Jul 23 16:59:44 CDT 2018 Rob Herring <robh@kernel.org> 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> 791d3ef2 Mon Jul 23 16:59:44 CDT 2018 Rob Herring <robh@kernel.org> 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>
|
/openbmc/linux/Documentation/devicetree/bindings/powerpc/nintendo/ |
H A D | wii.txt | 791d3ef2 Mon Jul 23 16:59:44 CDT 2018 Rob Herring <robh@kernel.org> 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> 791d3ef2 Mon Jul 23 16:59:44 CDT 2018 Rob Herring <robh@kernel.org> 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>
|
/openbmc/linux/Documentation/devicetree/bindings/remoteproc/ |
H A D | ti,keystone-rproc.txt | 791d3ef2 Mon Jul 23 16:59:44 CDT 2018 Rob Herring <robh@kernel.org> 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> 791d3ef2 Mon Jul 23 16:59:44 CDT 2018 Rob Herring <robh@kernel.org> 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>
|
/openbmc/linux/Documentation/devicetree/bindings/net/wireless/ |
H A D | marvell-8xxx.txt | 791d3ef2 Mon Jul 23 16:59:44 CDT 2018 Rob Herring <robh@kernel.org> 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> 791d3ef2 Mon Jul 23 16:59:44 CDT 2018 Rob Herring <robh@kernel.org> 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>
|
/openbmc/linux/Documentation/devicetree/bindings/serial/ |
H A D | nxp,sc16is7xx.txt | 791d3ef2 Mon Jul 23 16:59:44 CDT 2018 Rob Herring <robh@kernel.org> 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> 791d3ef2 Mon Jul 23 16:59:44 CDT 2018 Rob Herring <robh@kernel.org> 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>
|
/openbmc/linux/Documentation/devicetree/bindings/display/exynos/ |
H A D | exynos_dp.txt | 791d3ef2 Mon Jul 23 16:59:44 CDT 2018 Rob Herring <robh@kernel.org> 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> 791d3ef2 Mon Jul 23 16:59:44 CDT 2018 Rob Herring <robh@kernel.org> 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>
|
/openbmc/linux/Documentation/devicetree/bindings/sound/ |
H A D | cs35l35.txt | 791d3ef2 Mon Jul 23 16:59:44 CDT 2018 Rob Herring <robh@kernel.org> 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> 791d3ef2 Mon Jul 23 16:59:44 CDT 2018 Rob Herring <robh@kernel.org> 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>
|
/openbmc/linux/Documentation/devicetree/bindings/mfd/ |
H A D | motorola-cpcap.txt | 791d3ef2 Mon Jul 23 16:59:44 CDT 2018 Rob Herring <robh@kernel.org> 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> 791d3ef2 Mon Jul 23 16:59:44 CDT 2018 Rob Herring <robh@kernel.org> 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>
|
H A D | da9062.txt | 791d3ef2 Mon Jul 23 16:59:44 CDT 2018 Rob Herring <robh@kernel.org> 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> 791d3ef2 Mon Jul 23 16:59:44 CDT 2018 Rob Herring <robh@kernel.org> 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>
|
/openbmc/linux/Documentation/devicetree/bindings/interrupt-controller/ |
H A D | brcm,bcm2835-armctrl-ic.txt | 791d3ef2 Mon Jul 23 16:59:44 CDT 2018 Rob Herring <robh@kernel.org> 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> 791d3ef2 Mon Jul 23 16:59:44 CDT 2018 Rob Herring <robh@kernel.org> 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>
|
/openbmc/linux/Documentation/devicetree/bindings/display/tilcdc/ |
H A D | tilcdc.txt | 791d3ef2 Mon Jul 23 16:59:44 CDT 2018 Rob Herring <robh@kernel.org> 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> 791d3ef2 Mon Jul 23 16:59:44 CDT 2018 Rob Herring <robh@kernel.org> 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>
|
/openbmc/linux/Documentation/devicetree/bindings/input/ |
H A D | e3x0-button.txt | 791d3ef2 Mon Jul 23 16:59:44 CDT 2018 Rob Herring <robh@kernel.org> 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> 791d3ef2 Mon Jul 23 16:59:44 CDT 2018 Rob Herring <robh@kernel.org> 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>
|