All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: Re: [PATCH 5/5] arm64: dts: rockchip: Add GameForce Ace
Date: Sat, 27 Jul 2024 06:33:00 +0800	[thread overview]
Message-ID: <202407270618.OlatBL39-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: <20240726194948.109326-6-macroalpha82@gmail.com>
References: <20240726194948.109326-6-macroalpha82@gmail.com>
TO: Chris Morgan <macroalpha82@gmail.com>
TO: linux-rockchip@lists.infradead.org
CC: linux-pm@vger.kernel.org
CC: devicetree@vger.kernel.org
CC: jagan@edgeble.ai
CC: andyshrk@163.com
CC: jonas@kwiboo.se
CC: sre@kernel.org
CC: t.schramm@manjaro.org
CC: heiko@sntech.de
CC: conor+dt@kernel.org
CC: krzk+dt@kernel.org
CC: robh@kernel.org
CC: Chris Morgan <macromorgan@hotmail.com>

Hi Chris,

kernel test robot noticed the following build warnings:

[auto build test WARNING on rockchip/for-next]
[also build test WARNING on linus/master next-20240726]
[cannot apply to sre-power-supply/for-next robh/for-next amd-pstate/linux-next amd-pstate/bleeding-edge v6.10]
[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/Chris-Morgan/dt-bindings-power-supply-add-dual-cell-for-cw2015/20240727-035838
base:   https://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git for-next
patch link:    https://lore.kernel.org/r/20240726194948.109326-6-macroalpha82%40gmail.com
patch subject: [PATCH 5/5] arm64: dts: rockchip: Add GameForce Ace
:::::: branch date: 3 hours ago
:::::: commit date: 3 hours ago
config: arm64-randconfig-051-20240727 (https://download.01.org/0day-ci/archive/20240727/202407270618.OlatBL39-lkp@intel.com/config)
compiler: clang version 20.0.0git (https://github.com/llvm/llvm-project ccae7b461be339e717d02f99ac857cf0bc7d17fc)
dtschema version: 2024.6.dev4+g23441a4
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240727/202407270618.OlatBL39-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/202407270618.OlatBL39-lkp@intel.com/

dtcheck warnings: (new ones prefixed by >>)
>> arch/arm64/boot/dts/rockchip/rk3588s-gameforce-ace.dts:1283.7-1290.4: Warning (graph_child_address): /usb@fc000000/port: graph node has single child node 'endpoint@0', #address-cells/#size-cells are not necessary
>> arch/arm64/boot/dts/rockchip/rk3588s-gameforce-ace.dtb: typec-portc@22: 'vbus-supply' is a required property
   	from schema $id: http://devicetree.org/schemas/usb/fcs,fusb302.yaml#
>> arch/arm64/boot/dts/rockchip/rk3588s-gameforce-ace.dtb: /pwm-33: failed to match any schema with compatible: ['pwm-gpio']
   arch/arm64/boot/dts/rockchip/rk3588s-gameforce-ace.dtb: /pwm-132: failed to match any schema with compatible: ['pwm-gpio']

vim +1283 arch/arm64/boot/dts/rockchip/rk3588s-gameforce-ace.dts

aaec004564226b Chris Morgan 2024-07-26  1277  
aaec004564226b Chris Morgan 2024-07-26  1278  &usb_host0_xhci {
aaec004564226b Chris Morgan 2024-07-26  1279  	dr_mode = "otg";
aaec004564226b Chris Morgan 2024-07-26  1280  	usb-role-switch;
aaec004564226b Chris Morgan 2024-07-26  1281  	status = "okay";
aaec004564226b Chris Morgan 2024-07-26  1282  
aaec004564226b Chris Morgan 2024-07-26 @1283  	port {
aaec004564226b Chris Morgan 2024-07-26  1284  		#address-cells = <1>;
aaec004564226b Chris Morgan 2024-07-26  1285  		#size-cells = <0>;
aaec004564226b Chris Morgan 2024-07-26  1286  		dwc3_0_role_switch: endpoint@0 {
aaec004564226b Chris Morgan 2024-07-26  1287  			reg = <0>;
aaec004564226b Chris Morgan 2024-07-26  1288  			remote-endpoint = <&usbc0_role_sw>;
aaec004564226b Chris Morgan 2024-07-26  1289  		};
aaec004564226b Chris Morgan 2024-07-26  1290  	};
aaec004564226b Chris Morgan 2024-07-26  1291  };
aaec004564226b Chris Morgan 2024-07-26  1292  

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

             reply	other threads:[~2024-07-26 22:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-26 22:33 kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-07-26 19:49 [PATCH 0/5] Add GameForce Ace Chris Morgan
2024-07-26 19:49 ` [PATCH 5/5] arm64: dts: rockchip: " Chris Morgan
2024-07-26 19:49   ` Chris Morgan

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=202407270618.OlatBL39-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.