xref: /linux/drivers/s390/char/Kconfig (revision 9e9f60108423f18a99c9cc93ef7f23490ecc709b)
1comment "S/390 character device drivers"
2	depends on S390
3
4config TN3270
5	def_tristate y
6	prompt "Support for locally attached 3270 terminals"
7	depends on CCW
8	help
9	  Include support for IBM 3270 terminals.
10
11config TN3270_TTY
12	def_tristate y
13	prompt "Support for tty input/output on 3270 terminals"
14	depends on TN3270 && TTY
15	help
16	  Include support for using an IBM 3270 terminal as a Linux tty.
17
18config TN3270_FS
19	def_tristate m
20	prompt "Support for fullscreen applications on 3270 terminals"
21	depends on TN3270
22	help
23	  Include support for fullscreen applications on an IBM 3270 terminal.
24
25config TN3270_CONSOLE
26	def_bool y
27	prompt "Support for console on 3270 terminal"
28	depends on TN3270=y && TN3270_TTY=y
29	help
30	  Include support for using an IBM 3270 terminal as a Linux system
31	  console.  Available only if 3270 support is compiled in statically.
32
33config TN3215
34	def_bool y
35	prompt "Support for 3215 line mode terminal"
36	depends on CCW && TTY
37	help
38	  Include support for IBM 3215 line-mode terminals.
39
40config TN3215_CONSOLE
41	def_bool y
42	prompt "Support for console on 3215 line mode terminal"
43	depends on TN3215
44	help
45	  Include support for using an IBM 3215 line-mode terminal as a
46	  Linux system console.
47
48config CCW_CONSOLE
49	def_bool y if TN3215_CONSOLE || TN3270_CONSOLE
50
51config SCLP_TTY
52	def_bool y
53	prompt "Support for SCLP line mode terminal"
54	depends on S390 && TTY
55	help
56	  Include support for IBM SCLP line-mode terminals.
57
58config SCLP_CONSOLE
59	def_bool y
60	prompt "Support for console on SCLP line mode terminal"
61	depends on SCLP_TTY
62	help
63	  Include support for using an IBM HWC line-mode terminal as the Linux
64	  system console.
65
66config SCLP_VT220_TTY
67	def_bool y
68	prompt "Support for SCLP VT220-compatible terminal"
69	depends on S390 && TTY
70	help
71	  Include support for an IBM SCLP VT220-compatible terminal.
72
73config SCLP_VT220_CONSOLE
74	def_bool y
75	prompt "Support for console on SCLP VT220-compatible terminal"
76	depends on SCLP_VT220_TTY
77	help
78	  Include support for using an IBM SCLP VT220-compatible terminal as a
79	  Linux system console.
80
81config SCLP_CPI
82	def_tristate m
83	prompt "Control-Program Identification"
84	depends on S390
85	help
86	  This option enables the hardware console interface for system
87	  identification. This is commonly used for workload management and
88	  gives you a nice name for the system on the service element.
89	  Please select this option as a module since built-in operation is
90	  completely untested.
91	  You should only select this option if you know what you are doing,
92	  need this feature and intend to run your kernel in LPAR.
93
94config SCLP_ASYNC
95	def_tristate m
96	prompt "Support for Call Home via Asynchronous SCLP Records"
97	depends on S390
98	help
99	  This option enables the call home function, which is able to inform
100	  the service element and connected organisations about a kernel panic.
101	  You should only select this option if you know what you are doing,
102	  want for inform other people about your kernel panics,
103	  need this feature and intend to run your kernel in LPAR.
104
105config SCLP_ASYNC_ID
106       string "Component ID for Call Home"
107       depends on SCLP_ASYNC
108       default "000000000"
109       help
110	 The Component ID for Call Home is used to identify the correct
111	 problem reporting queue the call home records should be sent to.
112
113	 If your are unsure, please use the default value "000000000".
114
115config HMC_DRV
116	def_tristate m
117	prompt "Support for file transfers from HMC drive CD/DVD-ROM"
118	depends on S390 && 64BIT
119	select CRC16
120	help
121	  This option enables support for file transfers from a Hardware
122	  Management Console (HMC) drive CD/DVD-ROM. It is available as a
123	  module, called 'hmcdrv', and also as kernel built-in. There is one
124	  optional parameter for this module: cachesize=N, which modifies the
125	  transfer cache size from it's default value 0.5MB to N bytes. If N
126	  is zero, then no caching is performed.
127
128config S390_TAPE
129	def_tristate m
130	prompt "S/390 tape device support"
131	depends on CCW
132	help
133	  Select this option if you want to access channel-attached tape
134	  devices on IBM S/390 or zSeries.
135	  If you select this option you will also want to select at
136	  least one of the tape interface options and one of the tape
137	  hardware options in order to access a tape device.
138	  This option is also available as a module. The module will be
139	  called tape390 and include all selected interfaces and
140	  hardware drivers.
141
142comment "S/390 tape hardware support"
143	depends on S390_TAPE
144
145config S390_TAPE_34XX
146	def_tristate m
147	prompt "Support for 3480/3490 tape hardware"
148	depends on S390_TAPE
149	help
150	  Select this option if you want to access IBM 3480/3490 magnetic
151	  tape subsystems and 100% compatibles.
152	  It is safe to say "Y" here.
153
154config S390_TAPE_3590
155	def_tristate m
156	prompt "Support for 3590 tape hardware"
157	depends on S390_TAPE
158	help
159	  Select this option if you want to access IBM 3590 magnetic
160	  tape subsystems and 100% compatibles.
161	  It is safe to say "Y" here.
162
163config VMLOGRDR
164	def_tristate m
165	prompt "Support for the z/VM recording system services (VM only)"
166	depends on IUCV
167	help
168	  Select this option if you want to be able to receive records collected
169	  by the z/VM recording system services, eg. from *LOGREC, *ACCOUNT or
170	  *SYMPTOM.
171	  This driver depends on the IUCV support driver.
172
173config VMCP
174	def_bool y
175	prompt "Support for the z/VM CP interface"
176	depends on S390
177	help
178	  Select this option if you want to be able to interact with the control
179	  program on z/VM
180
181config MONREADER
182	def_tristate m
183	prompt "API for reading z/VM monitor service records"
184	depends on IUCV
185	help
186	  Character device driver for reading z/VM monitor service records
187
188config MONWRITER
189	def_tristate m
190	prompt "API for writing z/VM monitor service records"
191	depends on S390
192	help
193	  Character device driver for writing z/VM monitor service records
194
195config S390_VMUR
196	def_tristate m
197	prompt "z/VM unit record device driver"
198	depends on S390
199	help
200	  Character device driver for z/VM reader, puncher and printer.
201
202