Kconfig 6.8 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196
  1. menuconfig CORESIGHT
  2. bool "CoreSight Tracing Support"
  3. help
  4. CoreSight components are compliant with the ARM CoreSight
  5. architecture specification and can be connected in various
  6. topologies to suite a particular SoCs tracing needs. These trace
  7. components can generally be classified as sources, links and
  8. sinks. Trace data produced by one or more sources flows through
  9. the intermediate links connecting the source to the currently
  10. selected sink.
  11. This framework provides an interface for the CoreSight debug and
  12. trace drivers to register themselves with. It's intended to build
  13. up a topological view of the CoreSight components and configure
  14. the right series of components on user input via sysfs. It also
  15. provides status information to user space applications through
  16. sysfs interface.
  17. If unsure, say 'N' here to avoid potential power, performance and
  18. memory penalty.
  19. if CORESIGHT
  20. config HAVE_CORESIGHT_SINK
  21. bool
  22. config CORESIGHT_FUSE
  23. bool "CoreSight Fuse driver"
  24. help
  25. This driver provides support for CoreSight Fuse state checks that
  26. other CoreSight drivers can query to determine existence of
  27. Hardware functionality they support. Drivers can then take necessary
  28. actions like failing the probe if the Hardware they manage is
  29. functionally disabled.
  30. config CORESIGHT_CTI
  31. bool "CoreSight Cross Trigger Interface driver"
  32. help
  33. This driver provides support for Cross Trigger Interface that is
  34. used to input or output i.e. pass cross trigger events from one
  35. hardware component to another. It can also be used to pass
  36. software generated events.
  37. config CORESIGHT_CSR
  38. bool "CoreSight Slave Register driver"
  39. help
  40. This driver provides support for CoreSight Slave Register block
  41. that hosts miscellaneous configuration registers.
  42. config CORESIGHT_TMC
  43. bool "CoreSight Trace Memory Controller driver"
  44. select CORESIGHT_CTI
  45. select CORESIGHT_CSR
  46. select HAVE_CORESIGHT_SINK
  47. help
  48. This driver provides support for Trace Memory Controller which
  49. can be configured as either an ETB (Embedded Trace Buffer),
  50. ETR (Embedded Trace Router) or ETF (Embedded Trace Fifo). It acts
  51. as sink when configured as ETB, ETR or ETF in circular buffer mode
  52. whereas it is a link when configured as ETF in hardware fifo mode.
  53. ETB collects trace data in a circular buffer whereas ETR can be
  54. used to route trace data to memory allocated in RAM. ETF in
  55. circular buffer mode is like an ETB whereas in hardware fifo mode
  56. it is a fifo link.
  57. config CORESIGHT_TPIU
  58. bool "CoreSight Trace Port Interface Unit driver"
  59. select HAVE_CORESIGHT_SINK
  60. help
  61. This driver provides support for Trace Port Interface Unit which
  62. acts as a conduit for offchip trace collection.
  63. config CORESIGHT_ETB
  64. bool "CoreSight Embedded Trace Buffer driver"
  65. select HAVE_CORESIGHT_SINK
  66. help
  67. This driver provides support for the legacy Embedded Trace Buffer
  68. which is a circular buffer.
  69. if HAVE_CORESIGHT_SINK
  70. config CORESIGHT_FUNNEL
  71. bool "CoreSight Funnel driver"
  72. help
  73. This driver provides support for Funnel which is a link that
  74. typically has multiple input ports and a single output port. Input
  75. trace data streams from the input ports are interleaved into a
  76. single output trace data stream coming out of the output port.
  77. config CORESIGHT_REPLICATOR
  78. bool "CoreSight Replicator driver"
  79. help
  80. This driver provides support for Replicator that typically has
  81. a single input port and two output ports. Single trace data
  82. stream on the input port is replicated to produce two identical
  83. trace data output streams coming out of the two output ports.
  84. config CORESIGHT_STM
  85. bool "CoreSight System Trace Macrocell driver"
  86. help
  87. This driver provides support for hardware assisted software
  88. instrumentation based tracing. This is primarily useful for
  89. logging useful software events or data.
  90. config CORESIGHT_STM_DEFAULT_ENABLE
  91. bool "Turn on STM tracing by default"
  92. depends on CORESIGHT_STM
  93. help
  94. Turns on CoreSight STM tracing (hardware assisted software
  95. instrumentation based tracing) by default. Otherwise, tracing is
  96. disabled by default but can be enabled via sysfs.
  97. If unsure, say 'N' here to avoid potential power and performance
  98. penalty.
  99. config CORESIGHT_HWEVENT
  100. bool "CoreSight Hardware Event driver"
  101. depends on CORESIGHT_STM
  102. select CORESIGHT_CSR
  103. help
  104. This driver provides support for monitoring and tracing CoreSight
  105. Hardware Event across STM interface. It configures Coresight
  106. Hardware Event mux control registers to select hardware events
  107. based on user input.
  108. config CORESIGHT_ETM
  109. bool "CoreSight Embedded Trace Macrocell driver"
  110. help
  111. This driver provides support for processor tracing which allows
  112. tracing the instructions that the processor is executing. This is
  113. primarily useful for instruction level tracing.
  114. config CORESIGHT_ETM_DEFAULT_ENABLE
  115. bool "Turn on ETM tracing by default"
  116. depends on CORESIGHT_ETM
  117. help
  118. Turns on CoreSight ETM tracing (processor tracing) by default.
  119. Otherwise, tracing is disabled by default but can be enabled via
  120. sysfs.
  121. If unsure, say 'N' here to avoid potential power and performance
  122. penalty.
  123. config CORESIGHT_ETM_PCSAVE_DEFAULT_ENABLE
  124. bool "Turn on PC saving by default"
  125. depends on CORESIGHT_ETM
  126. help
  127. Turns on program counter saving on reset by default. Otherwise,
  128. PC saving is disabled by default but can be enabled via sysfs.
  129. If unsure, say 'N' here to avoid potential power penalty.
  130. config CORESIGHT_AUDIO_ETM
  131. bool "Audio processor ETM trace support"
  132. help
  133. Enables support for ETM trace collection on audio processor using
  134. CoreSight framework. Enabling this will allow turning on ETM tracing
  135. on audio processor via sysfs by configuring the required CoreSight
  136. components.
  137. config CORESIGHT_MODEM_ETM
  138. bool "Modem processor ETM trace support"
  139. help
  140. Enables support for ETM trace collection on modem processor using
  141. CoreSight framework. Enabling this will allow turning on ETM tracing
  142. on modem processor via sysfs by configuring the required CoreSight
  143. components.
  144. config CORESIGHT_WCN_ETM
  145. bool "Wireless subsystem processor ETM trace support"
  146. help
  147. Enables support for ETM trace collection on wireless subsystem
  148. processor using CoreSight framework. Enabling this will allow
  149. turning on ETM tracing on wireless subsystem via sysfs by configuring
  150. the required CoreSight components.
  151. config CORESIGHT_RPM_ETM
  152. bool "RPM processor ETM trace support"
  153. help
  154. Enables support for ETM trace collection on RPM processor using
  155. CoreSight framework. Enabling this will allow turning on ETM
  156. tracing on RPM processor via sysfs by configuring the required
  157. CoreSight components.
  158. endif
  159. config CORESIGHT_EVENT
  160. tristate "CoreSight Event driver"
  161. help
  162. This driver provides support for registering with various events
  163. and performing CoreSight actions like aborting trace on their
  164. occurrence.
  165. endif