arm64: dts: qcom: x1e80100: add HONOR MagicBook Art 14 devicetree
PATCH 1/1 arm64: dts: qcom: x1e80100: add HONOR MagicBook Art 14 devicetree
Introduce device tree for the HONOR MagicBook Art 14, built on the Qualcomm Snapdragon X Elite SoC (X1E78100).
Supported features:
- Keyboard
- Display
- Touchpad
- Touchscreen
- PCIe ports (pcie4)
- USB type-c, type-a, Magnetic webcam connector
- Wifi (WCN7850)
- ADSP and CDSP
- X1 GPU
- GPIO Keys (Lid switch)
- Audio definition
- UFS storage
Signature · 1 line
wbr, Kirill
From 67677879742e2a36c469cb7a7cbedb327ed4e8b5 Mon Sep 17 00:00:00 2001
From: "Kirill A. Korinsky" <[email protected]>
Date: Sat, 11 Jan 2025 22:45:13 +0100
Subject: [PATCH] arm64: dts: qcom: x1e80100: add HONOR MagicBook Art 14
devicetree
Introduce device tree for the HONOR MagicBook Art 14, built on the Qualcomm Snapdragon X Elite SoC (X1E78100).
Supported features:
- Keyboard
- Display
- Touchpad
- Touchscreen
- PCIe ports (pcie4)
- USB type-c, type-a, Magnetic webcam connector
- Wifi (WCN7850)
- ADSP and CDSP
- X1 GPU
- GPIO Keys (Lid switch)
- Audio definition
- UFS storage
--- arch/arm64/boot/dts/qcom/Makefile | 1 + .../qcom/x1e80100-honor-magicbook-art-14.dts | 1208 +++++++++++++++++ 2 files changed, 1209 insertions(+) create mode 100644 arch/arm64/boot/dts/qcom/x1e80100-honor-magicbook-art-14.dts
arch/arm64/boot/dts/qcom/Makefile +1 -0
@@ -293,6 +293,7 @@ dtb-$(CONFIG_ARCH_QCOM) += x1e78100-lenovo-thinkpad-t14s.dtb dtb-$(CONFIG_ARCH_QCOM) += x1e80100-asus-vivobook-s15.dtb dtb-$(CONFIG_ARCH_QCOM) += x1e80100-crd.dtb dtb-$(CONFIG_ARCH_QCOM) += x1e80100-dell-xps13-9345.dtb +dtb-$(CONFIG_ARCH_QCOM) += x1e80100-honor-magicbook-art-14.dtb dtb-$(CONFIG_ARCH_QCOM) += x1e80100-hp-omnibook-x14.dtb dtb-$(CONFIG_ARCH_QCOM) += x1e80100-lenovo-yoga-slim7x.dtb dtb-$(CONFIG_ARCH_QCOM) += x1e80100-microsoft-romulus13.dtb
arch/arm64/boot/dts/qcom/x1e80100-honor-magicbook-art-14.dts new file +1208 -0
1,208 lines not on this page · raw message
Signature · 1 line
2.47.1
kernel test robot
build botkernel test robot noticed the following build errors:
Hi Kirill,
kernel test robot noticed the following build errors:
[auto build test ERROR on next-20250110]
[cannot apply to robh/for-next v6.13-rc6 v6.13-rc5 v6.13-rc4 linus/master v6.13-rc6] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Kirill-A-Korinsky/arm64-dts-qcom-x1e80100-add-HONOR-MagicBook-Art-14-devicetree/20250112-061420 base: next-20250110 patch link: https://lore.kernel.org/r/871px910m1.wl-kirill%40korins.ky patch subject: [PATCH] arm64: dts: qcom: x1e80100: add HONOR MagicBook Art 14 devicetree config: arm64-randconfig-001-20250112 (https://download.01.org/0day-ci/archive/20250112/[email protected]/config) compiler: aarch64-linux-gcc (GCC) 14.2.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250112/[email protected]/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <[email protected]>
| Closes: https://lore.kernel.org/oe-kbuild-all/[email protected]/
All errors (new ones prefixed by >>):
>> Error: arch/arm64/boot/dts/qcom/x1e80100-honor-magicbook-art-14.dts:1093.1-12 Label or path ufs_mem_hc not found >> Error: arch/arm64/boot/dts/qcom/x1e80100-honor-magicbook-art-14.dts:1102.1-13 Label or path ufs_mem_phy not found
FATAL ERROR: Syntax error parsing input tree
Signature · 2 lines
0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Quoted 24 lines · kernel test robot
Hi Kirill,
kernel test robot noticed the following build errors:
[auto build test ERROR on next-20250110]
[cannot apply to robh/for-next v6.13-rc6 v6.13-rc5 v6.13-rc4 linus/master v6.13-rc6] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]url: https://github.com/intel-lab-lkp/linux/commits/Kirill-A-Korinsky/arm64-dts-qcom-x1e80100-add-HONOR-MagicBook-Art-14-devicetree/20250112-061420 base: next-20250110 patch link: https://lore.kernel.org/r/871px910m1.wl-kirill%40korins.ky patch subject: [PATCH] arm64: dts: qcom: x1e80100: add HONOR MagicBook Art 14 devicetree config: arm64-randconfig-001-20250112 (https://download.01.org/0day-ci/archive/20250112/[email protected]/config) compiler: aarch64-linux-gcc (GCC) 14.2.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250112/[email protected]/reproduce)If you fix the issue in a separate patch/commit (i.e. not just a new version of the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <[email protected]>
| Closes: https://lore.kernel.org/oe-kbuild-all/[email protected]/
Quoted 6 lines
All errors (new ones prefixed by >>):
Quoted 2 lines
Quoted 2 lines
Error: arch/arm64/boot/dts/qcom/x1e80100-honor-magicbook-art-14.dts:1093.1-12 Label or path
ufs_mem_hcnot found
Error: arch/arm64/boot/dts/qcom/x1e80100-honor-magicbook-art-14.dts:1102.1-13 Label or pathufs_mem_phynot foundFATAL ERROR: Syntax error parsing input tree
Ah, here an updated patch with missed piece.
Signature · 1 line
wbr, Kirill
From eb4565c0f61f1568b2ce838c4709e271902cf482 Mon Sep 17 00:00:00 2001
From: "Kirill A. Korinsky" <[email protected]>
Date: Sun, 12 Jan 2025 18:19:58 +0100
Subject: [PATCH] arm64: dts: qcom: x1e80100: add HONOR MagicBook Art 14
devicetree
Introduce device tree for the HONOR MagicBook Art 14, built on the Qualcomm Snapdragon X Elite SoC (X1E78100).
Supported features:
- Keyboard
- Display
- Touchpad
- Touchscreen
- PCIe ports (pcie4)
- USB type-c, type-a, Magnetic webcam connector
- Wifi (WCN7850)
- ADSP and CDSP
- X1 GPU
- GPIO Keys (Lid switch)
- Audio definition
- UFS storage
--- arch/arm64/boot/dts/qcom/Makefile | 1 + .../qcom/x1e80100-honor-magicbook-art-14.dts | 1208 +++++++++++++++++ arch/arm64/boot/dts/qcom/x1e80100.dtsi | 64 + 3 files changed, 1273 insertions(+) create mode 100644 arch/arm64/boot/dts/qcom/x1e80100-honor-magicbook-art-14.dts
arch/arm64/boot/dts/qcom/Makefile +1 -0
@@ -293,6 +293,7 @@ dtb-$(CONFIG_ARCH_QCOM) += x1e78100-lenovo-thinkpad-t14s.dtb dtb-$(CONFIG_ARCH_QCOM) += x1e80100-asus-vivobook-s15.dtb dtb-$(CONFIG_ARCH_QCOM) += x1e80100-crd.dtb dtb-$(CONFIG_ARCH_QCOM) += x1e80100-dell-xps13-9345.dtb +dtb-$(CONFIG_ARCH_QCOM) += x1e80100-honor-magicbook-art-14.dtb dtb-$(CONFIG_ARCH_QCOM) += x1e80100-hp-omnibook-x14.dtb dtb-$(CONFIG_ARCH_QCOM) += x1e80100-lenovo-yoga-slim7x.dtb dtb-$(CONFIG_ARCH_QCOM) += x1e80100-microsoft-romulus13.dtb
arch/arm64/boot/dts/qcom/x1e80100-honor-magicbook-art-14.dts new file +1208 -0
1,208 lines not on this page · raw message
arch/arm64/boot/dts/qcom/x1e80100.dtsi +64 -0
70 lines not on this page · raw message
Signature · 1 line
2.47.1
Rob Herring (Arm)
maintainerQuoted 25 lines · kernel test robot
Hi Kirill,
kernel test robot noticed the following build errors:
[auto build test ERROR on next-20250110]
[cannot apply to robh/for-next v6.13-rc6 v6.13-rc5 v6.13-rc4 linus/master v6.13-rc6] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]url: https://github.com/intel-lab-lkp/linux/commits/Kirill-A-Korinsky/arm64-dts-qcom-x1e80100-add-HONOR-MagicBook-Art-14-devicetree/20250112-061420 base: next-20250110 patch link: https://lore.kernel.org/r/871px910m1.wl-kirill%40korins.ky patch subject: [PATCH] arm64: dts: qcom: x1e80100: add HONOR MagicBook Art 14 devicetree config: arm64-randconfig-001-20250112 (https://download.01.org/0day-ci/archive/20250112/[email protected]/config) compiler: aarch64-linux-gcc (GCC) 14.2.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250112/[email protected]/reproduce)If you fix the issue in a separate patch/commit (i.e. not just a new version of the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <[email protected]>
| Closes: https://lore.kernel.org/oe-kbuild-all/[email protected]/All errors (new ones prefixed by >>):
Quoted 9 lines
Quoted 2 lines
Quoted 2 lines
Error: arch/arm64/boot/dts/qcom/x1e80100-honor-magicbook-art-14.dts:1093.1-12 Label or path
ufs_mem_hcnot found
Error: arch/arm64/boot/dts/qcom/x1e80100-honor-magicbook-art-14.dts:1102.1-13 Label or pathufs_mem_phynot foundFATAL ERROR: Syntax error parsing input tree
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
My bot found new DTB warnings on the .dts files added or changed in this series.
Some warnings may be from an existing SoC .dtsi. Or perhaps the warnings are fixed by another series. Ultimately, it is up to the platform maintainer whether these warnings are acceptable or not. No need to reply unless the platform maintainer has comments.
If you already ran DT checks and didn't see these error(s), then make sure dt-schema is up to date:
pip3 install dtschema --upgrade
New warnings running 'make CHECK_DTBS=y for arch/arm/boot/dts/nxp/' for [email protected]:
arch/arm/boot/dts/nxp/imx/imx6q-dmo-edmqmx6.dtb: /soc/bus@2100000/mipi@21dc000: failed to match any schema with compatible: ['fsl,imx6-mipi-csi2'] arch/arm/boot/dts/nxp/imx/imx6q-cm-fx6.dtb: /soc/bus@2100000/mipi@21dc000: failed to match any schema with compatible: ['fsl,imx6-mipi-csi2'] arch/arm/boot/dts/nxp/imx/imx6q-phytec-mira-rdk-nand.dtb: /display-subsystem: failed to match any schema with compatible: ['fsl,imx-display-subsystem']
Rob Herring (Arm)
maintainerQuoted 18 lines · Kirill A. Korinsky
Introduce device tree for the HONOR MagicBook Art 14, built on the Qualcomm Snapdragon X Elite SoC (X1E78100).
Supported features:
- Keyboard
- Display
- Touchpad
- Touchscreen
- PCIe ports (pcie4)
- USB type-c, type-a, Magnetic webcam connector
- Wifi (WCN7850)
- ADSP and CDSP
- X1 GPU
- GPIO Keys (Lid switch)
- Audio definition
- UFS storage
Quoted 5 lines
Signed-off-by Kirill A. Korinsky <[email protected]>--
wbr, Kirill
My bot found new DTB warnings on the .dts files added or changed in this series.
Some warnings may be from an existing SoC .dtsi. Or perhaps the warnings are fixed by another series. Ultimately, it is up to the platform maintainer whether these warnings are acceptable or not. No need to reply unless the platform maintainer has comments.
If you already ran DT checks and didn't see these error(s), then make sure dt-schema is up to date:
pip3 install dtschema --upgrade
New warnings running 'make CHECK_DTBS=y for arch/arm/boot/dts/aspeed/' for [email protected]:
arch/arm/boot/dts/aspeed/aspeed-bmc-ibm-blueridge-4u.dtb: /ahb/apb/fsi@1e79b100: failed to match any schema with compatible: ['aspeed,ast2600-fsi-master', 'fsi-master']arch/arm/boot/dts/aspeed/aspeed-bmc-inventec-starscream.dtb: /ahb/apb/dma-controller@1e79e000: failed to match any schema with compatible: ['aspeed,ast2600-udma']arch/arm/boot/dts/aspeed/aspeed-bmc-ibm-bonnell.dtb: /: compatible: 'oneOf' conditional failed, one must be fixed:
'ibm,bonnell-bmc' is not one of ['delta,ahe50dc-bmc', 'facebook,galaxy100-bmc', 'facebook,wedge100-bmc', 'facebook,wedge40-bmc', 'microsoft,olympus-bmc', 'quanta,q71l-bmc', 'tyan,palmetto-bmc', 'yadro,vesnin-bmc']
'ibm,bonnell-bmc' is not one of ['amd,daytonax-bmc', 'amd,ethanolx-bmc', 'ampere,mtjade-bmc', 'aspeed,ast2500-evb', 'asrock,e3c246d4i-bmc', 'asrock,e3c256d4i-bmc', 'asrock,romed8hm3-bmc', 'asrock,spc621d8hm3-bmc', 'asrock,x570d4u-bmc', 'bytedance,g220a-bmc', 'facebook,cmm-bmc', 'facebook,minipack-bmc', 'facebook,tiogapass-bmc', 'facebook,yamp-bmc', 'facebook,yosemitev2-bmc', 'facebook,wedge400-bmc', 'hxt,stardragon4800-rep2-bmc', 'ibm,mihawk-bmc', 'ibm,mowgli-bmc', 'ibm,romulus-bmc', 'ibm,swift-bmc', 'ibm,witherspoon-bmc', 'ingrasys,zaius-bmc', 'inspur,fp5280g2-bmc', 'inspur,nf5280m6-bmc', 'inspur,on5263m5-bmc', 'intel,s2600wf-bmc', 'inventec,lanyang-bmc', 'lenovo,hr630-bmc', 'lenovo,hr855xg2-bmc', 'portwell,neptune-bmc', 'qcom,centriq2400-rep-bmc', 'supermicro,x11spi-bmc', 'tyan,s7106-bmc', 'tyan,s8036-bmc', 'yadro,nicole-bmc', 'yadro,vegman-n110-bmc', 'yadro,vegman-rx20-bmc', 'yadro,vegman-sx20-bmc'] 'ibm,bonnell-bmc' is not one of ['ampere,mtmitchell-bmc', 'aspeed,ast2600-evb', 'aspeed,ast2600-evb-a1', 'asus,x4tf-bmc', 'facebook,bletchley-bmc', 'facebook,catalina-bmc', 'facebook,cloudripper-bmc', 'facebook,elbert-bmc', 'facebook,fuji-bmc', 'facebook,greatlakes-bmc', 'facebook,harma-bmc', 'facebook,minerva-cmc', 'facebook,yosemite4-bmc', 'ibm,blueridge-bmc', 'ibm,everest-bmc', 'ibm,fuji-bmc', 'ibm,rainier-bmc', 'ibm,system1-bmc', 'ibm,tacoma-bmc', 'inventec,starscream-bmc', 'inventec,transformer-bmc', 'jabil,rbp-bmc', 'qcom,dc-scm-v1-bmc', 'quanta,s6q-bmc', 'ufispace,ncplite-bmc']
'aspeed,ast2400' was expected
'aspeed,ast2500' was expected
from schema $id: http://devicetree.org/schemas/arm/aspeed/aspeed.yaml#arch/arm/boot/dts/aspeed/aspeed-bmc-ibm-rainier-4u.dtb: i2c3_mux_oe_n: $nodename:0: 'i2c3_mux_oe_n' does not match '^(hog-[0-9]+|.+-hog(-[0-9]+)?)$'
from schema $id: http://devicetree.org/schemas/gpio/gpio-hog.yaml#arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-catalina.dtb: /ahb/apb/bus@1e78a000/i2c@100/i2c-mux@70/i2c@3/delta_brick@63: failed to match any schema with compatible: ['pmbus']arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-catalina.dtb: /ahb/apb/bus@1e78a000/i2c@100/i2c-mux@70/i2c@3/delta_brick@64: failed to match any schema with compatible: ['pmbus']arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-catalina.dtb: /ahb/apb/bus@1e78a000/i2c@100/i2c-mux@70/i2c@3/delta_brick@65: failed to match any schema with compatible: ['pmbus']arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-catalina.dtb: /ahb/apb/bus@1e78a000/i2c@100/i2c-mux@70/i2c@3/delta_brick@66: failed to match any schema with compatible: ['pmbus']arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-catalina.dtb: /ahb/apb/bus@1e78a000/i2c@100/i2c-mux@70/i2c@3/delta_brick@67: failed to match any schema with compatible: ['pmbus']arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-yosemitev2.dtb: /ahb/apb/video@1e700000: failed to match any schema with compatible: ['aspeed,ast2500-video-engine']arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-fuji.dtb: /ahb/apb/sdc@1e740000/sdhci@1e740200: failed to match any schema with compatible: ['aspeed,ast2600-sdhci', 'sdhci']