xref: /openbmc/linux/drivers/rapidio/Kconfig (revision 207a369e)
1#
2# RapidIO configuration
3#
4
5config HAVE_RAPIDIO
6	bool
7
8menuconfig RAPIDIO
9	tristate "RapidIO support"
10	depends on HAVE_RAPIDIO || PCI
11	help
12	  If you say Y here, the kernel will include drivers and
13	  infrastructure code to support RapidIO interconnect devices.
14
15source "drivers/rapidio/devices/Kconfig"
16
17config RAPIDIO_DISC_TIMEOUT
18	int "Discovery timeout duration (seconds)"
19	depends on RAPIDIO
20	default "30"
21	---help---
22	  Amount of time a discovery node waits for a host to complete
23	  enumeration before giving up.
24
25config RAPIDIO_ENABLE_RX_TX_PORTS
26	bool "Enable RapidIO Input/Output Ports"
27	depends on RAPIDIO
28	---help---
29	  The RapidIO specification describes a Output port transmit
30	  enable and a Input port receive enable. The recommended state
31	  for Input ports and Output ports should be disabled. When
32	  this switch is set the RapidIO subsystem will enable all
33	  ports for Input/Output direction to allow other traffic
34	  than Maintenance transfers.
35
36config RAPIDIO_DMA_ENGINE
37	bool "DMA Engine support for RapidIO"
38	depends on RAPIDIO
39	select DMADEVICES
40	select DMA_ENGINE
41	help
42	  Say Y here if you want to use DMA Engine frameork for RapidIO data
43	  transfers to/from target RIO devices. RapidIO uses NREAD and
44	  NWRITE (NWRITE_R, SWRITE) requests to transfer data between local
45	  memory and memory on remote target device. You need a DMA controller
46	  capable to perform data transfers to/from RapidIO.
47
48	  If you are unsure about this, say Y here.
49
50config RAPIDIO_DEBUG
51	bool "RapidIO subsystem debug messages"
52	depends on RAPIDIO
53	help
54	  Say Y here if you want the RapidIO subsystem to produce a bunch of
55	  debug messages to the system log. Select this if you are having a
56	  problem with the RapidIO subsystem and want to see more of what is
57	  going on.
58
59	  If you are unsure about this, say N here.
60
61choice
62	prompt "Enumeration method"
63	depends on RAPIDIO
64	default RAPIDIO_ENUM_BASIC
65	help
66	  There are different enumeration and discovery mechanisms offered
67	  for RapidIO subsystem. You may select single built-in method or
68	  or any number of methods to be built as modules.
69	  Selecting a built-in method disables use of loadable methods.
70
71	  If unsure, select Basic built-in.
72
73config RAPIDIO_ENUM_BASIC
74	tristate "Basic"
75	help
76	  This option includes basic RapidIO fabric enumeration and discovery
77	  mechanism similar to one described in RapidIO specification Annex 1.
78
79endchoice
80
81config RAPIDIO_CHMAN
82	tristate "RapidIO Channelized Messaging driver"
83	depends on RAPIDIO
84	help
85	  This option includes RapidIO channelized messaging driver which
86	  provides socket-like interface to allow sharing of single RapidIO
87	  messaging mailbox between multiple user-space applications.
88	  See "Documentation/rapidio/rio_cm.txt" for driver description.
89
90config RAPIDIO_MPORT_CDEV
91	tristate "RapidIO /dev mport device driver"
92	depends on RAPIDIO
93	help
94	  This option includes generic RapidIO mport device driver which
95	  allows to user space applications to perform RapidIO-specific
96	  operations through selected RapidIO mport.
97
98menu "RapidIO Switch drivers"
99	depends on RAPIDIO
100
101source "drivers/rapidio/switches/Kconfig"
102
103endmenu
104