FreeCalypso > hg > fc-tourmaline
view src/ui/mfw/mfw_bt_api.h @ 78:c632896652ba
mfw/ti1_key.c: properly initialize notified_keys array
The code in this ti1_key.c layer needs to call kpd_subscribe() and
kpd_define_key_notification() functions in order to register with the
KPD driver. The original code passed KPD_NB_PHYSICAL_KEYS in
nb_notified_keys - this constant is defined to 24 in kpd_cfg.h on all
platforms of interest to us - but it only filled the first 23 slots
in the notified_keys array, resulting in stack garbage being passed
to KPD API functions. The fix consists of initializing the last
missed array slot to KPD_KEY_RECORD, the key ID for the right side
button on the D-Sample handset.
On our current hw targets this "Record" button exists as the EXTRA
button on our Luna keypad board and as the camera button on the
Pirelli DP-L10. There is no support whatsoever for this button
in current BMI+MFW, we have no plans of doing anything with Pirelli's
camera button even if we do get our UI fw running on that phone,
and the Mother's dream of building our own FreeCalypso handset with
the same button arrangement as D-Sample (including the right side
button) is currently very nebulous - but let us nonetheless handle
the full set of buttons on the KPD to MFW interface, and let upper
layers weed out unsupported buttons.
author | Mychaela Falconia <falcon@freecalypso.org> |
---|---|
date | Sun, 25 Oct 2020 23:41:01 +0000 |
parents | 67bfe9f274f6 |
children |
line wrap: on
line source
/*******************************************************************************\ * * * TEXAS INSTRUMENTS ISRAEL PROPRIETARY AND CONFIDENTIAL INFORMATION * * * * LEGAL NOTE: THE TRANSFER OF THE TECHNICAL INFORMATION IS BEING MADE * * UNDER AN EXPORT LICENSE ISSUED BY THE ISRAELI GOVERNMENT AND THAT THE * * APPLICABLE EXPORT LICENSE DOES NOT ALLOW THE TECHNICAL INFORMATION TO * * BE USED FOR THE MODIFICATION OF THE BT ENCRYPTION OR THE DEVELOPMENT * * OF ANY NEW ENCRYPTION. THE INFORMATION CAN BE USED FOR THE INTERNAL * * DESIGN AND MANUFACTURE OF TI PRODUCTS THAT WILL CONTAIN THE BT IC. * * * \*******************************************************************************/ /*******************************************************************************\ * * FILE NAME: mfw_bt_api.h * * DESCRIPTION: This file defines the API between BMI (MMI) and BT applications * * AUTHOR: Uzi Doron * * Rev 0.2 * \*******************************************************************************/ #ifndef __MFW_BT_API #define __MFW_BT_API /**********************************************/ /* */ /* */ /* from here on - events from BMI to BT */ /* */ /* */ /**********************************************/ /*------------------------------------------------------------------------------- * BmiAvEvent type * * Defines Audio/Video events initiated by MMI side. * These events will be sent from BMI to BT * */ typedef enum { BMI_EVENT_USER_PLAY = 0x0001, /* user pressed Play on handset */ BMI_EVENT_USER_STOP, /* user pressed Stop on handset */ BMI_EVENT_USER_PAUSE, /* user pressed Pause on handset */ BMI_EVENT_USER_RESUME, /* user pressed Resume on handset */ BMI_EVENT_TRACK_START, /* a track is starting to play */ BMI_EVENT_TRACK_END /* a track ended playing */ }BmiAvEvent; /*------------------------------------------------------------------------------- * BmiEventCallback type * * A callback function, implemented at BT application, that will be called by * BMI to send events (of type BmiAvEvent) to BT. BMI will be able to send events * after BT has registered such an event callback function * * At BT side the function prototype will look like: * void BT_NotifyBmiEvent(BmiAvEvent event); * * NOTE: Since the callback is called from BMI context, the BT application should * not spend considerable time in this function. In case significant processing * time and/or asynchronous activity is required as a result of calling this function, * the BT application should switch to its own context to perform this activity. * It must not block the BMI application. */ typedef void (*BmiEventCallback)(BmiAvEvent event); /*------------------------------------------------------------------------------- * BMI_RegisterEventCallback() * * BT application will call this function to register an event callback * function with BMI. * * Parameters: * eventCallback [in] - pointer of the callback function. if this parameter is * NULL (0), BMI should not try to make callbacks. * * Returns: * void * */ void BMI_RegisterEventCallback(BmiEventCallback eventCallback); /**********************************************/ /* */ /* */ /* from here on - events from BT to BMI */ /* */ /* */ /**********************************************/ /*------------------------------------------------------------------------------- * BtAppEvent type * * Defines events initiated by BT side. * These events will be sent from BT to BMI */ typedef enum { BT_EVENT_USER_PLAY = 0x0044, /* user pressed Play on BT headset */ BT_EVENT_USER_STOP, /* user pressed Stop on BT headset */ BT_EVENT_USER_PAUSE /* user pressed Pause on BT headset */ }BtAppEvent; /*------------------------------------------------------------------------------- * BMI_NotifyBtEvent() * * Notify the BMI about an A/V event initiated at BT side. * This function is implemented in the BMI application and used by the BT application. * * NOTE: Since it is called from BT context, the BMI application should not spend * considerable time in this function. In case significant processing time and/or * asynchronous activity is required as a result of calling this function, the BMI * application should switch to its own context to perform this activity. It must * not block the BT application. * * Parameters: * event [in] - the reported event * * Returns: * void * */ void BMI_NotifyBtEvent(BtAppEvent event); /*------------------------------------------------------------------------------- * BMI_SwitchAudioToBtHeadset() * * Connect or disconnect the audio output to BT headset. * BT will call this function to let BMI know an A2DP link to a wireless headset * has been connected (and is in Open state), or disconnected. * * When link is connected, BMI will decide whether it wants to * direct the audio output to the wireless headset. * * Parameters: * connected [in] - whether the link has just been connected or disconnected: * TRUE - connected * FALSE - disconnected * * Returns: * when connect parameter is TRUE: * - return TRUE when BMI approves and will use A2DP headset as the audio output * - return FALSE when BMI rejects using A2DP headset as the audio output * * when connect parameter is FALSE - returned value is ignored * */ BOOL BMI_SwitchAudioToBtHeadset(BOOL connected); #endif /* __MFWE_BT_API */