From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Georg Gottleuber <ggo@tuxedocomputers.com>,
Bjorn Andersson <andersson@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, wse@tuxedocomputers.com,
cs@tuxedocomputers.com
Subject: Re: [PATCH] arm64: dts: qcom: Add device tree for TUXEDO Elite 14 Gen1
Date: Thu, 6 Mar 2025 13:50:56 +0100 [thread overview]
Message-ID: <5e72992c-170c-48b9-8df4-2caf31c4ae44@oss.qualcomm.com> (raw)
In-Reply-To: <57589859-fec1-4875-9127-d1f99e40a827@tuxedocomputers.com>
On 6.03.2025 1:25 PM, Georg Gottleuber wrote:
> Initial support for TUXEDO Elite 14 Gen1 based on Qualcomm Snapdragon X
> Elite SoC (X1E78100).
>
> Working:
> * Touchpad
> * Keyboard
> * eDP (no brightness control yet)
in case your panel as a PWM backlight, you will need to set the PWM
output pin function explicitly, see x1e80100-microsoft-romulus.dtsi
> * NVMe
> * USB Type-C port
> * WiFi (WiFi 7 untested)
> * GPU (software rendering)
>
> Not working:
> * GPU (WIP: firmware loading but output is jerky)
Please tell us more
> * USB Type-A (WIP)
> * Suspend with substantial energy saving
> * Audio, Speakers, Microphones
> * Camera
> * Fingerprint Reader
If it's connected to the multiport controller, you should be able to
just enable it, like on the T14s, similarly to the Type-A port
[...]
> Signed-off-by: Georg Gottleuber <ggo@tuxedocomputers.com>
> ---
> arch/arm64/boot/dts/qcom/Makefile | 1 +
> .../qcom/x1e80100-tuxedo-elite-14-gen1.dts | 798 ++++++++++++++++++
> 2 files changed, 799 insertions(+)
> create mode 100644
> arch/arm64/boot/dts/qcom/x1e80100-tuxedo-elite-14-gen1.dts
>
> diff --git a/arch/arm64/boot/dts/qcom/Makefile b/arch/arm64/boot/dts/qcom/Makefile
> index 140b0b2abfb5..f0a9d677d957 100644
> --- a/arch/arm64/boot/dts/qcom/Makefile
> +++ b/arch/arm64/boot/dts/qcom/Makefile
> @@ -298,3 +298,4 @@ dtb-$(CONFIG_ARCH_QCOM) += x1e80100-lenovo-yoga-slim7x.dtb
> dtb-$(CONFIG_ARCH_QCOM) += x1e80100-microsoft-romulus13.dtb
> dtb-$(CONFIG_ARCH_QCOM) += x1e80100-microsoft-romulus15.dtb
> dtb-$(CONFIG_ARCH_QCOM) += x1e80100-qcp.dtb
> +dtb-$(CONFIG_ARCH_QCOM) += x1e80100-tuxedo-elite-14-gen1.dtb
> diff --git a/arch/arm64/boot/dts/qcom/x1e80100-tuxedo-elite-14-gen1.dts b/arch/arm64/boot/dts/qcom/x1e80100-tuxedo-elite-14-gen1.dts
> new file mode 100644
> index 000000000000..86bdec4a2dd8
> --- /dev/null
> +++ b/arch/arm64/boot/dts/qcom/x1e80100-tuxedo-elite-14-gen1.dts
> @@ -0,0 +1,798 @@
> +// SPDX-License-Identifier: BSD-3-Clause
> +/*
> + * Copyright (c) 2023 Qualcomm Innovation Center, Inc. All rights reserved.
> + * Copyright (c) 2025 TUXEDO Computers GmbH
> + */
> +
> +/dts-v1/;
> +
> +#include <dt-bindings/gpio/gpio.h>
> +#include <dt-bindings/regulator/qcom,rpmh-regulator.h>
> +
> +#include "x1e80100.dtsi"
> +#include "x1e80100-pmics.dtsi"
> +
> +/ {
> + model = "TUXEDO Elite 14 Gen1";
Please use 8-wide tabs instead of spaces
> + compatible = "tuxedo,elite14gen1", "qcom,x1e80100";
You'll need to define a new vendor in:
Documentation/devicetree/bindings/vendor-prefixes.yaml
[...]
> + vreg_edp_3p3: regulator-edp-3p3 {
> + compatible = "regulator-fixed";
> +
> + regulator-name = "VREG_EDP_3P3";
> + regulator-min-microvolt = <3300000>;
> + regulator-max-microvolt = <3300000>;
> +
> + // EDP_VDD_EN_GPIO54
C-style (/* foo */) comments are preferred, but these ones can be
removed, as they repeat what the code says
[...]
> +&gpu {
> + status = "okay";
> +
> + zap-shader {
> + firmware-name = "qcom/a740_zap.mbn";
Are the laptop's OEM key/security fuses not blown?
Konrad
next prev parent reply other threads:[~2025-03-06 12:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 12:25 Georg Gottleuber
2025-03-06 12:41 ` Krzysztof Kozlowski
2025-03-06 13:56 ` Georg Gottleuber
2025-03-06 14:03 ` Krzysztof Kozlowski
2025-03-06 16:45 ` Dmitry Baryshkov
2025-03-06 12:50 ` Konrad Dybcio [this message]
2025-03-06 15:22 ` Georg Gottleuber
2025-03-06 18:15 ` Konrad Dybcio
2025-03-06 19:30 ` Michael Srba
2025-03-07 6:45 ` Dmitry Baryshkov
2025-03-18 15:24 ` Georg Gottleuber
2025-03-18 15:57 ` Konrad Dybcio
2025-03-18 17:17 ` Rob Clark
2025-03-18 21:36 ` Dmitry Baryshkov
2025-03-21 15:49 ` Ettore Chimenti
2025-03-21 15:51 ` Dmitry Baryshkov
2025-03-28 11:34 ` Georg Gottleuber
2025-03-28 12:42 ` Dmitry Baryshkov
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=5e72992c-170c-48b9-8df4-2caf31c4ae44@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=cs@tuxedocomputers.com \
--cc=devicetree@vger.kernel.org \
--cc=ggo@tuxedocomputers.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=wse@tuxedocomputers.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
all inboxes | Powered by JetHome®