Searched +full:wake +full:- +full:device (Results 1 – 25 of 108) sorted by relevance
12345
| /Documentation/ABI/testing/ |
| D | sysfs-devices-power | 7 management related properties of given device.
14 space to check if the device is enabled to wake up the system
32 events this file is not present. In that case the device cannot
33 be enabled to wake up the system from sleep states.
40 space to control the run-time power management of the device.
45 + "auto\n" to allow the device to be power managed at run time;
46 + "on\n" to prevent the device from being power managed;
51 from power managing the device at run time. Doing that while
52 the device is suspended causes it to be woken up.
59 enable or diasble the device's suspend and resume callbacks to
[all …]
|
| D | sysfs-class-chromeos | 1 What: /sys/class/chromeos/<ec-device-name>/flashinfo
7 What: /sys/class/chromeos/<ec-device-name>/kb_wake_angle
11 Control the keyboard wake lid angle. Values are between
12 0 and 360. This file will also show the keyboard wake lid
15 What: /sys/class/chromeos/<ec-device-name>/reboot
21 - "cancel": Cancel a pending reboot.
22 - "ro": Jump to RO without rebooting.
23 - "rw": Jump to RW without rebooting.
24 - "cold": Cold reboot.
25 - "disable-jump": Disable jump until next reboot.
[all …]
|
| D | debugfs-cros-ec | 1 What: /sys/kernel/debug/<cros-ec-device>/console_log
10 What: /sys/kernel/debug/<cros-ec-device>/panicinfo
18 What: /sys/kernel/debug/<cros-ec-device>/pdinfo
23 information for all the USB PD/type-C ports available. If
27 What: /sys/kernel/debug/<cros-ec-device>/uptime
36 What: /sys/kernel/debug/<cros-ec-device>/last_resume_result
49 received. Bit 31 is set if the EC attempted to wake the
51 Callers can use this to detect a wake from the EC due to
58 What: /sys/kernel/debug/<cros-ec-device>/suspend_timeout_ms
63 a hardware-controlled sleep line, such as Intel's SLP_S0 line,
[all …]
|
| D | sysfs-class-rc | 6 The rc/ class sub-directory belongs to the Remote Controller
16 control receiver device where N is the number of the receiver.
33 Writing "-proto" will remove a protocol from the list of enabled
83 "rc-5 nec nec-x rc-6-0 rc-6-6a-24 [rc-6-6a-32] rc-6-mce"
86 "rc-5", "rc-6" have their different bit length encodings
110 to trigger a system wake event.
113 scancodes which match the filter will wake the system from e.g.
129 expected value to trigger a system wake event.
132 scancodes which match the filter will wake the system from e.g.
|
| /Documentation/devicetree/bindings/net/can/ |
| D | tcan4x5x.txt | 4 This file provides device node information for the TCAN4x5x interface contains.
7 - compatible:
11 - reg: 0
12 - #address-cells: 1
13 - #size-cells: 0
14 - spi-max-frequency: Maximum frequency of the SPI bus the chip can
16 - interrupt-parent: the phandle to the interrupt controller which provides
18 - interrupts: interrupt specification for data-ready.
24 - reset-gpios: Hardwired output GPIO. If not defined then software
26 - device-state-gpios: Input GPIO that indicates if the device is in
[all …]
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | samsung,pinctrl-wakeup-interrupt.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/pinctrl/samsung,pinctrl-wakeup-interrupt.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Samsung S3C/S5P/Exynos SoC pin controller - wake-up interrupt controller
10 - Krzysztof Kozlowski <krzk@kernel.org>
11 - Sylwester Nawrocki <s.nawrocki@samsung.com>
12 - Tomasz Figa <tomasz.figa@gmail.com>
15 This is a part of device tree bindings for Samsung S3C/S5P/Exynos SoC pin
18 External wake-up interrupts for Samsung S3C/S5P/Exynos SoC pin controller.
[all …]
|
| D | samsung,pinctrl-gpio-bank.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/pinctrl/samsung,pinctrl-gpio-bank.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Samsung S3C/S5P/Exynos SoC pin controller - gpio bank
10 - Krzysztof Kozlowski <krzk@kernel.org>
11 - Sylwester Nawrocki <s.nawrocki@samsung.com>
12 - Tomasz Figa <tomasz.figa@gmail.com>
15 This is a part of device tree bindings for Samsung S3C/S5P/Exynos SoC pin
24 '#gpio-cells':
[all …]
|
| D | samsung,pinctrl.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Krzysztof Kozlowski <krzk@kernel.org>
11 - Sylwester Nawrocki <s.nawrocki@samsung.com>
12 - Tomasz Figa <tomasz.figa@gmail.com>
15 This is a part of device tree bindings for Samsung S3C/S5P/Exynos SoC pin
22 - External GPIO interrupts (see interrupts property in pin controller node);
24 - External wake-up interrupts - multiplexed (capable of waking up the system
25 see interrupts property in external wake-up interrupt controller node -
[all …]
|
| /Documentation/devicetree/bindings/power/reset/ |
| D | atmel,sama5d2-shdwc.yaml | 1 # 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 …]
|
| /Documentation/devicetree/bindings/net/bluetooth/ |
| D | realtek,bluetooth.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Vasily Khoruzhick <anarsoul@gmail.com>
11 - Alistair Francis <alistair@alistair23.me>
22 - enum:
23 - realtek,rtl8723bs-bt
24 - realtek,rtl8723cs-bt
25 - realtek,rtl8723ds-bt
26 - realtek,rtl8822cs-bt
[all …]
|
| /Documentation/devicetree/bindings/power/ |
| D | wakeup-source.txt | 4 Any device nodes
5 ----------------
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
11 as wake capable, then it is up to the device to determine which interrupts can
12 wake the system.
14 However if a device has a dedicated interrupt as the wakeup source, then it
15 needs to specify/identify it using a device specific interrupt name. In such
22 ---------------------------------------------------------
[all …]
|
| /Documentation/networking/dsa/ |
| D | bcm_sf2.rst | 8 - xDSL gateways such as BCM63138
9 - streaming/multimedia Set Top Box such as BCM7445
10 - Cable Modem/residential gateways such as BCM7145/BCM3390
13 ports, offering a range of built-in and customizable interfaces:
15 - single integrated Gigabit PHY
16 - quad integrated Gigabit PHY
17 - quad external Gigabit PHY w/ MDIO multiplexer
18 - integrated MoCA PHY
19 - several external MII/RevMII/GMII/RGMII interfaces
22 fail-over not to lose packets during a MoCA role re-election, as well as out of
[all …]
|
| /Documentation/devicetree/bindings/timer/ |
| D | riscv,timer.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: RISC-V timer
10 - Anup Patel <anup@brainfault.org>
13 RISC-V platforms always have a RISC-V timer device for the supervisor-mode
14 based on the time CSR defined by the RISC-V privileged specification. The
15 timer interrupts of this device are configured using the RISC-V SBI Time
16 extension or the RISC-V Sstc extension.
18 The clock frequency of RISC-V timer device is specified via the
[all …]
|
| /Documentation/devicetree/bindings/net/ |
| D | btusb.txt | 2 ---------------------------------------------------
6 - compatible : should comply with the format "usbVID,PID" specified in
7 Documentation/devicetree/bindings/usb/usb-device.yaml
13 "usb4ca,301a" (Qualcomm QCA6174A (Lite-On))
16 Also, vendors that use btusb may have device additional properties, e.g:
17 Documentation/devicetree/bindings/net/marvell-bt-8xxx.txt
21 - interrupt-names: (see below)
22 - interrupts : The interrupt specified by the name "wakeup" is the interrupt
23 that shall be used for out-of-band wake-on-bt. Driver will
31 Following example uses irq pin number 3 of gpio0 for out of band wake-on-bt:
[all …]
|
| D | fsl-tsec-phy.txt | 1 * MDIO IO device
4 device that exists on this bus, a child node should be created. See
5 the definition of the PHY node in booting-without-of.txt for an example
9 - reg : Offset and length of the register set for the device, and optionally
14 - compatible : Should define the compatible device type for the
16 - "fsl,gianfar-tbi"
17 - "fsl,gianfar-mdio"
18 - "fsl,etsec2-tbi"
19 - "fsl,etsec2-mdio"
20 - "fsl,ucc-mdio"
[all …]
|
| D | smsc,lan9115.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: Smart Mixed-Signal Connectivity (SMSC) LAN911x/912x Controller
10 - Shawn Guo <shawnguo@kernel.org>
13 - $ref: ethernet-controller.yaml#
18 - const: smsc,lan9115
19 - items:
20 - enum:
21 - smsc,lan89218
[all …]
|
| /Documentation/sound/designs/ |
| D | powersave.rst | 2 Notes on Power-Saving Mode
5 AC97 and HD-audio drivers have the automatic power-saving mode.
9 With the automatic power-saving, the driver turns off the codec power
11 the device and/or no analog loopback is set, the power disablement is
15 The time-out for automatic power-off can be specified via ``power_save``
16 module option of snd-ac97-codec and snd-hda-intel modules. Specify
17 the time-out value in seconds. 0 means to disable the automatic
18 power-saving. The default value of timeout is given via
22 reopen the device frequently. 10 would be a good choice for normal
27 automatic power-save mode with 10 seconds, write to
[all …]
|
| /Documentation/power/ |
| D | suspend-and-interrupts.rst | 2 System Suspend and Device Interrupts
9 Suspending and Resuming Device IRQs
10 -----------------------------------
12 Device interrupt request lines (IRQs) are generally disabled during system
14 ->prepare, ->suspend and ->suspend_late callbacks have been executed for all
17 The rationale for doing so is that after the "late" phase of device suspend
21 interrupt handlers for shared IRQs that device drivers implementing them were
26 of suspend_device_irqs(), along with the "noirq" phase of device suspend and
29 Device IRQs are re-enabled during system resume, right before the "early" phase
30 of resuming devices (that is, before starting to execute ->resume_early
[all …]
|
| /Documentation/devicetree/bindings/net/wireless/ |
| D | brcm,bcm4329-fmac.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/net/wireless/brcm,bcm4329-fmac.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Arend van Spriel <arend@broadcom.com>
19 - $ref: ieee80211.yaml#
24 - items:
25 - enum:
26 - brcm,bcm43143-fmac
27 - brcm,bcm4341b0-fmac
[all …]
|
| /Documentation/devicetree/bindings/input/ |
| D | gpio-keys.yaml | 1 # 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
21 description: Name of entire device
23 poll-interval: true
26 …"^(button|event|key|switch|(button|event|key|switch)-[a-z0-9-]+|[a-z0-9-]+-(button|event|key|switc…
[all …]
|
| /Documentation/ABI/obsolete/ |
| D | sysfs-bus-usb | 6 Each USB device directory will contain a file named
7 power/level. This file holds a power-level setting for
8 the device, either "on" or "auto".
10 "on" means that the device is not allowed to autosuspend,
12 be honored. "auto" means the device will autosuspend
18 If you want to suspend a device immediately but leave it
19 free to wake up in response to I/O requests, you should
22 Device not capable of proper suspend and resume should be
26 initializes all non-hub devices in the "on" level. Some
|
| /Documentation/userspace-api/media/rc/ |
| D | rc-sysfs-nodes.rst | 1 .. SPDX-License-Identifier: GPL-2.0 OR GFDL-1.1-no-invariants-or-later
9 As defined at ``Documentation/ABI/testing/sysfs-class-rc``, those are
18 The ``/sys/class/rc/`` class sub-directory belongs to the Remote
29 receiver device where N is the number of the receiver.
45 Writing "-proto" will remove a protocol from the list of enabled
95 rc-5 nec nec-x rc-6-0 rc-6-6a-24 [rc-6-6a-32] rc-6-mce
97 Note that protocol variants are listed, so ``nec``, ``sony``, ``rc-5``, ``rc-6``
121 the bits set in the wakeup filter mask to trigger a system wake event.
124 scancodes which match the filter will wake the system from e.g. suspend
138 trigger a system wake event.
[all …]
|
| /Documentation/devicetree/bindings/sound/ |
| D | realtek,rt5514.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Animesh Agarwal <animeshagarwal28@gmail.com>
13 This device supports both I2C and SPI.
15 Pins on the device (for linking into audio routes) for I2C:
24 - $ref: /schemas/spi/spi-peripheral-props.yaml#
25 - $ref: dai-common.yaml#
36 - description: Master clock to the CODEC
38 clock-names:
[all …]
|
| D | da7218.txt | 8 - compatible : Should be "dlg,da7217" or "dlg,da7218"
9 - reg: Specifies the I2C slave address
11 - VDD-supply: VDD power supply for the device
12 - VDDMIC-supply: VDDMIC power supply for the device
13 - VDDIO-supply: VDDIO power supply for the device
18 - interrupts: IRQ line info for DA7218 chip.
19 (See Documentation/devicetree/bindings/interrupt-controller/interrupts.txt for
21 - interrupt-names : Name associated with interrupt line. Should be "wakeup" if
22 interrupt is to be used to wake system, otherwise "irq" should be used.
23 - wakeup-source: Flag to indicate this device can wake system (suspend/resume).
[all …]
|
| /Documentation/devicetree/bindings/iio/accel/ |
| D | lis302.txt | 3 This device is matched via its bus drivers, and has a number of properties
4 that apply in on the generic device (independent from the bus).
8 - compatible: should be set to "st,lis3lv02d-spi"
9 - reg: the chipselect index
10 - spi-max-frequency: maximal bus speed, should be set to 1000000 unless
12 - interrupts: the interrupt generated by the device
15 - compatible: should be set to "st,lis3lv02d"
16 - reg: i2c slave address
17 - Vdd-supply: The input supply for Vdd
18 - Vdd_IO-supply: The input supply for Vdd_IO
[all …]
|
12345