From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: Re: [PATCH 2/2] arm64: dts: rockchip: add Firefly CORE PX30 JD4
Date: Wed, 17 Jul 2024 05:59:39 +0800 [thread overview]
Message-ID: <202407170524.Pc8MMP6B-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "dtcheck: binding changes may go via different trees"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <20240716-rockchip-px30-firefly-v1-2-60cdad3023a3@collabora.com>
References: <20240716-rockchip-px30-firefly-v1-2-60cdad3023a3@collabora.com>
TO: Christopher Obbard <chris.obbard@collabora.com>
TO: Rob Herring <robh@kernel.org>
TO: Krzysztof Kozlowski <krzk@kernel.org>
TO: Conor Dooley <conor+dt@kernel.org>
TO: Heiko Stuebner <heiko@sntech.de>
CC: devicetree@vger.kernel.org
CC: linux-arm-kernel@lists.infradead.org
CC: linux-rockchip@lists.infradead.org
CC: linux-kernel@vger.kernel.org
CC: Kever Yang <kever.yang@rock-chips.com>
CC: Christopher Obbard <chris.obbard@collabora.com>
Hi Christopher,
kernel test robot noticed the following build warnings:
[auto build test WARNING on d67978318827d06f1c0fa4c31343a279e9df6fde]
url: https://github.com/intel-lab-lkp/linux/commits/Christopher-Obbard/dt-bindings-arm-rockchip-add-Firefly-CORE-PX30-JD4/20240717-042608
base: d67978318827d06f1c0fa4c31343a279e9df6fde
patch link: https://lore.kernel.org/r/20240716-rockchip-px30-firefly-v1-2-60cdad3023a3%40collabora.com
patch subject: [PATCH 2/2] arm64: dts: rockchip: add Firefly CORE PX30 JD4
:::::: branch date: 2 hours ago
:::::: commit date: 2 hours ago
config: arm64-randconfig-051-20240717 (https://download.01.org/0day-ci/archive/20240717/202407170524.Pc8MMP6B-lkp@intel.com/config)
compiler: clang version 14.0.6 (https://github.com/llvm/llvm-project f28c006a5895fc0e329fe15fead81e37457cb1d1)
dtschema version: 2024.6.dev4+g23441a4
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240717/202407170524.Pc8MMP6B-lkp@intel.com/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@intel.com>
| Closes: https://lore.kernel.org/r/202407170524.Pc8MMP6B-lkp@intel.com/
dtcheck warnings: (new ones prefixed by >>)
arch/arm64/boot/dts/rockchip/px30.dtsi:351.26-371.4: Warning (avoid_unnecessary_addr_size): /syscon@ff010000: unnecessary #address-cells/#size-cells without "ranges" or child "reg" property
arch/arm64/boot/dts/rockchip/px30.dtsi:453.23-497.4: Warning (avoid_unnecessary_addr_size): /syscon@ff140000: unnecessary #address-cells/#size-cells without "ranges" or child "reg" property
>> arch/arm64/boot/dts/rockchip/px30-firefly-core-px30-jd4.dts:142.9-153.5: Warning (graph_child_address): /dsi@ff450000/panel@0/ports: graph node has single child node 'port@0', #address-cells/#size-cells are not necessary
>> arch/arm64/boot/dts/rockchip/px30-firefly-core-px30-jd4.dtb: /dsi@ff450000/panel@0: failed to match any schema with compatible: ['sitronix,st7703']
vim +142 arch/arm64/boot/dts/rockchip/px30-firefly-core-px30-jd4.dts
28e7b005c693279 Christopher Obbard 2024-07-16 121
28e7b005c693279 Christopher Obbard 2024-07-16 122 &dsi {
28e7b005c693279 Christopher Obbard 2024-07-16 123 status = "okay";
28e7b005c693279 Christopher Obbard 2024-07-16 124
28e7b005c693279 Christopher Obbard 2024-07-16 125 ports {
28e7b005c693279 Christopher Obbard 2024-07-16 126 mipi_out: port@1 {
28e7b005c693279 Christopher Obbard 2024-07-16 127 reg = <1>;
28e7b005c693279 Christopher Obbard 2024-07-16 128
28e7b005c693279 Christopher Obbard 2024-07-16 129 mipi_out_panel: endpoint {
28e7b005c693279 Christopher Obbard 2024-07-16 130 remote-endpoint = <&mipi_in_panel>;
28e7b005c693279 Christopher Obbard 2024-07-16 131 };
28e7b005c693279 Christopher Obbard 2024-07-16 132 };
28e7b005c693279 Christopher Obbard 2024-07-16 133 };
28e7b005c693279 Christopher Obbard 2024-07-16 134
28e7b005c693279 Christopher Obbard 2024-07-16 135 panel@0 {
28e7b005c693279 Christopher Obbard 2024-07-16 136 compatible = "sitronix,st7703";
28e7b005c693279 Christopher Obbard 2024-07-16 137 reg = <0>;
28e7b005c693279 Christopher Obbard 2024-07-16 138 backlight = <&backlight>;
28e7b005c693279 Christopher Obbard 2024-07-16 139 iovcc-supply = <&vcc_1v8>;
28e7b005c693279 Christopher Obbard 2024-07-16 140 vci-supply = <&vcc3v3_lcd>;
28e7b005c693279 Christopher Obbard 2024-07-16 141
28e7b005c693279 Christopher Obbard 2024-07-16 @142 ports {
28e7b005c693279 Christopher Obbard 2024-07-16 143 #address-cells = <1>;
28e7b005c693279 Christopher Obbard 2024-07-16 144 #size-cells = <0>;
28e7b005c693279 Christopher Obbard 2024-07-16 145
28e7b005c693279 Christopher Obbard 2024-07-16 146 port@0 {
28e7b005c693279 Christopher Obbard 2024-07-16 147 reg = <0>;
28e7b005c693279 Christopher Obbard 2024-07-16 148
28e7b005c693279 Christopher Obbard 2024-07-16 149 mipi_in_panel: endpoint {
28e7b005c693279 Christopher Obbard 2024-07-16 150 remote-endpoint = <&mipi_out_panel>;
28e7b005c693279 Christopher Obbard 2024-07-16 151 };
28e7b005c693279 Christopher Obbard 2024-07-16 152 };
28e7b005c693279 Christopher Obbard 2024-07-16 153 };
28e7b005c693279 Christopher Obbard 2024-07-16 154 };
28e7b005c693279 Christopher Obbard 2024-07-16 155 };
28e7b005c693279 Christopher Obbard 2024-07-16 156
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2024-07-16 22:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-16 21:59 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-16 15:51 [PATCH 0/2] Add support for Firefly CORE PX30 JD4 Christopher Obbard
2024-07-16 15:51 ` [PATCH 2/2] arm64: dts: rockchip: add " Christopher Obbard
2024-07-16 15:51 ` Christopher Obbard
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=202407170524.Pc8MMP6B-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild@lists.linux.dev \
/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.