From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Ling Xu <quic_lxu5@quicinc.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,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Subject: Re: [PATCH v4 2/4] arm64: dts: qcom: sa8775p: add GDSP fastrpc-compute-cb nodes
Date: Fri, 27 Jun 2025 14:17:43 +0200 [thread overview]
Message-ID: <3f2279ce-7d4c-4ea7-8d3d-ba98208e212f@oss.qualcomm.com> (raw)
In-Reply-To: <20250627103319.2883613-3-quic_lxu5@quicinc.com>
On 6/27/25 12:33 PM, Ling Xu wrote:
> Add GDSP0 and GDSP1 fastrpc compute-cb nodes for sa8775p SoC.
>
> Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
> Signed-off-by: Ling Xu <quic_lxu5@quicinc.com>
> ---
Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Konrad
next prev parent reply other threads:[~2025-06-27 12:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-27 10:33 [PATCH v4 0/4] Add support for gdsp remoteproc on sa8775p Ling Xu
2025-06-27 10:33 ` [PATCH v4 1/4] dt-bindings: misc: qcom,fastrpc: Add GDSP label Ling Xu
2025-06-28 12:36 ` Krzysztof Kozlowski
2025-06-27 10:33 ` [PATCH v4 2/4] arm64: dts: qcom: sa8775p: add GDSP fastrpc-compute-cb nodes Ling Xu
2025-06-27 12:17 ` Konrad Dybcio [this message]
2025-06-27 10:33 ` [PATCH v4 3/4] misc: fastrpc: Refactor domain ID to enforce strict mapping Ling Xu
2025-06-27 12:23 ` Konrad Dybcio
2025-06-27 13:01 ` Srinivas Kandagatla
2025-06-27 10:33 ` [PATCH v4 4/4] misc: fastrpc: add support for gdsp remoteproc Ling Xu
2025-06-27 12:24 ` Konrad Dybcio
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=3f2279ce-7d4c-4ea7-8d3d-ba98208e212f@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.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=dmitry.baryshkov@oss.qualcomm.com \
--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