a046541623
The ftdi chip itself has a "get bitmode" command that doesn't actually return the current bitmode, just a snapshot of the gpio lines. The chip apparently has no way to provide the current bitmode. This implements the functionality at the driver level. The driver starts out assuming the chip is in UART mode (which it will be, coming out of reset) and keeps track of every successful set-bitmode operation so that it can always return the current mode with UFTDIIOC_GET_BITMODE. |
||
|---|---|---|
| .. | ||
| u3g.c | ||
| uark.c | ||
| ubsa.c | ||
| ubser.c | ||
| uchcom.c | ||
| ucycom.c | ||
| ufoma.c | ||
| uftdi_reg.h | ||
| uftdi.c | ||
| ugensa.c | ||
| uipaq.c | ||
| ulpt.c | ||
| umcs.c | ||
| umcs.h | ||
| umct.c | ||
| umodem.c | ||
| umoscom.c | ||
| uplcom.c | ||
| usb_serial.c | ||
| usb_serial.h | ||
| uslcom.c | ||
| uvisor.c | ||
| uvscom.c | ||