From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: david@ixit.cz, 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>,
Sumit Semwal <sumit.semwal@linaro.org>,
Casey Connolly <casey.connolly@linaro.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Jessica Zhang <jesszhan0024@gmail.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>
Cc: phodina@protonmail.com, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
phone-devel@vger.kernel.org, dri-devel@lists.freedesktop.org,
Amit Pundir <amit.pundir@linaro.org>,
Casey Connolly <casey@connolly.tech>,
Joel Selvaraj <foss@joelselvaraj.com>,
Vinod Koul <vkoul@kernel.org>
Subject: Re: [PATCH v3 8/8] arm64: dts: qcom: Add support for Pixel 3 and Pixel 3 XL
Date: Tue, 18 Nov 2025 13:32:23 +0100 [thread overview]
Message-ID: <d81b0e70-5e3f-4e33-a268-e8b903904e9b@oss.qualcomm.com> (raw)
In-Reply-To: <20251118-pixel-3-v3-8-317a2b400d8a@ixit.cz>
On 11/18/25 12:30 PM, David Heidelberg via B4 Relay wrote:
> From: David Heidelberg <david@ixit.cz>
>
> 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.
[...]
> +&cont_splash_mem {
> + reg = <0 0x9d400000 0 0x02400000>;
> +};
You override it to the same value on both devices, keep it in common
> +
> +&framebuffer0 {
> + width = <1080>;
> + height = <2160>;
> + stride = <(1080 * 4)>;
> + format = "a8r8g8b8";
The format is mandated by the UEFI specification and won't change too
[...]
> +&tlmm {
> + panel_te_pin: panel-te-state {
> + pins = "gpio12";
> + function = "mdp_vsync";
> + drive-strength = <2>;
> + bias-pull-down;
> + };
> +
> + panel_reset_pins: panel-active-state {
> + pins = "gpio6";
Pin entries would be best sorted by the GPIO index:
https://docs.kernel.org/devicetree/bindings/dts-coding-style.html#order-of-nodes
> + function = "gpio";
> + drive-strength = <8>;
> + bias-disable;
> + };
> +
> + panel_suspend: panel-suspend-state {
> + pins = "gpio6";
> + function = "gpio";
> + drive-strength = <2>;
> + bias-pull-down;
> + };
> +
> +};
Stray \n above
[...]
> +&adsp_pas {
> + firmware-name = "qcom/sdm845/Google/blueline/adsp.mbn";
Sorry if I asked this before, but are the binaries identical for
both devices?
[...]
> + vreg_l14a_1p88: ldo14 {
> + regulator-min-microvolt = <1800000>;
> + regulator-max-microvolt = <1800000>;
> + regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
> + regulator-boot-on;
> + /*
> + * We can't properly bring the panel back if it gets turned off
> + * so keep it's regulators always on for now.
> + */
> + regulator-always-on;
Is that still the case with your fixes to the panel driver?
[...]
> +
> + vreg_l28a_3p0: ldo28 {
> + regulator-min-microvolt = <2856000>;
> + regulator-max-microvolt = <3008000>;
> + regulator-initial-mode = <RPMH_REGULATOR_MODE_LPM>;
> + regulator-boot-on;
> + /*
> + * We can't properly bring the panel back if it gets turned off
> + * so keep it's regulators always on for now.
> + */
> + regulator-always-on;
ditto
[...]
> + regulators-1 {
> + compatible = "qcom,pmi8998-rpmh-regulators";
> + qcom,pmic-id = "b";
> +
> + vdd-bob-supply = <&vph_pwr>;
> +
> + vreg_bob: bob {
> + regulator-min-microvolt = <3312000>;
> + regulator-max-microvolt = <3600000>;
This is a very broad range, what voltage does it need to be?
[...]
[...]
> +&tlmm {
> + gpio-reserved-ranges = < 0 4>, /* SPI (Intel MNH Pixel Visual Core) */
stray space before '0'
Konrad
next prev parent reply other threads:[~2025-11-18 12:32 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-18 11:30 [PATCH v3 0/8] " David Heidelberg via B4 Relay
2025-11-18 11:30 ` [PATCH v3 1/8] dt-bindings: arm: qcom: Add Pixel 3 and " David Heidelberg via B4 Relay
2025-11-19 7:16 ` Krzysztof Kozlowski
2025-11-18 11:30 ` [PATCH v3 2/8] dt-bindings: panel: sw43408: adjust to reflect the DDIC and panel used David Heidelberg via B4 Relay
2025-11-18 12:29 ` Rob Herring (Arm)
2025-11-18 12:33 ` Konrad Dybcio
2025-11-18 12:34 ` David Heidelberg
2025-11-18 11:30 ` [PATCH v3 3/8] drm/panel: sw43408: Introduce LH546WF1-ED01 panel compatible David Heidelberg via B4 Relay
2025-11-19 7:36 ` Dmitry Baryshkov
2025-11-19 10:20 ` David Heidelberg
2025-11-18 11:30 ` [PATCH v3 4/8] drm/panel: sw43408: Introduce disable/enable functions David Heidelberg via B4 Relay
2025-11-19 7:28 ` Dmitry Baryshkov
2025-11-18 11:30 ` [PATCH v3 5/8] drm/panel: sw43408: Remove manual invocation of unprepare at remove David Heidelberg via B4 Relay
2025-11-19 7:29 ` Dmitry Baryshkov
2025-11-18 11:30 ` [PATCH v3 6/8] drm/panel: sw43408: Switch to devm_regulator_bulk_get_const David Heidelberg via B4 Relay
2025-11-19 7:29 ` Dmitry Baryshkov
2025-11-18 11:30 ` [PATCH v3 7/8] drm/panel: sw43408: Improve wording when reset-gpios aren't available David Heidelberg via B4 Relay
2025-11-19 7:30 ` Dmitry Baryshkov
2025-11-18 11:30 ` [PATCH v3 8/8] arm64: dts: qcom: Add support for Pixel 3 and Pixel 3 XL David Heidelberg via B4 Relay
2025-11-18 12:32 ` Konrad Dybcio [this message]
2025-11-18 13:31 ` David Heidelberg
2025-11-18 13:41 ` Konrad Dybcio
2025-11-20 1:04 ` Doug Anderson
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=d81b0e70-5e3f-4e33-a268-e8b903904e9b@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=airlied@gmail.com \
--cc=amit.pundir@linaro.org \
--cc=andersson@kernel.org \
--cc=casey.connolly@linaro.org \
--cc=casey@connolly.tech \
--cc=conor+dt@kernel.org \
--cc=david@ixit.cz \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=foss@joelselvaraj.com \
--cc=jesszhan0024@gmail.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=phodina@protonmail.com \
--cc=phone-devel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=simona@ffwll.ch \
--cc=sumit.semwal@linaro.org \
--cc=tzimmermann@suse.de \
--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
all inboxes | Powered by JetHome®