From: Chris Morgan <macroalpha82@gmail.com>
To: linux-sunxi@lists.linux.dev
Cc: devicetree@vger.kernel.org, mripard@kernel.org,
ryan@testtoast.com, andre.przywara@arm.com, samuel@sholland.org,
jernej.skrabec@gmail.com, wens@csie.org, conor+dt@kernel.org,
krzk+dt@kernel.org, robh@kernel.org,
Chris Morgan <macromorgan@hotmail.com>
Subject: [PATCH V3 0/4] Add Anbernic RG35XX-SP
Date: Wed, 10 Jul 2024 18:17:14 -0500 [thread overview]
Message-ID: <20240710231718.106894-1-macroalpha82@gmail.com> (raw)
From: Chris Morgan <macromorgan@hotmail.com>
Add support for the Anbernic RG35XX-SP handheld gaming device. The
Anbernic RG35XX-SP is a clamshell device, but hardware wise is very
similar to the RG35XX-Plus. The RG35XX-SP has a lid-switch and an
external RTC that necessitate a distinct device tree.
Please note that this series may have a soft pre-requisite on the patch
series here [1].
[1] https://lore.kernel.org/linux-sunxi/20240418000736.24338-1-andre.przywara@arm.com/
Changes from V2:
- Corrected commit message for device tree bindings.
- Added a fixes tag to i2c pinmux additions in sun50i-h616.dtsi file
based on recommendation from Andre Przywara.
Changes from V1:
- Switched all RG35XX devices from the r_rsb bus to the r_i2c bus for
the PMIC to keep it consistent.
- Added missing pinctrl nodes in sun50i-h616.dtsi file for the r_i2c
bus.
- Modified devicetree documentation to keep definition of the RG35XX
series consistent with other Allwinner devices.
Chris Morgan (4):
dt-bindings: arm: sunxi: Add Anbernic RG35XXSP
arm64: dts: allwinner: h616: Add r_i2c pinctrl nodes
arm64: dts: allwinner: h616: Change RG35XX Series from r_rsb to r_i2c
arm64: dts: allwinner: h700: Add Anbernic RG35XX-SP
.../devicetree/bindings/arm/sunxi.yaml | 9 +++--
arch/arm64/boot/dts/allwinner/Makefile | 3 +-
.../arm64/boot/dts/allwinner/sun50i-h616.dtsi | 2 ++
.../sun50i-h700-anbernic-rg35xx-2024.dts | 6 ++--
.../sun50i-h700-anbernic-rg35xx-sp.dts | 34 +++++++++++++++++++
5 files changed, 48 insertions(+), 6 deletions(-)
create mode 100644 arch/arm64/boot/dts/allwinner/sun50i-h700-anbernic-rg35xx-sp.dts
--
2.34.1
next reply other threads:[~2024-07-10 23:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 23:17 Chris Morgan [this message]
2024-07-10 23:17 ` [PATCH V3 1/4] dt-bindings: arm: sunxi: Add Anbernic RG35XXSP Chris Morgan
2024-07-11 6:35 ` Krzysztof Kozlowski
2024-07-10 23:17 ` [PATCH V3 2/4] arm64: dts: allwinner: h616: Add r_i2c pinctrl nodes Chris Morgan
2024-07-10 23:17 ` [PATCH V3 3/4] arm64: dts: allwinner: h616: Change RG35XX Series from r_rsb to r_i2c Chris Morgan
2024-07-11 9:52 ` Andre Przywara
2024-07-14 8:48 ` Ryan Walklin
2024-07-10 23:17 ` [PATCH V3 4/4] arm64: dts: allwinner: h700: Add Anbernic RG35XX-SP Chris Morgan
2024-07-11 10:10 ` Andre Przywara
2024-07-11 14:20 ` [PATCH V3 0/4] " Rob Herring (Arm)
2024-07-11 14:44 ` Andre Przywara
2024-08-01 16:25 ` Chen-Yu Tsai
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=20240710231718.106894-1-macroalpha82@gmail.com \
--to=macroalpha82@gmail.com \
--cc=andre.przywara@arm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jernej.skrabec@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=macromorgan@hotmail.com \
--cc=mripard@kernel.org \
--cc=robh@kernel.org \
--cc=ryan@testtoast.com \
--cc=samuel@sholland.org \
--cc=wens@csie.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).