Home
last modified time | relevance | path

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

12345678910>>...44

/kernel/linux/linux-5.10/Documentation/devicetree/bindings/input/
Dgpio-matrix-keypad.txt6 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")
24 - debounce-delay-ms: debounce interval in milliseconds
[all …]
Dnvidia,tegra20-kbc.txt7 - 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.
18 - resets: Must contain an entry for each entry in reset-names.
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/input/
Dgpio-matrix-keypad.txt6 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")
24 - debounce-delay-ms: debounce interval in milliseconds
[all …]
Dnvidia,tegra20-kbc.txt7 - 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.
18 - resets: Must contain an entry for each entry in reset-names.
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/sound/
Ddmic.txt1 Device-Tree bindings for Digital microphone (DMIC) codec
6 - compatible: should be "dmic-codec".
9 - dmicen-gpios: GPIO specifier for dmic to control start and stop
10 - num-channels: Number of microphones on this DAI
11 - wakeup-delay-ms: Delay (in ms) after enabling the DMIC
12 - modeswitch-delay-ms: Delay (in ms) to complete DMIC mode switch
17 compatible = "dmic-codec";
18 dmicen-gpios = <&gpio4 3 GPIO_ACTIVE_HIGH>;
19 num-channels = <1>;
20 wakeup-delay-ms <50>;
[all …]
Drockchip,rk3399-gru-sound.txt4 - compatible: "rockchip,rk3399-gru-sound"
5 - rockchip,cpu: The phandle of the Rockchip I2S controller that's
7 - rockchip,codec: The phandle of the audio codecs
10 - dmic-wakeup-delay-ms : specify delay time (ms) for DMIC ready.
12 delay for DMIC to ready so that rt5514 can avoid recording before
18 compatible = "rockchip,rk3399-gru-sound";
21 dmic-wakeup-delay-ms = <20>;
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/power/reset/
Datmel,sama5d2-shdwc.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/power/reset/atmel,sama5d2-shdwc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Claudiu Beznea <claudiu.beznea@microchip.com>
14 and VDDCORE and the wake-up detection on debounced input lines.
19 - items:
20 - const: microchip,sama7g5-shdwc
21 - const: syscon
22 - enum:
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/input/touchscreen/
Dads7846.txt7 Documentation/devicetree/bindings/spi/spi-bus.txt
23 vcc-supply A regulator node for the supply voltage.
28 ti,vref-delay-usecs vref supply delay in usecs, 0 for
30 ti,vref-mv The VREF voltage, in millivolts (u16).
33 ti,keep-vref-on set to keep vref on for differential
35 ti,settle-delay-usec Settling time of the analog signals;
37 on the X/Y drivers. If set to non-zero,
41 ti,penirq-recheck-delay-usecs If set to non-zero, after samples are
42 taken this delay is applied and penirq
47 ti,x-plate-ohms Resistance of the X-plate,
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/input/touchscreen/
Dads7846.txt7 Documentation/devicetree/bindings/spi/spi-bus.txt
23 vcc-supply A regulator node for the supply voltage.
28 ti,vref-delay-usecs vref supply delay in usecs, 0 for
30 ti,vref-mv The VREF voltage, in millivolts (u16).
33 ti,keep-vref-on set to keep vref on for differential
35 ti,settle-delay-usec Settling time of the analog signals;
37 on the X/Y drivers. If set to non-zero,
41 ti,penirq-recheck-delay-usecs If set to non-zero, after samples are
42 taken this delay is applied and penirq
47 ti,x-plate-ohms Resistance of the X-plate,
[all …]
/kernel/linux/linux-5.10/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 …]
/kernel/linux/linux-6.6/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 …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/sound/
Drockchip,rk3399-gru-sound.txt4 - compatible: "rockchip,rk3399-gru-sound"
5 - rockchip,cpu: The phandle of the Rockchip I2S controller that's
7 - rockchip,codec: The phandle of the audio codecs
10 - dmic-wakeup-delay-ms : specify delay time (ms) for DMIC ready.
12 delay for DMIC to ready so that rt5514 can avoid recording before
18 compatible = "rockchip,rk3399-gru-sound";
21 dmic-wakeup-delay-ms = <20>;
Ddmic-codec.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/sound/dmic-codec.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Arnaud Pouliquen <arnaud.pouliquen@foss.st.com>
13 - $ref: dai-common.yaml#
17 const: dmic-codec
19 '#sound-dai-cells':
22 dmicen-gpios:
26 num-channels:
[all …]
Dadi,adau7002.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 ADAU7002 Stereo PDM-to-I2S/TDM Converter
10 - Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
13 - $ref: dai-common.yaml#
19 IOVDD-supply:
24 wakeup-delay-ms:
26 Delay after power up needed for device to settle.
29 - compatible
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/extcon/
Dextcon-palmas.txt5 - compatible: should contain one of:
6 * "ti,palmas-usb-vid".
7 * "ti,twl6035-usb-vid".
8 * "ti,palmas-usb" (DEPRECATED - use "ti,palmas-usb-vid").
9 * "ti,twl6035-usb" (DEPRECATED - use "ti,twl6035-usb-vid").
12 - ti,wakeup : To enable the wakeup comparator in probe
13 - ti,enable-id-detection: Perform ID detection. If id-gpio is specified
14 it performs id-detection using GPIO else using OTG core.
15 - ti,enable-vbus-detection: Perform VBUS detection.
16 - id-gpio: gpio for GPIO ID detection. See gpio binding.
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/extcon/
Dextcon-palmas.txt5 - compatible: should contain one of:
6 * "ti,palmas-usb-vid".
7 * "ti,twl6035-usb-vid".
8 * "ti,palmas-usb" (DEPRECATED - use "ti,palmas-usb-vid").
9 * "ti,twl6035-usb" (DEPRECATED - use "ti,twl6035-usb-vid").
12 - ti,wakeup : To enable the wakeup comparator in probe
13 - ti,enable-id-detection: Perform ID detection. If id-gpio is specified
14 it performs id-detection using GPIO else using OTG core.
15 - ti,enable-vbus-detection: Perform VBUS detection.
16 - id-gpio: gpio for GPIO ID detection. See gpio binding.
[all …]
/kernel/linux/linux-6.6/drivers/base/power/
Dsysfs.c1 // SPDX-License-Identifier: GPL-2.0
15 * control - Report/change current runtime PM setting of the device
30 * wakeup - Report/change current wakeup option for device
32 * Some devices support "wakeup" events, which are hardware signals
34 * devices have one of three values for the sysfs power/wakeup file:
38 * + "\n" for temporary or permanent inability to issue wakeup.
42 * Familiar examples of devices that can issue wakeup events include
44 * "Wake-On-LAN" Ethernet links, GPIO lines, and more. Some events
47 * Some wakeup events use normal IRQ lines; other use special out
51 * wakeup signaling as part of changing device power states, respecting
[all …]
/kernel/linux/linux-5.10/drivers/base/power/
Dsysfs.c1 // SPDX-License-Identifier: GPL-2.0
15 * control - Report/change current runtime PM setting of the device
30 * wakeup - Report/change current wakeup option for device
32 * Some devices support "wakeup" events, which are hardware signals
34 * devices have one of three values for the sysfs power/wakeup file:
38 * + "\n" for temporary or permanent inability to issue wakeup.
42 * Familiar examples of devices that can issue wakeup events include
44 * "Wake-On-LAN" Ethernet links, GPIO lines, and more. Some events
47 * Some wakeup events use normal IRQ lines; other use special out
51 * wakeup signaling as part of changing device power states, respecting
[all …]
/kernel/linux/linux-5.10/include/linux/usb/
Disp116x.h1 /* SPDX-License-Identifier: GPL-2.0 */
3 * Board initialization code should put one of these into dev->platform_data
13 /* On-chip overcurrent detection */
19 /* Enable wakeup by devices on usb bus (e.g. wakeup
25 /* Inter-io delay (ns). The chip is picky about access timings; it
27 150ns delay between consecutive accesses to DATA_REG,
28 300ns delay between access to ADDR_REG and DATA_REG
31 void (*delay) (struct device *dev, int delay); member
/kernel/linux/linux-6.6/include/linux/usb/
Disp116x.h1 /* SPDX-License-Identifier: GPL-2.0 */
3 * Board initialization code should put one of these into dev->platform_data
13 /* On-chip overcurrent detection */
19 /* Enable wakeup by devices on usb bus (e.g. wakeup
25 /* Inter-io delay (ns). The chip is picky about access timings; it
27 150ns delay between consecutive accesses to DATA_REG,
28 300ns delay between access to ADDR_REG and DATA_REG
31 void (*delay) (struct device *dev, int delay); member
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/regulator/
Drichtek,rtmv20-regulator.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/regulator/richtek,rtmv20-regulator.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - ChiYuan Huang <cy_huang@richtek.com>
27 wakeup-source: true
32 enable-gpios:
36 richtek,ld-pulse-delay-us:
38 load current pulse delay in microsecond after strobe pin pulse high.
43 richtek,ld-pulse-width-us:
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/regulator/
Drichtek,rtmv20-regulator.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/regulator/richtek,rtmv20-regulator.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - ChiYuan Huang <cy_huang@richtek.com>
27 wakeup-source: true
32 enable-gpios:
36 richtek,ld-pulse-delay-us:
38 load current pulse delay in microsecond after strobe pin pulse high.
43 richtek,ld-pulse-width-us:
[all …]
/kernel/linux/linux-6.6/Documentation/timers/
Dtimers-howto.rst2 delays - Information on the various kernel delay / sleep mechanisms
6 RightWay (TM) to insert a delay?"
14 ----------------
18 it really need to delay in atomic context?" If so...
21 You must use the `*delay` family of functions. These
24 the desired delay:
30 udelay is the generally preferred API; ndelay-level
31 precision may not actually exist on many non-PC devices.
38 NON-ATOMIC CONTEXT:
45 -- Backed by busy-wait loop:
[all …]
/kernel/linux/linux-5.10/Documentation/timers/
Dtimers-howto.rst2 delays - Information on the various kernel delay / sleep mechanisms
6 RightWay (TM) to insert a delay?"
14 ----------------
18 it really need to delay in atomic context?" If so...
21 You must use the `*delay` family of functions. These
24 the desired delay:
30 udelay is the generally preferred API; ndelay-level
31 precision may not actually exist on many non-PC devices.
38 NON-ATOMIC CONTEXT:
45 -- Backed by busy-wait loop:
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/arm/
Datmel-sysregs.txt4 - compatible: Should be "atmel,sama5d2-chipid"
5 - reg : Should contain registers location and length
8 - compatible: Should be "atmel,at91sam9260-pit"
9 - reg: Should contain registers location and length
10 - interrupts: Should contain interrupt for the PIT which is the IRQ line
14 - compatible: Should be "microchip,sam9x60-pit64b"
15 - reg: Should contain registers location and length
16 - interrupts: Should contain interrupt for PIT64B timer
17 - clocks: Should contain the available clock sources for PIT64B timer.
20 - compatible: Should be "atmel,at91rm9200-st", "syscon", "simple-mfd"
[all …]

12345678910>>...44