view src/cs/services/cst/cus_cst.h @ 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 945cf7f506b2
children
line wrap: on
line source

/*
+--------------------------------------------------------------------+
| PROJECT : XXX                        SOURCE : CUS_CST.H            |
| AUTHOR  : XXX                        VERSION: 1.0                  |
| CREATED : 01.02.99                   STATE  : code                 |
+--------------------------------------------------------------------+

   MODULE  : CUS_CST

   PURPOSE : Custom dependent definitions for the CST entity of the
             mobile station.

             Use this header for definitions to integrate the protocol
             stack entity CST in your target system.
*/

#ifndef CUS_CST_H
#define CUS_CST_H


/*==== CONSTANTS ==================================================*/
/*
 * TIMER_VALUES
 *
 * Description :  The constants define the timer values for the CST
 *                timer TXXX depending on the various channel types
 *                and service access point identifiers.
 *
 *                If your target system uses other units please
 *                change the values.
 */

/*
 * Unit is 1 ms 
 */
#define T_RX_VALUE              1000
#define TICS_PER_DECIHOURS      (1000*60*6)


/*
 * MAX_CST_TIMER
 *
 * Description :  The constant define the number of timer available
 *                in the timer pool.
 */
#define MAX_CST_TIMER 4

/*
 * VERSION
 *
 * Description :  The constants define the type and the value of a
 *                version identification. The version is part of the
 *                monitor struct.
 */
#define T_VERSION   char
#define VERSION_CST  "CST 1.0"

/*
 * VSI_CALLER
 *
 * Description :  For multithread applications the constant VSI_CALLER
 *                must be defined to identify the calling thread of the
 *                VSI-Interface. This must be done correponding to the
 *                type of T_VSI_CALLER in VSI.H. The comma symbol is
 *                neccessary because the vsi-functions are called
 *                like this vsi_xxx (VSI_CALLER par2, par3 ...)
 */

#ifdef OPTION_MULTITHREAD
#define VSI_CALLER cst_handle,
#define VSI_CALLER_SINGLE cst_handle
#else
#define VSI_CALLER
#define VSI_CALLER_SINGLE
#endif

#endif // CUS_CST_H