The current PRUSS Interrupt Controller binding doesn't exactly specify
the convention for the node name. These interrupt-controllers will always
have a unit address. Update the binding with the '$nodename' using the
expected generic name, this shall ensure the interrupt-controller.yaml
is automatically applied to this binding.
Signed-off-by: Suman Anna <[email protected]>
---
This patch is a result of the previous discussion at
https://patchwork.kernel.org/comment/23926133/
.../bindings/interrupt-controller/ti,pruss-intc.yaml | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/devicetree/bindings/interrupt-controller/ti,pruss-intc.yaml b/Documentation/devicetree/bindings/interrupt-controller/ti,pruss-intc.yaml
index c2ce215501a5..9731dd4421a1 100644
--- a/Documentation/devicetree/bindings/interrupt-controller/ti,pruss-intc.yaml
+++ b/Documentation/devicetree/bindings/interrupt-controller/ti,pruss-intc.yaml
@@ -33,6 +33,9 @@ description: |
corresponding PRUSS node. The node should be named "interrupt-controller".
properties:
+ $nodename:
+ pattern: "^interrupt-controller@[0-9a-f]+$"
+
compatible:
enum:
- ti,pruss-intc
--
2.29.2
On Tue, 26 Jan 2021 10:32:51 -0600, Suman Anna wrote:
> The current PRUSS Interrupt Controller binding doesn't exactly specify
> the convention for the node name. These interrupt-controllers will always
> have a unit address. Update the binding with the '$nodename' using the
> expected generic name, this shall ensure the interrupt-controller.yaml
> is automatically applied to this binding.
>
> Signed-off-by: Suman Anna <[email protected]>
> ---
> This patch is a result of the previous discussion at
> https://patchwork.kernel.org/comment/23926133/
>
> .../bindings/interrupt-controller/ti,pruss-intc.yaml | 3 +++
> 1 file changed, 3 insertions(+)
>
Applied, thanks!