mirror of
https://github.com/brain-hackers/u-boot-brain
synced 2024-09-28 07:30:26 +09:00
fdc4aca89e
VirtIO can use various different buses and virtio devices are commonly implemented as PCI devices. But virtual environments without PCI support (a common situation in embedded devices models) might use simple memory mapped device (“virtio-mmio”) instead of the PCI device. This adds a transport driver that implements UCLASS_VIRTIO for virtio over mmio. Signed-off-by: Tuomas Tynkkynen <tuomas.tynkkynen@iki.fi> Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Simon Glass <sjg@chromium.org>
33 lines
1.1 KiB
Plaintext
33 lines
1.1 KiB
Plaintext
# SPDX-License-Identifier: GPL-2.0+
|
|
#
|
|
# Copyright (C) 2018, Tuomas Tynkkynen <tuomas.tynkkynen@iki.fi>
|
|
# Copyright (C) 2018, Bin Meng <bmeng.cn@gmail.com>
|
|
#
|
|
# VirtIO is a virtualization standard for network and disk device drivers
|
|
# where just the guest's device driver "knows" it is running in a virtual
|
|
# environment, and cooperates with the hypervisor. This enables guests to
|
|
# get high performance network and disk operations, and gives most of the
|
|
# performance benefits of paravirtualization. In the U-Boot case, the guest
|
|
# is U-Boot itself, while the virtual environment are normally QEMU targets
|
|
# like ARM, RISC-V and x86.
|
|
#
|
|
# See http://docs.oasis-open.org/virtio/virtio/v1.0/virtio-v1.0.pdf for
|
|
# the VirtIO specification v1.0.
|
|
|
|
menu "VirtIO Drivers"
|
|
|
|
config VIRTIO
|
|
bool
|
|
help
|
|
This option is selected by any driver which implements the virtio
|
|
transport, such as CONFIG_VIRTIO_MMIO or CONFIG_VIRTIO_PCI.
|
|
|
|
config VIRTIO_MMIO
|
|
bool "Platform bus driver for memory mapped virtio devices"
|
|
select VIRTIO
|
|
help
|
|
This driver provides support for memory mapped virtio
|
|
platform device driver.
|
|
|
|
endmenu
|