From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Stephen Boyd <sboyd@kernel.org>
Cc: Andy Gross <agross@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Olof Johansson <olof@lixom.net>, Rob Herring <robh@kernel.org>,
"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: Re: Removal of qcom,board-id and qcom,msm-id
Date: Sun, 22 May 2022 12:26:57 +0200 [thread overview]
Message-ID: <eb915633-4d88-ec9a-d51a-7d5f5ecc0843@linaro.org> (raw)
In-Reply-To: <CAA8EJpqjcAcoooaZ6iTSCy4B1x4=HTUgvJ4VqX_Fr_hSMEbfDA@mail.gmail.com>
On 20/05/2022 03:39, Dmitry Baryshkov wrote:
>
>>
>> I vaguely recall that the properties had to be extracted during the
>> boot.img creation process to create a table of contents header. But
>> after some time the bootloader started scanning the DTBs directly for
>> the vendor properties and thus the header was deprecated/removed. If the
>> bootloader is doing the scanning then I'm not sure what is preventing
>> the properties from being documented and allowed. I think the main
>> rejection was that the properties were added purely to be extracted
>> during post processing and placed into the table of contents header,
>> i.e. they weren't actually used by the kernel or the bootloader. If they
>> are now used by the bootloader it sounds OK to me if they're kept
>> around.
>
> Yes, as far as I understand, they are used by the bootloader directly.
>
I entirely missed one part - Stephen's patches from 2015 were actually
applied and since 2015 we expect all boards to follow convention:
compatible =
"qcom,<SoC>[-<soc_version>][-<foundry_id>]-<board>[/<subtype>][-<board_version>]"
The patchset was accepted, although in the thread I do not see "Applied"
message.
Stephen,
can you or anyone else confirm that the dtbTool Qualcomm uses (and/or
bootloader) are adjusted as well to these new compatibles?
If yes, we can simply remove board-id and msm-id properties from new
boards, because 7 years was enough to switch to these new tools...
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-05-22 10:27 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-19 10:44 Krzysztof Kozlowski
2022-05-19 11:39 ` 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 [this message]
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=eb915633-4d88-ec9a-d51a-7d5f5ecc0843@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=dmitry.baryshkov@linaro.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
all inboxes | Powered by JetHome®