Searched refs:activation (Results 1 – 25 of 71) sorted by relevance
123
| /linux-6.12.1/Documentation/driver-api/nvdimm/ |
| D | firmware-activate.rst | 17 to advertise and control their local runtime firmware activation
21 attribute that shows the state of the firmware activation as one of 'idle',
32 back to idle and completing an activation cycle.
36 the activation it could be the case that too many DIMMs are armed for
37 activation. In that scenario the potential for firmware activation to
42 run firmware activation from within the equivalent of the hibernation
45 firmware activation without this hibernation cycle. The
47 firmware activation capability is detected.
57 elided completely if no firmware activation capability is detected.
61 communicate the per-device firmware activation state. Similar to the
[all …]
|
| /linux-6.12.1/Documentation/ABI/testing/ |
| D | sysfs-driver-hid-ntrig | 30 Threholds to override activation slack.
50 activation and activity.
53 activation and activity.
|
| D | sysfs-bus-nfit | 212 the system over the activation event, or trust that the OS will
217 the activation might abort if, for example, platform firmware
218 determines that the activation time exceeds the max PCI-E
220 OS is running the activation from a suspend context it aborts,
223 enabled to bypass the activation abort.
|
| D | sysfs-class-net-qmi | 39 activation and data stream setup on the modem side by
|
| /linux-6.12.1/Documentation/input/devices/ |
| D | ntrig.rst | 36 |min_width |both to decide activation and during activity |
101 contact immediately overrides the waiting period and leads to activation.
103 Setting the activation size thresholds to large values will result in deciding
104 primarily on activation slack. If you see longer lived ghosts, turning up the
105 activation slack while reducing the size thresholds may suffice to eliminate
109 the initial activation filter is satisfied. The intent is to provide
|
| /linux-6.12.1/Documentation/leds/ |
| D | ledtrig-transient.rst | 11 gets deactivated. There is no provision for one time activation to implement
20 Transient trigger addresses the need for one shot timer activation. The
25 triggers it supports and a default trigger. During registration, activation
46 as its default trigger, trigger activation routine will get called. During
52 Transient trigger activation routine doesn't change the LED state. It
74 duration to be set after trigger activation.
136 - Timer activation is one shot and extending and/or shortening the timer
|
| /linux-6.12.1/Documentation/networking/devlink/ |
| D | devlink-reload.rst | 38 pending activation. If no limitation specified this action may involve
45 being performed without fw activation. Therefore, the devlink reload
|
| /linux-6.12.1/Documentation/devicetree/bindings/memory-controllers/ |
| D | ti-aemif.txt | 104 and the activation of read strobe.
108 Time between the activation and deactivation of
121 and the activation of write strobe.
125 Time between the activation and deactivation of
|
| /linux-6.12.1/security/tomoyo/ |
| D | Kconfig | 63 activation. You can override this setting via TOMOYO_loader= kernel
72 This is the default pathname of activation trigger.
|
| /linux-6.12.1/Documentation/core-api/ |
| D | debug-objects.rst | 117 This function is called whenever the activation function of a real
125 problem before the real activation of the object happens. E.g. it can
130 allow the legitimate activation of statically allocated and initialized
135 When the activation is legitimate, then the state of the associated
247 The activation of statically initialized objects is a special case. When
|
| /linux-6.12.1/arch/arm/boot/dts/ti/omap/ |
| D | omap2430-sdp.dts | 65 gpmc,clk-activation-ns = <0>;
|
| D | omap-gpmc-smsc911x.dtsi | 47 gpmc,clk-activation-ns = <0>;
|
| D | omap2420-n8x0-common.dtsi | 81 gpmc,clk-activation-ns = <9>;
|
| D | omap-zoom-common.dtsi | 49 gpmc,clk-activation-ns = <0>;
|
| D | omap3-sb-t35.dtsi | 130 gpmc,clk-activation-ns = <0>;
|
| D | dra62x-j5eco-evm.dts | 76 gpmc,clk-activation-ns = <0>;
|
| D | omap3-gta04a5one.dts | 82 gpmc,clk-activation-ns = <5>;
|
| D | dm8148-evm.dts | 76 gpmc,clk-activation-ns = <0>;
|
| D | omap4-duovero-parlor.dts | 168 gpmc,clk-activation-ns = <5>;
|
| D | am335x-chilisom.dtsi | 171 gpmc,clk-activation-ns = <0>;
|
| /linux-6.12.1/Documentation/trace/ |
| D | timerlat-tracer.rst | 47 prints two lines at every activation. The first is the *timer latency*
48 observed at the *hardirq* context before the activation of the thread.
220 a timer, and go to sleep for the following activation.
|
| /linux-6.12.1/arch/arm64/boot/dts/ti/ |
| D | k3-am62-lp-sk-nand.dtso | 77 gpmc,clk-activation-ns = <0>;
|
| D | k3-am642-evm-nand.dtso | 102 gpmc,clk-activation-ns = <0>;
|
| /linux-6.12.1/drivers/net/wireless/intel/iwlwifi/fw/api/ |
| D | mac-cfg.h | 725 __le32 activation; member
|
| /linux-6.12.1/Documentation/sound/cards/ |
| D | joystick.rst | 34 was a dynamic control API for the joystick activation. It was
|
123