| /linux-6.3-rc2/Documentation/devicetree/bindings/powerpc/fsl/ |
| A D | pmc.txt | 8 whose PMC is compatible, and implies deep-sleep capability.
12 whose PMC is compatible, and implies deep-sleep capability.
34 a wakeup source from deep sleep.
|
| /linux-6.3-rc2/Documentation/devicetree/bindings/soc/ti/ |
| A D | wkup-m3-ipc.yaml | 16 that cannot be controlled from the MPU, like suspend/resume and certain deep
39 'CTRL_CONF_' that contain DS0 (e.g. deep sleep) configuration bits that can
88 the CM3 firmware to activate IO isolation when suspending to deep sleep.
139 * for pull-up during normal system operation. However, the DS0 (deep sleep)
|
| /linux-6.3-rc2/drivers/mfd/ |
| A D | intel_pmc_bxt.c | 141 u64 deep, shlw; in intel_pmc_s0ix_counter_read() local
144 deep = readq(pmc->gcr_mem_base + PMC_GCR_TELEM_DEEP_S0IX_REG); in intel_pmc_s0ix_counter_read()
148 *data = S0IX_RESIDENCY_IN_USECS(deep, shlw); in intel_pmc_s0ix_counter_read()
|
| /linux-6.3-rc2/Documentation/devicetree/bindings/pinctrl/ |
| A D | sprd,pinctrl.txt | 44 by hardware when the system specified by sleep mode goes into deep
47 means when PUBCP system goes into deep sleep mode, this pin will be set
53 when the PUBCP system goes into deep sleep mode. Thus we introduce
|
| /linux-6.3-rc2/scripts/gdb/linux/ |
| A D | proc.py | 61 for res, deep in get_resources(child, depth + 1):
62 yield res, deep
|
| /linux-6.3-rc2/Documentation/devicetree/bindings/input/ |
| A D | atmel,maxtouch.yaml | 67 controller from deep-sleep mode before communication with the controller
69 consumption when the controller is in deep sleep mode. This feature is
|
| A D | iqs626a.yaml | 108 3: Proximity, touch or deep touch
112 description: Multiplies all touch and deep-touch thresholds by 4.
408 deep-touch events relative to their respective thresholds (generic
450 "^event-(prox|touch|deep)(-alt)?$":
454 Represents a proximity, touch or deep-touch event reported by the
472 deep-touch events are only available for the generic channels. Unless
488 Specifies the hysteresis for the event (touch and deep-touch
|
| A D | iqs269a.yaml | 193 3: Proximity, touch or deep touch
283 deep-touch events relative to their respective thresholds.
428 "^event-deep(-alt)?$":
431 description: Represents a deep-touch event reported by the channel.
|
| /linux-6.3-rc2/Documentation/devicetree/bindings/timer/ |
| A D | spreadtrum,sprd-timer.txt | 6 during deep sleep.
|
| /linux-6.3-rc2/Documentation/process/ |
| A D | development-process.rst | 27 discussion which does not require a deep knowledge of kernel programming to
|
| /linux-6.3-rc2/Documentation/devicetree/bindings/firmware/ |
| A D | nvidia,tegra210-bpmp.txt | 5 process as well as to assisting in entering deep low power state
|
| /linux-6.3-rc2/Documentation/devicetree/bindings/phy/ |
| A D | hisilicon,hi3670-usb3.yaml | 32 description: phandle of syscon used to control phy deep sleep.
|
| /linux-6.3-rc2/Documentation/devicetree/bindings/iio/accel/ |
| A D | adi,adxl367.yaml | 22 It includes a deep multimode output FIFO, a built-in micropower
|
| /linux-6.3-rc2/Documentation/admin-guide/pm/ |
| A D | suspend-flows.rst | 109 That allows the CPUs to stay in the deep idle state relatively long in one
186 There are platforms that can go into a very deep low-power state internally
187 when all CPUs in them are in sufficiently deep idle states and all I/O
212 offline (typically, the CPUs that have been taken offline go into deep idle
|
| A D | sleep-states.rst | 183 and "deep". The "s2idle" string always represents :ref:`suspend-to-idle
184 <s2idle>` and, by convention, "shallow" and "deep" represent
282 system go into the :ref:`suspend-to-RAM <s2ram>` state (write "deep" into
286 into :file:`/sys/power/mem_sleep`) is either "deep" (on the majority of systems
|
| /linux-6.3-rc2/Documentation/devicetree/bindings/clock/ |
| A D | qcom,rpmcc.yaml | 18 deep idle. If it is important that the clock keeps running during system
|
| /linux-6.3-rc2/drivers/staging/vc04_services/interface/ |
| A D | TODO | 46 indentation deep making it very unpleasant to read. This is specially relevant
|
| /linux-6.3-rc2/Documentation/driver-api/gpio/ |
| A D | using-gpio.rst | 26 operators to have a deep knowledge of the equipment and knows about the
|
| /linux-6.3-rc2/Documentation/core-api/ |
| A D | gfp_mask-from-fs-io.rst | 59 GFP_KERNEL allocations deep inside the allocator which are quite non-trivial
|
| /linux-6.3-rc2/Documentation/userspace-api/media/cec/ |
| A D | cec-ioc-adap-g-phys-addr.rst | 68 turn have addresses a.b.0.0, etc. So a topology of up to 5 devices deep
|
| /linux-6.3-rc2/Documentation/ABI/testing/ |
| A D | debugfs-cros-ec | 64 in order to detect cases where a system failed to go into deep
|
| /linux-6.3-rc2/Documentation/devicetree/bindings/mips/brcm/ |
| A D | soc.txt | 128 deep sleep states (S3).
|
| /linux-6.3-rc2/drivers/net/wireless/marvell/mwifiex/ |
| A D | README | 129 is_deep_sleep = <0/1, not deep sleep state/deep sleep state>
|
| /linux-6.3-rc2/Documentation/dev-tools/kunit/api/ |
| A D | functionredirection.rst | 102 the replacement function instead. Such calls may be buried deep in the
|
| /linux-6.3-rc2/Documentation/devicetree/bindings/arm/tegra/ |
| A D | nvidia,tegra20-pmc.yaml | 121 or resume from deep sleep mode. When the system is resumed
122 from the deep sleep mode, the warm boot code will restore
|