Re: [PATCH 2/8] ir-rx51: Handle signals properly

2012-08-24 Thread Sean Young
On Wed, Aug 22, 2012 at 10:50:35PM +0300, Timo Kokkonen wrote: The lirc-dev expects the ir-code to be transmitted when the write call returns back to the user space. We should not leave TX ongoing no matter what is the reason we return to the user space. Easiest solution for that is to simply

Re: [PATCH 2/8] ir-rx51: Handle signals properly

2012-08-24 Thread Timo Kokkonen
On 08/24/12 13:03, Sean Young wrote: On Wed, Aug 22, 2012 at 10:50:35PM +0300, Timo Kokkonen wrote: The lirc-dev expects the ir-code to be transmitted when the write call returns back to the user space. We should not leave TX ongoing no matter what is the reason we return to the user space.

[PATCH 2/8] ir-rx51: Handle signals properly

2012-08-22 Thread Timo Kokkonen
The lirc-dev expects the ir-code to be transmitted when the write call returns back to the user space. We should not leave TX ongoing no matter what is the reason we return to the user space. Easiest solution for that is to simply remove interruptible sleeps. The first wait_event_interruptible is