Hi Sean, On 11/01/2018 09:57 PM, Sean Young wrote: > Signed-off-by: Sean Young <sean@xxxxxxxx> > --- > man4/lirc.4 | 10 ++++++++++ > 1 file changed, 10 insertions(+) > > diff --git a/man4/lirc.4 b/man4/lirc.4 > index 3c2695895..338456ec5 100644 > --- a/man4/lirc.4 > +++ b/man4/lirc.4 > @@ -361,6 +361,16 @@ The driver supports changing the active transmitter(s) using > .BR LIRC_CAN_SET_REC_CARRIER > The driver supports setting the receive carrier frequency using > .BR LIRC_SET_REC_CARRIER . > +If the > +.BR LIRC_CAN_SET_REC_CARRIER_RANGE > +feature is also set, then the lower bound of the carrier must first > +be set using the > +.BR LIRC_SET_REC_CARRIER_RANGE > +ioctl, before using > +.BR LIRC_SET_REC_CARRIER > +ioctl to set the upper bound. > +Any lirc device since the drivers were merged in kernel release 2.6.36 > +have either both features set or not set. Missing work "must" here? Thanks, Michael > .TP > .BR LIRC_CAN_SET_REC_DUTY_CYCLE_RANGE > The driver supports > -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/
