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