Home
last modified time | relevance | path

Searched +full:cros +full:- +full:ec +full:- +full:keyb (Results 1 – 10 of 10) sorted by relevance

/kernel/linux/linux-5.10/Documentation/devicetree/bindings/input/
Dgoogle,cros-ec-keyb.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $id: http://devicetree.org/schemas/input/google,cros-ec-keyb.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
8 title: ChromeOS EC Keyboard
11 - Simon Glass <sjg@chromium.org>
12 - Benson Leung <bleung@chromium.org>
13 - Enric Balletbo i Serra <enric.balletbo@collabora.com>
16 Google's ChromeOS EC Keyboard is a simple matrix keyboard
17 implemented on a separate EC (Embedded Controller) device. It provides
[all …]
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/input/
Dcros-ec-keyb.txt1 ChromeOS EC Keyboard
3 Google's ChromeOS EC Keyboard is a simple matrix keyboard implemented on
4 a separate EC (Embedded Controller) device. It provides a message for reading
5 key scans from the EC. These are then converted into keycodes for processing
8 This binding is based on matrix-keymap.txt and extends/modifies it as follows:
11 - compatible: "google,cros-ec-keyb"
14 - google,needs-ghost-filter: True to enable a ghost filter for the matrix
15 keyboard. This is recommended if the EC does not have its own logic or
21 cros-ec-keyb {
22 compatible = "google,cros-ec-keyb";
[all …]
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/mfd/
Dcros-ec.txt3 Google's ChromeOS EC is a Cortex-M device which talks to the AP and
6 The EC can be connect through various means (I2C, SPI, LPC) and the
8 its own driver which connects to the top level interface-agnostic EC driver.
9 Other Linux driver (such as cros-ec-keyb for the matrix keyboard) connect to
10 the top-level driver.
13 - compatible: "google,cros-ec-i2c"
14 - reg: I2C slave address
17 - compatible: "google,cros-ec-spi"
18 - reg: SPI chip select
21 - google,cros-ec-spi-pre-delay: Some implementations of the EC need a little
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/mfd/
Dgoogle,cros-ec.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/mfd/google,cros-ec.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Benson Leung <bleung@chromium.org>
11 - Enric Balletbo i Serra <enric.balletbo@collabora.com>
12 - Guenter Roeck <groeck@chromium.org>
15 Google's ChromeOS EC is a microcontroller which talks to the AP and
17 The EC can be connected through various interfaces (I2C, SPI, and others)
23 - description:
[all …]
/kernel/linux/linux-4.19/drivers/input/keyboard/
Dcros_ec_keyb.c1 // SPDX-License-Identifier: GPL-2.0
2 // ChromeOS EC keyboard driver
6 // This driver uses the ChromeOS EC byte-level message-based protocol for
7 // communicating the keyboard state (which keys are pressed) from a keyboard EC
8 // to the AP over some bus (such as i2c, lpc, spi). The EC does debouncing,
10 // motivation for this is to keep the EC firmware as simple as possible, since
11 // it cannot be easily upgraded and EC flash/IRAM space is relatively
35 * @ghost_filter: true to enable the matrix key-ghosting filter
39 * @ec: Top level ChromeOS device to use to talk to EC
41 * @bs_idev: The input device for non-matrix buttons and switches (or NULL).
[all …]
/kernel/linux/linux-5.10/drivers/input/keyboard/
Dcros_ec_keyb.c1 // SPDX-License-Identifier: GPL-2.0
2 // ChromeOS EC keyboard driver
6 // This driver uses the ChromeOS EC byte-level message-based protocol for
7 // communicating the keyboard state (which keys are pressed) from a keyboard EC
8 // to the AP over some bus (such as i2c, lpc, spi). The EC does debouncing,
10 // motivation for this is to keep the EC firmware as simple as possible, since
11 // it cannot be easily upgraded and EC flash/IRAM space is relatively
35 * @ghost_filter: true to enable the matrix key-ghosting filter
39 * @ec: Top level ChromeOS device to use to talk to EC
41 * @bs_idev: The input device for non-matrix buttons and switches (or NULL).
[all …]
/kernel/linux/linux-5.10/arch/arm/boot/dts/
Dcros-ec-keyboard.dtsi1 // SPDX-License-Identifier: GPL-2.0-only
3 * Keyboard dts fragment for devices that use cros-ec-keyboard
8 #include <dt-bindings/input/input.h>
11 keyboard-controller {
12 compatible = "google,cros-ec-keyb";
13 keypad,num-rows = <8>;
14 keypad,num-columns = <13>;
15 google,needs-ghost-filter;
/kernel/linux/linux-4.19/arch/arm/boot/dts/
Dcros-ec-keyboard.dtsi2 * Keyboard dts fragment for devices that use cros-ec-keyboard
11 #include <dt-bindings/input/input.h>
14 keyboard-controller {
15 compatible = "google,cros-ec-keyb";
16 keypad,num-rows = <8>;
17 keypad,num-columns = <13>;
18 google,needs-ghost-filter;
/kernel/linux/linux-4.19/arch/arm64/boot/dts/nvidia/
Dtegra132-norrin.dts1 // SPDX-License-Identifier: GPL-2.0
2 /dts-v1/;
4 #include <dt-bindings/input/input.h>
18 stdout-path = "serial0:115200n8";
30 vdd-supply = <&vdd_3v3_hdmi>;
31 pll-supply = <&vdd_hdmi_pll>;
32 hdmi-supply = <&vdd_5v0_hdmi>;
34 nvidia,ddc-i2c-bus = <&hdmi_ddc>;
35 nvidia,hpd-gpio =
47 vdd-supply = <&vdd_3v3_panel>;
[all …]
/kernel/linux/linux-5.10/arch/arm64/boot/dts/nvidia/
Dtegra132-norrin.dts1 // SPDX-License-Identifier: GPL-2.0
2 /dts-v1/;
4 #include <dt-bindings/input/input.h>
18 stdout-path = "serial0:115200n8";
30 vdd-supply = <&vdd_3v3_hdmi>;
31 pll-supply = <&vdd_hdmi_pll>;
32 hdmi-supply = <&vdd_5v0_hdmi>;
34 nvidia,ddc-i2c-bus = <&hdmi_ddc>;
35 nvidia,hpd-gpio =
42 avdd-io-hdmi-dp-supply = <&vdd_3v3_hdmi>;
[all …]