Re: [PATCH v2] input: don't call input_dev_release_keys() in resume

2013-12-06 Thread Oskar Andero
Hi Dmitry, On 03:14 Tue 26 Nov , Dmitry Torokhov wrote: > Hi Oskar, > > On Fri, Nov 22, 2013 at 02:27:04PM +0100, Oskar Andero wrote: > > From: Aleksej Makarov > > > > When waking up the platform by pressing a specific key, sending a > > release on that key makes it impossible to react on t

Re: [PATCH v2] input: don't call input_dev_release_keys() in resume

2013-11-25 Thread Dmitry Torokhov
Hi Oskar, On Fri, Nov 22, 2013 at 02:27:04PM +0100, Oskar Andero wrote: > From: Aleksej Makarov > > When waking up the platform by pressing a specific key, sending a > release on that key makes it impossible to react on the event in > user-space. This is fixed by moving the input_reset_device()

[PATCH v2] input: don't call input_dev_release_keys() in resume

2013-11-22 Thread Oskar Andero
From: Aleksej Makarov When waking up the platform by pressing a specific key, sending a release on that key makes it impossible to react on the event in user-space. This is fixed by moving the input_reset_device() call to resume instead. Cc: Dmitry Torokhov Reviewed-by: Radovan Lekanovic Signe

Re: [PATCH v2] input: don't call input_dev_release_keys() in resume

2013-09-18 Thread Oskar Andero
Hii Dmitry, On 14:09 Thu 25 Jul , Oskar Andero wrote: > From: Aleksej Makarov > > When waking up the platform by pressing a specific key, sending a > release on that key makes it impossible to react on the event in > user-space. This is fixed by moving the input_reset_device() call to > resu

[PATCH v2] input: don't call input_dev_release_keys() in resume

2013-07-25 Thread Oskar Andero
From: Aleksej Makarov When waking up the platform by pressing a specific key, sending a release on that key makes it impossible to react on the event in user-space. This is fixed by moving the input_reset_device() call to resume instead. Cc: Dmitry Torokhov Reviewed-by: Radovan Lekanovic Signe