Kconfig 3.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118
  1. if TTY
  2. config HVC_DRIVER
  3. bool
  4. help
  5. Generic "hypervisor virtual console" infrastructure for various
  6. hypervisors (pSeries, iSeries, Xen, lguest).
  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. default n
  24. config HVC_OPAL
  25. bool "OPAL Console support"
  26. depends on PPC_POWERNV
  27. select HVC_DRIVER
  28. select HVC_IRQ
  29. default y
  30. help
  31. PowerNV machines running under OPAL need that driver to get a console
  32. config HVC_RTAS
  33. bool "IBM RTAS Console support"
  34. depends on PPC_RTAS
  35. select HVC_DRIVER
  36. help
  37. IBM Console device driver which makes use of RTAS
  38. config HVC_IUCV
  39. bool "z/VM IUCV Hypervisor console support (VM only)"
  40. depends on S390
  41. select HVC_DRIVER
  42. select IUCV
  43. default y
  44. help
  45. This driver provides a Hypervisor console (HVC) back-end to access
  46. a Linux (console) terminal via a z/VM IUCV communication path.
  47. config HVC_XEN
  48. bool "Xen Hypervisor Console support"
  49. depends on XEN
  50. select HVC_DRIVER
  51. select HVC_IRQ
  52. default y
  53. help
  54. Xen virtual console device driver
  55. config HVC_XEN_FRONTEND
  56. bool "Xen Hypervisor Multiple Consoles support"
  57. depends on HVC_XEN
  58. select XEN_XENBUS_FRONTEND
  59. default y
  60. help
  61. Xen driver for secondary virtual consoles
  62. config HVC_UDBG
  63. bool "udbg based fake hypervisor console"
  64. depends on PPC
  65. select HVC_DRIVER
  66. default n
  67. help
  68. This is meant to be used during HW bring up or debugging when
  69. no other console mechanism exist but udbg, to get you a quick
  70. console for userspace. Do NOT enable in production kernels.
  71. config HVC_DCC
  72. bool "ARM JTAG DCC console"
  73. depends on ARM || ARM64
  74. select HVC_DRIVER
  75. help
  76. This console uses the JTAG DCC on ARM to create a console under the HVC
  77. driver. This console is used through a JTAG only on ARM. If you don't have
  78. a JTAG then you probably don't want this option.
  79. config HVC_BFIN_JTAG
  80. bool "Blackfin JTAG console"
  81. depends on BLACKFIN
  82. select HVC_DRIVER
  83. help
  84. This console uses the Blackfin JTAG to create a console under the
  85. the HVC driver. If you don't have JTAG, then you probably don't
  86. want this option.
  87. config HVCS
  88. tristate "IBM Hypervisor Virtual Console Server support"
  89. depends on PPC_PSERIES && HVC_CONSOLE
  90. help
  91. Partitionable IBM Power5 ppc64 machines allow hosting of
  92. firmware virtual consoles from one Linux partition by
  93. another Linux partition. This driver allows console data
  94. from Linux partitions to be accessed through TTY device
  95. interfaces in the device tree of a Linux partition running
  96. this driver.
  97. To compile this driver as a module, choose M here: the
  98. module will be called hvcs. Additionally, this module
  99. will depend on arch specific APIs exported from hvcserver.ko
  100. which will also be compiled when this driver is built as a
  101. module.
  102. endif # TTY