-
Notifications
You must be signed in to change notification settings - Fork 7.4k
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
feat(touch): Support NG touch driver for P4 #10448
feat(touch): Support NG touch driver for P4 #10448
Conversation
👋 Hello P-R-O-C-H-Y, we appreciate your contribution to this project! Click to see more instructions ...
Review and merge process you can expect ...
|
31ffebf
to
030c07e
Compare
Memory usage test (comparing PR against master branch)The table below shows the summary of memory usage change (decrease - increase) in bytes and percentage for each target.
Click to expand the detailed deltas report [usage change in BYTES]
|
3b0e96c
to
da31968
Compare
tests/validation/touch/touch.ino
Outdated
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.
Does this test work properly on your board ? Mine is the older version and it fails 🤔
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.
On mine P4-EV board v1.4 it worked.
Description of Change
This PR adds support for the new NG Touch Driver, which is currently supports touch V3 (ESP32-P4). There is work in progress for V2 and later for V1 touch versions to be supported by the new touch driver.
The new touch driver is implemented the way, to keep backward compatibility with the old APIs.
To get more features as multiple sampling on different frequencies, we may add/change APIs a bit.
Tests scenarios
Tested locally on P4, also using the touch HW test.
NOTE: Touch deep sleep wakeup is currently not working, fix is needed on driver side. The implementation should be ready.
NOTE 2: Fix is ready and will be merged to IDF master and v5.3 branch.
Related links