From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.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>,
Luca Weiss <luca.weiss@fairphone.com>,
Alexey Minnekhanov <alexeymin@postmarketos.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: qcom: drop apq8084 support
Date: Wed, 25 Mar 2026 11:09:24 +0100 [thread overview]
Message-ID: <fe12ccfa-d201-4740-a317-e07353a96b1c@oss.qualcomm.com> (raw)
In-Reply-To: <20260325-drop-8084-dt-v1-1-a0255a404355@oss.qualcomm.com>
On 3/25/26 2:45 AM, Dmitry Baryshkov wrote:
> APQ8084 is one of the platforms which gained very little interest
> upstream. It doesn't look like the there was any interest in these
> devices since December 2019. Two devices supported upstream have very
> minumal DT files. Start forgetting about the platform by
> removing DT files.
>
> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
> ---
> ... and start dropping APQ8084-related drivers in +1 or +2 releases, if
> nobody objects.
> ---
+Some pmOS folks - if there's any community interest, please encourage
them to contribute sooner rather than later..
https://wiki.postmarketos.org/wiki/Qualcomm_Snapdragon_805_(APQ8084)
doesn't give much hope though
Too bad - this was a really technically interesting platform, loaded
with all the features you could dream of in 2013!
Konrad
next prev parent reply other threads:[~2026-03-25 10:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 1:45 Dmitry Baryshkov
2026-03-25 10:09 ` Konrad Dybcio [this message]
2026-03-25 10:39 ` Dmitry Baryshkov
2026-03-26 3:19 ` Bjorn Andersson
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=fe12ccfa-d201-4740-a317-e07353a96b1c@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=alexeymin@postmarketos.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.weiss@fairphone.com \
--cc=robh@kernel.org \
/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®