| # | |
| # RapidIO configuration | |
| # | |
| source "drivers/rapidio/devices/Kconfig" | |
| config RAPIDIO_DISC_TIMEOUT | |
| int "Discovery timeout duration (seconds)" | |
| depends on RAPIDIO | |
| default "30" | |
| ---help--- | |
| Amount of time a discovery node waits for a host to complete | |
| enumeration before giving up. | |
| config RAPIDIO_ENABLE_RX_TX_PORTS | |
| bool "Enable RapidIO Input/Output Ports" | |
| depends on RAPIDIO | |
| ---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 RAPIDIO_DMA_ENGINE | |
| bool "DMA Engine support for RapidIO" | |
| depends on RAPIDIO | |
| select DMADEVICES | |
| select DMA_ENGINE | |
| 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 RAPIDIO_DEBUG | |
| bool "RapidIO subsystem debug messages" | |
| depends on RAPIDIO | |
| 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. | |
| source "drivers/rapidio/switches/Kconfig" |