On 10 February 2014 22:50, James Hogan <james.hogan@xxxxxxxxxx> wrote: >> > I suspect it needs some more space at the end too, to be sure that no >> > more bits afterwards are accepted. >> >> I'm sorry but I'm not sure I completely understood what you meant >> here. For RC-5-SZ the entire scancode gets encoded and nothing more. >> Do you mean that the encoder should append some ir silence to the end >> result to make sure the ir sample has ended? > > Yeh something like that. Certainly the raw decoders I've looked at expect a > certain amount of space at the end to avoid decoding part of a longer protocol > (it's in the pulse distance helper as the trailer space timing). Similarly the > IMG hardware decoder has register fields for the free-time to require at the > end of the message. > > In fact it becomes a bit awkward for the raw IR driver for the IMG hardware > which uses edge interrupts, as it has to have a timeout to emit a final repeat > event after 150ms of inactivity, in order for the raw decoders to accept it > (unless you hold the button down in which case the repeat code edges result in > the long space). > Ok, I understand now. I suppose I can append some IR silence to the encoded result. The trailer space timing seems like a good way to do it. I'll create new version of my patches sometime later. Are you working on the wakeup protocol selector sysfs interface? -Antti -- 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
