From: Masami Hiramatsu <masami.hiramatsu@linaro.org>
To: Masahiro Yamada <yamada.masahiro@socionext.com>,
Rob Herring <robh@kernel.org>
Cc: devicetree@vger.kernel.org,
Kunihiko Hayashi <hayashi.kunihiko@socionext.com>,
Masami Hiramatsu <masami.hiramatsu@linaro.org>,
Jassi Brar <jaswinder.singh@linaro.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/2] dts: uniphier: Add Akebi96 Board support
Date: Mon, 20 Apr 2020 19:07:28 +0900 [thread overview]
Message-ID: <20200420190728.d720d18b9073e1c6c0304d72@linaro.org> (raw)
Hello,
Here is the 2nd version of the patches to add a devicetree for
Akebi96 board.
In this version, I fixed author's tag and rebase it on 5.7-rc2.
The Akebi96 is a certified 96boards which is based on Socionext
UniPhier LD20 SoC. Most of the part is similar to LD20 reference
board, but there are some changes.
- MAX3421 USB-SPI chip on SPI port3 (for USB gadget port.)
- Simple frame buffer with 1080p fixed resolution.
- I2S port which is connected to aout1b instead of aout1.
- 3 serial ports, only serial3 has CTS/RTS.
- No NAND, only eMMC on the board.
- OP-TEE support.
See https://www.96boards.org/product/akebi96/ for details.
Thank you,
---
Masami Hiramatsu (2):
dt-bindings: arm: Add Akebi96 board support
arm64: dts: uniphier: Add support for Akebi96
.../bindings/arm/socionext/uniphier.yaml | 1
arch/arm64/boot/dts/socionext/Makefile | 1
.../boot/dts/socionext/uniphier-ld20-akebi96.dts | 200 ++++++++++++++++++++
arch/arm64/boot/dts/socionext/uniphier-ld20.dtsi | 2
4 files changed, 203 insertions(+), 1 deletion(-)
create mode 100644 arch/arm64/boot/dts/socionext/uniphier-ld20-akebi96.dts
--
Masami Hiramatsu <masami.hiramatsu@linaro.org>
reply other threads:[~2020-04-20 10:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200420190728.d720d18b9073e1c6c0304d72@linaro.org \
--to=masami.hiramatsu@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=hayashi.kunihiko@socionext.com \
--cc=jaswinder.singh@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mhiramat@kernel.org \
--cc=robh@kernel.org \
--cc=yamada.masahiro@socionext.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).