From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Rob Herring <robh@kernel.org>, Stephan Gerhold <stephan@gerhold.net>
Cc: Bjorn Andersson <andersson@kernel.org>,
Andy Gross <agross@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org
Subject: Re: [PATCH 3/4] dt-bindings: arm: qcom,ids: Add a bunch of older SoCs
Date: Mon, 9 Jan 2023 00:20:55 +0200 [thread overview]
Message-ID: <a86973c7-db5e-ab2c-4b6b-d9c82f76a070@linaro.org> (raw)
In-Reply-To: <20230108214052.GA313089-robh@kernel.org>
On 08/01/2023 23:40, Rob Herring wrote:
> On Wed, Jan 04, 2023 at 12:53:47PM +0100, Stephan Gerhold wrote:
>> Sync the SoC IDs in qcom,ids.h with relevant entries from Qualcomm's LK
>> bootloader [1] that is used for almost all older Qualcomm SoCs.
>>
>> Several of these are already supported, e.g.:
>> - MSM8960 -> APQ8060, MSM8260, ...
>> - MSM8976 -> APQ8076
>> - MSM8956 -> APQ8056
>> Others are currently being worked on, e.g.:
>> - MSM8909(W) -> APQ8009(W), MSM8905, MSM8209, ...
>> - MSM8939 -> MSM8239, ...
>>
>> And even all remaining ones added are close enough to what is already
>> supported so that future support is realistic (if someone steps up to
>> do the work).
>>
>> Add all of them at once to avoid having to add them one by one in the
>> future. This will also benefit other projects making use of the same
>> dt-bindings, e.g. bootloaders where adding support for all these SoCs
>> is a bit easier than on Linux.
>
> The promise was in accepting the properties upstream is we'd only be
> adding these for bootloaders with dtbs that we can't otherwise update or
> change. Do all of those meet this criteria? Seems unlikely.
Most of Qualcomm platforms come with the signed bootloader, so it is
impossible to change it without vendor keys. This might sound bad for
you, but I fear that this list would include most of the platforms until
Qualcomm agrees to rework kernel-bootloader-dtb interaction.
--
With best wishes
Dmitry
next prev parent reply other threads:[~2023-01-08 22:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 11:53 [PATCH 0/4] soc: qcom: socinfo: Add a bunch of older SoCs Stephan Gerhold
2023-01-04 11:53 ` [PATCH 1/4] soc: qcom: socinfo: Fix soc_id order Stephan Gerhold
2023-01-09 9:30 ` Krzysztof Kozlowski
2023-01-04 11:53 ` [PATCH 2/4] dt-bindings: arm: qcom,ids: Add QRD board ID Stephan Gerhold
2023-01-08 21:36 ` Rob Herring
2023-01-04 11:53 ` [PATCH 3/4] dt-bindings: arm: qcom,ids: Add a bunch of older SoCs Stephan Gerhold
2023-01-08 21:40 ` Rob Herring
2023-01-08 22:20 ` Dmitry Baryshkov [this message]
2023-01-09 9:39 ` Stephan Gerhold
2023-01-09 8:43 ` Stephan Gerhold
2023-01-11 19:42 ` Bjorn Andersson
2023-01-12 21:08 ` Rob Herring
2023-01-04 11:53 ` [PATCH 4/4] soc: qcom: socinfo: " Stephan Gerhold
2023-01-18 23:55 ` [PATCH 0/4] " Bjorn Andersson
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=a86973c7-db5e-ab2c-4b6b-d9c82f76a070@linaro.org \
--to=dmitry.baryshkov@linaro.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=phone-devel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=stephan@gerhold.net \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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).