From: Mathieu Poirier <mathieu.poirier@linaro.org>
To: Simon Maurer <mail@maurer.systems>
Cc: linux-remoteproc@vger.kernel.org
Subject: Re: RemoteProc over PCIe
Date: Mon, 27 Jan 2025 09:27:33 -0700 [thread overview]
Message-ID: <CANLsYkyERtRf4F8DGK9-1=cztkA6Gz7-gUb5dGdaUO5ufBWg9Q@mail.gmail.com> (raw)
In-Reply-To: <1710b217-548c-4eab-a1f1-dd31cd7625e1@maurer.systems>
On Wed, 22 Jan 2025 at 11:53, Simon Maurer <mail@maurer.systems> wrote:
>
> The last patch would be the first step for RemoteProc over PCIe. I use a
> Xilinx Zynq 7000 PCIe card as my remote CPU and a x86 PC as the the
> host. Both vrings and RPMSG-buffer are in the remote (PCIe-Card) SRAM.
> So the RPMSG-buffer isn't actually DMA memory, but the SRAM on the Zynq
> is mapped in a PCIe-bar. I'm working now on a patch, that transfers the
> ownership of the RPMSG-buffer form virtio_rpmsg_bus to
> remoteproc_virtio. So instead of virtio_rpmsg_bus calling
> dma_alloc_coherent for buffer allocation, it would call
> virtio_get_shm_region to get TX/RX buffers and on rpmsg_remove it would
> call virtio_release_shm_regions (new in virtio_config_ops), analogue to
> find_vqs/del_vqs.
> Thoughts?
>
Hi Simon,
I don't know anything about the Zynq 7000 but I assume it needs to be
explicitly told to act as an endpoint rather than a PCI bus master.
I can't say much about the above without looking at real code so I
will wait for your patches before spending more time on the design you
are putting forward.
As for your patch adding a new operation to the rproc_ops structure,
please include in the submission for the work you presented above. It
can't be merged without an actual customer.
Thanks,
Mathieu
next prev parent reply other threads:[~2025-01-27 16:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-22 15:59 [PATCH] remoteproc: add optional hook for resource checking Simon Maurer
2025-01-22 18:53 ` RemoteProc over PCIe Simon Maurer
2025-01-27 16:27 ` Mathieu Poirier [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-09 13:42 remoteproc " Simon Maurer
2023-05-09 17:08 ` Arnaud POULIQUEN
2023-05-10 13:06 ` Simon Maurer
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='CANLsYkyERtRf4F8DGK9-1=cztkA6Gz7-gUb5dGdaUO5ufBWg9Q@mail.gmail.com' \
--to=mathieu.poirier@linaro.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mail@maurer.systems \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).