From: Georg Gottleuber <g.gottleuber@tuxedocomputers.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Georg Gottleuber <ggo@tuxedocomputers.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Ettore Chimenti <ettore.chimenti@linaro.org>,
Srinivas Kandagatla <srini@kernel.org>,
stefan.schmidt@linaro.org, stephan.gerhold@linaro.org,
wse@tuxedocomputers.com, cs@tuxedo.de
Subject: Re: [PATCH v2 6/7] arm64: dts: qcom: Add device tree for TUXEDO Elite 14 Gen1
Date: Fri, 7 Nov 2025 11:21:12 +0100 [thread overview]
Message-ID: <d1ed14ce-a948-4346-b6ae-4cda29a6a963@tuxedocomputers.com> (raw)
In-Reply-To: <20251106-excellent-cooperative-finch-5b379f@kuoka>
Am 06.11.25 um 09:13 schrieb Krzysztof Kozlowski:
> On Wed, Nov 05, 2025 at 04:41:06PM +0100, Georg Gottleuber wrote:
>>
>> Signed-off-by: Georg Gottleuber <ggo@tuxedocomputers.com>
>> Signed-off-by: Srinivas Kandagatla <srini@kernel.org>
>> Signed-off-by: Ettore Chimenti <ettore.chimenti@linaro.org>
>
> Wrong order of tags. Ettore is not sending this.
Ack.
>> ---
>> arch/arm64/boot/dts/qcom/Makefile | 2 +
>> .../qcom/x1e80100-tuxedo-elite-14-gen1.dts | 1486 +++++++++++++++++
>> 2 files changed, 1488 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 296688f7cb26..598bf4c6e84a 100644
>> --- a/arch/arm64/boot/dts/qcom/Makefile
>> +++ b/arch/arm64/boot/dts/qcom/Makefile
>> @@ -350,3 +350,5 @@ x1p42100-hp-omnibook-x14-el2-dtbs := x1p42100-hp-omnibook-x14.dtb x1-el2.dtbo
>> dtb-$(CONFIG_ARCH_QCOM) += x1p42100-hp-omnibook-x14.dtb x1p42100-hp-omnibook-x14-el2.dtb
>> x1p42100-lenovo-thinkbook-16-el2-dtbs := x1p42100-lenovo-thinkbook-16.dtb x1-el2.dtbo
>> dtb-$(CONFIG_ARCH_QCOM) += x1p42100-lenovo-thinkbook-16.dtb x1p42100-lenovo-thinkbook-16-el2.dtb
>> +x1e80100-tuxedo-elite-14-gen1-el2-dtbs := x1e80100-tuxedo-elite-14-gen1.dtb x1-el2.dtbo
>> +dtb-$(CONFIG_ARCH_QCOM) += x1e80100-tuxedo-elite-14-gen1.dtb
>
> Messed ordering. Please do not add to the end of lists. This applies
> almost EVERYWHERE, for every sort of change because it only introduces
> unnecessary conflicts when applying multiple patchsets.
Ack.>
>> + /*
>> + * TODO: These two regulators are actually part of the removable M.2
>> + * card and not the mainboard. Need to describe this differently.
>> + * Functionally it works correctly, because all we need to do is to
>> + * turn on the actual 3.3V supply above.
>> + */
>> + vreg_wcn_0p95: regulator-wcn-0p95 {
>> + compatible = "regulator-fixed";
>> +
>> + regulator-name = "VREG_WCN_0P95";
>> + regulator-min-microvolt = <950000>;
>> + regulator-max-microvolt = <950000>;
>> +
>> + vin-supply = <&vreg_wcn_3p3>;
>> + };
>> +
>> + vreg_wcn_1p9: regulator-wcn-1p9 {
>> + compatible = "regulator-fixed";
>> +
>> + regulator-name = "VREG_WCN_1P9";
>> + regulator-min-microvolt = <1900000>;
>> + regulator-max-microvolt = <1900000>;
>> +
>> + vin-supply = <&vreg_wcn_3p3>;
>> + };
>> +
>> + vreg_rtmr0_1p15: regulator-rtmr0-1p15 {
>
> w > r, please keep things ordered. See also DTS coding style.
Ack.
>> + compatible = "regulator-fixed";
>> +
>> + regulator-name = "VREG_RTMR0_1P15";
>> + regulator-min-microvolt = <1150000>;
>> + regulator-max-microvolt = <1150000>;
>> +
>> + gpio = <&pmc8380_5_gpios 8 GPIO_ACTIVE_HIGH>;
>> + enable-active-high;
>> +
>> + pinctrl-0 = <&usb0_pwr_1p15_reg_en>;
>> + pinctrl-names = "default";
>> +
>> + regulator-boot-on;
>> + };
>> +
>> + vreg_rtmr0_1p8: regulator-rtmr0-1p8 {
>> + compatible = "regulator-fixed";
>> +
>> + regulator-name = "VREG_RTMR0_1P8";
>> + regulator-min-microvolt = <1800000>;
>> + regulator-max-microvolt = <1800000>;
>> +
>> + gpio = <&pm8550ve_9_gpios 8 GPIO_ACTIVE_HIGH>;
>> + enable-active-high;
>> +
>> + pinctrl-0 = <&usb0_1p8_reg_en>;
>> + pinctrl-names = "default";
>> +
>> + regulator-boot-on;
>> + };
>> +
>> + vreg_rtmr0_3p3: regulator-rtmr0-3p3 {
>> + compatible = "regulator-fixed";
>> +
>> + regulator-name = "VREG_RTMR0_3P3";
>> + regulator-min-microvolt = <3300000>;
>> + regulator-max-microvolt = <3300000>;
>> +
>> + gpio = <&pm8550_gpios 11 GPIO_ACTIVE_HIGH>;
>> + enable-active-high;
>> +
>> + pinctrl-0 = <&usb0_3p3_reg_en>;
>> + pinctrl-names = "default";
>> +
>> + regulator-boot-on;
>> + };
>> +
>> + sound {
>> + compatible = "qcom,x1e80100-sndcard";
>> + model = "X1E80100-TUXEDO-Elite-14";
>> + audio-routing = "WooferLeft IN", "WSA WSA_SPK1 OUT",
>> + "TweeterLeft IN", "WSA WSA_SPK2 OUT",
>> + "WooferRight IN", "WSA2 WSA_SPK2 OUT",
>> + "TweeterRight IN", "WSA2 WSA_SPK2 OUT",
>> + "IN1_HPHL", "HPHL_OUT",
>> + "IN2_HPHR", "HPHR_OUT",
>> + "AMIC2", "MIC BIAS2",
>> + "VA DMIC0", "MIC BIAS1",
>> + "VA DMIC1", "MIC BIAS1",
>> + "VA DMIC0", "VA MIC BIAS1",
>> + "VA DMIC1", "VA MIC BIAS1",
>> + "TX SWR_INPUT1", "ADC2_OUTPUT";
>> +
>
> No USB ports for DisplayPort/HDMI audio? I think I saw HDMI connector.
We are going to add that to v3.
Regards,
Georg
>
> Best regards,
> Krzysztof
>
next prev parent reply other threads:[~2025-11-07 10:21 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-05 15:41 [PATCH v2 0/7] Add TUXEDO Elite 14 Gen1 (X1E78100) Georg Gottleuber
2025-11-05 15:41 ` [PATCH v2 1/7] dt-bindings: vendor-prefixes: Add ASL Xiamen Technology Georg Gottleuber
2025-11-06 8:05 ` Krzysztof Kozlowski
2025-11-06 11:12 ` Ettore Chimenti
2025-11-06 11:15 ` Georg Gottleuber
2025-11-06 8:07 ` Krzysztof Kozlowski
2025-11-06 10:29 ` Georg Gottleuber
2025-11-05 15:41 ` [PATCH v2 2/7] dt-bindings: display: bridge: simple: document the ASL CS5263 DP-to-HDMI bridge Georg Gottleuber
2025-11-05 15:41 ` [PATCH v2 3/7] drm/bridge: simple: add " Georg Gottleuber
2025-11-05 15:41 ` [PATCH v2 4/7] dt-bindings: vendor-prefixes: Add prefix for TUXEDO Computers GmbH Georg Gottleuber
2025-11-06 8:08 ` Krzysztof Kozlowski
2025-11-05 15:41 ` [PATCH v2 5/7] dt-bindings: arm: qcom: Add TUXEDO Computers device Georg Gottleuber
2025-11-06 8:06 ` Krzysztof Kozlowski
2025-11-06 16:50 ` Georg Gottleuber
2025-11-06 8:32 ` Krzysztof Kozlowski
2025-11-06 10:52 ` Georg Gottleuber
2025-11-05 15:41 ` [PATCH v2 6/7] arm64: dts: qcom: Add device tree for TUXEDO Elite 14 Gen1 Georg Gottleuber
2025-11-06 7:03 ` Maud Spierings
2025-11-06 8:13 ` Krzysztof Kozlowski
2025-11-07 10:21 ` Georg Gottleuber [this message]
2025-11-06 10:20 ` Konrad Dybcio
2025-11-10 13:41 ` Stephan Gerhold
2025-11-11 4:11 ` Bjorn Andersson
2025-11-11 9:54 ` Stephan Gerhold
2025-11-12 10:45 ` Georg Gottleuber
2025-11-12 13:50 ` Georg Gottleuber
2025-11-05 15:41 ` [PATCH v2 7/7] firmware: qcom: scm: Allow QSEECOM on Tuxedo " Georg Gottleuber
2025-11-06 8:09 ` Krzysztof Kozlowski
2025-11-06 8:15 ` [PATCH v2 0/7] Add TUXEDO Elite 14 Gen1 (X1E78100) Krzysztof Kozlowski
2025-11-06 12:56 ` Georg Gottleuber
2025-11-10 11:50 ` Georg Gottleuber
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=d1ed14ce-a948-4346-b6ae-4cda29a6a963@tuxedocomputers.com \
--to=g.gottleuber@tuxedocomputers.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=cs@tuxedo.de \
--cc=devicetree@vger.kernel.org \
--cc=ettore.chimenti@linaro.org \
--cc=ggo@tuxedocomputers.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=srini@kernel.org \
--cc=stefan.schmidt@linaro.org \
--cc=stephan.gerhold@linaro.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;
as well as URLs for NNTP newsgroup(s).