riot-ci/RIOT
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

drivers/uart: fix typos

Browse Source
This commit is contained in:
Laurent Navet 2016-06-14 22:54:25 +02:00
parent a701262cc7
commit 96ebff9174
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
drivers/include/periph/uart.h
View File

@ -16,7 +16,7 @@
* to allow platform independent access to the MCU's serial communication abilities. * to allow platform independent access to the MCU's serial communication abilities.
* This interface is intentionally designed to be as simple as possible, to allow * This interface is intentionally designed to be as simple as possible, to allow
* for easy implementation and maximum portability. In RIOT we only use the * for easy implementation and maximum portability. In RIOT we only use the
* common 8-N-1 format of the serial port (8 data bist, no parity bit, one stop bit). * common 8-N-1 format of the serial port (8 data bits, no parity bit, one stop bit).
* *
* The simple interface provides capabilities to initialize the serial communication * The simple interface provides capabilities to initialize the serial communication
* module, which automatically enables for receiving data, as well as writing data * module, which automatically enables for receiving data, as well as writing data
@ -27,9 +27,9 @@
* callback function that is executed in interrupt context when data is being received. * callback function that is executed in interrupt context when data is being received.
* The driver will then read the received data byte, call the registered callback * The driver will then read the received data byte, call the registered callback
* function and pass the received data to it via its argument. The interface enforces * function and pass the received data to it via its argument. The interface enforces
* the receiving to be impemented in an interrupt driven mode. Thus, you never now how * the receiving to be implemented in an interrupt driven mode. Thus, you never know how
* many bytes are going to be received and might want to handle that in your specific * many bytes are going to be received and might want to handle that in your specific
* callback function. The transmit function can be implemented in any way * callback function. The transmit function can be implemented in any way.
* *
* By default the @p UART_DEV(0) device of each board is initialized and mapped to STDIO * By default the @p UART_DEV(0) device of each board is initialized and mapped to STDIO
* in RIOT which is used for standard input/output functions like `printf()` or * in RIOT which is used for standard input/output functions like `printf()` or