[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <a3c932d1-a102-ce18-deea-18cbbd05ecab@linaro.org>
Date: Thu, 19 May 2022 12:44:58 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Bjorn Andersson <bjorn.andersson@...aro.org>,
Rob Herring <robh@...nel.org>, Stephen Boyd <sboyd@...nel.org>,
Arnd Bergmann <arnd@...db.de>, Andy Gross <agross@...nel.org>,
Olof Johansson <olof@...om.net>
Cc: "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
linux-arm-msm <linux-arm-msm@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Removal of qcom,board-id and qcom,msm-id
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
Powered by blists - more mailing lists