Fehler #696
Von Maximilian Seesslen vor 9 Tagen aktualisiert
In theory the application could be accessing EEPROM and user can press touch.
The I2C periphery would then get reconfigured, touch get read, returned to application, EEPROM access fails.
This could be fixed by locks. But then the codepath to read touch in applications event loop has to exist anyways.
Processing has to be implement to be called from event loop.
Meanwhile there are deferred signals and a global event loop. This can be easily adapted.
The state-machine can be split: the signal of the input can only handle the interrupt line; the event loop does not know about the line.
The I2C periphery would then get reconfigured, touch get read, returned to application, EEPROM access fails.
This could be fixed by locks. But then the codepath to read touch in applications event loop has to exist anyways.
Processing has to be implement to be called from event loop.
Meanwhile there are deferred signals and a global event loop. This can be easily adapted.
The state-machine can be split: the signal of the input can only handle the interrupt line; the event loop does not know about the line.