On Fri, Apr 09, 2021 at 04:19:31PM +0800, Nina Wu wrote: > From: Nina Wu <Nina-CM.Wu@xxxxxxxxxxxx> > > For new ICs, there are multiple devapc HWs for different subsys. > We add a field 'vio-idx-num' in DT to indicate the number of > devices controlled by each devapc. > To be backward compatible with old ICs which have only one devapc > HW, this field is not required. The 'vio-idx-num' info will be set > in compatible data instead. > > Signed-off-by: Nina Wu <Nina-CM.Wu@xxxxxxxxxxxx> > --- > Documentation/devicetree/bindings/soc/mediatek/devapc.yaml | 6 ++++++ > 1 file changed, 6 insertions(+) > > diff --git a/Documentation/devicetree/bindings/soc/mediatek/devapc.yaml b/Documentation/devicetree/bindings/soc/mediatek/devapc.yaml > index 31e4d3c..909e524 100644 > --- a/Documentation/devicetree/bindings/soc/mediatek/devapc.yaml > +++ b/Documentation/devicetree/bindings/soc/mediatek/devapc.yaml > @@ -20,11 +20,17 @@ properties: > compatible: > enum: > - mediatek,mt6779-devapc > + - mediatek,mt8192-devapc > > reg: > description: The base address of devapc register bank > maxItems: 1 > > + mediatek,vio-idx-num: > + description: The number of the devices controlled by devapc > + $ref: /schemas/types.yaml#/definitions/uint32 > + maxItems: 1 A uint32 is always 1 item, so drop. With that, Reviewed-by: Rob Herring <robh@xxxxxxxxxx> > + > interrupts: > description: A single interrupt specifier > maxItems: 1 > -- > 2.6.4 >
