Skip to content
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

4827S043C GT911 Interrupt Pin used? #167

Open
Danez-DK opened this issue May 24, 2024 · 1 comment
Open

4827S043C GT911 Interrupt Pin used? #167

Danez-DK opened this issue May 24, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@Danez-DK
Copy link

Hi,
This is more of a question, than an issue.

As far as I can understand, most 4827S043C boards does not have the Interrupt pin "enabled" by default.
You would have to bridge R17 (connect GT911 to GPIO18), and might have to remove/replace R5, as the GT911 might be too weak to pull GPIO18 low. Also the XPT2046 (U1) chip can be removed, as it is not used for anything, but it is attached to GPIO18.

On theses boards, the program code would have to check if there are changes from the GT911, and use more CPU on that task.

If I make the above changes, should I then change some settings somewhere to make LVGL use interrupt, or does it check if interrupts work, and if not, it just check the GT911 chip for changes all the time?

I could just make the changes, and see what happens, just wanted to ask someone that seems to have a better understanding of how LVGL and hardware input works. :)

You have done a Great job, I really appreciate all the work you have put into this. :)

@rzeldent
Copy link
Owner

If you make modifications, you should update the board definition and assign a pin to the IRQ.
There is support for INT in esp_touch_gt911.c but untested...

Good luck!

@rzeldent rzeldent added the enhancement New feature or request label Jun 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants