Home
last modified time | relevance | path

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

12345

/openbmc/linux/Documentation/devicetree/bindings/input/
H A 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 …]
H A 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 on 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 …]
H A 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 …]
H A 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 …]
H A 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 …]
/openbmc/linux/drivers/input/keyboard/
H A 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.
51 module will be called adp5588-keys.
61 module will be called adp5589-keys.
113 or other). This also works for AT and PS/2 keyboards connected over a
126 Say Y here if you have a PA-RISC machine and want to use an AT or
[all …]
H A 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 …]
/openbmc/linux/Documentation/devicetree/bindings/mfd/
H A 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 …]
/openbmc/linux/Documentation/devicetree/bindings/iio/accel/
H A Dbosch,bma255.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Linus Walleij <linus.walleij@linaro.org>
11 - Stephan Gerhold <stephan@gerhold.net>
15 4-wire interface.
20 # bmc150-accel driver in Linux
21 - bosch,bma222
22 - bosch,bma222e
23 - bosch,bma250e
[all …]
/openbmc/linux/Documentation/devicetree/bindings/
H A 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 …]
/openbmc/linux/drivers/gpu/drm/msm/disp/dpu1/
H A Ddpu_hw_pingpong.h1 /* SPDX-License-Identifier: GPL-2.0-only */
2 /* Copyright (c) 2015-2018, The Linux Foundation. All rights reserved.
17 * struct dpu_hw_dither_cfg - dither feature structure
24 * @matrix: dither strength matrix
33 u32 matrix[DITHER_MATRIX_SZ]; member
60 * @Return: 1 if TE was originally connected, 0 if not, or -ERROR
112 * to_dpu_hw_pingpong - convert base object dpu_hw_base to container
122 * dpu_hw_pingpong_init() - initializes the pingpong driver for the passed
132 * dpu_hw_pingpong_destroy - destroys pingpong driver context
/openbmc/u-boot/drivers/input/
H A DKconfig72 driver handles English and German keyboards - set the environment
77 bool "NVIDIA Tegra internal matrix keyboard controller support"
79 A matrix keyboard connected directly to the internal keyboard
/openbmc/linux/drivers/gpu/drm/vc4/
H A Dvc4_kms.c1 // SPDX-License-Identifier: GPL-2.0-only
49 struct drm_device *dev = state->dev; in vc4_get_ctm_state()
54 ret = drm_modeset_lock(&vc4->ctm_state_lock, state->acquire_ctx); in vc4_get_ctm_state()
70 state = kmemdup(obj->state, sizeof(*state), GFP_KERNEL); in vc4_ctm_duplicate_state()
74 __drm_atomic_helper_private_obj_duplicate_state(obj, &state->base); in vc4_ctm_duplicate_state()
76 return &state->base; in vc4_ctm_duplicate_state()
96 drm_atomic_private_obj_fini(&vc4->ctm_manager); in vc4_ctm_obj_fini()
103 drm_modeset_lock_init(&vc4->ctm_state_lock); in vc4_ctm_obj_init()
107 return -ENOMEM; in vc4_ctm_obj_init()
109 drm_atomic_private_obj_init(&vc4->base, &vc4->ctm_manager, &ctm_state->base, in vc4_ctm_obj_init()
[all …]
/openbmc/linux/Documentation/admin-guide/media/
H A 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 …]
/openbmc/linux/arch/arm/boot/dts/st/
H A Dste-href-tvk1281618-r2.dtsi1 // SPDX-License-Identifier: GPL-2.0-or-later
6 #include <dt-bindings/interrupt-controller/irq.h>
7 #include <dt-bindings/input/input.h>
11 compatible = "gpio-keys";
12 #address-cells = <1>;
13 #size-cells = <0>;
14 vdd-supply = <&ab8500_ldo_aux1_reg>;
15 pinctrl-names = "default";
16 pinctrl-0 = <&prox_tvk_mode>, <&hall_tvk_mode>;
37 interrupt-parent = <&gpio6>;
[all …]
/openbmc/linux/drivers/input/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
13 joystick, steering wheel ...) connected to your system and want
39 module will be called input-leds.
42 tristate "Support for memoryless force-feedback devices"
44 Say Y here if you have memoryless force-feedback input device
46 Power 2, or similar. You will also need to enable hardware-specific
52 module will be called ff-memless.
59 useful for out-of-tree drivers since in-tree drivers
65 module will be called sparse-keymap.
68 tristate "Matrix keymap support library"
[all …]
/openbmc/linux/drivers/gpu/drm/sti/
H A 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()
156 * tvout_vip_set_color_order - Set the clipping mode of a VIP
180 * tvout_vip_set_clip_mode - Set the clipping mode of a VIP
196 * tvout_vip_set_rnd - Set the rounded value of a VIP
212 * tvout_vip_set_sel_input - Select the VIP input
250 * tvout_vip_set_in_vid_fmt - Select the input video signed or unsigned
[all …]
/openbmc/linux/Documentation/devicetree/bindings/memory-controllers/
H A 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 …]
/openbmc/u-boot/board/siemens/taurus/
H A Dtaurus.c1 // SPDX-License-Identifier: GPL-2.0+
7 * U-Boot file: board/atmel/at91sam9260ek/at91sam9260ek.c
9 * (C) Copyright 2007-2008
50 struct at91_matrix *matrix = (struct at91_matrix *)ATMEL_BASE_MATRIX; in taurus_nand_hw_init() local
54 csa = readl(&matrix->ebicsa); in taurus_nand_hw_init()
56 writel(csa, &matrix->ebicsa); in taurus_nand_hw_init()
61 &smc->cs[3].setup); in taurus_nand_hw_init()
64 &smc->cs[3].pulse); in taurus_nand_hw_init()
66 &smc->cs[3].cycle); in taurus_nand_hw_init()
71 &smc->cs[3].mode); in taurus_nand_hw_init()
[all …]
/openbmc/linux/Documentation/devicetree/bindings/thermal/
H A Dgeneric-adc-thermal.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/thermal/generic-adc-thermal.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Laxman Dewangan <ldewangan@nvidia.com>
13 On some of platforms, thermal sensor like thermistors are connected to
16 temperature using voltage-temperature lookup table.
20 const: generic-adc-thermal
22 '#thermal-sensor-cells':
25 io-channels:
[all …]
/openbmc/linux/Documentation/devicetree/bindings/soc/fsl/cpm_qe/
H A Dfsl,cpm1-tsa.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/soc/fsl/cpm_qe/fsl,cpm1-tsa.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: PowerQUICC CPM Time-slot assigner (TSA) controller
10 - Herve Codina <herve.codina@bootlin.com>
13 The TSA is the time-slot assigner that can be found on some PowerQUICC SoC.
14 Its purpose is to route some TDM time-slots to other internal serial
20 - enum:
21 - fsl,mpc885-tsa
[all …]
/openbmc/linux/Documentation/devicetree/bindings/iio/
H A Dst,st-sensors.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/iio/st,st-sensors.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
9 description: The STMicroelectronics sensor devices are pretty straight-forward
16 - Denis Ciocca <denis.ciocca@st.com>
17 - Linus Walleij <linus.walleij@linaro.org>
22 - description: STMicroelectronics Accelerometers
24 - st,h3lis331dl-accel
25 - st,lis2de12
[all …]
/openbmc/linux/Documentation/admin-guide/blockdev/drbd/
H A 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
/openbmc/linux/Documentation/devicetree/bindings/arm/
H A Darm,coresight-cti.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
4 ---
5 $id: http://devicetree.org/schemas/arm/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.
18 CTI and the components it is directly connected to, consisting of input and
31 are implementation defined, except when the CTI is connected to an ARM v8
36 architecturally connected CTI an additional compatible string is used to
37 indicate this feature (arm,coresight-cti-v8-arch).
[all …]
/openbmc/u-boot/board/freescale/bsc9131rdb/
H A DREADME2 --------
3 - BSC9131 is integrated device that targets Femto base station market.
5 technologies with MAPLE-B2F baseband acceleration processing elements.
6 - It's MAPLE disabled personality is called 9231.
9 . Power Architecture subsystem including a e500 processor with 256-Kbyte shared
11 . StarCore SC3850 DSP subsystem with a 512-Kbyte private L2 cache
13 Processing (MAPLE-B2F)
14 . A multi-standard baseband algorithm accelerator for Channel Decoding/Encoding,
18 Turbo Decoding, Viterbi decoding, Chiprate processing, and Matrix Inversion
20 . DDR3/3L memory interface with 32-bit data width without ECC and 16-bit with
[all …]

12345