diff options
author | Timur Tabi <timur@freescale.com> | 2011-07-08 20:06:12 -0400 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@suse.de> | 2011-08-23 13:32:56 -0400 |
commit | dcd83aaff1c8cbd5b48c152b559e0af3ea1a7b65 (patch) | |
tree | 536ce3416fd908f0506899b371d86fb21171078c /drivers/tty/Kconfig | |
parent | fcb8ce5cfe30ca9ca5c9a79cdfe26d1993e65e0c (diff) |
tty/powerpc: introduce the ePAPR embedded hypervisor byte channel driver
The ePAPR embedded hypervisor specification provides an API for "byte
channels", which are serial-like virtual devices for sending and receiving
streams of bytes. This driver provides Linux kernel support for byte
channels via three distinct interfaces:
1) An early-console (udbg) driver. This provides early console output
through a byte channel. The byte channel handle must be specified in a
Kconfig option.
2) A normal console driver. Output is sent to the byte channel designated
for stdout in the device tree. The console driver is for handling kernel
printk calls.
3) A tty driver, which is used to handle user-space input and output. The
byte channel used for the console is designated as the default tty.
Signed-off-by: Timur Tabi <timur@freescale.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'drivers/tty/Kconfig')
-rw-r--r-- | drivers/tty/Kconfig | 34 |
1 files changed, 34 insertions, 0 deletions
diff --git a/drivers/tty/Kconfig b/drivers/tty/Kconfig index bd7cc0527999..f1ea59b09444 100644 --- a/drivers/tty/Kconfig +++ b/drivers/tty/Kconfig | |||
@@ -350,3 +350,37 @@ config TRACE_SINK | |||
350 | 350 | ||
351 | If you select this option, you need to select | 351 | If you select this option, you need to select |
352 | "Trace data router for MIPI P1149.7 cJTAG standard". | 352 | "Trace data router for MIPI P1149.7 cJTAG standard". |
353 | |||
354 | config PPC_EPAPR_HV_BYTECHAN | ||
355 | tristate "ePAPR hypervisor byte channel driver" | ||
356 | depends on PPC | ||
357 | help | ||
358 | This driver creates /dev entries for each ePAPR hypervisor byte | ||
359 | channel, thereby allowing applications to communicate with byte | ||
360 | channels as if they were serial ports. | ||
361 | |||
362 | config PPC_EARLY_DEBUG_EHV_BC | ||
363 | bool "Early console (udbg) support for ePAPR hypervisors" | ||
364 | depends on PPC_EPAPR_HV_BYTECHAN | ||
365 | help | ||
366 | Select this option to enable early console (a.k.a. "udbg") support | ||
367 | via an ePAPR byte channel. You also need to choose the byte channel | ||
368 | handle below. | ||
369 | |||
370 | config PPC_EARLY_DEBUG_EHV_BC_HANDLE | ||
371 | int "Byte channel handle for early console (udbg)" | ||
372 | depends on PPC_EARLY_DEBUG_EHV_BC | ||
373 | default 0 | ||
374 | help | ||
375 | If you want early console (udbg) output through a byte channel, | ||
376 | specify the handle of the byte channel to use. | ||
377 | |||
378 | For this to work, the byte channel driver must be compiled | ||
379 | in-kernel, not as a module. | ||
380 | |||
381 | Note that only one early console driver can be enabled, so don't | ||
382 | enable any others if you enable this one. | ||
383 | |||
384 | If the number you specify is not a valid byte channel handle, then | ||
385 | there simply will be no early console output. This is true also | ||
386 | if you don't boot under a hypervisor at all. | ||