From: Tanmay Shah <tanmay.shah@amd.com>
To: Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: andersson@kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
michal.simek@amd.com, ben.levinsky@amd.com,
linux-remoteproc@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v11 4/4] remoteproc: zynqmp: parse TCM from device tree
Date: Wed, 28 Feb 2024 11:12:05 -0600 [thread overview]
Message-ID: <693569eb-55d2-4e6b-b03b-f48ad2a51be1@amd.com> (raw)
In-Reply-To: <Zd9oKWz073OJxKwp@p14s>
On 2/28/24 11:06 AM, Mathieu Poirier wrote:
> On Mon, Feb 19, 2024 at 09:44:37AM -0800, Tanmay Shah wrote:
> > ZynqMP TCM information was fixed in driver. Now ZynqMP TCM information
> > is available in device-tree. Parse TCM information in driver
> > as per new bindings.
> >
> > Signed-off-by: Tanmay Shah <tanmay.shah@amd.com>
> > ---
> >
> > Changes in v11:
> > - Remove redundant initialization of the variable
> > - return correct error code if memory allocation failed
>
> Where is that? I looked really hard but couldn't find it.
Hi Mathieu,
Thanks for reviews. Please find my comment below.
>
> >
> > drivers/remoteproc/xlnx_r5_remoteproc.c | 112 ++++++++++++++++++++++--
> > 1 file changed, 107 insertions(+), 5 deletions(-)
> >
> > diff --git a/drivers/remoteproc/xlnx_r5_remoteproc.c b/drivers/remoteproc/xlnx_r5_remoteproc.c
> > index 42b0384d34f2..d4a22caebaad 100644
> > --- a/drivers/remoteproc/xlnx_r5_remoteproc.c
> > +++ b/drivers/remoteproc/xlnx_r5_remoteproc.c
> > @@ -74,8 +74,8 @@ struct mbox_info {
> > };
> >
> > /*
> > - * Hardcoded TCM bank values. This will be removed once TCM bindings are
> > - * accepted for system-dt specifications and upstreamed in linux kernel
> > + * Hardcoded TCM bank values. This will stay in driver to maintain backward
> > + * compatibility with device-tree that does not have TCM information.
> > */
> > static const struct mem_bank_data zynqmp_tcm_banks_split[] = {
> > {0xffe00000UL, 0x0, 0x10000UL, PD_R5_0_ATCM, "atcm0"}, /* TCM 64KB each */
> > @@ -757,6 +757,103 @@ static struct zynqmp_r5_core *zynqmp_r5_add_rproc_core(struct device *cdev)
> > return ERR_PTR(ret);
> > }
> >
> > +static int zynqmp_r5_get_tcm_node_from_dt(struct zynqmp_r5_cluster *cluster)
> > +{
> > + int i, j, tcm_bank_count, ret, tcm_pd_idx, pd_count;
> > + struct of_phandle_args out_args;
> > + struct zynqmp_r5_core *r5_core;
> > + struct platform_device *cpdev;
> > + struct mem_bank_data *tcm;
> > + struct device_node *np;
> > + struct resource *res;
> > + u64 abs_addr, size;
> > + struct device *dev;
> > +
> > + for (i = 0; i < cluster->core_count; i++) {
> > + r5_core = cluster->r5_cores[i];
> > + dev = r5_core->dev;
> > + np = r5_core->np;
> > +
> > + pd_count = of_count_phandle_with_args(np, "power-domains",
> > + "#power-domain-cells");
> > +
> > + if (pd_count <= 0) {
> > + dev_err(dev, "invalid power-domains property, %d\n", pd_count);
> > + return -EINVAL;
> > + }
> > +
> > + /* First entry in power-domains list is for r5 core, rest for TCM. */
> > + tcm_bank_count = pd_count - 1;
> > +
> > + if (tcm_bank_count <= 0) {
> > + dev_err(dev, "invalid TCM count %d\n", tcm_bank_count);
> > + return -EINVAL;
> > + }
> > +
> > + r5_core->tcm_banks = devm_kcalloc(dev, tcm_bank_count,
> > + sizeof(struct mem_bank_data *),
> > + GFP_KERNEL);
> > + if (!r5_core->tcm_banks)
> > + return -ENOMEM;
Hi Mathiue,
Here: in v10 it was following:
+ if (!r5_core->tcm_banks)
+ ret = -ENOMEM;
Which is not correct. Somehow I missed to return the error code instead it was just storing the error in variable.
> > +
> > + r5_core->tcm_bank_count = tcm_bank_count;
> > + for (j = 0, tcm_pd_idx = 1; j < tcm_bank_count; j++, tcm_pd_idx++) {
> > + tcm = devm_kzalloc(dev, sizeof(struct mem_bank_data),
> > + GFP_KERNEL);
> > + if (!tcm)
> > + return -ENOMEM;
> > +
> > + r5_core->tcm_banks[j] = tcm;
> > +
> > + /* Get power-domains id of TCM. */
> > + ret = of_parse_phandle_with_args(np, "power-domains",
> > + "#power-domain-cells",
> > + tcm_pd_idx, &out_args);
> > + if (ret) {
> > + dev_err(r5_core->dev,
> > + "failed to get tcm %d pm domain, ret %d\n",
> > + tcm_pd_idx, ret);
> > + return ret;
> > + }
> > + tcm->pm_domain_id = out_args.args[0];
> > + of_node_put(out_args.np);
> > +
> > + /* Get TCM address without translation. */
> > + ret = of_property_read_reg(np, j, &abs_addr, &size);
> > + if (ret) {
> > + dev_err(dev, "failed to get reg property\n");
> > + return ret;
> > + }
> > +
> > + /*
> > + * Remote processor can address only 32 bits
> > + * so convert 64-bits into 32-bits. This will discard
> > + * any unwanted upper 32-bits.
> > + */
> > + tcm->da = (u32)abs_addr;
> > + tcm->size = (u32)size;
> > +
> > + cpdev = to_platform_device(dev);
> > + res = platform_get_resource(cpdev, IORESOURCE_MEM, j);
> > + if (!res) {
> > + dev_err(dev, "failed to get tcm resource\n");
> > + return -EINVAL;
> > + }
> > +
> > + tcm->addr = (u32)res->start;
> > + tcm->bank_name = (char *)res->name;
> > + res = devm_request_mem_region(dev, tcm->addr, tcm->size,
> > + tcm->bank_name);
> > + if (!res) {
> > + dev_err(dev, "failed to request tcm resource\n");
> > + return -EINVAL;
> > + }
> > + }
> > + }
> > +
> > + return 0;
> > +}
> > +
> > /**
> > * zynqmp_r5_get_tcm_node()
> > * Ideally this function should parse tcm node and store information
> > @@ -835,9 +932,14 @@ static int zynqmp_r5_core_init(struct zynqmp_r5_cluster *cluster,
> > struct zynqmp_r5_core *r5_core;
> > int ret, i;
> >
> > - ret = zynqmp_r5_get_tcm_node(cluster);
> > - if (ret < 0) {
> > - dev_err(dev, "can't get tcm node, err %d\n", ret);
> > + r5_core = cluster->r5_cores[0];
> > + if (of_find_property(r5_core->np, "reg", NULL))
> > + ret = zynqmp_r5_get_tcm_node_from_dt(cluster);
> > + else
> > + ret = zynqmp_r5_get_tcm_node(cluster);
> > +
> > + if (ret) {
> > + dev_err(dev, "can't get tcm, err %d\n", ret);
> > return ret;
> > }
> >
> > --
> > 2.25.1
> >
prev parent reply other threads:[~2024-02-28 17:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 17:44 [PATCH v11 0/4] add zynqmp TCM bindings Tanmay Shah
2024-02-19 17:44 ` [PATCH v11 1/4] remoteproc: zynqmp: fix lockstep mode memory region Tanmay Shah
2024-02-19 17:44 ` [PATCH v11 2/4] dt-bindings: remoteproc: add Tightly Coupled Memory (TCM) bindings Tanmay Shah
2024-02-28 19:20 ` Tanmay Shah
2024-02-29 9:59 ` Krzysztof Kozlowski
2024-02-29 23:45 ` Tanmay Shah
2024-02-19 17:44 ` [PATCH v11 3/4] dts: zynqmp: add properties for TCM in remoteproc Tanmay Shah
2024-02-19 17:44 ` [PATCH v11 4/4] remoteproc: zynqmp: parse TCM from device tree Tanmay Shah
2024-02-19 17:44 ` [PATCH v11 0/4] add zynqmp TCM bindings Tanmay Shah
2024-02-19 17:55 ` Tanmay Shah
2024-02-19 17:44 ` [PATCH v11 1/4] remoteproc: zynqmp: fix lockstep mode memory region Tanmay Shah
2024-02-28 17:08 ` Mathieu Poirier
2024-02-28 19:24 ` Tanmay Shah
2024-02-28 20:03 ` Mathieu Poirier
2024-02-19 17:44 ` [PATCH v11 2/4] dt-bindings: remoteproc: add Tightly Coupled Memory (TCM) bindings Tanmay Shah
2024-02-19 17:44 ` [PATCH v11 3/4] dts: zynqmp: add properties for TCM in remoteproc Tanmay Shah
2024-02-19 17:44 ` [PATCH v11 4/4] remoteproc: zynqmp: parse TCM from device tree Tanmay Shah
2024-02-28 17:06 ` Mathieu Poirier
2024-02-28 17:12 ` Tanmay Shah [this message]
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=693569eb-55d2-4e6b-b03b-f48ad2a51be1@amd.com \
--to=tanmay.shah@amd.com \
--cc=andersson@kernel.org \
--cc=ben.levinsky@amd.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=michal.simek@amd.com \
--cc=robh+dt@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