On 1 April 2014 10:04, Austin Lund <austin.lund@xxxxxxxxx> wrote: > Hi, > > I've been having a problem with a GPIO ir device in an i.mx6 arm > system that I have (cubox-i). > > It seems to all work ok, except the output on /dev/lirc0 is not quite > what lircd seems to expect. Lircd wants a long space before the > starting pulse before processing any output. However, no long space is > sent when I check the output (doing "mode2" and a plain hexdump > /dev/lirc0). > > This causes problems in detecting button presses on remotes. > Sometimes it works if you press the buttons quick enough, but after > waiting a while it doesn't work. > > I have been looking at the code for a while now, and it seems that it > has something to do with the lirc codec ignoring reset events (just > returns 0). > > I've made up this patch, but I'm travelling at the moment and haven't > had a chance to actually test it. > > What I'm wondering is if this issue is known, and if my approach is > going down the right path. > > The only alternative I could see is to change the way the gpio ir > driver handles events. It seems to just call ir_raw_event_store_edge > which put a zeroed reset event into the queue. I'm assuming there are > other users of these functions and that it's probably best not to > fiddle with that if possible. > > Thanks. > > PS Please CC me as I'm not subscribed. Just a note that I have tested this patch now and it works. No idea what impact it might have on other users. -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
