devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Morgan <macroalpha82@gmail.com>
To: devicetree@vger.kernel.org
Cc: linux-rockchip@lists.infradead.org, robh+dt@kernel.org,
	krzysztof.kozlowski+dt@linaro.org, heiko@sntech.de,
	pgwipeout@gmail.com, michael.riesch@wolfvision.net,
	frattaroli.nicolas@gmail.com, jagan@amarulasolutions.com,
	Chris Morgan <macromorgan@hotmail.com>
Subject: [PATCH 0/4] Add Anbernic RG353V and RG353VS
Date: Fri, 28 Oct 2022 13:40:41 -0500	[thread overview]
Message-ID: <20221028184045.13113-1-macroalpha82@gmail.com> (raw)

From: Chris Morgan <macromorgan@hotmail.com>

Add support for the Anbernic RG353V and RG353VS handheld gaming
consoles. These devices are extremely similar to the existing
Anbernic RG353P.

Add support for the battery of the existing RG353P and RG503 too
as part of this change, as to keep things compact we must first split
the 353p devicetree into attributes common to all 353 devices and
attributes that only exist for the 353P, 353V, and 353VS devices
(which includes a different battery in the V and VS).

Lastly, add poll-interval to the parent tree so that it affects all
existing Anbernic RGxx3 devices.

Chris Morgan (4):
  dt-bindings: arm: rockchip: Add Anbernic RG353V and RG353VS
  arm64: dts: rockchip: add Anbernic RG353V and RG353VS
  arm64: dts: rockchip: add rk817 chg to RG353P and RG503
  arm64: dts: rockchip: add poll-interval to RGxx3 devices

 .../devicetree/bindings/arm/rockchip.yaml     |  10 ++
 arch/arm64/boot/dts/rockchip/Makefile         |   2 +
 .../dts/rockchip/rk3566-anbernic-rg353p.dts   | 109 +++++++++++------
 .../dts/rockchip/rk3566-anbernic-rg353v.dts   | 114 ++++++++++++++++++
 .../dts/rockchip/rk3566-anbernic-rg353vs.dts  |  87 +++++++++++++
 .../dts/rockchip/rk3566-anbernic-rg353x.dtsi  |  60 +++++++++
 .../dts/rockchip/rk3566-anbernic-rg503.dts    |  79 ++++++++++++
 .../dts/rockchip/rk3566-anbernic-rgxx3.dtsi   |  47 +-------
 8 files changed, 424 insertions(+), 84 deletions(-)
 create mode 100644 arch/arm64/boot/dts/rockchip/rk3566-anbernic-rg353v.dts
 create mode 100644 arch/arm64/boot/dts/rockchip/rk3566-anbernic-rg353vs.dts
 create mode 100644 arch/arm64/boot/dts/rockchip/rk3566-anbernic-rg353x.dtsi

-- 
2.25.1


             reply	other threads:[~2022-10-28 18:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-28 18:40 Chris Morgan [this message]
2022-10-28 18:40 ` [PATCH 1/4] dt-bindings: arm: rockchip: Add Anbernic RG353V and RG353VS Chris Morgan
2022-10-28 19:52   ` Krzysztof Kozlowski
2022-10-28 18:40 ` [PATCH 2/4] arm64: dts: rockchip: add " Chris Morgan
2022-10-28 18:40 ` [PATCH 3/4] arm64: dts: rockchip: add rk817 chg to RG353P and RG503 Chris Morgan
2022-10-28 18:40 ` [PATCH 4/4] arm64: dts: rockchip: add poll-interval to RGxx3 devices Chris Morgan
2022-10-30 20:08 ` [PATCH 0/4] Add Anbernic RG353V and RG353VS 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=20221028184045.13113-1-macroalpha82@gmail.com \
    --to=macroalpha82@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=frattaroli.nicolas@gmail.com \
    --cc=heiko@sntech.de \
    --cc=jagan@amarulasolutions.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=macromorgan@hotmail.com \
    --cc=michael.riesch@wolfvision.net \
    --cc=pgwipeout@gmail.com \
    --cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).