Kconfig 4.1 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136
  1. # SPDX-License-Identifier: GPL-2.0
  2. config HVC_DRIVER
  3. bool
  4. help
  5. Generic "hypervisor virtual console" infrastructure for various
  6. hypervisors (pSeries, iSeries, Xen).
  7. It will automatically be selected if one of the back-end console drivers
  8. is selected.
  9. config HVC_IRQ
  10. bool
  11. config HVC_CONSOLE
  12. bool "pSeries Hypervisor Virtual Console support"
  13. depends on PPC_PSERIES
  14. select HVC_DRIVER
  15. select HVC_IRQ
  16. help
  17. pSeries machines when partitioned support a hypervisor virtual
  18. console. This driver allows each pSeries partition to have a console
  19. which is accessed via the HMC.
  20. config HVC_OLD_HVSI
  21. bool "Old driver for pSeries serial port (/dev/hvsi*)"
  22. depends on HVC_CONSOLE
  23. config HVC_OPAL
  24. bool "OPAL Console support"
  25. depends on PPC_POWERNV
  26. select HVC_DRIVER
  27. select HVC_IRQ
  28. default y
  29. help
  30. PowerNV machines running under OPAL need that driver to get a console
  31. config HVC_RTAS
  32. bool "IBM RTAS Console support"
  33. depends on PPC_RTAS
  34. select HVC_DRIVER
  35. help
  36. IBM Console device driver which makes use of RTAS
  37. config HVC_IUCV
  38. bool "z/VM IUCV Hypervisor console support (VM only)"
  39. depends on S390 && NET
  40. select HVC_DRIVER
  41. select IUCV
  42. default y
  43. help
  44. This driver provides a Hypervisor console (HVC) back-end to access
  45. a Linux (console) terminal via a z/VM IUCV communication path.
  46. config HVC_XEN
  47. bool "Xen Hypervisor Console support"
  48. depends on XEN
  49. select HVC_DRIVER
  50. select HVC_IRQ
  51. default y
  52. help
  53. Xen virtual console device driver
  54. config HVC_XEN_FRONTEND
  55. bool "Xen Hypervisor Multiple Consoles support"
  56. depends on HVC_XEN
  57. select XEN_XENBUS_FRONTEND
  58. default y
  59. help
  60. Xen driver for secondary virtual consoles
  61. config HVC_UDBG
  62. bool "udbg based fake hypervisor console"
  63. depends on PPC
  64. select HVC_DRIVER
  65. help
  66. This is meant to be used during HW bring up or debugging when
  67. no other console mechanism exist but udbg, to get you a quick
  68. console for userspace. Do NOT enable in production kernels.
  69. config HVC_DCC
  70. bool "ARM JTAG DCC console"
  71. depends on ARM || ARM64
  72. select HVC_DRIVER
  73. select SERIAL_CORE_CONSOLE
  74. help
  75. This console uses the JTAG DCC on ARM to create a console under the HVC
  76. driver. This console is used through a JTAG only on ARM. If you don't have
  77. a JTAG then you probably don't want this option.
  78. config HVC_DCC_SERIALIZE_SMP
  79. bool "Use DCC only on core 0"
  80. depends on SMP && HVC_DCC
  81. help
  82. Some debuggers, such as Trace32 from Lauterbach GmbH, do not handle
  83. reads/writes from/to DCC on more than one core. Each core has its
  84. own DCC device registers, so when a core reads or writes from/to DCC,
  85. it only accesses its own DCC device. Since kernel code can run on
  86. any core, every time the kernel wants to write to the console, it
  87. might write to a different DCC.
  88. In SMP mode, Trace32 only uses the DCC on core 0. In AMP mode, it
  89. creates multiple windows, and each window shows the DCC output
  90. only from that core's DCC. The result is that console output is
  91. either lost or scattered across windows.
  92. Selecting this option will enable code that serializes all console
  93. input and output to core 0. The DCC driver will create input and
  94. output FIFOs that all cores will use. Reads and writes from/to DCC
  95. are handled by a workqueue that runs only core 0.
  96. config HVC_RISCV_SBI
  97. bool "RISC-V SBI console support"
  98. depends on RISCV_SBI_V01
  99. select HVC_DRIVER
  100. help
  101. This enables support for console output via RISC-V SBI calls, which
  102. is normally used only during boot to output printk.
  103. If you don't know what do to here, say Y.
  104. config HVCS
  105. tristate "IBM Hypervisor Virtual Console Server support"
  106. depends on PPC_PSERIES && HVC_CONSOLE
  107. help
  108. Partitionable IBM Power5 ppc64 machines allow hosting of
  109. firmware virtual consoles from one Linux partition by
  110. another Linux partition. This driver allows console data
  111. from Linux partitions to be accessed through TTY device
  112. interfaces in the device tree of a Linux partition running
  113. this driver.
  114. To compile this driver as a module, choose M here: the
  115. module will be called hvcs. Additionally, this module
  116. will depend on arch specific APIs exported from hvcserver.ko
  117. which will also be compiled when this driver is built as a
  118. module.