From mboxrd@z Thu Jan 1 00:00:00 1970 From: lirc@bartelmus.de (Christoph Bartelmus) Subject: Re: [PATCH 0/9 v2] IR: few fixes, additions and ENE driver Date: 29 Jul 2010 21:35:00 +0200 Message-ID: References: <1280424946.32069.11.camel@maxim-laptop> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Return-path: Sender: linux-media-owner@vger.kernel.org To: maximlevitsky@gmail.com Cc: awalls@md.metrocast.net, linux-input@vger.kernel.org, linux-media@vger.kernel.org, lirc-list@lists.sourceforge.net, mchehab@redhat.com List-Id: linux-input@vger.kernel.org Hi! Maxim Levitsky "maximlevitsky@gmail.com" wrote: [...] >>>>> Could you explain exactly how timeout reports work? [...] >>> So, timeout report is just another sample, with a mark attached, that >>> this is last sample? right? >> >> No, a timeout report is just an additional hint for the decoder that a >> specific amount of time has passed since the last pulse _now_. >> >> [...] >>> In that case, lets do that this way: >>> >>> As soon as timeout is reached, I just send lirc the timeout report. >>> Then next keypress will start with pulse. >> >> When timeout reports are enabled the sequence must be: >> >> where is optional. >> >> lircd will not work when you leave out the space. It must know the exact >> time between the pulses. Some hardware generates timeout reports that are >> too short to distinguish between spaces that are so short that the next >> sequence can be interpreted as a repeat or longer spaces which indicate >> that this is a new key press. > Let me give an example to see if I got that right. > > > Suppose we have this sequence of reports from the driver: > > 500 (pulse) > 200000 (timeout) > 100000000 (space) > 500 (pulse) > > > Is that correct that time between first and second pulse is > '100200000' ? No, it's 100000000. The timeout is optional and just a hint to the decoder how much time has passed already since the last pulse. It does not change the meaning of the next space. Christoph