On 02/05/2013 12:40 AM, NeilBrown wrote:
On Thu, 31 Jan 2013 15:25:43 +0200 "ivan.khoronzhuk"
wrote:
On 01/28/2013 08:51 PM, NeilBrown wrote:
On Mon, 28 Jan 2013 18:13:14 +0200 "ivan.khoronzhuk"
wrote:
On 01/22/2013 07:24 AM, NeilBrown wrote:
On Mon, 21 Jan 2013 15:57:18 -0800 Dmitry
On 02/05/2013 12:40 AM, NeilBrown wrote:
On Thu, 31 Jan 2013 15:25:43 +0200 ivan.khoronzhuk ivan.khoronz...@ti.com
wrote:
On 01/28/2013 08:51 PM, NeilBrown wrote:
On Mon, 28 Jan 2013 18:13:14 +0200 ivan.khoronzhuk ivan.khoronz...@ti.com
wrote:
On 01/22/2013 07:24 AM, NeilBrown wrote:
On
On Thu, 31 Jan 2013 15:25:43 +0200 "ivan.khoronzhuk"
wrote:
> On 01/28/2013 08:51 PM, NeilBrown wrote:
> > On Mon, 28 Jan 2013 18:13:14 +0200 "ivan.khoronzhuk"
> >
> > wrote:
> >
> >> On 01/22/2013 07:24 AM, NeilBrown wrote:
> >>> On Mon, 21 Jan 2013 15:57:18 -0800 Dmitry Torokhov
> >>>
On Thu, 31 Jan 2013 15:25:43 +0200 ivan.khoronzhuk ivan.khoronz...@ti.com
wrote:
On 01/28/2013 08:51 PM, NeilBrown wrote:
On Mon, 28 Jan 2013 18:13:14 +0200 ivan.khoronzhuk
ivan.khoronz...@ti.com
wrote:
On 01/22/2013 07:24 AM, NeilBrown wrote:
On Mon, 21 Jan 2013 15:57:18 -0800
On 01/28/2013 08:51 PM, NeilBrown wrote:
On Mon, 28 Jan 2013 18:13:14 +0200 "ivan.khoronzhuk"
wrote:
On 01/22/2013 07:24 AM, NeilBrown wrote:
On Mon, 21 Jan 2013 15:57:18 -0800 Dmitry Torokhov
wrote:
Hi Ivan,
On Mon, Jan 21, 2013 at 03:15:14PM +0200, Ivan Khoronzhuk wrote:
Rebased on
On 01/28/2013 08:51 PM, NeilBrown wrote:
On Mon, 28 Jan 2013 18:13:14 +0200 ivan.khoronzhuk ivan.khoronz...@ti.com
wrote:
On 01/22/2013 07:24 AM, NeilBrown wrote:
On Mon, 21 Jan 2013 15:57:18 -0800 Dmitry Torokhov
dmitry.torok...@gmail.com wrote:
Hi Ivan,
On Mon, Jan 21, 2013 at 03:15:14PM
On Mon, 28 Jan 2013 18:13:14 +0200 "ivan.khoronzhuk"
wrote:
> On 01/22/2013 07:24 AM, NeilBrown wrote:
> > On Mon, 21 Jan 2013 15:57:18 -0800 Dmitry Torokhov
> > wrote:
> >
> >> Hi Ivan,
> >>
> >> On Mon, Jan 21, 2013 at 03:15:14PM +0200, Ivan Khoronzhuk wrote:
> >>> Rebased on
On 01/22/2013 07:24 AM, NeilBrown wrote:
On Mon, 21 Jan 2013 15:57:18 -0800 Dmitry Torokhov
wrote:
Hi Ivan,
On Mon, Jan 21, 2013 at 03:15:14PM +0200, Ivan Khoronzhuk wrote:
Rebased on linux_omap/master.
During suspend/resume the key press can be lost if time of resume
sequence is
On 01/22/2013 07:24 AM, NeilBrown wrote:
On Mon, 21 Jan 2013 15:57:18 -0800 Dmitry Torokhov
dmitry.torok...@gmail.com wrote:
Hi Ivan,
On Mon, Jan 21, 2013 at 03:15:14PM +0200, Ivan Khoronzhuk wrote:
Rebased on linux_omap/master.
During suspend/resume the key press can be lost if time of
On Mon, 28 Jan 2013 18:13:14 +0200 ivan.khoronzhuk ivan.khoronz...@ti.com
wrote:
On 01/22/2013 07:24 AM, NeilBrown wrote:
On Mon, 21 Jan 2013 15:57:18 -0800 Dmitry Torokhov
dmitry.torok...@gmail.com wrote:
Hi Ivan,
On Mon, Jan 21, 2013 at 03:15:14PM +0200, Ivan Khoronzhuk wrote:
On Mon, 21 Jan 2013 15:57:18 -0800 Dmitry Torokhov
wrote:
> Hi Ivan,
>
> On Mon, Jan 21, 2013 at 03:15:14PM +0200, Ivan Khoronzhuk wrote:
> > Rebased on linux_omap/master.
> >
> > During suspend/resume the key press can be lost if time of resume
> > sequence is significant.
> >
> > If press
Hi Ivan,
On Mon, Jan 21, 2013 at 03:15:14PM +0200, Ivan Khoronzhuk wrote:
> Rebased on linux_omap/master.
>
> During suspend/resume the key press can be lost if time of resume
> sequence is significant.
>
> If press event cannot be remembered then the driver can read the
> current button state
Rebased on linux_omap/master.
During suspend/resume the key press can be lost if time of resume
sequence is significant.
If press event cannot be remembered then the driver can read the
current button state only in time of interrupt handling. But in some
cases when time between IRQ and IRQ
Rebased on linux_omap/master.
During suspend/resume the key press can be lost if time of resume
sequence is significant.
If press event cannot be remembered then the driver can read the
current button state only in time of interrupt handling. But in some
cases when time between IRQ and IRQ
Hi Ivan,
On Mon, Jan 21, 2013 at 03:15:14PM +0200, Ivan Khoronzhuk wrote:
Rebased on linux_omap/master.
During suspend/resume the key press can be lost if time of resume
sequence is significant.
If press event cannot be remembered then the driver can read the
current button state only in
On Mon, 21 Jan 2013 15:57:18 -0800 Dmitry Torokhov
dmitry.torok...@gmail.com wrote:
Hi Ivan,
On Mon, Jan 21, 2013 at 03:15:14PM +0200, Ivan Khoronzhuk wrote:
Rebased on linux_omap/master.
During suspend/resume the key press can be lost if time of resume
sequence is significant.
During suspend/resume the key press can be lost if time of resume
sequence is significant.
If press event cannot be remembered then the driver can read the
current button state only in time of interrupt handling. But in some
cases when time between IRQ and IRQ handler is significant we can
read
During suspend/resume the key press can be lost if time of resume
sequence is significant.
If press event cannot be remembered then the driver can read the
current button state only in time of interrupt handling. But in some
cases when time between IRQ and IRQ handler is significant we can
read
18 matches
Mail list logo