Kconfig 3.1 KB

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