projects / GitHub / mt8127 / android_kernel_alcatel_ttab.git / blame
| Commit | Line | Data |
|---|---|---|
| 394b701c MP |
1 | # |
| 2 | # RapidIO configuration | |
| 3 | # | |
| 48618fb4 AB |
4 | source "drivers/rapidio/devices/Kconfig" |
| 5 | ||
| 394b701c MP |
6 | config RAPIDIO_DISC_TIMEOUT |
| 7 | int "Discovery timeout duration (seconds)" | |
| 8 | depends on RAPIDIO | |
| 9 | default "30" | |
| 10 | ---help--- | |
| 11 | Amount of time a discovery node waits for a host to complete | |
| 09509603 | 12 | enumeration before giving up. |
| 07590ff0 | 13 | |
| 933af4a6 TM |
14 | config RAPIDIO_ENABLE_RX_TX_PORTS |
| 15 | bool "Enable RapidIO Input/Output Ports" | |
| 16 | depends on RAPIDIO | |
| 17 | ---help--- | |
| 18 | The RapidIO specification describes a Output port transmit | |
| 19 | enable and a Input port receive enable. The recommended state | |
| 20 | for Input ports and Output ports should be disabled. When | |
| 21 | this switch is set the RapidIO subsystem will enable all | |
| 22 | ports for Input/Output direction to allow other traffic | |
| 23 | than Maintenance transfers. | |
| 24 | ||
| e42d98eb AB |
25 | config RAPIDIO_DMA_ENGINE |
| 26 | bool "DMA Engine support for RapidIO" | |
| 27 | depends on RAPIDIO | |
| 28 | select DMADEVICES | |
| 29 | select DMA_ENGINE | |
| 30 | help | |
| 31 | Say Y here if you want to use DMA Engine frameork for RapidIO data | |
| 32 | transfers to/from target RIO devices. RapidIO uses NREAD and | |
| 33 | NWRITE (NWRITE_R, SWRITE) requests to transfer data between local | |
| 34 | memory and memory on remote target device. You need a DMA controller | |
| 35 | capable to perform data transfers to/from RapidIO. | |
| 36 | ||
| 37 | If you are unsure about this, say Y here. | |
| 38 | ||
| 011507e4 AB |
39 | config RAPIDIO_DEBUG |
| 40 | bool "RapidIO subsystem debug messages" | |
| 41 | depends on RAPIDIO | |
| 42 | help | |
| 43 | Say Y here if you want the RapidIO subsystem to produce a bunch of | |
| 44 | debug messages to the system log. Select this if you are having a | |
| 45 | problem with the RapidIO subsystem and want to see more of what is | |
| 46 | going on. | |
| 47 | ||
| 48 | If you are unsure about this, say N here. | |
| 48618fb4 | 49 | |
| a11650e1 AB |
50 | choice |
| 51 | prompt "Enumeration method" | |
| 52 | depends on RAPIDIO | |
| 53 | default RAPIDIO_ENUM_BASIC | |
| 54 | help | |
| 55 | There are different enumeration and discovery mechanisms offered | |
| 56 | for RapidIO subsystem. You may select single built-in method or | |
| 57 | or any number of methods to be built as modules. | |
| 58 | Selecting a built-in method disables use of loadable methods. | |
| 59 | ||
| 60 | If unsure, select Basic built-in. | |
| 61 | ||
| 62 | config RAPIDIO_ENUM_BASIC | |
| 63 | tristate "Basic" | |
| 64 | help | |
| 65 | This option includes basic RapidIO fabric enumeration and discovery | |
| 66 | mechanism similar to one described in RapidIO specification Annex 1. | |
| 67 | ||
| 68 | endchoice | |
| 69 | ||
| 48618fb4 | 70 | source "drivers/rapidio/switches/Kconfig" |