From: kernel test robot <lkp@intel.com>
To: Dongjin Kim <tobetter@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [tobetter:odroid-6.1.y 87/91] arch/arm64/boot/dts/rockchip/overlays/odroidm1s/display_vu5s.dts:61.15-66.5: Warning (unit_address_vs_reg): /fragment@3/__overlay__: node has a reg or ranges property, but no unit name
Date: Sat, 15 Jun 2024 03:03:35 +0800 [thread overview]
Message-ID: <202406150336.gT7VC5da-lkp@intel.com> (raw)
tree: https://github.com/tobetter/linux odroid-6.1.y
head: a50c6922e2b4c1d7c895bde521d13096ba16a863
commit: b3726159d0e7eb27996b0dc0c4f5fccd182a6b25 [87/91] ODROID-M1S: dtb/dtbo: add device tree for ODROID-Vu5S
config: arm64-allnoconfig (https://download.01.org/0day-ci/archive/20240615/202406150336.gT7VC5da-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240615/202406150336.gT7VC5da-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/202406150336.gT7VC5da-lkp@intel.com/
dtcheck warnings: (new ones prefixed by >>)
>> arch/arm64/boot/dts/rockchip/overlays/odroidm1s/display_vu5s.dts:61.15-66.5: Warning (unit_address_vs_reg): /fragment@3/__overlay__: node has a reg or ranges property, but no unit name
vim +61 arch/arm64/boot/dts/rockchip/overlays/odroidm1s/display_vu5s.dts
10
11 /{
12 fragment@0 {
13 target = <&backlight>;
14
15 __overlay__ {
16 status = "okay";
17 brightness-levels = <
18 1 2 3 4 5 6 7 8
19 9 10 11 12 13 14 15 16
20 17 18 19 20 21 22 23 24
21 25 26 27 28 29 30 31 32
22 33 34 35 36 37 38 39 40
23 41 42 43 44 45 46 47 48
24 49 50 51 52 53 54 55 56
25 57 58 59 60 61 62 63 64
26 65 66 67 68 69 70 71 72
27 73 74 75 76 77 78 79 80
28 81 82 83 84 85 86 87 88
29 89 90 91 92 93 94 95 96
30 97 98 99 100 101 102 103 104
31 105 106 107 108 109 110 111 112
32 113 114 115 116 117 118 119 120
33 121 122 123 124 125 126 127 128
34 >;
35 default-brightness-level = <64>;
36 };
37 };
38
39 fragment@1 {
40 target = <&pwm4>;
41
42 __overlay__ {
43 status = "okay";
44 };
45 };
46
47 fragment@2 {
48 target = <&i2c2>;
49
50 __overlay__ {
51 status = "okay";
52 };
53 };
54
55 fragment@3 {
56 target = <&touchscreen>;
57
58 #address-cells = <1>;
59 #size-cells = <0>;
60
> 61 __overlay__ {
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2024-06-14 19:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 19:03 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-14 9:37 [tobetter:odroid-6.1.y 87/91] arch/arm64/boot/dts/rockchip/overlays/odroidm1s/display_vu5s.dts:61.15-66.5: Warning (unit_address_vs_reg): /fragment@3/__overlay__: node has a reg or ranges property, but no unit name kernel test robot
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=202406150336.gT7VC5da-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tobetter@gmail.com \
/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.