Reading the Touch Data from #PineDio Stack's CST816S Touch Panel
https://lupyuen.github.io/articles/touch?12#get-i2c-touch-data
Here's the Touch Data returned by #PineDio Stack's CST816S Touch Panel
https://lupyuen.github.io/articles/touch?11#fetch-touch-data
Testing the GPIO Interrupt that's triggered ... When we tap #PineDio Stack's CST816S Touch Panel
https://lupyuen.github.io/articles/touch?10#test-gpio-interrupt
Initialising the Touch Panel Driver on #PineDio Stack #BL604
https://lupyuen.github.io/articles/touch?8#initialise-driver
What's inside a #NuttX Touchscreen Driver
https://lupyuen.github.io/articles/touch?4#nuttx-touchscreen-drivers
#PineDio Stack's CST816S Touch Panel seems elusive ... Thanks to PineTime we know everything now!
https://lupyuen.github.io/articles/touch?2#cst816s-touch-panel
But for Touch Up Events the Touch Coordinates are invalid ... Our #PineDio Stack driver patches the Touch Coordinates with the data from the last Touch Down Event
LVGL Test App calls read() repeatedly on #PineDio Stack's Touch Panel Driver to get Touch Data ... But it should call poll() instead to block on Touch Data 🤔
IoT Techie and Educator / Apache NuttX PMC