Home
last modified time | relevance | path

Searched full:dormant (Results 1 – 25 of 51) sorted by relevance

123

/kernel/linux/linux-6.6/Documentation/ABI/testing/
Dsysfs-class-net124 What: /sys/class/net/<iface>/dormant
129 Indicates whether the interface is in dormant state. Possible
131 0: interface is not dormant
132 1: interface is dormant
137 will also reflect the dormant state.
215 attribute should be used in conjunction with 'dormant' attribute
220 1 dormant link mode
254 "dormant", "up".
Dsysfs-class-devlink74 - 'dormant'
85 'dormant' means the supplier and the consumer devices have not
/kernel/linux/linux-5.10/Documentation/ABI/testing/
Dsysfs-class-net124 What: /sys/class/net/<iface>/dormant
129 Indicates whether the interface is in dormant state. Possible
131 0: interface is not dormant
132 1: interface is dormant
137 will also reflect the dormant state.
215 attribute should be used in conjunction with 'dormant' attribute
220 1 dormant link mode
254 "dormant", "up".
Dsysfs-class-devlink74 - 'dormant'
85 'dormant' means the supplier and the consumer devices have not
/kernel/linux/linux-6.6/arch/arm/mach-omap2/
Dsleep44xx.S50 * @return: This function never returns for CPU OFF and DORMANT power states.
51 * Post WFI, CPU transitions to DORMANT or OFF power state and on wake-up
55 * CPU failed to transition to targeted OFF/DORMANT state.
98 * the SCU power status to DORMANT or OFF mode.
186 * CPU is here when it failed to enter OFF/DORMANT or
236 * OFF or DORMANT state. Physical address of the function is
237 * stored in the SAR RAM while entering to OFF or DORMANT mode.
Domap-mpuss-lowpower.c15 * because the mode is not supported by hw constraints of dormant
16 * mode. While waking up from the dormant mode, a reset signal
116 * used for OFF or DORMANT wakeup.
Dpm44xx.c72 * CPU0 and CPU1 power domains need to be in OFF or DORMANT state, in omap4_pm_suspend()
/kernel/linux/linux-5.10/arch/arm/mach-omap2/
Dsleep44xx.S50 * @return: This function never returns for CPU OFF and DORMANT power states.
51 * Post WFI, CPU transitions to DORMANT or OFF power state and on wake-up
55 * CPU failed to transition to targeted OFF/DORMANT state.
98 * the SCU power status to DORMANT or OFF mode.
186 * CPU is here when it failed to enter OFF/DORMANT or
236 * OFF or DORMANT state. Physical address of the function is
237 * stored in the SAR RAM while entering to OFF or DORMANT mode.
Domap-mpuss-lowpower.c15 * because the mode is not supported by hw constraints of dormant
16 * mode. While waking up from the dormant mode, a reset signal
115 * used for OFF or DORMANT wakeup.
Dpm44xx.c72 * CPU0 and CPU1 power domains need to be in OFF or DORMANT state, in omap4_pm_suspend()
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/soc/bcm/
Dbrcm,bcm23550-cdc.yaml7 title: Broadcom BCM23550 Cluster Dormant Control
10 The Cluster Dormant Control block keeps the CPU in idle state. A command
/kernel/linux/linux-6.6/arch/arm/mach-bcm/
Dplatsmp.c213 /* Cluster Dormant Control command to bring CPU into a running state */
219 * BCM23550 has a Cluster Dormant Control block that keeps the core in
/kernel/linux/linux-5.10/arch/arm/mach-bcm/
Dplatsmp.c213 /* Cluster Dormant Control command to bring CPU into a running state */
219 * BCM23550 has a Cluster Dormant Control block that keeps the core in
/kernel/linux/linux-5.10/include/uapi/linux/
Dif.h79 * @IFF_DORMANT: driver signals dormant. Volatile.
180 IF_LINK_MODE_DORMANT, /* limit upward transition to dormant */
/kernel/linux/linux-6.6/include/uapi/linux/
Dif.h79 * @IFF_DORMANT: driver signals dormant. Volatile.
180 IF_LINK_MODE_DORMANT, /* limit upward transition to dormant */
/kernel/linux/linux-5.10/drivers/platform/mellanox/
Dmlxreg-hotplug.c374 * 0x0 indicates ASIC the bad health or dormant state and value in mlxreg_hotplug_health_work_helper()
376 * pass the following states: dormant -> booting -> good. in mlxreg_hotplug_health_work_helper()
/kernel/linux/linux-6.6/drivers/platform/mellanox/
Dmlxreg-hotplug.c444 * 0x0 indicates ASIC the bad health or dormant state and value in mlxreg_hotplug_health_work_helper()
446 * pass the following states: dormant -> booting -> good. in mlxreg_hotplug_health_work_helper()
/kernel/linux/linux-6.6/Documentation/staging/
Dstatic-keys.rst62 tracepoints are often dormant (disabled) and provide no direct kernel
/kernel/linux/linux-5.10/Documentation/staging/
Dstatic-keys.rst62 tracepoints are often dormant (disabled) and provide no direct kernel
/kernel/linux/linux-6.6/net/mac80211/
Dlink.c153 "Invalid links: valid=0x%x, dormant=0x%x", in ieee80211_set_vif_links_bitmaps()
/kernel/linux/linux-6.6/include/linux/
Dnetdevice.h4189 * netif_dormant_on - mark device as dormant.
4192 * Mark device as dormant (as per RFC2863).
4194 * The dormant state indicates that the relevant interface is not
4207 * netif_dormant_off - set device as not dormant.
4210 * Device is not in dormant state.
4219 * netif_dormant - test if device is dormant
4222 * Check if device is dormant.
4238 * will change to up, dormant, or down, as appropriate.
/kernel/linux/linux-5.10/Documentation/driver-api/
Ddevice_link.rst264 DORMANT <=> AVAILABLE <=> CONSUMER_PROBE => ACTIVE
/kernel/linux/linux-5.10/mm/
Dmemcg_reclaim.c531 * successful direct reclaim run will revive a dormant kswapd. in shrink_node_hyperhold()
/kernel/linux/linux-6.6/Documentation/driver-api/
Ddevice_link.rst264 DORMANT <=> AVAILABLE <=> CONSUMER_PROBE => ACTIVE
/kernel/linux/linux-6.6/drivers/hwmon/
Dhp-wmi-sensors.c219 * "Dormant","Supporting Entity in Error","Completed",
309 * "Dormant","Supporting Entity in Error","Completed",
348 * "Dormant","Supporting Entity in Error","Completed",

123