[PATCH v3 0/4] arm64: qcom: x1-vivobook-s15: add X1P42100 variant, restructure dts files
From: Jens Glathe via B4 Relay
Date: Sat Feb 14 2026 - 03:33:27 EST
This patchset adds the X1P42100 variant of the ASUS Vivobook S15 [1]. To avoid
redundant code, it pulls the part that is identical to both variants into
x1-asus-vivobook-s15.dtsi.
I have maintained the X1P42100 variant on my tree for about a year now, it has
been tested by quite a few users. Also added sound (not in this patchset) and
users operate this successfully.
[1]: https://www.asus.com/de/laptops/for-home/vivobook/asus-vivobook-s-15-s5507/techspec/
Signed-off-by: Jens Glathe <jens.glathe@xxxxxxxxxxxxxxxxxxxxxx>
---
Changes in v3:
- Fixed the \nstatus = "okay"; nit
- Dropped the t-b on the bindings commit
- Rebased onto next-20260213
- Link to v2: https://lore.kernel.org/r/20260211-b4-vivobook-v2-0-9f500415d2ed@xxxxxxxxxxxxxxxxxxxxxx
Changes in v2:
- Fixed the bindings mixup and the redundant gpu node in the Purwa dts
- Re-partitioned the patch set to have no new dangling file
- Rebased onto next-20260210
- Thanks to all that commented on the patches.
- Link to v1: https://lore.kernel.org/r/20260208-b4-vivobook-v1-0-3a9b5e153909@xxxxxxxxxxxxxxxxxxxxxx
---
Jens Glathe (4):
dt-bindings: arm: qcom: Add ASUS Vivobook X1P42100 variant
firmware: qcom: scm: allow QSEECOM on ASUS Vivobook X1P42100 variant
arm64: dts: qcom: x1-vivobook-s15: create a common dtsi for Hamoa and Purwa variants
arm64: dts: qcom: x1-vivobook-s15: add Purwa-compatible device tree
Documentation/devicetree/bindings/arm/qcom.yaml | 1 +
arch/arm64/boot/dts/qcom/Makefile | 2 +
arch/arm64/boot/dts/qcom/x1-asus-vivobook-s15.dtsi | 1362 ++++++++++++++++++++
.../boot/dts/qcom/x1e80100-asus-vivobook-s15.dts | 1346 +------------------
.../boot/dts/qcom/x1p42100-asus-vivobook-s15.dts | 44 +
drivers/firmware/qcom/qcom_scm.c | 1 +
6 files changed, 1411 insertions(+), 1345 deletions(-)
---
base-commit: 635c467cc14ebdffab3f77610217c1dacaf88e8c
change-id: 20260118-b4-vivobook-d05546efec82
Best regards,
--
Jens Glathe <jens.glathe@xxxxxxxxxxxxxxxxxxxxxx>