Merging upstream version 4.23.0.

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

1 files changed, 10 insertions, 9 deletions

diff --git a/upstream/opensuse-tumbleweed/man4/lirc.4 b/upstream/opensuse-tumbleweed/man4/lirc.4
index dcaae9ba..3660bcd0 100644
--- a/upstream/opensuse-tumbleweed/man4/lirc.4
+++ b/upstream/opensuse-tumbleweed/man4/lirc.4
@@ -2,7 +2,7 @@
 .\" Copyright (c) 2018, Sean Young <sean@mess.org>
 .\"
 .\" SPDX-License-Identifier: GPL-2.0-or-later
-.TH lirc 4 2023-05-03 "Linux man-pages 6.05.01"
+.TH lirc 4 2024-05-02 "Linux man-pages (unreleased)"
 .SH NAME
 lirc \- lirc devices
 .SH DESCRIPTION
@@ -13,7 +13,7 @@ bidirectional interface to infra-red (IR) remotes.
 Most of these devices can receive, and some can send.
 When receiving or sending data, the driver works in two different modes
 depending on the underlying hardware.
-.PP
+.P
 Some hardware (typically TV-cards) decodes the IR signal internally
 and provides decoded button presses as scancode values.
 Drivers for this kind of hardware work in
@@ -23,7 +23,7 @@ Such hardware usually does not support sending IR signals.
 Furthermore, such hardware can only decode a limited set of IR protocols,
 usually only the protocol of the specific remote which is
 bundled with, for example, a TV-card.
-.PP
+.P
 Other hardware provides a stream of pulse/space durations.
 Such drivers work in
 .B LIRC_MODE_MODE2
@@ -39,7 +39,7 @@ and attached to the
 device.
 Sometimes, this kind of hardware also supports
 sending IR data.
-.PP
+.P
 The \fBLIRC_GET_FEATURES\fR ioctl (see below) allows probing for whether
 receiving and sending is supported, and in which modes, amongst other
 features.
@@ -119,7 +119,7 @@ device cannot transmit.
 \&
 int ioctl(int fd, int cmd, int *val);
 .fi
-.PP
+.P
 The following
 .BR ioctl (2)
 operations are provided by the
@@ -132,7 +132,7 @@ hardware settings.
 .TP 4
 .BR LIRC_GET_FEATURES " (\fIvoid\fP)"
 Returns a bit mask of combined features bits; see FEATURES.
-.PP
+.P
 If a device returns an error code for
 .BR LIRC_GET_FEATURES ,
 it is safe to assume it is not a
@@ -215,8 +215,9 @@ describes the pulse width as a percentage of the total cycle.
 Currently, no special meaning is defined for 0 or 100, but the values
 are reserved for future use.
 .TP
-.BR LIRC_GET_MIN_TIMEOUT " (\fIvoid\fP)", " "\
-LIRC_GET_MAX_TIMEOUT " (\fIvoid\fP)"
+.BI LIRC_GET_MIN_TIMEOUT( void )
+.TQ
+.BI LIRC_GET_MAX_TIMEOUT( void )
 Some devices have internal timers that can be used to detect when
 there has been no IR activity for a long time.
 This can help
@@ -417,6 +418,6 @@ Users of older kernels could use the file bundled in
 .\"
 .SH SEE ALSO
 \fBir\-ctl\fP(1), \fBlircd\fP(8),\ \fBbpf\fP(2)
-.PP
+.P
 .UR https://www.kernel.org/\:doc/\:html/\:latest/\:userspace\-api/\:media/\:rc/\:lirc\-dev.html
 .UE