From: Krzysztof Kozlowski <krzk@kernel.org>
To: Valentina Fernandez <valentina.fernandezalanis@microchip.com>,
paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, peterlin@andestech.com,
dminus@andestech.com, conor.dooley@microchip.com,
conor+dt@kernel.org, ycliang@andestech.com,
jassisinghbrar@gmail.com, robh@kernel.org, krzk+dt@kernel.org,
andersson@kernel.org, mathieu.poirier@linaro.org
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-remoteproc@vger.kernel.org
Subject: Re: [PATCH v1 5/5] remoteproc: add support for Microchip IPC remoteproc platform driver
Date: Mon, 16 Sep 2024 22:18:16 +0200 [thread overview]
Message-ID: <6f1fa401-e9ca-466f-990a-52bc37899bf4@kernel.org> (raw)
In-Reply-To: <20240912170025.455167-6-valentina.fernandezalanis@microchip.com>
On 12/09/2024 19:00, Valentina Fernandez wrote:
> The Microchip family of RISC-V SoCs typically has one or more clusters.
> These clusters can be configured to run in Asymmetric Multi-Processing
> (AMP) mode.
>
> Add a remoteproc platform driver to be able to load and boot firmware
> to the remote processor(s).
...
> +
> +static int mchp_ipc_rproc_prepare(struct rproc *rproc)
> +{
> + struct mchp_ipc_rproc *priv = rproc->priv;
> + struct device_node *np = priv->dev->of_node;
> + struct rproc_mem_entry *mem;
> + struct reserved_mem *rmem;
> + struct of_phandle_iterator it;
> + u64 device_address;
> +
> + reinit_completion(&priv->start_done);
> +
> + of_phandle_iterator_init(&it, np, "memory-region", NULL, 0);
> + while (of_phandle_iterator_next(&it) == 0) {
> + /*
> + * Ignore the first memory region which will be used vdev
> + * buffer. No need to do extra handlings, rproc_add_virtio_dev
> + * will handle it.
> + */
> + if (!strcmp(it.node->name, "vdev0buffer"))
What? If you ignore the first, then why are you checking names? This
does not make sense. Especially that your binding did not say anything
about these phandles being somehow special.
> + continue;
> +
> + if (!strcmp(it.node->name, "rsc-table"))
Nope.
> + continue;
> +
> + rmem = of_reserved_mem_lookup(it.node);
> + if (!rmem) {
> + of_node_put(it.node);
> + dev_err(priv->dev, "unable to acquire memory-region\n");
> + return -EINVAL;
> + }
> +
> + device_address = rmem->base;
> +
> + mem = rproc_mem_entry_init(priv->dev, NULL, (dma_addr_t)rmem->base,
> + rmem->size, device_address, mchp_ipc_rproc_mem_alloc,
> + mchp_ipc_rproc_mem_release, it.node->name);
> +
> + if (!mem) {
> + of_node_put(it.node);
> + return -ENOMEM;
> + }
> +
> + rproc_add_carveout(rproc, mem);
> + }
> +
> + return 0;
> +}
> +
> +static int mchp_ipc_rproc_parse_fw(struct rproc *rproc, const struct firmware *fw)
> +{
> + int ret;
> +
> + ret = rproc_elf_load_rsc_table(rproc, fw);
> + if (ret)
> + dev_info(&rproc->dev, "No resource table in elf\n");
> +
> + return 0;
> +}
> +
> +static void mchp_ipc_rproc_kick(struct rproc *rproc, int vqid)
> +{
> + struct mchp_ipc_rproc *priv = (struct mchp_ipc_rproc *)rproc->priv;
> + struct mchp_ipc_msg msg;
> + int ret;
> +
> + msg.buf = (void *)&vqid;
> + msg.size = sizeof(vqid);
> +
> + ret = mbox_send_message(priv->mbox_channel, (void *)&msg);
> + if (ret < 0)
> + dev_err(priv->dev,
> + "failed to send mbox message, status = %d\n", ret);
> +}
> +
> +static int mchp_ipc_rproc_attach(struct rproc *rproc)
> +{
> + return 0;
> +}
> +
> +static struct resource_table
> +*mchp_ipc_rproc_get_loaded_rsc_table(struct rproc *rproc, size_t *table_sz)
> +{
> + struct mchp_ipc_rproc *priv = rproc->priv;
> +
> + if (!priv->rsc_table)
> + return NULL;
> +
> + *table_sz = SZ_1K;
> + return (struct resource_table *)priv->rsc_table;
> +}
> +
> +static const struct rproc_ops mchp_ipc_rproc_ops = {
> + .prepare = mchp_ipc_rproc_prepare,
> + .start = mchp_ipc_rproc_start,
> + .get_loaded_rsc_table = mchp_ipc_rproc_get_loaded_rsc_table,
> + .attach = mchp_ipc_rproc_attach,
> + .stop = mchp_ipc_rproc_stop,
> + .kick = mchp_ipc_rproc_kick,
> + .load = rproc_elf_load_segments,
> + .parse_fw = mchp_ipc_rproc_parse_fw,
> + .find_loaded_rsc_table = rproc_elf_find_loaded_rsc_table,
> + .sanity_check = rproc_elf_sanity_check,
> + .get_boot_addr = rproc_elf_get_boot_addr,
> +};
> +
> +static int mchp_ipc_rproc_addr_init(struct mchp_ipc_rproc *priv,
> + struct platform_device *pdev)
> +{
> + struct device *dev = &pdev->dev;
> + struct device_node *np = dev->of_node;
> + int i, err, rmem_np;
> +
> + rmem_np = of_count_phandle_with_args(np, "memory-region", NULL);
> + if (rmem_np <= 0)
> + return 0;
> +
> + for (i = 0; i < rmem_np; i++) {
> + struct device_node *node;
> + struct resource res;
> +
> + node = of_parse_phandle(np, "memory-region", i);
> + if (!node)
> + continue;
> +
> + if (!strncmp(node->name, "vdev", strlen("vdev"))) {
Uh? Why do you look for node names? What if I call the name differently?
Why would that matter?
> + of_node_put(node);
> + continue;
> + }
> +
> + if (!strcmp(node->name, "rsc-table")) {
No, really. Why are you checking for these?
NAK
> + err = of_address_to_resource(node, 0, &res);
> + if (err) {
> + of_node_put(node);
> + return dev_err_probe(dev, err,
> + "unable to resolve memory region\n");
> + }
> + priv->rsc_table = devm_ioremap(&pdev->dev,
> + res.start, resource_size(&res));
> + of_node_put(node);
> + }
> + }
> +
> + return 0;
> +}
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-09-16 20:18 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-12 17:00 [PATCH v1 0/5] Add Microchip IPC mailbox and remoteproc support Valentina Fernandez
2024-09-12 17:00 ` [PATCH v1 1/5] riscv: asm: vendorid_list: Add Microchip Technology to the vendor list Valentina Fernandez
2024-09-12 17:16 ` Conor Dooley
2024-09-12 17:00 ` [PATCH v1 2/5] dt-bindings: mailbox: add binding for Microchip IPC mailbox driver Valentina Fernandez
2024-09-12 17:15 ` Conor Dooley
2024-09-12 21:23 ` Samuel Holland
2024-09-16 16:31 ` Conor Dooley
2024-09-18 15:35 ` Rob Herring
2024-09-19 7:40 ` Conor Dooley
2024-09-12 17:00 ` [PATCH v1 3/5] mailbox: add Microchip IPC support Valentina Fernandez
2024-09-12 21:30 ` Samuel Holland
2024-09-16 9:25 ` Valentina.FernandezAlanis
2024-09-16 20:21 ` Krzysztof Kozlowski
2024-09-12 17:00 ` [PATCH v1 4/5] dt-bindings: remoteproc: add binding for Microchip IPC remoteproc Valentina Fernandez
2024-09-16 20:14 ` Krzysztof Kozlowski
2024-10-15 12:09 ` Valentina.FernandezAlanis
2024-10-15 13:35 ` Krzysztof Kozlowski
2024-10-15 20:22 ` Conor Dooley
2024-09-12 17:00 ` [PATCH v1 5/5] remoteproc: add support for Microchip IPC remoteproc platform driver Valentina Fernandez
2024-09-16 20:18 ` Krzysztof Kozlowski [this message]
2024-09-18 15:51 ` Valentina.FernandezAlanis
2024-09-22 20:21 ` Krzysztof Kozlowski
2024-09-13 14:44 ` [PATCH v1 0/5] Add Microchip IPC mailbox and remoteproc support Mathieu Poirier
2024-09-16 15:04 ` Mathieu Poirier
2024-09-16 22:28 ` Bo Gan
2024-09-17 10:45 ` Valentina.FernandezAlanis
2024-09-17 12:42 ` Conor Dooley
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=6f1fa401-e9ca-466f-990a-52bc37899bf4@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=dminus@andestech.com \
--cc=jassisinghbrar@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mathieu.poirier@linaro.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=peterlin@andestech.com \
--cc=robh@kernel.org \
--cc=valentina.fernandezalanis@microchip.com \
--cc=ycliang@andestech.com \
/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;
as well as URLs for NNTP newsgroup(s).