b70ea16d2d
Without CONFIG_NET, we get a build failure for the new driver:
ERROR: "skb_queue_tail" [drivers/rpmsg/rpmsg_char.ko] undefined!
ERROR: "skb_put" [drivers/rpmsg/rpmsg_char.ko] undefined!
ERROR: "__alloc_skb" [drivers/rpmsg/rpmsg_char.ko] undefined!
ERROR: "kfree_skb" [drivers/rpmsg/rpmsg_char.ko] undefined!
ERROR: "skb_dequeue" [drivers/rpmsg/rpmsg_char.ko] undefined!
This adds a dependency so we don't try to build the broken configuration.
Fixes: c0cdc19f84 ("rpmsg: Driver for user space endpoint interface")
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
33 lines
736 B
Plaintext
33 lines
736 B
Plaintext
menu "Rpmsg drivers"
|
|
|
|
# RPMSG always gets selected by whoever wants it
|
|
config RPMSG
|
|
tristate
|
|
|
|
config RPMSG_CHAR
|
|
tristate "RPMSG device interface"
|
|
depends on RPMSG
|
|
depends on NET
|
|
help
|
|
Say Y here to export rpmsg endpoints as device files, usually found
|
|
in /dev. They make it possible for user-space programs to send and
|
|
receive rpmsg packets.
|
|
|
|
config RPMSG_QCOM_SMD
|
|
tristate "Qualcomm Shared Memory Driver (SMD)"
|
|
depends on QCOM_SMEM
|
|
depends on QCOM_SMD=n
|
|
select RPMSG
|
|
help
|
|
Say y here to enable support for the Qualcomm Shared Memory Driver
|
|
providing communication channels to remote processors in Qualcomm
|
|
platforms.
|
|
|
|
config RPMSG_VIRTIO
|
|
tristate
|
|
select RPMSG
|
|
select VIRTIO
|
|
select VIRTUALIZATION
|
|
|
|
endmenu
|