From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: Re: [PATCH V2 1/2 RESEND] arm64: dts: rockchip: Add DTS for FriendlyARM NanoPi R2S Plus
Date: Sat, 3 Aug 2024 12:53:48 +0800 [thread overview]
Message-ID: <202408031252.KrHshVrx-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: <20240801175736.16591-2-jin@mediatomb.cc>
References: <20240801175736.16591-2-jin@mediatomb.cc>
TO: Sergey Bostandzhyan <jin@mediatomb.cc>
TO: robh@kernel.org
TO: krzk+dt@kernel.org
TO: conor+dt@kernel.org
TO: 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: Sergey Bostandzhyan <jin@mediatomb.cc>
Hi Sergey,
kernel test robot noticed the following build warnings:
[auto build test WARNING on robh/for-next]
[also build test WARNING on rockchip/for-next linus/master v6.11-rc1 next-20240802]
[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/Sergey-Bostandzhyan/arm64-dts-rockchip-Add-DTS-for-FriendlyARM-NanoPi-R2S-Plus/20240803-025302
base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next
patch link: https://lore.kernel.org/r/20240801175736.16591-2-jin%40mediatomb.cc
patch subject: [PATCH V2 1/2 RESEND] arm64: dts: rockchip: Add DTS for FriendlyARM NanoPi R2S Plus
:::::: branch date: 10 hours ago
:::::: commit date: 10 hours ago
config: arm64-randconfig-051-20240803 (https://download.01.org/0day-ci/archive/20240803/202408031252.KrHshVrx-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 14.1.0
dtschema version: 2024.6.dev8+gf13c181
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240803/202408031252.KrHshVrx-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/202408031252.KrHshVrx-lkp@intel.com/
dtcheck warnings: (new ones prefixed by >>)
'rockchip,px3' was expected
'rockchip,px30' was expected
'rockchip,px5' was expected
'rockchip,rk3228' was expected
'tsd,rk3588-tiger' was expected
'xunlong,orangepi-3b' was expected
'rockchip,rk3318' was expected
'rockchip,rk3328' is not one of ['rockchip,rv1126', 'rockchip,rv1109']
from schema $id: http://devicetree.org/schemas/arm/rockchip.yaml#
arch/arm64/boot/dts/rockchip/rk3328-nanopi-r2s-plus.dtb: /: failed to match any schema with compatible: ['friendlyarm,nanopi-r2s-plus', 'rockchip,rk3328']
>> arch/arm64/boot/dts/rockchip/rk3328-nanopi-r2s-plus.dtb: hdmi@ff3c0000: interrupts: [[0, 35, 4], [0, 71, 4]] is too long
from schema $id: http://devicetree.org/schemas/display/rockchip/rockchip,dw-hdmi.yaml#
>> arch/arm64/boot/dts/rockchip/rk3328-nanopi-r2s-plus.dtb: /phy@ff430000: failed to match any schema with compatible: ['rockchip,rk3328-hdmi-phy']
>> arch/arm64/boot/dts/rockchip/rk3328-nanopi-r2s-plus.dtb: /clock-controller@ff440000: failed to match any schema with compatible: ['rockchip,rk3328-cru', 'rockchip,cru', 'syscon']
>> arch/arm64/boot/dts/rockchip/rk3328-nanopi-r2s-plus.dtb: /clock-controller@ff440000: failed to match any schema with compatible: ['rockchip,rk3328-cru', 'rockchip,cru', 'syscon']
>> arch/arm64/boot/dts/rockchip/rk3328-nanopi-r2s-plus.dtb: mmc@ff520000: Unevaluated properties are not allowed ('num-slots', 'supports-emmc' were unexpected)
from schema $id: http://devicetree.org/schemas/mmc/rockchip-dw-mshc.yaml#
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2024-08-03 4:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-03 4:53 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-08-01 8:10 [PATCH 2/2] dt-bindings: arm: rockchip: Add NanoPi R2S Plus Krzysztof Kozlowski
2024-08-01 17:57 ` [PATCH V2 0/2 RESEND] Add DTS for " Sergey Bostandzhyan
2024-08-01 17:57 ` [PATCH V2 1/2 RESEND] arm64: dts: rockchip: Add DTS for FriendlyARM " Sergey Bostandzhyan
2024-08-01 17:57 ` Sergey Bostandzhyan
2024-08-04 0:27 ` Daniel Golle
2024-08-04 0:27 ` Daniel Golle
2024-08-05 8:59 ` Sergey 'Jin' Bostandzhyan
2024-08-05 8:59 ` Sergey 'Jin' Bostandzhyan
2024-08-10 19:11 ` Heiko Stübner
2024-08-10 19:11 ` Heiko Stübner
2024-08-14 11:21 ` Sergey 'Jin' Bostandzhyan
2024-08-14 11:21 ` Sergey 'Jin' Bostandzhyan
2024-08-14 11:30 ` Diederik de Haas
2024-08-14 11:30 ` Diederik de Haas
2024-08-14 11:34 ` Diederik de Haas
2024-08-14 11:34 ` Diederik de Haas
2024-08-14 11:36 ` Heiko Stübner
2024-08-14 11:36 ` Heiko Stübner
2024-08-14 12:24 ` Sergey 'Jin' Bostandzhyan
2024-08-14 12:24 ` Sergey 'Jin' Bostandzhyan
2024-08-14 13:53 ` Heiko Stübner
2024-08-14 13:53 ` Heiko Stübner
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=202408031252.KrHshVrx-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.