[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4491e009-0071-4130-9e1a-29145314e349@oss.qualcomm.com>
Date: Thu, 18 Dec 2025 11:54:13 +0100
From: Konrad Dybcio <konrad.dybcio@....qualcomm.com>
To: jerome.debretagne@...il.com, Bjorn Andersson <andersson@...nel.org>,
Konrad Dybcio <konradybcio@...nel.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley
<conor+dt@...nel.org>,
Johannes Berg <johannes@...solutions.net>,
Lorenzo Bianconi <lorenzo@...nel.org>,
Maximilian Luz <luzmaximilian@...il.com>,
Hans de Goede <hansg@...nel.org>,
Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>,
Jeff Johnson <jjohnson@...nel.org>
Cc: linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-wireless@...r.kernel.org,
platform-driver-x86@...r.kernel.org, ath12k@...ts.infradead.org,
Dale Whinham <daleyo@...il.com>
Subject: Re: [PATCH v3 5/6] arm64: dts: qcom: Add support for Surface Pro 11
On 12/18/25 12:56 AM, Jérôme de Bretagne via B4 Relay wrote:
> From: Dale Whinham <daleyo@...il.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@...il.com>
> Tested-by: Dale Whinham <daleyo@...il.com>
> Signed-off-by: Jérôme de Bretagne <jerome.debretagne@...il.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@....qualcomm.com>
Konrad
Powered by blists - more mailing lists