FreeCalypso > hg > fc-magnetite
view src/cs/drivers/drv_app/kpd/kpd_physical_key_def.h @ 636:57e67ca2e1cb
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 | 92dbfa906f66 |
| children |
line wrap: on
line source
/** * @file kpd_physical_key_def.h * * Definition of physical key values available on keypad. * * @author Laurent Sollier (l-sollier@ti.com) * @version 0.1 */ /* * History: * * Date Author Modification * ---------------------------------------- * 11/02/2001 L Sollier Create * * * (C) Copyright 2001 by Texas Instruments Incorporated, All Rights Reserved */ /** Definition of the physical key ID. */ #ifndef _KPD_PHYSICAL_KEY_DEF_H_ #define _KPD_PHYSICAL_KEY_DEF_H_ #ifndef _WINDOWS #include "config/board.cfg" #include "config/fc-target.h" #endif /** Definition of the physical key ID. */ #define KPD_PKEY_NULL (-1) #define KPD_PKEY_0 (0) #define KPD_PKEY_1 (1) #define KPD_PKEY_2 (2) #define KPD_PKEY_3 (3) #define KPD_PKEY_4 (4) #define KPD_PKEY_5 (5) #define KPD_PKEY_6 (6) #define KPD_PKEY_7 (7) #define KPD_PKEY_8 (8) #define KPD_PKEY_9 (9) #define KPD_PKEY_UP (10) #define KPD_PKEY_DOWN (11) #define KPD_PKEY_SOFT_LEFT (12) #define KPD_PKEY_SOFT_RIGHT (13) #define KPD_PKEY_GREEN (14) #define KPD_PKEY_RED (15) #define KPD_PKEY_DIESE (16) #define KPD_PKEY_STAR (17) #if (BOARD == 40) || (BOARD == 41) || (BOARD == 42) || (BOARD == 43) || (defined _WINDOWS) #define KPD_PKEY_VOL_UP (18) #define KPD_PKEY_VOL_DOWN (19) #define KPD_PKEY_LEFT (20) #define KPD_PKEY_RIGHT (21) #define KPD_PKEY_NAV_CENTER (22) #define KPD_PKEY_REC (23) #endif #ifndef CONFIG_TARGET_COMPAL /* The PWR key is mapped on Analog Base Band, it's the SPI which inform the keypad that the PWR key is pressed, so the process for this key is different of the others, a subscriber can be notified only by a short press of the PWR key, even if this key has been set for a long press or repeat press with the function kpd_define_repeat_keys. The following #define allows to map any key with the PWR key. */ #define KPD_SHORT_PRESS_PWR_KEY KPD_PKEY_RED #else /* * On C1xx phones the red key grounds not only the PWON signal to the ABB, * but also row input line 4 of the regular keypad matrix. The latter * results in the regular keypad interrupt being generated, so we have * to handle it with the regular keys, not in TI's way. We disable the * KPD_SHORT_PRESS_PWR_KEY mechanism by defining it to a key that does not * exist on this keypad. */ #define KPD_SHORT_PRESS_PWR_KEY KPD_PKEY_REC #endif #endif /* #ifndef _KPD_PHYSICAL_KEY_DEF_H_ */