From: "Shah, Tanmay" <tanmays@amd.com>
To: Francesco Valla <francesco@valla.it>, Tanmay Shah <tanmay.shah@amd.com>
Cc: <andersson@kernel.org>, <mathieu.poirier@linaro.org>,
<ohad@wizery.com>, <linux-remoteproc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] remoteproc: remoteproc_virtio: reset vdev before removing it
Date: Wed, 30 Sep 2026 16:59:27 -0500 [thread overview]
Message-ID: <44648601-e04e-4d6e-a192-3df6dc1b3b24@amd.com> (raw)
In-Reply-To: <arjZvftSMlG3OMHP@bywater>
On 9/27/2026 3:55 AM, Francesco Valla wrote:
> Hi Tanmay,
>
> On Thu, Sep 24, 2026 at 01:59:02PM -0700, Tanmay Shah wrote:
>> The virtio device is removed when the remoteproc device is removed. The
>> driver should issue reset on the virtio device so the remote can do
>> corresponding cleanup.
>>
>
> Shouldn't be the driver, and not the transport, the one that calls
> virtio_reset_device()?
>
Hello Francesco,
Thanks for your reviews. I will look into it.
Tanmay
>> Fixes: 7a186941626d ("remoteproc: remove the single rpmsg vdev limitation")
>> Signed-off-by: Tanmay Shah <tanmay.shah@amd.com>
>> ---
>> drivers/remoteproc/remoteproc_virtio.c | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/drivers/remoteproc/remoteproc_virtio.c b/drivers/remoteproc/remoteproc_virtio.c
>> index d5e9ff045a28..1cb0ee0ea656 100644
>> --- a/drivers/remoteproc/remoteproc_virtio.c
>> +++ b/drivers/remoteproc/remoteproc_virtio.c
>> @@ -469,6 +469,8 @@ static int rproc_remove_virtio_dev(struct device *dev, void *data)
>> {
>> struct virtio_device *vdev = dev_to_virtio(dev);
>>
>> + virtio_reset_device(vdev);
>> +
>> unregister_virtio_device(vdev);
>> return 0;
>> }
>>
>> base-commit: 5f639b3018c0026a5341949724b4b921cf3a3d5d
>> --
>> 2.43.0
>>
next prev parent reply other threads:[~2026-09-30 21:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 20:59 Tanmay Shah
2026-09-27 8:55 ` Francesco Valla
2026-09-30 21:59 ` Shah, Tanmay [this message]
2026-10-01 16:50 ` Mathieu Poirier
2026-10-01 17:18 ` Shah, Tanmay
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=44648601-e04e-4d6e-a192-3df6dc1b3b24@amd.com \
--to=tanmays@amd.com \
--cc=andersson@kernel.org \
--cc=francesco@valla.it \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=ohad@wizery.com \
--cc=tanmay.shah@amd.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
all inboxes | Powered by JetHome®