FreeCalypso > hg > fc-magnetite
view src/cs/services/atp/atp_spp_api.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 Name : atp_spp_api.h * * Definitions for the interface between ATP and SPP SW entity * * (C) Texas Instruments, all rights reserved * * Version number : 0.1 Date : 16-Marsh-2000 * * History : 0.1 - Created by E. Baissus * * * Author : Eric Baissus : e-baissus@ti.com * * (C) Copyright 2000 by Texas Instruments Incorporated, All Rights Reserved ******************************************************************************/ #ifndef ATP_SPP_API_H #define ATP_SPP_API_H #include "rv/rv_general.h" #include "rvf/rvf_api.h" #include "l2cap_gen.h" #include "spp_general.h" #include "atp/atp_api.h" #define SPP_ALL_THE_EVENTS (0xFF) #define SPP_RX_HEAD_SIZE (SPP_TX_OFFSET) #define SPP_RX_TRAIL_SIZE (SPP_TX_LENGTH-(SPP_TX_OFFSET)) /* Types and definition used between ATP and SPP */ typedef enum { ATP_IS_SERVER, ATP_IS_CLIENT } T_ATP_IS_SERVER; /* Custom information used during a new open port request to spp */ typedef enum { ATP_PAYLOAD_LENGTH_RENEG_ON, ATP_PAYLOAD_LENGTH_RENEG_OFF } T_ATP_PAYLOAD_LENTH_RENEG_EN; typedef enum { ATP_AUTOMATIC_FLOW_CTRL_ON, ATP_AUTOMATIC_FLOW_CTRL_OFF } T_ATP_SPP_FLOW_CONTROL_MODE; typedef struct { T_ATP_CUSTOM_TYPE custom_type; T_BD_ADDR bd_addr; UINT16 server_channel; UINT16 max_payload_length; // max = 32 KBytes T_ATP_PAYLOAD_LENTH_RENEG_EN max_payload_length_reneg_en; T_RVF_MB_ID rx_mb; T_ATP_SPP_FLOW_CONTROL_MODE flow_ctrl_mode; T_ATP_IS_SERVER is_server; } T_ATP_CUSTOM_TO_SPP_INFO; /* Custom information used during a new open port response by spp */ typedef struct { T_ATP_CUSTOM_TYPE custom_type; T_BD_ADDR bd_addr; UINT16 max_payload_length; } T_ATP_CUSTOM_FROM_SPP_INFO; /* Custom Commands exchanged with SPP : see atp_send_cmd and ATP_CMD_RDY definitions*/ #define ATP_FROM_SPP_MAX_PAYLOAD_IND_CMD (0) // custom info is the payload value (UINT32) #define ATP_FROM_SPP_REG_SERVER_ERROR (1) // No custom info extern T_RV_RET atp_spp_init(T_RVF_ADDR_ID addr_id, T_RVF_MB_ID mb_id); extern T_RV_RET atp_spp_start(void); #endif
