Searched +full:linux +full:- +full:event +full:- +full:codes (Results 1 – 25 of 55) sorted by relevance
123
| /Documentation/input/ |
| D | event-codes.rst | 1 .. _input-event-codes:
4 Input event codes
8 The input protocol uses a map of types and codes to express input device values
9 to userspace. This document describes the types and codes and how and when they
12 A single hardware event generates multiple input events. Each input event
13 contains the new value of a single data item. A special event type, EV_SYN, is
15 the same moment in time. In the following, the term "event" refers to a single
16 input event encompassing a type, code, and value.
19 of event codes have changed. However, the state is maintained within the Linux
22 event code values using the EVIOCG* ioctls defined in linux/input.h. The event
[all …]
|
| D | input.rst | 7 :Copyright: |copy| 1999-2001 Vojtech Pavlik <vojtech@ucw.cz> - Sponsored by SuSE
13 all input devices under Linux. Most of the drivers reside in
18 loaded before any other of the input modules - it serves as a way of
22 --------------
27 Event handlers
28 --------------
31 via various interfaces - keystrokes to the kernel, mouse movements via
51 crw-r--r-- 1 root root 13, 63 Mar 28 22:45 mice
61 XFree to this device to use it - GPM should be called like::
63 gpm -t ps2 -m /dev/input/mice
[all …]
|
| D | input_uapi.rst | 4 Linux Input Subsystem userspace API
13 event-codes
14 multi-touch-protocol
|
| /Documentation/devicetree/bindings/input/ |
| D | qcom,pm8941-pwrkey.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/input/qcom,pm8941-pwrkey.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Courtney Cavin <courtney.cavin@sonymobile.com>
11 - Vinod Koul <vkoul@kernel.org>
14 - $ref: input.yaml#
19 - qcom,pm8941-pwrkey
20 - qcom,pm8941-resin
21 - qcom,pmk8350-pwrkey
[all …]
|
| D | gpio-keys.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
4 $id: http://devicetree.org/schemas/input/gpio-keys.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Rob Herring <robh@kernel.org>
15 - gpio-keys
16 - gpio-keys-polled
23 poll-interval: true
26 …"^(button|event|key|switch|(button|event|key|switch)-[a-z0-9-]+|[a-z0-9-]+-(button|event|key|switc…
35 - items:
[all …]
|
| D | atmel,captouch.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Dharma balasubiramani <dharma.b@microchip.com>
17 - $ref: input.yaml#
29 linux,keycodes:
34 - compatible
35 - reg
36 - interrupts
37 - linux,keycodes
[all …]
|
| D | iqs269a.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jeff LaBundy <jeff@labundy.com>
13 - $ref: input.yaml#
16 The Azoteq IQS269A is an 8-channel capacitive touch controller that features
17 additional Hall-effect and inductive sensing capabilities.
24 - azoteq,iqs269a
25 - azoteq,iqs269a-00
26 - azoteq,iqs269a-d0
[all …]
|
| /Documentation/admin-guide/media/ |
| D | remote-controller.rst | 1 .. SPDX-License-Identifier: GPL-2.0
14 pulse/space sequences and then to scan codes, returning such codes to
19 standard Linux input layer. The support for raw mode is provided via LIRC.
22 the `v4l-utils <https://git.linuxtv.org/v4l-utils.git/>`_. It provides
25 - ir-keytable: provides a way to query the remote controller, list the
26 protocols it supports, enable in-kernel support for IR decoder or
27 switch the protocol and to test the reception of scan codes;
29 - ir-ctl: provide tools to handle remote controllers that support raw mode
32 Usually, the remote controller module is auto-loaded when the TV card is
34 ir-kbd-i2c module.
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-event_source-devices-hv_gpci | 3 Contact: Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
4 Description: Read-only. Attribute group to describe the magic bits
6 (See ABI/testing/sysfs-bus-event_source-devices-format).
12 counter_info_version = "config:16-23"
13 length = "config:24-31"
14 partition_id = "config:32-63"
15 request = "config:0-31"
16 sibling_part_id = "config:32-63"
17 hw_chip_id = "config:32-63"
18 offset = "config:32-63"
[all …]
|
| /Documentation/userspace-api/gpio/ |
| D | gpio-lineevent-data-read.rst | 1 .. SPDX-License-Identifier: GPL-2.0
11 gpio-v2-line-event-read.rst.
16 GPIO_LINEEVENT_DATA_READ - Read edge detection events from a line event.
28 :c:type:`request.fd<gpioevent_request>` by gpio-get-lineevent-ioctl.rst.
40 Read edge detection events for a line from a line event.
56 The source of the clock for :c:type:`event.timestamp<gpioevent_data>` is
57 ``CLOCK_MONOTONIC``, except for kernels earlier than Linux 5.7 when it was
65 The size of the kernel event buffer is fixed at 16 events.
68 by userspace. If an overflow occurs then the most recent event is discarded.
76 The `read()` will block if no event is available and the ``event_fd`` has not
[all …]
|
| D | chardev_v1.rst | 1 .. SPDX-License-Identifier: GPL-2.0
20 The API is based around three major objects, the :ref:`gpio-v1-chip`, the
21 :ref:`gpio-v1-line-handle`, and the :ref:`gpio-v1-line-event`.
23 Where "line event" is used in this document it refers to the request that can
26 .. _gpio-v1-chip:
36 ``offset`` in the range from 0 to ``chip.lines - 1``, i.e. `[0,chip.lines)`.
38 Lines are requested from the chip using either gpio-get-linehandle-ioctl.rst
40 gpio-get-lineevent-ioctl.rst and the resulting line event is used to monitor
47 ----------
54 Get Line Handle <gpio-get-linehandle-ioctl>
[all …]
|
| D | chardev.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 ``include/uapi/linux/gpio.h.``
18 Read Documentation/driver-api/gpio/drivers-on-gpio.rst to avoid reinventing
21 Similarly, for multi-function lines there may be other subsystems, such as
23 Documentation/driver-api/pwm.rst, Documentation/w1/index.rst etc, that
28 The API is based around two major objects, the :ref:`gpio-v2-chip` and the
29 :ref:`gpio-v2-line-request`.
31 .. _gpio-v2-chip:
41 ``offset`` in the range from 0 to ``chip.lines - 1``, i.e. `[0,chip.lines)`.
43 Lines are requested from the chip using gpio-v2-get-line-ioctl.rst
[all …]
|
| /Documentation/driver-api/surface_aggregator/clients/ |
| D | dtx.rst | 1 .. SPDX-License-Identifier: GPL-2.0+
10 User-Space DTX (Clipboard Detachment System) Interface
14 and re-attachment handling. To this end, it provides the ``/dev/surface/dtx``
15 device file, through which it can interface with a user-space daemon. This
18 unloading/reloading the graphics-driver, user-notifications, etc.
24 change. Commands are always driver-initiated, whereas events are always
56 ------------
65 being hot-unplugged while in use. More details can be found in the
70 --------------------
73 ``surface_dtx`` driver only relays events from the EC to user-space and
[all …]
|
| /Documentation/devicetree/bindings/input/touchscreen/ |
| D | cypress,tt21000.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
13 - Alistair Francis <alistair@alistair23.me>
16 - $ref: touchscreen.yaml#
25 '#address-cells':
28 '#size-cells':
34 vdd-supply:
37 vddio-supply:
40 reset-gpios:
[all …]
|
| /Documentation/filesystems/spufs/ |
| D | spu_run.rst | 1 .. SPDX-License-Identifier: GPL-2.0
10 spu_run - execute an spu context
20 int spu_run(int fd, unsigned int *npc, unsigned int *event);
25 Cell Broadband Engine Architecture in order to access Synergistic Pro-
26 cessor Units (SPUs). It uses the fd that was returned from spu_cre-
27 ate(2) to address a specific SPU context. When the context gets sched-
32 not return while the SPU is still running. If there is a need to exe-
41 event can be a NULL pointer or point to an extended status code that
42 gets filled when spu_run returns. It can be one of the following con-
54 If NULL is passed as the event argument, these errors will result in a
[all …]
|
| /Documentation/driver-api/media/ |
| D | rc-core.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 -------------------------
14 milliseconds produce a repeat key event. That's somewhat similar to what
15 a normal keyboard or mouse is handled internally on Linux\ [#f1]_. So, the
16 remote controller core is implemented on the top of the linux input/evdev
22 produces one event for a key press and another one for key release. On
23 infrared-based remote controllers, there's no key release event. Instead,
48 At receiver, a simple low-pass filter can be used to convert the received
58 codes to the Kernel. Such kind of receivers are identified
75 to convert into a Linux input event code. This is done via a mapping
[all …]
|
| /Documentation/driver-api/usb/ |
| D | hotplug.rst | 4 Linux Hotplugging
8 In hotpluggable busses like USB (and Cardbus PCI), end-users plug devices
12 - Find a driver that can handle the device. That may involve
13 loading a kernel module; newer drivers can use module-init-tools
16 - Bind a driver to that device. Bus frameworks do that using a
19 - Tell other subsystems to configure the new device. Print
22 be driver-specific actions.
48 some kernel event. That name is used as the first key for further event
54 http://linux-hotplug.sourceforge.net
70 PRODUCT USB vendor, product, and version codes (hex)
[all …]
|
| /Documentation/devicetree/bindings/mfd/ |
| D | nxp,bbnsm.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: NXP Battery-Backed Non-Secure Module
10 - Jacky Bai <ping.bai@nxp.com>
13 NXP BBNSM serves as non-volatile logic and storage for the system.
17 significant 32 bits of the real-time counter match the value in the
26 - enum:
27 - nxp,imx93-bbnsm
28 - const: syscon
[all …]
|
| D | mps,mp2629.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Saravanan Sekar <sravanhome@gmail.com>
22 - mps,mp2629
23 - mps,mp2733
31 interrupt-controller: true
33 "#interrupt-cells":
39 - compatible
40 - reg
[all …]
|
| D | max77650.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: MAX77650 ultra low-power PMIC from Maxim Integrated.
10 - Bartosz Golaszewski <bgolaszewski@baylibre.com>
13 MAX77650 is an ultra-low power PMIC providing battery charging and power
14 supply for low-power IoT and wearable applications.
16 The GPIO-controller module is represented as part of the top-level PMIC
19 For device-tree bindings of other sub-modules (regulator, power supply,
21 sub-system directories.
[all …]
|
| /Documentation/userspace-api/media/dvb/ |
| D | legacy_dvb_video.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later OR GPL-2.0
17 ``linux/dvb/video.h`` in your application.
40 --------------
45 .. code-block:: c
56 .. flat-table::
57 :header-rows: 0
58 :stub-columns: 0
60 - ..
62 - ``VIDEO_FORMAT_4_3``
64 - Select 4:3 format.
[all …]
|
| /Documentation/devicetree/bindings/power/reset/ |
| D | qcom,pon.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Vinod Koul <vkoul@kernel.org>
14 and resin along with the Android reboot-mode.
21 - qcom,pm8916-pon
22 - qcom,pm8941-pon
23 - qcom,pms405-pon
24 - qcom,pm8998-pon
25 - qcom,pmk8350-pon
[all …]
|
| /Documentation/scsi/ |
| D | dpti.rst | 1 .. SPDX-License-Identifier: GPL-2.0
14 are disclaimed. In no event shall Adaptec be
28 The original linux driver was ported to Linux by Karen White while at
30 non-Linux driver. Mark Salyzyn and Bob Pasteur consulted on the original
38 The driver was originally ported to linux version 2.0.34
41 V2.0 Rewrite of driver. Re-architectured based on i2o subsystem.
49 - Added Raptor Support
50 - Fixed bug causing system to hang under extreme load with
51 - management utilities running (removed GFP_DMA from kmalloc flags)
57 - Implemented suggestions from Alan Cox
[all …]
|
| /Documentation/admin-guide/ |
| D | sysfs-rules.rst | 4 The kernel-exported sysfs exports internal kernel implementation details
6 by the kernel developers that the Linux kernel does not provide a stable
11 low-level userspace applications, with a new kernel release, the users
12 of sysfs must follow some rules to use an as-abstract-as-possible way to
21 - Do not use libsysfs
23 offer any abstraction, it exposes all the kernel driver-core
31 - sysfs is always at ``/sys``
38 - devices are only "devices"
39 There is no such thing like class-, bus-, physical devices,
41 just simply a "device". Class-, bus-, physical, ... types are just
[all …]
|
| /Documentation/userspace-api/media/rc/ |
| D | lirc-dev-intro.rst | 1 .. SPDX-License-Identifier: GPL-2.0 OR GFDL-1.1-no-invariants-or-later
9 LIRC stands for Linux Infrared Remote Control. The LIRC device interface is
10 a bi-directional interface for transporting raw IR and decoded scancodes
21 .. code-block:: none
28 .. code-block:: none
30 $ ls -l /dev/lirc*
31 crw-rw---- 1 root root 248, 0 Jul 2 22:20 /dev/lirc0
33 Note that the package `v4l-utils <https://git.linuxtv.org/v4l-utils.git/>`_
36 - ir-ctl: can receive raw IR and transmit IR, as well as query LIRC
39 - ir-keytable: can load keymaps; allows you to set IR kernel protocols; load
[all …]
|
123