From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: Re: [PATCH V2 5/5] arm64: dts: rockchip: Add USB and charger to Gameforce Ace
Date: Sun, 22 Jun 2025 17:32:31 +0800 [thread overview]
Message-ID: <202506221723.IkyezPLC-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: <20250621180119.163423-6-macroalpha82@gmail.com>
References: <20250621180119.163423-6-macroalpha82@gmail.com>
TO: Chris Morgan <macroalpha82@gmail.com>
TO: linux-pm@vger.kernel.org
CC: linux-rockchip@lists.infradead.org
CC: devicetree@vger.kernel.org
CC: broonie@kernel.org
CC: lgirdwood@gmail.com
CC: sre@kernel.org
CC: heiko@sntech.de
CC: conor+dt@kernel.org
CC: krzk+dt@kernel.org
CC: robh@kernel.org
CC: lee@kernel.org
CC: Chris Morgan <macromorgan@hotmail.com>
Hi Chris,
kernel test robot noticed the following build warnings:
[auto build test WARNING on lee-mfd/for-mfd-next]
[also build test WARNING on lee-mfd/for-mfd-fixes broonie-regulator/for-next sre-power-supply/for-next linus/master v6.16-rc2]
[cannot apply to next-20250620]
[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-mfd-ti-bq25703a-Add-TI-BQ25703A-Charger/20250622-020443
base: https://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git for-mfd-next
patch link: https://lore.kernel.org/r/20250621180119.163423-6-macroalpha82%40gmail.com
patch subject: [PATCH V2 5/5] arm64: dts: rockchip: Add USB and charger to Gameforce Ace
:::::: branch date: 15 hours ago
:::::: commit date: 15 hours ago
config: arm64-randconfig-001-20250622 (https://download.01.org/0day-ci/archive/20250622/202506221723.IkyezPLC-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 9.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250622/202506221723.IkyezPLC-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/202506221723.IkyezPLC-lkp@intel.com/
dtcheck warnings: (new ones prefixed by >>)
>> arch/arm64/boot/dts/rockchip/rk3588s-gameforce-ace.dts:1329.7-1336.4: Warning (graph_child_address): /usb@fc000000/port: graph node has single child node 'endpoint@0', #address-cells/#size-cells are not necessary
vim +1329 arch/arm64/boot/dts/rockchip/rk3588s-gameforce-ace.dts
3b1465b25894b6 Chris Morgan 2025-06-21 1324
3b1465b25894b6 Chris Morgan 2025-06-21 1325 &usb_host0_xhci {
3b1465b25894b6 Chris Morgan 2025-06-21 1326 usb-role-switch;
3b1465b25894b6 Chris Morgan 2025-06-21 1327 status = "okay";
3b1465b25894b6 Chris Morgan 2025-06-21 1328
3b1465b25894b6 Chris Morgan 2025-06-21 @1329 port {
3b1465b25894b6 Chris Morgan 2025-06-21 1330 #address-cells = <1>;
3b1465b25894b6 Chris Morgan 2025-06-21 1331 #size-cells = <0>;
3b1465b25894b6 Chris Morgan 2025-06-21 1332 dwc3_0_role_switch: endpoint@0 {
3b1465b25894b6 Chris Morgan 2025-06-21 1333 reg = <0>;
3b1465b25894b6 Chris Morgan 2025-06-21 1334 remote-endpoint = <&usbc0_role_sw>;
3b1465b25894b6 Chris Morgan 2025-06-21 1335 };
3b1465b25894b6 Chris Morgan 2025-06-21 1336 };
3b1465b25894b6 Chris Morgan 2025-06-21 1337 };
3b1465b25894b6 Chris Morgan 2025-06-21 1338
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2025-06-22 9:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-22 9:32 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-06-21 18:01 [PATCH V2 0/5] Add Texas Instruments BQ25703A Charger Chris Morgan
2025-06-21 18:01 ` [PATCH V2 5/5] arm64: dts: rockchip: Add USB and charger to Gameforce Ace Chris Morgan
2025-06-21 18:01 ` 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=202506221723.IkyezPLC-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.