From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [chrome-os:chromeos-6.6 333/333] arch/arm64/boot/dts/mediatek/mt8196-evb.dts:19.27-26.4: Warning (unit_address_vs_reg): /regulator@0: node has a unit name, but no reg or ranges property
Date: Mon, 20 Jan 2025 06:43:42 +0800 [thread overview]
Message-ID: <202501200630.EGRZ2Zlc-lkp@intel.com> (raw)
tree: https://chromium.googlesource.com/chromiumos/third_party/kernel chromeos-6.6
head: 2fd541a9d43eceddbb3b4bfd2872a1655f335e09
commit: 1468cdcfa0ac2513ba51ea93a575e951453e928f [333/333] CHROMIUM: arm64: dts: mt8196: Add usb dts
config: arm64-randconfig-001-20250120 (https://download.01.org/0day-ci/archive/20250120/202501200630.EGRZ2Zlc-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250120/202501200630.EGRZ2Zlc-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/oe-kbuild-all/202501200630.EGRZ2Zlc-lkp@intel.com/
dtcheck warnings: (new ones prefixed by >>)
>> arch/arm64/boot/dts/mediatek/mt8196-evb.dts:19.27-26.4: Warning (unit_address_vs_reg): /regulator@0: node has a unit name, but no reg or ranges property
arch/arm64/boot/dts/mediatek/mt8196.dtsi:569.37-594.5: Warning (avoid_unnecessary_addr_size): /soc/interrupt-controller@c400000: unnecessary #address-cells/#size-cells without "ranges" or child "reg" property
vim +19 arch/arm64/boot/dts/mediatek/mt8196-evb.dts
9
10 / {
11 model = "MediaTek MT8196 evaluation board";
12 compatible = "mediatek,mt8196-evb", "mediatek,mt8196";
13
14 /* chosen */
15 chosen: chosen {
16 stdout-path = "serial0:115200n8";
17 };
18
> 19 usb_p0_vbus: regulator@0 {
20 compatible = "regulator-fixed";
21 regulator-name = "vbus";
22 regulator-min-microvolt = <5000000>;
23 regulator-max-microvolt = <5000000>;
24 gpio = <&pio 20 GPIO_ACTIVE_HIGH>;
25 enable-active-high;
26 };
27 };
28
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-01-19 22:43 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=202501200630.EGRZ2Zlc-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.com \
--cc=oe-kbuild-all@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.