uart: Move OUTPUT_PROTO format description to pd.py.

[libsigrokdecode.git] / decoders / uart / __init__.py

diff --git a/decoders/uart/__init__.py b/decoders/uart/__init__.py
index a8b73039916b505ad0e0b46aecb281943833d7e8..a0c9cef0a5cf89e8a00d7f38ba016b4f5a0bc2ac 100644 (file)
--- a/decoders/uart/__init__.py
+++ b/decoders/uart/__init__.py
@@ -38,25 +38,6 @@ the correct place where to probe). Once the data is in digital form and
 matches the "UART" description above, this protocol decoder can work with
 it though, no matter whether the source was on TTL UART levels, or RS232,
 or others.
-
-Protocol output format:
-
-UART packet:
-[<packet-type>, <rxtx>, <packet-data>]
-
-This is the list of <packet-type>s and their respective <packet-data>:
- - 'STARTBIT': The data is the (integer) value of the start bit (0/1).
- - 'DATA': The data is the (integer) value of the UART data. Valid values
-   range from 0 to 512 (as the data can be up to 9 bits in size).
- - 'PARITYBIT': The data is the (integer) value of the parity bit (0/1).
- - 'STOPBIT': The data is the (integer) value of the stop bit (0 or 1).
- - 'INVALID STARTBIT': The data is the (integer) value of the start bit (0/1).
- - 'INVALID STOPBIT': The data is the (integer) value of the stop bit (0/1).
- - 'PARITY ERROR': The data is a tuple with two entries. The first one is
-   the expected parity value, the second is the actual parity value.
- - TODO: Frame error?
-
-The <rxtx> field is 0 for RX packets, 1 for TX packets.
 '''
 
 from .pd import *