From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Dale Whinham <daleyo@gmail.com>,
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: "Jérôme de Bretagne" <jerome.debretagne@gmail.com>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 4/8] arm64: dts: qcom: Add support for Surface Pro 11
Date: Mon, 1 Dec 2025 16:35:24 +0100 [thread overview]
Message-ID: <ae91cad5-5a0b-4c83-9eb0-6e7baf6a33d0@oss.qualcomm.com> (raw)
In-Reply-To: <20251201011457.17422-5-daleyo@gmail.com>
On 12/1/25 2:14 AM, Dale Whinham wrote:
> Add device trees for the Qualcomm X1E and X1P-based Microsoft Surface
> Pro 11 machines (codenamed 'Denali').
>
> This device is very similar to the Surface Laptop 7 ('Romulus').
>
> Use a similar strategy to x1-asus-zenbook-a14.dtsi so that we can create
> x1e and x1p-specific flavors of the device tree without too much code
> duplication.
[...]
> + pinctrl-0 = <&hall_int_n_default>;
> + pinctrl-names = "default";
> +
> + switch-lid {
> + gpios = <&tlmm 2 GPIO_ACTIVE_LOW>;
> + linux,input-type = <EV_SW>;
> + linux,code = <SW_LID>;
I.. don't think this device has a lid - what triggers this GPIO?
[...]
> + /*
> + * TODO: These two regulators are actually part of the removable M.2
> + * card and not the CRD mainboard. Need to describe this differently.
> + * Functionally it works correctly, because all we need to do is to
> + * turn on the actual 3.3V supply above.
There's not a M.2 card, the WLAN chip is soldered on board
https://www.ifixit.com/Guide/Microsoft+Surface+Pro+11+Chip+ID/174016#s370945
> + sound {
> + compatible = "qcom,x1e80100-sndcard";
> + model = "X1E80100-Microsoft-Surface-Pro-11";
> + audio-routing = "SpkrLeft IN", "WSA WSA_SPK1 OUT",
> + "SpkrRight IN", "WSA WSA_SPK2 OUT",
> + "VA DMIC0", "vdd-micb",
> + "VA DMIC1", "vdd-micb";
> +
> + wsa-dai-link {
> + link-name = "WSA Playback";
> +
> + cpu {
> + sound-dai = <&q6apmbedai WSA_CODEC_DMA_RX_0>;
> + };
> +
> + codec {
'co'dec < 'cp'u
please flip the order of the two
[...]
> +&i2c0 {
> + clock-frequency = <400000>;
> +
> + status = "disabled";
Is there anything connected to that controller?
If so, let's keep it enabled so that it's accessible through i2c-tools
It'd be even better if you could document (in a comment, like in romulus.dtsi)
what and at what address that is
[...]
> +&lpass_tlmm {
> + spkr_01_sd_n_active: spkr-01-sd-n-active-state {
> + pins = "gpio12";
> + function = "gpio";
> + drive-strength = <16>;
> + bias-disable;
> + output-low;
Please drop output-low from both definitions, the output state is
controlled manually by the WSA driver. Although from the diff below
it looks like spkr_23_sd_n is unused and you only have 2 speakers
[...]
> +&tlmm {
> + gpio-reserved-ranges = <44 4>, /* SPI (TPM) */
> + <238 1>; /* UFS Reset */
Please ensure your tab width is set to 8
[...]
> + cam_indicator_en: cam-indicator-en-state {
> + pins = "gpio225";
> + function = "gpio";
> + drive-strength = <2>;
> + bias-disable;
> + };
> +
> + wcn_sw_en: wcn-sw-en-state {
> + pins = "gpio214";
> + function = "gpio";
> + drive-strength = <2>;
> + bias-disable;
> + };
> +
> + wcn_wlan_bt_en: wcn-wlan-bt-en-state {
> + pins = "gpio116", "gpio117";
> + function = "gpio";
> + drive-strength = <2>;
> + bias-disable;
> + };
and here (+ these last 2 entries are out of order, GPIO num-wise,
please adjust that )
[...]
> +++ b/arch/arm64/boot/dts/qcom/x1e80100-microsoft-denali-oled.dts
> @@ -0,0 +1,20 @@
> +// SPDX-License-Identifier: BSD-3-Clause
> +/*
> + * Copyright (c) 2024 Qualcomm Innovation Center, Inc. All rights reserved.
> + * Copyright (c) 2025 Dale Whinham <daleyo@gmail.com>
> + */
> +
> +/dts-v1/;
> +
> +#include "x1e80100.dtsi"
> +#include "x1-microsoft-denali.dtsi"
> +
> +/ {
> + model = "Microsoft Surface Pro 11th Edition (OLED)";
> + compatible = "microsoft,denali-oled", "microsoft,denali",
> + "qcom,x1e80100";
Are the OLED models always X1E and the LCD ones always based on X1E80100
and LCD models always based on X1P64100?
Konrad
> +};
> +
> +&panel {
> + compatible = "samsung,atna30dw01", "samsung,atna33xc20";
> +};
> diff --git a/arch/arm64/boot/dts/qcom/x1p64100-microsoft-denali.dts b/arch/arm64/boot/dts/qcom/x1p64100-microsoft-denali.dts
> new file mode 100644
> index 000000000000..7c064ad49395
> --- /dev/null
> +++ b/arch/arm64/boot/dts/qcom/x1p64100-microsoft-denali.dts
> @@ -0,0 +1,16 @@
> +// SPDX-License-Identifier: BSD-3-Clause
> +/*
> + * Copyright (c) 2024 Qualcomm Innovation Center, Inc. All rights reserved.
> + * Copyright (c) 2025 Dale Whinham <daleyo@gmail.com>
> + */
> +
> +/dts-v1/;
> +
> +#include "x1e80100.dtsi"
> +#include "x1-microsoft-denali.dtsi"
> +
> +/ {
> + model = "Microsoft Surface Pro 11th Edition (LCD)";
> + compatible = "microsoft,denali-lcd", "microsoft,denali",
> + "qcom,x1p64100", "qcom,x1e80100";
> +};
next prev parent reply other threads:[~2025-12-01 15:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-01 1:14 [PATCH v2 0/8] Microsoft Surface Pro 11 support Dale Whinham
2025-12-01 1:14 ` [PATCH v2 1/8] dt-bindings: arm: qcom: Document Microsoft Surface Pro 11 Dale Whinham
2025-12-01 2:17 ` Rob Herring (Arm)
2025-12-01 7:30 ` Krzysztof Kozlowski
2025-12-01 1:14 ` [PATCH v2 2/8] firmware: qcom: scm: allow QSEECOM on " Dale Whinham
2025-12-04 1:25 ` Dmitry Baryshkov
2025-12-01 1:14 ` [PATCH v2 4/8] arm64: dts: qcom: Add support for " Dale Whinham
2025-12-01 15:35 ` Konrad Dybcio [this message]
2025-12-02 18:50 ` Jérôme de Bretagne
2025-12-03 10:56 ` Konrad Dybcio
2025-12-03 21:58 ` Jérôme de Bretagne
2025-12-04 9:02 ` Konrad Dybcio
2025-12-01 1:14 ` [PATCH v2 5/8] drm/msm/dp: Add dpcd link_rate quirk for Surface Pro 11 OLED Dale Whinham
2025-12-04 9:46 ` Dmitry Baryshkov
2025-12-01 1:14 ` [PATCH v2 8/8] arm64: dts: qcom: x1-microsoft-denali: Disable rfkill for wifi0 Dale Whinham
2025-12-01 7:35 ` Krzysztof Kozlowski
2025-12-01 12:27 ` [PATCH v2 0/8] Microsoft Surface Pro 11 support Rob Herring
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=ae91cad5-5a0b-4c83-9eb0-6e7baf6a33d0@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=daleyo@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jerome.debretagne@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=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