From: Oleksii Onchul <oleksiionchul@gmail.com>
To: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>
Cc: Abel Vesa <abelvesa@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Oleksii Onchul <oleksiionchul@gmail.com>
Subject: [PATCH 0/2] arm64: dts: qcom: Add Nothing Phone (4a) Pro support
Date: Sun, 11 Oct 2026 11:52:19 +0200 [thread overview]
Message-ID: <20261011095221.24767-1-oleksiionchul@gmail.com> (raw)
Add initial device tree support for the Nothing Phone (4a) Pro
(FroggerPro), based on the Qualcomm Eliza platform.
The DTS describes the UART, GPIO keys and reserved memory,
including ramoops.
Boot-tested on the phone with Linux 7.3-rc3 using a minimal initramfs.
GPIO key events and ramoops persistence were verified. DTB and binding
checks pass.
LLM assistance was used to prepare and review the DTS and patch
descriptions. Hardware testing was performed by the author.
Oleksii Onchul (2):
dt-bindings: arm: qcom: Add Nothing Phone (4a) Pro
arm64: dts: qcom: Add initial Nothing Phone (4a) Pro support
.../devicetree/bindings/arm/qcom.yaml | 1 +
arch/arm64/boot/dts/qcom/Makefile | 1 +
.../dts/qcom/eliza-nothing-froggerpro.dts | 157 ++++++++++++++++++
3 files changed, 159 insertions(+)
create mode 100644 arch/arm64/boot/dts/qcom/eliza-nothing-froggerpro.dts
base-commit: 705529dab1fa872d8b53b09c95e1b03a95573376
--
2.56.0
next reply other threads:[~2026-10-11 9:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-11 9:52 Oleksii Onchul [this message]
2026-10-11 9:52 ` [PATCH 1/2] dt-bindings: arm: qcom: Add Nothing Phone (4a) Pro Oleksii Onchul
2026-10-12 9:48 ` Krzysztof Kozlowski
2026-10-11 9:52 ` [PATCH 2/2] arm64: dts: qcom: Add initial Nothing Phone (4a) Pro support Oleksii Onchul
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=20261011095221.24767-1-oleksiionchul@gmail.com \
--to=oleksiionchul@gmail.com \
--cc=abelvesa@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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