From: Maya Matuszczyk <maccraft123mc@gmail.com>
To: linux-rockchip@lists.infradead.org
Cc: "Heiko Stuebner" <heiko@sntech.de>,
"João H . Spies" <jhlspies@gmail.com>,
"Chris Morgan" <macroalpha82@gmail.com>,
"Maya Matuszczyk" <maccraft123mc@gmail.com>
Subject: [PATCH v4 0/5] Add more RK3326 gaming handhelds
Date: Thu, 17 Nov 2022 22:59:49 +0100 [thread overview]
Message-ID: <20221117215954.4114202-1-maccraft123mc@gmail.com> (raw)
This patch series adds Odroid Go Advance, Odroid Go Super(without
display) and Anbernic RG351M.
RG351P uses almost the same motherboard, and I'm not sure how to handle
it. RG351P DTS file would look exactly the same, aside name change.
--
Changes from V3:
- Changed go3's volume buttons to not re-use builtin controller dt node
- Addressed Krzysztof Kozlowski's comments - removed status = "okay"
where it's not needed, and added a commit message to patch adding dt
bindings.
- Addressed Chris Morgan's comments - removed battery node from RG351M
- Added a cover letter even harder
Changes from V2:
- Fixed a typo
- Added "v3" tag, sorry!
- Added the cover letter in a way that shouldn't get swallowed by gmail
this time
Changes from V1:
- Addressed Chris Morgan's comments
- Added RG351M
- Added RG351M and Odroid Go Super
--
Maya Matuszczyk (5):
arm64: dts: rockchip: Move most of Odroid Go Advance DTS into a DTSI
dt-bindings: arm: rockchip: Add more RK3326 devices
arm64: dts: rockchip: Add Odroid Go Advance Black Edition
arm64: dts: rockchip: Add Odroid Go Super
arm64: dts: rockchip: Add Anbernic RG351M
.../devicetree/bindings/arm/rockchip.yaml | 25 +
arch/arm64/boot/dts/rockchip/Makefile | 3 +
.../dts/rockchip/rk3326-anbernic-rg351m.dts | 33 +
.../boot/dts/rockchip/rk3326-odroid-go.dtsi | 600 +++++++++++++++++
.../dts/rockchip/rk3326-odroid-go2-v11.dts | 156 +++++
.../boot/dts/rockchip/rk3326-odroid-go2.dts | 620 +-----------------
.../boot/dts/rockchip/rk3326-odroid-go3.dts | 185 ++++++
7 files changed, 1011 insertions(+), 611 deletions(-)
create mode 100644 arch/arm64/boot/dts/rockchip/rk3326-anbernic-rg351m.dts
create mode 100644 arch/arm64/boot/dts/rockchip/rk3326-odroid-go.dtsi
create mode 100644 arch/arm64/boot/dts/rockchip/rk3326-odroid-go2-v11.dts
create mode 100644 arch/arm64/boot/dts/rockchip/rk3326-odroid-go3.dts
--
2.38.1
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next reply other threads:[~2022-11-17 22:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 21:59 Maya Matuszczyk [this message]
2022-11-17 21:59 ` [PATCH v4 1/5] arm64: dts: rockchip: Move most of Odroid Go Advance DTS into a DTSI Maya Matuszczyk
2022-11-17 21:59 ` [PATCH v4 2/5] dt-bindings: arm: rockchip: Add more RK3326 devices Maya Matuszczyk
2022-11-18 8:12 ` Krzysztof Kozlowski
2022-11-17 21:59 ` [PATCH v4 3/5] arm64: dts: rockchip: Add Odroid Go Advance Black Edition Maya Matuszczyk
2022-11-17 21:59 ` [PATCH v4 4/5] arm64: dts: rockchip: Add Odroid Go Super Maya Matuszczyk
2022-11-17 21:59 ` [PATCH v4 5/5] arm64: dts: rockchip: Add Anbernic RG351M Maya Matuszczyk
2022-11-22 22:34 ` [PATCH v4 0/5] Add more RK3326 gaming handhelds Heiko Stuebner
2022-11-23 2:25 ` Chris Morgan
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=20221117215954.4114202-1-maccraft123mc@gmail.com \
--to=maccraft123mc@gmail.com \
--cc=heiko@sntech.de \
--cc=jhlspies@gmail.com \
--cc=linux-rockchip@lists.infradead.org \
--cc=macroalpha82@gmail.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