| 1 |
.. SPDX-License-Identifier: GPL-2.0 OR GFDL-1.1-no-invariants-or-later |
| 2 |
|
| 3 |
.. _Remote_controllers_Intro: |
| 4 |
|
| 5 |
************ |
| 6 |
Introduction |
| 7 |
************ |
| 8 |
|
| 9 |
Currently, most analog and digital devices have a Infrared input for |
| 10 |
remote controllers. Each manufacturer has their own type of control. It |
| 11 |
is not rare for the same manufacturer to ship different types of |
| 12 |
controls, depending on the device. |
| 13 |
|
| 14 |
A Remote Controller interface is mapped as a normal evdev/input |
| 15 |
interface, just like a keyboard or a mouse. So, it uses all ioctls |
| 16 |
already defined for any other input devices. |
| 17 |
|
| 18 |
However, remove controllers are more flexible than a normal input |
| 19 |
device, as the IR receiver (and/or transmitter) can be used in |
| 20 |
conjunction with a wide variety of different IR remotes. |
| 21 |
|
| 22 |
In order to allow flexibility, the Remote Controller subsystem allows |
| 23 |
controlling the RC-specific attributes via |
| 24 |
:ref:`the sysfs class nodes <remote_controllers_sysfs_nodes>`. |