| /kernel/linux/linux-6.6/drivers/hid/ |
| D | hid-letsketch.c | 1 // SPDX-License-Identifier: GPL-2.0-only
7 * presumably this driver will work for all of them. But it has only been
10 * These tablets also work without a special HID driver, but then only part
12 * to special key-combos. E.g. the 2 stylus buttons send right mouse clicks /
19 * This interface sends raw event input reports in a custom format, but only
25 * but only for some part of the active area due to special "aspect ratio"
26 * correction and only half by default since it assumes it will be used
31 * This interfaces send various hard-coded key-combos for the pad buttons
35 * This reports right-click mouse-button events for the 1st stylus button
38 #include <linux/input.h>
[all …]
|
| /kernel/linux/linux-6.6/Documentation/hwmon/ |
| D | tps53679.rst | 10 Addresses scanned: -
18 Addresses scanned: -
26 Addresses scanned: -
34 Addresses scanned: -
42 Addresses scanned: -
50 Addresses scanned: -
57 Guenter Roeck <linux@roeck-us.net>
61 -----------
63 Chips in this series are multi-phase step-down converters with one or two
68 -----------
[all …]
|
| D | ltc2978.rst | 10 Addresses scanned: -
18 Addresses scanned: -
26 Addresses scanned: -
34 Addresses scanned: -
42 Addresses scanned: -
52 Addresses scanned: -
60 Addresses scanned: -
68 Addresses scanned: -
76 Addresses scanned: -
84 Addresses scanned: -
[all …]
|
| D | lm25066.rst | 10 Addresses scanned: -
22 Addresses scanned: -
34 Addresses scanned: -
44 Addresses scanned: -
54 Addresses scanned: -
61 Author: Guenter Roeck <linux@roeck-us.net>
65 -----------
76 -----------
78 This driver does not auto-detect devices. You will have to instantiate the
79 devices explicitly. Please see Documentation/i2c/instantiating-devices.rst for
[all …]
|
| D | lineage-pem.rst | 1 Kernel driver lineage-pem
8 Prefix: 'lineage-pem'
10 Addresses scanned: -
16 Author: Guenter Roeck <linux@roeck-us.net>
20 -----------
27 and status reporting commands are non-standard. For this reason, a standard
32 -----------
41 $ modprobe lineage-pem
42 $ echo lineage-pem 0x40 > /sys/bus/i2c/devices/i2c-1/new_device
44 All Lineage CPL power entry modules have a built-in I2C bus master selector
[all …]
|
| /kernel/linux/linux-5.10/Documentation/hwmon/ |
| D | tps53679.rst | 10 Addresses scanned: -
18 Addresses scanned: -
26 Addresses scanned: -
34 Addresses scanned: -
42 Addresses scanned: -
49 Guenter Roeck <linux@roeck-us.net>
53 -----------
55 Chips in this series are multi-phase step-down converters with one or two
60 -----------
69 # echo tps53681 0x60 > /sys/bus/i2c/devices/i2c-1/new_device
[all …]
|
| D | ltc2978.rst | 10 Addresses scanned: -
18 Addresses scanned: -
26 Addresses scanned: -
34 Addresses scanned: -
42 Addresses scanned: -
52 Addresses scanned: -
60 Addresses scanned: -
68 Addresses scanned: -
76 Addresses scanned: -
84 Addresses scanned: -
[all …]
|
| D | lm25066.rst | 10 Addresses scanned: -
22 Addresses scanned: -
34 Addresses scanned: -
44 Addresses scanned: -
54 Addresses scanned: -
61 Author: Guenter Roeck <linux@roeck-us.net>
65 -----------
76 -----------
78 This driver does not auto-detect devices. You will have to instantiate the
79 devices explicitly. Please see Documentation/i2c/instantiating-devices.rst for
[all …]
|
| D | lineage-pem.rst | 1 Kernel driver lineage-pem
8 Prefix: 'lineage-pem'
10 Addresses scanned: -
16 Author: Guenter Roeck <linux@roeck-us.net>
20 -----------
27 and status reporting commands are non-standard. For this reason, a standard
32 -----------
41 $ modprobe lineage-pem
42 $ echo lineage-pem 0x40 > /sys/bus/i2c/devices/i2c-1/new_device
44 All Lineage CPL power entry modules have a built-in I2C bus master selector
[all …]
|
| /kernel/linux/linux-5.10/drivers/input/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
3 # Input device configuration
6 menu "Input device support"
9 config INPUT config
10 tristate "Generic input layer (needed for keyboard, mouse, ...)" if EXPERT
13 Say Y here if you have any input device (mouse, keyboard, tablet,
20 More information is available: <file:Documentation/input/input.rst>
25 module will be called input.
27 if INPUT
30 tristate "Export input device LEDs in sysfs"
[all …]
|
| /kernel/linux/linux-5.10/Documentation/sparc/oradax/ |
| D | dax-hv-api.txt | 3 Publication date 2017-09-25 08:21
5 Extracted via "pdftotext -f 547 -l 572 -layout sun4v_20170925.pdf"
14 …These APIs may only be provided by certain platforms, and may not be available to all virtual mach…
16 live-migration and other system management activities.
20 …high speed processoring of database-centric operations. The coprocessors may support one or more of
28 …e Completion Area and, unless execution order is specifically restricted through the use of serial-
45 …device node in the guest MD (Section 8.24.17, “Database Analytics Accelerators (DAX) virtual-device
51 36.1.1.1. "ORCL,sun4v-dax" Device Compatibility
54 • No-op/Sync
77 …See Section 36.2.1, “Query CCB Command Formats” for the corresponding CCB input and output formats.
[all …]
|
| /kernel/linux/linux-6.6/Documentation/arch/sparc/oradax/ |
| D | dax-hv-api.txt | 3 Publication date 2017-09-25 08:21
5 Extracted via "pdftotext -f 547 -l 572 -layout sun4v_20170925.pdf"
14 …These APIs may only be provided by certain platforms, and may not be available to all virtual mach…
16 live-migration and other system management activities.
20 …high speed processoring of database-centric operations. The coprocessors may support one or more of
28 …e Completion Area and, unless execution order is specifically restricted through the use of serial-
45 …device node in the guest MD (Section 8.24.17, “Database Analytics Accelerators (DAX) virtual-device
51 36.1.1.1. "ORCL,sun4v-dax" Device Compatibility
54 • No-op/Sync
77 …See Section 36.2.1, “Query CCB Command Formats” for the corresponding CCB input and output formats.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/regulator/ |
| D | max77802.txt | 3 This is a part of device tree bindings of MAX77802 multi-function device.
6 The MAX77802 PMIC has 10 high-efficiency Buck and 32 Low-dropout (LDO)
12 - inb1-supply: The input supply for BUCK1
13 - inb2-supply: The input supply for BUCK2
14 - inb3-supply: The input supply for BUCK3
15 - inb4-supply: The input supply for BUCK4
16 - inb5-supply: The input supply for BUCK5
17 - inb6-supply: The input supply for BUCK6
18 - inb7-supply: The input supply for BUCK7
19 - inb8-supply: The input supply for BUCK8
[all …]
|
| /kernel/linux/linux-6.6/Documentation/admin-guide/media/ |
| D | vivid.rst | 1 .. SPDX-License-Identifier: GPL-2.0
13 Each input can be a webcam, TV capture device, S-Video capture device or an HDMI
14 capture device. Each output can be an S-Video output device or an HDMI output
18 allows you to use this driver as a test input for application development, since
23 - Support for read()/write(), MMAP, USERPTR and DMABUF streaming I/O.
24 - A large list of test patterns and variations thereof
25 - Working brightness, contrast, saturation and hue controls
26 - Support for the alpha color component
27 - Full colorspace support, including limited/full RGB range
28 - All possible control types are present
[all …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/media/ |
| D | vivid.rst | 1 .. SPDX-License-Identifier: GPL-2.0
13 Each input can be a webcam, TV capture device, S-Video capture device or an HDMI
14 capture device. Each output can be an S-Video output device or an HDMI output
18 allows you to use this driver as a test input for application development, since
23 - Support for read()/write(), MMAP, USERPTR and DMABUF streaming I/O.
24 - A large list of test patterns and variations thereof
25 - Working brightness, contrast, saturation and hue controls
26 - Support for the alpha color component
27 - Full colorspace support, including limited/full RGB range
28 - All possible control types are present
[all …]
|
| /kernel/linux/linux-5.10/Documentation/input/ |
| D | input-programming.rst | 2 Creating an input device driver
8 Here comes a very simple example of an input device driver. The device has
12 #include <linux/input.h>
34 return -EBUSY;
40 error = -ENOMEM;
44 button_dev->evbit[0] = BIT_MASK(EV_KEY);
45 button_dev->keybit[BIT_WORD(BTN_0)] = BIT_MASK(BTN_0);
74 First it has to include the <linux/input.h> file, which interfaces to the
75 input subsystem. This provides all the definitions needed.
81 Then it allocates a new input device structure with input_allocate_device()
[all …]
|
| /kernel/linux/linux-6.6/drivers/input/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
3 # Input device configuration
6 menu "Input device support"
8 config INPUT config
9 tristate "Generic input layer (needed for keyboard, mouse, ...)" if EXPERT
12 Say Y here if you have any input device (mouse, keyboard, tablet,
19 More information is available: <file:Documentation/input/input.rst>
24 module will be called input.
26 if INPUT
29 tristate "Export input device LEDs in sysfs"
[all …]
|
| /kernel/linux/linux-6.6/Documentation/input/ |
| D | input-programming.rst | 2 Creating an input device driver
8 Here comes a very simple example of an input device driver. The device has
12 #include <linux/input.h>
34 return -EBUSY;
40 error = -ENOMEM;
44 button_dev->evbit[0] = BIT_MASK(EV_KEY);
45 button_dev->keybit[BIT_WORD(BTN_0)] = BIT_MASK(BTN_0);
74 First it has to include the <linux/input.h> file, which interfaces to the
75 input subsystem. This provides all the definitions needed.
81 Then it allocates a new input device structure with input_allocate_device()
[all …]
|
| 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
12 A single hardware event generates multiple input events. Each input event
14 used to separate input events into packets of input data changes occurring at
16 input event encompassing a type, code, and value.
18 The input protocol is a stateful protocol. Events are emitted only when values
20 input subsystem; drivers do not need to maintain the state and may attempt to
22 event code values using the EVIOCG* ioctls defined in linux/input.h. The event
24 class/input/event*/device/capabilities/, and the properties of a device are
[all …]
|
| /kernel/linux/linux-6.6/include/linux/ |
| D | xz.h | 5 * Igor Pavlov <https://7-zip.org/>
28 * enum xz_mode - Operation mode
30 * @XZ_SINGLE: Single-call mode. This uses less RAM than
31 * multi-call modes, because the LZMA2
36 * @XZ_PREALLOC: Multi-call mode with preallocated LZMA2
40 * @XZ_DYNALLOC: Multi-call mode. The LZMA2 dictionary is
46 * It is possible to enable support only for a subset of the above
59 * enum xz_ret - Return codes
60 * @XZ_OK: Everything is OK so far. More input or more
62 * return code is possible only in multi-call mode
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/pinctrl/ |
| D | starfive,jh7100-pinctrl.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/pinctrl/starfive,jh7100-pinctrl.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 Bindings for the JH7100 RISC-V SoC from StarFive Ltd.
12 Out of the SoC's many pins only the ones named PAD_GPIO[0] to PAD_GPIO[63]
15 interesting 2-layered approach to pin muxing best illustrated by the diagram
21 LCD output -----------------| |
22 CMOS Camera interface ------| |--- PAD_GPIO[0]
23 Ethernet PHY interface -----| MUX |--- PAD_GPIO[1]
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/phy/ |
| D | qcom,usb-snps-femto-v2.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/phy/qcom,usb-snps-femto-v2.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Qualcomm Synopsys Femto High-Speed USB PHY V2
10 - Wesley Cheng <quic_wcheng@quicinc.com>
13 Qualcomm High-Speed USB PHY
18 - items:
19 - enum:
20 - qcom,sa8775p-usb-hs-phy
[all …]
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-platform-dfl-fme | 1 What: /sys/bus/platform/devices/dfl-fme.0/ports_num
5 Description: Read-only. One DFL FPGA device may have more than 1
9 What: /sys/bus/platform/devices/dfl-fme.0/bitstream_id
13 Description: Read-only. It returns Bitstream (static FPGA region)
17 What: /sys/bus/platform/devices/dfl-fme.0/bitstream_metadata
21 Description: Read-only. It returns Bitstream (static FPGA region) meta
25 What: /sys/bus/platform/devices/dfl-fme.0/cache_size
29 Description: Read-only. It returns cache size of this FPGA device.
31 What: /sys/bus/platform/devices/dfl-fme.0/fabric_version
35 Description: Read-only. It returns fabric version of this FPGA device.
[all …]
|
| /kernel/linux/linux-6.6/Documentation/ABI/testing/ |
| D | sysfs-platform-dfl-fme | 1 What: /sys/bus/platform/devices/dfl-fme.0/ports_num
5 Description: Read-only. One DFL FPGA device may have more than 1
9 What: /sys/bus/platform/devices/dfl-fme.0/bitstream_id
13 Description: Read-only. It returns Bitstream (static FPGA region)
17 What: /sys/bus/platform/devices/dfl-fme.0/bitstream_metadata
21 Description: Read-only. It returns Bitstream (static FPGA region) meta
25 What: /sys/bus/platform/devices/dfl-fme.0/cache_size
29 Description: Read-only. It returns cache size of this FPGA device.
31 What: /sys/bus/platform/devices/dfl-fme.0/fabric_version
35 Description: Read-only. It returns fabric version of this FPGA device.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/display/bridge/ |
| D | adi,adv7511.txt | 2 ------------------------------------------------
6 conversion, S/PDIF, CEC and HDCP. ADV7533/5 supports the DSI interface for input
11 - compatible: Should be one of:
18 - reg: I2C slave addresses
26 The ADV7511 supports a large number of input data formats that differ by their
29 properties describe the input and map directly to the video input tables of the
32 - adi,input-depth: Number of bits per color component at the input (8, 10 or
34 - adi,input-colorspace: The input color space, one of "rgb", "yuv422" or
36 - adi,input-clock: The input clock type, one of "1x" (one clock cycle per
40 The following input format properties are required except in "rgb 1x" and
[all …]
|