-----Original Message-----
From: Daniel Baluta (OSS) <redacted>
Sent: Tuesday, February 24, 2026 10:04 AM
To: Shenwei Wang <shenwei.wang@nxp.com>; Bjorn Andersson
[off-list ref]; Arnaud POULIQUEN [off-list ref]
Cc: Linus Walleij <linusw@kernel.org>; Andrew Lunn <andrew@lunn.ch>; Bartosz
Golaszewski [off-list ref]; Jonathan Corbet [off-list ref]; Rob Herring
[off-list ref]; Krzysztof Kozlowski [off-list ref]; Conor Dooley
[off-list ref]; Mathieu Poirier [off-list ref]; Frank Li
[off-list ref]; Sascha Hauer [off-list ref]; Shuah Khan
[off-list ref]; linux-gpio@vger.kernel.org; linux-
doc@vger.kernel.org; linux-kernel@vger.kernel.org; Pengutronix Kernel Team
[off-list ref]; Fabio Estevam [off-list ref]; Peng Fan
[off-list ref]; devicetree@vger.kernel.org; linux-
remoteproc@vger.kernel.org; imx@lists.linux.dev; linux-arm-
kernel@lists.infradead.org; dl-linux-imx [off-list ref]; Bartosz
Golaszewski [off-list ref]
Subject: Re: [PATCH v8 3/4] gpio: rpmsg: add generic rpmsg GPIO driver

On 2/24/26 17:56, Shenwei Wang wrote:

quoted

Technically, yes—it's possible to use the virtio mechanism directly without

rpmsg.

quoted

It’s a bit like talking straight to the IP layer without involving TCP
or UDP: doable, but at a lower‑level approach.

As for the idea of gpio‑virtio, which could be an optional solution
that certain customers might prefer. I recall hearing this idea from
Mathieu originally, though I’m not sure whether he plans to implement it.

gpio-virtio is already upstream in drivers/gpio/gpio-virtio.c

I’m not an expert on virtio, but having the gpio‑virtio driver upstream on the Linux side doesn’t 
necessarily mean the overall solution is complete. The remote firmware still needs to implement 
the virtio‑GPIO backend, expose the virtio‑GPIO device, and handle all of the underlying hardware 
interactions.

My understanding is that this firmware-side implementation is the part we were interested in.

Thanks,
Shenwei