1.. Permission is granted to copy, distribute and/or modify this
2.. document under the terms of the GNU Free Documentation License,
3.. Version 1.1 or any later version published by the Free Software
4.. Foundation, with no Invariant Sections, no Front-Cover Texts
5.. and no Back-Cover Texts. A copy of the license is included at
6.. Documentation/userspace-api/media/fdl-appendix.rst.
7..
8.. TODO: replace it to GFDL-1.1-or-later WITH no-invariant-sections
9
10.. _Remote_controllers_Intro:
11
12************
13Introduction
14************
15
16Currently, most analog and digital devices have a Infrared input for
17remote controllers. Each manufacturer has their own type of control. It
18is not rare for the same manufacturer to ship different types of
19controls, depending on the device.
20
21A Remote Controller interface is mapped as a normal evdev/input
22interface, just like a keyboard or a mouse. So, it uses all ioctls
23already defined for any other input devices.
24
25However, remove controllers are more flexible than a normal input
26device, as the IR receiver (and/or transmitter) can be used in
27conjunction with a wide variety of different IR remotes.
28
29In order to allow flexibility, the Remote Controller subsystem allows
30controlling the RC-specific attributes via
31:ref:`the sysfs class nodes <remote_controllers_sysfs_nodes>`.
32