UART_REMOVE_ONE_PORT(9) 16x50 UART Driver UART_REMOVE_ONE_PORT(9)NAME
uart_remove_one_port - detach a driver defined port structure
int uart_remove_one_port(struct uart_driver * drv, struct uart_port * uport);
pointer to the uart low level driver structure for this port
uart port structure for this port
This unhooks (and hangs up) the specified port structure from the core driver. No further calls will be made to the low-level code for this
COPYRIGHT Kernel Hackers Manual 3.10 June 2014 UART_REMOVE_ONE_PORT(9)
Check Out this Related Man Page
UART(4) BSD Kernel Interfaces Manual UART(4)NAME
uart -- driver for Universal Asynchronous Receiver/Transmitter (UART) devices
With flags encoded as:
0x00010 device is potential system console
0x00080 use this port for remote kernel debugging
0x00100 set RX FIFO trigger level to ``low'' (NS8250 only)
0x00200 set RX FIFO trigger level to ``medium low'' (NS8250 only)
0x00400 set RX FIFO trigger level to ``medium high'' (default, NS8250 only)
0x00800 set RX FIFO trigger level to ``high'' (NS8250 only)
The uart device driver provides support for various classes of UARTs implementing the EIA RS-232C (CCITT V.24) serial communications inter-
face. Each such interface is controlled by a separate and independent instance of the uart driver. The primary support for devices that
contain multiple serial interfaces or that contain other functionality besides one or more serial interfaces is provided by the puc(4), or
scc(4) device drivers. However, the serial interfaces of those devices that are managed by the puc(4), or scc(4) driver are each indepen-
dently controlled by the uart driver. As such, the puc(4), or scc(4) driver provides umbrella functionality for the uart driver and hides
the complexities that are inherent when elementary components are packaged together.
The uart driver has a modular design to allow it to be used on differing hardware and for various purposes. In the following sections the
components are discussed in detail. Options are described in the section that covers the component to which each option applies.
At the heart of the uart driver is the core component. It contains the bus attachments and the low-level interrupt handler.
The core component and the kernel interfaces talk to the hardware through the hardware interface. This interface serves as an abstraction of
the hardware and allows varying UARTs to be used for serial communications.
System devices are UARTs that have a special purpose by way of hardware design or software setup. For example, Sun UltraSparc machines use
UARTs as their keyboard interface. Such an UART cannot be used for general purpose communications. Likewise, when the kernel is configured
for a serial console, the corresponding UART will in turn be a system device so that the kernel can output boot messages early on in the boot
The last but not least of the components is the kernel interface. This component ultimately determines how the UART is made visible to the
kernel in particular and to users in general. The default kernel interface is the TTY interface. This allows the UART to be used for termi-
nals, modems and serial line IP applications. System devices, with the notable exception of serial consoles, generally have specialized ker-
The uart driver supports the following classes of UARTs:
o NS8250: standard hardware based on the 8250, 16450, 16550, 16650, 16750 or the 16950 UARTs.
o SCC: serial communications controllers supported by the scc(4) device driver.
/dev/ttyu? for callin ports
/dev/ttyu?.lock corresponding callin initial-state and lock-state devices
/dev/cuau? for callout ports
/dev/cuau?.lock corresponding callout initial-state and lock-state devices
SEE ALSO puc(4), scc(4)HISTORY
The uart device driver first appeared in FreeBSD 5.2.
The uart device driver and this manual page were written by Marcel Moolenaar <email@example.com>.
BSD March 12, 2008 BSD