From: Ling Xu <quic_lxu5@quicinc.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: <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>, <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 v3 1/3] dt-bindings: misc: qcom,fastrpc: Add GDSP label
Date: Fri, 27 Jun 2025 18:15:56 +0800 [thread overview]
Message-ID: <9fda4c17-869f-4d2f-930c-01eb714d68a8@quicinc.com> (raw)
In-Reply-To: <j2nni4oyoochjgw5w7vodxnn562vff2krkesta6zzgqs5ihvcx@5up7ga7k4gdl>
在 6/25/2025 3:44 PM, Krzysztof Kozlowski 写道:
> On Sun, Jun 22, 2025 at 07:08:18PM +0530, Ling Xu wrote:
>> Add "gdsp" as the new supported label for GDSP fastrpc domain.
>
> Neither this commit, nor second nor third explain what is GDSP...
>
> Best regards,
> Krzysztof
> Okay, I will edit commit message in next patch.
GDSP is General Purpose DSP where tasks can be offloaded, and it includes GDSP0 and GDSP1.
Analogous to CDSP (Compute DSP) which includes CDSP0 and CDSP1.
--
Thx and BRs,
Ling Xu
next prev parent reply other threads:[~2025-06-27 10:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-22 13:38 [PATCH v3 0/3] Add support for gdsp remoteproc on sa8775p Ling Xu
2025-06-22 13:38 ` [PATCH v3 1/3] dt-bindings: misc: qcom,fastrpc: Add GDSP label Ling Xu
2025-06-25 7:44 ` Krzysztof Kozlowski
2025-06-27 10:15 ` Ling Xu [this message]
2025-06-22 13:38 ` [PATCH v3 2/3] arm64: dts: qcom: sa8775p: add GDSP fastrpc-compute-cb nodes Ling Xu
2025-06-22 13:38 ` [PATCH v3 3/3] misc: fastrpc: add support for gdsp remoteproc Ling Xu
2025-06-23 10:28 ` Konrad Dybcio
2025-06-24 5:58 ` Ling Xu
2025-06-28 5:51 ` Dmitry Baryshkov
2025-06-24 2:37 ` Dmitry Baryshkov
2025-06-24 5:59 ` Ling Xu
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=9fda4c17-869f-4d2f-930c-01eb714d68a8@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=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@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).