From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: [arm-integrator:b4/genexis-xg6846b-v6.17-rc1 8/9] arch/arm/boot/dts/broadcom/bcm6846-genexis-xg6846b.dts:236.20-300.4: Warning (avoid_unnecessary_addr_size): /bus@ff800000/mdio@2060/switch@0: unnecessary #address-cells/#size-cells without "ranges", "dma-ranges" or child "reg" property
Date: Sun, 31 Aug 2025 07:44:25 +0200 [thread overview]
Message-ID: <202508310706.2QfEVoNP-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
TO: Linus Walleij <linus.walleij@linaro.org>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-integrator.git b4/genexis-xg6846b-v6.17-rc1
head: e48e1a2def8a9105cfaf3ccbf10260bde3e75f78
commit: e948b107f985bc442fba9d1327b7f9e90cc6f960 [8/9] ARM: dts: bcm6846: Add I2C bus block
:::::: branch date: 2 days ago
:::::: commit date: 2 days ago
config: arm-randconfig-2052-20250830 (https://download.01.org/0day-ci/archive/20250831/202508310706.2QfEVoNP-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 8.5.0
dtschema version: 2025.8
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250831/202508310706.2QfEVoNP-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/202508310706.2QfEVoNP-lkp@intel.com/
dtcheck warnings: (new ones prefixed by >>)
>> arch/arm/boot/dts/broadcom/bcm6846-genexis-xg6846b.dts:236.20-300.4: Warning (avoid_unnecessary_addr_size): /bus@ff800000/mdio@2060/switch@0: unnecessary #address-cells/#size-cells without "ranges", "dma-ranges" or child "reg" property
arch/arm/boot/dts/broadcom/bcm6846-genexis-xg6846b.dtb: switch@0 (marvell,mv88e6085): Unevaluated properties are not allowed ('#address-cells', '#size-cells' were unexpected)
from schema $id: http://devicetree.org/schemas/net/dsa/marvell,mv88e6xxx.yaml#
arch/arm/boot/dts/broadcom/bcm6846-genexis-xg6846b.dtb: /bus@ff800000/i2c@2100: failed to match any schema with compatible: ['brcm,bcmbca-i2c']
vim +236 arch/arm/boot/dts/broadcom/bcm6846-genexis-xg6846b.dts
618775c9007d66 Linus Walleij 2024-10-19 232
618775c9007d66 Linus Walleij 2024-10-19 233 &mdio {
618775c9007d66 Linus Walleij 2024-10-19 234 status = "okay";
618775c9007d66 Linus Walleij 2024-10-19 235
2790c39bcadee0 Linus Walleij 2025-06-18 @236 switch0: switch@0 {
2790c39bcadee0 Linus Walleij 2025-06-18 237 /* Actually MV88E6320 revision 2 */
2790c39bcadee0 Linus Walleij 2025-06-18 238 compatible = "marvell,mv88e6085";
2790c39bcadee0 Linus Walleij 2025-06-18 239 #address-cells = <1>;
2790c39bcadee0 Linus Walleij 2025-06-18 240 #size-cells = <0>;
2790c39bcadee0 Linus Walleij 2025-06-18 241 reg = <0>;
2790c39bcadee0 Linus Walleij 2025-06-18 242
2790c39bcadee0 Linus Walleij 2025-06-18 243 interrupt-controller;
2790c39bcadee0 Linus Walleij 2025-06-18 244 #interrupt-cells = <2>;
2790c39bcadee0 Linus Walleij 2025-06-18 245
2790c39bcadee0 Linus Walleij 2025-06-18 246 ports {
2790c39bcadee0 Linus Walleij 2025-06-18 247 #address-cells = <1>;
2790c39bcadee0 Linus Walleij 2025-06-18 248 #size-cells = <0>;
2790c39bcadee0 Linus Walleij 2025-06-18 249
2790c39bcadee0 Linus Walleij 2025-06-18 250 port@0 {
2790c39bcadee0 Linus Walleij 2025-06-18 251 reg = <0>;
2790c39bcadee0 Linus Walleij 2025-06-18 252
2790c39bcadee0 Linus Walleij 2025-06-18 253 phy-mode = "sgmii";
2790c39bcadee0 Linus Walleij 2025-06-18 254 // ethernet = <?> the SGMII of BCM68460
2790c39bcadee0 Linus Walleij 2025-06-18 255 // also known as "serdes"
2790c39bcadee0 Linus Walleij 2025-06-18 256
2790c39bcadee0 Linus Walleij 2025-06-18 257 fixed-link {
2790c39bcadee0 Linus Walleij 2025-06-18 258 // TODO: can this do 2500?
2790c39bcadee0 Linus Walleij 2025-06-18 259 speed = <1000>;
2790c39bcadee0 Linus Walleij 2025-06-18 260 full-duplex;
2790c39bcadee0 Linus Walleij 2025-06-18 261 };
2790c39bcadee0 Linus Walleij 2025-06-18 262 };
2790c39bcadee0 Linus Walleij 2025-06-18 263
2790c39bcadee0 Linus Walleij 2025-06-18 264 port@1 {
2790c39bcadee0 Linus Walleij 2025-06-18 265 reg = <1>;
2790c39bcadee0 Linus Walleij 2025-06-18 266 label = "wan";
2790c39bcadee0 Linus Walleij 2025-06-18 267
2790c39bcadee0 Linus Walleij 2025-06-18 268 phy-mode = "rgmii-id";
2790c39bcadee0 Linus Walleij 2025-06-18 269 sfp = <&sfp0>;
2790c39bcadee0 Linus Walleij 2025-06-18 270
2790c39bcadee0 Linus Walleij 2025-06-18 271 fixed-link {
2790c39bcadee0 Linus Walleij 2025-06-18 272 // TODO: can this do 2500?
2790c39bcadee0 Linus Walleij 2025-06-18 273 speed = <1000>;
2790c39bcadee0 Linus Walleij 2025-06-18 274 full-duplex;
2790c39bcadee0 Linus Walleij 2025-06-18 275 };
2790c39bcadee0 Linus Walleij 2025-06-18 276 };
2790c39bcadee0 Linus Walleij 2025-06-18 277
2790c39bcadee0 Linus Walleij 2025-06-18 278 port@4 {
2790c39bcadee0 Linus Walleij 2025-06-18 279 reg = <4>;
2790c39bcadee0 Linus Walleij 2025-06-18 280 label = "wan/ext1";
2790c39bcadee0 Linus Walleij 2025-06-18 281 phy-mode = "rgmii";
2790c39bcadee0 Linus Walleij 2025-06-18 282 // I think the PHY adds the delay
2790c39bcadee0 Linus Walleij 2025-06-18 283 phy-handle = <&phy21>;
2790c39bcadee0 Linus Walleij 2025-06-18 284 };
2790c39bcadee0 Linus Walleij 2025-06-18 285
2790c39bcadee0 Linus Walleij 2025-06-18 286 port@6 {
2790c39bcadee0 Linus Walleij 2025-06-18 287 reg = <6>;
2790c39bcadee0 Linus Walleij 2025-06-18 288
2790c39bcadee0 Linus Walleij 2025-06-18 289 phy-mode = "rgmii-id";
2790c39bcadee0 Linus Walleij 2025-06-18 290 // ethernet = <?> the RGMII of BCM68460
2790c39bcadee0 Linus Walleij 2025-06-18 291 // From port n on the "brcm,enet"
2790c39bcadee0 Linus Walleij 2025-06-18 292 // UNIMAC driver
2790c39bcadee0 Linus Walleij 2025-06-18 293
2790c39bcadee0 Linus Walleij 2025-06-18 294 fixed-link {
2790c39bcadee0 Linus Walleij 2025-06-18 295 speed = <1000>;
2790c39bcadee0 Linus Walleij 2025-06-18 296 full-duplex;
2790c39bcadee0 Linus Walleij 2025-06-18 297 };
2790c39bcadee0 Linus Walleij 2025-06-18 298 };
2790c39bcadee0 Linus Walleij 2025-06-18 299 };
2790c39bcadee0 Linus Walleij 2025-06-18 300 };
2790c39bcadee0 Linus Walleij 2025-06-18 301
2790c39bcadee0 Linus Walleij 2025-06-18 302 /* These PHYs have ID 0xae0251e1 called "bca_phy" in the source */
618775c9007d66 Linus Walleij 2024-10-19 303 phy1: ethernet-phy@1 {
2790c39bcadee0 Linus Walleij 2025-06-18 304 // Port 0 on the enet/UNIMAC
618775c9007d66 Linus Walleij 2024-10-19 305 reg = <1>;
618775c9007d66 Linus Walleij 2024-10-19 306 };
618775c9007d66 Linus Walleij 2024-10-19 307 phy2: ethernet-phy@2 {
2790c39bcadee0 Linus Walleij 2025-06-18 308 // Port 1 on the enet/UNIMAC
618775c9007d66 Linus Walleij 2024-10-19 309 reg = <2>;
618775c9007d66 Linus Walleij 2024-10-19 310 };
618775c9007d66 Linus Walleij 2024-10-19 311 phy3: ethernet-phy@3 {
2790c39bcadee0 Linus Walleij 2025-06-18 312 // Port 2 on the enet/UNIMAC
618775c9007d66 Linus Walleij 2024-10-19 313 reg = <3>;
618775c9007d66 Linus Walleij 2024-10-19 314 };
618775c9007d66 Linus Walleij 2024-10-19 315 phy4: ethernet-phy@4 {
2790c39bcadee0 Linus Walleij 2025-06-18 316 // Port 3 on the enet/UNIMAC
618775c9007d66 Linus Walleij 2024-10-19 317 reg = <4>;
618775c9007d66 Linus Walleij 2024-10-19 318 };
2790c39bcadee0 Linus Walleij 2025-06-18 319
2790c39bcadee0 Linus Walleij 2025-06-18 320 /* This external PHY used for wan/ext1 has ID 0xff001152 */
618775c9007d66 Linus Walleij 2024-10-19 321 phy21: ethernet-phy@21 {
2790c39bcadee0 Linus Walleij 2025-06-18 322 // Port 4 on the MV88E6320
618775c9007d66 Linus Walleij 2024-10-19 323 reg = <21>;
2790c39bcadee0 Linus Walleij 2025-06-18 324 // Vendor device tree says RX and TX are delayed in the PHY
2790c39bcadee0 Linus Walleij 2025-06-18 325 // but not by how much.
2790c39bcadee0 Linus Walleij 2025-06-18 326 rx-internal-delay-ps = <2000>;
2790c39bcadee0 Linus Walleij 2025-06-18 327 tx-internal-delay-ps = <2000>;
2790c39bcadee0 Linus Walleij 2025-06-18 328 };
618775c9007d66 Linus Walleij 2024-10-19 329 };
2790c39bcadee0 Linus Walleij 2025-06-18 330
:::::: The code at line 236 was first introduced by commit
:::::: 2790c39bcadee0a009f6f6809a66f94c21b2e2ca ARM: dts: bcm6846: Add Marvell switch and SFP
:::::: TO: Linus Walleij <linus.walleij@linaro.org>
:::::: CC: Linus Walleij <linus.walleij@linaro.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-08-31 5:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202508310706.2QfEVoNP-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.