From: Siddharth Gupta <sidgup@codeaurora.org>
To: bjorn.andersson@linaro.org, agross@kernel.org, ohad@wizery.com,
linux-arm-msm@vger.kernel.org, linux-remoteproc@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Siddharth Gupta <sidgup@codeaurora.org>,
psodagud@codeaurora.org, rishabhb@codeaurora.org
Subject: [PATCH 0/3] soc: qcom: mdt_loader: General improvements
Date: Wed, 6 Jan 2021 13:23:28 -0800 [thread overview]
Message-ID: <1609968211-7579-1-git-send-email-sidgup@codeaurora.org> (raw)
This series of patches improves general functionality for the mdt loader.
Patch 1 adds the ability to dynamically detect hash segment location.
Patch 2 updates the logic used to identify whether the firmware is split or not.
Patch 3 updates the way the metadata is read and generated.
Siddharth Gupta (3):
soc: qcom: mdt_loader: Allow hash at any phdr
soc: qcom: mdt_loader: Handle split bins correctly
soc: qcom: mdt_loader: Read hash from firmware blob
drivers/remoteproc/qcom_q6v5_mss.c | 4 +-
drivers/soc/qcom/mdt_loader.c | 110 ++++++++++++++++++++++++------------
include/linux/soc/qcom/mdt_loader.h | 3 +-
3 files changed, 79 insertions(+), 38 deletions(-)
--
Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
next reply other threads:[~2021-01-06 21:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 21:23 Siddharth Gupta [this message]
2021-01-06 21:23 ` [PATCH 1/3] soc: qcom: mdt_loader: Allow hash at any phdr Siddharth Gupta
2021-01-08 0:03 ` Bjorn Andersson
2021-01-06 21:23 ` [PATCH 2/3] soc: qcom: mdt_loader: Handle split bins correctly Siddharth Gupta
2021-01-08 0:07 ` Bjorn Andersson
2021-01-06 21:23 ` [PATCH 3/3] soc: qcom: mdt_loader: Read hash from firmware blob Siddharth Gupta
2021-01-06 23:41 ` kernel test robot
2021-01-06 23:41 ` kernel test robot
2021-01-08 0:21 ` Bjorn Andersson
2021-01-13 23:01 ` Siddharth Gupta
2021-01-14 17:46 ` Bjorn Andersson
2021-01-17 23:03 ` Siddharth Gupta
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=1609968211-7579-1-git-send-email-sidgup@codeaurora.org \
--to=sidgup@codeaurora.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=ohad@wizery.com \
--cc=psodagud@codeaurora.org \
--cc=rishabhb@codeaurora.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.