From: Krzysztof Kozlowski <krzk@kernel.org>
To: FUKAUMI Naoki <naoki@radxa.com>, neil.armstrong@linaro.org
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
khilman@baylibre.com, jbrunet@baylibre.com,
martin.blumenstingl@googlemail.com, devicetree@vger.kernel.org,
linux-amlogic@lists.infradead.org
Subject: Re: [PATCH v2 2/2] arm64: dts: amlogic: add support for Radxa ZERO 2 Pro
Date: Fri, 12 Jul 2024 09:52:47 +0200 [thread overview]
Message-ID: <c008b62f-9bf2-4f1e-ad9d-b934721a6bd0@kernel.org> (raw)
In-Reply-To: <20240711202013.26573-2-naoki@radxa.com>
On 11/07/2024 22:20, FUKAUMI Naoki wrote:
> Radxa ZERO 2 Pro is a ultra tiny high performance SBC[1] using the
> Amlogic A311D chip that ships in a number of eMMC configurations:
>
> - Amlogic A311D SoC
> - Quad A73 + Dual A53 CPU
> - Mali G52-MP4 GPU
> - NPU (5 TOPs)
> - 4GB LPDDR4 RAM
> - 32/64/128GB eMMC
> - micro SD Card slot
> - Wi-Fi 5 and BT 5.0
> - 1x USB 2.0 Type-C port (OTG)
> - 1x USB 3.0 Type-C port (Host)
> - Micro HDMI 2.0
> - MIPI DSI
> - MIPI CSI
> - 40 Pin GPIO header
>
> [1] https://radxa.com/products/zeros/zero2pro
>
> Signed-off-by: FUKAUMI Naoki <naoki@radxa.com>
>
> Changes in v2:
> - fix dtb build error
Same problem.
Best regards,
Krzysztof
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2024-07-12 7:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-11 20:20 [PATCH v2 1/2] dt-bindings: arm: amlogic: add support for Radxa ZERO 2 Pro FUKAUMI Naoki
2024-07-11 20:20 ` [PATCH v2 2/2] arm64: dts: " FUKAUMI Naoki
[not found] ` <D60FBED7-C930-41F6-A2C6-12C2CAC62F5D@hewittfamily.org.uk>
2024-07-12 5:01 ` FUKAUMI Naoki
2024-07-12 10:13 ` Neil Armstrong
2024-07-12 10:28 ` FUKAUMI Naoki
2024-07-12 7:52 ` Krzysztof Kozlowski [this message]
2024-07-12 7:52 ` [PATCH v2 1/2] dt-bindings: arm: " Krzysztof Kozlowski
2024-07-12 8:04 ` 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=c008b62f-9bf2-4f1e-ad9d-b934721a6bd0@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=naoki@radxa.com \
--cc=neil.armstrong@linaro.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