-
Notifications
You must be signed in to change notification settings - Fork 120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
lcd_touch_ft5x06: Fixed missing reset. #216
Conversation
5204c0e
to
d60faf6
Compare
d60faf6
to
aee920d
Compare
94b083b
to
5a4a565
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall LGTM.
But I agree with @Lzw655 that we could use this PR for fixing the 'delete' behavior.
Moreover, I'd suggest moving the 'delete' function to the base component esp_lcd_touch
.
So the esp_lcd_touch
would deregister the ISR and reset all pins to default. What do you think @espzav ?
Becasue this section of code
/* Reset GPIO pin settings */
if (tp->config.int_gpio_num != GPIO_NUM_NC) {
gpio_reset_pin(tp->config.int_gpio_num);
}
/* Reset GPIO pin settings */
if (tp->config.rst_gpio_num != GPIO_NUM_NC) {
gpio_reset_pin(tp->config.rst_gpio_num);
}
is called from every touch driver, but the base esp_lcd_touch can do it, too
I partially agree, but it wouldn't be consistent, because initialization will be in end driver ( |
True, unless we can move the initialization to the base esp_lcd_touch too, we can leave it as it is |
5a4a565
to
dfea0ed
Compare
dfea0ed
to
7f3f266
Compare
@tore-espressif and @Lzw655 Thank you for review. All changes done. @tore-espressif Could we merge it? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
ESP-BSP Pull Request checklist
Change description
Fixed missing reset call in
esp_lcd_touch_ft5x06
.Fixed interrupt level in all touch drivers.
Closes #211