FreeCalypso > hg > fc-tourmaline
view src/g23m-fad/t30/cus_t30.h @ 223:740a8e8fc9d7
startup sync logic rework for the new PWON button boot scheme
Previously we added logic to the MMI task to hold off PEI init until
R2D is running, and then extended that condition to wait for FCHG
init too. However, the dependencies of MMI upon R2D and FCHG don't
start until mmiInit(), and that call is driven by Switch_ON() code,
hence the wait for R2D and FCHG init can be made in that code path
instead of the MMI task. Furthermore, with our new way of signaling
PWON button boot to MMI, we need a new wait to ensure that the MMI
task is up - previously this assurance was provided by the wait for
Kp pointers to be set.
Solution: revert our previous PEI init hold-off additions to MMI,
add a new flag indicating MMI task init done, and put the combined
wait for all needed conditions into our new PWON button boot code
in power.c.
author | Mychaela Falconia <falcon@freecalypso.org> |
---|---|
date | Tue, 27 Apr 2021 06:24:52 +0000 |
parents | fa8dc04885d8 |
children |
line wrap: on
line source
/* +----------------------------------------------------------------------------- | Project : GSM-F&D (8411) | Modul : CUS_T30 +----------------------------------------------------------------------------- | Copyright 2002 Texas Instruments Berlin, AG | All rights reserved. | | This file is confidential and a trade secret of Texas | Instruments Berlin, AG | The receipt of or possession of this file does not convey | any rights to reproduce or disclose its contents or to | manufacture, use, or sell anything it may describe, in | whole, or in part, without the specific written consent of | Texas Instruments Berlin, AG. +----------------------------------------------------------------------------- | Purpose : Custom dependent definitions for the | Protocol Stack Entity | T30 +----------------------------------------------------------------------------- */ #ifndef CUS_T30_H #define CUS_T30_H /*==== CONSTANTS ==================================================*/ /* * TIMER_VALUES * * Description : The constants define the timer values * for the T30 timers * If the target system uses other units please * change the values. */ #define T1_VALUE 35000 /* ms +/- 5000 ms */ #define T2_VALUE 6000 /* ms +/- 1000 ms */ #define T4_VALUE 3000 /* ms +/- 15% */ #define DCN_VALUE 500 #define MSG_VALUE 12500 #define FRAMES_400 1846 /* * TIMER IDENTIFIER * * Description : The constants define the identifier of the * timer resources of T30. The identifier is used * to reference a timer in a config primitive */ #define T1_NAME "T1" #define T2_NAME "T2" #define T4_NAME "T4" /* * MAX_T30_TIMER * * Description : The constant define the number of timer * available in the timer pool. This should be * the amount of timer which can be active * simultaneously. */ #define MAX_T30_TIMER 3 /* * 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_T30 "T30 2.0" /* NEW_FRAME only */ /* * 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_t30 (VSI_CALLER par2, par3 ...) */ #ifdef OPTION_MULTITHREAD #define VSI_CALLER t30_handle, #define VSI_CALLER_SINGLE t30_handle #else #define VSI_CALLER #define VSI_CALLER_SINGLE #endif #endif