From: Krzysztof Kozlowski <krzk@kernel.org>
To: FUKAUMI Naoki <naoki@radxa.com>, heiko@sntech.de
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org, linux-rockchip@lists.infradead.org
Subject: Re: [PATCH 3/3] arm64: dts: rockchip: add support for Radxa ROCK Pi E v3.0
Date: Sun, 23 Jun 2024 14:09:57 +0200 [thread overview]
Message-ID: <32f61b72-9346-4ac7-b225-c7fce45f0785@kernel.org> (raw)
In-Reply-To: <20240623120016.82990-3-naoki@radxa.com>
On 23/06/2024 14:00, FUKAUMI Naoki wrote:
> ROCK Pi E v3.0 is newer version of ROCK Pi E v1.2x. Changes are
>
> - Upgrade DDR3 to DDR4
> - Elevate eMMC connector to onboard eMMC
> - Update silkscreen to ROCK PI E V3.0
>
> Signed-off-by: FUKAUMI Naoki <naoki@radxa.com>
> ---
> arch/arm64/boot/dts/rockchip/rk3328-rock-pi-e-v3.dts | 10 ++++++++++
> arch/arm64/boot/dts/rockchip/rk3328-rock-pi-e.dts | 10 ++++++++++
> 2 files changed, 20 insertions(+)
> create mode 100644 arch/arm64/boot/dts/rockchip/rk3328-rock-pi-e-v3.dts
> create mode 100644 arch/arm64/boot/dts/rockchip/rk3328-rock-pi-e.dts
And how did you test it if you cannot build it?
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-06-23 12:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-23 12:00 [PATCH 1/3] dt-bindings: arm: rockchip: Add Radxa ROCK Pi E v3.0 FUKAUMI Naoki
2024-06-23 12:00 ` [PATCH 2/3] arm64: dts: rockchip: prepare common .dtsi for Radxa ROCK Pi E FUKAUMI Naoki
2024-06-23 12:09 ` Krzysztof Kozlowski
2024-06-23 12:00 ` [PATCH 3/3] arm64: dts: rockchip: add support for Radxa ROCK Pi E v3.0 FUKAUMI Naoki
2024-06-23 12:09 ` Krzysztof Kozlowski [this message]
2024-06-23 12:08 ` [PATCH 1/3] dt-bindings: arm: rockchip: Add " Krzysztof Kozlowski
2024-06-23 12:11 ` FUKAUMI Naoki
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=32f61b72-9346-4ac7-b225-c7fce45f0785@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=krzk+dt@kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=naoki@radxa.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;
as well as URLs for NNTP newsgroup(s).