bybrooklyn/linux
1
0
Fork 0
mirror of https://github.com/torvalds/linux.git synced 2026-04-19 07:13:56 -04:00
Code Issues Packages Projects Releases Wiki Activity

media: lirc: report ir receiver overflow

Browse Source 
If the driver reports that the hardware had an overflow, report this to
userspace. It would be nice to know when this happens, and not just get
a long space.

This change has been tested with lircd, ir-ctl, and ir-keytable.

Signed-off-by: Sean Young <sean@mess.org>
Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
This commit is contained in:
Sean Young
2022-01-15 11:19:11 +01:00
committed by Mauro Carvalho Chehab
parent 950170d6d2
commit 68a99f6a0e
5 changed files with 30 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
Documentation/userspace-api/media/rc/lirc-dev-intro.rst
View File

@@ -103,11 +103,11 @@ on the following table.
``LIRC_MODE2_PULSE``
Signifies the presence of IR in microseconds.
Signifies the presence of IR in microseconds, also known as *flash*.
``LIRC_MODE2_SPACE``
Signifies absence of IR in microseconds.
Signifies absence of IR in microseconds, also known as *gap*.
``LIRC_MODE2_FREQUENCY``
@@ -121,6 +121,13 @@ on the following table.
to no IR being detected, this packet will be sent, with the number
of microseconds with no IR.
``LIRC_MODE2_OVERFLOW``
Signifies that the IR receiver encounter an overflow, and some IR
is missing. The IR data after this should be correct again. The
actual value is not important, but this is set to 0xffffff by the
kernel for compatibility with lircd.
.. _lirc-mode-pulse:
``LIRC_MODE_PULSE``