From: Douglas Anderson <dianders@chromium.org>
To: Bjorn Andersson <andersson@kernel.org>
Cc: mka@chromium.org, swboyd@chromium.org,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Douglas Anderson <dianders@chromium.org>,
Andy Gross <agross@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/4] arm64: dts: qcom: sc7180: Delete a few unused trogdor dts files
Date: Wed, 1 Mar 2023 10:50:02 -0800 [thread overview]
Message-ID: <20230301185007.1101006-1-dianders@chromium.org> (raw)
In general on ChromeOS we try hard not to throw away perfectly good
hardware, even if it has a few quirks. Many people keep early versions
of boards around indefinitely and keep using them for testing /
development if the feature they're working on doesn't need the latest
and greatest. This is the reason why there are so many sc7180-trogdor
device tree files.
That being said, _very_ early hardware tends not to be kept. -rev0
hardware tends (not always) to be prototype hardware and often comes
as a pile of parts. People are really only willing to put up with this
for so long. Even if it's not a pile of parts, -rev0 tends to be a
very small production run and isn't widely distributed. That means
that, by and large, we can eventually drop support for -rev0. Here,
we'll do that for kingoftown and wormdingler, and lazor.
While looking at the -rev0 of mrbland, I noticed that mrbland appears
to be long dead and unlikely to be revived. Let's just fully delete
it.
Douglas Anderson (4):
arm64: dts: qcom: sc7180: Delete wormdingler-rev0
arm64: dts: qcom: sc7180: Delete kingoftown-rev0
arm64: dts: qcom: sc7180: Delete lazor-rev0
arm64: dts: qcom: sc7180: Delete mrbland
arch/arm64/boot/dts/qcom/Makefile | 10 +-
.../dts/qcom/sc7180-trogdor-kingoftown-r0.dts | 38 ---
...n-r1.dts => sc7180-trogdor-kingoftown.dts} | 0
.../boot/dts/qcom/sc7180-trogdor-lazor-r0.dts | 34 --
.../qcom/sc7180-trogdor-mrbland-rev0-auo.dts | 22 --
.../qcom/sc7180-trogdor-mrbland-rev0-boe.dts | 22 --
.../dts/qcom/sc7180-trogdor-mrbland-rev0.dtsi | 36 --
.../qcom/sc7180-trogdor-mrbland-rev1-auo.dts | 22 --
.../qcom/sc7180-trogdor-mrbland-rev1-boe.dts | 24 --
.../boot/dts/qcom/sc7180-trogdor-mrbland.dtsi | 320 ------------------
.../sc7180-trogdor-wormdingler-rev0-boe.dts | 22 --
.../sc7180-trogdor-wormdingler-rev0-inx.dts | 22 --
12 files changed, 1 insertion(+), 571 deletions(-)
delete mode 100644 arch/arm64/boot/dts/qcom/sc7180-trogdor-kingoftown-r0.dts
rename arch/arm64/boot/dts/qcom/{sc7180-trogdor-kingoftown-r1.dts => sc7180-trogdor-kingoftown.dts} (100%)
delete mode 100644 arch/arm64/boot/dts/qcom/sc7180-trogdor-lazor-r0.dts
delete mode 100644 arch/arm64/boot/dts/qcom/sc7180-trogdor-mrbland-rev0-auo.dts
delete mode 100644 arch/arm64/boot/dts/qcom/sc7180-trogdor-mrbland-rev0-boe.dts
delete mode 100644 arch/arm64/boot/dts/qcom/sc7180-trogdor-mrbland-rev0.dtsi
delete mode 100644 arch/arm64/boot/dts/qcom/sc7180-trogdor-mrbland-rev1-auo.dts
delete mode 100644 arch/arm64/boot/dts/qcom/sc7180-trogdor-mrbland-rev1-boe.dts
delete mode 100644 arch/arm64/boot/dts/qcom/sc7180-trogdor-mrbland.dtsi
delete mode 100644 arch/arm64/boot/dts/qcom/sc7180-trogdor-wormdingler-rev0-boe.dts
delete mode 100644 arch/arm64/boot/dts/qcom/sc7180-trogdor-wormdingler-rev0-inx.dts
--
2.39.2.722.g9855ee24e9-goog
next reply other threads:[~2023-03-01 18:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 18:50 Douglas Anderson [this message]
2023-03-01 18:50 ` [PATCH 1/4] arm64: dts: qcom: sc7180: Delete wormdingler-rev0 Douglas Anderson
2023-03-01 21:59 ` Konrad Dybcio
2023-03-01 18:50 ` [PATCH 2/4] arm64: dts: qcom: sc7180: Delete kingoftown-rev0 Douglas Anderson
2023-03-01 22:02 ` Konrad Dybcio
2023-03-01 18:50 ` [PATCH 3/4] arm64: dts: qcom: sc7180: Delete lazor-rev0 Douglas Anderson
2023-03-01 22:03 ` Konrad Dybcio
2023-03-01 18:50 ` [PATCH 4/4] arm64: dts: qcom: sc7180: Delete mrbland Douglas Anderson
2023-03-01 22:05 ` Konrad Dybcio
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=20230301185007.1101006-1-dianders@chromium.org \
--to=dianders@chromium.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mka@chromium.org \
--cc=robh+dt@kernel.org \
--cc=swboyd@chromium.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;
as well as URLs for NNTP newsgroup(s).