Searched +full:wakeup +full:- +full:delay (Results 1 – 25 of 30) sorted by relevance
12
| /Documentation/devicetree/bindings/sound/ |
| D | dmic.txt | 1 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 …]
|
| D | rockchip,rk3399-gru-sound.txt | 4 - 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>;
|
| /Documentation/devicetree/bindings/input/ |
| D | gpio-matrix-keypad.txt | 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")
24 - debounce-delay-ms: debounce interval in milliseconds
[all …]
|
| D | nvidia,tegra20-kbc.txt | 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.
18 - resets: Must contain an entry for each entry in reset-names.
[all …]
|
| D | qcom,pm8xxx-keypad.txt | 5 - compatible:
9 "qcom,pm8058-keypad"
10 "qcom,pm8921-keypad"
12 - reg:
14 Value type: <prop-encoded-array>
17 - interrupts:
19 Value type: <prop-encoded-array>
25 - linux,keymap:
27 Value type: <prop-encoded-array>
29 input/matrix-keymap.txt.
[all …]
|
| /Documentation/devicetree/bindings/extcon/ |
| D | extcon-palmas.txt | 5 - 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 …]
|
| /Documentation/devicetree/bindings/regulator/ |
| D | richtek,rtmv20-regulator.yaml | 1 # 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 …]
|
| /Documentation/devicetree/bindings/input/touchscreen/ |
| D | ads7846.txt | 7 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 …]
|
| /Documentation/timers/ |
| D | timers-howto.rst | 2 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 …]
|
| /Documentation/devicetree/bindings/arm/ |
| D | atmel-sysregs.txt | 4 - 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 …]
|
| D | idle-states.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/arm/idle-states.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
14 1 - Introduction
18 where cores can be put in different low-power states (ranging from simple wfi
20 range of dynamic idle states that a processor can enter at run-time, can be
27 - Running
28 - Idle_standby
[all …]
|
| /Documentation/devicetree/bindings/mfd/ |
| 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 …]
|
| D | google,cros-ec.yaml | 1 # 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>
23 - description:
25 const: google,cros-ec-i2c
26 - description:
[all …]
|
| /Documentation/driver-api/usb/ |
| D | power-management.rst | 1 .. _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/ABI/testing/ |
| D | sysfs-devices-power | 9 What: /sys/devices/.../power/wakeup
13 The /sys/devices/.../power/wakeup attribute allows the user
19 Some devices support "wakeup" events, which are hardware signals
21 have one of the following two values for the sysfs power/wakeup
31 For the devices that are not capable of generating system wakeup
40 space to control the run-time power management of the device.
61 with the main suspend/resume thread) during system-wide power
85 of signaled wakeup events associated with the device. This
86 attribute is read-only. If the device is not capable to wake up
96 number of times the processing of wakeup events associated with
[all …]
|
| /Documentation/devicetree/bindings/i2c/ |
| D | i2c.txt | 8 -----------------------------
10 - #address-cells - should be <1>. Read more about addresses below.
11 - #size-cells - should be <0>.
12 - compatible - name of I2C bus controller
21 -----------------------------
26 - clock-frequency
29 - i2c-bus
31 devices and non-I2C devices, the 'i2c-bus' subnode can be used for
32 populating I2C devices. If the 'i2c-bus' subnode is present, only
34 '#address-cells' and '#size-cells' must be defined under this subnode
[all …]
|
| /Documentation/devicetree/bindings/input/rmi4/ |
| D | rmi_f01.txt | 10 http://www.synaptics.com/sites/default/files/511-000136-01-Rev-E-RMI4-Interfacing-Guide.pdf
13 - syna,nosleep-mode: If set the device will run at full power without sleeping.
17 - syna,wakeup-threshold: Defines the amplitude of the disturbance to the
20 - syna,doze-holdoff-ms: The delay to wait after the last finger lift and the
22 - syna,doze-interval-ms: The time period that the device sleeps between finger
29 rmi4-i2c-dev@2c {
30 compatible = "syna,rmi4-i2c";
34 rmi4-f01@1 {
36 syna,nosleep-mode = <1>;
|
| /Documentation/devicetree/bindings/serial/ |
| D | st,stm32-uart.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/serial/st,stm32-uart.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
8 - Erwan Le Ray <erwan.leray@st.com>
13 - $ref: rs485.yaml
18 - st,stm32-uart
19 - st,stm32f7-uart
20 - st,stm32h7-uart
37 st,hw-flow-ctrl:
[all …]
|
| /Documentation/devicetree/bindings/mmc/ |
| D | mmc-controller.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/mmc/mmc-controller.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Ulf Hansson <ulf.hansson@linaro.org>
25 "#address-cells":
30 "#size-cells":
37 broken-cd:
42 cd-gpios:
46 non-removable:
[all …]
|
| /Documentation/power/ |
| D | charger-manager.rst | 7 Charger Manager provides in-kernel battery charger management that
8 requires temperature monitoring during suspend-to-RAM state
12 Charger Manager is a platform_driver with power-supply-class entries.
13 An instance of Charger Manager (a platform-device created with Charger-Manager)
26 own power-supply-class and each power-supply-class can provide
28 aggregates charger-related information from multiple sources and
29 shows combined information as a single power-supply-class.
31 * Support for in suspend-to-RAM polling (with suspend_again callback)
32 While the battery is being charged and the system is in suspend-to-RAM,
50 * Support for premature full-battery event handling
[all …]
|
| D | runtime_pm.rst | 5 (C) 2009-2011 Rafael J. Wysocki <rjw@sisk.pl>, Novell Inc.
18 put their PM-related work items. It is strongly recommended that pm_wq be
20 them to be synchronized with system-wide power transitions (suspend to RAM,
53 The ->runtime_suspend(), ->runtime_resume() and ->runtime_idle() callbacks
57 1. PM domain of the device, if the device's PM domain object, dev->pm_domain,
60 2. Device type of the device, if both dev->type and dev->type->pm are present.
62 3. Device class of the device, if both dev->class and dev->class->pm are
65 4. Bus type of the device, if both dev->bus and dev->bus->pm are present.
69 dev->driver->pm directly (if present).
73 and bus type. Moreover, the high-priority one will always take precedence over
[all …]
|
| /Documentation/devicetree/bindings/phy/ |
| D | ti-phy.txt | 6 - compatible: Should be one of
7 "ti,control-phy-otghs" - if it has otghs_control mailbox register as on OMAP4.
8 "ti,control-phy-usb2" - if it has Power down bit in control_dev_conf register
10 "ti,control-phy-pipe3" - if it has DPLL and individual Rx & Tx power control
12 "ti,control-phy-pcie" - for pcie to support external clock for pcie and to
13 set PCS delay value.
15 "ti,control-phy-usb2-dra7" - if it has power down register like USB2 PHY on
17 "ti,control-phy-usb2-am437" - if it has power down register like USB2 PHY on
19 - reg : register ranges as listed in the reg-names property
20 - reg-names: "otghs_control" for control-phy-otghs
[all …]
|
| /Documentation/admin-guide/pm/ |
| D | cpuidle.rst | 1 .. SPDX-License-Identifier: GPL-2.0
27 CPU idle time management is an energy-efficiency feature concerned about using
31 ------------
37 software as individual single-core processors. In other words, a CPU is an
46 Second, if the processor is multi-core, each core in it is able to follow at
61 Finally, each core in a multi-core processor may be able to follow more than one
66 multiple individual single-core "processors", referred to as *hardware threads*
67 (or hyper-threads specifically on Intel hardware), that each can follow one
78 ---------
107 next wakeup event, or there are strict latency constraints preventing any of the
[all …]
|
| /Documentation/devicetree/bindings/remoteproc/ |
| D | ti,omap-remoteproc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only or BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/remoteproc/ti,omap-remoteproc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Suman Anna <s-anna@ti.com>
13 The OMAP family of SoCs usually have one or more slave processor sub-systems
14 that are used to offload some of the processor-intensive tasks, or to manage
17 The processor cores in the sub-system are usually behind an IOMMU, and may
18 contain additional sub-modules like Internal RAM and/or ROMs, L1 and/or L2
21 The OMAP SoCs usually have a DSP processor sub-system and/or an IPU processor
[all …]
|
| /Documentation/trace/ |
| D | ftrace.rst | 2 ftrace - Function Tracer
13 - Written for: 2.6.28-rc2
14 - Updated for: 3.10
15 - Updated for: 4.13 - Copyright 2017 VMware Inc. Steven Rostedt
16 - Converted to rst format - Changbin Du <changbin.du@intel.com>
19 ------------
24 performance issues that take place outside of user-space.
41 ----------------------
43 See :doc:`ftrace-design` for details for arch porters and such.
47 ---------------
[all …]
|
12