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 🤔
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
#PineDio Stack's CST816S Touch Panel seems elusive ... Thanks to PineTime we know everything now!
What's inside a #NuttX Touchscreen Driver
Apache #NuttX RTOS defines a standard data format for Touch Data
Testing the GPIO Interrupt that's triggered ... When we tap #PineDio Stack's CST816S Touch Panel
Here's the Touch Data returned by #PineDio Stack's CST816S Touch Panel
Reading the Touch Data from #PineDio Stack's CST816S Touch Panel
QOTO: Question Others to Teach Ourselves
An inclusive, Academic Freedom, instance
All cultures welcome.
Hate speech and harassment strictly forbidden.