From: Chris Morgan <macroalpha82@gmail.com>
To: linux-rockchip@lists.infradead.org
Cc: devicetree@vger.kernel.org, heiko@sntech.de, conor+dt@kernel.org,
krzk+dt@kernel.org, robh@kernel.org,
Chris Morgan <macromorgan@hotmail.com>
Subject: [PATCH 0/2] Add Powkiddy RGB20SX
Date: Tue, 1 Oct 2024 10:40:14 -0500 [thread overview]
Message-ID: <20241001154016.87386-1-macroalpha82@gmail.com> (raw)
From: Chris Morgan <macromorgan@hotmail.com>
Add support for the Powkiddy RGB20SX handheld gaming console. The
device is mostly identical to the RGB30 but with a few key differences.
Namely, the size of the battery and presense of a function button
differ from the RGB30; these changes cannot be detected at runtime and
necessitate a distinct devicetree.
https://powkiddy.com/products/pre-sale-powkiddy-rgb20sx-handheld-game-console
Chris Morgan (2):
dt-bindings: arm: rockchip: Add Powkiddy RGB20SX
arm64: dts: rockchip: Add Powkiddy RGB20SX
.../devicetree/bindings/arm/rockchip.yaml | 1 +
arch/arm64/boot/dts/rockchip/Makefile | 1 +
.../dts/rockchip/rk3566-powkiddy-rgb20sx.dts | 89 +++++++++++++++++++
3 files changed, 91 insertions(+)
create mode 100644 arch/arm64/boot/dts/rockchip/rk3566-powkiddy-rgb20sx.dts
--
2.43.0
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
WARNING: multiple messages have this Message-ID (diff)
From: Chris Morgan <macroalpha82@gmail.com>
To: linux-rockchip@lists.infradead.org
Cc: devicetree@vger.kernel.org, heiko@sntech.de, conor+dt@kernel.org,
krzk+dt@kernel.org, robh@kernel.org,
Chris Morgan <macromorgan@hotmail.com>
Subject: [PATCH 0/2] Add Powkiddy RGB20SX
Date: Tue, 1 Oct 2024 10:40:14 -0500 [thread overview]
Message-ID: <20241001154016.87386-1-macroalpha82@gmail.com> (raw)
From: Chris Morgan <macromorgan@hotmail.com>
Add support for the Powkiddy RGB20SX handheld gaming console. The
device is mostly identical to the RGB30 but with a few key differences.
Namely, the size of the battery and presense of a function button
differ from the RGB30; these changes cannot be detected at runtime and
necessitate a distinct devicetree.
https://powkiddy.com/products/pre-sale-powkiddy-rgb20sx-handheld-game-console
Chris Morgan (2):
dt-bindings: arm: rockchip: Add Powkiddy RGB20SX
arm64: dts: rockchip: Add Powkiddy RGB20SX
.../devicetree/bindings/arm/rockchip.yaml | 1 +
arch/arm64/boot/dts/rockchip/Makefile | 1 +
.../dts/rockchip/rk3566-powkiddy-rgb20sx.dts | 89 +++++++++++++++++++
3 files changed, 91 insertions(+)
create mode 100644 arch/arm64/boot/dts/rockchip/rk3566-powkiddy-rgb20sx.dts
--
2.43.0
next reply other threads:[~2024-10-01 15:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 15:40 Chris Morgan [this message]
2024-10-01 15:40 ` [PATCH 0/2] Add Powkiddy RGB20SX Chris Morgan
2024-10-01 15:40 ` [PATCH 1/2] dt-bindings: arm: rockchip: " Chris Morgan
2024-10-01 15:40 ` Chris Morgan
2024-10-01 15:51 ` Conor Dooley
2024-10-01 15:51 ` Conor Dooley
2024-10-01 15:40 ` [PATCH 2/2] arm64: dts: " Chris Morgan
2024-10-01 15:40 ` Chris Morgan
2024-10-02 10:30 ` [PATCH 0/2] " Heiko Stuebner
2024-10-02 10:30 ` Heiko Stuebner
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=20241001154016.87386-1-macroalpha82@gmail.com \
--to=macroalpha82@gmail.com \
--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=macromorgan@hotmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.