u-boot.git/drivers/virtio, branch master

virtio: fix return value check

2026-05-12T18:38:49+00:00

The virtio_blk_do_single_req function returns ulong, which normally is
the processed size, but in an error case can be the actual error. Use
the special IS_ERR_VALUE macro to test for error.

Addresses-Coverity-ID: CID 645833 (DEADCODE) & CID 645834 (NO_EFFECT)
Signed-off-by: Christian Pötzsch 
Reviewed-by: Simon Glass

virtio: fix boot device hunting in qemu with virtio

2026-05-08T21:49:27+00:00

Commit 70101c3217ae ("virtio: mmio: Return error codes on probe
failures") returns -ENODEV where it would return 0 before. That path is
apparently hit in qemu and breaks boot device discovery
(virtio_bootdev_hunt() expects only ENOENT). So return -ENOENT in
that path instead.
The remaining two error returns in the function are untouched as I
don't know where they play a role.

Signed-off-by: Ludwig Nussel 
Reviewed-by: Simon Glass 
Acked-by: Kuan-Wei Chiu

virtio: add support for SIZE_MAX & SEG_MAX features

2026-04-27T17:11:54+00:00

Some virtio implementations may forward the virtio requests directly to
the underlying hw. The hw may have some restrictions in how many and how
big the requests can be. Therefore, the corresponding virtio device will
announce this limitations with the SIZE_MAX & SEG_MAX feature.

Add support for those features. Split an io request into multiple virtio
requests if more than seg_max segments would be used. Also split a
single buffer request into multiple segments if the buffer is bigger
then size_max.

Signed-off-by: Christian Pötzsch 
Signed-off-by: Adam Lackorzynski

virtio: mmio: Return error codes on probe failures

2026-04-22T17:07:55+00:00

Currently, virtio_mmio_probe() returns 0 when it encounters an invalid
magic value, an unsupported version, or a dummy device (ID 0). In
U-Boot's driver model, returning 0 indicates a successful probe. This
causes the system to incorrectly register and activate invalid or
placeholder devices, potentially leading to undefined behavior or
crashes later on.

Update the probe function to return appropriate error codes (-ENODEV
for invalid magic values and dummy devices, and -ENXIO for unsupported
versions). This fix correctly instructs the DM to abort the binding
process.

Fixes: fdc4aca89ecb ("virtio: Add virtio over mmio transport driver")
Signed-off-by: Kuan-Wei Chiu 
Acked-by: Daniel Palmer

virtio: Fix virtio initialization sequence

2026-03-25T20:33:00+00:00

The virtio spec clearly states in "3.1.1 Driver Requirements: Device
Initialization" the sequence a client has to follow after device reset.
Because u-boot resets here again, it also needs to set the "acknowledge"
bit again even if this was done in virtio_uclass_child_post_bind already
once before.

Signed-off-by: Christian Pötzsch 
Signed-off-by: Adam Lackorzynski 
[trini: Add VIRTIO_CONFIG_S_ACKNOWLEDGE flag check to the test]
Signed-off-by: Tom Rini

virtio: rng: Handle oversized return buffers

2026-03-25T20:32:38+00:00

If extra random bytes are returned, truncate and use the requested number
instead of returning an error.

Signed-off-by: Kavin Gunasekara 
Signed-off-by: Meet Patel 
Reviewed-by: Andre Przywara

virtio: typo 'private date'

2025-11-07T21:34:22+00:00

%s/private date/private data/

Signed-off-by: Heinrich Schuchardt 
Reviewed-by: Bin Meng

virtio: typo complaint

2025-11-07T21:34:22+00:00

%s/v1.0 complaint/v1.0 compliant/

Signed-off-by: Heinrich Schuchardt 
Reviewed-by: Bin Meng

virito: blk: fix logic to determine block sizes

2025-10-17T00:01:42+00:00

With commit c85b8071e7d3 ("virtio: blk: support block sizes exceeding 512
bytes") logic was added to detect the VIRTIO_BLK_F_BLK_SIZE capability and
to copy the block size reported by QEMU to the block device descriptor.

The logical block size can be set when invoking QEMU:

    -drive if=none,file=4096.img,format=raw,id=vda \
    -device virtio-blk-device,drive=vda,physical_block_size=4096,logical_block_size=4096

In U-Boot the logical block size is shown by command `virtio info`:

    => virtio info
    Device 0: QEMU VirtIO Block Device
                Type: Hard Disk
                Capacity: 1024.0 MB = 1.0 GB (262144 x 4096)

There where two flaws which together hid that the logic was incorrect:

* VIRTIO_BLK_F_BLK_SIZE was missing in the driver capabilities and the bit
  was filtered out.
* The result of the call to virtio_has_feature() was negated.

The problem became apparent when using ARM FVP as emulator which does not set
VIRTIO_BLK_F_BLK_SIZE.

Fixes: c85b8071e7d3 ("virtio: blk: support block sizes exceeding 512 bytes")
Reported-by: Debbie Horsfall 
Tested-by: Andre Przywara 
Signed-off-by: Heinrich Schuchardt

virtio: blk: support block sizes exceeding 512 bytes

2025-09-10T17:02:23+00:00

QEMU allows to specify the logical block size via parameter
logical_block_size of a virtio-blk-device.

The communication channel via virtqueues remains based on 512 byte blocks
even if the logical_block_size is larger.

Consider the logical block size in the block device driver.

Reported-by: Emil Renner Berthing 
Signed-off-by: Heinrich Schuchardt 
Tested-by: Emil Renner Berthing