| Message ID | 20220126231146.1632819-1-robh@kernel.org |
|---|---|
| State | Accepted |
| Commit | d7f17b661fe947719500f8b3296f7f02113e8951 |
| Headers | show |
| Series | dt-bindings: arm,cci-400: Add interrupt controller to example | expand |
On Wed, 26 Jan 2022 17:11:46 -0600, Rob Herring wrote: > In order to parse the 'interrupts' an interrupt provider node is needed. > That is because the example is a full example (starting with root node) > and on those we don't guess and generate a fake provider. > > Signed-off-by: Rob Herring <robh@kernel.org> > --- > Documentation/devicetree/bindings/arm/arm,cci-400.yaml | 5 +++++ > 1 file changed, 5 insertions(+) > Applied, thanks!
diff --git a/Documentation/devicetree/bindings/arm/arm,cci-400.yaml b/Documentation/devicetree/bindings/arm/arm,cci-400.yaml index f8530a50863a..1706134b75a3 100644 --- a/Documentation/devicetree/bindings/arm/arm,cci-400.yaml +++ b/Documentation/devicetree/bindings/arm/arm,cci-400.yaml @@ -119,6 +119,11 @@ examples: arm,hbi = <0x249>; interrupt-parent = <&gic>; + gic: interrupt-controller { + interrupt-controller; + #interrupt-cells = <3>; + }; + /* * This CCI node corresponds to a CCI component whose control * registers sits at address 0x000000002c090000.
In order to parse the 'interrupts' an interrupt provider node is needed. That is because the example is a full example (starting with root node) and on those we don't guess and generate a fake provider. Signed-off-by: Rob Herring <robh@kernel.org> --- Documentation/devicetree/bindings/arm/arm,cci-400.yaml | 5 +++++ 1 file changed, 5 insertions(+)