Lines Matching +full:modem +full:- +full:control +full:- +full:line +full:- +full:ports
1 /* SPDX-License-Identifier: GPL-2.0+ */
3 * Definitions for MCT (Magic Control Technology) USB-RS232 Converter Driver
7 * This driver is for the device MCT USB-RS232 Converter (25 pin, Model No.
8 * U232-P25) from Magic Control Technology Corp. (there is also a 9 pin
9 * Model No. U232-P9). See http://www.mct.com.tw/products/product_us232.html
11 * of this file. This device was used in the Dlink DSB-S25.
24 /* U232-P25, Sitecom */
27 /* DU-H3SP USB BAY hub */
28 #define MCT_U232_DU_H3SP_PID 0x0200 /* D-Link DU-H3SP USB BAY */
30 /* Belkin badge the MCT U232-P9 as the F5U109 */
40 /* Get Modem Status Register (MSR) */
44 /* Get Line Control Register (LCR) */
53 /* Set Line Control Register (LCR) */
57 /* Set Modem Control Register (MCR) */
63 * the MCT-supplied Windows driver whenever the baud rate changes.
69 * This USB device request code appears to control whether CTS is required
91 * Line Control Register (LCR)
110 * Modem Control Register (MCR)
117 * Modem Status Register (MSR)
130 * Line Status Register (LSR)
144 /* -----------------------------------------------------------------------------
149 * and the vendor-supplied device driver (version 2.3A) under Windows98. To
150 * identify the USB vendor-specific requests and to assign them to terminal
151 * settings (flow control, baud rate, etc.) the program "SerialSettings" from
153 * Win98 "HyperTerminal" and "usb-robot" on Linux for testing. The results and
163 * -------------------
174 * MCT-supplied Windows98 driver (U2SPORT.VXD, "File version: 1.21P.0104 for
176 * of the fact that the Belkin adapter and the 'Sitecom U232-P25' adapter
177 * use a baud-rate code instead of a conventional RS-232 baud rate divisor.
182 * Line Control Register (LCR)
183 * ---------------------------
194 * (IER) is disabled. Any access to these ports is now redirected to the
208 * Bit 2: Number of Stop Bits (STB). If set to "1" and using 5-bit data words,
210 * 6, 7 and 8-bit data words, 2 Stop Bits are transmitted and expected.
227 * Modem Control Register (MCR)
228 * ----------------------------
240 * Bit 4: Loop-Back Enable. When set to "1", the UART transmitter and receiver
242 * addition, the UART modem control outputs are connected to the UART
243 * modem control inputs. CTS is connected to RTS, DTR is connected to
247 * to tri-state (disable) the interrupt signal from the
251 * Bit 1: Request to Send (RTS). When set to "1", the output of the UART -RTS
252 * line is Low (Active).
254 * -DTR line is Low (Active).
260 * Modem Status Register (MSR)
261 * ---------------------------
270 * Bit 7: Data Carrier Detect (CD). Reflects the state of the DCD line on the
272 * Bit 6: Ring Indicator (RI). Reflects the state of the RI line on the UART.
273 * Bit 5: Data Set Ready (DSR). Reflects the state of the DSR line on the UART.
274 * Bit 4: Clear To Send (CTS). Reflects the state of the CTS line on the UART.
275 * Bit 3: Delta Data Carrier Detect (DDCD). Set to "1" if the -DCD line has
278 * Bit 2: Trailing Edge Ring Indicator (TERI). Set to "1" if the -RI line has
281 * Bit 1: Delta Data Set Ready (DDSR). Set to "1" if the -DSR line has changed
284 * Bit 0: Delta Clear To Send (DCTS). Set to "1" if the -CTS line has changed
289 * interrupt-in endpoint 0x83 to signal changes of modem status lines. The USB
293 * Line Status Register (LSR)
294 * --------------------------
313 * in the receive buffer. The newly-arrived word in the shift register
315 * is discarded and the newly- arrived word is put in the holding
323 * interrupt-in endpoint 0x83 to signal error conditions. Such errors have
328 * -------------------
337 * SniffUSB observations (Nov 2003): With the MCT-supplied Windows98 driver
345 * -------------------
354 * SniffUSB observations (Nov 2003): With the MCT-supplied Windows98 driver
358 * any) this message might serve, but without it, the USB/RS-232 adapter
359 * will not write to RS-232 devices which do not assert the 'CTS' signal.
362 * Flow control
363 * ------------
365 * SniffUSB observations: no flow control specific requests have been realized
366 * apart from DTR/RTS settings. Both signals are dropped for no flow control
367 * but asserted for hardware or software flow control.
371 * --------------
373 * SniffUSB observations: the bulk-out endpoint 0x1 and interrupt-in endpoint
374 * 0x81 is used to transmit and receive characters. The second interrupt-in
375 * endpoint 0x83 signals exceptional conditions like modem line changes and
380 * ------------------
386 * -----------------------------------------------------------------
389 * Product: USB-232 Interfact Controller
400 * Per-interface classes
444 * -----------------------------------------------------------------
447 * adaptor, which turns out to simply be a re-badged U232-P9. We
449 * which says "U232-P9" ;-)