From: Haipeng Lin <jimmie.lin@gmail.com>
To: Val Packett <val@packett.cool>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Abel Vesa <abelvesa@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: "Maximilian Luz" <luzmaximilian@gmail.com>,
"Hans de Goede" <hansg@kernel.org>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Alexandre Belloni" <alexandre.belloni@bootlin.com>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-rtc@vger.kernel.org
Subject: Re: [PATCH 2/5] arm64: dts: qcom: sc8180x: Add Microsoft Surface Pro X
Date: Sun, 15 Nov 2026 11:28:58 -0500 [thread overview]
Message-ID: <b92385e0-d39a-430c-925e-93dd978769dd@gmail.com> (raw)
In-Reply-To: <4a7e0f27-60b6-46ec-956b-8897812622a2@packett.cool>
On 11/15/26 3:20 AM, Val Packett wrote:
[...]>> Would it make sense to move opp-3072000000 and opp-3148800000 into the
>> shared sc8180x-microsoft-surface-pro-x.dtsi? qcom-cpufreq-hw disables
>> all DT OPPs first and only re-enables freqs present in the hardware LUT
>> so this would work for SQ1 and caspar.dtb will cover both the SQ1 and
>> SQ2 Wi-Fi models out of the box and carina.dts won't need its own
>> &cpu4_opp_table override.
>
> I'm pretty sure mine *did* complain very loudly about having these OPPs and might've even had broken scaling.
>
> I'll retest again, if it works I'll move it to the shared dtsi (or even the SoC's?)
I like the idea of moving it to the SoC. Did a test on my SQ2 Wi-Fi
with opp-3072000000/opp-3148800000 moved into sc8180x.dtsi, dropping
it from carina.dts, plus a dummy opp-32256000000 above my LUT's top
entry so I can "simulate" the SQ1 situation where there's a DT OPP that
the LUT does not have. Booting that with caspar.dtb:
- no cpufreq/OPP messages at all (e.g., "Voltage update failed" or
"failed to update OPP" as observed for caspar.dts in this v1 on SQ2)
- policy4 scaling_available_frequencies tops out at 3148800, the dummy
3225600 is disabled silently (by qcom_cpufreq_hw_read_lut() ?)
- under load time_in_state shows gold cluster sits at 3148800
Hopefully, this solution should work for both SQ1 and SQ2. sc8180x.dtsi
looks like it tops out at 2995200, and that is SQ1's bin above the
"regular" 8cx Gen 1's 2.84 GHz on the gold cluster so if it was broken
it would already be broken for the 8cx G1 due to the SQ1 entries...
[...]>
> BTW, please send me the output of `sudo fwupdtool hwids`, these are needed to add support to dtbloader/systemd-stub/stubble DT auto-selection.
>
> (If anyone with the cellular variants reads this: you too :))
>
>
> Thanks,
>
> ~val
This is not the latest BIOS which is 11.504.140 according to
https://support.microsoft.com/en-us/surface/updates/surface-pro-x-update-history
but I don't have dual boot to update it...
Surface Pro X SQ2 Wi-Fi only:
Computer Information
--------------------
BiosVendor: Microsoft Corporation
BiosVersion: 11.311.140
BiosMajorRelease: 255
BiosMinorRelease: 255
BiosReleaseDate: 2/03/2026
FirmwareMajorRelease: ff
FirmwareMinorRelease: ff
Manufacturer: Microsoft Corporation
Family: Surface
ProductName: Surface Pro X
ProductSku: Surface_Pro_X_2010
EnclosureKind: 9
BaseboardManufacturer: Microsoft Corporation
BaseboardProduct: Surface Pro X
Hardware IDs
------------
{bf87a823-6823-50f1-9f18-2030fd86b087} <- Manufacturer + Family + ProductName + ProductSku + BiosVendor + BiosVersion + BiosMajorRelease + BiosMinorRelease
{43cb3df2-05e6-5637-a89c-718381284f3d} <- Manufacturer + Family + ProductName + BiosVendor + BiosVersion + BiosMajorRelease + BiosMinorRelease
{1d2505b3-3329-5a15-b934-e1990787e978} <- Manufacturer + ProductName + BiosVendor + BiosVersion + BiosMajorRelease + BiosMinorRelease
{75b4817e-50ec-5e63-a904-1175cd1abff6} <- Manufacturer + Family + ProductName + ProductSku + BaseboardManufacturer + BaseboardProduct
{cdf510a8-d41c-54bf-b2c5-61ba10957019} <- Manufacturer + Family + ProductName + ProductSku
{cc2bc434-a08a-59c0-85ac-2576ed611de6} <- Manufacturer + Family + ProductName
{69c2fd0d-8593-575f-b6af-5f70f0299ea4} <- Manufacturer + ProductSku + BaseboardManufacturer + BaseboardProduct
{aa2c30e9-117c-5aeb-a8aa-4b01761cf493} <- Manufacturer + ProductSku
{b07028e2-19c1-577d-a3c9-2eabef35c2a1} <- Manufacturer + ProductName + BaseboardManufacturer + BaseboardProduct
{5d018db8-6de6-55f8-8d8b-4b773caf8450} <- Manufacturer + ProductName
{db7e6e61-56bf-531d-b594-e4b1660d04aa} <- Manufacturer + Family + BaseboardManufacturer + BaseboardProduct
{ca2e5189-1d32-509f-88a0-d4ebcc721899} <- Manufacturer + Family
{aca387a9-183e-5da9-8f9d-f460c3f50f54} <- Manufacturer + EnclosureKind
{f199ec04-d0d9-542b-b035-209532a4d1f6} <- Manufacturer + BaseboardManufacturer + BaseboardProduct
{cc0aea32-ad2c-5013-8bed-cede6be8c9f4} <- Manufacturer
Thanks,
Haipeng
next prev parent reply other threads:[~2026-11-15 16:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 7:04 [PATCH 0/5] Add support for the Microsoft Surface Pro X Val Packett
2026-11-04 7:04 ` [PATCH 1/5] dt-bindings: arm: qcom: Document " Val Packett
2026-11-04 7:10 ` sashiko-bot
2026-11-15 3:25 ` Haipeng Lin
2026-11-04 7:04 ` [PATCH 2/5] arm64: dts: qcom: sc8180x: Add " Val Packett
2026-11-04 7:22 ` sashiko-bot
2026-11-04 8:36 ` Konrad Dybcio
2026-11-04 9:05 ` Val Packett
2026-11-15 3:16 ` Haipeng Lin
2026-11-15 8:20 ` Val Packett
2026-11-15 16:28 ` Haipeng Lin [this message]
2026-11-04 7:04 ` [PATCH 3/5] firmware: qcom: scm: Allow QSEECOM on the " Val Packett
2026-11-04 7:09 ` sashiko-bot
2026-11-04 7:04 ` [PATCH 4/5] rtc: Add basic support for RTC via Surface System Aggregator Module Val Packett
2026-11-04 7:13 ` sashiko-bot
2026-11-04 18:44 ` Alexandre Belloni
2026-11-04 7:04 ` [PATCH 5/5] platform/surface: aggregator_registry: Add support for Surface Pro X Val Packett
2026-11-04 7:09 ` sashiko-bot
2026-11-15 2:53 ` [PATCH 0/5] Add support for the Microsoft " Haipeng Lin
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=b92385e0-d39a-430c-925e-93dd978769dd@gmail.com \
--to=jimmie.lin@gmail.com \
--cc=abelvesa@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=luzmaximilian@gmail.com \
--cc=robh@kernel.org \
--cc=val@packett.cool \
/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