From: Dragan Simic <dsimic@manjaro.org>
To: Sebastian Kropatsch <seb-dev@web.de>
Cc: Jonas Karlman <jonas@kwiboo.se>, Heiko Stuebner <heiko@sntech.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Sebastian Reichel <sebastian.reichel@collabora.com>,
linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] arm64: dts: rockchip: Add CM3588 NAS board
Date: Wed, 29 May 2024 02:10:38 +0200 [thread overview]
Message-ID: <bccd8879a19ceacfd92a41e7533b324c@manjaro.org> (raw)
In-Reply-To: <29e5cf31-3d9a-469a-befa-41a5aa2fe8b3@web.de>
Hello Sebastian,
On 2024-05-28 19:22, Sebastian Kropatsch wrote:
> Am 27.05.2024 um 21:02 schrieb Jonas Karlman:
>> On 2024-05-26 23:48, Sebastian Kropatsch wrote:
>>> The CM3588 NAS by FriendlyElec pairs the CM3588 compute module, based
>>> on
>>> the Rockchip RK3588 SoC, with the CM3588 NAS Kit carrier board.
>>>
>>> [...]
>>>
>>> PCIe bifurcation is used to handle all four M.2 sockets at PCIe 3.0
>>> x1
>>> speed. Data lane mapping in the DT is done like described in commit
>>> f8020dfb311d ("phy: rockchip-snps-pcie3: fix bifurcation on rk3588").
>>>
>>> This device tree includes support for eMMC, SD card, ethernet, all
>>> USB2
>>> and USB3 ports, all four M.2 slots, GPU, RTC, buzzer, UART debugging
>>> as
>>> well as the buttons and LEDs.
>>> The GPIOs are labeled according to the schematics.
>>>
>>> Signed-off-by: Sebastian Kropatsch <seb-dev@web.de>
>>> ---
>>> arch/arm64/boot/dts/rockchip/Makefile | 1 +
>>> .../boot/dts/rockchip/rk3588-cm3588-nas.dts | 1269
>>> +++++++++++++++++
>>> 2 files changed, 1270 insertions(+)
>>> create mode 100644
>>> arch/arm64/boot/dts/rockchip/rk3588-cm3588-nas.dts
>>
>> Because the CM3588 is a SoM and the NAS is a carrier board this should
>> probably be split in two, cm3588.dtsi and cm3588-nas.dts.
>
> I thought about this before submitting. My reason for not splitting
> this
> into two files for now was that as far as I know this board is the only
> combination for the CM, maybe no other daughter board will ever get
> released. If another carrier board compatible with the CM3588 is
> released, the splitting could be done at that point in time.
>
> But since both you and Heiko prefer to have it split, I will figure out
> a way how and which parts will have to split up to the CM so we can
> have two files in the end. I guess most things will go into the NAS dts
> anyway.
>
> I'll have a look how other Rockchip compute modules with split device
> trees were done in the past and orient myself by that.
I also support the DT split between the SoM and the carrier board,
even if there are currently no more carrier boards available for
the particular SoM. That may seem redundant, but it reflects the
nature of the hardware setup, in which the SoM plugs into the carrier
board. This follows the principle of the DT describing hardware.
next prev parent reply other threads:[~2024-05-29 0:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-26 21:42 [PATCH 0/2] RK3588: FriendlyElec CM3588 NAS board support Sebastian Kropatsch
2024-05-26 21:46 ` [PATCH 1/2] dt-bindings: arm: rockchip: Add CM3588 NAS Sebastian Kropatsch
2024-05-27 6:10 ` Krzysztof Kozlowski
2024-05-26 21:48 ` [PATCH 2/2] arm64: dts: rockchip: Add CM3588 NAS board Sebastian Kropatsch
2024-05-27 19:02 ` Jonas Karlman
2024-05-27 20:54 ` Heiko Stübner
2024-05-28 15:55 ` Sebastian Kropatsch
2024-05-29 7:57 ` Heiko Stübner
2024-05-29 15:53 ` Sebastian Kropatsch
2024-05-28 17:22 ` Sebastian Kropatsch
2024-05-29 0:10 ` Dragan Simic [this message]
2024-05-29 17:20 ` Sebastian Kropatsch
-- strict thread matches above, loose matches on Subject: below --
2024-05-28 15:52 Sebastian Kropatsch
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=bccd8879a19ceacfd92a41e7533b324c@manjaro.org \
--to=dsimic@manjaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=jonas@kwiboo.se \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh@kernel.org \
--cc=seb-dev@web.de \
--cc=sebastian.reichel@collabora.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 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).