FreeCalypso > hg > fc-magnetite
view src/cs/services/mks/mks_i.h @ 600:8f50b202e81f
board preprocessor conditionals: prep for more FC hw in the future
This change eliminates the CONFIG_TARGET_FCDEV3B preprocessor symbol and
all preprocessor conditionals throughout the code base that tested for it,
replacing them with CONFIG_TARGET_FCFAM or CONFIG_TARGET_FCMODEM. These
new symbols are specified as follows:
CONFIG_TARGET_FCFAM is intended to cover all hardware designs created by
Mother Mychaela under the FreeCalypso trademark. This family will include
modem products (repackagings of the FCDEV3B, possibly with RFFE or even
RF transceiver changes), and also my desired FreeCalypso handset product.
CONFIG_TARGET_FCMODEM is intended to cover all FreeCalypso modem products
(which will be firmware-compatible with the FCDEV3B if they use TI Rita
transceiver, or will require a different fw build if we switch to one of
Silabs Aero transceivers), but not the handset product. Right now this
CONFIG_TARGET_FCMODEM preprocessor symbol is used to conditionalize
everything dealing with MCSI.
At the present moment the future of FC hardware evolution is still unknown:
it is not known whether we will ever have any beyond-FCDEV3B hardware at all
(contingent on uncertain funding), and if we do produce further FC hardware
designs, it is not known whether they will retain the same FIC modem core
(triband), if we are going to have a quadband design that still retains the
classic Rita transceiver, or if we are going to switch to Silabs Aero II
or some other transceiver. If we produce a quadband modem that still uses
Rita, it will run exactly the same fw as the FCDEV3B thanks to the way we
define TSPACT signals for the RF_FAM=12 && CONFIG_TARGET_FCFAM combination,
and the current fcdev3b build target will be renamed to fcmodem. OTOH, if
that putative quadband modem will be Aero-based, then it will require a
different fw build target, the fcdev3b target will stay as it is, and the
two targets will both define CONFIG_TARGET_FCFAM and CONFIG_TARGET_FCMODEM,
but will have different RF_FAM numbers. But no matter which way we are
going to evolve, it is not right to have conditionals on CONFIG_TARGET_FCDEV3B
in places like ACI, and the present change clears the way for future
evolution.
author | Mychaela Falconia <falcon@freecalypso.org> |
---|---|
date | Mon, 01 Apr 2019 01:05:24 +0000 |
parents | 945cf7f506b2 |
children |
line wrap: on
line source
/** * @file mks_i.h * * Declaration of internal function for MKS service. * * @author Laurent Sollier (l-sollier@ti.com) * @version 0.1 */ /* * History: * * Date Author Modification * ---------------------------------------- * 11/19/2001 L Sollier Create * * * (C) Copyright 2001 by Texas Instruments Incorporated, All Rights Reserved */ #ifndef _MKS_I_H_ #define _MKS_I_H_ #include "mks/mks_api.h" #include "mks/mks_messages_i.h" /* Macro definition for sending trace */ #define MKS_SEND_TRACE(text,level) rvf_send_trace(text, sizeof(text)-1, NULL_PARAM, level, MKS_USE_ID ) #define MKS_SEND_TRACE_PARAM(text,param,level) rvf_send_trace(text, sizeof(text)-1, param, level, MKS_USE_ID ) /** * @name Internal functions * */ /*@{*/ /** * function: mks_add_key_sequence_i * * This function add a magic key sequence. * * @param infos_key_sequence_p Key sequence informations. * * @return * - RV_OK if operation is successfull * - RV_INTERNAL_ERR if operation cannot be completed * - RV_MEMORY_ERR if memory reach its size limit. */ T_RV_RET mks_add_key_sequence_i(T_MKS_INFOS_KEY_SEQUENCE_MSG* infos_key_sequence_p); /** * function: mks_remove_key_sequence_i * * This function remove a magic key sequence. * * @param remove_key_sequence_p Key sequence name. * * @return * - RV_OK */ T_RV_RET mks_remove_key_sequence_i(T_MKS_REMOVE_KEY_SEQUENCE_MSG* remove_key_sequence_p); /** * function: mks_check_key_sequence * * This function is called when a key is pressed and check if a magic * key sequence is completed. * * @param key_event_p Key event message. * */ void mks_check_key_sequence(T_KPD_KEY_EVENT_MSG* key_event_p); /** * function: mks_send_key_sequence_completed_msg * * Send a message that magic key sequence is completed. * * @param completion_level - MKS_SEQUENCE_COMPLETED: * Call subscriber when magic key sequence is completed, * - MKS_POST_SEQUENCE: * Call subscriber after magic key sequence is completed * @param key_id Virtual key Id pressed. * @param return_path Return path used to notify the subscriber. * @param name Name of the key sequence. */ void mks_send_key_sequence_completed_msg(UINT8 completion_level, T_KPD_VIRTUAL_KEY_ID key_id, T_RV_RETURN return_path, char* name); /** * function: mks_reset_sequence * * This function is called when timer 0 expire, to reset all * key sequence. * */ void mks_reset_sequence(void); /** * function: mks_initialize_swe * * This function is called at the initialization of the SWE. * It only subscribe to the keypad. * */ void mks_initialize_swe(void); /** * function: mks_stop_swe * * This function is called when SWE is stopped, * It unsubscribe from the keypad * */ void mks_stop_swe(void); /*@}*/ #endif /* #ifndef _MKS_I_H_ */