Em Wed, 20 May 2015 10:53:59 +0200 David Härdeman <david@xxxxxxxxxxx> escreveu: > On 2015-03-19 22:50, Sean Young wrote: > > The send mode has to be switched to LIRC_MODE_SCANCODE and then you can > > send one scancode with a write. The encoding is the same as for > > receiving > > scancodes. > > Why do the encoding in-kernel when it can be done in userspace? > > I'd understand if it was hardware that accepted a scancode as input, but > that doesn't seem to be the case? IMO, that makes the interface clearer. Also, the encoding code is needed anyway, as it is needed to setup the wake up keycode on some hardware. So, we already added encoder capabilities at some decoders: 0d830b2d1295 [media] rc: rc-core: Add support for encode_wakeup drivers cf257e288ad3 [media] rc: ir-rc6-decoder: Add encode capability a0466f15b465 [media] rc: ir-rc5-decoder: Add encode capability 1d971d927efa [media] rc: rc-ir-raw: Add Manchester encoder (phase encoder) helper 9869da5bacc5 [media] rc: rc-ir-raw: Add scancode encoder callback > > > FIXME: Currently only the nec encoder can encode IR. We actually need to be sure that the NEC encoder is doing the same way as the RC5/RC6 encoders. Regards, Mauro -- 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
