Home
last modified time | relevance | path

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

12345678910>>...36

/Linux-v6.1/drivers/base/power/
Dwakeup_stats.c1 // SPDX-License-Identifier: GPL-2.0
3 * Wakeup statistics in sysfs
6 * Copyright (c) 2019 Greg Kroah-Hartman <gregkh@linuxfoundation.org>
29 return sysfs_emit(buf, "%lu\n", ws->_name); \
43 ws->active ? ktime_sub(ktime_get(), ws->last_time) : 0; in active_time_ms_show()
54 ktime_t total_time = ws->total_time; in total_time_ms_show()
56 if (ws->active) { in total_time_ms_show()
57 active_time = ktime_sub(ktime_get(), ws->last_time); in total_time_ms_show()
70 ktime_t max_time = ws->max_time; in max_time_ms_show()
72 if (ws->active) { in max_time_ms_show()
[all …]
/Linux-v6.1/drivers/acpi/
Ddevice_pm.c1 // SPDX-License-Identifier: GPL-2.0-only
3 * drivers/acpi/device_pm.c - ACPI device power management routines.
27 * acpi_power_state_string - String representation of ACPI device power state.
53 status = acpi_evaluate_integer(device->handle, "_PSC", NULL, &psc); in acpi_dev_pm_explicit_get()
55 return -ENODEV; in acpi_dev_pm_explicit_get()
62 * acpi_device_get_power - Get power state of an ACPI device.
67 * update its parent's power.state field (when the parent's power state is
78 struct acpi_device *parent; in acpi_device_get_power() local
82 return -EINVAL; in acpi_device_get_power()
84 parent = acpi_dev_parent(device); in acpi_device_get_power()
[all …]
/Linux-v6.1/Documentation/devicetree/bindings/interrupt-controller/
Dinterrupts.txt5 -------------------------
8 "interrupts" property, an "interrupts-extended" property, or both. If both are
16 interrupt-parent = <&intc1>;
19 The "interrupt-parent" property is used to specify the controller to which
22 interrupt client node or in any of its parent nodes. Interrupts listed in the
23 "interrupts" property are always in reference to the node's interrupt parent.
25 The "interrupts-extended" property is a special form; useful when a node needs
26 to reference multiple interrupt parents or a different interrupt parent than
27 the inherited one. Each entry in this property contains both the parent phandle
31 interrupts-extended = <&intc1 5 1>, <&intc2 1 0>;
[all …]
/Linux-v6.1/Documentation/devicetree/bindings/net/
Dmarvell-bt-8xxx.txt2 ------
9 - compatible : should be one of the following:
10 * "marvell,sd8897-bt" (for SDIO)
11 * "marvell,sd8997-bt" (for SDIO)
16 - marvell,cal-data: Calibration data downloaded to the device during
20 - marvell,wakeup-pin: It represents wakeup pin number of the bluetooth chip.
21 firmware will use the pin to wakeup host system (u16).
22 - marvell,wakeup-gap-ms: wakeup gap represents wakeup latency of the host
25 - interrupt-names: Used only for USB based devices (See below)
26 - interrupts : specifies the interrupt pin number to the cpu. For SDIO, the
[all …]
Dbtusb.txt2 ---------------------------------------------------
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))
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
24 request this interrupt for wakeup. During system suspend, the
25 irq will be enabled so that the bluetooth chip can wakeup host
[all …]
/Linux-v6.1/Documentation/devicetree/bindings/input/
Dcypress,cyapa.txt4 - compatible: must be "cypress,cyapa".
5 - reg: I2C address of the chip.
6 - interrupts: interrupt to which the chip is connected (see interrupt
10 - wakeup-source: touchpad can be used as a wakeup source.
11 - pinctrl-names: should be "default" (see pinctrl binding [1]).
12 - pinctrl-0: a phandle pointing to the pin settings for the device (see
14 - vcc-supply: a phandle for the regulator supplying 3.3V power.
16 [0]: Documentation/devicetree/bindings/interrupt-controller/interrupts.txt
17 [1]: Documentation/devicetree/bindings/pinctrl/pinctrl-bindings.txt
27 interrupt-parent = <&gpio>;
[all …]
Dqcom,pm8xxx-keypad.txt5 - 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>
23 document describing the node's interrupt parent.
25 - linux,keymap:
27 Value type: <prop-encoded-array>
[all …]
/Linux-v6.1/Documentation/devicetree/bindings/rtc/
Disil,isl12057.txt8 ("wakeup-source") to handle the specific use-case found
9 on at least three in-tree users of the chip (NETGEAR ReadyNAS 102, 104
10 and 2120 ARM-based NAS); On those devices, the IRQ#2 pin of the chip
13 RTC alarm rings. In order to mark the device has a wakeup source and
20 - "compatible": must be "isil,isl12057"
21 - "reg": I2C bus address of the device
25 - "wakeup-source": mark the chip as a wakeup source, independently of
38 that the pinctrl-related properties below are given for completeness and
41 "interrupt-parent" and "interrupts" are usually sufficient):
60 pinctrl-0 = <&rtc_alarm_pin>;
[all …]
/Linux-v6.1/Documentation/devicetree/bindings/mfd/
Dtc3589x.txt1 * 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 …]
/Linux-v6.1/drivers/input/keyboard/
Dgpio_keys.c1 // SPDX-License-Identifier: GPL-2.0-only
31 #include <dt-bindings/input/gpio-keys.h>
41 unsigned int release_delay; /* in msecs, for IRQ-only buttons */
45 unsigned int software_debounce; /* in msecs, for GPIO-driven buttons */
67 * There are 4 attributes under /sys/devices/platform/gpio-keys/
68 * keys [ro] - bitmap of keys (EV_KEY) which can be
70 * switches [ro] - bitmap of switches (EV_SW) which can be
72 * disabled_keys [rw] - bitmap of keys currently disabled
73 * disabled_switches [rw] - bitmap of switches currently disabled
79 * For example, if we have following switches set up as gpio-keys:
[all …]
/Linux-v6.1/arch/arm/boot/dts/
Domap3-ldp.dts1 // SPDX-License-Identifier: GPL-2.0-only
3 * Copyright (C) 2013 Texas Instruments Incorporated - https://www.ti.com/
5 /dts-v1/;
7 #include <dt-bindings/input/input.h>
9 #include "omap-gpmc-smsc911x.dtsi"
13 compatible = "ti,omap3-ldp", "ti,omap3430", "ti,omap3";
22 cpu0-supply = <&vcc>;
27 compatible = "gpio-keys";
28 pinctrl-names = "default";
29 pinctrl-0 = <&gpio_key_pins>;
[all …]
Dr8a7791-koelsch.dts1 // SPDX-License-Identifier: GPL-2.0
6 * Copyright (C) 2013-2014 Renesas Solutions Corp.
11 * SSI-AK4643
38 /dts-v1/;
40 #include <dt-bindings/gpio/gpio.h>
41 #include <dt-bindings/input/input.h>
63 stdout-path = "serial0:115200n8";
77 #address-cells = <1>;
78 #size-cells = <1>;
82 compatible = "gpio-keys";
[all …]
Dr8a7793-gose.dts1 // SPDX-License-Identifier: GPL-2.0
5 * Copyright (C) 2014-2015 Renesas Electronics Corporation
9 * SSI-AK4643
36 /dts-v1/;
38 #include <dt-bindings/gpio/gpio.h>
39 #include <dt-bindings/input/input.h>
59 stdout-path = "serial0:115200n8";
68 compatible = "gpio-keys";
70 pinctrl-0 = <&keyboard_pins>;
71 pinctrl-names = "default";
[all …]
Domap3-gta04a3.dts1 // SPDX-License-Identifier: GPL-2.0-only
6 #include "omap3-gta04.dtsi"
18 interrupt-parent = <&gpio3>;
20 Vdd-supply = <&vaux2>;
21 Vdd_IO-supply = <&vaux2>;
23 st,click-single-x;
24 st,click-single-y;
25 st,click-single-z;
26 st,click-thresh-x = <8>;
27 st,click-thresh-y = <8>;
[all …]
Dr8a7792-blanche.dts1 // SPDX-License-Identifier: GPL-2.0
9 /dts-v1/;
11 #include <dt-bindings/gpio/gpio.h>
12 #include <dt-bindings/input/input.h>
25 stdout-path = "serial0:115200n8";
33 d3_3v: regulator-3v3 {
34 compatible = "regulator-fixed";
35 regulator-name = "D3.3V";
36 regulator-min-microvolt = <3300000>;
37 regulator-max-microvolt = <3300000>;
[all …]
/Linux-v6.1/Documentation/devicetree/bindings/pinctrl/
Dsamsung,pinctrl.yaml1 # 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>
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 -
26 samsung,pinctrl-wakeup-interrupt.yaml);
[all …]
/Linux-v6.1/drivers/soc/fsl/
Drcpm.c1 // SPDX-License-Identifier: GPL-2.0
3 // rcpm.c - Freescale QorIQ RCPM driver
5 // Copyright 2019-2020 NXP
34 np = of_find_compatible_node(NULL, NULL, "fsl,ls1021a-scfg"); in copy_ippdexpcr1_setting()
49 * rcpm_pm_prepare - performs device-level tasks associated with power
50 * management, such as programming related to the wakeup source control.
60 struct device_node *np = dev->of_node; in rcpm_pm_prepare()
66 return -EINVAL; in rcpm_pm_prepare()
68 base = rcpm->ippdexpcr_base; in rcpm_pm_prepare()
71 /* Begin with first registered wakeup source */ in rcpm_pm_prepare()
[all …]
/Linux-v6.1/Documentation/driver-api/pm/
Ddevices.rst1 .. SPDX-License-Identifier: GPL-2.0
10 :Copyright: |copy| 2010-2011 Rafael J. Wysocki <rjw@sisk.pl>, Novell Inc.
18 management (PM) code is also driver-specific. Most drivers will do very
22 This writeup gives an overview of how drivers interact with system-wide
25 background for the domain-specific work you'd do with any specific driver.
31 Drivers will use one or both of these models to put devices into low-power
36 Drivers can enter low-power states as part of entering system-wide
37 low-power states like "suspend" (also known as "suspend-to-RAM"), or
39 "suspend-to-disk").
42 by implementing various role-specific suspend and resume methods to
[all …]
/Linux-v6.1/Documentation/devicetree/bindings/power/
Dwakeup-source.txt1 Specifying wakeup capability for devices
5 ----------------
6 Nodes that describe devices which has wakeup capability must contain an
7 "wakeup-source" boolean property.
9 Also, if device is marked as a wakeup source, then all the primary
10 interrupt(s) can be used as wakeup interrupt(s).
12 However if the devices have dedicated interrupt as the wakeup source
14 interrupt name. In such cases only that interrupt can be used as wakeup
18 ---------------------------------------------------------
20 1. "enable-sdio-wakeup" Documentation/devicetree/bindings/mmc/mmc.txt
[all …]
/Linux-v6.1/Documentation/devicetree/bindings/remoteproc/
Dwkup_m3_rproc.txt1 TI Wakeup M3 Remoteproc Driver
4 The TI AM33xx and AM43xx family of devices use a small Cortex M3 co-processor
5 (commonly referred to as Wakeup M3 or CM3) to help with various low power tasks
12 A wkup_m3 device node is used to represent the Wakeup M3 processor instance
13 within the SoC. It is added as a child node of the parent interconnect bus
17 --------------------
18 - compatible: Should be one of,
19 "ti,am3352-wkup-m3" for AM33xx SoCs
20 "ti,am4372-wkup-m3" for AM43xx SoCs
21 - reg: Should contain the address ranges for the two internal
[all …]
/Linux-v6.1/drivers/soc/xilinx/
Dzynqmp_pm_domains.c1 // SPDX-License-Identifier: GPL-2.0
5 * Copyright (C) 2015-2019 Xilinx, Inc.
20 #include <linux/firmware/xlnx-zynqmp.h>
27 * struct zynqmp_pm_domain - Wrapper around struct generic_pm_domain
42 * zynqmp_gpd_is_active_wakeup_path() - Check if device is in wakeup source
44 * @dev: Device to check for wakeup source path
48 * set as wakeup source.
50 * Return: 1 if device is in wakeup source path else 0
65 * zynqmp_gpd_power_on() - Power on PM domain
78 ret = zynqmp_pm_set_requirement(pd->node_id, in zynqmp_gpd_power_on()
[all …]
/Linux-v6.1/Documentation/devicetree/bindings/net/wireless/
Dmarvell-8xxx.txt2 ------
10 - compatible : should be one of the following:
19 - marvell,caldata* : A series of properties with marvell,caldata prefix,
21 initialization. This is an array of unsigned 8-bit values.
24 "marvell,caldata-txpwrlimit-2g" (length = 566).
25 "marvell,caldata-txpwrlimit-5g-sub0" (length = 502).
26 "marvell,caldata-txpwrlimit-5g-sub1" (length = 688).
27 "marvell,caldata-txpwrlimit-5g-sub2" (length = 750).
28 "marvell,caldata-txpwrlimit-5g-sub3" (length = 502).
29 - marvell,wakeup-pin : a wakeup pin number of wifi chip which will be configured
[all …]
/Linux-v6.1/Documentation/devicetree/bindings/gpio/
Dbrcm,brcmstb-gpio.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/gpio/brcm,brcmstb-gpio.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 The controller's registers are organized as sets of eight 32-bit
15 - Doug Berger <opendmb@gmail.com>
16 - Florian Fainelli <f.fainelli@gmail.com>
21 - enum:
22 - brcm,bcm7445-gpio
23 - const: brcm,brcmstb-gpio
[all …]
/Linux-v6.1/Documentation/devicetree/bindings/iio/accel/
Dlis302.txt8 - 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
23 - st,click-single-{x,y,z}: if present, tells the device to issue an
26 - st,click-double-{x,y,z}: if present, tells the device to issue an
[all …]
/Linux-v6.1/drivers/usb/cdns3/
Dcdns3-imx.c1 // SPDX-License-Identifier: GPL-2.0
3 * cdns3-imx.c - NXP i.MX specific Glue layer for Cadence USB Controller
14 #include <linux/dma-mapping.h>
99 return readl(data->noncore + offset); in cdns_imx_readl()
104 writel(value, data->noncore + offset); in cdns_imx_writel()
119 struct device *dev = data->dev; in cdns_imx_noncore_init()
123 ret = readl_poll_timeout(data->noncore + USB3_SSPHY_STATUS, value, in cdns_imx_noncore_init()
151 bool suspend, bool wakeup);
167 struct device *dev = &pdev->dev; in cdns_imx_probe()
168 struct device_node *node = dev->of_node; in cdns_imx_probe()
[all …]

12345678910>>...36