Re: Q: weird hidraw behaviour

2013-10-10 Thread David Herrmann
Hi On Tue, Sep 24, 2013 at 10:56 AM, Mika Westerberg mika.westerb...@linux.intel.com wrote: Hi, I noticed that after commit 212a871a393 (HID: hidraw: correctly deallocate memory on device disconnect) hidraw doesn't close the underlying hid device when the device node is closed last time.

Re: Q: weird hidraw behaviour

2013-10-10 Thread Mika Westerberg
On Thu, Oct 10, 2013 at 11:26:45AM +0200, David Herrmann wrote: Hi On Tue, Sep 24, 2013 at 10:56 AM, Mika Westerberg mika.westerb...@linux.intel.com wrote: Hi, I noticed that after commit 212a871a393 (HID: hidraw: correctly deallocate memory on device disconnect) hidraw doesn't close

Re: Q: weird hidraw behaviour

2013-10-10 Thread David Herrmann
Hi On Thu, Oct 10, 2013 at 11:39 AM, Mika Westerberg mika.westerb...@linux.intel.com wrote: On Thu, Oct 10, 2013 at 11:26:45AM +0200, David Herrmann wrote: I don't know whether it's intentional, but it is hardcoded this way now. Logic is, -close() is called on hidraw_disconnect() that is,

Q: weird hidraw behaviour

2013-09-24 Thread Mika Westerberg
Hi, I noticed that after commit 212a871a393 (HID: hidraw: correctly deallocate memory on device disconnect) hidraw doesn't close the underlying hid device when the device node is closed last time. For example I have a touch panel (HID over I2C) device with added debug prints in