From: Srinivas Kandagatla <srini@kernel.org>
To: "Rob Herring (Arm)" <robh@kernel.org>,
Srinivas Kandagatla <srini@kernel.org>,
Amol Maheshwari <amahesh@qti.qualcomm.com>,
Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] misc: fastrpc: Use of_reserved_mem_region_to_resource() for "memory-region"
Date: Sat, 12 Jul 2025 19:27:42 +0100 [thread overview]
Message-ID: <acd5b3e3-5370-49a4-aad9-b1001aa0eb5a@kernel.org> (raw)
In-Reply-To: <20250703183455.2074215-1-robh@kernel.org>
On 7/3/25 7:34 PM, Rob Herring (Arm) wrote:
> Use the newly added of_reserved_mem_region_to_resource() function to
> handle "memory-region" properties.
>
> The error handling is a bit different. "memory-region" is optional, so
> failed lookup is not an error. But then an error in
> of_reserved_mem_lookup() is treated as an error. However, that
> distinction is not really important. Either the region is available
> and usable or it is not. So now, it is just
> of_reserved_mem_region_to_resource() which is checked for an error.
>
> Signed-off-by: Rob Herring (Arm) <robh@kernel.org>
> ---
Reviewed-by: Srinivas Kandagatla <srini@kernel.org>
Greg, there are no more patches for fastrpc for this cycle, can you
please pick this up via char-misc tree?
thanks,
Srini
> drivers/misc/fastrpc.c | 19 +++++++------------
> 1 file changed, 7 insertions(+), 12 deletions(-)
>
> diff --git a/drivers/misc/fastrpc.c b/drivers/misc/fastrpc.c
> index 378923594f02..53e88a1bc430 100644
> --- a/drivers/misc/fastrpc.c
> +++ b/drivers/misc/fastrpc.c
> @@ -2262,8 +2262,6 @@ static int fastrpc_rpmsg_probe(struct rpmsg_device *rpdev)
> int i, err, domain_id = -1, vmcount;
> const char *domain;
> bool secure_dsp;
> - struct device_node *rmem_node;
> - struct reserved_mem *rmem;
> unsigned int vmids[FASTRPC_MAX_VMIDS];
>
> err = of_property_read_string(rdev->of_node, "label", &domain);
> @@ -2306,20 +2304,17 @@ static int fastrpc_rpmsg_probe(struct rpmsg_device *rpdev)
> }
> }
>
> - rmem_node = of_parse_phandle(rdev->of_node, "memory-region", 0);
> - if (domain_id == SDSP_DOMAIN_ID && rmem_node) {
> + if (domain_id == SDSP_DOMAIN_ID) {
> + struct resource res;
> u64 src_perms;
>
> - rmem = of_reserved_mem_lookup(rmem_node);
> - if (!rmem) {
> - err = -EINVAL;
> - goto err_free_data;
> - }
> + err = of_reserved_mem_region_to_resource(rdev->of_node, 0, &res);
> + if (!err) {
> + src_perms = BIT(QCOM_SCM_VMID_HLOS);
>
> - src_perms = BIT(QCOM_SCM_VMID_HLOS);
> -
> - qcom_scm_assign_mem(rmem->base, rmem->size, &src_perms,
> + qcom_scm_assign_mem(res.start, resource_size(&res), &src_perms,
> data->vmperms, data->vmcount);
> + }
>
> }
>
next prev parent reply other threads:[~2025-07-12 18:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-03 18:34 Rob Herring (Arm)
2025-07-03 19:45 ` Dmitry Baryshkov
2025-07-12 18:27 ` Srinivas Kandagatla [this message]
2025-07-16 12:16 ` Greg Kroah-Hartman
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=acd5b3e3-5370-49a4-aad9-b1001aa0eb5a@kernel.org \
--to=srini@kernel.org \
--cc=amahesh@qti.qualcomm.com \
--cc=arnd@arndb.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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®