From: Krzysztof Kozlowski <krzk@kernel.org>
To: jerome.debretagne@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>,
"Johannes Berg" <johannes@sipsolutions.net>,
"Lorenzo Bianconi" <lorenzo@kernel.org>,
"Maximilian Luz" <luzmaximilian@gmail.com>,
"Hans de Goede" <hansg@kernel.org>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Jeff Johnson" <jjohnson@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
platform-driver-x86@vger.kernel.org, ath12k@lists.infradead.org,
Dale Whinham <daleyo@gmail.com>
Subject: Re: [PATCH v4 1/6] dt-bindings: arm: qcom: Document Microsoft Surface Pro 11
Date: Fri, 19 Dec 2025 18:40:00 +0100 [thread overview]
Message-ID: <4d167792-cc62-422b-bf65-3ce101377d46@kernel.org> (raw)
In-Reply-To: <20251218-surface-sp11-for-next-v4-1-7bcf83c1504a@gmail.com>
On 18/12/2025 23:22, Jérôme de Bretagne via B4 Relay wrote:
> From: Jérôme de Bretagne <jerome.debretagne@gmail.com>
>
> Add the compatibles for the Qualcomm-based Microsoft Surface Pro 11,
> using its Denali codename.
>
> The LCD models are using the Qualcomm Snapdragon X1 Plus (X1P64100),
> the OLED ones are using the Qualcomm Snapdragon X1 Elite (X1E80100).
>
> Due to the difference in how the built-in panel is being handled
> between the OLED variant and LCD one, it is required to have two
> separate DTBs, so document the compatible string for both variants.
>
> Signed-off-by: Jérôme de Bretagne <jerome.debretagne@gmail.com>
> ---
> Documentation/devicetree/bindings/arm/qcom.yaml | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/arm/qcom.yaml b/Documentation/devicetree/bindings/arm/qcom.yaml
> index d84bd3bca2010508a8225b9549d8c634efa06531..3685330344c0bf621125fc3d2f9c04082d6de144 100644
> --- a/Documentation/devicetree/bindings/arm/qcom.yaml
> +++ b/Documentation/devicetree/bindings/arm/qcom.yaml
> @@ -1067,6 +1067,17 @@ properties:
> - const: qcom,x1e78100
> - const: qcom,x1e80100
>
> + - items:
> + - const: microsoft,denali-lcd
> + - const: microsoft,denali
> + - const: qcom,x1p64100
64 < 78, so this should be placed after devkit list.
> + - const: qcom,x1e80100
> +
> + - items:
> + - const: microsoft,denali-oled
> + - const: microsoft,denali
So this goes after hamoa list, to keep somehow logical order.
> + - const: qcom,x1e80100
> +
> - items:
> - enum:
> - asus,vivobook-s15
>
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-12-19 17:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-18 22:22 [PATCH v4 0/6] Microsoft Surface Pro 11 support Jérôme de Bretagne via B4 Relay
2025-12-18 22:22 ` [PATCH v4 1/6] dt-bindings: arm: qcom: Document Microsoft Surface Pro 11 Jérôme de Bretagne via B4 Relay
2025-12-19 17:40 ` Krzysztof Kozlowski [this message]
2025-12-19 17:44 ` Krzysztof Kozlowski
2025-12-19 20:58 ` Jérôme de Bretagne
2025-12-18 22:22 ` [PATCH v4 2/6] dt-bindings: wireless: ieee80211: Add disable-rfkill property Jérôme de Bretagne via B4 Relay
2025-12-19 17:38 ` Krzysztof Kozlowski
2025-12-19 20:57 ` Jérôme de Bretagne
2025-12-18 22:22 ` [PATCH v4 3/6] firmware: qcom: scm: allow QSEECOM on Surface Pro 11 Jérôme de Bretagne via B4 Relay
2025-12-18 22:22 ` [PATCH v4 4/6] platform/surface: aggregator_registry: Add Surface Pro 11 (QCOM) Jérôme de Bretagne via B4 Relay
2025-12-19 7:49 ` Dmitry Baryshkov
2025-12-18 22:22 ` [PATCH v4 5/6] arm64: dts: qcom: Add support for Surface Pro 11 Jérôme de Bretagne via B4 Relay
2025-12-19 17:47 ` Krzysztof Kozlowski
2025-12-19 19:27 ` Dale Whinham
2025-12-19 20:55 ` Jérôme de Bretagne
2025-12-20 8:23 ` Krzysztof Kozlowski
2025-12-19 20:49 ` Jérôme de Bretagne
2025-12-18 22:22 ` [PATCH v4 6/6] wifi: ath12k: Add support for disabling rfkill via devicetree Jérôme de Bretagne via B4 Relay
2025-12-19 16:49 ` [PATCH v4 0/6] 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=4d167792-cc62-422b-bf65-3ce101377d46@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=ath12k@lists.infradead.org \
--cc=conor+dt@kernel.org \
--cc=daleyo@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jerome.debretagne@gmail.com \
--cc=jjohnson@kernel.org \
--cc=johannes@sipsolutions.net \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=luzmaximilian@gmail.com \
--cc=platform-driver-x86@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