# SPDX-License-Identifier: GPL-2.0-only
#
# RapidIO configuration
#
config [31mCONFIG_HAVE_RAPIDIO[0m
bool
menuconfig [31mCONFIG_RAPIDIO[0m
tristate "RapidIO support"
depends on [31mCONFIG_HAVE_RAPIDIO[0m || [31mCONFIG_PCI[0m
help
If you say Y here, the kernel will include drivers and
infrastructure code to support RapidIO interconnect devices.
source "drivers/rapidio/devices/Kconfig"
config [31mCONFIG_RAPIDIO_DISC_TIMEOUT[0m
int "Discovery timeout duration (seconds)"
depends on [31mCONFIG_RAPIDIO[0m
default "30"
---help---
Amount of time a discovery node waits for a host to complete
enumeration before giving up.
config [31mCONFIG_RAPIDIO_ENABLE_RX_TX_PORTS[0m
bool "Enable RapidIO Input/Output Ports"
depends on [31mCONFIG_RAPIDIO[0m
---help---
The RapidIO specification describes a Output port transmit
enable and a Input port receive enable. The recommended state
for Input ports and Output ports should be disabled. When
this switch is set the RapidIO subsystem will enable all
ports for Input/Output direction to allow other traffic
than Maintenance transfers.
config [31mCONFIG_RAPIDIO_DMA_ENGINE[0m
bool "DMA Engine support for RapidIO"
depends on [31mCONFIG_RAPIDIO[0m
select [31mCONFIG_DMADEVICES[0m
select [31mCONFIG_DMA_ENGINE[0m
help
Say Y here if you want to use DMA Engine frameork for RapidIO data
transfers to/from target RIO devices. RapidIO uses NREAD and
NWRITE (NWRITE_R, SWRITE) requests to transfer data between local
memory and memory on remote target device. You need a DMA controller
capable to perform data transfers to/from RapidIO.
If you are unsure about this, say Y here.
config [31mCONFIG_RAPIDIO_DEBUG[0m
bool "RapidIO subsystem debug messages"
depends on [31mCONFIG_RAPIDIO[0m
help
Say Y here if you want the RapidIO subsystem to produce a bunch of
debug messages to the system log. Select this if you are having a
problem with the RapidIO subsystem and want to see more of what is
going on.
If you are unsure about this, say N here.
choice
prompt "Enumeration method"
depends on [31mCONFIG_RAPIDIO[0m
default [31mCONFIG_RAPIDIO_ENUM_BASIC[0m
help
There are different enumeration and discovery mechanisms offered
for RapidIO subsystem. You may select single built-in method or
or any number of methods to be built as modules.
Selecting a built-in method disables use of loadable methods.
If unsure, select Basic built-in.
config [31mCONFIG_RAPIDIO_ENUM_BASIC[0m
tristate "Basic"
help
This option includes basic RapidIO fabric enumeration and discovery
mechanism similar to one described in RapidIO specification Annex 1.
endchoice
config [31mCONFIG_RAPIDIO_CHMAN[0m
tristate "RapidIO Channelized Messaging driver"
depends on [31mCONFIG_RAPIDIO[0m
help
This option includes RapidIO channelized messaging driver which
provides socket-like interface to allow sharing of single RapidIO
messaging mailbox between multiple user-space applications.
See "Documentation/driver-api/rapidio/rio_cm.rst" for driver description.
config [31mCONFIG_RAPIDIO_MPORT_CDEV[0m
tristate "RapidIO /dev mport device driver"
depends on [31mCONFIG_RAPIDIO[0m
help
This option includes generic RapidIO mport device driver which
allows to user space applications to perform RapidIO-specific
operations through selected RapidIO mport.
menu "RapidIO Switch drivers"
depends on [31mCONFIG_RAPIDIO[0m
source "drivers/rapidio/switches/Kconfig"
endmenu