nuttx/drivers/rpmsg/Kconfig

#
# For a description of the syntax of this configuration file,
# see the file kconfig-language.txt in the NuttX tools repository.
#

config RPMSG
	bool
	default n
	select OPENAMP

if RPMSG

config RPMSG_LOCAL_CPUNAME
	string "Rpmsg Local Cpuname"
	default LIBC_HOSTNAME

config RPMSG_PING
	bool "rpmsg ping support"
	default n
	---help---
		This is for debugging & profiling, create ping rpmsg
		channel, user can use it to get send/recv speed & latency.

config RPMSG_PORT
	bool
	default n
	---help---
		Rpmsg port transport layer used for cross chip communication.

endif # RPMSG

config RPMSG_VIRTIO
	bool "rpmsg virtio transport support"
	default n
	select RPMSG

if RPMSG_VIRTIO

config RPMSG_VIRTIO_PRIORITY
	int "rpmsg virtio rx thread priority"
	default 224

config RPMSG_VIRTIO_STACKSIZE
	int "rpmsg virtio rx thread stack size"
	default DEFAULT_TASK_STACKSIZE

config RPMSG_VIRTIO_IVSHMEM
	bool "rpmsg virtio ivshmem support"
	default n
	depends on PCI_IVSHMEM
	---help---
		This is rpmsg virtio driver based on pci ivshmem.

if RPMSG_VIRTIO_IVSHMEM

config RPMSG_VIRTIO_IVSHMEM_NAME
	string "rpmsg virtio ivshmem name"
	---help---
		Using this config to custom the rpmsg virtio ivshmem id, cpuname and role,
		using ";" to split the names.
		For example, if RPMSG_VIRTIO_IVSHMEM_CPUNAME = "0:cpu1:m;1:cpu2:s" and pass
		two ivshmem devices to the qemu, we will get two rpmsg virtio ivshmem drivers
		with remote cpu ids: "0","1", names: "cpu1", "cpu2", and roles: "master", "slave"

config RPMSG_VIRTIO_IVSHMEM_BUFFSIZE
	int "rpmsg virtio ivshmem rpmsg buffer size"
	default 2048
	---help---
		The rpmsg buffer size in share memory, the RX and TX buffer size
		are same for now.

config RPMSG_VIRTIO_IVSHMEM_BUFFNUM
	int "rpmsg virtio ivshmem rpmsg buffer number"
	default 8
	---help---
		The rpmsg virtio buffer number in share memory, the RX and TX buffer number
		are same for now.

endif

endif