> -----Original Message----- > From: Daniel Baluta (OSS) <[email protected]> > Sent: Tuesday, February 24, 2026 10:04 AM > To: Shenwei Wang <[email protected]>; Bjorn Andersson > <[email protected]>; Arnaud POULIQUEN <[email protected]> > Cc: Linus Walleij <[email protected]>; Andrew Lunn <[email protected]>; Bartosz > Golaszewski <[email protected]>; Jonathan Corbet <[email protected]>; Rob Herring > <[email protected]>; Krzysztof Kozlowski <[email protected]>; Conor Dooley > <[email protected]>; Mathieu Poirier <[email protected]>; Frank Li > <[email protected]>; Sascha Hauer <[email protected]>; Shuah Khan > <[email protected]>; [email protected]; linux- > [email protected]; [email protected]; Pengutronix Kernel Team > <[email protected]>; Fabio Estevam <[email protected]>; Peng Fan > <[email protected]>; [email protected]; linux- > [email protected]; [email protected]; linux-arm- > [email protected]; dl-linux-imx <[email protected]>; Bartosz > Golaszewski <[email protected]> > Subject: Re: [PATCH v8 3/4] gpio: rpmsg: add generic rpmsg GPIO driver > > On 2/24/26 17:56, Shenwei Wang wrote: > > Technically, yes—it's possible to use the virtio mechanism directly without > rpmsg. > > 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
