drivers/tty/hvc/Kconfig

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