From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Bjorn Andersson <bjorn.andersson@linaro.org>,
Rob Herring <robh@kernel.org>, Stephen Boyd <sboyd@kernel.org>,
Arnd Bergmann <arnd@arndb.de>, Andy Gross <agross@kernel.org>,
Olof Johansson <olof@lixom.net>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Removal of qcom,board-id and qcom,msm-id
Date: Thu, 19 May 2022 12:44:58 +0200 [thread overview]
Message-ID: <a3c932d1-a102-ce18-deea-18cbbd05ecab@linaro.org> (raw)
Hi,
There was an old effort of removal of qcom,board-id and qcom,msm-id
properties from Qualcomm SoC-based boards like [1].
First approach was to document them, which (obviously) was not well
received [2] [3] [4].
The solution from Stephen was to encode these in the board compatible,
so bootloader can extract that information. That seemed to receive
positive comments, at least from Rob. [5]
It was 2015... ~7 years later we are still things doing the same way,
still with undocumented properties: qcom,board-id and qcom,msm-id.
I would like to revive that topic, but before I start doing something
pointless - any guidance on last patch from Stephen [5]? Was it ok? Some
early NAKs?
[1]
https://elixir.bootlin.com/linux/v5.18-rc7/source/arch/arm64/boot/dts/qcom/sdm845-oneplus-fajita.dts#L14
[2] https://lore.kernel.org/all/7229476.C4So9noUlf@wuerfel/
[3]
https://lore.kernel.org/all/1450371534-10923-20-git-send-email-mtitinger+renesas@baylibre.com/
[4] https://lore.kernel.org/all/20151119153640.GC893@linaro.org/
[5]
https://lore.kernel.org/all/1448062280-15406-1-git-send-email-sboyd@codeaurora.org/
Best regards,
Krzysztof
next reply other threads:[~2022-05-19 10:45 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-19 10:44 Krzysztof Kozlowski [this message]
2022-05-19 11:39 ` Removal of qcom,board-id and qcom,msm-id Dmitry Baryshkov
2022-05-19 11:53 ` Krzysztof Kozlowski
2022-05-19 12:46 ` Dmitry Baryshkov
[not found] ` <20220519221227.B66D3C385AA@smtp.kernel.org>
2022-05-20 1:39 ` Dmitry Baryshkov
2022-05-20 7:00 ` Krzysztof Kozlowski
2022-05-22 10:26 ` Krzysztof Kozlowski
2022-05-22 10:50 ` Dmitry Baryshkov
2022-05-22 19:51 ` Konrad Dybcio
2022-05-23 5:41 ` Amit Pundir
2022-05-23 7:21 ` Krzysztof Kozlowski
2022-05-23 12:02 ` Konrad Dybcio
2022-05-23 12:14 ` Krzysztof Kozlowski
2022-05-23 15:29 ` Konrad Dybcio
2022-05-23 16:41 ` Trilok Soni
2022-05-23 21:34 ` Bjorn Andersson
2022-05-23 22:13 ` Trilok Soni
2022-05-23 21:29 ` Rob Clark
2022-05-23 21:50 ` Bjorn Andersson
2022-05-23 22:18 ` Dmitry Baryshkov
2022-05-25 17:36 ` Stephan Gerhold
2022-05-26 7:16 ` Krzysztof Kozlowski
2022-06-22 8:21 ` Dmitry Baryshkov
2022-06-22 11:53 ` Konrad Dybcio
2022-06-23 9:55 ` 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=a3c932d1-a102-ce18-deea-18cbbd05ecab@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=agross@kernel.org \
--cc=arnd@arndb.de \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=robh@kernel.org \
--cc=sboyd@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;
as well as URLs for NNTP newsgroup(s).