FreeCalypso > hg > fc-magnetite
view cdg-hybrid/sap/mdl.pdf @ 635:baa0a02bc676
niq32.c DTR handling restored for targets that have it
TI's original TCS211 fw treated GPIO 3 as the DTR input (wired so on C-Sample
and D-Sample boards, also compatible with Leonardo and FCDEV3B which have a
fixed pull-down resistor on this GPIO line), and the code in niq32.c called
UAF_DTRInterruptHandler() (implemented in uartfax.c) from the
IQ_KeypadGPIOHandler() function. But on Openmoko's GTA02 with their official
fw this GPIO is a floating input, all of the DTR handling code in uartfax.c
including the interrupt logic is still there, but the hobbled TCS211-20070608
semi-src delivery which OM got from TI contained a change in niq32.c (which
had been kept in FC until now) that removed the call to
UAF_DTRInterruptHandler() as part of those not-quite-understood "CC test"
hacks.
The present change fixes this bug at a long last: if we are building fw for a
target that has TI's "classic" DTR & DCD GPIO arrangement (dsample, fcmodem and
gtm900), we bring back all of TI's original code in both uartfax.c and niq32.c,
whereas if we are building fw for a target that does not use this classic GPIO
arrangement, the code in niq32.c goes back to what we got from OM and all
DTR & DCD code in uartfax.c is conditioned out. This change also removes the
very last remaining bit of "CC test" bogosity from our FreeCalypso code base.
| author | Mychaela Falconia <falcon@freecalypso.org> |
|---|---|
| date | Sun, 19 Jan 2020 01:41:35 +0000 |
| parents | e7a67accfad9 |
| children |
line wrap: on
line source
;******************************************************************************** ;*** File : mdl.pdf ;*** Creation : Wed Mar 11 09:58:17 CST 2009 ;*** XSLT Processor : Apache Software Foundation / http://xml.apache.org/xalan-j / supports XSLT-Ver: 1 ;*** Copyright : (c) Texas Instruments AG, Berlin Germany 2002 ;******************************************************************************** ;*** Document Type : Service Access Point Specification ;*** Document Name : mdl ;*** Document No. : 6147.111.97.101 ;*** Document Date : 2002-04-19 ;*** Document Status: BEING_PROCESSED ;*** Document Author: SBK ;******************************************************************************** PRAGMA SRC_FILE_TIME "Thu Nov 29 09:45:46 2007" PRAGMA LAST_MODIFIED "2002-04-19" PRAGMA ID_AND_VERSION "6147.111.97.101" VALTAB VAL_ch_type VAL 0 CH_TYPE_SACCH "SACCH" VAL 1 CH_TYPE_SDCCH "SDCCH" VAL 2 CH_TYPE_FACCH "FACCH" VAL 3 CH_TYPE_BCCH "BCCH" VAL 4 CH_TYPE_CCCH "CCCH" VAL 5 CH_TYPE_RACH "RACH" VAL 6 CH_TYPE_NBR_CEL_BCCH "Neighbour Cell BCCH" VALTAB VAL_sapi VAL 0 SAPI_0 "SAPI 0" VAL 3 SAPI_3 "SAPI 3" VALTAB VAL_cs VAL 0 CS_T200_EXP "T200 expired (N200 + 1 times)" VAL 1 CS_REEST_REQ "re-establishment request" VAL 2 CS_UNSOL_UA_RESP "unsolicited UA response" VAL 3 CS_UNSOL_DM_RESP "unsolicited DM response" VAL 4 CS_UNSOL_DM_RESP_MULT_FRM "unsolicited DM response, multiple frame established state" VAL 5 CS_UNSOL_SUP_RESP "unsolicited supervisory response" VAL 6 CS_SEQ_ERR "sequence error" VAL 7 CS_UFRM_W_INC_PARA "U frame with incorrect parameters" VAL 8 CS_SFRM_W_INC_PARA "S frame with incorrect parameters" VAL 9 CS_IFRM_W_INC_MBIT "I frame with incorrect use of M bit" VAL 10 CS_IFRM_W_INC_LEN "I frame with incorrect length" VAL 11 CS_FRM_NOT_IMPL "frame not implemented" VAL 12 CS_SABM_MULT_FRM "SABM command, multiple frame established state" VAL 13 CS_SABM_NO_INFO "SABM command with information field not allowed in this state" VAL 14 CS_NR_SEQ_ERR "sequence error, perform abnormal release" VAR ch_type "channel type" B VAL @p_mdl - VAL_ch_type@ VAR sapi "service access point identifier" B VAL @p_mdl - VAL_sapi@ VAR cs "error cause" B VAL @p_mdl - VAL_cs@ ; MDL_ERROR_IND 0x80000004 ; MDL_RELEASE_REQ 0x80004004 PRIM MDL_ERROR_IND 0x80000004 { ch_type ; channel type sapi ; service access point identifier cs ; error cause } PRIM MDL_RELEASE_REQ 0x80004004 { ch_type ; channel type sapi ; service access point identifier }