From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Konrad Dybcio <konrad.dybcio@somainline.org>,
Amit Pundir <amit.pundir@linaro.org>,
Trilok Soni <quic_tsoni@quicinc.com>,
Rob Clark <robdclark@gmail.com>,
Stephan Gerhold <stephan@gerhold.net>,
Kumar Gala <galak@codeaurora.org>,
Stephen Boyd <sboyd@kernel.org>
Subject: Re: [PATCH v2 1/2] dt-bindings: arm: qcom: document qcom,msm-id and qcom,board-id
Date: Wed, 22 Jun 2022 11:49:40 +0200 [thread overview]
Message-ID: <ad2733ea-4a7b-d8d4-0380-3270f9e6bf9a@linaro.org> (raw)
In-Reply-To: <3ccbcaa0-d5b6-9f46-03c3-2a3e0ee72782@linaro.org>
On 22/06/2022 11:44, Dmitry Baryshkov wrote:
> On 21/06/2022 21:56, Krzysztof Kozlowski wrote:
>> The top level qcom,msm-id and qcom,board-id properties are utilized by
>> bootloaders on Qualcomm MSM platforms to determine which device tree
>> should be used and passed to the kernel.
>>
>> The commit b32e592d3c28 ("devicetree: bindings: Document qcom board
>> compatible format") from 2015 was a consensus during discussion about
>> upstreaming qcom,msm-id and qcom,board-id fields. There are however still
>> problems with that consensus:
>> 1. It was reached 7 years ago but it turned out its implementation did
>> not reach all possible products.
>>
>> 2. Initially additional tool (dtbTool) was needed for parsing these
>> fields to create a QCDT image consisting of multiple DTBs, later the
>> bootloaders were improved and they use these qcom,msm-id and
>> qcom,board-id properties directly.
>>
>> 3. Extracting relevant information from the board compatible requires
>> this additional tool (dtbTool), which makes the build process more
>> complicated and not easily reproducible (DTBs are modified after the
>> kernel build).
>>
>> 4. Some versions of Qualcomm bootloaders expect these properties even
>> when booting with a single DTB. The community is stuck with these
>> bootloaders thus they require properties in the DTBs.
>>
>> Since several upstreamed Qualcomm SoC-based boards require these
>> properties to properly boot and the properties are reportedly used by
>> bootloaders, document them.
>>
>> Link: https://lore.kernel.org/r/a3c932d1-a102-ce18-deea-18cbbd05ecab@linaro.org/
>> Co-developed-by: Kumar Gala <galak@codeaurora.org>
>> Signed-off-by: Kumar Gala <galak@codeaurora.org>
>> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>> ---
>> .../devicetree/bindings/arm/qcom.yaml | 123 ++++++++++++++++++
>> include/dt-bindings/arm/qcom,ids.h | 30 +++++
>> 2 files changed, 153 insertions(+)
>> create mode 100644 include/dt-bindings/arm/qcom,ids.h
>>
>> diff --git a/Documentation/devicetree/bindings/arm/qcom.yaml b/Documentation/devicetree/bindings/arm/qcom.yaml
>> index 6c38c1387afd..05b98cde4653 100644
>> --- a/Documentation/devicetree/bindings/arm/qcom.yaml
>> +++ b/Documentation/devicetree/bindings/arm/qcom.yaml
>> @@ -403,6 +403,129 @@ properties:
>> - qcom,sm8450-qrd
>> - const: qcom,sm8450
>>
>> + # Board compatibles go above
>> +
>> + qcom,msm-id:
>> + $ref: /schemas/types.yaml#/definitions/uint32-matrix
>> + minItems: 1
>> + maxItems: 8
>> + items:
>> + items:
>> + - description: |
>> + MSM chipset ID - an exact match value consisting of three bitfields::
>> + - bits 0-15 - The unique MSM chipset ID
>> + - bits 16-31 - Reserved; should be 0
>> + - description: |
>> + Hardware revision ID - a chipset specific 32-bit ID representing
>> + the version of the chipset. It is best a match value - the
>> + bootloader will look for the closest possible match.
>> + deprecated: true
>> + description:
>> + The MSM chipset and hardware revision use by Qualcomm bootloaders. It
>> + can optionally be an array of these to indicate multiple hardware that
>> + use the same device tree. It is expected that the bootloader will use
>> + this information at boot-up to decide which device tree to use when given
>> + multiple device trees, some of which may not be compatible with the
>> + actual hardware. It is the bootloader's responsibility to pass the
>> + correct device tree to the kernel.
>> + The property is deprecated - it is not expected on newer boards
>> + (starting with SM8350).
>
> I have been thinking about this for quite a while. I think this patch is
> good.
>
> With this paragraph (and the corresponding paragraph from the next item)
> rephrased to remove references to 'newer boards':
>
> Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Great, thanks! And thank you for responding in previous discussions.
I'll remove entire "newer boards ..." part, fix the "two bitfields" and
change the name of the define QCOM_ID_MSM8996. I won't add more board
IDs yet, this can be in following up patches (not only my me).
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-06-22 9:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 18:56 [PATCH v2 0/2] dt-bindings: arm: qcom: qcom,board-id and qcom,msm-id Krzysztof Kozlowski
2022-06-21 18:56 ` [PATCH v2 1/2] dt-bindings: arm: qcom: document qcom,msm-id and qcom,board-id Krzysztof Kozlowski
2022-06-21 19:26 ` Dmitry Baryshkov
2022-06-21 19:32 ` Krzysztof Kozlowski
2022-06-21 19:49 ` Dmitry Baryshkov
2022-06-22 7:00 ` Krzysztof Kozlowski
2022-06-22 7:31 ` Dmitry Baryshkov
2022-06-22 9:44 ` Dmitry Baryshkov
2022-06-22 9:49 ` Krzysztof Kozlowski [this message]
2022-06-22 9:50 ` Dmitry Baryshkov
2022-06-21 18:56 ` [PATCH v2 2/2] arm64: dts: qcom: msm8992-xiaomi-libra: split qcom,msm-id into tuples Krzysztof Kozlowski
2022-06-21 19:26 ` 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=ad2733ea-4a7b-d8d4-0380-3270f9e6bf9a@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=agross@kernel.org \
--cc=amit.pundir@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=galak@codeaurora.org \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_tsoni@quicinc.com \
--cc=robdclark@gmail.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=stephan@gerhold.net \
/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®