From: Christopher Obbard <chris.obbard@collabora.com>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org,
linux-kernel@vger.kernel.org,
Kever Yang <kever.yang@rock-chips.com>,
Dragan Simic <dsimic@manjaro.org>,
Collabora Kernel Mailing List <kernel@collabora.com>,
Christopher Obbard <chris.obbard@collabora.com>
Subject: [PATCH v3 0/3] Add support for Firefly Core-PX30-JD4 SoM & baseboard
Date: Thu, 18 Jul 2024 09:40:23 +0100 [thread overview]
Message-ID: <20240718-rockchip-px30-firefly-v3-0-3835cdd22eae@collabora.com> (raw)
This adds support for the PX30-based Core-PX30-JD4 system-on-module from
Firefly and includes support for the SoM in combination with the
Firefly MB-JD4-PX30 baseboard.
---
Changes in v3:
- Rename px30-firefly-jd4.dts=>px30-firefly-jd4-core-mb.dts to follow
the existing <SoC>-<brand>-<SoM>-<carrier>.dts pattern.
- Change the compatible names to firefly,px30-jd4-core and
firefly,px30-jd4-core-mb to follow the above pattern.
- Adjust some grammatical errors (with=>on).
- Link to v2: https://lore.kernel.org/r/20240717-rockchip-px30-firefly-v2-0-06541a5a5946@collabora.com
Changes in v2:
- Split into two separate files: dtsi for the SoM and dts for the carrier.
- Change devicetree compatible to match SoM/carrier split.
- Change device names to better match vendor's name.
- Properly model baseboard & SoM regulators.
- Properly model baseboard recovery key.
- Remove DSI panel (& related nodes) since "sitronix,st7703" compatible
is undocumented & hardware is unavailable.
- Remove unused audio-related nodes.
- Remove unused UART nodes.
- Remove unused PMIC pinctrl nodes.
- Add node for baseboard LEDs.
- Link to v1: https://lore.kernel.org/r/20240716-rockchip-px30-firefly-v1-0-60cdad3023a3@collabora.com
---
Christopher Obbard (3):
dt-bindings: arm: rockchip: Add Firefly Core-PX30-JD4 on baseboard
arm64: dts: rockchip: add Firefly Core-PX30-JD4 SoM
arm64: dts: rockchip: add Firefly JD4 baseboard with Core-PX30-JD4 SoM
.../devicetree/bindings/arm/rockchip.yaml | 6 +
arch/arm64/boot/dts/rockchip/Makefile | 1 +
.../boot/dts/rockchip/px30-firefly-jd4-core-mb.dts | 179 ++++++++++++
.../boot/dts/rockchip/px30-firefly-jd4-core.dtsi | 322 +++++++++++++++++++++
4 files changed, 508 insertions(+)
---
base-commit: 51835949dda3783d4639cfa74ce13a3c9829de00
change-id: 20240716-rockchip-px30-firefly-59efc93d6784
Best regards,
--
Christopher Obbard <chris.obbard@collabora.com>
next reply other threads:[~2024-07-18 8:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-18 8:40 Christopher Obbard [this message]
2024-07-18 8:40 ` [PATCH v3 1/3] dt-bindings: arm: rockchip: Add Firefly Core-PX30-JD4 on baseboard Christopher Obbard
2024-07-18 8:49 ` Dragan Simic
2024-07-18 14:40 ` Conor Dooley
2024-07-18 8:40 ` [PATCH v3 2/3] arm64: dts: rockchip: add Firefly Core-PX30-JD4 SoM Christopher Obbard
2024-07-18 8:40 ` [PATCH v3 3/3] arm64: dts: rockchip: add Firefly JD4 baseboard with " Christopher Obbard
2024-07-29 20:21 ` [PATCH v3 0/3] Add support for Firefly Core-PX30-JD4 SoM & baseboard 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=20240718-rockchip-px30-firefly-v3-0-3835cdd22eae@collabora.com \
--to=chris.obbard@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dsimic@manjaro.org \
--cc=heiko@sntech.de \
--cc=kernel@collabora.com \
--cc=kever.yang@rock-chips.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox