/* SPDX-License-Identifier: GPL-2.0+ */ /************************************************************************ * * IONSP.H Definitions for I/O Networks Serial Protocol * * Copyright (C) 1997-1998 Inside Out Networks, Inc. * * These definitions are used by both kernel-mode driver and the * peripheral firmware and MUST be kept in sync. * ************************************************************************/ /************************************************************************ The data to and from all ports on the peripheral is multiplexed through a single endpoint pair (EP1 since it supports 64-byte MaxPacketSize). Therefore, the data, commands, and status for each port must be preceded by a short header identifying the destination port. The header also identifies the bytes that follow as data or as command/status info. Header format, first byte: CLLLLPPP -------- | | |------ Port Number: 0-7 | |--------- Length: MSB bits of length |----------- Data/Command: 0 = Data header 1 = Cmd / Status (Cmd if OUT, Status if IN) This gives 2 possible formats: Data header: 0LLLLPPP LLLLLLLL ============ Where (LLLL,LLLLLLL) is 12-bit length of data that follows for port number (PPP). The length is 0-based (0-FFF means 0-4095 bytes). The ~4K limit allows the host driver (which deals in transfer requests instead of individual packets) to write a large chunk of data in a single request. Note, however, that the length must always be <= the current TxCredits for a given port due to buffering limitations on the peripheral. Cmd/Status header: 1ccccPPP [ CCCCCCCC, Params ]... ================== Where (cccc) or (cccc,CCCCCCCC) is the cmd or status identifier. Frequently-used values are encoded as (cccc), longer ones using (cccc,CCCCCCCC). Subsequent bytes are optional parameters and are specific to the cmd or status code. This may include a length for command and status codes that need variable-length parameters. In addition, we use another interrupt pipe (endpoint) which the host polls periodically for flow control information. The peripheral, when there has been a change, sends the following 10-byte packet: RRRRRRRRRRRRRRRR T0T0T0T0T0T0T0T0 T1T1T1T1T1T1T1T1 T2T2T2T2T2T2T2T2 T3T3T3T3T3T3T3T3 The first field is the 16-bit RxBytesAvail field, which indicates the number of bytes which may be read by the host from EP1. This is necessary: (a) because OSR2.1 has a bug which causes data loss if the peripheral returns fewer bytes than the host expects to read, and (b) because, on Microsoft platforms at least, an outstanding read posted on EP1 consumes about 35% of the CPU just polling the device for data. The next 4 fields are the 16-bit TxCredits for each port, which indicate how many bytes the host is allowed to send on EP1 for transmit to a given port. After an OPEN_PORT command, the Edgeport sends the initial TxCredits for that port. All 16-bit fields are sent in little-endian (Intel) format. ************************************************************************/ // // Define format of InterruptStatus packet returned from the // Interrupt pipe // struct int_status_pkt { … }; #define GET_INT_STATUS_SIZE(NumPorts) … // // Define cmd/status header values and macros to extract them. // // Data: 0LLLLPPP LLLLLLLL // Cmd/Stat: 1ccccPPP CCCCCCCC #define IOSP_DATA_HDR_SIZE … #define IOSP_CMD_HDR_SIZE … #define IOSP_MAX_DATA_LENGTH … #define IOSP_PORT_MASK … #define IOSP_CMD_STAT_BIT … #define IS_CMD_STAT_HDR(Byte1) … #define IS_DATA_HDR(Byte1) … #define IOSP_GET_HDR_PORT(Byte1) … #define IOSP_GET_HDR_DATA_LEN(Byte1, Byte2) … #define IOSP_GET_STATUS_CODE(Byte1) … // // These macros build the 1st and 2nd bytes for a data header // #define IOSP_BUILD_DATA_HDR1(Port, Len) … #define IOSP_BUILD_DATA_HDR2(Port, Len) … // // These macros build the 1st and 2nd bytes for a command header // #define IOSP_BUILD_CMD_HDR1(Port, Cmd) … //-------------------------------------------------------------- // // Define values for commands and command parameters // (sent from Host to Edgeport) // // 1ccccPPP P1P1P1P1 [ P2P2P2P2P2 ]... // // cccc: 00-07 2-byte commands. Write UART register 0-7 with // value in P1. See 16650.H for definitions of // UART register numbers and contents. // // 08-0B 3-byte commands: ==== P1 ==== ==== P2 ==== // 08 available for expansion // 09 1-param commands Command Code Param // 0A available for expansion // 0B available for expansion // // 0C-0D 4-byte commands. P1 = extended cmd and P2,P3 = params // Currently unimplemented. // // 0E-0F N-byte commands: P1 = num bytes after P1 (ie, TotalLen - 2) // P2 = extended cmd, P3..Pn = parameters. // Currently unimplemented. // #define IOSP_WRITE_UART_REG(n) … // Register numbers and contents // defined in 16554.H. // 0x08 // Available for expansion. #define IOSP_EXT_CMD … // P2 = Parameter // // Extended Command values, used with IOSP_EXT_CMD, may // or may not use parameter P2. // #define IOSP_CMD_OPEN_PORT … #define IOSP_CMD_CLOSE_PORT … #define IOSP_CMD_CHASE_PORT … #define IOSP_CMD_SET_RX_FLOW … #define IOSP_CMD_SET_TX_FLOW … #define IOSP_CMD_SET_XON_CHAR … #define IOSP_CMD_SET_XOFF_CHAR … #define IOSP_CMD_RX_CHECK_REQ … // the receive data stream (Parameter = 1 byte sequence number) #define IOSP_CMD_SET_BREAK … #define IOSP_CMD_CLEAR_BREAK … // // Define macros to simplify building of IOSP cmds // #define MAKE_CMD_WRITE_REG(ppBuf, pLen, Port, Reg, Val) … #define MAKE_CMD_EXT_CMD(ppBuf, pLen, Port, ExtCmd, Param) … //-------------------------------------------------------------- // // Define format of flow control commands // (sent from Host to Edgeport) // // 11001PPP FlowCmd FlowTypes // // Note that the 'FlowTypes' parameter is a bit mask; that is, // more than one flow control type can be active at the same time. // FlowTypes = 0 means 'no flow control'. // // // IOSP_CMD_SET_RX_FLOW // // Tells Edgeport how it can stop incoming UART data // // Example for Port 0 // P0 = 11001000 // P1 = IOSP_CMD_SET_RX_FLOW // P2 = Bit mask as follows: #define IOSP_RX_FLOW_RTS … #define IOSP_RX_FLOW_DTR … #define IOSP_RX_FLOW_DSR_SENSITIVITY … // Not currently implemented by firmware. #define IOSP_RX_FLOW_XON_XOFF … // Host must have previously programmed the // XON/XOFF values with SET_XON/SET_XOFF // before enabling this bit. // // IOSP_CMD_SET_TX_FLOW // // Tells Edgeport what signal(s) will stop it from transmitting UART data // // Example for Port 0 // P0 = 11001000 // P1 = IOSP_CMD_SET_TX_FLOW // P2 = Bit mask as follows: #define IOSP_TX_FLOW_CTS … #define IOSP_TX_FLOW_DSR … #define IOSP_TX_FLOW_DCD … #define IOSP_TX_FLOW_XON_XOFF … // Host must have previously programmed the // XON/XOFF values with SET_XON/SET_XOFF // before enabling this bit. #define IOSP_TX_FLOW_XOFF_CONTINUE … // sending XOFF in order to fix broken // systems that interpret the next // received char as XON. // If set, Edgeport continues Tx // normally after transmitting XOFF. // Not currently implemented by firmware. #define IOSP_TX_TOGGLE_RTS … // Request-to-Send signal: it is raised before // beginning transmission and lowered after // the last Tx char leaves the UART. // Not currently implemented by firmware. // // IOSP_CMD_SET_XON_CHAR // // Sets the character which Edgeport transmits/interprets as XON. // Note: This command MUST be sent before sending a SET_RX_FLOW or // SET_TX_FLOW with the XON_XOFF bit set. // // Example for Port 0 // P0 = 11001000 // P1 = IOSP_CMD_SET_XON_CHAR // P2 = 0x11 // // IOSP_CMD_SET_XOFF_CHAR // // Sets the character which Edgeport transmits/interprets as XOFF. // Note: This command must be sent before sending a SET_RX_FLOW or // SET_TX_FLOW with the XON_XOFF bit set. // // Example for Port 0 // P0 = 11001000 // P1 = IOSP_CMD_SET_XOFF_CHAR // P2 = 0x13 // // IOSP_CMD_RX_CHECK_REQ // // This command is used to assist in the implementation of the // IOCTL_SERIAL_PURGE Windows IOCTL. // This IOSP command tries to place a marker at the end of the RX // queue in the Edgeport. If the Edgeport RX queue is full then // the Check will be discarded. // It is up to the device driver to timeout waiting for the // RX_CHECK_RSP. If a RX_CHECK_RSP is received, the driver is // sure that all data has been received from the edgeport and // may now purge any internal RX buffers. // Note tat the sequence numbers may be used to detect lost // CHECK_REQs. // Example for Port 0 // P0 = 11001000 // P1 = IOSP_CMD_RX_CHECK_REQ // P2 = Sequence number // Response will be: // P1 = IOSP_EXT_RX_CHECK_RSP // P2 = Request Sequence number //-------------------------------------------------------------- // // Define values for status and status parameters // (received by Host from Edgeport) // // 1ssssPPP P1P1P1P1 [ P2P2P2P2P2 ]... // // ssss: 00-07 2-byte status. ssss identifies which UART register // has changed value, and the new value is in P1. // Note that the ssss values do not correspond to the // 16554 register numbers given in 16554.H. Instead, // see below for definitions of the ssss numbers // used in this status message. // // 08-0B 3-byte status: ==== P1 ==== ==== P2 ==== // 08 LSR_DATA: New LSR Errored byte // 09 1-param responses Response Code Param // 0A OPEN_RSP: InitialMsr TxBufferSize // 0B available for expansion // // 0C-0D 4-byte status. P1 = extended status code and P2,P3 = params // Not currently implemented. // // 0E-0F N-byte status: P1 = num bytes after P1 (ie, TotalLen - 2) // P2 = extended status, P3..Pn = parameters. // Not currently implemented. // /**************************************************** * SSSS values for 2-byte status messages (0-8) ****************************************************/ #define IOSP_STATUS_LSR … // Bits defined in 16554.H. Edgeport // returns this in order to report // line status errors (overrun, // parity, framing, break). This form // is used when a errored receive data // character was NOT present in the // UART when the LSR error occurred // (ie, when LSR bit 0 = 0). #define IOSP_STATUS_MSR … // Bits defined in 16554.H. Edgeport // returns this in order to report // changes in modem status lines // (CTS, DSR, RI, CD) // // 0x02 // Available for future expansion // 0x03 // // 0x04 // // 0x05 // // 0x06 // // 0x07 // /**************************************************** * SSSS values for 3-byte status messages (8-A) ****************************************************/ #define IOSP_STATUS_LSR_DATA … // P2 is errored character read from // RxFIFO after LSR reported an error. #define IOSP_EXT_STATUS … // Response Codes (P1 values) for 3-byte status messages #define IOSP_EXT_STATUS_CHASE_RSP … #define IOSP_EXT_STATUS_CHASE_PASS … #define IOSP_EXT_STATUS_CHASE_FAIL … // control from remote device). #define IOSP_EXT_STATUS_RX_CHECK_RSP … #define IOSP_STATUS_OPEN_RSP … // P1 is Initial MSR value // P2 is encoded TxBuffer Size: // TxBufferSize = (P2 + 1) * 64 // 0x0B // Available for future expansion #define GET_TX_BUFFER_SIZE(P2) … /**************************************************** * SSSS values for 4-byte status messages ****************************************************/ #define IOSP_EXT4_STATUS … // Params in P2, P3 // Currently unimplemented. // 0x0D // Currently unused, available. // // Macros to parse status messages // #define IOSP_GET_STATUS_LEN(code) … #define IOSP_STATUS_IS_2BYTE(code) … #define IOSP_STATUS_IS_3BYTE(code) … #define IOSP_STATUS_IS_4BYTE(code) …
Codebase Browser
linux