| /OK3568_Linux_fs/kernel/drivers/input/keyboard/ |
| H A D | Kconfig | 1 # 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.
109 or other). This also works for AT and PS/2 keyboards connected over a
122 Say Y here if you have a PA-RISC machine and want to use an AT or
[all …]
|
| H A D | twl4030_keypad.c | 1 // 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 …]
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/input/ |
| H A D | gpio-matrix-keypad.txt | 1 * 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 D | matrix-keymap.yaml | 1 # 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 …]
|
| H A D | brcm,bcm-keypad.txt | 3 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 D | st-keyscan.txt | 4 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 D | samsung-keypad.txt | 3 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 …]
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/iio/temperature/ |
| H A D | adi,ltc2983.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: 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 …]
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/mfd/ |
| H A D | tc3589x.txt | 1 * 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 …]
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/ |
| H A D | numa.txt | 6 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 …]
|
| /OK3568_Linux_fs/kernel/drivers/gpu/drm/vc4/ |
| H A D | vc4_kms.c | 1 // 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 …]
|
| /OK3568_Linux_fs/external/rknpu2/examples/3rdparty/opencv/opencv-linux-armhf/include/opencv2/ |
| H A D | imgproc.hpp | 13 // Copyright (C) 2000-2008, Intel Corporation, all rights reserved.
51 This module includes image-processing functions.
56 Functions and classes described in this section are used to perform various linear or non-linear
62 will be of the same size as the input image. Normally, the functions support multi-channel arrays,
67 simple arithmetic functions, they need to extrapolate values of some non-existing pixels. For
69 processing the left-most pixels in each row, you need pixels to the left of them, that is, outside
70 of the image. You can let these pixels be the same as the left-most image pixels ("replicated
71 border" extrapolation method), or assume that all the non-existing pixels are zeros ("constant
78 --------------------------|----------------------
79 CV_8U | -1/CV_16S/CV_32F/CV_64F
[all …]
|
| /OK3568_Linux_fs/external/rknpu2/examples/3rdparty/opencv/OpenCV-android-sdk/sdk/native/jni/include/opencv2/ |
| H A D | imgproc.hpp | 13 // Copyright (C) 2000-2008, Intel Corporation, all rights reserved.
51 This module includes image-processing functions.
56 Functions and classes described in this section are used to perform various linear or non-linear
62 will be of the same size as the input image. Normally, the functions support multi-channel arrays,
67 simple arithmetic functions, they need to extrapolate values of some non-existing pixels. For
69 processing the left-most pixels in each row, you need pixels to the left of them, that is, outside
70 of the image. You can let these pixels be the same as the left-most image pixels ("replicated
71 border" extrapolation method), or assume that all the non-existing pixels are zeros ("constant
78 --------------------------|----------------------
79 CV_8U | -1/CV_16S/CV_32F/CV_64F
[all …]
|
| /OK3568_Linux_fs/external/rknpu2/examples/3rdparty/opencv/opencv-linux-aarch64/include/opencv2/ |
| H A D | imgproc.hpp | 13 // Copyright (C) 2000-2008, Intel Corporation, all rights reserved.
51 This module includes image-processing functions.
56 Functions and classes described in this section are used to perform various linear or non-linear
62 will be of the same size as the input image. Normally, the functions support multi-channel arrays,
67 simple arithmetic functions, they need to extrapolate values of some non-existing pixels. For
69 processing the left-most pixels in each row, you need pixels to the left of them, that is, outside
70 of the image. You can let these pixels be the same as the left-most image pixels ("replicated
71 border" extrapolation method), or assume that all the non-existing pixels are zeros ("constant
78 --------------------------|----------------------
79 CV_8U | -1/CV_16S/CV_32F/CV_64F
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/admin-guide/media/ |
| H A D | ipu3.rst | 1 .. 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 …]
|
| /OK3568_Linux_fs/kernel/drivers/gpu/drm/msm/disp/dpu1/ |
| H A D | dpu_hw_pingpong.h | 1 /* 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
|
| /OK3568_Linux_fs/kernel/drivers/gpu/drm/sti/ |
| H A D | sti_tvout.c | 1 // 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 …]
|
| /OK3568_Linux_fs/kernel/drivers/input/ |
| H A D | Kconfig | 1 # 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 …]
|
| /OK3568_Linux_fs/u-boot/board/siemens/taurus/ |
| H A D | taurus.c | 6 * U-Boot file: board/atmel/at91sam9260ek/at91sam9260ek.c
8 * (C) Copyright 2007-2008
12 * SPDX-License-Identifier: GPL-2.0+
51 struct at91_matrix *matrix = (struct at91_matrix *)ATMEL_BASE_MATRIX; in taurus_nand_hw_init() local
55 csa = readl(&matrix->ebicsa); in taurus_nand_hw_init()
57 writel(csa, &matrix->ebicsa); in taurus_nand_hw_init()
62 &smc->cs[3].setup); in taurus_nand_hw_init()
65 &smc->cs[3].pulse); in taurus_nand_hw_init()
67 &smc->cs[3].cycle); in taurus_nand_hw_init()
72 &smc->cs[3].mode); in taurus_nand_hw_init()
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/memory-controllers/ |
| H A D | atmel,ebi.txt | 5 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 …]
|
| /OK3568_Linux_fs/buildroot/board/forlinx/ok3568/fs-overlay/usr/share/matrix-gui-2.0/ |
| H A D | app_description.php | 4 * Copyright (C) 2011 Texas Instruments Incorporated - http://www.ti.com/
66 if($found_app["Description_Link"]!=-1)
83 …ho $title; ?>. The system has detected that your embedded system is not connected to a display dev…
87 …You are currently running Matrix remotely and <?php echo $title; ?> is a GUI based application. <b…
88 …After clicking run, look at the display device connected to the embedded system to see and/or inte…
90 <div id = "run_application" style= "text-align:center;">
91 <a href = "<?php echo $link;?>"><img id = "run_img" src= "images/run-icon.png"></a>
|
| /OK3568_Linux_fs/buildroot/board/rockchip/rk3566_rk3568/fs-overlay/usr/share/matrix-gui-2.0/ |
| H A D | app_description.php | 4 * Copyright (C) 2011 Texas Instruments Incorporated - http://www.ti.com/
66 if($found_app["Description_Link"]!=-1)
83 …ho $title; ?>. The system has detected that your embedded system is not connected to a display dev…
87 …You are currently running Matrix remotely and <?php echo $title; ?> is a GUI based application. <b…
88 …After clicking run, look at the display device connected to the embedded system to see and/or inte…
90 <div id = "run_application" style= "text-align:center;">
91 <a href = "<?php echo $link;?>"><img id = "run_img" src= "images/run-icon.png"></a>
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/arm/ |
| H A D | coresight-cti.yaml | 1 # 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 …]
|
| /OK3568_Linux_fs/u-boot/board/freescale/bsc9131rdb/ |
| H A D | README | 2 --------
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 …]
|
| /OK3568_Linux_fs/kernel/Documentation/admin-guide/blockdev/drbd/ |
| H A D | data-structure-v9.rst | 2 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
|