Blame view

kernel/linux-rt-4.4.41/drivers/rapidio/Kconfig 2.5 KB
5113f6f70   김현기   kernel add
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
  #
  # 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.
  
  choice
  	prompt "Enumeration method"
  	depends on RAPIDIO
  	default RAPIDIO_ENUM_BASIC
  	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 RAPIDIO_ENUM_BASIC
  	tristate "Basic"
  	help
  	  This option includes basic RapidIO fabric enumeration and discovery
  	  mechanism similar to one described in RapidIO specification Annex 1.
  
  endchoice
  
  config RAPIDIO_MPORT_CDEV
  	tristate "RapidIO /dev mport device driver"
  	depends on RAPIDIO
  	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 RAPIDIO
  
  source "drivers/rapidio/switches/Kconfig"
  
  endmenu