From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Manikanta Mylavarapu <quic_mmanikan@quicinc.com>,
agross@kernel.org, andersson@kernel.org,
konrad.dybcio@linaro.org, mathieu.poirier@linaro.org,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org, mturquette@baylibre.com, sboyd@kernel.org,
quic_eberman@quicinc.com, kvalo@kernel.org,
loic.poulain@linaro.org, linux-arm-msm@vger.kernel.org,
linux-remoteproc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org
Cc: quic_srichara@quicinc.com, quic_sjaganat@quicinc.com,
quic_kathirav@quicinc.com, quic_anusha@quicinc.com
Subject: Re: [V3,09/11] remoteproc: qcom: Add Hexagon based multipd rproc driver
Date: Thu, 20 Jul 2023 15:13:38 +0200 [thread overview]
Message-ID: <c53c8fc5-a898-df1d-4626-696ffd990796@linaro.org> (raw)
In-Reply-To: <20230718120501.3205661-10-quic_mmanikan@quicinc.com>
On 18/07/2023 14:04, Manikanta Mylavarapu wrote:
> It adds support to bring up remoteproc's on multipd model.
> Pd means protection domain. It's similar to process in Linux.
> Here QDSP6 processor runs each wifi radio functionality on a
> separate process. One process can't access other process
> resources, so this is termed as PD i.e protection domain.
...
> + * User pd boot-info format mentioned below
> + * <Version> <No of elements passing over smem> <Header type> <Header Length>
> + * <Process Id> <Load address> <firmware mem Size>
> + *
> + * Returns 0 on success else negative value on failure.
> + */
> +static int share_upd_bootinfo_to_q6(struct rproc *rproc)
> +{
> + int ret;
> + size_t size;
> + u16 cnt = 0, version;
> + void *ptr;
> + struct q6_wcss *wcss = rproc->priv, *upd_wcss;
> + struct device_node *upd_np;
> + struct platform_device *upd_pdev;
> + struct rproc *upd_rproc;
> + struct userpd_boot_info upd_bootinfo = {0};
> + const struct firmware *fw;
> +
> + ret = qcom_smem_alloc(REMOTE_PID, UPD_BOOT_INFO_SMEM_ID,
> + UPD_BOOT_INFO_SMEM_SIZE);
> + if (ret && ret != -EEXIST) {
> + dev_err(wcss->dev,
> + "failed to allocate q6 bootinfo smem segment\n");
> + return ret;
> + }
> +
> + ptr = qcom_smem_get(REMOTE_PID, UPD_BOOT_INFO_SMEM_ID, &size);
> + if (IS_ERR(ptr) || size != UPD_BOOT_INFO_SMEM_SIZE) {
> + dev_err(wcss->dev,
> + "Unable to acquire smp2p item(%d) ret:%ld\n",
> + UPD_BOOT_INFO_SMEM_ID, PTR_ERR(ptr));
> + return PTR_ERR(ptr);
> + }
> +
> + /* print physical address */
> + dev_info(wcss->dev,
> + "smem phyiscal address:0x%lX\n",
> + (uintptr_t)qcom_smem_virt_to_phys(ptr));
One more thought. Why do you need it? Even if this is not a kernel or
user-space address, why would like to disclose the memory layout? I
think this is contradictory to the kptr_restrict concept.
> +
> + /*Version*/
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-07-20 13:13 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-18 12:04 [V3,00/11] Add multipd remoteproc support Manikanta Mylavarapu
2023-07-18 12:04 ` [V3,01/11] dt-bindings: remoteproc: qcom: Add support for multipd model Manikanta Mylavarapu
2023-07-19 7:11 ` Krzysztof Kozlowski
2023-07-18 12:04 ` [V3,02/11] dt-bindings: clock: qcom: gcc-ipq9574: remove q6 bring up clock macros Manikanta Mylavarapu
2023-07-19 7:14 ` Krzysztof Kozlowski
2023-07-19 7:15 ` Krzysztof Kozlowski
2023-07-19 15:11 ` Manikanta Mylavarapu
2023-07-19 15:21 ` Krzysztof Kozlowski
2023-07-18 12:04 ` [V3,03/11] dt-bindings: clock: qcom: gcc-ipq5332: " Manikanta Mylavarapu
2023-07-19 7:15 ` Krzysztof Kozlowski
2023-07-18 12:04 ` [V3,04/11] clk: qcom: ipq9574: remove q6 bring up clocks Manikanta Mylavarapu
2023-07-18 12:04 ` [V3,05/11] clk: qcom: ipq5332: " Manikanta Mylavarapu
2023-07-18 12:04 ` [V3,06/11] firmware: qcom_scm: ipq5332: add support to pass metadata size Manikanta Mylavarapu
2023-07-18 12:04 ` [V3,07/11] firmware: qcom_scm: ipq5332: add msa lock/unlock support Manikanta Mylavarapu
2023-07-18 12:04 ` [V3,08/11] remoteproc: qcom: q6v5: Add multipd interrupts support Manikanta Mylavarapu
2023-07-18 12:04 ` [V3,09/11] remoteproc: qcom: Add Hexagon based multipd rproc driver Manikanta Mylavarapu
2023-07-19 7:26 ` Krzysztof Kozlowski
2023-07-19 15:32 ` Manikanta Mylavarapu
2023-07-21 7:14 ` Manikanta Mylavarapu
2023-07-19 11:04 ` kernel test robot
2023-07-20 13:13 ` Krzysztof Kozlowski [this message]
2023-07-21 6:33 ` Manikanta Mylavarapu
2023-07-18 12:05 ` [V3,10/11] arm64: dts: qcom: ipq5332: Add nodes to bringup multipd Manikanta Mylavarapu
2023-07-18 12:05 ` [V3,11/11] arm64: dts: qcom: ipq9574: Add nodes to bring up multipd Manikanta Mylavarapu
2023-07-19 7:01 ` [V3,00/11] Add multipd remoteproc support Krzysztof Kozlowski
2023-07-19 7:09 ` Manikanta Mylavarapu
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=c53c8fc5-a898-df1d-4626-696ffd990796@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kvalo@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=loic.poulain@linaro.org \
--cc=mathieu.poirier@linaro.org \
--cc=mturquette@baylibre.com \
--cc=quic_anusha@quicinc.com \
--cc=quic_eberman@quicinc.com \
--cc=quic_kathirav@quicinc.com \
--cc=quic_mmanikan@quicinc.com \
--cc=quic_sjaganat@quicinc.com \
--cc=quic_srichara@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@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;
as well as URLs for NNTP newsgroup(s).