From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Kathiravan Thirumoorthy
<kathiravan.thirumoorthy@oss.qualcomm.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] soc: qcom: socinfo: Add support to retrieve APPSBL build details
Date: Fri, 11 Jul 2025 15:30:18 +0200 [thread overview]
Message-ID: <493987e4-2b1a-42b1-af5e-85cd9f2a5d7c@oss.qualcomm.com> (raw)
In-Reply-To: <e5bb0197-70e4-4b4e-922f-baaaa2e514c7@oss.qualcomm.com>
On 7/11/25 3:24 PM, Kathiravan Thirumoorthy wrote:
>
> On 7/11/2025 5:41 PM, Konrad Dybcio wrote:
>> On 7/11/25 1:03 PM, Kathiravan Thirumoorthy wrote:
>>> Add support to retrieve APPS (Application Processor Subsystem) Bootloader
>>> image details from SMEM.
>>>
>>> Signed-off-by: Kathiravan Thirumoorthy <kathiravan.thirumoorthy@oss.qualcomm.com>
>>> ---
>> Can we expand the driver with all the known IDs at once instead?
>
> With respect to the IPQ SoCs only APPSBL image detail is missing, which this change address it
Next week someone else will come around and say the same thing
for e.g. automotive platforms
>
> I can expand the list, but unfortunately don't have ways to validate them. I can check internally with folks to test it or even send an RTF. Till then, can this patch go independently?
There is nothing to validate here really, the bootloader either
populates the data or not
For now, this one alone is good to go, but please look into the
broader scope
Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Konrad
next prev parent reply other threads:[~2025-07-11 13:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-11 11:03 Kathiravan Thirumoorthy
2025-07-11 12:11 ` Konrad Dybcio
2025-07-11 13:24 ` Kathiravan Thirumoorthy
2025-07-11 13:30 ` Konrad Dybcio [this message]
2025-07-11 14:05 ` Kathiravan Thirumoorthy
2025-07-17 4:30 ` 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=493987e4-2b1a-42b1-af5e-85cd9f2a5d7c@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=kathiravan.thirumoorthy@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.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®