FreeCalypso > hg > fc-magnetite

view src/cs/drivers/drv_app/spi/spi_process.h @ 636:57e67ca2e1cb

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
pcmdata.c: default +CGMI to "FreeCalypso" and +CGMM to model The present change has no effect whatsoever on Falconia-made and Openmoko-made devices on which /pcm/CGMI and /pcm/CGMM files have been programmed in FFS with sensible ID strings by the respective factories, but what should AT+CGMI and AT+CGMM queries return when the device is a Huawei GTM900 or Tango modem that has been converted to FreeCalypso with a firmware change? Before the present change they would return compiled-in defaults of "<manufacturer>" and "<model>", respectively; with the present change the firmware will self-identify as "FreeCalypso GTM900-FC" or "FreeCalypso Tango" on the two respective targets. This firmware identification will become important if someone incorporates an FC-converted GTM900 or Tango modem into a ZeroPhone-style smartphone where some high-level software like ofono will be talking to the modem and will need to properly identify this modem as FreeCalypso, as opposed to some other AT command modem flavor with different quirks. In technical terms, the compiled-in default for the AT+CGMI query (which will always be overridden by the /pcm/CGMI file in FFS if one is present) is now "FreeCalypso" in all configs on all targets; the compiled-in default for the AT+CGMM query (likewise always overridden by /pcm/CGMM if present) is "GTM900-FC" if CONFIG_TARGET_GTM900 or "Tango" if CONFIG_TARGET_TANGO or the original default of "<model>" otherwise.
author Mychaela Falconia <falcon@freecalypso.org>
date Sun, 19 Jan 2020 20:14:58 +0000
parents 945cf7f506b2
children
line wrap: on
line source

/*****************************************************************************/
/*                                                                           */
/*  Name       spi_process.h                                                 */
/*                                                                           */
/*  Function    this file contains the spi_process function prototype,       */
/*				used to handle messages received in the SPI task mailbox.    */
/*                                                                           */
/*  Version    0.1                                                           */
/*                                                                           */
/*  Date       Modification                                                  */
/*  ------------------------------------                                     */
/*                                                                           */
/* Author      Candice Bazanegue                                             */
/*                                                                           */
/* (C) Copyright 2000 by Texas Instruments Incorporated, All Rights Reserved */
/*****************************************************************************/

#ifndef __SPI_PROCESS_H__
#define __SPI_PROCESS_H__


#define SPI_ABB_READ_EVT            1
#define SPI_ABB_WRITE_EVT           2
#define SPI_ABB_CONF_ADC_EVT        3
#define SPI_ABB_READ_ADC_EVT        4
#define ABB_EXT_IRQ_EVT             5

/* Prototypes */

/*******************************************************************************
** Function         spi_process
**
** Description     It is called by the spi task core to handle the access to                                         
**                 the ABB through the SPI in a non-preemptive way.        
**
*******************************************************************************/
UINT8 spi_process(T_RV_HDR * msg_ptr);

#endif /* __SPI_PROCESS_H__ */