[PATCH v2 0/4] remoteproc: virtio: Fixes and cleanups in the vdev<->pdev relationship

[Francesco Valla <francesco@valla.it>]

V2 is simply a rebase on rproc-next, with conflicts solved.

Hello,

while proceeding on [1] I noticed a possible simplification on the
rproc-virtio registration and tracking path, which led to the discovery
of a couple of bugs. This series is the result of the work that followed
and thus contains both (proposed) fixes for the bugs and the
aforementioned simplification, which consists in less poking the backing
pdev from the vdev side.

Patches 1 and 2 can be collapsed into one, but I preferred to leave them
separate to show the reasoning behind (and to allow cherry-picking, if
that's the case).

Thank you!

Regards,
Francesco

Signed-off-by: Francesco Valla <francesco@valla.it>
---
Changes in v2:
- Rebased on rproc-next, solving conflicts.
- Link to v1: https://patch.msgid.link/20261108-remoteproc_pdev_decouple-v1-0-3dc2fad4951d@valla.it

---
Francesco Valla (4):
      remoteproc: virtio: Decouple vdev from the parent pdev
      remoteproc: virtio: Rework memory release
      remoteproc: virtio: Drop rvdevs list and associated functions
      remoteproc: virtio: Stop de-referencing pdev from its children

 drivers/remoteproc/remoteproc_core.c     | 34 +++++++++++-----------
 drivers/remoteproc/remoteproc_internal.h |  4 +--
 drivers/remoteproc/remoteproc_virtio.c   | 49 ++++++++++++++------------------
 include/linux/remoteproc.h               | 10 ++-----
 4 files changed, 43 insertions(+), 54 deletions(-)
---
base-commit: 3035b6708f61259c93a368238e206dcec313e584
change-id: 20261107-remoteproc_pdev_decouple-9933eb3a5998

Best regards,
--  
Francesco Valla <francesco@valla.it>