view src/aci2/aci/dcm_state.h @ 624:012028896cfb

FFS dev.c, Leonardo target: Fujitsu MB84VF5F5F4J2 #if 0'ed out The FFS code we got from TI/Openmoko had a stanza for "Fujitsu MB84VF5F5F4J2 stacked device", using a fake device ID code that would need to be patched manually into cfgffs.c (suppressing and overriding autodetection) and using an FFS base address in the nCS2 bank, indicating that this FFS config was probably meant for the MCP version of Leonardo which allows for 16 MiB flash with a second bank on nCS2. We previously had this FFS config stanza conditionalized under CONFIG_TARGET_LEONARDO because the base address contained therein is invalid for other targets, but now that we actually have a Leonardo build target in FC Magnetite, I realize that the better approach is to #if 0 out this stanza altogether: it is already non-functional because it uses a fake device ID code, thus it is does not add support for more Leonardo board variants, instead it is just noise.
author Mychaela Falconia <falcon@freecalypso.org>
date Sun, 22 Dec 2019 21:24:29 +0000
parents 93999a60b835
children
line wrap: on
line source

/*
+-----------------------------------------------------------------------------
|  Project :  GSM-F&D (8411)
|  Modul   :  ACI
+-----------------------------------------------------------------------------
|  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.
+-----------------------------------------------------------------------------
|  Description :  DCM instance is a state machine with several possible states.
|                 Based on the current state, DCM handle different kind of messages/events.
|                 States are listed in the order they should normally be sequenced.
+-----------------------------------------------------------------------------
*/

#ifndef __DCMSTATE_H__
#define __DCMSTATE_H__

/**
 * DCM states.
 *
 * DCM instance is a state machine with several possible states.
 * Based on the current state, DCM handle different kind of messages/events.
 * States are listed in the order they should normally be sequenced.
 *
 * See the Readme file for a description of the state machine.
 */
typedef enum
{
	DCM_OFF,
	DCM_IDLE,
	DCM_ACTIVATING_CONN,
	DCM_CONN_ACTIVATED,
	DCM_CLOSING_CONN
} T_DCM_INTERNAL_STATE;


/**
 * DCM substates.
 *
 * DCM instance is a state machine with several possible states.
 * Substates are included in some states.
 */

typedef enum
{
  DCM_SUB_NO_ACTION = 0,                            /* ALL */
  DCM_SUB_WAIT_CGATT_CNF,                           /* DCM_ACTIVATING_CONN */
  DCM_SUB_WAIT_CGACT_CNF,                           /* DCM_ACTIVATING_CONN */
  DCM_SUB_WAIT_SATDN_CNF,                           /* DCM_ACTIVATING_CONN */
  DCM_SUB_WAIT_SATH_CNF,                            /* DCM_CLOSING_CONN    */
  DCM_SUB_WAIT_CGDEATT_CNF,                         /* DCM_CLOSING_CONN    */
  DCM_SUB_WAIT_CGDEACT_CNF                          /* DCM_CLOSING_CONN    */
} T_DCM_INTERNAL_SUBSTATE;


T_DCM_RET dcm_idle (T_DCM_HDR * msg_p);
T_DCM_RET dcm_activating_conn(T_DCM_HDR * msg_p);
T_DCM_RET dcm_conn_activated(T_DCM_HDR * msg_p);
T_DCM_RET dcm_closing_conn(T_DCM_HDR * msg_p );

T_DCM_RET dcm_new_state(U8 state, U8 substate);
T_DCM_RET dcm_save_state(void);
T_DCM_RET dcm_restore_state(void);
void dcm_dispay_state(U8 state, U8 substate);
void dcm_dispay_sub_state(U8 substate_1, U8 substate_2);


#endif