Home
last modified time | relevance | path

Searched +full:matrix +full:- +full:connected (Results 1 – 25 of 58) sorted by relevance

123

/Linux-v5.10/Documentation/devicetree/bindings/input/
Dgpio-matrix-keypad.txt1 * GPIO driven matrix keypad device tree bindings
3 GPIO driven matrix keypad is used to interface a SoC with a matrix keypad.
4 The matrix keypad supports multiple row and column lines, a key can be
5 placed at each intersection of a unique row and a unique column. The matrix
6 keypad can sense a key-press and key-release by means of GPIO lines and
10 - compatible: Should be "gpio-matrix-keypad"
11 - row-gpios: List of gpios used as row lines. The gpio specifier
13 which these row lines are connected.
14 - col-gpios: List of gpios used as column lines. The gpio specifier
16 which these column lines are connected.
[all …]
Dmatrix-keymap.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/input/matrix-keymap.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Common key matrices binding for matrix-connected key boards
10 - Olof Johansson <olof@lixom.net>
13 A simple common binding for matrix-connected key boards. Currently targeted at
19 for said properties are "linux,fn-keymap" or with another descriptive
24 $ref: '/schemas/types.yaml#/definitions/uint32-array'
26 An array of packed 1-cell entries containing the equivalent of row,
[all …]
Dst-keyscan.txt4 matrix-keymap.
7 - compatible: "st,sti-keyscan"
9 - reg: Register base address and size of st-keyscan controller.
11 - interrupts: Interrupt number for the st-keyscan controller.
13 - clocks: Must contain one entry, for the module clock.
14 See ../clocks/clock-bindings.txt for details.
16 - pinctrl: Should specify pin control groups used for this controller.
17 See ../pinctrl/pinctrl-bindings.txt for details.
19 - linux,keymap: The keymap for keys as described in the binding document
20 devicetree/bindings/input/matrix-keymap.txt.
[all …]
Dbrcm,bcm-keypad.txt3 Broadcom Keypad controller is used to interface a SoC with a matrix-type
6 The keypad controller can sense a key-press and key-release and report the
9 This binding is based on the matrix-keymap binding with the following
12 keypad,num-rows and keypad,num-columns are required.
15 - compatible: should be "brcm,bcm-keypad"
17 - reg: physical base address of the controller and length of memory mapped
20 - interrupts: The interrupt number to the cpu.
23 - keypad,num-rows: Number of row lines connected to the keypad
26 - keypad,num-columns: Number of column lines connected to the
29 - col-debounce-filter-period: The debounce period for the Column filter.
[all …]
Dsamsung-keypad.txt3 Samsung's Keypad controller is used to interface a SoC with a matrix-type
6 The keypad controller can sense a key-press and key-release and report the
10 - compatible: should be one of the following
11 - "samsung,s3c6410-keypad": For controllers compatible with s3c6410 keypad
13 - "samsung,s5pv210-keypad": For controllers compatible with s5pv210 keypad
16 - reg: physical base address of the controller and length of memory mapped
19 - interrupts: The interrupt number to the cpu.
22 - samsung,keypad-num-rows: Number of row lines connected to the keypad
25 - samsung,keypad-num-columns: Number of column lines connected to the
28 - Keys represented as child nodes: Each key connected to the keypad
[all …]
/Linux-v5.10/drivers/input/keyboard/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
20 This driver implements support for buttons connected
23 Say Y here if your device has such buttons connected to an ADC. Your
24 board-specific setup logic must also provide a configuration data
34 This option enables support for the keypad scan matrix
38 be called adp5520-keys.
48 module will be called adp5588-keys.
58 module will be called adp5589-keys.
112 or other). This also works for AT and PS/2 keyboards connected over a
125 Say Y here if you have a PA-RISC machine and want to use an AT or
[all …]
Dtwl4030_keypad.c1 // SPDX-License-Identifier: GPL-2.0-or-later
3 * twl4030_keypad.c - driver for 8x8 keypad controller in twl4030 chips
8 * Code re-written for 2430SDP by:
26 * up to an 8x8 switch matrix. The controller can issue system wakeup
27 * events, since it uses only the always-on 32KiHz oscillator, and has
29 * multi-key combinations.
42 * row lines connected to the gnd (see twl4030_col_xlate()).
59 /*----------------------------------------------------------------------*/
100 #define KEYP_PERIOD_US(t, prescale) ((t) / (31 << ((prescale) + 1)) - 1)
123 /*----------------------------------------------------------------------*/
[all …]
/Linux-v5.10/Documentation/devicetree/bindings/mfd/
Dtc3589x.txt1 * Toshiba TC3589x multi-purpose expander
3 The Toshiba TC3589x series are I2C-based MFD devices which may expose the
4 following built-in devices: gpio, keypad, rotator (vibrator), PWM (for
7 - TC35890
8 - TC35892
9 - TC35893
10 - TC35894
11 - TC35895
12 - TC35896
15 - compatible : must be "toshiba,tc35890", "toshiba,tc35892", "toshiba,tc35893",
[all …]
/Linux-v5.10/Documentation/devicetree/bindings/
Dnuma.txt6 1 - Introduction
18 2 - numa-node-id
23 a node id is a 32-bit integer.
26 numa-node-id property which contains the node id of the device.
30 numa-node-id = <0>;
33 numa-node-id = <1>;
36 3 - distance-map
39 The optional device tree node distance-map describes the relative
42 - compatible : Should at least contain "numa-distance-map-v1".
44 - distance-matrix
[all …]
/Linux-v5.10/Documentation/devicetree/bindings/iio/temperature/
Dadi,ltc2983.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Analog Devices LTC2983 Multi-sensor Temperature system
10 - Nuno Sá <nuno.sa@analog.com>
13 Analog Devices LTC2983 Multi-Sensor Digital Temperature Measurement System
14 https://www.analog.com/media/en/technical-documentation/data-sheets/2983fc.pdf
19 - adi,ltc2983
27 adi,mux-delay-config-us:
38 adi,filter-notch-freq:
[all …]
/Linux-v5.10/drivers/gpu/drm/vc4/
Dvc4_kms.c1 // SPDX-License-Identifier: GPL-2.0-only
66 struct drm_device *dev = state->dev; in vc4_get_ctm_state()
71 ret = drm_modeset_lock(&vc4->ctm_state_lock, state->acquire_ctx); in vc4_get_ctm_state()
87 state = kmemdup(obj->state, sizeof(*state), GFP_KERNEL); in vc4_ctm_duplicate_state()
91 __drm_atomic_helper_private_obj_duplicate_state(obj, &state->base); in vc4_ctm_duplicate_state()
93 return &state->base; in vc4_ctm_duplicate_state()
113 drm_atomic_private_obj_fini(&vc4->ctm_manager); in vc4_ctm_obj_fini()
120 drm_modeset_lock_init(&vc4->ctm_state_lock); in vc4_ctm_obj_init()
124 return -ENOMEM; in vc4_ctm_obj_init()
126 drm_atomic_private_obj_init(&vc4->base, &vc4->ctm_manager, &ctm_state->base, in vc4_ctm_obj_init()
[all …]
/Linux-v5.10/drivers/gpu/drm/msm/disp/dpu1/
Ddpu_hw_pingpong.h1 /* SPDX-License-Identifier: GPL-2.0-only */
2 /* Copyright (c) 2015-2018, The Linux Foundation. All rights reserved.
40 * struct dpu_hw_dither_cfg - dither feature structure
47 * @matrix: dither strength matrix
56 u32 matrix[DITHER_MATRIX_SZ]; member
85 * @Return: 1 if TE was originally connected, 0 if not, or -ERROR
99 * @Return: 0 on success, -ETIMEDOUT on timeout
128 * to_dpu_hw_pingpong - convert base object dpu_hw_base to container
138 * dpu_hw_pingpong_init - initializes the pingpong driver for the passed
150 * dpu_hw_pingpong_destroy - destroys pingpong driver context
/Linux-v5.10/Documentation/admin-guide/media/
Dipu3.rst1 .. SPDX-License-Identifier: GPL-2.0
24 ImgU). The CIO2 driver is available as drivers/media/pci/intel/ipu3/ipu3-cio2*
36 Both of the drivers implement V4L2, Media Controller and V4L2 sub-device
37 interfaces. The IPU3 CIO2 driver supports camera sensors connected to the CIO2
38 MIPI CSI-2 interfaces through V4L2 sub-device sensor drivers.
44 interface to the user space. There is a video node for each CSI-2 receiver,
47 The CIO2 contains four independent capture channel, each with its own MIPI CSI-2
48 receiver and DMA engine. Each channel is modelled as a V4L2 sub-device exposed
49 to userspace as a V4L2 sub-device node and has two pads:
53 .. flat-table::
[all …]
/Linux-v5.10/drivers/input/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
14 joystick, steering wheel ...) connected to your system and want
40 module will be called input-leds.
43 tristate "Support for memoryless force-feedback devices"
45 Say Y here if you have memoryless force-feedback input device
47 Power 2, or similar. You will also need to enable hardware-specific
53 module will be called ff-memless.
60 option is only useful for out-of-tree drivers since
61 in-tree drivers select it automatically.
66 module will be called input-polldev.
[all …]
/Linux-v5.10/drivers/gpu/drm/sti/
Dsti_tvout.c1 // SPDX-License-Identifier: GPL-2.0
131 #define to_sti_tvout(x) to_sti_tvout_encoder(x)->tvout
133 /* preformatter conversion matrix */
147 return readl(tvout->regs + offset); in tvout_read()
152 writel(val, tvout->regs + offset); in tvout_write()
267 * Set preformatter matrix
278 if (mode->vdisplay >= TVO_MIN_HD_HEIGHT) in tvout_preformatter_set_matrix()
303 dev_dbg(tvout->dev, "%s\n", __func__); in tvout_dvo_start()
334 /* Set round mode (rounded to 8-bit per component) */ in tvout_dvo_start()
356 dev_dbg(tvout->dev, "%s\n", __func__); in tvout_hdmi_start()
[all …]
/Linux-v5.10/Documentation/devicetree/bindings/memory-controllers/
Datmel,ebi.txt5 The EBI provides a glue-less interface to asynchronous memories through the SMC
10 - compatible: "atmel,at91sam9260-ebi"
11 "atmel,at91sam9261-ebi"
12 "atmel,at91sam9263-ebi0"
13 "atmel,at91sam9263-ebi1"
14 "atmel,at91sam9rl-ebi"
15 "atmel,at91sam9g45-ebi"
16 "atmel,at91sam9x5-ebi"
17 "atmel,sama5d3-ebi"
18 "microchip,sam9x60-ebi"
[all …]
/Linux-v5.10/Documentation/admin-guide/blockdev/drbd/
Ddata-structure-v9.rst2 kernel data structure for DRBD-9
5 This describes the in kernel data structure for DRBD-9. Starting with
15 The DRBD objects are interconnected to form a matrix as depicted below; a
19 /--------------+---------------+.....+---------------\
21 +--------------+---------------+.....+---------------+
23 +--------------+---------------+.....+---------------+
26 +--------------+---------------+.....+---------------+
28 \--------------+---------------+.....+---------------/
32 their volume number. Objects in the vertical direction are connected by double
36 All resources are in the drbd_resources double-linked list. In addition, all
/Linux-v5.10/Documentation/devicetree/bindings/arm/
Dcoresight-cti.yaml1 # SPDX-License-Identifier: GPL-2.0-only or BSD-2-Clause
4 ---
5 $id: http://devicetree.org/schemas/arm/coresight-cti.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 The CoreSight Embedded Cross Trigger (ECT) consists of CTI devices connected
13 a star topology via the Cross Trigger Matrix (CTM), which is not programmable.
19 CTI and the components it is directly connected to, consisting of input and
32 are implementation defined, except when the CTI is connected to an ARM v8
37 architecturally connected CTI an additional compatible string is used to
38 indicate this feature (arm,coresight-cti-v8-arch).
[all …]
/Linux-v5.10/Documentation/trace/coresight/
Dcoresight-ect.rst1 .. SPDX-License-Identifier: GPL-2.0
11 --------------------
15 devices and interconnects them via the Cross Trigger Matrix (CTM) to other
21 0 C 0----------->: : +======>(other CTI channel IO)
22 0 P 0<-----------: : v
24 0000000 : CTI :<=========>*CTM*<====>: CTI :---+
25 ####### in_trigs : : (id 0-3) ***** ::::::: v
26 # ETM #----------->: : ^ #######
27 # #<-----------: : +---# ETR #
34 activating connected output triggers there, unless filtered by the CTI
[all …]
/Linux-v5.10/Documentation/devicetree/bindings/leds/
Dcommon.yaml1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jacek Anaszewski <jacek.anaszewski@gmail.com>
11 - Pavel Machek <pavel@ucw.cz>
18 Many LED devices expose more than one current output that can be connected
25 led-sources:
27 List of device current outputs the LED is connected to. The outputs are
30 $ref: /schemas/types.yaml#definitions/uint32-array
35 from the header include/dt-bindings/leds/common.h. If there is no
[all …]
/Linux-v5.10/Documentation/ABI/testing/
Dsysfs-bus-iio3 Contact: linux-iio@vger.kernel.org
11 Contact: linux-iio@vger.kernel.org
25 Contact: linux-iio@vger.kernel.org
31 Contact: linux-iio@vger.kernel.org
38 Contact: linux-iio@vger.kernel.org
48 Contact: linux-iio@vger.kernel.org
65 Contact: linux-iio@vger.kernel.org
70 - a small discrete set of values like "0 2 4 6 8"
71 - a range with minimum, step and maximum frequencies like
76 Contact: linux-iio@vger.kernel.org
[all …]
/Linux-v5.10/drivers/auxdisplay/
Dpanel.c1 // SPDX-License-Identifier: GPL-2.0+
4 * Copyright (C) 2000-2008, Willy Tarreau <w@1wt.eu>
5 * Copyright (C) 2016-2017 Glider bvba
8 * connected to a parallel printer port.
10 * The LCD module may either be an HD44780-like 8-bit parallel LCD, or a 1-bit
11 * serial module compatible with Samsung's KS0074. The pins may be connected in
14 * The keypad consists in a matrix of push buttons connecting input pins to
15 * data output pins or to the ground. The combinations have to be hard-coded
22 * - the initialization/deinitialization process is very dirty and should
26 * - document 24 keys keyboard (3 rows of 8 cols, 32 diodes + 2 inputs)
[all …]
/Linux-v5.10/drivers/media/pci/bt8xx/
Dbttv-cards.c1 // SPDX-License-Identifier: GPL-2.0-or-later
4 bttv-cards.c
6 this file has configuration information - card-specific stuff
9 Copyright (C) 1996,97,98 Ralph Metzler (rjkm@thp.uni-koeln.de)
10 & Marcus Metzler (mocm@thp.uni-koeln.de)
11 (c) 1999-2001 Gerd Knorr <kraxel@goldbach.in-berlin.de>
31 #include <media/v4l2-common.h>
33 #include "bttv-audio-hook.h"
84 int no_overlay=-1;
86 static unsigned int card[BTTV_MAX] = { [ 0 ... (BTTV_MAX-1) ] = UNSET };
[all …]
/Linux-v5.10/Documentation/input/devices/
Datarikbd.rst12 provides a convenient connection point for a mouse and switch-type joysticks.
13 The ikbd processor also maintains a time-of-day clock with one second
18 The ikbd communicates with the main processor over a high speed bi-directional
41 0xF8-0xFB relative mouse position records (lsbs determined by
43 0xFC time-of-day
67 ---------------------------
92 +127...-128 range, the motion is broken into multiple packets.
97 ---------------------------
104 ---------------------
120 ------------------------
[all …]
/Linux-v5.10/include/drm/
Ddrm_mode_config.h42 * struct drm_mode_config_funcs - basic driver provided mode setting functions
44 * Some global (i.e. not per-CRTC, connector, etc) mode setting functions that
59 * ie. when (@mode_cmd->flags & DRM_MODE_FB_MODIFIERS) == 0.
64 * driver-specific information (like the internal native buffer object
106 * Except that there's no vtable for device-level helper callbacks
130 * - Checking that the modes, framebuffers, scaling and placement
133 * - Checking that any hidden shared resources are not oversubscribed.
138 * - Checking that virtualized resources exported to userspace are not
141 * example is dual-pipe operations (which generally should be hidden
148 * - Check that any transitional state is possible and that if
[all …]

123