public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: "Ondřej Jirman" <megi@xff.cz>
To: Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Heiko Stuebner <heiko@sntech.de>
Cc: Ondrej Jirman <megi@xff.cz>, Jagan Teki <jagan@edgeble.ai>,
	Jonas Karlman <jonas@kwiboo.se>,
	Chris Morgan <macromorgan@hotmail.com>,
	Sebastian Reichel <sebastian.reichel@collabora.com>,
	Kever Yang <kever.yang@rock-chips.com>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/2] Add support for Pine64 QuartzPro64
Date: Wed, 11 Oct 2023 23:58:43 +0200	[thread overview]
Message-ID: <20231011215856.2082241-1-megi@xff.cz> (raw)

From: Ondrej Jirman <megi@xff.cz>

This series adds an initial support for Pine64 QuartzPro64 SBC.

The series was tested against Linux 6.6-rc4.

Please take a look.

For v2, I proactively went through changes made by Heiko when merging my
other patchset for Orange Pi 5 Plus, and made the same changes to this
patchset, which had some similar issues:

- order regulator-name inside pmic nodes as the first property
- re-oreder some other properties alphabetically (in rtc node and in
  some regulators under /)
- drop rockchip,system-power-controller (will re-add later without prefix once
  https://lore.kernel.org/lkml/20231010174138.1888396-1-megi@xff.cz/ gets merged)
- drop mem-supply from cpu nodes (this will also be re-added later
  once cpufreq support is upstreamed)
- sort nodes under pinctrl alphabetically
- added acked-by tag for DT bindings patch

Thank you,
	Ondřej Jirman

Ondrej Jirman (2):
  dt-bindings: arm: rockchip: Add Pine64 QuarzPro64
  arm64: dts: rk3588-quartzpro64: Add QuartzPro64 SBC device tree

 .../devicetree/bindings/arm/rockchip.yaml     |    5 +
 arch/arm64/boot/dts/rockchip/Makefile         |    1 +
 .../boot/dts/rockchip/rk3588-quartzpro64.dts  | 1137 +++++++++++++++++
 3 files changed, 1143 insertions(+)
 create mode 100644 arch/arm64/boot/dts/rockchip/rk3588-quartzpro64.dts

-- 
2.42.0


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2023-10-11 21:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-11 21:58 Ondřej Jirman [this message]
2023-10-11 21:58 ` [PATCH v2 1/2] dt-bindings: arm: rockchip: Add Pine64 QuarzPro64 Ondřej Jirman
2023-10-11 21:58 ` [PATCH v2 2/2] arm64: dts: rk3588-quartzpro64: Add QuartzPro64 SBC device tree Ondřej Jirman
2023-10-11 22:36 ` [PATCH v2 0/2] Add support for Pine64 QuartzPro64 Heiko Stuebner
2023-10-11 22:50   ` Ondřej Jirman

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=20231011215856.2082241-1-megi@xff.cz \
    --to=megi@xff.cz \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --cc=jagan@edgeble.ai \
    --cc=jonas@kwiboo.se \
    --cc=kever.yang@rock-chips.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=macromorgan@hotmail.com \
    --cc=robh+dt@kernel.org \
    --cc=sebastian.reichel@collabora.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