Searched +full:wakeup +full:- +full:mode (Results 1 – 25 of 88) sorted by relevance
1234
| /Documentation/devicetree/bindings/power/reset/ |
| D | atmel,at91sam9260-shdwc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/power/reset/atmel,at91sam9260-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 - atmel,at91sam9260-shdwc 20 - atmel,at91sam9rl-shdwc 21 - atmel,at91sam9x5-shdwc 29 atmel,wakeup-mode: [all …]
|
| /Documentation/devicetree/bindings/net/bluetooth/ |
| D | brcm,bluetooth.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Linus Walleij <linus.walleij@linaro.org> 13 This binding describes Broadcom UART-attached bluetooth chips. 18 - items: 19 - enum: 20 - infineon,cyw43439-bt 21 - const: brcm,bcm4329-bt 22 - enum: [all …]
|
| /Documentation/devicetree/bindings/usb/ |
| D | mediatek,mtu3.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 4 --- 6 $schema: http://devicetree.org/meta-schemas/core.yaml# 11 - Chunfeng Yun <chunfeng.yun@mediatek.com> 14 - $ref: usb-drd.yaml 23 - enum: 24 - mediatek,mt2712-mtu3 25 - mediatek,mt8173-mtu3 26 - mediatek,mt8183-mtu3 27 - mediatek,mt8186-mtu3 [all …]
|
| D | mediatek,mtk-xhci.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 4 --- 5 $id: http://devicetree.org/schemas/usb/mediatek,mtk-xhci.yaml# 6 $schema: http://devicetree.org/meta-schemas/core.yaml# 11 - Chunfeng Yun <chunfeng.yun@mediatek.com> 14 - $ref: usb-xhci.yaml 19 case 2: supports dual-role mode, and the host is based on xHCI driver. 25 - enum: 26 - mediatek,mt2701-xhci 27 - mediatek,mt2712-xhci [all …]
|
| D | usb-nop-xceiv.yaml | 1 # SPDX-License-Identifier: GPL-2.0 3 --- 4 $id: http://devicetree.org/schemas/usb/usb-nop-xceiv.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Rob Herring <robh@kernel.org> 14 const: usb-nop-xceiv 19 clock-names: 22 clock-frequency: true 24 '#phy-cells': 27 vcc-supply: [all …]
|
| D | dwc2.yaml | 1 # SPDX-License-Identifier: GPL-2.0 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Rob Herring <robh@kernel.org> 13 - $ref: usb-drd.yaml# 14 - $ref: usb-hcd.yaml# 19 - const: brcm,bcm2835-usb 20 - const: hisilicon,hi6220-usb 21 - const: ingenic,jz4775-otg 22 - const: ingenic,jz4780-otg [all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-power | 15 labels, which may be "mem" (suspend), "standby" (power-on 16 suspend), "freeze" (suspend-to-idle) and "disk" (hibernation). 21 See Documentation/admin-guide/pm/sleep-states.rst for more 28 The /sys/power/mem_sleep file controls the operating mode of 31 supported). The mode that will be used on subsequent attempts 35 Writing one of the above strings to this file causes the mode 39 See Documentation/admin-guide/pm/sleep-states.rst for more 46 The /sys/power/disk file controls the operating mode of the 47 suspend-to-disk mechanism. Reading from this file returns 51 'firmware' - means that the memory image will be saved to disk [all …]
|
| 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/rtc/ |
| D | fsl,ls-ftm-alarm.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/rtc/fsl,ls-ftm-alarm.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Frank Li <Frank.Li@nxp.com> 15 - fsl,ls1012a-ftm-alarm 16 - fsl,ls1021a-ftm-alarm 17 - fsl,ls1028a-ftm-alarm 18 - fsl,ls1043a-ftm-alarm 19 - fsl,ls1046a-ftm-alarm [all …]
|
| /Documentation/devicetree/bindings/power/supply/ |
| D | richtek,rt9471.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Alina Yu <alina_yu@richtek.com> 11 - ChiYuan Huang <cy_huang@richtek.com> 14 RT9471 is a switch-mode single cell Li-Ion/Li-Polymer battery charger for 16 voltage regulations in both charging and boost mode. 19 https://www.richtek.com/assets/product_file/RT9471=RT9471D/DS9471D-02.pdf 28 charge-enable-gpios: 32 wakeup-source: true [all …]
|
| D | richtek,rt9467.yaml | 1 # 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> 11 - ChiaEn Wu <chiaen_wu@richtek.com> 14 RT9467 is a switch-mode single cell Li-Ion/Li-Polymer battery charger for 16 MOSFETs, input current sensing and regulation, high-accuracy voltage 20 The RT9467 also features USB On-The-Go (OTG) support. It also integrates 21 D+/D- pin for USB host/charging port detection. 24 https://www.richtek.com/assets/product_file/RT9467/DS9467-01.pdf [all …]
|
| /Documentation/admin-guide/ |
| D | btmrvl.rst | 14 bit 8:0 -- Gap 15 bit 16:8 -- GPIO 18 It could be any valid GPIO pin# (e.g. 0-7) or 0xff (SDIO interface 19 wakeup will be used instead). 21 where Gap is the gap in milli seconds between wakeup signal and 22 wakeup event, or 0xff for special host sleep setting. 35 These commands are used to enable/disable auto sleep mode 39 1 -- Enable auto sleep mode 40 0 -- Disable auto sleep mode 44 # Enable auto sleep mode [all …]
|
| /Documentation/devicetree/bindings/regulator/ |
| D | richtek,rt6190.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: Richtek RT6190 4-Switch BuckBoost controller 10 - ChiYuan Huang <cy_huang@richtek.com> 13 The RT6190 is 4-Switch BuckBoost controller designed for converting input 21 https://www.richtek.com/assets/product_file/RT6190/DS6190-02.pdf 24 - $ref: regulator.yaml# 29 - richtek,rt6190 34 enable-gpios: [all …]
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | ste,nomadik.txt | 4 - compatible: "stericsson,db8500-pinctrl", "stericsson,db8540-pinctrl", 5 "stericsson,stn8815-pinctrl" 6 - nomadik-gpio-chips: array of phandles to the corresponding GPIO chips 8 - prcm: phandle to the PRCMU managing the back end of this pin controller 10 Please refer to pinctrl-bindings.txt in this directory for details of the 23 (see pinctrl-bindings.txt): 26 - function: A string containing the name of the function to mux to the 28 - groups : An array of strings. Each string contains the name of a pin 30 set-up. 33 - pins: A string array describing the pins affected by the configuration [all …]
|
| /Documentation/devicetree/bindings/input/ |
| D | atmel,maxtouch.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Nick Dyer <nick@shmanahar.org> 11 - Linus Walleij <linus.walleij@linaro.org> 18 - $ref: input.yaml# 30 vdda-supply: 34 vdd-supply: 38 reset-gpios: 45 wake-gpios: [all …]
|
| D | microchip,qt1050.txt | 1 Microchip AT42QT1050 Five-channel Touch Sensor IC 4 one to five keys, dependent on mode. The QT1050 includes all signal processing 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: 25 - linux,code: Keycode to emit. 26 - reg: The key number. Valid values: 0, 1, 2, 3, 4. [all …]
|
| /Documentation/devicetree/bindings/sound/ |
| D | dmic-codec.yaml | 1 # 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 …]
|
| /Documentation/devicetree/bindings/soc/qcom/ |
| D | qcom,rpm.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 16 - Bjorn Andersson <andersson@kernel.org> 21 - qcom,rpm-apq8064 22 - qcom,rpm-msm8660 23 - qcom,rpm-msm8960 24 - qcom,rpm-ipq8064 25 - qcom,rpm-mdm9615 33 interrupt-names: [all …]
|
| /Documentation/devicetree/bindings/mfd/ |
| D | richtek,rt5120.yaml | 1 # 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 17 sequence control, operation mode selection. 22 - richtek,rt5120 30 interrupt-controller: true 32 "#interrupt-cells": 35 wakeup-source: true [all …]
|
| /Documentation/arch/arm/pxa/ |
| D | mfp.rst | 7 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/locking/ |
| D | robust-futex-ABI.rst | 47 If a thread is running in 32 bit compatibility mode on a 64 native arch 48 kernel, then it can actually have two such structures - one using 32 bit 49 words for 32 bit compatibility mode, and one using 64 bit words for 64 50 bit native mode. The kernel, if it is a 64 bit kernel supporting 32 bit 51 compatibility mode, will attempt to process both lists on each task 81 robust_futexes. The kernel will only be able to wakeup the next thread 90 indicating their holder died, and wakeup the next thread waiting for 118 existing futex mechanism to wait for, and wakeup, locks. The kernels 163 wakeup on that address, which will waken the next thread that has
|
| /Documentation/devicetree/bindings/mmc/ |
| D | mtk-sd.yaml | 1 # SPDX-License-Identifier: GPL-2.0 3 --- 4 $id: http://devicetree.org/schemas/mmc/mtk-sd.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Chaotian Jing <chaotian.jing@mediatek.com> 11 - Wenbin Mei <wenbin.mei@mediatek.com> 16 - enum: 17 - mediatek,mt2701-mmc 18 - mediatek,mt2712-mmc 19 - mediatek,mt6779-mmc [all …]
|
| /Documentation/devicetree/bindings/net/can/ |
| D | fsl,flexcan.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 8 Flexcan CAN controller on Freescale's ARM and PowerPC system-on-a-chip (SOC). 11 - Marc Kleine-Budde <mkl@pengutronix.de> 14 - $ref: can-controller.yaml# 19 - enum: 20 - fsl,imx95-flexcan 21 - fsl,imx93-flexcan 22 - fsl,imx8qm-flexcan [all …]
|
| /Documentation/devicetree/bindings/timer/ |
| D | sprd,sc9860-timer.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 3 --- 4 $id: http://devicetree.org/schemas/timer/sprd,sc9860-timer.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Orson Zhai <orsonzhai@gmail.com> 11 - Baolin Wang <baolin.wang7@gmail.com> 12 - Chunyan Zhang <zhang.lyra@gmail.com> 15 The Spreadtrum SC9860 platform provides 3 general-purpose timers. 17 period mode or one-shot mode, and they can be a wakeup source 23 - sprd,sc9860-timer [all …]
|
| /Documentation/devicetree/bindings/cpu/ |
| D | idle-states.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/cpu/idle-states.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Lorenzo Pieralisi <lorenzo.pieralisi@arm.com> 11 - Anup Patel <anup@brainfault.org> 15 1 - Introduction 18 ARM and RISC-V systems contain HW capable of managing power consumption 19 dynamically, where cores can be put in different low-power states (ranging 22 run-time, can be specified through device tree bindings representing the [all …]
|
1234