devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Heidelberg via B4 Relay <devnull+david.ixit.cz@kernel.org>
To: Bjorn Andersson <andersson@kernel.org>,
	 Konrad Dybcio <konradybcio@kernel.org>,
	Rob Herring <robh@kernel.org>,
	 Krzysztof Kozlowski <krzk+dt@kernel.org>,
	 Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	 linux-kernel@vger.kernel.org, David Heidelberg <david@ixit.cz>,
	 Amit Pundir <amit.pundir@linaro.org>,
	Casey Connolly <casey@connolly.tech>,
	 Joel Selvaraj <foss@joelselvaraj.com>,
	 Sumit Semwal <sumit.semwal@linaro.org>,
	Vinod Koul <vkoul@kernel.org>,
	 Bjorn Andersson <andersson@kernel.org>
Subject: [PATCH 0/2] Add support for Pixel 3 and Pixel 3 XL
Date: Sun, 05 Oct 2025 15:16:27 +0200	[thread overview]
Message-ID: <20251005-pixel-3-v1-0-ab8b85f6133f@ixit.cz> (raw)

This adds initial device tree support for the following phones:

 - Google Pixel 3 (blueline)
 - Google Pixel 3 XL (crosshatch)

Both phone boards use the same identifiers and differ only slightly
in their connected peripherals.

Supported functionality includes:
 - Debug UART
 - UFS
 - Charger
 - USB-C (peripheral mode)
 - Display (Pixel 3 only)

This is mainly focused to get the base functionality of the board and
being able to use the upstream DTS within Linux and u-boot.

Booting
-------
For older Pixel 3 bootloaders, bootloader-compatible board and MSM IDs are
required for the kernel to boot, so these have been added.

For recent Pixel 3 bootloaders,
a) you want chainloaded proper bootloader (f.e. u-boot),
b) you can also boot kernel when adding back TEXT_OFFSET
   (partial revert of 120dc60d).

This series is a beggining of cleaning up and transitioning support from
sdm845 close to mainline tree to the mainline.

Signed-off-by: David Heidelberg <david@ixit.cz>
---
David Heidelberg (2):
      Documentation: dt-bindings: arm: qcom: Add Pixel 3 and 3 XL
      arm64: dts: qcom: Add support for Pixel 3 and Pixel 3 XL

 Documentation/devicetree/bindings/arm/qcom.yaml    |   5 +-
 arch/arm64/boot/dts/qcom/Makefile                  |   2 +
 .../arm64/boot/dts/qcom/sdm845-google-blueline.dts | 128 ++++++
 arch/arm64/boot/dts/qcom/sdm845-google-common.dtsi | 467 +++++++++++++++++++++
 .../boot/dts/qcom/sdm845-google-crosshatch.dts     | 137 ++++++
 5 files changed, 736 insertions(+), 3 deletions(-)
---
base-commit: e5f0a698b34ed76002dc5cff3804a61c80233a7a
change-id: 20250419-pixel-3-511edc2a4607

Best regards,
-- 
David Heidelberg <david@ixit.cz>



             reply	other threads:[~2025-10-05 13:16 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-05 13:16 David Heidelberg via B4 Relay [this message]
2025-10-05 13:16 ` [PATCH 1/2] Documentation: dt-bindings: arm: qcom: Add Pixel 3 and 3 XL David Heidelberg via B4 Relay
2025-10-05 22:21   ` Dmitry Baryshkov
2025-10-06  8:09     ` Konrad Dybcio
2025-10-06 10:09       ` David Heidelberg
2025-10-06 10:16         ` Konrad Dybcio
2025-10-06 10:17       ` Dmitry Baryshkov
2025-10-05 13:16 ` [PATCH 2/2] arm64: dts: qcom: Add support for Pixel 3 and Pixel " David Heidelberg via B4 Relay
2025-10-05 13:25   ` David Heidelberg
2025-10-05 22:03   ` Dmitry Baryshkov
2025-10-09 21:20     ` David Heidelberg
2025-10-09 21:50       ` Dmitry Baryshkov
2025-10-10  7:51         ` David Heidelberg
2025-10-10  8:17           ` Dmitry Baryshkov
2025-10-17 16:59     ` David Heidelberg
2025-10-19 11:51       ` Dmitry Baryshkov
2025-10-19 13:02         ` David Heidelberg
2025-10-19 14:53           ` Dmitry Baryshkov
2025-10-17 22:23     ` David Heidelberg
2025-10-19 11:51       ` Dmitry Baryshkov
2025-10-06 12:41   ` Konrad Dybcio
2025-10-17 23:32     ` David Heidelberg
2025-10-05 22:15 ` [PATCH 0/2] " Dmitry Baryshkov

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=20251005-pixel-3-v1-0-ab8b85f6133f@ixit.cz \
    --to=devnull+david.ixit.cz@kernel.org \
    --cc=amit.pundir@linaro.org \
    --cc=andersson@kernel.org \
    --cc=casey@connolly.tech \
    --cc=conor+dt@kernel.org \
    --cc=david@ixit.cz \
    --cc=devicetree@vger.kernel.org \
    --cc=foss@joelselvaraj.com \
    --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 \
    --cc=sumit.semwal@linaro.org \
    --cc=vkoul@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).