mirror of
https://mirrors.bfsu.edu.cn/git/linux.git
synced 2024-12-29 22:14:41 +08:00
60c2820d0f
The name of the subsystem is "media", and not "linux_tv". Also, as we plan to add other stuff there in the future, let's rename also the media uAPI book to media_uapi, to make it clearer. No functional changes. Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
29 lines
835 B
ReStructuredText
29 lines
835 B
ReStructuredText
.. -*- coding: utf-8; mode: rst -*-
|
|
|
|
.. _lirc_dev_intro:
|
|
|
|
************
|
|
Introduction
|
|
************
|
|
|
|
The LIRC device interface is a bi-directional interface for transporting
|
|
raw IR data between userspace and kernelspace. Fundamentally, it is just
|
|
a chardev (/dev/lircX, for X = 0, 1, 2, ...), with a number of standard
|
|
struct file_operations defined on it. With respect to transporting raw
|
|
IR data to and fro, the essential fops are read, write and ioctl.
|
|
|
|
Example dmesg output upon a driver registering w/LIRC:
|
|
|
|
.. code-block:: none
|
|
|
|
$ dmesg |grep lirc_dev
|
|
lirc_dev: IR Remote Control driver registered, major 248
|
|
rc rc0: lirc_dev: driver ir-lirc-codec (mceusb) registered at minor = 0
|
|
|
|
What you should see for a chardev:
|
|
|
|
.. code-block:: none
|
|
|
|
$ ls -l /dev/lirc*
|
|
crw-rw---- 1 root root 248, 0 Jul 2 22:20 /dev/lirc0
|