From: Ling Xu <quic_lxu5@quicinc.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
<srini@kernel.org>, <amahesh@qti.qualcomm.com>, <robh@kernel.org>,
<krzk+dt@kernel.org>, <conor+dt@kernel.org>,
<andersson@kernel.org>, <konradybcio@kernel.org>, <arnd@arndb.de>,
<gregkh@linuxfoundation.org>
Cc: <quic_kuiw@quicinc.com>, <ekansh.gupta@oss.qualcomm.com>,
<devicetree@vger.kernel.org>, <linux-arm-msm@vger.kernel.org>,
<dri-devel@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v6 4/4] misc: fastrpc: add support for gdsp remoteproc
Date: Fri, 11 Jul 2025 10:33:48 +0800 [thread overview]
Message-ID: <170ed625-ca3a-49ef-95bb-158d666be909@quicinc.com> (raw)
In-Reply-To: <075e59d0-569c-429f-ba14-c2e59e2f63a2@oss.qualcomm.com>
在 7/10/2025 3:19 AM, Konrad Dybcio 写道:
> On 7/9/25 7:52 AM, Ling Xu wrote:
>> 在 7/9/2025 1:47 PM, Ling Xu 写道:
>>> The fastrpc driver has support for 5 types of remoteprocs. There are
>>> some products which support GDSP remoteprocs. GDSP is General Purpose
>>> DSP where tasks can be offloaded. This patch extends the driver to
>>> support GDSP remoteprocs.
>>>
>>
>> sorry, please ignore this patch.
>> I haven't change commit message here.
>> "Extend the driver to support GDSP remoteprocs."
>
> How about this instead:
>
> Some platforms (like SMabcd) feature one or more GPDSPs (General
> Purpose DSPs). Similar to other kinds of Hexagon DSPs, they provide a
> FastRPC implementation, allowing code execution in both signed and
> unsigned protection domains.
>
> Extend the checks to allow domain names starting with "gdsp"
> (possibly followed by an index).
>
Thanks very much.
I will update in next patch.
> Konrad
>
>>
>>> Signed-off-by: Ling Xu <quic_lxu5@quicinc.com>
>>> ---
>>> drivers/misc/fastrpc.c | 6 +++++-
>>> 1 file changed, 5 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/drivers/misc/fastrpc.c b/drivers/misc/fastrpc.c
>>> index 85b6eb16b616..d05969de406e 100644
>>> --- a/drivers/misc/fastrpc.c
>>> +++ b/drivers/misc/fastrpc.c
>>> @@ -27,6 +27,7 @@
>>> #define MDSP_DOMAIN_ID (1)
>>> #define SDSP_DOMAIN_ID (2)
>>> #define CDSP_DOMAIN_ID (3)
>>> +#define GDSP_DOMAIN_ID (4)
>>> #define FASTRPC_MAX_SESSIONS 14
>>> #define FASTRPC_MAX_VMIDS 16
>>> #define FASTRPC_ALIGN 128
>>> @@ -2249,6 +2250,8 @@ static int fastrpc_get_domain_id(const char *domain)
>>> return MDSP_DOMAIN_ID;
>>> else if (!strncmp(domain, "sdsp", 4))
>>> return SDSP_DOMAIN_ID;
>>> + else if (!strncmp(domain, "gdsp", 4))
>>> + return GDSP_DOMAIN_ID;
>>>
>>> return -EINVAL;
>>> }
>>> @@ -2323,13 +2326,14 @@ static int fastrpc_rpmsg_probe(struct rpmsg_device *rpdev)
>>> case ADSP_DOMAIN_ID:
>>> case MDSP_DOMAIN_ID:
>>> case SDSP_DOMAIN_ID:
>>> - /* Unsigned PD offloading is only supported on CDSP */
>>> + /* Unsigned PD offloading is only supported on CDSP and GDSP */
>>> data->unsigned_support = false;
>>> err = fastrpc_device_register(rdev, data, secure_dsp, domain);
>>> if (err)
>>> goto err_free_data;
>>> break;
>>> case CDSP_DOMAIN_ID:
>>> + case GDSP_DOMAIN_ID:
>>> data->unsigned_support = true;
>>> /* Create both device nodes so that we can allow both Signed and Unsigned PD */
>>> err = fastrpc_device_register(rdev, data, true, domain);
>>
--
Thx and BRs,
Ling Xu
prev parent reply other threads:[~2025-07-11 2:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-09 5:47 [PATCH v6 0/4] Add support for gdsp remoteproc on sa8775p Ling Xu
2025-07-09 5:47 ` [PATCH v6 1/4] dt-bindings: misc: qcom,fastrpc: Add GDSP label Ling Xu
2025-07-09 5:47 ` [PATCH v6 2/4] arm64: dts: qcom: sa8775p: add GDSP fastrpc-compute-cb nodes Ling Xu
2025-07-09 5:47 ` [PATCH v6 3/4] misc: fastrpc: Cleanup the domain names Ling Xu
2025-07-09 19:25 ` Konrad Dybcio
2025-07-11 2:32 ` Ling Xu
2025-07-09 5:47 ` [PATCH v6 4/4] misc: fastrpc: add support for gdsp remoteproc Ling Xu
2025-07-09 5:52 ` Ling Xu
2025-07-09 19:19 ` Konrad Dybcio
2025-07-11 2:33 ` Ling Xu [this message]
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=170ed625-ca3a-49ef-95bb-158d666be909@quicinc.com \
--to=quic_lxu5@quicinc.com \
--cc=amahesh@qti.qualcomm.com \
--cc=andersson@kernel.org \
--cc=arnd@arndb.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=ekansh.gupta@oss.qualcomm.com \
--cc=gregkh@linuxfoundation.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_kuiw@quicinc.com \
--cc=robh@kernel.org \
--cc=srini@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).