FreeCalypso > hg > fc-magnetite
view cdg-hybrid/sap/mmsms.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 : mmsms.pdf ;*** Creation : Wed Mar 11 09:58:22 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 : mmsms ;*** Document No. : 6147.106.97.102 ;*** Document Date : 2002-07-19 ;*** Document Status: BEING_PROCESSED ;*** Document Author: HM ;******************************************************************************** PRAGMA SRC_FILE_TIME "Thu Nov 29 09:47:08 2007" PRAGMA LAST_MODIFIED "2002-07-19" PRAGMA ID_AND_VERSION "6147.106.97.102" CONST MAX_SDU_LEN 1 ; maximum service data unit length VALTAB VAL_ti VAL 0 - 6 "ms originated transaction" VAL 8 - 14 "ms originated transaction" VAL 7 TI_RES_MO "reserved" VAL 15 TI_RES_MT "reserved" VAR cause "MM cause" S VAR l_buf "length in bits" S VAR o_buf "offset in bits" S VAR buf "bit buffer" B VAR ti "transaction identifier" B VAL @p_mmsms - VAL_ti@ VAR d1 "dummy, not used" B VAR d2 "dummy, not used" B COMP sdu "Service Data Unit" { l_buf ; length in bits o_buf ; offset in bits buf [MAX_SDU_LEN] ; bit buffer } ; MMSMS_ESTABLISH_REQ 0x80000009 ; MMSMS_RELEASE_REQ 0x80010009 ; MMSMS_DATA_REQ 0x80020009 ; MMSMS_DATA_IND 0x80004009 ; MMSMS_ERROR_IND 0x80014009 ; MMSMS_ESTABLISH_CNF 0x80024009 ; MMSMS_ESTABLISH_IND 0x80034009 ; MMSMS_RELEASE_IND 0x80044009 ; MMSMS_UNITDATA_IND 0x80054009 PRIM MMSMS_ESTABLISH_REQ 0x80000009 { ti ; transaction identifier } PRIM MMSMS_RELEASE_REQ 0x80010009 { ti ; transaction identifier } PRIM MMSMS_DATA_REQ 0x80020009 { d1 ; dummy d2 ; dummy sdu ; service data unit } PRIM MMSMS_DATA_IND 0x80004009 { d1 ; dummy d2 ; dummy sdu ; service data unit } PRIM MMSMS_ERROR_IND 0x80014009 { ti ; transaction identifier cause ; error cause } PRIM MMSMS_ESTABLISH_CNF 0x80024009 { ti ; transaction identifier } PRIM MMSMS_ESTABLISH_IND 0x80034009 { d1 ; dummy d2 ; dummy sdu ; service data unit } PRIM MMSMS_RELEASE_IND 0x80044009 { ti ; transaction identifier cause ; release cause } PRIM MMSMS_UNITDATA_IND 0x80054009 { d1 ; dummy d2 ; dummy sdu ; service data unit }