linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Heiko Stübner" <heiko@sntech.de>
To: patrick@blueri.se, Jimmy Hon <honyuenkwun@gmail.com>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org,
	kever.yang@rock-chips.com, krzk+dt@kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, robh@kernel.org
Subject: Re: [PATCH v2 2/2] arm64: dts: rockchip: add MNT Reform 2
Date: Tue, 11 Feb 2025 08:33:52 +0100	[thread overview]
Message-ID: <3840752.CbtlEUcBR6@diego> (raw)
In-Reply-To: <20250211040300.1905-1-honyuenkwun@gmail.com>

Hi Jimmy,

Am Dienstag, 11. Februar 2025, 05:03:00 MEZ schrieb Jimmy Hon:
> The RCORE looks like a carrier board for the Firefly iCore RK3588Q SoM [1].
> So it would be better to restructure the DTS as a dtsi for the SoM and
> a board DTS which includes the SoM dtsi.

thanks a lot for finding that bit of information.

And I do agree that if there is a Firefly module in the middle, that things
should be modelled accordingly.

> That's similar to the structure of the Firefly ITX-RK3558J board which 
> uses the rk3588-firefly-core-3588j.dtsi. [2]
> 
> [1] https://source.mnt.re/reform/mnt-reform-rk3588-som
> [2] https://lore.kernel.org/linux-rockchip/20241216214152.58387-1-shimrrashai@gmail.com/#t


Heiko




      reply	other threads:[~2025-02-11  7:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-10 22:16 [PATCH v2 1/2] dt-bindings: arm: rockchip: Add MNT Reform 2 (RCORE) Patrick Wildt
2025-02-10 22:17 ` [PATCH v2 2/2] arm64: dts: rockchip: add MNT Reform 2 Patrick Wildt
2025-02-11  4:03   ` Jimmy Hon
2025-02-11  7:33     ` Heiko Stübner [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=3840752.CbtlEUcBR6@diego \
    --to=heiko@sntech.de \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=honyuenkwun@gmail.com \
    --cc=kever.yang@rock-chips.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=patrick@blueri.se \
    --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;
as well as URLs for NNTP newsgroup(s).