lirc.4: Both ioctls are supported if LIRC_CAN_SET_REC_CARRIER_RANGE is set

Signed-off-by: Sean Young <sean@mess.org>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Sean Young 2018-11-02 11:04:34 +00:00 committed by Michael Kerrisk
parent f75ee79d12
commit 29a1847441
1 changed files with 21 additions and 4 deletions

View File

@ -290,12 +290,16 @@ file descriptors until timeouts were disabled again.
.RE
.TP
.BR LIRC_SET_REC_CARRIER " (\fIint\fP)"
Set the receive carrier frequency (Hz).
Set the upper bound of the receive carrier frequency (Hz). See
.BR LIRC_SET_REC_CARRIER_RANGE .
.TP
.BR LIRC_SET_REC_CARRIER_RANGE " (\fIint\fP)"
After opening device, the first use of this operation
sets the lower bound of the carrier range,
and the second use sets the upper bound (Hz).
Sets the lower bound of the receive carrier frequency (Hz).
For this to take affect, first set the lower bound of using the
.BR LIRC_SET_REC_CARRIER_RANGE
ioctl, and then the upper bound using the
.BR LIRC_SET_REC_CARRIER
ioctl.
.TP
.BR LIRC_SET_MEASURE_CARRIER_MODE " (\fIint\fP)"
Enable
@ -372,10 +376,23 @@ 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 .
Any
.B lirc
device since the drivers were merged in kernel release 2.6.36
must have
.BR LIRC_CAN_SET_REC_CARRIER_RANGE
set if
.BR LIRC_CAN_SET_REC_CARRIER
feature is set.
.TP
.BR LIRC_CAN_SET_REC_CARRIER_RANGE
The driver supports
.BR LIRC_SET_REC_CARRIER_RANGE .
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.
.TP
.BR LIRC_CAN_GET_REC_RESOLUTION
The driver supports