From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Ling Xu <quic_lxu5@quicinc.com>,
andersson@kernel.org, konradybcio@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
srinivas.kandagatla@linaro.org, amahesh@qti.qualcomm.com,
arnd@arndb.de, gregkh@linuxfoundation.org
Cc: quic_kuiw@quicinc.com, quic_ekangupt@quicinc.com,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Subject: Re: [PATCH v2 2/3] misc: fastrpc: add support for gpdsp remoteproc
Date: Thu, 20 Mar 2025 11:30:59 +0100 [thread overview]
Message-ID: <f8d12312-dfb7-481c-a025-dd4c6d3aa268@oss.qualcomm.com> (raw)
In-Reply-To: <20250320091446.3647918-3-quic_lxu5@quicinc.com>
On 3/20/25 10:14 AM, Ling Xu wrote:
> The fastrpc driver has support for 5 types of remoteprocs. There are
> some products which support GPDSP remoteprocs. Add changes to support
> GPDSP remoteprocs.
>
> Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
> Signed-off-by: Ling Xu <quic_lxu5@quicinc.com>
> ---
> drivers/misc/fastrpc.c | 10 ++++++++--
> 1 file changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/misc/fastrpc.c b/drivers/misc/fastrpc.c
> index 7b7a22c91fe4..80aa554b3042 100644
> --- a/drivers/misc/fastrpc.c
> +++ b/drivers/misc/fastrpc.c
> @@ -28,7 +28,9 @@
> #define SDSP_DOMAIN_ID (2)
> #define CDSP_DOMAIN_ID (3)
> #define CDSP1_DOMAIN_ID (4)
> -#define FASTRPC_DEV_MAX 5 /* adsp, mdsp, slpi, cdsp, cdsp1 */
> +#define GDSP0_DOMAIN_ID (5)
> +#define GDSP1_DOMAIN_ID (6)
> +#define FASTRPC_DEV_MAX 7 /* adsp, mdsp, slpi, cdsp, cdsp1, gdsp0, gdsp1 */
> #define FASTRPC_MAX_SESSIONS 14
> #define FASTRPC_MAX_VMIDS 16
> #define FASTRPC_ALIGN 128
> @@ -107,7 +109,9 @@
> #define miscdev_to_fdevice(d) container_of(d, struct fastrpc_device, miscdev)
>
> static const char *domains[FASTRPC_DEV_MAX] = { "adsp", "mdsp",
> - "sdsp", "cdsp", "cdsp1" };
> + "sdsp", "cdsp",
> + "cdsp1", "gdsp0",
> + "gdsp1" };
> struct fastrpc_phy_page {
> u64 addr; /* physical address */
> u64 size; /* size of contiguous region */
> @@ -2338,6 +2342,8 @@ static int fastrpc_rpmsg_probe(struct rpmsg_device *rpdev)
> break;
> case CDSP_DOMAIN_ID:
> case CDSP1_DOMAIN_ID:
> + case GDSP0_DOMAIN_ID:
> + case GDSP1_DOMAIN_ID:
> data->unsigned_support = true;
There's a comment above this hunk that is no longer valid:
'/* Unsigned PD offloading is only supported on CDSP and CDSP1 */'
I would say it can be removed altogether
I would also support renaming "unsigned_support" which is very generic to
something like allow_unsigned_pds
Konrad
next prev parent reply other threads:[~2025-03-20 10:31 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-20 9:14 [PATCH v2 0/3] Add support for gpdsp remoteproc on sa8775p Ling Xu
2025-03-20 9:14 ` [PATCH v2 1/3] arm64: dts: qcom: sa8775p: add GPDSP fastrpc-compute-cb nodes Ling Xu
2025-03-20 10:54 ` Dmitry Baryshkov
2025-03-20 9:14 ` [PATCH v2 2/3] misc: fastrpc: add support for gpdsp remoteproc Ling Xu
2025-03-20 9:26 ` Ekansh Gupta
2025-03-20 10:30 ` Konrad Dybcio [this message]
2025-03-20 17:11 ` Srinivas Kandagatla
2025-03-20 18:43 ` Dmitry Baryshkov
2025-03-21 12:23 ` Srinivas Kandagatla
2025-03-21 14:07 ` Dmitry Baryshkov
2025-04-02 8:38 ` Ekansh Gupta
2025-04-02 8:42 ` Dmitry Baryshkov
2025-04-03 4:44 ` Ekansh Gupta
2025-04-03 13:49 ` Srinivas Kandagatla
2025-03-21 14:07 ` Dmitry Baryshkov
2025-03-24 13:29 ` Srinivas Kandagatla
2025-03-24 16:24 ` Dmitry Baryshkov
2025-04-07 9:13 ` Ling Xu
2025-04-08 8:14 ` Srinivas Kandagatla
2025-06-16 11:28 ` Ling Xu
2025-06-16 11:32 ` Dmitry Baryshkov
2025-06-18 5:15 ` Ling Xu
2025-06-18 21:08 ` Dmitry Baryshkov
2025-03-20 9:14 ` [PATCH v2 3/3] dt-bindings: misc: qcom,fastrpc: Add GPDSPs label Ling Xu
2025-03-21 9:42 ` Krzysztof Kozlowski
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=f8d12312-dfb7-481c-a025-dd4c6d3aa268@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=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_ekangupt@quicinc.com \
--cc=quic_kuiw@quicinc.com \
--cc=quic_lxu5@quicinc.com \
--cc=robh@kernel.org \
--cc=srinivas.kandagatla@linaro.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®