On 29-10-26, 17:27, Francesco Valla wrote: > When a virtio transport exposes a non-discoverable bus, the devicetree > can be used to declare its child devices (if any) and/or other > properties. To allow for that, the virtio framework searches for a node > with a suitable compatible in virtio_device_of_init() when registering > a device [1]; such compatible takes the form "virtio,deviceXX", where > XX is the hexadecimal representation of the virtio device ID as defined > by the virtio specification. > > This patchset thus does not introduce a new functionality, but allows > proper validation of nodes tied to spi-virtio devices, aligning SPI to > what is already being done for e.g. I2C and GPIO virtio devices. > It was sent initially as part of a different patchset [2], but since it > complements a functionality that is de-facto already there and is useful > beyond that specific use case it was sent separately (also following the > maintainer's feedback there to separate it from remoteproc-specific > changes). > > This was tested both with virtio-mmio using qemu-system-aarch64 and with > remoteproc-virtio with a Zephyr backend (with relevant remoteproc-virtio > parts still not upstreamed - see [2]). > > On top of that, I added myself as maintainer for the spi-virtio driver, > since the former maintainer's e-mail bounces back and its owner (Haixu > Cui) did not update it after changing employment. > > Thank you! > > Regards, > Francesco > > [1] > https://elixir.bootlin.com/linux/v7.2.8/source/drivers/virtio/virtio.c#L488 > [2] > https://lore.kernel.org/linux-remoteproc/[email protected]/ > > Signed-off-by: Francesco Valla <[email protected]> > --- > Changes in v3: > - Add Francesco as Maintainer of the spi-virtio driver (instead of > Reviewer) as replacement for the former maintainer (Haixu Cui). > - Link to v2: > https://patch.msgid.link/[email protected]
Acked-by: Viresh Kumar <[email protected]> -- viresh
