From: Krzysztof Kozlowski <krzk@kernel.org>
To: weifu wu <wwfu06@163.com>,
andersson@kernel.org, konradybcio@kernel.org, robh@kernel.org
Cc: krzk+dt@kernel.org, conor+dt@kernel.org,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/2] arm64: dts: qcom: add Acer Swift SFA14-11 device tree
Date: Wed, 21 Jan 2026 12:50:44 +0100 [thread overview]
Message-ID: <f7c36665-71c2-4f80-82db-47ebdc1d9449@kernel.org> (raw)
In-Reply-To: <20260121112721.2981491-3-wwfu06@163.com>
On 21/01/2026 12:27, weifu wu wrote:
> Add initial device tree for Acer Swift SFA14-11 laptop based on Qualcomm X1E78100 SoC.
Do not write
each sentence
in each line.
>
> Generated based on x1e78100-lenovo-thinkpad-t14s.dts.
>
> Adjusted node ordering according to review feedback.
Drop, not relevant. Is this changelog part?
>
> Passed format checks and successfully built without errors.
Drop, not relevant. Is this changelog part?
>
> Signed-off-by: weifu wu <wwfu06@163.com>
> ---
> arch/arm64/boot/dts/qcom/Makefile | 2 +
> .../dts/qcom/x1e78100-acer-swift-sfa14-11.dts | 1784 +++++++++++++++++
> 2 files changed, 1786 insertions(+)
> create mode 100644 arch/arm64/boot/dts/qcom/x1e78100-acer-swift-sfa14-11.dts
>
> diff --git a/arch/arm64/boot/dts/qcom/Makefile b/arch/arm64/boot/dts/qcom/Makefile
> index f80b5d9cf1e8..d07587950c8c 100644
> --- a/arch/arm64/boot/dts/qcom/Makefile
> +++ b/arch/arm64/boot/dts/qcom/Makefile
> @@ -350,6 +350,8 @@ dtb-$(CONFIG_ARCH_QCOM) += sm8750-mtp.dtb
> dtb-$(CONFIG_ARCH_QCOM) += sm8750-qrd.dtb
> x1e001de-devkit-el2-dtbs := x1e001de-devkit.dtb x1-el2.dtbo
> dtb-$(CONFIG_ARCH_QCOM) += x1e001de-devkit.dtb x1e001de-devkit-el2.dtb
> +x1e78100-acer-swift-sfa14-11-el2-dtbs := x1e78100-acer-swift-sfa14-11.dtb x1-el2.dtbo
> +dtb-$(CONFIG_ARCH_QCOM) += x1e78100-acer-swift-sfa14-11.dtb x1e78100-acer-swift-sfa14-11-el2.dtb
> x1e78100-lenovo-thinkpad-t14s-el2-dtbs := x1e78100-lenovo-thinkpad-t14s.dtb x1-el2.dtbo
> dtb-$(CONFIG_ARCH_QCOM) += x1e78100-lenovo-thinkpad-t14s.dtb x1e78100-lenovo-thinkpad-t14s-el2.dtb
> x1e78100-lenovo-thinkpad-t14s-oled-el2-dtbs := x1e78100-lenovo-thinkpad-t14s-oled.dtb x1-el2.dtbo
> diff --git a/arch/arm64/boot/dts/qcom/x1e78100-acer-swift-sfa14-11.dts b/arch/arm64/boot/dts/qcom/x1e78100-acer-swift-sfa14-11.dts
> new file mode 100644
> index 000000000000..13c115e687c6
> --- /dev/null
> +++ b/arch/arm64/boot/dts/qcom/x1e78100-acer-swift-sfa14-11.dts
> @@ -0,0 +1,1784 @@
> +// SPDX-License-Identifier: BSD-3-Clause
> +/*
> + * Copyright (c) 2023 Qualcomm Innovation Center, Inc. All rights reserved.
> + * Copyright (c) 2024, Linaro Limited
> + */
> +
> +/dts-v1/;
> +
> +#include <dt-bindings/gpio/gpio.h>
> +#include <dt-bindings/input/gpio-keys.h>
> +#include <dt-bindings/input/input.h>
> +#include <dt-bindings/pinctrl/qcom,pmic-gpio.h>
> +#include <dt-bindings/regulator/qcom,rpmh-regulator.h>
> +
> +#include "hamoa.dtsi"
> +#include "hamoa-pmics.dtsi"
> +
> +/ {
> + model = "Acer Swift 14 Go Pro AI (SFA14-11)";
> + compatible = "acer,swift-sfa14-11", "lenovo,thinkpad-t14s", "qcom,x1e78100", "qcom,x1e80100";
> + chassis-type = "laptop";
> +
> + aliases {
> + serial0 = &uart21;
No, it does not "Passed format checks" because it has inconsistent white
spaces.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-01-21 11:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-21 11:27 [PATCH v3 0/2] arm64: dts: qcom: add Acer Swift SFA14-11 support weifu wu
2026-01-21 11:27 ` [PATCH v3 1/2] dt-bindings: arm: qcom: add Acer Swift SFA14-11 weifu wu
2026-01-21 11:48 ` Krzysztof Kozlowski
2026-01-28 11:55 ` Konrad Dybcio
2026-01-28 13:19 ` Konrad Dybcio
2026-01-21 11:27 ` [PATCH v3 2/2] arm64: dts: qcom: add Acer Swift SFA14-11 device tree weifu wu
2026-01-21 11:50 ` Krzysztof Kozlowski [this message]
2026-01-28 12:25 ` Konrad Dybcio
2026-01-28 14:05 ` wwf
2026-02-03 11:02 ` Konrad Dybcio
2026-02-05 10:13 ` wwf
2026-02-17 15:15 ` Konrad Dybcio
2026-01-21 11:52 ` [PATCH v3 0/2] arm64: dts: qcom: add Acer Swift SFA14-11 support Krzysztof Kozlowski
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=f7c36665-71c2-4f80-82db-47ebdc1d9449@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=wwfu06@163.com \
/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