espressif/esp-idf
1
0
Fork 1
mirror of https://github.com/espressif/esp-idf.git synced 2025-11-04 09:01:40 +01:00
Code Issues Packages Projects Releases Wiki Activity
Files
48837334725f941725b01e2005c4c23b150bb9b0
esp-idf/components/driver/gpio.c

680 lines
22 KiB
C
Raw Normal View History

refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
// Copyright 2015-2019 Espressif Systems (Shanghai) PTE LTD
Convert Windows -> Unix line ends in gpio.c
2016-10-08 14:12:55 +08:00
//
// 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
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
//
Convert Windows -> Unix line ends in gpio.c
2016-10-08 14:12:55 +08:00
// 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.
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
Convert Windows -> Unix line ends in gpio.c
2016-10-08 14:12:55 +08:00
#include <esp_types.h>
#include "esp_err.h"
#include "freertos/FreeRTOS.h"
#include "freertos/xtensa_api.h"
#include "driver/gpio.h"
driver: add rtc module and bugfix gpio32 gpio33 feature(rtc_module):add rtc module 1. add rtc io control API (pull,output and input) 2. add touch pad API (touch pad read and interrupt) 3. add adc1 API (the max width is 12 Bits and support attenuation) 4. add hall sensor API (support hall sensor read ) 5. add dac API (the width is 8 Bits) bugfix(gpio):gpio32 and gpio33 can not output and input the gpio32 and gpio33 is initialize by librtc.a,and gpio_config not initialize the gpio as digital gpio.they can not output and input,when users use gpio32 or gpio33.And there are some problems about others driver ,when they use gpio32 or gpio33 as matrix.
2016-12-07 14:18:10 +08:00
#include "driver/rtc_io.h"
Convert Windows -> Unix line ends in gpio.c
2016-10-08 14:12:55 +08:00
#include "soc/soc.h"
can build and run hello-world app
2019-06-10 12:08:08 +08:00
#include "soc/periph_defs.h"
ipc: prevent code getting pulled in for unicore configuration
2019-08-15 12:35:59 +05:30
#if !CONFIG_FREERTOS_UNICORE
bugfix(GPIO): Fixed the bug that GPIO enables interrupts on one core, but registers interrupt service routines on another core closes https://github.com/espressif/esp-idf/issues/2808 closes https://github.com/espressif/esp-idf/issues/2845
2019-07-18 11:34:49 +08:00
#include "esp_ipc.h"
ipc: prevent code getting pulled in for unicore configuration
2019-08-15 12:35:59 +05:30
#endif
Convert Windows -> Unix line ends in gpio.c
2016-10-08 14:12:55 +08:00
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
#include "soc/gpio_caps.h"
#include "soc/gpio_periph.h"
#include "esp_log.h"
#include "hal/gpio_hal.h"
static const char *GPIO_TAG = "gpio";
drivers: remove file paths from log statements Function name and error string are usually sufficient to find the place which has triggered an error. __FILE__ macro generates a string which has absolute file name (with our build system), so there is a lot of long strings present in the program because of that. Fixes https://github.com/espressif/esp-idf/issues/126
2016-12-07 12:01:30 +08:00
#define GPIO_CHECK(a, str, ret_val) \
if (!(a)) { \
ESP_LOGE(GPIO_TAG,"%s(%d): %s", __FUNCTION__, __LINE__, str); \
return (ret_val); \
}
bugfix(GPIO): Fixed the bug that GPIO enables interrupts on one core, but registers interrupt service routines on another core closes https://github.com/espressif/esp-idf/issues/2808 closes https://github.com/espressif/esp-idf/issues/2845
2019-07-18 11:34:49 +08:00
#define GPIO_ISR_CORE_ID_UNINIT (3)
Convert Windows -> Unix line ends in gpio.c
2016-10-08 14:12:55 +08:00
gpio_driver: add per-pin interrupt handlers 1. add ISR handler apis so that users of different layers can hook their own isr handler on different GPIO. Audio project has different software layers, they need different gpio isr handler for layer instead of processing all GPIO interrupts in one handler. If this kind of calling a handler from isr is not proper, please kindly point out. 2. add gpio example code. 3. improve gpio.rst 4. add readme for gpio example Squashed commits: [278e50f] update: GPIO 1. coding style, add a space between conditional or loop keyword and an opening paren. 2. modify some return value and doc 3. use printf in example code Squashed commits: [efb23bb] minor change of comment
2016-12-24 20:45:57 +08:00
typedef struct {
gpio_isr_t fn; /*!< isr function */
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
void *args; /*!< isr function args */
gpio_driver: add per-pin interrupt handlers 1. add ISR handler apis so that users of different layers can hook their own isr handler on different GPIO. Audio project has different software layers, they need different gpio isr handler for layer instead of processing all GPIO interrupts in one handler. If this kind of calling a handler from isr is not proper, please kindly point out. 2. add gpio example code. 3. improve gpio.rst 4. add readme for gpio example Squashed commits: [278e50f] update: GPIO 1. coding style, add a space between conditional or loop keyword and an opening paren. 2. modify some return value and doc 3. use printf in example code Squashed commits: [efb23bb] minor change of comment
2016-12-24 20:45:57 +08:00
} gpio_isr_func_t;
bugfix(GPIO): Fixed the bug that GPIO enables interrupts on one core, but registers interrupt service routines on another core closes https://github.com/espressif/esp-idf/issues/2808 closes https://github.com/espressif/esp-idf/issues/2845
2019-07-18 11:34:49 +08:00
// Used by the IPC call to register the interrupt service routine.
typedef struct {
int source; /*!< ISR source */
int intr_alloc_flags; /*!< ISR alloc flag */
void (*fn)(void*); /*!< ISR function */
void *arg; /*!< ISR function args*/
void *handle; /*!< ISR handle */
esp_err_t ret;
} gpio_isr_alloc_t;
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
typedef struct {
gpio_hal_context_t *gpio_hal;
portMUX_TYPE gpio_spinlock;
uint32_t isr_core_id;
gpio_isr_func_t *gpio_isr_func;
gpio_isr_handle_t gpio_isr_handle;
} gpio_context_t;
static gpio_hal_context_t _gpio_hal = {
.dev = GPIO_HAL_GET_HW(GPIO_PORT_0)
};
static gpio_context_t gpio_context = {
.gpio_hal = &_gpio_hal,
.gpio_spinlock = portMUX_INITIALIZER_UNLOCKED,
.isr_core_id = GPIO_ISR_CORE_ID_UNINIT,
.gpio_isr_func = NULL,
};
gpio_driver: add per-pin interrupt handlers 1. add ISR handler apis so that users of different layers can hook their own isr handler on different GPIO. Audio project has different software layers, they need different gpio isr handler for layer instead of processing all GPIO interrupts in one handler. If this kind of calling a handler from isr is not proper, please kindly point out. 2. add gpio example code. 3. improve gpio.rst 4. add readme for gpio example Squashed commits: [278e50f] update: GPIO 1. coding style, add a space between conditional or loop keyword and an opening paren. 2. modify some return value and doc 3. use printf in example code Squashed commits: [efb23bb] minor change of comment
2016-12-24 20:45:57 +08:00
esp_err_t gpio_pullup_en(gpio_num_t gpio_num)
{
Amend gpio driver to work around SoC bug with some pullups/pulldowns in the GPIO peripheral; mark existing function that does not always work as deprecated
2016-11-15 10:29:52 +08:00
GPIO_CHECK(GPIO_IS_VALID_GPIO(gpio_num), "GPIO number error", ESP_ERR_INVALID_ARG);
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
bugfix(gpio):fix esp32 s2 rtc io issue * Modify the function implementation of ESP32-S2 RTC GPIO On ESP32 those PADs which have RTC functions must set pullup/down/capability via RTC register. On ESP32-S2, Digital IOs have their own registers to control pullup/down/capability, independent with RTC registers. * Add ESP32-S2 support of unit test * Modify the pull-up test of unit test * Modify the interrupt test of unit test * Modify input and output mode test of unit test
2019-11-26 20:00:24 +08:00
if (!rtc_gpio_is_valid_gpio(gpio_num) || GPIO_SUPPORTS_RTC_INDEPENDENT) {
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
portENTER_CRITICAL(&gpio_context.gpio_spinlock);
gpio_hal_pullup_en(gpio_context.gpio_hal, gpio_num);
portEXIT_CRITICAL(&gpio_context.gpio_spinlock);
bugfix(gpio):fix esp32 s2 rtc io issue * Modify the function implementation of ESP32-S2 RTC GPIO On ESP32 those PADs which have RTC functions must set pullup/down/capability via RTC register. On ESP32-S2, Digital IOs have their own registers to control pullup/down/capability, independent with RTC registers. * Add ESP32-S2 support of unit test * Modify the pull-up test of unit test * Modify the interrupt test of unit test * Modify input and output mode test of unit test
2019-11-26 20:00:24 +08:00
} else {
rtc_gpio_pullup_en(gpio_num);
driver: add rtc module and bugfix gpio32 gpio33 feature(rtc_module):add rtc module 1. add rtc io control API (pull,output and input) 2. add touch pad API (touch pad read and interrupt) 3. add adc1 API (the max width is 12 Bits and support attenuation) 4. add hall sensor API (support hall sensor read ) 5. add dac API (the width is 8 Bits) bugfix(gpio):gpio32 and gpio33 can not output and input the gpio32 and gpio33 is initialize by librtc.a,and gpio_config not initialize the gpio as digital gpio.they can not output and input,when users use gpio32 or gpio33.And there are some problems about others driver ,when they use gpio32 or gpio33 as matrix.
2016-12-07 14:18:10 +08:00
}
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
Amend gpio driver to work around SoC bug with some pullups/pulldowns in the GPIO peripheral; mark existing function that does not always work as deprecated
2016-11-15 10:29:52 +08:00
return ESP_OK;
}
gpio_driver: add per-pin interrupt handlers 1. add ISR handler apis so that users of different layers can hook their own isr handler on different GPIO. Audio project has different software layers, they need different gpio isr handler for layer instead of processing all GPIO interrupts in one handler. If this kind of calling a handler from isr is not proper, please kindly point out. 2. add gpio example code. 3. improve gpio.rst 4. add readme for gpio example Squashed commits: [278e50f] update: GPIO 1. coding style, add a space between conditional or loop keyword and an opening paren. 2. modify some return value and doc 3. use printf in example code Squashed commits: [efb23bb] minor change of comment
2016-12-24 20:45:57 +08:00
esp_err_t gpio_pullup_dis(gpio_num_t gpio_num)
{
Amend gpio driver to work around SoC bug with some pullups/pulldowns in the GPIO peripheral; mark existing function that does not always work as deprecated
2016-11-15 10:29:52 +08:00
GPIO_CHECK(GPIO_IS_VALID_GPIO(gpio_num), "GPIO number error", ESP_ERR_INVALID_ARG);
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
bugfix(gpio):fix esp32 s2 rtc io issue * Modify the function implementation of ESP32-S2 RTC GPIO On ESP32 those PADs which have RTC functions must set pullup/down/capability via RTC register. On ESP32-S2, Digital IOs have their own registers to control pullup/down/capability, independent with RTC registers. * Add ESP32-S2 support of unit test * Modify the pull-up test of unit test * Modify the interrupt test of unit test * Modify input and output mode test of unit test
2019-11-26 20:00:24 +08:00
if (!rtc_gpio_is_valid_gpio(gpio_num) || GPIO_SUPPORTS_RTC_INDEPENDENT) {
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
portENTER_CRITICAL(&gpio_context.gpio_spinlock);
gpio_hal_pullup_dis(gpio_context.gpio_hal, gpio_num);
portEXIT_CRITICAL(&gpio_context.gpio_spinlock);
bugfix(gpio):fix esp32 s2 rtc io issue * Modify the function implementation of ESP32-S2 RTC GPIO On ESP32 those PADs which have RTC functions must set pullup/down/capability via RTC register. On ESP32-S2, Digital IOs have their own registers to control pullup/down/capability, independent with RTC registers. * Add ESP32-S2 support of unit test * Modify the pull-up test of unit test * Modify the interrupt test of unit test * Modify input and output mode test of unit test
2019-11-26 20:00:24 +08:00
} else {
rtc_gpio_pullup_dis(gpio_num);
driver: add rtc module and bugfix gpio32 gpio33 feature(rtc_module):add rtc module 1. add rtc io control API (pull,output and input) 2. add touch pad API (touch pad read and interrupt) 3. add adc1 API (the max width is 12 Bits and support attenuation) 4. add hall sensor API (support hall sensor read ) 5. add dac API (the width is 8 Bits) bugfix(gpio):gpio32 and gpio33 can not output and input the gpio32 and gpio33 is initialize by librtc.a,and gpio_config not initialize the gpio as digital gpio.they can not output and input,when users use gpio32 or gpio33.And there are some problems about others driver ,when they use gpio32 or gpio33 as matrix.
2016-12-07 14:18:10 +08:00
}
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
Amend gpio driver to work around SoC bug with some pullups/pulldowns in the GPIO peripheral; mark existing function that does not always work as deprecated
2016-11-15 10:29:52 +08:00
return ESP_OK;
}
gpio_driver: add per-pin interrupt handlers 1. add ISR handler apis so that users of different layers can hook their own isr handler on different GPIO. Audio project has different software layers, they need different gpio isr handler for layer instead of processing all GPIO interrupts in one handler. If this kind of calling a handler from isr is not proper, please kindly point out. 2. add gpio example code. 3. improve gpio.rst 4. add readme for gpio example Squashed commits: [278e50f] update: GPIO 1. coding style, add a space between conditional or loop keyword and an opening paren. 2. modify some return value and doc 3. use printf in example code Squashed commits: [efb23bb] minor change of comment
2016-12-24 20:45:57 +08:00
esp_err_t gpio_pulldown_en(gpio_num_t gpio_num)
{
Amend gpio driver to work around SoC bug with some pullups/pulldowns in the GPIO peripheral; mark existing function that does not always work as deprecated
2016-11-15 10:29:52 +08:00
GPIO_CHECK(GPIO_IS_VALID_GPIO(gpio_num), "GPIO number error", ESP_ERR_INVALID_ARG);
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
bugfix(gpio):fix esp32 s2 rtc io issue * Modify the function implementation of ESP32-S2 RTC GPIO On ESP32 those PADs which have RTC functions must set pullup/down/capability via RTC register. On ESP32-S2, Digital IOs have their own registers to control pullup/down/capability, independent with RTC registers. * Add ESP32-S2 support of unit test * Modify the pull-up test of unit test * Modify the interrupt test of unit test * Modify input and output mode test of unit test
2019-11-26 20:00:24 +08:00
if (!rtc_gpio_is_valid_gpio(gpio_num) || GPIO_SUPPORTS_RTC_INDEPENDENT) {
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
portENTER_CRITICAL(&gpio_context.gpio_spinlock);
gpio_hal_pulldown_en(gpio_context.gpio_hal, gpio_num);
portEXIT_CRITICAL(&gpio_context.gpio_spinlock);
bugfix(gpio):fix esp32 s2 rtc io issue * Modify the function implementation of ESP32-S2 RTC GPIO On ESP32 those PADs which have RTC functions must set pullup/down/capability via RTC register. On ESP32-S2, Digital IOs have their own registers to control pullup/down/capability, independent with RTC registers. * Add ESP32-S2 support of unit test * Modify the pull-up test of unit test * Modify the interrupt test of unit test * Modify input and output mode test of unit test
2019-11-26 20:00:24 +08:00
} else {
rtc_gpio_pulldown_en(gpio_num);
driver: add rtc module and bugfix gpio32 gpio33 feature(rtc_module):add rtc module 1. add rtc io control API (pull,output and input) 2. add touch pad API (touch pad read and interrupt) 3. add adc1 API (the max width is 12 Bits and support attenuation) 4. add hall sensor API (support hall sensor read ) 5. add dac API (the width is 8 Bits) bugfix(gpio):gpio32 and gpio33 can not output and input the gpio32 and gpio33 is initialize by librtc.a,and gpio_config not initialize the gpio as digital gpio.they can not output and input,when users use gpio32 or gpio33.And there are some problems about others driver ,when they use gpio32 or gpio33 as matrix.
2016-12-07 14:18:10 +08:00
}
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
Amend gpio driver to work around SoC bug with some pullups/pulldowns in the GPIO peripheral; mark existing function that does not always work as deprecated
2016-11-15 10:29:52 +08:00
return ESP_OK;
}
gpio_driver: add per-pin interrupt handlers 1. add ISR handler apis so that users of different layers can hook their own isr handler on different GPIO. Audio project has different software layers, they need different gpio isr handler for layer instead of processing all GPIO interrupts in one handler. If this kind of calling a handler from isr is not proper, please kindly point out. 2. add gpio example code. 3. improve gpio.rst 4. add readme for gpio example Squashed commits: [278e50f] update: GPIO 1. coding style, add a space between conditional or loop keyword and an opening paren. 2. modify some return value and doc 3. use printf in example code Squashed commits: [efb23bb] minor change of comment
2016-12-24 20:45:57 +08:00
esp_err_t gpio_pulldown_dis(gpio_num_t gpio_num)
{
Amend gpio driver to work around SoC bug with some pullups/pulldowns in the GPIO peripheral; mark existing function that does not always work as deprecated
2016-11-15 10:29:52 +08:00
GPIO_CHECK(GPIO_IS_VALID_GPIO(gpio_num), "GPIO number error", ESP_ERR_INVALID_ARG);
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
bugfix(gpio):fix esp32 s2 rtc io issue * Modify the function implementation of ESP32-S2 RTC GPIO On ESP32 those PADs which have RTC functions must set pullup/down/capability via RTC register. On ESP32-S2, Digital IOs have their own registers to control pullup/down/capability, independent with RTC registers. * Add ESP32-S2 support of unit test * Modify the pull-up test of unit test * Modify the interrupt test of unit test * Modify input and output mode test of unit test
2019-11-26 20:00:24 +08:00
if (!rtc_gpio_is_valid_gpio(gpio_num) || GPIO_SUPPORTS_RTC_INDEPENDENT) {
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
portENTER_CRITICAL(&gpio_context.gpio_spinlock);
gpio_hal_pulldown_dis(gpio_context.gpio_hal, gpio_num);
portEXIT_CRITICAL(&gpio_context.gpio_spinlock);
bugfix(gpio):fix esp32 s2 rtc io issue * Modify the function implementation of ESP32-S2 RTC GPIO On ESP32 those PADs which have RTC functions must set pullup/down/capability via RTC register. On ESP32-S2, Digital IOs have their own registers to control pullup/down/capability, independent with RTC registers. * Add ESP32-S2 support of unit test * Modify the pull-up test of unit test * Modify the interrupt test of unit test * Modify input and output mode test of unit test
2019-11-26 20:00:24 +08:00
} else {
rtc_gpio_pulldown_dis(gpio_num);
driver: add rtc module and bugfix gpio32 gpio33 feature(rtc_module):add rtc module 1. add rtc io control API (pull,output and input) 2. add touch pad API (touch pad read and interrupt) 3. add adc1 API (the max width is 12 Bits and support attenuation) 4. add hall sensor API (support hall sensor read ) 5. add dac API (the width is 8 Bits) bugfix(gpio):gpio32 and gpio33 can not output and input the gpio32 and gpio33 is initialize by librtc.a,and gpio_config not initialize the gpio as digital gpio.they can not output and input,when users use gpio32 or gpio33.And there are some problems about others driver ,when they use gpio32 or gpio33 as matrix.
2016-12-07 14:18:10 +08:00
}
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
Amend gpio driver to work around SoC bug with some pullups/pulldowns in the GPIO peripheral; mark existing function that does not always work as deprecated
2016-11-15 10:29:52 +08:00
return ESP_OK;
}
gpio_driver: add per-pin interrupt handlers 1. add ISR handler apis so that users of different layers can hook their own isr handler on different GPIO. Audio project has different software layers, they need different gpio isr handler for layer instead of processing all GPIO interrupts in one handler. If this kind of calling a handler from isr is not proper, please kindly point out. 2. add gpio example code. 3. improve gpio.rst 4. add readme for gpio example Squashed commits: [278e50f] update: GPIO 1. coding style, add a space between conditional or loop keyword and an opening paren. 2. modify some return value and doc 3. use printf in example code Squashed commits: [efb23bb] minor change of comment
2016-12-24 20:45:57 +08:00
Convert Windows -> Unix line ends in gpio.c
2016-10-08 14:12:55 +08:00
esp_err_t gpio_set_intr_type(gpio_num_t gpio_num, gpio_int_type_t intr_type)
{
Minor changes for driver 1. remove "\n" when calling ESP_LOGX APIs. 2. modify uart_event_t for uart rx data. 3. use MICRO for uart inverse value 4. add uart_tx_data_t for internal tx function.
2016-11-07 14:16:52 +08:00
GPIO_CHECK(GPIO_IS_VALID_GPIO(gpio_num), "GPIO number error", ESP_ERR_INVALID_ARG);
GPIO_CHECK(intr_type < GPIO_INTR_MAX, "GPIO interrupt type error", ESP_ERR_INVALID_ARG);
Convert Windows -> Unix line ends in gpio.c
2016-10-08 14:12:55 +08:00
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
portENTER_CRITICAL(&gpio_context.gpio_spinlock);
gpio_hal_set_intr_type(gpio_context.gpio_hal, gpio_num, intr_type);
portEXIT_CRITICAL(&gpio_context.gpio_spinlock);
return ESP_OK;
driver(gpio) : Fixed the gpio related bug for release v3.1.
2018-06-04 10:34:23 +08:00
}
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
static esp_err_t gpio_intr_enable_on_core(gpio_num_t gpio_num, uint32_t core_id)
Convert Windows -> Unix line ends in gpio.c
2016-10-08 14:12:55 +08:00
{
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
GPIO_CHECK(GPIO_IS_VALID_GPIO(gpio_num), "GPIO number error", ESP_ERR_INVALID_ARG);
gpio_hal_intr_enable_on_core(gpio_context.gpio_hal, gpio_num, core_id);
Convert Windows -> Unix line ends in gpio.c
2016-10-08 14:12:55 +08:00
return ESP_OK;
}
gpio: Attach gpio intr to the isr_server on the right core. Make sure GPIO interrupts get attached to the core that the ISR service routine is running on, otherwise they don't arrive.
2017-01-19 23:46:41 +11:00
esp_err_t gpio_intr_enable(gpio_num_t gpio_num)
{
bugfix(GPIO): Fixed the bug that GPIO enables interrupts on one core, but registers interrupt service routines on another core closes https://github.com/espressif/esp-idf/issues/2808 closes https://github.com/espressif/esp-idf/issues/2845
2019-07-18 11:34:49 +08:00
GPIO_CHECK(GPIO_IS_VALID_GPIO(gpio_num), "GPIO number error", ESP_ERR_INVALID_ARG);
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
portENTER_CRITICAL(&gpio_context.gpio_spinlock);
if(gpio_context.isr_core_id == GPIO_ISR_CORE_ID_UNINIT) {
gpio_context.isr_core_id = xPortGetCoreID();
bugfix(GPIO): Fixed the bug that GPIO enables interrupts on one core, but registers interrupt service routines on another core closes https://github.com/espressif/esp-idf/issues/2808 closes https://github.com/espressif/esp-idf/issues/2845
2019-07-18 11:34:49 +08:00
}
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
portEXIT_CRITICAL(&gpio_context.gpio_spinlock);
return gpio_intr_enable_on_core (gpio_num, gpio_context.isr_core_id);
gpio: Attach gpio intr to the isr_server on the right core. Make sure GPIO interrupts get attached to the core that the ISR service routine is running on, otherwise they don't arrive.
2017-01-19 23:46:41 +11:00
}
Convert Windows -> Unix line ends in gpio.c
2016-10-08 14:12:55 +08:00
esp_err_t gpio_intr_disable(gpio_num_t gpio_num)
{
Minor changes for driver 1. remove "\n" when calling ESP_LOGX APIs. 2. modify uart_event_t for uart rx data. 3. use MICRO for uart inverse value 4. add uart_tx_data_t for internal tx function.
2016-11-07 14:16:52 +08:00
GPIO_CHECK(GPIO_IS_VALID_GPIO(gpio_num), "GPIO number error", ESP_ERR_INVALID_ARG);
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
gpio_hal_intr_disable(gpio_context.gpio_hal, gpio_num);
Convert Windows -> Unix line ends in gpio.c
2016-10-08 14:12:55 +08:00
return ESP_OK;
}
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
static esp_err_t gpio_input_disable(gpio_num_t gpio_num)
Convert Windows -> Unix line ends in gpio.c
2016-10-08 14:12:55 +08:00
{
Minor changes for driver 1. remove "\n" when calling ESP_LOGX APIs. 2. modify uart_event_t for uart rx data. 3. use MICRO for uart inverse value 4. add uart_tx_data_t for internal tx function.
2016-11-07 14:16:52 +08:00
GPIO_CHECK(GPIO_IS_VALID_GPIO(gpio_num), "GPIO number error", ESP_ERR_INVALID_ARG);
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
gpio_hal_input_disable(gpio_context.gpio_hal, gpio_num);
return ESP_OK;
}
gpio driver: Clear GPIO matrix output config when setting pin as input Otherwise, if a non-GPIO peripheral has been routed to this pin (as an output), output driver can remain enabled.
2017-06-26 12:41:40 +10:00
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
static esp_err_t gpio_input_enable(gpio_num_t gpio_num)
{
GPIO_CHECK(GPIO_IS_VALID_GPIO(gpio_num), "GPIO number error", ESP_ERR_INVALID_ARG);
gpio_hal_input_enable(gpio_context.gpio_hal, gpio_num);
return ESP_OK;
}
gpio driver: Clear GPIO matrix output config when setting pin as input Otherwise, if a non-GPIO peripheral has been routed to this pin (as an output), output driver can remain enabled.
2017-06-26 12:41:40 +10:00
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
static esp_err_t gpio_output_disable(gpio_num_t gpio_num)
{
GPIO_CHECK(GPIO_IS_VALID_GPIO(gpio_num), "GPIO number error", ESP_ERR_INVALID_ARG);
gpio_hal_output_disable(gpio_context.gpio_hal, gpio_num);
Convert Windows -> Unix line ends in gpio.c
2016-10-08 14:12:55 +08:00
return ESP_OK;
}
static esp_err_t gpio_output_enable(gpio_num_t gpio_num)
{
Minor changes for driver 1. remove "\n" when calling ESP_LOGX APIs. 2. modify uart_event_t for uart rx data. 3. use MICRO for uart inverse value 4. add uart_tx_data_t for internal tx function.
2016-11-07 14:16:52 +08:00
GPIO_CHECK(GPIO_IS_VALID_OUTPUT_GPIO(gpio_num), "GPIO output gpio_num error", ESP_ERR_INVALID_ARG);
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
gpio_hal_output_enable(gpio_context.gpio_hal, gpio_num);
gpio driver: Clear GPIO matrix output config when setting pin as input Otherwise, if a non-GPIO peripheral has been routed to this pin (as an output), output driver can remain enabled.
2017-06-26 12:41:40 +10:00
gpio_matrix_out(gpio_num, SIG_GPIO_OUT_IDX, false, false);
Convert Windows -> Unix line ends in gpio.c
2016-10-08 14:12:55 +08:00
return ESP_OK;
}
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
static esp_err_t gpio_od_disable(gpio_num_t gpio_num)
{
GPIO_CHECK(GPIO_IS_VALID_GPIO(gpio_num), "GPIO number error", ESP_ERR_INVALID_ARG);
gpio_hal_od_disable(gpio_context.gpio_hal, gpio_num);
return ESP_OK;
}
static esp_err_t gpio_od_enable(gpio_num_t gpio_num)
{
GPIO_CHECK(GPIO_IS_VALID_GPIO(gpio_num), "GPIO number error", ESP_ERR_INVALID_ARG);
gpio_hal_od_enable(gpio_context.gpio_hal, gpio_num);
return ESP_OK;
}
Convert Windows -> Unix line ends in gpio.c
2016-10-08 14:12:55 +08:00
esp_err_t gpio_set_level(gpio_num_t gpio_num, uint32_t level)
{
gpio driver: Fix gpio_set_level validation of gpio_num argument Closes #125 https://github.com/espressif/esp-idf/issues/125
2016-12-22 13:05:19 +11:00
GPIO_CHECK(GPIO_IS_VALID_OUTPUT_GPIO(gpio_num), "GPIO output gpio_num error", ESP_ERR_INVALID_ARG);
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
gpio_hal_set_level(gpio_context.gpio_hal, gpio_num, level);
Convert Windows -> Unix line ends in gpio.c
2016-10-08 14:12:55 +08:00
return ESP_OK;
}
int gpio_get_level(gpio_num_t gpio_num)
{
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
return gpio_hal_get_level(gpio_context.gpio_hal, gpio_num);
Convert Windows -> Unix line ends in gpio.c
2016-10-08 14:12:55 +08:00
}
esp_err_t gpio_set_pull_mode(gpio_num_t gpio_num, gpio_pull_mode_t pull)
{
Minor changes for driver 1. remove "\n" when calling ESP_LOGX APIs. 2. modify uart_event_t for uart rx data. 3. use MICRO for uart inverse value 4. add uart_tx_data_t for internal tx function.
2016-11-07 14:16:52 +08:00
GPIO_CHECK(GPIO_IS_VALID_GPIO(gpio_num), "GPIO number error", ESP_ERR_INVALID_ARG);
GPIO_CHECK(pull <= GPIO_FLOATING, "GPIO pull mode error", ESP_ERR_INVALID_ARG);
Convert Windows -> Unix line ends in gpio.c
2016-10-08 14:12:55 +08:00
esp_err_t ret = ESP_OK;
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
driver: add rtc module and bugfix gpio32 gpio33 feature(rtc_module):add rtc module 1. add rtc io control API (pull,output and input) 2. add touch pad API (touch pad read and interrupt) 3. add adc1 API (the max width is 12 Bits and support attenuation) 4. add hall sensor API (support hall sensor read ) 5. add dac API (the width is 8 Bits) bugfix(gpio):gpio32 and gpio33 can not output and input the gpio32 and gpio33 is initialize by librtc.a,and gpio_config not initialize the gpio as digital gpio.they can not output and input,when users use gpio32 or gpio33.And there are some problems about others driver ,when they use gpio32 or gpio33 as matrix.
2016-12-07 14:18:10 +08:00
switch (pull) {
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
case GPIO_PULLUP_ONLY:
gpio_pulldown_dis(gpio_num);
gpio_pullup_en(gpio_num);
break;
case GPIO_PULLDOWN_ONLY:
gpio_pulldown_en(gpio_num);
gpio_pullup_dis(gpio_num);
break;
case GPIO_PULLUP_PULLDOWN:
gpio_pulldown_en(gpio_num);
gpio_pullup_en(gpio_num);
break;
case GPIO_FLOATING:
gpio_pulldown_dis(gpio_num);
gpio_pullup_dis(gpio_num);
break;
default:
ESP_LOGE(GPIO_TAG, "Unknown pull up/down mode,gpio_num=%u,pull=%u", gpio_num, pull);
ret = ESP_ERR_INVALID_ARG;
break;
Convert Windows -> Unix line ends in gpio.c
2016-10-08 14:12:55 +08:00
}
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
Convert Windows -> Unix line ends in gpio.c
2016-10-08 14:12:55 +08:00
return ret;
}
esp_err_t gpio_set_direction(gpio_num_t gpio_num, gpio_mode_t mode)
{
Minor changes for driver 1. remove "\n" when calling ESP_LOGX APIs. 2. modify uart_event_t for uart rx data. 3. use MICRO for uart inverse value 4. add uart_tx_data_t for internal tx function.
2016-11-07 14:16:52 +08:00
GPIO_CHECK(GPIO_IS_VALID_GPIO(gpio_num), "GPIO number error", ESP_ERR_INVALID_ARG);
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
if ((GPIO_IS_VALID_OUTPUT_GPIO(gpio_num) != true) && (mode & GPIO_MODE_DEF_OUTPUT)) {
driver: add rtc module and bugfix gpio32 gpio33 feature(rtc_module):add rtc module 1. add rtc io control API (pull,output and input) 2. add touch pad API (touch pad read and interrupt) 3. add adc1 API (the max width is 12 Bits and support attenuation) 4. add hall sensor API (support hall sensor read ) 5. add dac API (the width is 8 Bits) bugfix(gpio):gpio32 and gpio33 can not output and input the gpio32 and gpio33 is initialize by librtc.a,and gpio_config not initialize the gpio as digital gpio.they can not output and input,when users use gpio32 or gpio33.And there are some problems about others driver ,when they use gpio32 or gpio33 as matrix.
2016-12-07 14:18:10 +08:00
ESP_LOGE(GPIO_TAG, "io_num=%d can only be input", gpio_num);
Convert Windows -> Unix line ends in gpio.c
2016-10-08 14:12:55 +08:00
return ESP_ERR_INVALID_ARG;
}
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
Convert Windows -> Unix line ends in gpio.c
2016-10-08 14:12:55 +08:00
esp_err_t ret = ESP_OK;
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
driver: add rtc module and bugfix gpio32 gpio33 feature(rtc_module):add rtc module 1. add rtc io control API (pull,output and input) 2. add touch pad API (touch pad read and interrupt) 3. add adc1 API (the max width is 12 Bits and support attenuation) 4. add hall sensor API (support hall sensor read ) 5. add dac API (the width is 8 Bits) bugfix(gpio):gpio32 and gpio33 can not output and input the gpio32 and gpio33 is initialize by librtc.a,and gpio_config not initialize the gpio as digital gpio.they can not output and input,when users use gpio32 or gpio33.And there are some problems about others driver ,when they use gpio32 or gpio33 as matrix.
2016-12-07 14:18:10 +08:00
if (mode & GPIO_MODE_DEF_INPUT) {
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
gpio_input_enable(gpio_num);
Convert Windows -> Unix line ends in gpio.c
2016-10-08 14:12:55 +08:00
} else {
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
gpio_input_disable(gpio_num);
Convert Windows -> Unix line ends in gpio.c
2016-10-08 14:12:55 +08:00
}
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
driver: add rtc module and bugfix gpio32 gpio33 feature(rtc_module):add rtc module 1. add rtc io control API (pull,output and input) 2. add touch pad API (touch pad read and interrupt) 3. add adc1 API (the max width is 12 Bits and support attenuation) 4. add hall sensor API (support hall sensor read ) 5. add dac API (the width is 8 Bits) bugfix(gpio):gpio32 and gpio33 can not output and input the gpio32 and gpio33 is initialize by librtc.a,and gpio_config not initialize the gpio as digital gpio.they can not output and input,when users use gpio32 or gpio33.And there are some problems about others driver ,when they use gpio32 or gpio33 as matrix.
2016-12-07 14:18:10 +08:00
if (mode & GPIO_MODE_DEF_OUTPUT) {
gpio driver: Clear GPIO matrix output config when setting pin as input Otherwise, if a non-GPIO peripheral has been routed to this pin (as an output), output driver can remain enabled.
2017-06-26 12:41:40 +10:00
gpio_output_enable(gpio_num);
Convert Windows -> Unix line ends in gpio.c
2016-10-08 14:12:55 +08:00
} else {
gpio driver: Clear GPIO matrix output config when setting pin as input Otherwise, if a non-GPIO peripheral has been routed to this pin (as an output), output driver can remain enabled.
2017-06-26 12:41:40 +10:00
gpio_output_disable(gpio_num);
Convert Windows -> Unix line ends in gpio.c
2016-10-08 14:12:55 +08:00
}
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
driver: add rtc module and bugfix gpio32 gpio33 feature(rtc_module):add rtc module 1. add rtc io control API (pull,output and input) 2. add touch pad API (touch pad read and interrupt) 3. add adc1 API (the max width is 12 Bits and support attenuation) 4. add hall sensor API (support hall sensor read ) 5. add dac API (the width is 8 Bits) bugfix(gpio):gpio32 and gpio33 can not output and input the gpio32 and gpio33 is initialize by librtc.a,and gpio_config not initialize the gpio as digital gpio.they can not output and input,when users use gpio32 or gpio33.And there are some problems about others driver ,when they use gpio32 or gpio33 as matrix.
2016-12-07 14:18:10 +08:00
if (mode & GPIO_MODE_DEF_OD) {
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
gpio_od_enable(gpio_num);
Convert Windows -> Unix line ends in gpio.c
2016-10-08 14:12:55 +08:00
} else {
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
gpio_od_disable(gpio_num);
Convert Windows -> Unix line ends in gpio.c
2016-10-08 14:12:55 +08:00
}
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
Convert Windows -> Unix line ends in gpio.c
2016-10-08 14:12:55 +08:00
return ret;
}
components/driver: 'const' all config calls. Some were, some weren't. They all could/should be. Signed-off-by: Michel Pollet <buserror@gmail.com>
2017-04-13 18:33:33 +01:00
esp_err_t gpio_config(const gpio_config_t *pGPIOConfig)
Convert Windows -> Unix line ends in gpio.c
2016-10-08 14:12:55 +08:00
{
uint64_t gpio_pin_mask = (pGPIOConfig->pin_bit_mask);
uint32_t io_reg = 0;
uint32_t io_num = 0;
Minor changes for driver 1. remove "\n" when calling ESP_LOGX APIs. 2. modify uart_event_t for uart rx data. 3. use MICRO for uart inverse value 4. add uart_tx_data_t for internal tx function.
2016-11-07 14:16:52 +08:00
uint8_t input_en = 0;
uint8_t output_en = 0;
uint8_t od_en = 0;
uint8_t pu_en = 0;
uint8_t pd_en = 0;
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
driver: add rtc module and bugfix gpio32 gpio33 feature(rtc_module):add rtc module 1. add rtc io control API (pull,output and input) 2. add touch pad API (touch pad read and interrupt) 3. add adc1 API (the max width is 12 Bits and support attenuation) 4. add hall sensor API (support hall sensor read ) 5. add dac API (the width is 8 Bits) bugfix(gpio):gpio32 and gpio33 can not output and input the gpio32 and gpio33 is initialize by librtc.a,and gpio_config not initialize the gpio as digital gpio.they can not output and input,when users use gpio32 or gpio33.And there are some problems about others driver ,when they use gpio32 or gpio33 as matrix.
2016-12-07 14:18:10 +08:00
if (pGPIOConfig->pin_bit_mask == 0 || pGPIOConfig->pin_bit_mask >= (((uint64_t) 1) << GPIO_PIN_COUNT)) {
Minor changes for driver 1. remove "\n" when calling ESP_LOGX APIs. 2. modify uart_event_t for uart rx data. 3. use MICRO for uart inverse value 4. add uart_tx_data_t for internal tx function.
2016-11-07 14:16:52 +08:00
ESP_LOGE(GPIO_TAG, "GPIO_PIN mask error ");
Convert Windows -> Unix line ends in gpio.c
2016-10-08 14:12:55 +08:00
return ESP_ERR_INVALID_ARG;
}
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
driver: add rtc module and bugfix gpio32 gpio33 feature(rtc_module):add rtc module 1. add rtc io control API (pull,output and input) 2. add touch pad API (touch pad read and interrupt) 3. add adc1 API (the max width is 12 Bits and support attenuation) 4. add hall sensor API (support hall sensor read ) 5. add dac API (the width is 8 Bits) bugfix(gpio):gpio32 and gpio33 can not output and input the gpio32 and gpio33 is initialize by librtc.a,and gpio_config not initialize the gpio as digital gpio.they can not output and input,when users use gpio32 or gpio33.And there are some problems about others driver ,when they use gpio32 or gpio33 as matrix.
2016-12-07 14:18:10 +08:00
if ((pGPIOConfig->mode) & (GPIO_MODE_DEF_OUTPUT)) {
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
if(GPIO_MASK_CONTAIN_INPUT_GPIO(gpio_pin_mask)) {
ESP_LOGE(GPIO_TAG, "GPIO can only be used as input mode");
Convert Windows -> Unix line ends in gpio.c
2016-10-08 14:12:55 +08:00
return ESP_ERR_INVALID_ARG;
}
}
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
Convert Windows -> Unix line ends in gpio.c
2016-10-08 14:12:55 +08:00
do {
io_reg = GPIO_PIN_MUX_REG[io_num];
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
driver(gpio) : Fixed the gpio related bug for release v3.1.
2018-06-04 10:34:23 +08:00
if (((gpio_pin_mask >> io_num) & BIT(0))) {
if (!io_reg) {
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
ESP_LOGE(GPIO_TAG, "IO%d is not a valid GPIO", io_num);
driver(gpio) : Fixed the gpio related bug for release v3.1.
2018-06-04 10:34:23 +08:00
return ESP_ERR_INVALID_ARG;
}
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
if (rtc_gpio_is_valid_gpio(io_num)) {
driver: add rtc module and bugfix gpio32 gpio33 feature(rtc_module):add rtc module 1. add rtc io control API (pull,output and input) 2. add touch pad API (touch pad read and interrupt) 3. add adc1 API (the max width is 12 Bits and support attenuation) 4. add hall sensor API (support hall sensor read ) 5. add dac API (the width is 8 Bits) bugfix(gpio):gpio32 and gpio33 can not output and input the gpio32 and gpio33 is initialize by librtc.a,and gpio_config not initialize the gpio as digital gpio.they can not output and input,when users use gpio32 or gpio33.And there are some problems about others driver ,when they use gpio32 or gpio33 as matrix.
2016-12-07 14:18:10 +08:00
rtc_gpio_deinit(io_num);
}
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
driver: add rtc module and bugfix gpio32 gpio33 feature(rtc_module):add rtc module 1. add rtc io control API (pull,output and input) 2. add touch pad API (touch pad read and interrupt) 3. add adc1 API (the max width is 12 Bits and support attenuation) 4. add hall sensor API (support hall sensor read ) 5. add dac API (the width is 8 Bits) bugfix(gpio):gpio32 and gpio33 can not output and input the gpio32 and gpio33 is initialize by librtc.a,and gpio_config not initialize the gpio as digital gpio.they can not output and input,when users use gpio32 or gpio33.And there are some problems about others driver ,when they use gpio32 or gpio33 as matrix.
2016-12-07 14:18:10 +08:00
if ((pGPIOConfig->mode) & GPIO_MODE_DEF_INPUT) {
Minor changes for driver 1. remove "\n" when calling ESP_LOGX APIs. 2. modify uart_event_t for uart rx data. 3. use MICRO for uart inverse value 4. add uart_tx_data_t for internal tx function.
2016-11-07 14:16:52 +08:00
input_en = 1;
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
gpio_input_enable(io_num);
Convert Windows -> Unix line ends in gpio.c
2016-10-08 14:12:55 +08:00
} else {
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
gpio_input_disable(io_num);
Convert Windows -> Unix line ends in gpio.c
2016-10-08 14:12:55 +08:00
}
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
driver: add rtc module and bugfix gpio32 gpio33 feature(rtc_module):add rtc module 1. add rtc io control API (pull,output and input) 2. add touch pad API (touch pad read and interrupt) 3. add adc1 API (the max width is 12 Bits and support attenuation) 4. add hall sensor API (support hall sensor read ) 5. add dac API (the width is 8 Bits) bugfix(gpio):gpio32 and gpio33 can not output and input the gpio32 and gpio33 is initialize by librtc.a,and gpio_config not initialize the gpio as digital gpio.they can not output and input,when users use gpio32 or gpio33.And there are some problems about others driver ,when they use gpio32 or gpio33 as matrix.
2016-12-07 14:18:10 +08:00
if ((pGPIOConfig->mode) & GPIO_MODE_DEF_OD) {
Minor changes for driver 1. remove "\n" when calling ESP_LOGX APIs. 2. modify uart_event_t for uart rx data. 3. use MICRO for uart inverse value 4. add uart_tx_data_t for internal tx function.
2016-11-07 14:16:52 +08:00
od_en = 1;
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
gpio_od_enable(io_num);
Convert Windows -> Unix line ends in gpio.c
2016-10-08 14:12:55 +08:00
} else {
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
gpio_od_disable(io_num);
Convert Windows -> Unix line ends in gpio.c
2016-10-08 14:12:55 +08:00
}
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
driver: add rtc module and bugfix gpio32 gpio33 feature(rtc_module):add rtc module 1. add rtc io control API (pull,output and input) 2. add touch pad API (touch pad read and interrupt) 3. add adc1 API (the max width is 12 Bits and support attenuation) 4. add hall sensor API (support hall sensor read ) 5. add dac API (the width is 8 Bits) bugfix(gpio):gpio32 and gpio33 can not output and input the gpio32 and gpio33 is initialize by librtc.a,and gpio_config not initialize the gpio as digital gpio.they can not output and input,when users use gpio32 or gpio33.And there are some problems about others driver ,when they use gpio32 or gpio33 as matrix.
2016-12-07 14:18:10 +08:00
if ((pGPIOConfig->mode) & GPIO_MODE_DEF_OUTPUT) {
Minor changes for driver 1. remove "\n" when calling ESP_LOGX APIs. 2. modify uart_event_t for uart rx data. 3. use MICRO for uart inverse value 4. add uart_tx_data_t for internal tx function.
2016-11-07 14:16:52 +08:00
output_en = 1;
Convert Windows -> Unix line ends in gpio.c
2016-10-08 14:12:55 +08:00
gpio_output_enable(io_num);
} else {
gpio_output_disable(io_num);
}
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
driver: add rtc module and bugfix gpio32 gpio33 feature(rtc_module):add rtc module 1. add rtc io control API (pull,output and input) 2. add touch pad API (touch pad read and interrupt) 3. add adc1 API (the max width is 12 Bits and support attenuation) 4. add hall sensor API (support hall sensor read ) 5. add dac API (the width is 8 Bits) bugfix(gpio):gpio32 and gpio33 can not output and input the gpio32 and gpio33 is initialize by librtc.a,and gpio_config not initialize the gpio as digital gpio.they can not output and input,when users use gpio32 or gpio33.And there are some problems about others driver ,when they use gpio32 or gpio33 as matrix.
2016-12-07 14:18:10 +08:00
if (pGPIOConfig->pull_up_en) {
Minor changes for driver 1. remove "\n" when calling ESP_LOGX APIs. 2. modify uart_event_t for uart rx data. 3. use MICRO for uart inverse value 4. add uart_tx_data_t for internal tx function.
2016-11-07 14:16:52 +08:00
pu_en = 1;
driver: add rtc module and bugfix gpio32 gpio33 feature(rtc_module):add rtc module 1. add rtc io control API (pull,output and input) 2. add touch pad API (touch pad read and interrupt) 3. add adc1 API (the max width is 12 Bits and support attenuation) 4. add hall sensor API (support hall sensor read ) 5. add dac API (the width is 8 Bits) bugfix(gpio):gpio32 and gpio33 can not output and input the gpio32 and gpio33 is initialize by librtc.a,and gpio_config not initialize the gpio as digital gpio.they can not output and input,when users use gpio32 or gpio33.And there are some problems about others driver ,when they use gpio32 or gpio33 as matrix.
2016-12-07 14:18:10 +08:00
gpio_pullup_en(io_num);
Convert Windows -> Unix line ends in gpio.c
2016-10-08 14:12:55 +08:00
} else {
driver: add rtc module and bugfix gpio32 gpio33 feature(rtc_module):add rtc module 1. add rtc io control API (pull,output and input) 2. add touch pad API (touch pad read and interrupt) 3. add adc1 API (the max width is 12 Bits and support attenuation) 4. add hall sensor API (support hall sensor read ) 5. add dac API (the width is 8 Bits) bugfix(gpio):gpio32 and gpio33 can not output and input the gpio32 and gpio33 is initialize by librtc.a,and gpio_config not initialize the gpio as digital gpio.they can not output and input,when users use gpio32 or gpio33.And there are some problems about others driver ,when they use gpio32 or gpio33 as matrix.
2016-12-07 14:18:10 +08:00
gpio_pullup_dis(io_num);
Convert Windows -> Unix line ends in gpio.c
2016-10-08 14:12:55 +08:00
}
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
driver: add rtc module and bugfix gpio32 gpio33 feature(rtc_module):add rtc module 1. add rtc io control API (pull,output and input) 2. add touch pad API (touch pad read and interrupt) 3. add adc1 API (the max width is 12 Bits and support attenuation) 4. add hall sensor API (support hall sensor read ) 5. add dac API (the width is 8 Bits) bugfix(gpio):gpio32 and gpio33 can not output and input the gpio32 and gpio33 is initialize by librtc.a,and gpio_config not initialize the gpio as digital gpio.they can not output and input,when users use gpio32 or gpio33.And there are some problems about others driver ,when they use gpio32 or gpio33 as matrix.
2016-12-07 14:18:10 +08:00
if (pGPIOConfig->pull_down_en) {
Minor changes for driver 1. remove "\n" when calling ESP_LOGX APIs. 2. modify uart_event_t for uart rx data. 3. use MICRO for uart inverse value 4. add uart_tx_data_t for internal tx function.
2016-11-07 14:16:52 +08:00
pd_en = 1;
driver: add rtc module and bugfix gpio32 gpio33 feature(rtc_module):add rtc module 1. add rtc io control API (pull,output and input) 2. add touch pad API (touch pad read and interrupt) 3. add adc1 API (the max width is 12 Bits and support attenuation) 4. add hall sensor API (support hall sensor read ) 5. add dac API (the width is 8 Bits) bugfix(gpio):gpio32 and gpio33 can not output and input the gpio32 and gpio33 is initialize by librtc.a,and gpio_config not initialize the gpio as digital gpio.they can not output and input,when users use gpio32 or gpio33.And there are some problems about others driver ,when they use gpio32 or gpio33 as matrix.
2016-12-07 14:18:10 +08:00
gpio_pulldown_en(io_num);
Convert Windows -> Unix line ends in gpio.c
2016-10-08 14:12:55 +08:00
} else {
driver: add rtc module and bugfix gpio32 gpio33 feature(rtc_module):add rtc module 1. add rtc io control API (pull,output and input) 2. add touch pad API (touch pad read and interrupt) 3. add adc1 API (the max width is 12 Bits and support attenuation) 4. add hall sensor API (support hall sensor read ) 5. add dac API (the width is 8 Bits) bugfix(gpio):gpio32 and gpio33 can not output and input the gpio32 and gpio33 is initialize by librtc.a,and gpio_config not initialize the gpio as digital gpio.they can not output and input,when users use gpio32 or gpio33.And there are some problems about others driver ,when they use gpio32 or gpio33 as matrix.
2016-12-07 14:18:10 +08:00
gpio_pulldown_dis(io_num);
Convert Windows -> Unix line ends in gpio.c
2016-10-08 14:12:55 +08:00
}
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
Minor changes for driver 1. remove "\n" when calling ESP_LOGX APIs. 2. modify uart_event_t for uart rx data. 3. use MICRO for uart inverse value 4. add uart_tx_data_t for internal tx function.
2016-11-07 14:16:52 +08:00
ESP_LOGI(GPIO_TAG, "GPIO[%d]| InputEn: %d| OutputEn: %d| OpenDrain: %d| Pullup: %d| Pulldown: %d| Intr:%d ", io_num, input_en, output_en, od_en, pu_en, pd_en, pGPIOConfig->intr_type);
Convert Windows -> Unix line ends in gpio.c
2016-10-08 14:12:55 +08:00
gpio_set_intr_type(io_num, pGPIOConfig->intr_type);
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
driver: add rtc module and bugfix gpio32 gpio33 feature(rtc_module):add rtc module 1. add rtc io control API (pull,output and input) 2. add touch pad API (touch pad read and interrupt) 3. add adc1 API (the max width is 12 Bits and support attenuation) 4. add hall sensor API (support hall sensor read ) 5. add dac API (the width is 8 Bits) bugfix(gpio):gpio32 and gpio33 can not output and input the gpio32 and gpio33 is initialize by librtc.a,and gpio_config not initialize the gpio as digital gpio.they can not output and input,when users use gpio32 or gpio33.And there are some problems about others driver ,when they use gpio32 or gpio33 as matrix.
2016-12-07 14:18:10 +08:00
if (pGPIOConfig->intr_type) {
Convert Windows -> Unix line ends in gpio.c
2016-10-08 14:12:55 +08:00
gpio_intr_enable(io_num);
} else {
gpio_intr_disable(io_num);
}
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
Convert Windows -> Unix line ends in gpio.c
2016-10-08 14:12:55 +08:00
PIN_FUNC_SELECT(io_reg, PIN_FUNC_GPIO); /*function number 2 is GPIO_FUNC for each pin */
}
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
Convert Windows -> Unix line ends in gpio.c
2016-10-08 14:12:55 +08:00
io_num++;
driver: add rtc module and bugfix gpio32 gpio33 feature(rtc_module):add rtc module 1. add rtc io control API (pull,output and input) 2. add touch pad API (touch pad read and interrupt) 3. add adc1 API (the max width is 12 Bits and support attenuation) 4. add hall sensor API (support hall sensor read ) 5. add dac API (the width is 8 Bits) bugfix(gpio):gpio32 and gpio33 can not output and input the gpio32 and gpio33 is initialize by librtc.a,and gpio_config not initialize the gpio as digital gpio.they can not output and input,when users use gpio32 or gpio33.And there are some problems about others driver ,when they use gpio32 or gpio33 as matrix.
2016-12-07 14:18:10 +08:00
} while (io_num < GPIO_PIN_COUNT);
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
Convert Windows -> Unix line ends in gpio.c
2016-10-08 14:12:55 +08:00
return ESP_OK;
}
fix(spi): reset gpios that used by spi when deinited
2018-06-08 15:33:04 +08:00
esp_err_t gpio_reset_pin(gpio_num_t gpio_num)
{
assert(gpio_num >= 0 && GPIO_IS_VALID_GPIO(gpio_num));
gpio_config_t cfg = {
gpio: Bitmask overflow fix in gpio_reset_pin For pins 32 and up the BIT(nr) macro used here overflowed, causing undetermined GPIO pins to be reset. Example: freeing SPI device/bus where CS is on pin 33 caused debug UART to cease communication, TXD0 was disabled. Fixed as BIT64(nr) macro, to be used elsewhere as needed. For example in definitions like GPIO_SEL_32..GPIO_SEL_39.
2018-08-08 15:31:17 +03:00
.pin_bit_mask = BIT64(gpio_num),
fix(spi): reset gpios that used by spi when deinited
2018-06-08 15:33:04 +08:00
.mode = GPIO_MODE_DISABLE,
//for powersave reasons, the GPIO should not be floating, select pullup
.pull_up_en = true,
.pull_down_en = false,
.intr_type = GPIO_INTR_DISABLE,
};
gpio_config(&cfg);
return ESP_OK;
}
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
static inline void IRAM_ATTR gpio_isr_loop(uint32_t status, const uint32_t gpio_num_start)
{
gpio/driver: Sped the gpio_intr_service ISR up by 1.5 uSeconds (+-50% faster). Removed as much branching (if statements) from the gpio_intr_service ISR, as possible and split the while loop into two. Also forced writing the two status*_w1tc variables only once, instead of every time after calling the external function hooks. The measurements below, was done using the following tools: Toolchain version: crosstool-ng-1.22.0-80-g6c4433a Compiler version: 5.2.0 Here follows a comparison of the gpio_intr_service ISR's execution time, using a DS1054 oscilloscope. All the time spent calling external functions, via the function pointers gpio_isr_func[gpio_num].fn, were disregarded. With OPTIMIZATION_FLAGS = -Og, 1.34 uSeconds faster: 3.22 uSec (with this patch) 4.56 uSec (with commit 71c90ac4) 100 - (100 * 4.56 / 3.22) = 42% faster With OPTIMIZATION_FLAGS = -Os, 1.65 uSeconds faster: 2.89 uSec (with this patch) 4.54 uSec (with commit 71c90ac4) 100 - (100 * 4.54 / 2.89) = 57% faster Signed-off-by: Konstantin Kondrashov <konstantin@espressif.com> Merges https://github.com/espressif/esp-idf/pull/2861
2018-12-21 14:07:51 +00:00
while (status) {
int nbit = __builtin_ffs(status) - 1;
status &= ~(1 << nbit);
int gpio_num = gpio_num_start + nbit;
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
if (gpio_context.gpio_isr_func[gpio_num].fn != NULL) {
gpio_context.gpio_isr_func[gpio_num].fn(gpio_context.gpio_isr_func[gpio_num].args);
gpio/driver: Sped the gpio_intr_service ISR up by 1.5 uSeconds (+-50% faster). Removed as much branching (if statements) from the gpio_intr_service ISR, as possible and split the while loop into two. Also forced writing the two status*_w1tc variables only once, instead of every time after calling the external function hooks. The measurements below, was done using the following tools: Toolchain version: crosstool-ng-1.22.0-80-g6c4433a Compiler version: 5.2.0 Here follows a comparison of the gpio_intr_service ISR's execution time, using a DS1054 oscilloscope. All the time spent calling external functions, via the function pointers gpio_isr_func[gpio_num].fn, were disregarded. With OPTIMIZATION_FLAGS = -Og, 1.34 uSeconds faster: 3.22 uSec (with this patch) 4.56 uSec (with commit 71c90ac4) 100 - (100 * 4.56 / 3.22) = 42% faster With OPTIMIZATION_FLAGS = -Os, 1.65 uSeconds faster: 2.89 uSec (with this patch) 4.54 uSec (with commit 71c90ac4) 100 - (100 * 4.54 / 2.89) = 57% faster Signed-off-by: Konstantin Kondrashov <konstantin@espressif.com> Merges https://github.com/espressif/esp-idf/pull/2861
2018-12-21 14:07:51 +00:00
}
}
}
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
static void IRAM_ATTR gpio_intr_service(void *arg)
gpio_driver: add per-pin interrupt handlers 1. add ISR handler apis so that users of different layers can hook their own isr handler on different GPIO. Audio project has different software layers, they need different gpio isr handler for layer instead of processing all GPIO interrupts in one handler. If this kind of calling a handler from isr is not proper, please kindly point out. 2. add gpio example code. 3. improve gpio.rst 4. add readme for gpio example Squashed commits: [278e50f] update: GPIO 1. coding style, add a space between conditional or loop keyword and an opening paren. 2. modify some return value and doc 3. use printf in example code Squashed commits: [efb23bb] minor change of comment
2016-12-24 20:45:57 +08:00
{
//GPIO intr process
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
if (gpio_context.gpio_isr_func == NULL) {
gpio_driver: add per-pin interrupt handlers 1. add ISR handler apis so that users of different layers can hook their own isr handler on different GPIO. Audio project has different software layers, they need different gpio isr handler for layer instead of processing all GPIO interrupts in one handler. If this kind of calling a handler from isr is not proper, please kindly point out. 2. add gpio example code. 3. improve gpio.rst 4. add readme for gpio example Squashed commits: [278e50f] update: GPIO 1. coding style, add a space between conditional or loop keyword and an opening paren. 2. modify some return value and doc 3. use printf in example code Squashed commits: [efb23bb] minor change of comment
2016-12-24 20:45:57 +08:00
return;
}
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
gpio/driver: Sped the gpio_intr_service ISR up by 1.5 uSeconds (+-50% faster). Removed as much branching (if statements) from the gpio_intr_service ISR, as possible and split the while loop into two. Also forced writing the two status*_w1tc variables only once, instead of every time after calling the external function hooks. The measurements below, was done using the following tools: Toolchain version: crosstool-ng-1.22.0-80-g6c4433a Compiler version: 5.2.0 Here follows a comparison of the gpio_intr_service ISR's execution time, using a DS1054 oscilloscope. All the time spent calling external functions, via the function pointers gpio_isr_func[gpio_num].fn, were disregarded. With OPTIMIZATION_FLAGS = -Og, 1.34 uSeconds faster: 3.22 uSec (with this patch) 4.56 uSec (with commit 71c90ac4) 100 - (100 * 4.56 / 3.22) = 42% faster With OPTIMIZATION_FLAGS = -Os, 1.65 uSeconds faster: 2.89 uSec (with this patch) 4.54 uSec (with commit 71c90ac4) 100 - (100 * 4.54 / 2.89) = 57% faster Signed-off-by: Konstantin Kondrashov <konstantin@espressif.com> Merges https://github.com/espressif/esp-idf/pull/2861
2018-12-21 14:07:51 +00:00
//read status to get interrupt status for GPIO0-31
Merge branch 'master' into feature/esp32s2beta_update
2019-08-08 14:00:45 +10:00
uint32_t gpio_intr_status;
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
gpio_hal_get_intr_status(gpio_context.gpio_hal, gpio_context.isr_core_id, &gpio_intr_status);
gpio/driver: Sped the gpio_intr_service ISR up by 1.5 uSeconds (+-50% faster). Removed as much branching (if statements) from the gpio_intr_service ISR, as possible and split the while loop into two. Also forced writing the two status*_w1tc variables only once, instead of every time after calling the external function hooks. The measurements below, was done using the following tools: Toolchain version: crosstool-ng-1.22.0-80-g6c4433a Compiler version: 5.2.0 Here follows a comparison of the gpio_intr_service ISR's execution time, using a DS1054 oscilloscope. All the time spent calling external functions, via the function pointers gpio_isr_func[gpio_num].fn, were disregarded. With OPTIMIZATION_FLAGS = -Og, 1.34 uSeconds faster: 3.22 uSec (with this patch) 4.56 uSec (with commit 71c90ac4) 100 - (100 * 4.56 / 3.22) = 42% faster With OPTIMIZATION_FLAGS = -Os, 1.65 uSeconds faster: 2.89 uSec (with this patch) 4.54 uSec (with commit 71c90ac4) 100 - (100 * 4.54 / 2.89) = 57% faster Signed-off-by: Konstantin Kondrashov <konstantin@espressif.com> Merges https://github.com/espressif/esp-idf/pull/2861
2018-12-21 14:07:51 +00:00
if (gpio_intr_status) {
gpio_isr_loop(gpio_intr_status, 0);
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
gpio_hal_clear_intr_status(gpio_context.gpio_hal, gpio_intr_status);
gpio/driver: Sped the gpio_intr_service ISR up by 1.5 uSeconds (+-50% faster). Removed as much branching (if statements) from the gpio_intr_service ISR, as possible and split the while loop into two. Also forced writing the two status*_w1tc variables only once, instead of every time after calling the external function hooks. The measurements below, was done using the following tools: Toolchain version: crosstool-ng-1.22.0-80-g6c4433a Compiler version: 5.2.0 Here follows a comparison of the gpio_intr_service ISR's execution time, using a DS1054 oscilloscope. All the time spent calling external functions, via the function pointers gpio_isr_func[gpio_num].fn, were disregarded. With OPTIMIZATION_FLAGS = -Og, 1.34 uSeconds faster: 3.22 uSec (with this patch) 4.56 uSec (with commit 71c90ac4) 100 - (100 * 4.56 / 3.22) = 42% faster With OPTIMIZATION_FLAGS = -Os, 1.65 uSeconds faster: 2.89 uSec (with this patch) 4.54 uSec (with commit 71c90ac4) 100 - (100 * 4.54 / 2.89) = 57% faster Signed-off-by: Konstantin Kondrashov <konstantin@espressif.com> Merges https://github.com/espressif/esp-idf/pull/2861
2018-12-21 14:07:51 +00:00
}
//read status1 to get interrupt status for GPIO32-39
Merge branch 'master' into feature/esp32s2beta_update
2019-08-08 14:00:45 +10:00
uint32_t gpio_intr_status_h;
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
gpio_hal_get_intr_status_high(gpio_context.gpio_hal, gpio_context.isr_core_id, &gpio_intr_status_h);
gpio/driver: Sped the gpio_intr_service ISR up by 1.5 uSeconds (+-50% faster). Removed as much branching (if statements) from the gpio_intr_service ISR, as possible and split the while loop into two. Also forced writing the two status*_w1tc variables only once, instead of every time after calling the external function hooks. The measurements below, was done using the following tools: Toolchain version: crosstool-ng-1.22.0-80-g6c4433a Compiler version: 5.2.0 Here follows a comparison of the gpio_intr_service ISR's execution time, using a DS1054 oscilloscope. All the time spent calling external functions, via the function pointers gpio_isr_func[gpio_num].fn, were disregarded. With OPTIMIZATION_FLAGS = -Og, 1.34 uSeconds faster: 3.22 uSec (with this patch) 4.56 uSec (with commit 71c90ac4) 100 - (100 * 4.56 / 3.22) = 42% faster With OPTIMIZATION_FLAGS = -Os, 1.65 uSeconds faster: 2.89 uSec (with this patch) 4.54 uSec (with commit 71c90ac4) 100 - (100 * 4.54 / 2.89) = 57% faster Signed-off-by: Konstantin Kondrashov <konstantin@espressif.com> Merges https://github.com/espressif/esp-idf/pull/2861
2018-12-21 14:07:51 +00:00
if (gpio_intr_status_h) {
gpio_isr_loop(gpio_intr_status_h, 32);
bugfix(gpio):fix esp32 s2 rtc io issue * Modify the function implementation of ESP32-S2 RTC GPIO On ESP32 those PADs which have RTC functions must set pullup/down/capability via RTC register. On ESP32-S2, Digital IOs have their own registers to control pullup/down/capability, independent with RTC registers. * Add ESP32-S2 support of unit test * Modify the pull-up test of unit test * Modify the interrupt test of unit test * Modify input and output mode test of unit test
2019-11-26 20:00:24 +08:00
gpio_hal_clear_intr_status_high(gpio_context.gpio_hal, gpio_intr_status_h);
gpio/driver: Sped the gpio_intr_service ISR up by 1.5 uSeconds (+-50% faster). Removed as much branching (if statements) from the gpio_intr_service ISR, as possible and split the while loop into two. Also forced writing the two status*_w1tc variables only once, instead of every time after calling the external function hooks. The measurements below, was done using the following tools: Toolchain version: crosstool-ng-1.22.0-80-g6c4433a Compiler version: 5.2.0 Here follows a comparison of the gpio_intr_service ISR's execution time, using a DS1054 oscilloscope. All the time spent calling external functions, via the function pointers gpio_isr_func[gpio_num].fn, were disregarded. With OPTIMIZATION_FLAGS = -Og, 1.34 uSeconds faster: 3.22 uSec (with this patch) 4.56 uSec (with commit 71c90ac4) 100 - (100 * 4.56 / 3.22) = 42% faster With OPTIMIZATION_FLAGS = -Os, 1.65 uSeconds faster: 2.89 uSec (with this patch) 4.54 uSec (with commit 71c90ac4) 100 - (100 * 4.54 / 2.89) = 57% faster Signed-off-by: Konstantin Kondrashov <konstantin@espressif.com> Merges https://github.com/espressif/esp-idf/pull/2861
2018-12-21 14:07:51 +00:00
}
gpio_driver: add per-pin interrupt handlers 1. add ISR handler apis so that users of different layers can hook their own isr handler on different GPIO. Audio project has different software layers, they need different gpio isr handler for layer instead of processing all GPIO interrupts in one handler. If this kind of calling a handler from isr is not proper, please kindly point out. 2. add gpio example code. 3. improve gpio.rst 4. add readme for gpio example Squashed commits: [278e50f] update: GPIO 1. coding style, add a space between conditional or loop keyword and an opening paren. 2. modify some return value and doc 3. use printf in example code Squashed commits: [efb23bb] minor change of comment
2016-12-24 20:45:57 +08:00
}
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
esp_err_t gpio_install_isr_service(int intr_alloc_flags)
gpio_driver: add per-pin interrupt handlers 1. add ISR handler apis so that users of different layers can hook their own isr handler on different GPIO. Audio project has different software layers, they need different gpio isr handler for layer instead of processing all GPIO interrupts in one handler. If this kind of calling a handler from isr is not proper, please kindly point out. 2. add gpio example code. 3. improve gpio.rst 4. add readme for gpio example Squashed commits: [278e50f] update: GPIO 1. coding style, add a space between conditional or loop keyword and an opening paren. 2. modify some return value and doc 3. use printf in example code Squashed commits: [efb23bb] minor change of comment
2016-12-24 20:45:57 +08:00
{
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
GPIO_CHECK(gpio_context.gpio_isr_func == NULL, "GPIO isr service already installed", ESP_ERR_INVALID_STATE);
esp_err_t ret;
portENTER_CRITICAL(&gpio_context.gpio_spinlock);
gpio_context.gpio_isr_func = (gpio_isr_func_t *) calloc(GPIO_NUM_MAX, sizeof(gpio_isr_func_t));
portEXIT_CRITICAL(&gpio_context.gpio_spinlock);
if (gpio_context.gpio_isr_func == NULL) {
ret = ESP_ERR_NO_MEM;
} else {
ret = gpio_isr_register(gpio_intr_service, NULL, intr_alloc_flags, &gpio_context.gpio_isr_handle);
gpio_driver: add per-pin interrupt handlers 1. add ISR handler apis so that users of different layers can hook their own isr handler on different GPIO. Audio project has different software layers, they need different gpio isr handler for layer instead of processing all GPIO interrupts in one handler. If this kind of calling a handler from isr is not proper, please kindly point out. 2. add gpio example code. 3. improve gpio.rst 4. add readme for gpio example Squashed commits: [278e50f] update: GPIO 1. coding style, add a space between conditional or loop keyword and an opening paren. 2. modify some return value and doc 3. use printf in example code Squashed commits: [efb23bb] minor change of comment
2016-12-24 20:45:57 +08:00
}
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
return ret;
gpio_driver: add per-pin interrupt handlers 1. add ISR handler apis so that users of different layers can hook their own isr handler on different GPIO. Audio project has different software layers, they need different gpio isr handler for layer instead of processing all GPIO interrupts in one handler. If this kind of calling a handler from isr is not proper, please kindly point out. 2. add gpio example code. 3. improve gpio.rst 4. add readme for gpio example Squashed commits: [278e50f] update: GPIO 1. coding style, add a space between conditional or loop keyword and an opening paren. 2. modify some return value and doc 3. use printf in example code Squashed commits: [efb23bb] minor change of comment
2016-12-24 20:45:57 +08:00
}
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
esp_err_t gpio_isr_handler_add(gpio_num_t gpio_num, gpio_isr_t isr_handler, void *args)
gpio_driver: add per-pin interrupt handlers 1. add ISR handler apis so that users of different layers can hook their own isr handler on different GPIO. Audio project has different software layers, they need different gpio isr handler for layer instead of processing all GPIO interrupts in one handler. If this kind of calling a handler from isr is not proper, please kindly point out. 2. add gpio example code. 3. improve gpio.rst 4. add readme for gpio example Squashed commits: [278e50f] update: GPIO 1. coding style, add a space between conditional or loop keyword and an opening paren. 2. modify some return value and doc 3. use printf in example code Squashed commits: [efb23bb] minor change of comment
2016-12-24 20:45:57 +08:00
{
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
GPIO_CHECK(gpio_context.gpio_isr_func != NULL, "GPIO isr service is not installed, call gpio_install_isr_service() first", ESP_ERR_INVALID_STATE);
gpio_driver: add per-pin interrupt handlers 1. add ISR handler apis so that users of different layers can hook their own isr handler on different GPIO. Audio project has different software layers, they need different gpio isr handler for layer instead of processing all GPIO interrupts in one handler. If this kind of calling a handler from isr is not proper, please kindly point out. 2. add gpio example code. 3. improve gpio.rst 4. add readme for gpio example Squashed commits: [278e50f] update: GPIO 1. coding style, add a space between conditional or loop keyword and an opening paren. 2. modify some return value and doc 3. use printf in example code Squashed commits: [efb23bb] minor change of comment
2016-12-24 20:45:57 +08:00
GPIO_CHECK(GPIO_IS_VALID_GPIO(gpio_num), "GPIO number error", ESP_ERR_INVALID_ARG);
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
portENTER_CRITICAL(&gpio_context.gpio_spinlock);
gpio_driver: add per-pin interrupt handlers 1. add ISR handler apis so that users of different layers can hook their own isr handler on different GPIO. Audio project has different software layers, they need different gpio isr handler for layer instead of processing all GPIO interrupts in one handler. If this kind of calling a handler from isr is not proper, please kindly point out. 2. add gpio example code. 3. improve gpio.rst 4. add readme for gpio example Squashed commits: [278e50f] update: GPIO 1. coding style, add a space between conditional or loop keyword and an opening paren. 2. modify some return value and doc 3. use printf in example code Squashed commits: [efb23bb] minor change of comment
2016-12-24 20:45:57 +08:00
gpio_intr_disable(gpio_num);
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
if (gpio_context.gpio_isr_func) {
gpio_context.gpio_isr_func[gpio_num].fn = isr_handler;
gpio_context.gpio_isr_func[gpio_num].args = args;
gpio_driver: add per-pin interrupt handlers 1. add ISR handler apis so that users of different layers can hook their own isr handler on different GPIO. Audio project has different software layers, they need different gpio isr handler for layer instead of processing all GPIO interrupts in one handler. If this kind of calling a handler from isr is not proper, please kindly point out. 2. add gpio example code. 3. improve gpio.rst 4. add readme for gpio example Squashed commits: [278e50f] update: GPIO 1. coding style, add a space between conditional or loop keyword and an opening paren. 2. modify some return value and doc 3. use printf in example code Squashed commits: [efb23bb] minor change of comment
2016-12-24 20:45:57 +08:00
}
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
gpio_intr_enable_on_core (gpio_num, esp_intr_get_cpu(gpio_context.gpio_isr_handle));
portEXIT_CRITICAL(&gpio_context.gpio_spinlock);
gpio_driver: add per-pin interrupt handlers 1. add ISR handler apis so that users of different layers can hook their own isr handler on different GPIO. Audio project has different software layers, they need different gpio isr handler for layer instead of processing all GPIO interrupts in one handler. If this kind of calling a handler from isr is not proper, please kindly point out. 2. add gpio example code. 3. improve gpio.rst 4. add readme for gpio example Squashed commits: [278e50f] update: GPIO 1. coding style, add a space between conditional or loop keyword and an opening paren. 2. modify some return value and doc 3. use printf in example code Squashed commits: [efb23bb] minor change of comment
2016-12-24 20:45:57 +08:00
return ESP_OK;
}
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
esp_err_t gpio_isr_handler_remove(gpio_num_t gpio_num)
gpio_driver: add per-pin interrupt handlers 1. add ISR handler apis so that users of different layers can hook their own isr handler on different GPIO. Audio project has different software layers, they need different gpio isr handler for layer instead of processing all GPIO interrupts in one handler. If this kind of calling a handler from isr is not proper, please kindly point out. 2. add gpio example code. 3. improve gpio.rst 4. add readme for gpio example Squashed commits: [278e50f] update: GPIO 1. coding style, add a space between conditional or loop keyword and an opening paren. 2. modify some return value and doc 3. use printf in example code Squashed commits: [efb23bb] minor change of comment
2016-12-24 20:45:57 +08:00
{
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
GPIO_CHECK(gpio_context.gpio_isr_func != NULL, "GPIO isr service is not installed, call gpio_install_isr_service() first", ESP_ERR_INVALID_STATE);
GPIO_CHECK(GPIO_IS_VALID_GPIO(gpio_num), "GPIO number error", ESP_ERR_INVALID_ARG);
portENTER_CRITICAL(&gpio_context.gpio_spinlock);
gpio_intr_disable(gpio_num);
if (gpio_context.gpio_isr_func) {
gpio_context.gpio_isr_func[gpio_num].fn = NULL;
gpio_context.gpio_isr_func[gpio_num].args = NULL;
gpio_driver: add per-pin interrupt handlers 1. add ISR handler apis so that users of different layers can hook their own isr handler on different GPIO. Audio project has different software layers, they need different gpio isr handler for layer instead of processing all GPIO interrupts in one handler. If this kind of calling a handler from isr is not proper, please kindly point out. 2. add gpio example code. 3. improve gpio.rst 4. add readme for gpio example Squashed commits: [278e50f] update: GPIO 1. coding style, add a space between conditional or loop keyword and an opening paren. 2. modify some return value and doc 3. use printf in example code Squashed commits: [efb23bb] minor change of comment
2016-12-24 20:45:57 +08:00
}
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
portEXIT_CRITICAL(&gpio_context.gpio_spinlock);
return ESP_OK;
gpio_driver: add per-pin interrupt handlers 1. add ISR handler apis so that users of different layers can hook their own isr handler on different GPIO. Audio project has different software layers, they need different gpio isr handler for layer instead of processing all GPIO interrupts in one handler. If this kind of calling a handler from isr is not proper, please kindly point out. 2. add gpio example code. 3. improve gpio.rst 4. add readme for gpio example Squashed commits: [278e50f] update: GPIO 1. coding style, add a space between conditional or loop keyword and an opening paren. 2. modify some return value and doc 3. use printf in example code Squashed commits: [efb23bb] minor change of comment
2016-12-24 20:45:57 +08:00
}
tools: Mass fixing of empty prototypes (for -Wstrict-prototypes)
2019-07-16 16:33:30 +07:00
void gpio_uninstall_isr_service(void)
gpio_driver: add per-pin interrupt handlers 1. add ISR handler apis so that users of different layers can hook their own isr handler on different GPIO. Audio project has different software layers, they need different gpio isr handler for layer instead of processing all GPIO interrupts in one handler. If this kind of calling a handler from isr is not proper, please kindly point out. 2. add gpio example code. 3. improve gpio.rst 4. add readme for gpio example Squashed commits: [278e50f] update: GPIO 1. coding style, add a space between conditional or loop keyword and an opening paren. 2. modify some return value and doc 3. use printf in example code Squashed commits: [efb23bb] minor change of comment
2016-12-24 20:45:57 +08:00
{
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
if (gpio_context.gpio_isr_func == NULL) {
gpio_driver: add per-pin interrupt handlers 1. add ISR handler apis so that users of different layers can hook their own isr handler on different GPIO. Audio project has different software layers, they need different gpio isr handler for layer instead of processing all GPIO interrupts in one handler. If this kind of calling a handler from isr is not proper, please kindly point out. 2. add gpio example code. 3. improve gpio.rst 4. add readme for gpio example Squashed commits: [278e50f] update: GPIO 1. coding style, add a space between conditional or loop keyword and an opening paren. 2. modify some return value and doc 3. use printf in example code Squashed commits: [efb23bb] minor change of comment
2016-12-24 20:45:57 +08:00
return;
}
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
portENTER_CRITICAL(&gpio_context.gpio_spinlock);
esp_intr_free(gpio_context.gpio_isr_handle);
free(gpio_context.gpio_isr_func);
gpio_context.gpio_isr_func = NULL;
gpio_context.isr_core_id = GPIO_ISR_CORE_ID_UNINIT;
portEXIT_CRITICAL(&gpio_context.gpio_spinlock);
gpio_driver: add per-pin interrupt handlers 1. add ISR handler apis so that users of different layers can hook their own isr handler on different GPIO. Audio project has different software layers, they need different gpio isr handler for layer instead of processing all GPIO interrupts in one handler. If this kind of calling a handler from isr is not proper, please kindly point out. 2. add gpio example code. 3. improve gpio.rst 4. add readme for gpio example Squashed commits: [278e50f] update: GPIO 1. coding style, add a space between conditional or loop keyword and an opening paren. 2. modify some return value and doc 3. use printf in example code Squashed commits: [efb23bb] minor change of comment
2016-12-24 20:45:57 +08:00
return;
}
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
bugfix(GPIO): Fixed the bug that GPIO enables interrupts on one core, but registers interrupt service routines on another core closes https://github.com/espressif/esp-idf/issues/2808 closes https://github.com/espressif/esp-idf/issues/2845
2019-07-18 11:34:49 +08:00
static void gpio_isr_register_on_core_static(void *param)
{
gpio_isr_alloc_t *p = (gpio_isr_alloc_t *)param;
//We need to check the return value.
p->ret = esp_intr_alloc(p->source, p->intr_alloc_flags, p->fn, p->arg, p->handle);
}
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
esp_err_t gpio_isr_register(void (*fn)(void *), void *arg, int intr_alloc_flags, gpio_isr_handle_t *handle)
Convert Windows -> Unix line ends in gpio.c
2016-10-08 14:12:55 +08:00
{
Minor changes for driver 1. remove "\n" when calling ESP_LOGX APIs. 2. modify uart_event_t for uart rx data. 3. use MICRO for uart inverse value 4. add uart_tx_data_t for internal tx function.
2016-11-07 14:16:52 +08:00
GPIO_CHECK(fn, "GPIO ISR null", ESP_ERR_INVALID_ARG);
bugfix(GPIO): Fixed the bug that GPIO enables interrupts on one core, but registers interrupt service routines on another core closes https://github.com/espressif/esp-idf/issues/2808 closes https://github.com/espressif/esp-idf/issues/2845
2019-07-18 11:34:49 +08:00
gpio_isr_alloc_t p;
p.source = ETS_GPIO_INTR_SOURCE;
p.intr_alloc_flags = intr_alloc_flags;
p.fn = fn;
p.arg = arg;
p.handle = handle;
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
portENTER_CRITICAL(&gpio_context.gpio_spinlock);
if(gpio_context.isr_core_id == GPIO_ISR_CORE_ID_UNINIT) {
gpio_context.isr_core_id = xPortGetCoreID();
bugfix(GPIO): Fixed the bug that GPIO enables interrupts on one core, but registers interrupt service routines on another core closes https://github.com/espressif/esp-idf/issues/2808 closes https://github.com/espressif/esp-idf/issues/2845
2019-07-18 11:34:49 +08:00
}
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
portEXIT_CRITICAL(&gpio_context.gpio_spinlock);
ipc: prevent code getting pulled in for unicore configuration
2019-08-15 12:35:59 +05:30
esp_err_t ret;
#if CONFIG_FREERTOS_UNICORE
gpio_isr_register_on_core_static(&p);
ret = ESP_OK;
#else /* CONFIG_FREERTOS_UNICORE */
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
ret = esp_ipc_call_blocking(gpio_context.isr_core_id, gpio_isr_register_on_core_static, (void *)&p);
ipc: prevent code getting pulled in for unicore configuration
2019-08-15 12:35:59 +05:30
#endif /* !CONFIG_FREERTOS_UNICORE */
bugfix(GPIO): Fixed the bug that GPIO enables interrupts on one core, but registers interrupt service routines on another core closes https://github.com/espressif/esp-idf/issues/2808 closes https://github.com/espressif/esp-idf/issues/2845
2019-07-18 11:34:49 +08:00
if(ret != ESP_OK || p.ret != ESP_OK) {
return ESP_ERR_NOT_FOUND;
}
return ESP_OK;
Convert Windows -> Unix line ends in gpio.c
2016-10-08 14:12:55 +08:00
}
esp_err_t gpio_wakeup_enable(gpio_num_t gpio_num, gpio_int_type_t intr_type)
{
Minor changes for driver 1. remove "\n" when calling ESP_LOGX APIs. 2. modify uart_event_t for uart rx data. 3. use MICRO for uart inverse value 4. add uart_tx_data_t for internal tx function.
2016-11-07 14:16:52 +08:00
GPIO_CHECK(GPIO_IS_VALID_GPIO(gpio_num), "GPIO number error", ESP_ERR_INVALID_ARG);
Convert Windows -> Unix line ends in gpio.c
2016-10-08 14:12:55 +08:00
esp_err_t ret = ESP_OK;
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
if ((intr_type == GPIO_INTR_LOW_LEVEL) || (intr_type == GPIO_INTR_HIGH_LEVEL)) {
if (rtc_gpio_is_valid_gpio(gpio_num)) {
driver/gpio: support wakeup function for RTC IOs
2018-08-14 01:57:32 +03:00
ret = rtc_gpio_wakeup_enable(gpio_num, intr_type);
} else {
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
portENTER_CRITICAL(&gpio_context.gpio_spinlock);
gpio_hal_wakeup_enable(gpio_context.gpio_hal, gpio_num, intr_type);
portEXIT_CRITICAL(&gpio_context.gpio_spinlock);
driver/gpio: support wakeup function for RTC IOs
2018-08-14 01:57:32 +03:00
}
Convert Windows -> Unix line ends in gpio.c
2016-10-08 14:12:55 +08:00
} else {
driver/gpio: support wakeup function for RTC IOs
2018-08-14 01:57:32 +03:00
ESP_LOGE(GPIO_TAG, "GPIO wakeup only supports level mode, but edge mode set. gpio_num:%u", gpio_num);
Convert Windows -> Unix line ends in gpio.c
2016-10-08 14:12:55 +08:00
ret = ESP_ERR_INVALID_ARG;
}
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
Convert Windows -> Unix line ends in gpio.c
2016-10-08 14:12:55 +08:00
return ret;
}
esp_err_t gpio_wakeup_disable(gpio_num_t gpio_num)
{
Minor changes for driver 1. remove "\n" when calling ESP_LOGX APIs. 2. modify uart_event_t for uart rx data. 3. use MICRO for uart inverse value 4. add uart_tx_data_t for internal tx function.
2016-11-07 14:16:52 +08:00
GPIO_CHECK(GPIO_IS_VALID_GPIO(gpio_num), "GPIO number error", ESP_ERR_INVALID_ARG);
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
esp_err_t ret = ESP_OK;
if (rtc_gpio_is_valid_gpio(gpio_num)) {
ret = rtc_gpio_wakeup_disable(gpio_num);
} else {
portENTER_CRITICAL(&gpio_context.gpio_spinlock);
gpio_hal_wakeup_disable(gpio_context.gpio_hal, gpio_num);
portEXIT_CRITICAL(&gpio_context.gpio_spinlock);
}
return ret;
Convert Windows -> Unix line ends in gpio.c
2016-10-08 14:12:55 +08:00
}
feature(gpio): add APIs to set and get pad drive capability. RTC pads use RTC registers to contol drive capability.
2017-07-17 15:38:19 +08:00
esp_err_t gpio_set_drive_capability(gpio_num_t gpio_num, gpio_drive_cap_t strength)
{
GPIO_CHECK(GPIO_IS_VALID_OUTPUT_GPIO(gpio_num), "GPIO number error", ESP_ERR_INVALID_ARG);
GPIO_CHECK(strength < GPIO_DRIVE_CAP_MAX, "GPIO drive capability error", ESP_ERR_INVALID_ARG);
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
esp_err_t ret = ESP_OK;
bugfix(gpio):fix esp32 s2 rtc io issue * Modify the function implementation of ESP32-S2 RTC GPIO On ESP32 those PADs which have RTC functions must set pullup/down/capability via RTC register. On ESP32-S2, Digital IOs have their own registers to control pullup/down/capability, independent with RTC registers. * Add ESP32-S2 support of unit test * Modify the pull-up test of unit test * Modify the interrupt test of unit test * Modify input and output mode test of unit test
2019-11-26 20:00:24 +08:00
if (!rtc_gpio_is_valid_gpio(gpio_num) || GPIO_SUPPORTS_RTC_INDEPENDENT) {
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
portENTER_CRITICAL(&gpio_context.gpio_spinlock);
gpio_hal_set_drive_capability(gpio_context.gpio_hal, gpio_num, strength);
portEXIT_CRITICAL(&gpio_context.gpio_spinlock);
bugfix(gpio):fix esp32 s2 rtc io issue * Modify the function implementation of ESP32-S2 RTC GPIO On ESP32 those PADs which have RTC functions must set pullup/down/capability via RTC register. On ESP32-S2, Digital IOs have their own registers to control pullup/down/capability, independent with RTC registers. * Add ESP32-S2 support of unit test * Modify the pull-up test of unit test * Modify the interrupt test of unit test * Modify input and output mode test of unit test
2019-11-26 20:00:24 +08:00
} else {
ret = rtc_gpio_set_drive_capability(gpio_num, strength);
feature(gpio): add APIs to set and get pad drive capability. RTC pads use RTC registers to contol drive capability.
2017-07-17 15:38:19 +08:00
}
bugfix(gpio):fix esp32 s2 rtc io issue * Modify the function implementation of ESP32-S2 RTC GPIO On ESP32 those PADs which have RTC functions must set pullup/down/capability via RTC register. On ESP32-S2, Digital IOs have their own registers to control pullup/down/capability, independent with RTC registers. * Add ESP32-S2 support of unit test * Modify the pull-up test of unit test * Modify the interrupt test of unit test * Modify input and output mode test of unit test
2019-11-26 20:00:24 +08:00
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
return ret;
feature(gpio): add APIs to set and get pad drive capability. RTC pads use RTC registers to contol drive capability.
2017-07-17 15:38:19 +08:00
}
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
esp_err_t gpio_get_drive_capability(gpio_num_t gpio_num, gpio_drive_cap_t *strength)
feature(gpio): add APIs to set and get pad drive capability. RTC pads use RTC registers to contol drive capability.
2017-07-17 15:38:19 +08:00
{
GPIO_CHECK(GPIO_IS_VALID_OUTPUT_GPIO(gpio_num), "GPIO number error", ESP_ERR_INVALID_ARG);
GPIO_CHECK(strength != NULL, "GPIO drive capability pointer error", ESP_ERR_INVALID_ARG);
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
esp_err_t ret = ESP_OK;
bugfix(gpio):fix esp32 s2 rtc io issue * Modify the function implementation of ESP32-S2 RTC GPIO On ESP32 those PADs which have RTC functions must set pullup/down/capability via RTC register. On ESP32-S2, Digital IOs have their own registers to control pullup/down/capability, independent with RTC registers. * Add ESP32-S2 support of unit test * Modify the pull-up test of unit test * Modify the interrupt test of unit test * Modify input and output mode test of unit test
2019-11-26 20:00:24 +08:00
if (!rtc_gpio_is_valid_gpio(gpio_num) || GPIO_SUPPORTS_RTC_INDEPENDENT) {
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
portENTER_CRITICAL(&gpio_context.gpio_spinlock);
gpio_hal_get_drive_capability(gpio_context.gpio_hal, gpio_num, strength);
portEXIT_CRITICAL(&gpio_context.gpio_spinlock);
bugfix(gpio):fix esp32 s2 rtc io issue * Modify the function implementation of ESP32-S2 RTC GPIO On ESP32 those PADs which have RTC functions must set pullup/down/capability via RTC register. On ESP32-S2, Digital IOs have their own registers to control pullup/down/capability, independent with RTC registers. * Add ESP32-S2 support of unit test * Modify the pull-up test of unit test * Modify the interrupt test of unit test * Modify input and output mode test of unit test
2019-11-26 20:00:24 +08:00
} else {
ret = rtc_gpio_get_drive_capability(gpio_num, strength);
feature(gpio): add APIs to set and get pad drive capability. RTC pads use RTC registers to contol drive capability.
2017-07-17 15:38:19 +08:00
}
bugfix(gpio):fix esp32 s2 rtc io issue * Modify the function implementation of ESP32-S2 RTC GPIO On ESP32 those PADs which have RTC functions must set pullup/down/capability via RTC register. On ESP32-S2, Digital IOs have their own registers to control pullup/down/capability, independent with RTC registers. * Add ESP32-S2 support of unit test * Modify the pull-up test of unit test * Modify the interrupt test of unit test * Modify input and output mode test of unit test
2019-11-26 20:00:24 +08:00
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
return ret;
feature(gpio): add APIs to set and get pad drive capability. RTC pads use RTC registers to contol drive capability.
2017-07-17 15:38:19 +08:00
}
driver(gpio): Add api support digital pad hold function.
2018-04-03 22:09:30 +08:00
esp_err_t gpio_hold_en(gpio_num_t gpio_num)
{
GPIO_CHECK(GPIO_IS_VALID_OUTPUT_GPIO(gpio_num), "Only output-capable GPIO support this function", ESP_ERR_NOT_SUPPORTED);
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
int ret = ESP_OK;
if (rtc_gpio_is_valid_gpio(gpio_num)) {
ret = rtc_gpio_hold_en(gpio_num);
Driver: gpio and rtcio dirver update
2019-06-13 15:37:58 +08:00
} else if (GPIO_HOLD_MASK[gpio_num]) {
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
portENTER_CRITICAL(&gpio_context.gpio_spinlock);
gpio_hal_hold_en(gpio_context.gpio_hal, gpio_num);
portEXIT_CRITICAL(&gpio_context.gpio_spinlock);
driver(gpio): Add api support digital pad hold function.
2018-04-03 22:09:30 +08:00
} else {
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
ret = ESP_ERR_NOT_SUPPORTED;
driver(gpio): Add api support digital pad hold function.
2018-04-03 22:09:30 +08:00
}
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
return ret;
driver(gpio): Add api support digital pad hold function.
2018-04-03 22:09:30 +08:00
}
esp_err_t gpio_hold_dis(gpio_num_t gpio_num)
{
GPIO_CHECK(GPIO_IS_VALID_OUTPUT_GPIO(gpio_num), "Only output-capable GPIO support this function", ESP_ERR_NOT_SUPPORTED);
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
int ret = ESP_OK;
if (rtc_gpio_is_valid_gpio(gpio_num)) {
ret = rtc_gpio_hold_dis(gpio_num);
Driver: gpio and rtcio dirver update
2019-06-13 15:37:58 +08:00
}else if (GPIO_HOLD_MASK[gpio_num]) {
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
portENTER_CRITICAL(&gpio_context.gpio_spinlock);
gpio_hal_hold_dis(gpio_context.gpio_hal, gpio_num);
portEXIT_CRITICAL(&gpio_context.gpio_spinlock);
Driver: gpio and rtcio dirver update
2019-06-13 15:37:58 +08:00
} else {
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
ret = ESP_ERR_NOT_SUPPORTED;
Driver: gpio and rtcio dirver update
2019-06-13 15:37:58 +08:00
}
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
return ret;
feat(gpio): add function allowing switching input source from GPIO back to IOMUX
2018-04-24 01:23:12 +08:00
}
driver(gpio): fixed digital gpio unable hold bug during deep-sleep.
2018-12-07 21:44:43 +08:00
void gpio_deep_sleep_hold_en(void)
{
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
portENTER_CRITICAL(&gpio_context.gpio_spinlock);
gpio_hal_deep_sleep_hold_en(gpio_context.gpio_hal);
portEXIT_CRITICAL(&gpio_context.gpio_spinlock);
driver(gpio): fixed digital gpio unable hold bug during deep-sleep.
2018-12-07 21:44:43 +08:00
}
void gpio_deep_sleep_hold_dis(void)
{
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
portENTER_CRITICAL(&gpio_context.gpio_spinlock);
gpio_hal_deep_sleep_hold_dis(gpio_context.gpio_hal);
portEXIT_CRITICAL(&gpio_context.gpio_spinlock);
driver(gpio): fixed digital gpio unable hold bug during deep-sleep.
2018-12-07 21:44:43 +08:00
}
bugfix(gpio):fix esp32 s2 rtc io issue * Modify the function implementation of ESP32-S2 RTC GPIO On ESP32 those PADs which have RTC functions must set pullup/down/capability via RTC register. On ESP32-S2, Digital IOs have their own registers to control pullup/down/capability, independent with RTC registers. * Add ESP32-S2 support of unit test * Modify the pull-up test of unit test * Modify the interrupt test of unit test * Modify input and output mode test of unit test
2019-11-26 20:00:24 +08:00
#if GPIO_SUPPORTS_FORCE_HOLD
Driver: gpio and rtcio dirver update
2019-06-13 15:37:58 +08:00
esp_err_t gpio_force_hold_all()
{
rtc_gpio_force_hold_all();
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
portENTER_CRITICAL(&gpio_context.gpio_spinlock);
bugfix(gpio):fix esp32 s2 rtc io issue * Modify the function implementation of ESP32-S2 RTC GPIO On ESP32 those PADs which have RTC functions must set pullup/down/capability via RTC register. On ESP32-S2, Digital IOs have their own registers to control pullup/down/capability, independent with RTC registers. * Add ESP32-S2 support of unit test * Modify the pull-up test of unit test * Modify the interrupt test of unit test * Modify input and output mode test of unit test
2019-11-26 20:00:24 +08:00
gpio_hal_force_hold_all(gpio_context.gpio_hal);
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
portEXIT_CRITICAL(&gpio_context.gpio_spinlock);
Driver: gpio and rtcio dirver update
2019-06-13 15:37:58 +08:00
return ESP_OK;
}
esp_err_t gpio_force_unhold_all()
{
rtc_gpio_force_hold_dis_all();
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
portENTER_CRITICAL(&gpio_context.gpio_spinlock);
bugfix(gpio):fix esp32 s2 rtc io issue * Modify the function implementation of ESP32-S2 RTC GPIO On ESP32 those PADs which have RTC functions must set pullup/down/capability via RTC register. On ESP32-S2, Digital IOs have their own registers to control pullup/down/capability, independent with RTC registers. * Add ESP32-S2 support of unit test * Modify the pull-up test of unit test * Modify the interrupt test of unit test * Modify input and output mode test of unit test
2019-11-26 20:00:24 +08:00
gpio_hal_force_unhold_all(gpio_context.gpio_hal);
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
portEXIT_CRITICAL(&gpio_context.gpio_spinlock);
Driver: gpio and rtcio dirver update
2019-06-13 15:37:58 +08:00
return ESP_OK;
}
#endif
feat(gpio): add function allowing switching input source from GPIO back to IOMUX
2018-04-24 01:23:12 +08:00
void gpio_iomux_in(uint32_t gpio, uint32_t signal_idx)
{
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
gpio_hal_iomux_in(gpio_context.gpio_hal, gpio, signal_idx);
feat(gpio): add function allowing switching input source from GPIO back to IOMUX
2018-04-24 01:23:12 +08:00
}
void gpio_iomux_out(uint8_t gpio_num, int func, bool oen_inv)
{
refactor(gpio): add hal gpio driver
2019-07-15 14:44:15 +08:00
gpio_hal_iomux_out(gpio_context.gpio_hal, gpio_num, func, (uint32_t)oen_inv);
feat(gpio): add function allowing switching input source from GPIO back to IOMUX
2018-04-24 01:23:12 +08:00
}
Reference in New Issue Copy Permalink