From: Khairul Anuar Romli <karom.9560@gmail.com>
To: Dinh Nguyen <dinguyen@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] an/rm64: dts: socfpga: agilex: fix CHECK_DTBS DTC_FLAGS warning
Date: Wed, 24 Dec 2025 10:11:59 +0800 [thread overview]
Message-ID: <66eee345-83a7-4584-9afa-b06a9f0483b0@gmail.com> (raw)
In-Reply-To: <fc89c97f-a455-4e84-a219-6ec7ad9b4216@kernel.org>
On 23/12/2025 11:34 am, Dinh Nguyen wrote:
>
>
> On 12/22/25 19:15, Khairul Anuar Romli wrote:
>> On 22/12/2025 8:16 pm, Dinh Nguyen wrote:
>>>
>>>
>>> On 12/19/25 17:48, Khairul Anuar Romli wrote:
>>>> Add start address and ranges to eccmgr. This change corrects the
>>>> warning:
>>>>
>>>> socfpga_agilex.dtsi:612.10-669.5: Warning (simple_bus_reg): /soc@0/
>>>> eccmgr:
>>>> missing or empty reg/ranges property
>>>>
>>>
>>> Sorry, but I'm not seeing this warning on my local build with v6.19-
>>> rc1, nor at Rob's build[1].
>>>
>>> Dinh
>>>
>>> [1] https://gitlab.com/robherring/linux-dt/-/jobs?kind=BUILD
>>
>>
>> The warning observe if we build with DTC_FLAGS=-@.
>>
>
> Still do not see the warning.
>
> Dinh
I can only see it if I remove existing
arch/arm64/boot/dts/intel/socfpga_agilex_socdk.dtb and then recompile with:
make -j24 DTC_FLAGS=-@ CHECK_DTBS=y intel/socfpga_agilex_socdk.dtb.
Toolchain:
aarch64-linux-gnu-gcc (Ubuntu 14.2.0-4ubuntu2~24.04) 14.2.0
aarch64-linux-gnu-gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
Thanks.
Best Regards,
Khairul
prev parent reply other threads:[~2025-12-24 2:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-19 23:48 [PATCH v2 1/2] an/rm64: dts: socfpga: agilex: fix CHECK_DTBS DTC_FLAGS warning Khairul Anuar Romli
2025-12-19 23:48 ` [PATCH v2 2/2] arm64: dts: socfpga: stratix10: " Khairul Anuar Romli
2025-12-22 12:16 ` [PATCH v2 1/2] an/rm64: dts: socfpga: agilex: " Dinh Nguyen
2025-12-23 1:15 ` Khairul Anuar Romli
2025-12-23 3:34 ` Dinh Nguyen
2025-12-24 2:11 ` Khairul Anuar Romli [this message]
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=66eee345-83a7-4584-9afa-b06a9f0483b0@gmail.com \
--to=karom.9560@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox