Hi! > We are still missing handling for errata i689 related issues for the > case where we never see a key up interrupt for the last pressed key. > > To fix the issue, we must scan the key state again after the keyboard > controller has idled to check if a key up event was missed. This is > described in the omap4 silicon errata documentation for Errata ID i689 > "1.32 Keyboard Key Up Event Can Be Missed": > > "When a key is released for a time shorter than the debounce time, > in-between 2 key press (KP1 and KP2), the keyboard state machine will go > to idle mode and will never detect the key release (after KP1, and also > after KP2), and thus will never generate a new IRQ indicating the key > release." > > We can use PM runtime autosuspend features to check the keyboard state > after it enters idle. I thought about this and... is it reasonable? Autosuspend is now required for correct operation. But autosuspend is optional feature, configurable by user, and may not be available depending on .config. Do we need some other solution? Pavel -- http://www.livejournal.com/~pavelmachek
Attachment:
signature.asc
Description: Digital signature
