u-boot.git/test/dm/virtio_device.c, branch v2024.04

virtio: Avoid strange behaviour on removal

2023-01-23T23:11:40Z

This device does a check on removal which is better handled in the actual test. Move it. Signed-off-by: Simon Glass

dm: treewide: Use uclass_first_device_err when accessing one device

2022-10-18T03:17:12Z

There is a number of users that use uclass_first_device to access the first and (assumed) only device in uclass. Some check the return value of uclass_first_device and also that a device was returned which is exactly what uclass_first_device_err does. Some are not checking that a device was returned and can potentially crash if no device exists in the uclass. Finally there is one that returns NULL on error either way. Convert all of these to use uclass_first_device_err instead, the return value will be removed from uclass_first_device in a later patch. Signed-off-by: Michal Suchanek Reviewed-by: Simon Glass

test: dm: virtio: Test virtio device driver probing

2022-06-08T13:24:04Z

Once the virtio-rng driver has been bound, probe it to trigger the pre and post child probe hooks of the virtio uclass driver. Check the status of the virtio device to confirm it reached the expected state. Signed-off-by: Andrew Scull Reviewed-by: Simon Glass

virtio: sandbox: Bind RNG rather than block device

2022-06-08T13:24:04Z

The virtio-rng driver is extremely simple, making it suitable for testing more of the virtio uclass logic. Have the sandbox driver bind the virtio-rng driver rather than the virtio-blk driver so it can be used in tests. Signed-off-by: Andrew Scull Reviewed-by: Simon Glass

test: dm: virtio: Split out virtio device tests

2022-06-08T13:24:04Z

Virtio tests that find a child device require the virtio device driver to be included in the build so it can probe. The sandbox virtio transport driver currently reports a virtio-blk device so make sure the corresponding driver is built before running tests that need it. Signed-off-by: Andrew Scull