Re: [PATCH 0/2] input: mt: Add helper function to send end events

Hi Dmitry and Henrik, On 01/01/2014 11:18 AM, Dmitry Torokhov wrote: On Wed, Jan 01, 2014 at 05:19:10PM +0100, Henrik Rydberg wrote: Hi Dmitry, What problematic scenario is this supposed to solve? The 'release on suspend' is only an approximation to the 'close laptop' scenario, it is certain

Re: [PATCH 0/2] input: mt: Add helper function to send end events

On Wed, Jan 01, 2014 at 05:19:10PM +0100, Henrik Rydberg wrote: > Hi Dmitry, > > >> What problematic scenario is this supposed to solve? > >> > >> The 'release on suspend' is only an approximation to the 'close > >> laptop' scenario, it is certainly not correct in the coffee table > >> case, > >

Re: [PATCH 0/2] input: mt: Add helper function to send end events

Hi Dmitry, >> What problematic scenario is this supposed to solve? >> >> The 'release on suspend' is only an approximation to the 'close >> laptop' scenario, it is certainly not correct in the coffee table >> case, > > Why would it not be correct for coffee table? Do we expect the touches > to re

Re: [PATCH 0/2] input: mt: Add helper function to send end events

Hi Henrik, On Tue, Dec 31, 2013 at 10:26:31AM +0100, Henrik Rydberg wrote: > Hi Felipe, > > > Adds a helper function to send end touch events for active tracking ids. > > And also implements it in egalax driver. > > What problematic scenario is this supposed to solve? > > The 'release on suspen

Re: [PATCH 0/2] input: mt: Add helper function to send end events

Hi Felipe, > Adds a helper function to send end touch events for active tracking ids. > And also implements it in egalax driver. What problematic scenario is this supposed to solve? The 'release on suspend' is only an approximation to the 'close laptop' scenario, it is certainly not correct in