Difference between revisions of "Unit UART"
(Created page with "Return to Unit Reference === Description === ---- ''To be documented'' === Constants === ---- ''To be documented'' === Type definitions === ---- ''To...") |
|||
| Line 5: | Line 5: | ||
---- | ---- | ||
| − | + | UART (Universal Asynchronous Receiver Transmitter) devices represent the industry standard serial communications devices that are available on almost every system. | |
| + | |||
| + | This unit implements the framework for UART devices and provides a standardized API to allow driver specific implementation to be abstracted. All UART devices are also represented as a serial device | ||
| + | and this unit handles the relationship between the two devices. | ||
| + | |||
| + | Each UART device returns a set of properties that describe the capabilities of the device and includes a set of flags that indicate what features are supported. | ||
| + | |||
| + | Reads and writes to UART devices are unbuffered and simply pass raw data to and from the caller unless the serial interface is used instead which includes buffering of transmitted and received data. Both reads and writes allow for non blocking so that a caller can avoid waiting for received data to be available or the device to be ready to transmit. | ||
=== Constants === | === Constants === | ||
Revision as of 03:44, 9 September 2016
Return to Unit Reference
Description
UART (Universal Asynchronous Receiver Transmitter) devices represent the industry standard serial communications devices that are available on almost every system.
This unit implements the framework for UART devices and provides a standardized API to allow driver specific implementation to be abstracted. All UART devices are also represented as a serial device and this unit handles the relationship between the two devices.
Each UART device returns a set of properties that describe the capabilities of the device and includes a set of flags that indicate what features are supported.
Reads and writes to UART devices are unbuffered and simply pass raw data to and from the caller unless the serial interface is used instead which includes buffering of transmitted and received data. Both reads and writes allow for non blocking so that a caller can avoid waiting for received data to be available or the device to be ready to transmit.
Constants
To be documented
Type definitions
To be documented
Public variables
To be documented
Function declarations
To be documented
Return to Unit Reference
