The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Michal Simek <monstr@monstr.eu>
To: Masahiro Yamada <masahiroy@kernel.org>,
	Rob Herring <robh@kernel.org>,
	"Simek, Michal" <michal.simek@amd.com>
Cc: linux-kernel@vger.kernel.org, Conor Dooley <conor+dt@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	devicetree@vger.kernel.org
Subject: Re: [PATCH 4/4] microblaze: remove unnecessary system.dts
Date: Mon, 3 Feb 2025 12:17:16 +0100	[thread overview]
Message-ID: <b211188e-6c31-49fd-96be-137d3fc3f7bb@monstr.eu> (raw)
In-Reply-To: <CAK7LNATCFFQFYenkY2F5HkXx_otub9ebuTHJOD_TLiqCDnYN0w@mail.gmail.com>



On 2/1/25 04:42, Masahiro Yamada wrote:
> On Sat, Feb 1, 2025 at 7:25 AM Rob Herring <robh@kernel.org> wrote:
>>
>> On Tue, Jan 14, 2025 at 12:15 PM Masahiro Yamada <masahiroy@kernel.org> wrote:
>>>
>>> The default image linux.bin does not contain any DTB, but a separate
>>> system.dtb is compiled.
>>>
>>> Michal Simek clearly explained "system.dtb is really old dtb more for
>>> demonstration purpose and nothing else and likely it is not working on
>>> any existing board." [1]
>>>
>>> The system.dts is not necessary even for demonstration purposes. There
>>> is no need to compile out-of-tree *.dts under arch/microblaze/boot/dts/
>>> unless it is embedded into the kernel. Users can directly use dtc.
>>>
>>> [1]: https://lore.kernel.org/all/d2bdfbfd-3721-407f-991e-566d48392add@amd.com/
>>>
>>> Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
>>> ---
>>>
>>>   arch/microblaze/boot/dts/Makefile   |   3 +-
>>>   arch/microblaze/boot/dts/system.dts | 353 ----------------------------
>>>   2 files changed, 1 insertion(+), 355 deletions(-)
>>>   delete mode 100644 arch/microblaze/boot/dts/system.dts
>>>
>>> diff --git a/arch/microblaze/boot/dts/Makefile b/arch/microblaze/boot/dts/Makefile
>>> index 932dc7550a1b..fa0a6c0854ca 100644
>>> --- a/arch/microblaze/boot/dts/Makefile
>>> +++ b/arch/microblaze/boot/dts/Makefile
>>> @@ -1,8 +1,6 @@
>>>   # SPDX-License-Identifier: GPL-2.0
>>>   #
>>>
>>> -dtb-y := system.dtb
>>> -
>>>   ifneq ($(DTB),)
>>>   obj-y += linked_dtb.o
>>>
>>> @@ -11,6 +9,7 @@ $(obj)/linked_dtb.o: $(obj)/system.dtb
>>>
>>>   # Generate system.dtb from $(DTB).dtb
>>>   ifneq ($(DTB),system)
>>
>> Can't this be dropped as setting DTB=system.dtb should work if there's
>> not an in-tree system.dts anymore.
> 
> I believe this ifneq is necessary, just in case
> a user adds system.dtb to arch/microblaze/boot/dts/.
> 
> 'system.dtb' is a special name because
> arch/microblaze/boot/dts/linked_dtb.S wraps it.
> 
> So, $(DTB) is copied to system.dtb, and then
> it is wrapped by linked_dtb.S.
> 
> If $(DTB) is already 'system',
> we cannot copy system.dtb to itself.
> 
> 
> See the definition of cmd_copy in scripts/Makefile.lib
> 
> cmd_copy = cat $< > $@
> 
> 
> "cat system.dtb > system.dtb"
> would create an empty system.dtb
> 

I have played with this and pretty much this patch is blocking 
simpleImage.system build target.

I have no issue with patches 1-3 and I would keep system.dts as empty and keep 
it in the tree because users (including me) just rewrite system.dts with proper 
DTS and call make simpleImage.system.

Thanks,
Michal

-- 
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Xilinx Microblaze
Maintainer of Linux kernel - Xilinx Zynq ARM and ZynqMP/Versal ARM64 SoCs
U-Boot custodian - Xilinx Microblaze/Zynq/ZynqMP/Versal/Versal NET SoCs
TF-A maintainer - Xilinx ZynqMP/Versal/Versal NET SoCs


  reply	other threads:[~2025-02-03 11:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-14 18:13 [PATCH 1/4] microblaze: fix 'FORCE prerequisite is missing' warning Masahiro Yamada
2025-01-14 18:13 ` [PATCH 2/4] microblaze: merge build rules for linux.bin and simpleImage.$(DTB) Masahiro Yamada
2025-01-14 18:13 ` [PATCH 3/4] microblaze: prevent linux.bin from containing a built-in DTB Masahiro Yamada
2025-01-14 18:13 ` [PATCH 4/4] microblaze: remove unnecessary system.dts Masahiro Yamada
2025-01-31 22:25   ` Rob Herring
2025-02-01  3:42     ` Masahiro Yamada
2025-02-03 11:17       ` Michal Simek [this message]
2025-05-13  4:50         ` Masahiro Yamada
2025-06-10  7:49           ` Michal Simek

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=b211188e-6c31-49fd-96be-137d3fc3f7bb@monstr.eu \
    --to=monstr@monstr.eu \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=michal.simek@amd.com \
    --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