b19671e0d4
1. BLE Mesh Core * Provisioning: Node Role * PB-ADV and PB-GATT * Authentication OOB * Provisioning: Provisioner Role * PB-ADV and PB-GATT * Authentication OOB * Networking * Relay * Segmentation and Reassembly * Key Refresh * IV Update * Proxy Support * Multiple Client Models Run Simultaneously * Support multiple client models send packets to different nodes simultaneously * No blocking between client model and server * NVS Storage * Store BLE Mesh node related information in flash * Store BLE Mesh Provisioner related information in flash 2. BLE Mesh Models * Foundation Models * Configuration Server Model * Configuration Client Model * Health Server Model * Health Client Model * Generic * Generic OnOff Server * Generic OnOff Client * Generic Level Server * Generic Level Client * Generic Default Transition Time Server * Generic Default Transition Time Client * Generic Power OnOff Server * Generic Power OnOff Setup Server * Generic Power OnOff Client * Generic Power Level Server * Generic Power Level Setup Server * Generic Power Level Client * Generic Battery Server * Generic Battery Client * Generic Location Server * Generic Location Setup Server * Generic Location Client * Generic Admin Property Server * Generic Manufacturer Property Server * Generic User Property Server * Generic Client Property Server * Generic Property Client * Sensor Server Model * Sensor Server * Sensor Setup Server * Sensor Client * Time and Scenes * Time Server * Time Setup Server * Time Client * Scene Server * Scene Setup Server * Scene Client * Scheduler Server * Scheduler Setup Server * Scheduler Client * Lighting * Light Lightness Server * Light Lightness Setup Server * Light Lightness Client * Light CTL Server * Light CTL Setup Server * Light CTL Client * Light CTL Temperature Server * Light HSL Server * Light HSL Setup Server * Light HSL Client * Light HSL Hue Server * Light HSL Saturation Server * Light xyL Server * Light xyL Setup Server * Light xyL Client * Light LC Server * Light LC Setup Server * Light LC Client 3. BLE Mesh Applications * BLE Mesh Node * OnOff Client Example * OnOff Server Example * BLE Mesh Provisioner * Example * Fast Provisioning * Vendor Fast Prov Server Model * Vendor Fast Prov Client Model * Examples * Wi-Fi & BLE Mesh Coexistence * Example * BLE Mesh Console Commands * Examples
230 lines
8.3 KiB
C++
230 lines
8.3 KiB
C++
// Copyright 2015-2016 Espressif Systems (Shanghai) PTE LTD
|
|
//
|
|
// Licensed under the Apache License, Version 2.0 (the "License");
|
|
// you may not use this file except in compliance with the License.
|
|
// You may obtain a copy of the License at
|
|
|
|
// http://www.apache.org/licenses/LICENSE-2.0
|
|
//
|
|
// Unless required by applicable law or agreed to in writing, software
|
|
// distributed under the License is distributed on an "AS IS" BASIS,
|
|
// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
// See the License for the specific language governing permissions and
|
|
// limitations under the License.
|
|
#ifndef _IOT_BUTTON_H_
|
|
#define _IOT_BUTTON_H_
|
|
|
|
#ifdef __cplusplus
|
|
extern "C" {
|
|
#endif
|
|
|
|
#include "driver/gpio.h"
|
|
#include "freertos/portmacro.h"
|
|
typedef void (* button_cb)(void*);
|
|
typedef void* button_handle_t;
|
|
|
|
typedef enum {
|
|
BUTTON_ACTIVE_HIGH = 1, /*!<button active level: high level*/
|
|
BUTTON_ACTIVE_LOW = 0, /*!<button active level: low level*/
|
|
} button_active_t;
|
|
|
|
typedef enum {
|
|
BUTTON_CB_PUSH = 0, /*!<button push callback event */
|
|
BUTTON_CB_RELEASE, /*!<button release callback event */
|
|
BUTTON_CB_TAP, /*!<button quick tap callback event(will not trigger if there already is a "PRESS" event) */
|
|
BUTTON_CB_SERIAL, /*!<button serial trigger callback event */
|
|
} button_cb_type_t;
|
|
|
|
/**
|
|
* @brief Init button functions
|
|
*
|
|
* @param gpio_num GPIO index of the pin that the button uses
|
|
* @param active_level button hardware active level.
|
|
* For "BUTTON_ACTIVE_LOW" it means when the button pressed, the GPIO will read low level.
|
|
*
|
|
* @return A button_handle_t handle to the created button object, or NULL in case of error.
|
|
*/
|
|
button_handle_t iot_button_create(gpio_num_t gpio_num, button_active_t active_level);
|
|
|
|
/**
|
|
* @brief Register a callback function for a serial trigger event.
|
|
*
|
|
* @param btn_handle handle of the button object
|
|
* @start_after_sec define the time after which to start serial trigger action
|
|
* @interval_tick serial trigger interval
|
|
* @cb callback function for "TAP" action.
|
|
* @arg Parameter for callback function
|
|
* @note
|
|
* Button callback functions execute in the context of the timer service task.
|
|
* It is therefore essential that button callback functions never attempt to block.
|
|
* For example, a button callback function must not call vTaskDelay(), vTaskDelayUntil(),
|
|
* or specify a non zero block time when accessing a queue or a semaphore.
|
|
* @return
|
|
* - ESP_OK Success
|
|
* - ESP_FAIL Parameter error
|
|
*/
|
|
esp_err_t iot_button_set_serial_cb(button_handle_t btn_handle, uint32_t start_after_sec, TickType_t interval_tick, button_cb cb, void* arg);
|
|
|
|
/**
|
|
* @brief Register a callback function for a button_cb_type_t action.
|
|
*
|
|
* @param btn_handle handle of the button object
|
|
* @param type callback function type
|
|
* @param cb callback function for "TAP" action.
|
|
* @param arg Parameter for callback function
|
|
* @note
|
|
* Button callback functions execute in the context of the timer service task.
|
|
* It is therefore essential that button callback functions never attempt to block.
|
|
* For example, a button callback function must not call vTaskDelay(), vTaskDelayUntil(),
|
|
* or specify a non zero block time when accessing a queue or a semaphore.
|
|
* @return
|
|
* - ESP_OK Success
|
|
* - ESP_FAIL Parameter error
|
|
*/
|
|
esp_err_t iot_button_set_evt_cb(button_handle_t btn_handle, button_cb_type_t type, button_cb cb, void* arg);
|
|
|
|
/**
|
|
* @brief
|
|
*
|
|
* @param btn_handle handle of the button object
|
|
* @param press_sec the callback function would be called if you press the button for a specified period of time
|
|
* @param cb callback function for "PRESS" action.
|
|
* @param arg Parameter for callback function
|
|
*
|
|
* @note
|
|
* Button callback functions execute in the context of the timer service task.
|
|
* It is therefore essential that button callback functions never attempt to block.
|
|
* For example, a button callback function must not call vTaskDelay(), vTaskDelayUntil(),
|
|
* or specify a non zero block time when accessing a queue or a semaphore.
|
|
* @return
|
|
* - ESP_OK Success
|
|
* - ESP_FAIL Parameter error
|
|
*/
|
|
esp_err_t iot_button_add_custom_cb(button_handle_t btn_handle, uint32_t press_sec, button_cb cb, void* arg);
|
|
|
|
/**
|
|
* @brief Delete button object and free memory
|
|
* @param btn_handle handle of the button object
|
|
*
|
|
* @return
|
|
* - ESP_OK Success
|
|
* - ESP_FAIL Parameter error
|
|
*/
|
|
esp_err_t iot_button_delete(button_handle_t btn_handle);
|
|
|
|
/**
|
|
* @brief Remove callback
|
|
*
|
|
* @param btn_handle The handle of the button object
|
|
* @param type callback function event type
|
|
*
|
|
* @return
|
|
* - ESP_OK Success
|
|
*/
|
|
esp_err_t iot_button_rm_cb(button_handle_t btn_handle, button_cb_type_t type);
|
|
|
|
#ifdef __cplusplus
|
|
}
|
|
#endif
|
|
|
|
#ifdef __cplusplus
|
|
|
|
/**
|
|
* class of button
|
|
* simple usage:
|
|
* CButton* btn = new CButton(BUTTON_IO_NUM, BUTTON_ACTIVE_LEVEL, BUTTON_SERIAL_TRIGGER, 3);
|
|
* btn->add_cb(BUTTON_CB_PUSH, button_tap_cb, (void*) push, 50 / portTICK_PERIOD_MS);
|
|
* btn->add_custom_cb(5, button_press_5s_cb, NULL);
|
|
* ......
|
|
* delete btn;
|
|
*/
|
|
class CButton
|
|
{
|
|
private:
|
|
button_handle_t m_btn_handle;
|
|
|
|
/**
|
|
* prevent copy constructing
|
|
*/
|
|
CButton(const CButton&);
|
|
CButton& operator = (const CButton&);
|
|
public:
|
|
|
|
/**
|
|
* @brief constructor of CButton
|
|
*
|
|
* @param gpio_num GPIO index of the pin that the button uses
|
|
* @param active_level button hardware active level.
|
|
* For "BUTTON_ACTIVE_LOW" it means when the button pressed, the GPIO will read low level.
|
|
*/
|
|
CButton(gpio_num_t gpio_num, button_active_t active_level = BUTTON_ACTIVE_LOW);
|
|
|
|
~CButton();
|
|
|
|
/**
|
|
* @brief Register a callback function for a button_cb_type_t action.
|
|
*
|
|
* @param type callback function type
|
|
* @param cb callback function for "TAP" action.
|
|
* @param arg Parameter for callback function
|
|
* @note
|
|
* Button callback functions execute in the context of the timer service task.
|
|
* It is therefore essential that button callback functions never attempt to block.
|
|
* For example, a button callback function must not call vTaskDelay(), vTaskDelayUntil(),
|
|
* or specify a non zero block time when accessing a queue or a semaphore.
|
|
* @return
|
|
* - ESP_OK Success
|
|
* - ESP_FAIL Parameter error
|
|
*/
|
|
esp_err_t set_evt_cb(button_cb_type_t type, button_cb cb, void* arg);
|
|
|
|
/**
|
|
* @brief Register a callback function for a serial trigger event.
|
|
*
|
|
* @param btn_handle handle of the button object
|
|
* @start_after_sec define the time after which to start serial trigger action
|
|
* @interval_tick serial trigger interval
|
|
* @cb callback function for "TAP" action.
|
|
* @arg Parameter for callback function
|
|
* @note
|
|
* Button callback functions execute in the context of the timer service task.
|
|
* It is therefore essential that button callback functions never attempt to block.
|
|
* For example, a button callback function must not call vTaskDelay(), vTaskDelayUntil(),
|
|
* or specify a non zero block time when accessing a queue or a semaphore.
|
|
* @return
|
|
* - ESP_OK Success
|
|
* - ESP_FAIL Parameter error
|
|
*/
|
|
esp_err_t set_serial_cb(button_cb cb, void* arg, TickType_t interval_tick, uint32_t start_after_sec);
|
|
|
|
/**
|
|
* @brief
|
|
*
|
|
* @param press_sec the callback function would be called if you press the button for a specified period of time
|
|
* @param cb callback function for "PRESS" action.
|
|
* @param arg Parameter for callback function
|
|
*
|
|
* @note
|
|
* Button callback functions execute in the context of the timer service task.
|
|
* It is therefore essential that button callback functions never attempt to block.
|
|
* For example, a button callback function must not call vTaskDelay(), vTaskDelayUntil(),
|
|
* or specify a non zero block time when accessing a queue or a semaphore.
|
|
* @return
|
|
* - ESP_OK Success
|
|
* - ESP_FAIL Parameter error
|
|
*/
|
|
esp_err_t add_custom_cb(uint32_t press_sec, button_cb cb, void* arg);
|
|
|
|
/**
|
|
* @brief Remove callback
|
|
*
|
|
* @param type callback function event type
|
|
*
|
|
* @return
|
|
* - ESP_OK Success
|
|
*/
|
|
esp_err_t rm_cb(button_cb_type_t type);
|
|
};
|
|
#endif
|
|
|
|
#endif
|