From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH] ARM: dts: qcom: nexus7: remove vcss supply which never existed
Date: Mon, 27 Dec 2021 11:41:17 +0800 [thread overview]
Message-ID: <202112271106.grB2oAxg-lkp@intel.com> (raw)
In-Reply-To: <20211225212000.80459-1-david@ixit.cz>
[-- Attachment #1: Type: text/plain, Size: 3526 bytes --]
Hi David,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on robh/for-next]
[also build test WARNING on linux/master linus/master v5.16-rc6 next-20211224]
[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]
url: https://github.com/0day-ci/linux/commits/David-Heidelberg/ARM-dts-qcom-nexus7-remove-vcss-supply-which-never-existed/20211226-052117
base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next
compiler: arm-linux-gnueabi-gcc (GCC) 11.2.0
reproduce: make ARCH=arm dtbs_check
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
dtcheck warnings: (new ones prefixed by >>)
arch/arm/boot/dts/qcom-apq8064-asus-nexus7-flo.dt.yaml: mdss_dsi(a)4700000: assigned-clocks: [[65, 83], [65, 87], [65, 56], [65, 105]] is too long
From schema: Documentation/devicetree/bindings/display/msm/dsi-controller-main.yaml
arch/arm/boot/dts/qcom-apq8064-asus-nexus7-flo.dt.yaml: mdss_dsi(a)4700000: assigned-clock-parents: [[69, 0], [69, 0], [69, 1], [69, 1]] is too long
From schema: Documentation/devicetree/bindings/display/msm/dsi-controller-main.yaml
arch/arm/boot/dts/qcom-apq8064-asus-nexus7-flo.dt.yaml: mdss_dsi(a)4700000: 'phy-names' is a required property
From schema: Documentation/devicetree/bindings/display/msm/dsi-controller-main.yaml
arch/arm/boot/dts/qcom-apq8064-asus-nexus7-flo.dt.yaml: mdss_dsi(a)4700000: 'power-domains' is a required property
From schema: Documentation/devicetree/bindings/display/msm/dsi-controller-main.yaml
arch/arm/boot/dts/qcom-apq8064-asus-nexus7-flo.dt.yaml: mdss_dsi(a)4700000: 'operating-points-v2' is a required property
From schema: Documentation/devicetree/bindings/display/msm/dsi-controller-main.yaml
>> arch/arm/boot/dts/qcom-apq8064-asus-nexus7-flo.dt.yaml: mdss_dsi(a)4700000: 'avdd-supply', 'label', 'panel(a)0', 'vdd-supply', 'vdda-supply', 'vddio-supply' do not match any of the regexes: 'pinctrl-[0-9]+'
From schema: Documentation/devicetree/bindings/display/msm/dsi-controller-main.yaml
arch/arm/boot/dts/qcom-apq8064-asus-nexus7-flo.dt.yaml: panel(a)0: 'port' does not match any of the regexes: 'pinctrl-[0-9]+'
From schema: Documentation/devicetree/bindings/display/panel/jdi,lt070me05000.yaml
arch/arm/boot/dts/qcom-apq8064-asus-nexus7-flo.dt.yaml: dsi-phy(a)4700200: clock-names:0: 'iface' was expected
From schema: Documentation/devicetree/bindings/display/msm/dsi-phy-28nm.yaml
arch/arm/boot/dts/qcom-apq8064-asus-nexus7-flo.dt.yaml: dsi-phy(a)4700200: Unevaluated properties are not allowed ('#clock-cells', '#phy-cells', 'clock-names', 'clocks' were unexpected)
From schema: Documentation/devicetree/bindings/display/msm/dsi-phy-28nm.yaml
arch/arm/boot/dts/qcom-apq8064-asus-nexus7-flo.dt.yaml:0:0: /soc/iommu(a)7500000: failed to match any schema with compatible: ['qcom,apq8064-iommu']
arch/arm/boot/dts/qcom-apq8064-asus-nexus7-flo.dt.yaml:0:0: /soc/iommu(a)7600000: failed to match any schema with compatible: ['qcom,apq8064-iommu']
arch/arm/boot/dts/qcom-apq8064-asus-nexus7-flo.dt.yaml:0:0: /soc/iommu(a)7c00000: failed to match any schema with compatible: ['qcom,apq8064-iommu']
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
next prev parent reply other threads:[~2021-12-27 3:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-25 21:20 [PATCH] ARM: dts: qcom: nexus7: remove vcss supply which never existed David Heidelberg
2021-12-27 3:41 ` kernel test robot [this message]
2022-02-01 5:19 ` (subset) " Bjorn Andersson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=202112271106.grB2oAxg-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.