From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: Re: [PATCH 10/11] ARM: dts: mediatek: add basic support for JTY D101 board
Date: Tue, 24 Jun 2025 09:36:26 +0800 [thread overview]
Message-ID: <202506241126.td9jarBJ-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: <20250620-mt6572-v1-10-e2d47820f042@proton.me>
References: <20250620-mt6572-v1-10-e2d47820f042@proton.me>
TO: Max Shevchenko via B4 Relay <devnull+wctrl.proton.me@kernel.org>
TO: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
TO: Jiri Slaby <jirislaby@kernel.org>
TO: Rob Herring <robh@kernel.org>
TO: Krzysztof Kozlowski <krzk@kernel.org>
TO: Conor Dooley <conor+dt@kernel.org>
TO: Matthias Brugger <matthias.bgg@gmail.com>
TO: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
TO: Thomas Gleixner <tglx@linutronix.de>
TO: Daniel Lezcano <daniel.lezcano@linaro.org>
TO: Wim Van Sebroeck <wim@linux-watchdog.org>
TO: Guenter Roeck <linux@roeck-us.net>
TO: Sean Wang <sean.wang@mediatek.com>
TO: Russell King <linux@armlinux.org.uk>
CC: linux-kernel@vger.kernel.org
CC: linux-serial@vger.kernel.org
CC: devicetree@vger.kernel.org
CC: linux-arm-kernel@lists.infradead.org
CC: linux-mediatek@lists.infradead.org
CC: linux-watchdog@vger.kernel.org
CC: Max Shevchenko <wctrl@proton.me>
Hi Max,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 0ff41df1cb268fc69e703a08a57ee14ae967d0ca]
url: https://github.com/intel-lab-lkp/linux/commits/Max-Shevchenko-via-B4-Relay/dt-bindings-serial-mediatek-uart-add-MT6572/20250620-234721
base: 0ff41df1cb268fc69e703a08a57ee14ae967d0ca
patch link: https://lore.kernel.org/r/20250620-mt6572-v1-10-e2d47820f042%40proton.me
patch subject: [PATCH 10/11] ARM: dts: mediatek: add basic support for JTY D101 board
:::::: branch date: 4 days ago
:::::: commit date: 4 days ago
config: arm-randconfig-051-20250621 (https://download.01.org/0day-ci/archive/20250624/202506241126.td9jarBJ-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 8.5.0
dtschema version: 2025.6.1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250624/202506241126.td9jarBJ-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/202506241126.td9jarBJ-lkp@intel.com/
dtcheck warnings: (new ones prefixed by >>)
>> arch/arm/boot/dts/mediatek/mt6572-jty-d101.dts:22.37-30.5: Warning (unit_address_vs_reg): /chosen/framebuffer@bf400000: node has a unit name, but no reg or ranges property
>> arch/arm/boot/dts/mediatek/mt6572-jty-d101.dts:33.9-36.4: Warning (unit_address_vs_reg): /memory: node has a reg or ranges property, but no unit name
>> arch/arm/boot/dts/mediatek/mt6572-jty-d101.dts:17.9-31.4: Warning (avoid_unnecessary_addr_size): /chosen: unnecessary #address-cells/#size-cells without "ranges", "dma-ranges" or child "reg" property
>> arch/arm/boot/dts/mediatek/mt6572-jty-d101.dtb: / (jty,d101): memory: False schema does not allow {'device_type': ['memory'], 'reg': [[2147483648, 1073741824]]}
from schema $id: http://devicetree.org/schemas/root-node.yaml#
vim +22 arch/arm/boot/dts/mediatek/mt6572-jty-d101.dts
a913a253369557 Max Shevchenko 2025-06-20 8
a913a253369557 Max Shevchenko 2025-06-20 9 / {
a913a253369557 Max Shevchenko 2025-06-20 10 model = "JTY D101";
a913a253369557 Max Shevchenko 2025-06-20 11 compatible = "jty,d101", "mediatek,mt6572";
a913a253369557 Max Shevchenko 2025-06-20 12
a913a253369557 Max Shevchenko 2025-06-20 13 aliases {
a913a253369557 Max Shevchenko 2025-06-20 14 serial0 = &uart0;
a913a253369557 Max Shevchenko 2025-06-20 15 };
a913a253369557 Max Shevchenko 2025-06-20 16
a913a253369557 Max Shevchenko 2025-06-20 @17 chosen {
a913a253369557 Max Shevchenko 2025-06-20 18 #address-cells = <1>;
a913a253369557 Max Shevchenko 2025-06-20 19 #size-cells = <1>;
a913a253369557 Max Shevchenko 2025-06-20 20 stdout-path = "serial0:921600n8";
a913a253369557 Max Shevchenko 2025-06-20 21
a913a253369557 Max Shevchenko 2025-06-20 @22 framebuffer: framebuffer@bf400000 {
a913a253369557 Max Shevchenko 2025-06-20 23 compatible = "simple-framebuffer";
a913a253369557 Max Shevchenko 2025-06-20 24 memory-region = <&framebuffer_reserved>;
a913a253369557 Max Shevchenko 2025-06-20 25 width = <1024>;
a913a253369557 Max Shevchenko 2025-06-20 26 height = <600>;
a913a253369557 Max Shevchenko 2025-06-20 27 stride = <(1024 * 2)>;
a913a253369557 Max Shevchenko 2025-06-20 28 format = "r5g6b5";
a913a253369557 Max Shevchenko 2025-06-20 29 status = "okay";
a913a253369557 Max Shevchenko 2025-06-20 30 };
a913a253369557 Max Shevchenko 2025-06-20 31 };
a913a253369557 Max Shevchenko 2025-06-20 32
a913a253369557 Max Shevchenko 2025-06-20 @33 memory {
a913a253369557 Max Shevchenko 2025-06-20 34 device_type = "memory";
a913a253369557 Max Shevchenko 2025-06-20 35 reg = <0x80000000 0x40000000>;
a913a253369557 Max Shevchenko 2025-06-20 36 };
a913a253369557 Max Shevchenko 2025-06-20 37
a913a253369557 Max Shevchenko 2025-06-20 38 reserved-memory {
a913a253369557 Max Shevchenko 2025-06-20 39 #address-cells = <1>;
a913a253369557 Max Shevchenko 2025-06-20 40 #size-cells = <1>;
a913a253369557 Max Shevchenko 2025-06-20 41 ranges;
a913a253369557 Max Shevchenko 2025-06-20 42
a913a253369557 Max Shevchenko 2025-06-20 43 connsys@80000000 {
a913a253369557 Max Shevchenko 2025-06-20 44 reg = <0x80000000 0x100000>;
a913a253369557 Max Shevchenko 2025-06-20 45 no-map;
a913a253369557 Max Shevchenko 2025-06-20 46 };
a913a253369557 Max Shevchenko 2025-06-20 47
a913a253369557 Max Shevchenko 2025-06-20 48 modem@be000000 {
a913a253369557 Max Shevchenko 2025-06-20 49 reg = <0xbe000000 0x1400000>;
a913a253369557 Max Shevchenko 2025-06-20 50 no-map;
a913a253369557 Max Shevchenko 2025-06-20 51 };
a913a253369557 Max Shevchenko 2025-06-20 52
a913a253369557 Max Shevchenko 2025-06-20 53 framebuffer_reserved: framebuffer@bf400000 {
a913a253369557 Max Shevchenko 2025-06-20 54 reg = <0xbf400000 0xc00000>;
a913a253369557 Max Shevchenko 2025-06-20 55 no-map;
a913a253369557 Max Shevchenko 2025-06-20 56 };
a913a253369557 Max Shevchenko 2025-06-20 57 };
a913a253369557 Max Shevchenko 2025-06-20 58 };
a913a253369557 Max Shevchenko 2025-06-20 59
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2025-06-24 1:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-24 1:36 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-06-20 15:40 [PATCH 00/11] ASoC: mediatek: Add support for MT6572 SoC Max Shevchenko
2025-06-20 15:40 ` [PATCH 10/11] ARM: dts: mediatek: add basic support for JTY D101 board Max Shevchenko
2025-06-20 15:40 ` Max Shevchenko via B4 Relay
2025-06-23 6:12 ` Krzysztof Kozlowski
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=202506241126.td9jarBJ-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.