From: Stephan Gerhold <stephan.gerhold@linaro.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Georg Gottleuber <ggo@tuxedocomputers.com>,
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, wse@tuxedocomputers.com, cs@tuxedo.de
Subject: Re: [PATCH v3 0/7] Add TUXEDO Elite 14 Gen1 (X1E78100)
Date: Sat, 22 Nov 2025 12:00:11 +0100 [thread overview]
Message-ID: <aSGXu7IhPDNSkYhi@linaro.org> (raw)
In-Reply-To: <af3d3295-1340-417f-8682-7d7e2bc6c812@kernel.org>
On Sat, Nov 22, 2025 at 11:16:25AM +0100, Krzysztof Kozlowski wrote:
> On 21/11/2025 15:26, Georg Gottleuber wrote:
> > [...]
> > Initial support for TUXEDO Elite 14 Gen1 laptop. It is based on Qualcomm
> > Snapdragon X Elite SoC (X1E78100).
> >
> [...]
>
> > Because the SoC is now outdated and some functions still do not work as
> > well as customers would expect from the TUXEDO brand, TUXEDO Elite 14 Gen1
> > will not be offered for sale. We would still like to submit our device
> > tree to the mainline kernel and thus contribute to Linux support for a
> > compatible device sold by Medion (SPRCHRGD 14 S1 Elite). At least in
> > Germany, this device was sold in many large stores. (An official press
> > statement will follow on our website.)
>
> For me this is unmergeable, because we do not take stuff which no one
> uses (no one can even use), and I am sad I put effort in reviewing AFTER
> this was known to be cancelled.
>
I don't think we have any requirement to have a large user base in order
to merge changes. There is already support for plenty of cancelled
products with only a few (if any) remaining users in mainline, e.g.
- Snapdragon X Elite Dev Kit (x1e001de-devkit), shipped only to a
handful of users before cancelled
- All ChromeOS SC7280 devices (including DTB variants for several
revisions of pre-production samples), never shipped to anyone
There are also plenty of internal reference devices that only a handful
of people have access to (MTP, HDK, CRD etc). What makes these any
different? Ettore has been actively testing and contributing to the port
for the TUXEDO laptop, so if he wants to continue that, I don't think
anything speaks against merging this device tree.
In any case, I don't think the time reviewing these changes is wasted:
As Georg wrote, there is also the Medion SPRCHRGD 14 S1 Elite laptop
that uses basically the same hardware design. I'm sure there are (or
eventually will be) users of that device who would appreciate having a
fully-functional device tree ready to use. There is an open issue in one
of the Ubuntu repositories for example [1] to add automatic DTB
selection for it.
In other words, even if we decide against adding support for the
"x1e80100-tuxedo-elite-14-gen1", the same changes renamed to
"x1e80100-medion-sprchrgd-14-s1" would still be valid and valuable.
I wouldn't expect any other changes to be needed, although obviously
someone with access to the device should confirm that before submitting.
Thanks,
Stephan
[1]: https://github.com/ubuntu/stubble/issues/34
next prev parent reply other threads:[~2025-11-22 11:00 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-21 14:26 [PATCH v3 0/7] Add TUXEDO Elite 14 Gen1 (X1E78100) Georg Gottleuber
2025-11-21 14:26 ` [PATCH v3 1/7] dt-bindings: vendor-prefixes: Add ASL Xiamen Technology Georg Gottleuber
2025-11-21 17:26 ` Krzysztof Kozlowski
2025-11-21 14:26 ` [PATCH v3 2/7] dt-bindings: display: bridge: simple: document the ASL CS5263 DP-to-HDMI bridge Georg Gottleuber
2025-11-21 18:03 ` Krzysztof Kozlowski
2025-11-21 14:26 ` [PATCH v3 3/7] drm/bridge: simple: add " Georg Gottleuber
2025-11-21 14:36 ` Neil Armstrong
2025-11-21 14:26 ` [PATCH v3 4/7] dt-bindings: vendor-prefixes: Add prefix for TUXEDO Computers GmbH Georg Gottleuber
2025-11-21 14:26 ` [PATCH v3 5/7] dt-bindings: arm: qcom: Add TUXEDO Computers device Georg Gottleuber
2025-11-21 18:03 ` Krzysztof Kozlowski
2025-11-21 14:26 ` [PATCH v3 6/7] arm64: dts: qcom: Add device tree for TUXEDO Elite 14 Gen1 Georg Gottleuber
2025-11-22 10:07 ` Krzysztof Kozlowski
2025-11-22 10:09 ` Krzysztof Kozlowski
2025-11-22 11:10 ` Georg Gottleuber
2025-11-22 11:23 ` Georg Gottleuber
2025-11-21 14:26 ` [PATCH v3 7/7] firmware: qcom: scm: Allow QSEECOM on Tuxedo " Georg Gottleuber
2025-11-22 10:16 ` [PATCH v3 0/7] Add TUXEDO Elite 14 Gen1 (X1E78100) Krzysztof Kozlowski
2025-11-22 11:00 ` Stephan Gerhold [this message]
2025-11-22 11:15 ` Krzysztof Kozlowski
2025-11-24 14:09 ` Georg Gottleuber
2025-11-25 10:37 ` Neil Armstrong
2025-11-25 10:50 ` Konrad Dybcio
2025-11-25 11:07 ` Ettore Chimenti
2025-11-24 14:34 ` Dmitry Baryshkov
2025-11-24 15:09 ` Krzysztof Kozlowski
2025-11-24 23:41 ` Dmitry Baryshkov
2025-11-25 7:28 ` Krzysztof Kozlowski
2025-11-24 16:58 ` (subset) " Neil Armstrong
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=aSGXu7IhPDNSkYhi@linaro.org \
--to=stephan.gerhold@linaro.org \
--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=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