On Tue, Nov 10, 2015 at 12:16 AM, Dmitry Torokhov
wrote:
> On Thu, Nov 05, 2015 at 03:37:25PM -0800, Andrew Duggan wrote:
>> From: Benjamin Tissoires
>>
>> If the device has been registered but is not populated, we should not
>> process any incoming interrupt.
>> Make sure the pointers we are fol
On Thu, Nov 05, 2015 at 03:37:25PM -0800, Andrew Duggan wrote:
> From: Benjamin Tissoires
>
> If the device has been registered but is not populated, we should not
> process any incoming interrupt.
> Make sure the pointers we are following are valid.
Why are the interrupts enabled when device is
On Fri, Nov 6, 2015 at 12:37 AM, Andrew Duggan wrote:
> From: Benjamin Tissoires
>
> If the device has been registered but is not populated, we should not
> process any incoming interrupt.
> Make sure the pointers we are following are valid.
>
> Signed-off-by: Benjamin Tissoires
> Tested-by: An
From: Benjamin Tissoires
If the device has been registered but is not populated, we should not
process any incoming interrupt.
Make sure the pointers we are following are valid.
Signed-off-by: Benjamin Tissoires
Tested-by: Andrew Duggan
---
drivers/input/rmi4/rmi_driver.c | 3 +++
1 file chan
From: Benjamin Tissoires
If the device has been registered but is not populated, we should not
process any incoming interrupt.
Make sure the pointers we are following are valid.
Signed-off-by: Benjamin Tissoires
Tested-by: Andrew Duggan
---
drivers/input/rmi4/rmi_driver.c | 3 +++
1 file chan
