From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
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 v3 5/6] arm64: dts: qcom: Add support for Surface Pro 11
Date: Thu, 18 Dec 2025 11:54:13 +0100 [thread overview]
Message-ID: <4491e009-0071-4130-9e1a-29145314e349@oss.qualcomm.com> (raw)
In-Reply-To: <20251218-surface-sp11-for-next-v3-5-875afc7bd3b7@gmail.com>
On 12/18/25 12:56 AM, Jérôme de Bretagne via B4 Relay wrote:
> From: Dale Whinham <daleyo@gmail.com>
>
> 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.
>
> Hardware support is similar to other X1 machines. The most notable
> missing features are:
>
> - Touchscreen and pen
> - Cameras (and status LEDs)
>
> Signed-off-by: Dale Whinham <daleyo@gmail.com>
> Tested-by: Dale Whinham <daleyo@gmail.com>
> Signed-off-by: Jérôme de Bretagne <jerome.debretagne@gmail.com>
> ---
[...]
> +&i2c4 {
> + clock-frequency = <400000>;
> +
> + status = "disabled";
> +};
> +
> +&i2c5 {
> + clock-frequency = <400000>;
> +
> + status = "disabled";
> +};
A little bit odd to leave them explicitly disabled. If they're useful,
enabling them makes sense. If not, removing the reference seems to be the
way to go.
With that taken care of, one way or the other:
Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Konrad
next prev parent reply other threads:[~2025-12-18 10:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-17 23:56 [PATCH v3 0/6] Microsoft Surface Pro 11 support Jérôme de Bretagne via B4 Relay
2025-12-17 23:56 ` [PATCH v3 1/6] dt-bindings: arm: qcom: Document Microsoft Surface Pro 11 Jérôme de Bretagne via B4 Relay
2025-12-18 14:15 ` Konrad Dybcio
2025-12-18 16:35 ` Jérôme de Bretagne
2025-12-19 11:33 ` Konrad Dybcio
2025-12-17 23:56 ` [PATCH v3 2/6] dt-bindings: wireless: ieee80211: Add disable-rfkill property Jérôme de Bretagne via B4 Relay
2025-12-17 23:56 ` [PATCH v3 3/6] firmware: qcom: scm: allow QSEECOM on Surface Pro 11 Jérôme de Bretagne via B4 Relay
2025-12-17 23:56 ` [PATCH v3 4/6] platform/surface: aggregator_registry: Add " Jérôme de Bretagne via B4 Relay
2025-12-18 0:07 ` Dmitry Baryshkov
2025-12-18 8:04 ` Jérôme de Bretagne
2025-12-17 23:56 ` [PATCH v3 5/6] arm64: dts: qcom: Add support for " Jérôme de Bretagne via B4 Relay
2025-12-18 10:54 ` Konrad Dybcio [this message]
2025-12-17 23:56 ` [PATCH v3 6/6] wifi: ath12k: Add support for disabling rfkill via devicetree Jérôme de Bretagne via B4 Relay
2025-12-18 14:10 ` [PATCH v3 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=4491e009-0071-4130-9e1a-29145314e349@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--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