Home
last modified time | relevance | path

Searched +full:key +full:- +full:wakeup (Results 1 – 25 of 37) sorted by relevance

12

/Documentation/devicetree/bindings/input/
Dgpio-keys.yaml1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
4 $id: http://devicetree.org/schemas/input/gpio-keys.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Rob Herring <robh@kernel.org>
15 - gpio-keys
16 - gpio-keys-polled
23 poll-interval: true
26 …"^(button|event|key|switch|(button|event|key|switch)-[a-z0-9-]+|[a-z0-9-]+-(button|event|key|switc…
35 - items:
[all …]
Dsamsung,s3c6410-keypad.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/input/samsung,s3c6410-keypad.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 Samsung SoC Keypad controller is used to interface a SoC with a matrix-type
12 A key can be placed at each intersection of a unique row and a unique column.
13 The keypad controller can sense a key-press and key-release and report the
17 - Krzysztof Kozlowski <krzk@kernel.org>
22 - samsung,s3c6410-keypad
23 - samsung,s5pv210-keypad
[all …]
Dgpio-matrix-keypad.txt4 The matrix keypad supports multiple row and column lines, a key can be
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
14 - col-gpios: List of gpios used as column lines. The gpio specifier
17 - linux,keymap: The definition can be found at
18 bindings/input/matrix-keymap.txt
21 - linux,no-autorepeat: do no enable autorepeat feature.
22 - wakeup-source: use any event on keypad as wakeup event.
23 (Legacy property supported: "linux,wakeup")
[all …]
Dqcom,pm8921-keypad.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/input/qcom,pm8921-keypad.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
13 - $ref: input.yaml#
14 - $ref: matrix-keymap.yaml#
19 - qcom,pm8058-keypad
20 - qcom,pm8921-keypad
27 - description: key sense
[all …]
Dfsl,scu-key.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/input/fsl,scu-key.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: i.MX SCU Client Device Node - SCU Key Based on SCU Message Protocol
10 - Dong Aisheng <aisheng.dong@nxp.com>
13 Client nodes are maintained as children of the relevant IMX-SCU device node.
16 - $ref: input.yaml#
21 - const: fsl,imx8qxp-sc-key
22 - const: fsl,imx-sc-key
[all …]
Dmediatek,mt6779-keypad.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/input/mediatek,mt6779-keypad.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Mattijs Korpershoek <mkorpershoek@baylibre.com>
13 - $ref: /schemas/input/matrix-keymap.yaml#
16 Mediatek's Keypad controller is used to interface a SoC with a matrix-type
18 A key can be placed at each intersection of a unique row and a unique column.
19 The keypad controller can sense a key-press and key-release and report the
25 - const: mediatek,mt6779-keypad
[all …]
Dmicrochip,qt1050.txt1 Microchip AT42QT1050 Five-channel Touch Sensor IC
11 - compatible: Must be "microchip,qt1050"
12 - reg: The I2C address of the device
13 - interrupts: The sink for the touchpad's IRQ output,
14 see ../interrupt-controller/interrupts.txt
17 - wakeup-source: touch keys can be used as a wakeup source
19 Each button (key) is represented as a sub-node:
21 Each not specified key or key with linux,code set to KEY_RESERVED gets disabled
25 - linux,code: Keycode to emit.
26 - reg: The key number. Valid values: 0, 1, 2, 3, 4.
[all …]
Dnvidia,tegra20-kbc.txt2 The key controller has maximum 24 pins to make matrix keypad. Any pin
7 - compatible: "nvidia,tegra20-kbc"
8 - reg: Register base address of KBC.
9 - interrupts: Interrupt number for the KBC.
10 - nvidia,kbc-row-pins: The KBC pins which are configured as row. This is an
12 - nvidia,kbc-col-pins: The KBC pins which are configured as column. This is an
14 - linux,keymap: The keymap for keys as described in the binding document
15 devicetree/bindings/input/matrix-keymap.txt.
16 - clocks: Must contain one entry, for the module clock.
17 See ../clocks/clock-bindings.txt for details.
[all …]
Dmediatek,pmic-keys.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/input/mediatek,pmic-keys.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Chen Zhong <chen.zhong@mediatek.com>
13 - $ref: input.yaml#
16 There are two key functions provided by MT6397, MT6323 and other MediaTek
18 The key functions are defined as the subnode of the function node provided
19 by the PMIC that is defined as a Multi-Function Device (MFD).
27 - mediatek,mt6323-keys
[all …]
Dallwinner,sun4i-a10-lradc-keys.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/input/allwinner,sun4i-a10-lradc-keys.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Chen-Yu Tsai <wens@csie.org>
11 - Maxime Ripard <mripard@kernel.org>
16 - const: allwinner,sun4i-a10-lradc-keys
17 - const: allwinner,sun8i-a83t-r-lradc
18 - items:
19 - enum:
[all …]
/Documentation/devicetree/bindings/power/
Dwakeup-source.txt1 Specifying wakeup capability for devices
5 ----------------
6 Nodes that describe devices which have wakeup capability may contain a
7 "wakeup-source" boolean property.
9 If the device is marked as a wakeup-source, interrupt wake capability depends
10 on the device specific "interrupt-names" property. If no interrupts are labeled
14 However if a device has a dedicated interrupt as the wakeup source, then it
16 cases only that interrupt can be used as a wakeup interrupt.
18 While various legacy interrupt names exist, new devices should use "wakeup" as
22 ---------------------------------------------------------
[all …]
/Documentation/devicetree/bindings/crypto/
Dfsl,sec-v4.0-mon.yaml1 # SPDX-License-Identifier: GPL-2.0
2 # Copyright (C) 2008-2011 Freescale Semiconductor Inc.
4 ---
5 $id: http://devicetree.org/schemas/crypto/fsl,sec-v4.0-mon.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
8 title: Freescale Secure Non-Volatile Storage (SNVS)
11 - '"Horia Geantă" <horia.geanta@nxp.com>'
12 - Pankaj Gupta <pankaj.gupta@nxp.com>
13 - Gaurav Jain <gaurav.jain@nxp.com>
18 violations. This also included rtc, system power off and ON/OFF key.
[all …]
/Documentation/scheduler/
Dsched-capacity.rst9 ----------------
13 different performance characteristics - on such platforms, not all CPUs can be
23 - not all CPUs may have the same microarchitecture (µarch).
24 - with Dynamic Voltage and Frequency Scaling (DVFS), not all CPUs may be
28 performance-oriented than the LITTLE ones (more pipeline stages, bigger caches,
39 -------------------
49 while ``original capacity`` is class-agnostic. The rest of this document will use
54 ---------------------
59 Consider an hypothetical dual-core asymmetric CPU capacity system where
61 - work_per_hz(CPU0) = W
[all …]
Dschedutil.rst15 individual tasks to task-group slices to CPU runqueues. As the basis for this
28 is key, since it gives the ability to recompose the averages when tasks move
31 Note that blocked tasks still contribute to the aggregates (task-group slices
35 Using this we track 2 key metrics: 'running' and 'runnable'. 'Running'
57 r_dvfs := -----
61 hardware counters (Intel APERF/MPERF, ARMv8.4-AMU) to provide us this ratio.
65 f_cur := ----- * P0
68 4C-turbo; if available and turbo enabled
69 f_max := { 1C-turbo; if turbo enabled
73 r_dvfs := min( 1, ----- )
[all …]
Dsched-ext.rst6 programs - the BPF scheduler.
12 together, as tasks aren't tied to specific CPUs at the time of wakeup.
18 a runnable task stalls, or on invoking the SysRq key sequence
19 :kbd:`SysRq-S`.
24 `sched_ext_dump` tracepoint. The SysRq key sequence :kbd:`SysRq-D`
35 .. code-block:: none
54 in ``ops->flags``, all ``SCHED_NORMAL``, ``SCHED_BATCH``, ``SCHED_IDLE``, and
58 set in ``ops->flags``, only tasks with the ``SCHED_EXT`` policy are scheduled
62 Terminating the sched_ext scheduler program, triggering :kbd:`SysRq-S`, or
66 .. code-block:: none
[all …]
/Documentation/input/
Dinput-programming.rst34 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);
83 parts of the input systems what it is - what events can be generated or
88 set_bit(EV_KEY, button_dev->evbit);
89 set_bit(BTN_0, button_dev->keybit);
126 dev->open() and dev->close()
140 return -EBUSY;
154 button_dev->open = button_open;
[all …]
/Documentation/devicetree/bindings/mfd/
Dstericsson,ab8500.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: ST-Ericsson Analog Baseband AB8500 and AB8505
10 - Linus Walleij <linus.walleij@linaro.org>
13 the AB8500 "Analog Baseband" is the mixed-signals integrated circuit
14 handling power management (regulators), analog-to-digital conversion
15 (ADC), battery charging, fuel gauging of the battery, battery-backed
16 RTC, PWM, USB PHY and some GPIO lines in the ST-Ericsson U8500 platforms
21 USB charging handling has changed, and it has an embedded USB-to-serial
[all …]
Drichtek,rt5120.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - ChiYuan Huang <cy_huang@richtek.com>
13 The RT5120 provides four high-efficiency buck converters and one LDO voltage
22 - richtek,rt5120
30 interrupt-controller: true
32 "#interrupt-cells":
35 wakeup-source: true
37 richtek,enable-undervolt-hiccup:
[all …]
Dst,stmpe.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
15 - Linus Walleij <linus.walleij@linaro.org>
18 - $ref: /schemas/spi/spi-peripheral-props.yaml#
23 - st,stmpe601
24 - st,stmpe801
25 - st,stmpe811
26 - st,stmpe1600
27 - st,stmpe1601
[all …]
/Documentation/devicetree/bindings/interrupt-controller/
Dbrcm,bcm7038-l1-intc.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/interrupt-controller/brcm,bcm7038-l1-intc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Broadcom BCM7038-style Level 1 interrupt controller
11 directly to one of the HW INT lines on each CPU. Every BCM7xxx set-top chip
14 Key elements of the hardware design include:
16 - 64, 96, 128, or 160 incoming level IRQ lines
18 - Most onchip peripherals are wired directly to an L1 input
20 - A separate instance of the register set for each CPU, allowing individual
[all …]
/Documentation/admin-guide/pm/
Dsleep-states.rst1 .. SPDX-License-Identifier: GPL-2.0
13 Sleep states are global low-power states of the entire system in which user
28 Suspend-to-Idle
29 ---------------
31 This is a generic, pure software, light-weight variant of system suspend (also
34 I/O devices into low-power states (possibly lower-power than available in the
38 The system is woken up from this state by in-band interrupts, so theoretically
40 also be set up as wakeup devices for S2Idle.
43 or :ref:`suspend-to-RAM <s2ram>`, or it can be used in addition to any of the
50 -------
[all …]
/Documentation/arch/arm/pxa/
Dmfp.rst7 MFP stands for Multi-Function Pin, which is the pin-mux logic on PXA3xx and
15 mechanism is introduced from PXA3xx to completely move the pin-mux functions
16 out of the GPIO controller. In addition to pin-mux configurations, the MFP
17 also controls the low power state, driving strength, pull-up/down and event
21 +--------+
22 | |--(GPIO19)--+
24 | |--(GPIO...) |
25 +--------+ |
26 | +---------+
27 +--------+ +------>| |
[all …]
/Documentation/driver-api/usb/
Dpower-management.rst1 .. _usb-power-management:
7 :Date: Last-updated: February 2014
11 ---------
13 * What is Remote Wakeup?
17 * Changing the default idle-delay time
31 -------------------------
35 component is ``suspended`` it is in a nonfunctional low-power state; it
37 ``resumed`` (returned to a functional full-power state) when the kernel
66 What is Remote Wakeup?
67 ----------------------
[all …]
/Documentation/trace/
Dhistogram-design.rst1 .. SPDX-License-Identifier: GPL-2.0
20 generally be truncated - only enough to make the point is displayed.
35 can do with histograms - create one with a single key on a single
60 pid as a key and with a single value, hitcount, which even if not
63 The hitcount value is a per-bucket value that's automatically
64 incremented on every hit for the given key, which in this case is the
73 To keep track of each key and value field in the histogram, hist_data
76 histogram val and key in the histogram (variables are also included
78 key and one value; in this case the one value is the hitcount value,
86 (in most cases - some hist_fields such as hitcount don't directly map
[all …]
/Documentation/livepatch/
Dshadow-vars.rst11 The implementation introduces a global, in-kernel hashtable that
15 specifically, the parent pointer serves as the hashtable key while the
30 meta-data and shadow-data:
32 - meta-data
34 - obj - pointer to parent object
35 - id - data identifier
37 - data[] - storage for shadow data
41 They also allow to call a custom constructor function when a non-zero
48 * klp_shadow_get() - retrieve a shadow variable data pointer
49 - search hashtable for <obj, id> pair
[all …]

12