On Mon Apr 12 2021, DENG Qingfang wrote: > Add device tree binding to support MT7530 interrupt controller. > > Signed-off-by: DENG Qingfang <dqfext@xxxxxxxxx> > Reviewed-by: Andrew Lunn <andrew@xxxxxxx> > --- > RFC v3 -> RFC v4: > - Add #interrupt-cells property. > > Documentation/devicetree/bindings/net/dsa/mt7530.txt | 6 ++++++ > 1 file changed, 6 insertions(+) > > diff --git a/Documentation/devicetree/bindings/net/dsa/mt7530.txt b/Documentation/devicetree/bindings/net/dsa/mt7530.txt > index de04626a8e9d..892b1570c496 100644 > --- a/Documentation/devicetree/bindings/net/dsa/mt7530.txt > +++ b/Documentation/devicetree/bindings/net/dsa/mt7530.txt > @@ -81,6 +81,12 @@ Optional properties: > - gpio-controller: Boolean; if defined, MT7530's LED controller will run on > GPIO mode. > - #gpio-cells: Must be 2 if gpio-controller is defined. > +- interrupt-controller: Boolean; Enables the internal interrupt controller. > + > +If interrupt-controller is defined, the following property is required. > + > +- #interrupt-cells: Must be 1. > +- interrupts: Parent interrupt for the interrupt controller. > > See Documentation/devicetree/bindings/net/dsa/dsa.txt for a list of additional That dsa.txt still exists, but it refers to the dsa.yaml binding. Any chance to convert this mt7530.txt to yaml as well? Then, device trees can be automatically validated for correct entries. There are a few examples of dsa yaml bindings already: ksz, b53, sf2, hellcreek, ... Thanks, Kurt
Attachment:
signature.asc
Description: PGP signature
