From: Simon Glass <sjg@chromium.org> When a device type is not supported by U-Boot it is silently ignored. Add some debugging for this. Also show the driver features to provide a fuller picture of feature negotiation. Signed-off-by: Simon Glass <sjg@chromium.org> --- drivers/virtio/virtio-uclass.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/drivers/virtio/virtio-uclass.c b/drivers/virtio/virtio-uclass.c index 262d8ee4655..96a17bae940 100644 --- a/drivers/virtio/virtio-uclass.c +++ b/drivers/virtio/virtio-uclass.c @@ -227,8 +227,8 @@ static int virtio_uclass_post_probe(struct udevice *udev) name = virtio_drv_name[uc_priv->device]; if (!name) { - debug("(%s): underlying virtio device driver unavailable\n", - udev->name); + debug("(%s): underlying virtio device driver (type %#x) unavailable\n", + udev->name, uc_priv->device); return 0; } @@ -307,6 +307,7 @@ static int virtio_uclass_child_pre_probe(struct udevice *vdev) WARN_ON(f >= 64); driver_features |= (1ULL << f); } + log_debug("driver_features %016llx\n", driver_features); /* Some drivers have a separate feature table for virtio v1.0 */ if (uc_priv->feature_table_legacy) { -- 2.43.0