From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Sibi Sankar <quic_sibis@quicinc.com>,
Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-remoteproc@vger.kernel.org,
Johan Hovold <johan+linaro@kernel.org>,
Xilin Wu <wuxilin123@gmail.com>,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
Steev Klimaszewski <steev@kali.org>,
Alexey Minnekhanov <alexeymin@postmarketos.org>,
Chris Lew <quic_clew@quicinc.com>,
Neil Armstrong <neil.armstrong@linaro.org>
Subject: [PATCH v9 2/5] soc: qcom: pdr: fix parsing of domains lists
Date: Sat, 22 Jun 2024 01:03:41 +0300 [thread overview]
Message-ID: <20240622-qcom-pd-mapper-v9-2-a84ee3591c8e@linaro.org> (raw)
In-Reply-To: <20240622-qcom-pd-mapper-v9-0-a84ee3591c8e@linaro.org>
While parsing the domains list, start offsets from 0 rather than from
domains_read. The domains_read is equal to the total count of the
domains we have seen, while the domains list in the message starts from
offset 0.
Fixes: fbe639b44a82 ("soc: qcom: Introduce Protection Domain Restart helpers")
Tested-by: Steev Klimaszewski <steev@kali.org>
Tested-by: Alexey Minnekhanov <alexeymin@postmarketos.org>
Reviewed-by: Chris Lew <quic_clew@quicinc.com>
Tested-by: Neil Armstrong <neil.armstrong@linaro.org> # on SM8550-QRD
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
---
drivers/soc/qcom/pdr_interface.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/soc/qcom/pdr_interface.c b/drivers/soc/qcom/pdr_interface.c
index 76a62c2ecc58..216166e98fae 100644
--- a/drivers/soc/qcom/pdr_interface.c
+++ b/drivers/soc/qcom/pdr_interface.c
@@ -417,7 +417,7 @@ static int pdr_locate_service(struct pdr_handle *pdr, struct pdr_service *pds)
if (ret < 0)
goto out;
- for (i = domains_read; i < resp->domain_list_len; i++) {
+ for (i = 0; i < resp->domain_list_len; i++) {
entry = &resp->domain_list[i];
if (strnlen(entry->name, sizeof(entry->name)) == sizeof(entry->name))
--
2.39.2
next prev parent reply other threads:[~2024-06-21 22:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-21 22:03 [PATCH v9 0/5] soc: qcom: add in-kernel pd-mapper implementation Dmitry Baryshkov
2024-06-21 22:03 ` [PATCH v9 1/5] soc: qcom: pdr: protect locator_addr with the main mutex Dmitry Baryshkov
2024-06-25 0:52 ` Chris Lew
2024-06-21 22:03 ` Dmitry Baryshkov [this message]
2024-06-21 22:03 ` [PATCH v9 3/5] soc: qcom: pdr: extract PDR message marshalling data Dmitry Baryshkov
2024-06-21 22:03 ` [PATCH v9 4/5] soc: qcom: add pd-mapper implementation Dmitry Baryshkov
2024-06-21 22:03 ` [PATCH v9 5/5] remoteproc: qcom: enable in-kernel PD mapper Dmitry Baryshkov
2024-06-25 3:16 ` (subset) [PATCH v9 0/5] soc: qcom: add in-kernel pd-mapper implementation Bjorn Andersson
2024-06-25 16:45 ` 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=20240622-qcom-pd-mapper-v9-2-a84ee3591c8e@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=alexeymin@postmarketos.org \
--cc=andersson@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--cc=johan+linaro@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=neil.armstrong@linaro.org \
--cc=quic_clew@quicinc.com \
--cc=quic_sibis@quicinc.com \
--cc=steev@kali.org \
--cc=wuxilin123@gmail.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).