From: Manikanta Mylavarapu <quic_mmanikan@quicinc.com>
To: Guru Das Srinagesh <quic_gurus@quicinc.com>
Cc: <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>,
<quic_srichara@quicinc.com>, <quic_sjaganat@quicinc.com>,
<quic_kathirav@quicinc.com>, <quic_anusha@quicinc.com>,
<quic_varada@quicinc.com>
Subject: Re: [PATCH v4 07/11] firmware: qcom_scm: ipq5332: add msa lock/unlock support
Date: Mon, 31 Jul 2023 10:44:41 +0530 [thread overview]
Message-ID: <4d278763-153c-bb9c-56d4-4b262ed2cc99@quicinc.com> (raw)
In-Reply-To: <20230729003037.GA25463@quicinc.com>
On 7/29/2023 6:00 AM, Guru Das Srinagesh wrote:
> On Jul 28 2023 12:04, Manikanta Mylavarapu wrote:
>> IPQ5332 user pd remoteproc firmwares need to be locked
>> with MSA(modem secure access) features. This patch add
>> support to lock/unlock MSA features.
>>
>> Signed-off-by: Manikanta Mylavarapu <quic_mmanikan@quicinc.com>
>> ---
>> Changes in v4:
>> - Rebased on linux-next
>>
>> drivers/firmware/qcom_scm.c | 78 ++++++++++++++++++++++++++
>> drivers/firmware/qcom_scm.h | 2 +
>> include/linux/firmware/qcom/qcom_scm.h | 2 +
>> 3 files changed, 82 insertions(+)
>>
>> diff --git a/drivers/firmware/qcom_scm.c b/drivers/firmware/qcom_scm.c
>> index 3bc8c63a997f..2275cf7bc887 100644
>> --- a/drivers/firmware/qcom_scm.c
>> +++ b/drivers/firmware/qcom_scm.c
>> @@ -676,6 +676,84 @@ bool qcom_scm_pas_supported(u32 peripheral)
>> }
>> EXPORT_SYMBOL(qcom_scm_pas_supported);
>>
>> +/**
>> + * qcom_scm_msa_lock() - Lock given peripheral firmware region as MSA
>> + *
>> + * @peripheral: peripheral id
>> + *
>> + * Return 0 on success.
>> + */
>> +int qcom_scm_msa_lock(u32 peripheral)
>> +{
>> + int ret;
>> + struct qcom_scm_desc desc = {
>> + .svc = QCOM_SCM_SVC_PIL,
>> + .cmd = QCOM_SCM_MSA_LOCK,
>> + .arginfo = QCOM_SCM_ARGS(1),
>> + .args[0] = peripheral,
>> + .owner = ARM_SMCCC_OWNER_SIP,
>> + };
>> + struct qcom_scm_res res;
>> +
>> + if (!__qcom_scm_is_call_available(__scm->dev, QCOM_SCM_SVC_PIL,
>> + QCOM_SCM_MSA_LOCK))
>> + return 0;
>> +
>> + ret = qcom_scm_clk_enable();
>> + if (ret)
>> + return ret;
>> +
>> + ret = qcom_scm_bw_enable();
>> + if (ret)
>> + return ret;
>> +
>> + ret = qcom_scm_call(__scm->dev, &desc, &res);
>> + qcom_scm_bw_disable();
>> + qcom_scm_clk_disable();
>> +
>> + return ret ? : res.result[0];
>> +}
>> +EXPORT_SYMBOL(qcom_scm_msa_lock);
>
> Could you please convert this to EXPORT_SYMBOL_GPL?
>
Ok, sure.
>> +
>> +/**
>> + * qcom_scm_msa_unlock() - Unlock given peripheral MSA firmware region
>> + *
>> + * @peripheral: peripheral id
>> + *
>> + * Return 0 on success.
>> + */
>> +int qcom_scm_msa_unlock(u32 peripheral)
>> +{
>> + int ret;
>> + struct qcom_scm_desc desc = {
>> + .svc = QCOM_SCM_SVC_PIL,
>> + .cmd = QCOM_SCM_MSA_UNLOCK,
>> + .arginfo = QCOM_SCM_ARGS(1),
>> + .args[0] = peripheral,
>> + .owner = ARM_SMCCC_OWNER_SIP,
>> + };
>> + struct qcom_scm_res res;
>> +
>> + if (!__qcom_scm_is_call_available(__scm->dev, QCOM_SCM_SVC_PIL,
>> + QCOM_SCM_MSA_UNLOCK))
>> + return 0;
>> +
>> + ret = qcom_scm_clk_enable();
>> + if (ret)
>> + return ret;
>> +
>> + ret = qcom_scm_bw_enable();
>> + if (ret)
>> + return ret;
>> +
>> + ret = qcom_scm_call(__scm->dev, &desc, &res);
>> + qcom_scm_bw_disable();
>> + qcom_scm_clk_disable();
>> +
>> + return ret ? : res.result[0];
>> +}
>> +EXPORT_SYMBOL(qcom_scm_msa_unlock);
>
> This one too?
>
Ok, sure.
> Reference: [1]
> The whole driver has now moved to using EXPORT_SYMBOL_GPL() now.
>
> [1] https://lore.kernel.org/lkml/19d9ac0bf79f957574ef9b3b73246ea0113cc0fd.1690503893.git.quic_gurus@quicinc.com/
>
> Thank you.
>
> Guru Das.
Thanks & Regards,
Manikanta.
next prev parent reply other threads:[~2023-07-31 5:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 6:34 [PATCH v4 00/11] Add multipd remoteproc support Manikanta Mylavarapu
2023-07-28 6:34 ` [PATCH v4 01/11] dt-bindings: remoteproc: qcom: Add support for multipd model Manikanta Mylavarapu
2023-07-28 6:34 ` [PATCH v4 02/11] clk: qcom: ipq5332: remove q6 bring up clocks Manikanta Mylavarapu
2023-07-28 6:34 ` [PATCH v4 03/11] clk: qcom: ipq9574: " Manikanta Mylavarapu
2023-07-28 6:34 ` [PATCH v4 04/11] dt-bindings: clock: qcom: gcc-ipq5332: remove q6 bring up clock macros Manikanta Mylavarapu
2023-07-28 8:24 ` Krzysztof Kozlowski
2023-07-28 6:34 ` [PATCH v4 05/11] dt-bindings: clock: qcom: gcc-ipq9574: " Manikanta Mylavarapu
2023-07-28 8:24 ` Krzysztof Kozlowski
2023-07-28 6:34 ` [PATCH v4 06/11] firmware: qcom_scm: ipq5332: add support to pass metadata size Manikanta Mylavarapu
2023-07-28 6:34 ` [PATCH v4 07/11] firmware: qcom_scm: ipq5332: add msa lock/unlock support Manikanta Mylavarapu
2023-07-29 0:30 ` Guru Das Srinagesh
2023-07-31 5:14 ` Manikanta Mylavarapu [this message]
2023-07-28 6:34 ` [PATCH v4 08/11] remoteproc: qcom: q6v5: Add multipd interrupts support Manikanta Mylavarapu
2023-07-28 6:34 ` [PATCH v4 09/11] remoteproc: qcom: Add Hexagon based multipd rproc driver Manikanta Mylavarapu
2023-07-28 8:27 ` Krzysztof Kozlowski
2023-07-31 5:04 ` Manikanta Mylavarapu
2023-07-30 6:05 ` kernel test robot
2023-07-28 6:34 ` [PATCH v4 10/11] arm64: dts: qcom: ipq5332: Add nodes to bringup multipd Manikanta Mylavarapu
2023-07-28 6:34 ` [PATCH v4 11/11] arm64: dts: qcom: ipq9574: Add nodes to bring up multipd 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=4d278763-153c-bb9c-56d4-4b262ed2cc99@quicinc.com \
--to=quic_mmanikan@quicinc.com \
--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_gurus@quicinc.com \
--cc=quic_kathirav@quicinc.com \
--cc=quic_sjaganat@quicinc.com \
--cc=quic_srichara@quicinc.com \
--cc=quic_varada@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
all inboxes | Powered by JetHome®