From: Krzysztof Kozlowski <krzk@kernel.org>
To: Ling Xu <quic_lxu5@quicinc.com>
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 v5 1/4] dt-bindings: misc: qcom,fastrpc: Add GDSP label
Date: Thu, 3 Jul 2025 09:20:47 +0200 [thread overview]
Message-ID: <20250703-qualified-roaring-gaur-c7c2b7@krzk-bin> (raw)
In-Reply-To: <20250702025341.1473332-2-quic_lxu5@quicinc.com>
On Wed, Jul 02, 2025 at 08:23:38AM +0530, Ling Xu wrote:
> There are some products which support GDSP remoteprocs. GDSP is General
> Purpose DSP where tasks can be offloaded. There are 2 GDSPs named gdsp0
> and gdsp1. Add "gdsp0" and "gdsp1" as the new supported labels for GDSP
> fastrpc domains.
>
> Signed-off-by: Ling Xu <quic_lxu5@quicinc.com>
> ---
> Documentation/devicetree/bindings/misc/qcom,fastrpc.yaml | 2 ++
> 1 file changed, 2 insertions(+)
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-07-03 7:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-02 2:53 [PATCH v5 0/4] Add support for gdsp remoteproc on sa8775p Ling Xu
2025-07-02 2:53 ` [PATCH v5 1/4] dt-bindings: misc: qcom,fastrpc: Add GDSP label Ling Xu
2025-07-03 7:20 ` Krzysztof Kozlowski [this message]
2025-07-02 2:53 ` [PATCH v5 2/4] arm64: dts: qcom: sa8775p: add GDSP fastrpc-compute-cb nodes Ling Xu
2025-07-02 2:53 ` [PATCH v5 3/4] misc: fastrpc: Refactor domain ID to enforce strict mapping Ling Xu
2025-07-04 16:54 ` Dmitry Baryshkov
2025-07-08 13:05 ` Ling Xu
2025-07-02 2:53 ` [PATCH v5 4/4] misc: fastrpc: add support for gdsp remoteproc Ling Xu
2025-07-04 16:55 ` Dmitry Baryshkov
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=20250703-qualified-roaring-gaur-c7c2b7@krzk-bin \
--to=krzk@kernel.org \
--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=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_kuiw@quicinc.com \
--cc=quic_lxu5@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