Hi yu-chang.lee, kernel test robot noticed the following build warnings: [auto build test WARNING on robh/for-next] [also build test WARNING on krzk-dt/for-next linus/master v6.9-rc1 next-20240328] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as documented in https://git-scm.com/docs/git-format-patch#_base_tree_information] url: https://github.com/intel-lab-lkp/linux/commits/yu-chang-lee/pmdomain-mediatek-add-smi_larb_reset-function-when-power-on/20240327-140007 base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next patch link: https://lore.kernel.org/r/20240327055732.28198-3-yu-chang.lee%40mediatek.com patch subject: [PATCH v2 2/3] dt-bindings: power: Add mediatek larb definition compiler: loongarch64-linux-gcc (GCC) 13.2.0 reproduce: (https://download.01.org/0day-ci/archive/20240331/202403312222.fjYPC06h-lkp@xxxxxxxxx/reproduce) If you fix the issue in a separate patch/commit (i.e. not just a new version of the same patch/commit), kindly add following tags | Reported-by: kernel test robot <lkp@xxxxxxxxx> | Closes: https://lore.kernel.org/oe-kbuild-all/202403312222.fjYPC06h-lkp@xxxxxxxxx/ dtcheck warnings: (new ones prefixed by >>) >> Documentation/devicetree/bindings/power/mediatek,power-controller.yaml:128:6: [error] syntax error: expected <block end>, but found '<block mapping start>' (syntax) >> Documentation/devicetree/bindings/power/mediatek,power-controller.yaml:129:9: [warning] wrong indentation: expected 7 but found 8 (indentation) -- >> Documentation/devicetree/bindings/power/mediatek,power-controller.yaml:128:6: did not find expected key >> Documentation/devicetree/bindings/mfd/mediatek,mt8195-scpsys.yaml: while parsing a block mapping in "<unicode string>", line 64, column 5 did not find expected key in "<unicode string>", line 128, column 6 -- >> Documentation/devicetree/bindings/power/mediatek,power-controller.yaml: ignoring, error parsing file vim +128 Documentation/devicetree/bindings/power/mediatek,power-controller.yaml 8 9 maintainers: 10 - MandyJH Liu <mandyjh.liu@xxxxxxxxxxxx> 11 - Matthias Brugger <mbrugger@xxxxxxxx> 12 13 description: | 14 Mediatek processors include support for multiple power domains which can be 15 powered up/down by software based on different application scenes to save power. 16 17 IP cores belonging to a power domain should contain a 'power-domains' 18 property that is a phandle for SCPSYS node representing the domain. 19 20 properties: 21 $nodename: 22 pattern: '^power-controller(@[0-9a-f]+)?$' 23 24 compatible: 25 enum: 26 - mediatek,mt6795-power-controller 27 - mediatek,mt8167-power-controller 28 - mediatek,mt8173-power-controller 29 - mediatek,mt8183-power-controller 30 - mediatek,mt8186-power-controller 31 - mediatek,mt8188-power-controller 32 - mediatek,mt8192-power-controller 33 - mediatek,mt8195-power-controller 34 - mediatek,mt8365-power-controller 35 36 '#power-domain-cells': 37 const: 1 38 39 '#address-cells': 40 const: 1 41 42 '#size-cells': 43 const: 0 44 45 patternProperties: 46 "^power-domain@[0-9a-f]+$": 47 $ref: "#/$defs/power-domain-node" 48 patternProperties: 49 "^power-domain@[0-9a-f]+$": 50 $ref: "#/$defs/power-domain-node" 51 patternProperties: 52 "^power-domain@[0-9a-f]+$": 53 $ref: "#/$defs/power-domain-node" 54 patternProperties: 55 "^power-domain@[0-9a-f]+$": 56 $ref: "#/$defs/power-domain-node" 57 unevaluatedProperties: false 58 unevaluatedProperties: false 59 unevaluatedProperties: false 60 unevaluatedProperties: false 61 62 $defs: 63 power-domain-node: 64 type: object 65 description: | 66 Represents the power domains within the power controller node as documented 67 in Documentation/devicetree/bindings/power/power-domain.yaml. 68 69 properties: 70 71 '#power-domain-cells': 72 description: 73 Must be 0 for nodes representing a single PM domain and 1 for nodes 74 providing multiple PM domains. 75 76 '#address-cells': 77 const: 1 78 79 '#size-cells': 80 const: 0 81 82 reg: 83 description: | 84 Power domain index. Valid values are defined in: 85 "include/dt-bindings/power/mt6795-power.h" - for MT8167 type power domain. 86 "include/dt-bindings/power/mt8167-power.h" - for MT8167 type power domain. 87 "include/dt-bindings/power/mt8173-power.h" - for MT8173 type power domain. 88 "include/dt-bindings/power/mt8183-power.h" - for MT8183 type power domain. 89 "include/dt-bindings/power/mediatek,mt8188-power.h" - for MT8188 type power domain. 90 "include/dt-bindings/power/mt8192-power.h" - for MT8192 type power domain. 91 "include/dt-bindings/power/mt8195-power.h" - for MT8195 type power domain. 92 "include/dt-bindings/power/mediatek,mt8365-power.h" - for MT8365 type power domain. 93 maxItems: 1 94 95 clocks: 96 description: | 97 A number of phandles to clocks that need to be enabled during domain 98 power-up sequencing. 99 100 clock-names: 101 description: | 102 List of names of clocks, in order to match the power-up sequencing 103 for each power domain we need to group the clocks by name. BASIC 104 clocks need to be enabled before enabling the corresponding power 105 domain, and should not have a '-' in their name (i.e mm, mfg, venc). 106 SUSBYS clocks need to be enabled before releasing the bus protection, 107 and should contain a '-' in their name (i.e mm-0, isp-0, cam-0). 108 109 In order to follow properly the power-up sequencing, the clocks must 110 be specified by order, adding first the BASIC clocks followed by the 111 SUSBSYS clocks. 112 113 domain-supply: 114 description: domain regulator supply. 115 116 mediatek,infracfg: 117 $ref: /schemas/types.yaml#/definitions/phandle 118 description: phandle to the device containing the INFRACFG register range. 119 120 mediatek,infracfg-nao: 121 $ref: /schemas/types.yaml#/definitions/phandle 122 description: phandle to the device containing the INFRACFG-NAO register range. 123 124 mediatek,smi: 125 $ref: /schemas/types.yaml#/definitions/phandle 126 description: phandle to the device containing the SMI register range. 127 > 128 mediatek,larb: > 129 $ref: /schemas/types.yaml#/definitions/phandle 130 description: phandle to the device containing the LARB register range. 131 132 required: 133 - reg 134 135 required: 136 - compatible 137 -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
