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
Subject: Re: [PATCH v3 3/3] misc: fastrpc: add support for gdsp remoteproc
Date: Mon, 23 Jun 2025 12:28:50 +0200 [thread overview]
Message-ID: <09bf24d7-2998-4a15-9b9e-ba476fc08a90@oss.qualcomm.com> (raw)
In-Reply-To: <20250622133820.18369-4-quic_lxu5@quicinc.com>
On 6/22/25 3:38 PM, Ling Xu wrote:
> The fastrpc driver has support for 5 types of remoteprocs. There are
> some products which support GDSP remoteprocs. Add changes to support
> GDSP remoteprocs.
Commit messages saying "add changes to support xyz" often indicate
the problem or the non-obvious solution is not properly described
(which is the case here as well)
[...]
> +static int fastrpc_get_domain_id(const char *domain)
> +{
> + if (strncmp(domain, "adsp", 4) == 0)
if (!strncmp(...)) is the common syntax, although it's obviously
not functionally different
> + return ADSP_DOMAIN_ID;
> + else if (strncmp(domain, "cdsp", 4) == 0)
> + return CDSP_DOMAIN_ID;
> + else if (strncmp(domain, "mdsp", 4) == 0)
> + return MDSP_DOMAIN_ID;
> + else if (strncmp(domain, "sdsp", 4) == 0)
> + return SDSP_DOMAIN_ID;
> + else if (strncmp(domain, "gdsp", 4) == 0)
> + return GDSP_DOMAIN_ID;
FWIW, other places call it G*P*DSP
[...]
> --- a/include/uapi/misc/fastrpc.h
> +++ b/include/uapi/misc/fastrpc.h
> @@ -18,6 +18,14 @@
> #define FASTRPC_IOCTL_MEM_UNMAP _IOWR('R', 11, struct fastrpc_mem_unmap)
> #define FASTRPC_IOCTL_GET_DSP_INFO _IOWR('R', 13, struct fastrpc_ioctl_capability)
>
> +#define ADSP_DOMAIN_ID (0)
> +#define MDSP_DOMAIN_ID (1)
> +#define SDSP_DOMAIN_ID (2)
> +#define CDSP_DOMAIN_ID (3)
> +#define GDSP_DOMAIN_ID (4)
> +
> +#define FASTRPC_DOMAIN_MAX 4
What are these used for now?
> /**
> * enum fastrpc_map_flags - control flags for mapping memory on DSP user process
> * @FASTRPC_MAP_STATIC: Map memory pages with RW- permission and CACHE WRITEBACK.
> @@ -134,10 +142,9 @@ struct fastrpc_mem_unmap {
> };
>
> struct fastrpc_ioctl_capability {
> - __u32 domain;
> __u32 attribute_id;
> __u32 capability; /* dsp capability */
> - __u32 reserved[4];
> + __u32 reserved[5];
This is an ABI break, as the data within structs is well, structured
Konrad
next prev parent reply other threads:[~2025-06-23 10:28 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
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 [this message]
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=09bf24d7-2998-4a15-9b9e-ba476fc08a90@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=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
all inboxes | Powered by JetHome®