Searched full:activation (Results 1 – 25 of 297) sorted by relevance
12345678910>>...12
| /linux-6.8/Documentation/driver-api/nvdimm/ |
| D | firmware-activate.rst | 4 NVDIMM Runtime Firmware Activation
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.
[all …]
|
| /linux-6.8/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.8/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.8/drivers/thermal/intel/ |
| D | intel_tcc.c | 12 * intel_tcc_get_tjmax() - returns the default TCC activation Temperature
16 * activation temperature in degrees C.
43 * activation temperature equals "Tjmax" - "TCC Offset", in degrees C.
69 * activation temperature equals "Tjmax" - "TCC Offset", in degree C.
|
| /linux-6.8/drivers/nvme/host/ |
| D | constants.c | 119 [NVME_SC_FW_NEEDS_CONV_RESET] = "Firmware Activation Requires Conventional Reset",
124 [NVME_SC_FW_NEEDS_SUBSYS_RESET] = "Firmware Activation Requires NVM Subsystem Reset",
125 [NVME_SC_FW_NEEDS_RESET] = "Firmware Activation Requires Reset",
126 [NVME_SC_FW_NEEDS_MAX_TIME] = "Firmware Activation Requires Maximum Time Violation",
127 [NVME_SC_FW_ACTIVATE_PROHIBITED] = "Firmware Activation Prohibited",
|
| /linux-6.8/Documentation/core-api/ |
| D | debug-objects.rst | 15 - Activation of uninitialized objects
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.8/Documentation/ABI/testing/ |
| 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-driver-hid-ntrig | 30 Threholds to override activation slack.
50 activation and activity.
53 activation and activity.
|
| D | sysfs-driver-intel_sdsi | 58 a Capability Activation Payload. Mailbox command.
65 (WO) Used to write a Capability Activation Payload (CAP) to the
|
| /linux-6.8/include/uapi/linux/sched/ |
| D | types.h | 48 * - the activation period or minimum instance inter-arrival time;
51 * - the deadline (relative to the actual activation time) of each
57 * the instance activation time + the deadline.
|
| /linux-6.8/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
|
| D | ti,gpmc-child.yaml | 118 gpmc,clk-activation-ns:
119 description: GPMC clock activation time
|
| /linux-6.8/Documentation/trace/ |
| D | timerlat-tracer.rst | 33 # |||| ACTIVATION
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.
49 The second is the *timer latency* observed by the thread. The ACTIVATION
220 a timer, and go to sleep for the following activation.
|
| /linux-6.8/arch/mips/lantiq/falcon/ |
| D | sysctrl.c | 33 /* Activation Status Register */
35 /* Activation Register */
48 /* Activation Status Register */
88 pr_err("module de/activation failed %d %08X %08X %08X\n", in sysctl_wait()
|
| /linux-6.8/security/tomoyo/ |
| D | Kconfig | 63 activation. You can override this setting via TOMOYO_loader= kernel
72 This is the default pathname of activation trigger.
|
| D | load_policy.c | 58 * tomoyo_trigger_setup - Set trigger for activation.
60 * @str: Program to use as an activation trigger (e.g. /sbin/init ).
|
| /linux-6.8/drivers/message/fusion/lsi/ |
| D | mpi_log_sas.h | 243 /* Activation failed due to trying to activate an already active volume */
245 /* Activation failed due to trying to active unsupported volume type */
247 /* Activation failed due to trying to active too many volumes */
249 /* Activation failed due to Volume ID in use already */
251 /* Activation failed call to activateVolume returned failure */
253 /* Activation failed trying to import the volume */
255 /* Activation failed trying to import the volume */
|
| /linux-6.8/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.8/arch/s390/include/asm/ |
| D | cpu_mf.h | 66 unsigned int cs:1; /* 30: basic-sampling activation control */
67 unsigned int cd:1; /* 31: diag-sampling activation control */
89 unsigned int cs:1; /* 62: basic-sampling activation control */
90 unsigned int cd:1; /* 63: diag-sampling activation control */
|
| /linux-6.8/drivers/hid/ |
| D | hid-ntrig.c | 65 /* The current activation state. */
78 /* Threshold to override activation slack */
674 * ignore them for activation state in ntrig_event()
684 * Contact meets the activation size threshold in ntrig_event()
704 * Defer adjusting the activation state in ntrig_event()
761 * Activation state machine logic: in ntrig_event()
829 * Note: activation slack will decrease over in ntrig_event()
|
| /linux-6.8/drivers/pnp/ |
| D | manager.c | 3 * manager.c - Resource Management, Conflict Resolution, Activation and Disabling of Devices
340 pnp_dbg(&dev->dev, "activation not supported\n"); in pnp_start_dev()
346 dev_err(&dev->dev, "activation failed\n"); in pnp_start_dev()
|
| /linux-6.8/Documentation/devicetree/bindings/spi/ |
| D | cdns,qspi-nor-peripheral-props.yaml | 30 and the activation of another.
|
| /linux-6.8/include/linux/spi/ |
| D | mmc_spi.h | 19 /* driver activation and (optional) card detect irq hookup */
|
| /linux-6.8/tools/testing/selftests/drivers/net/mlxsw/ |
| D | devlink_linecard.sh | 144 # Wait for possible activation to make sure the state
295 log_test "Activation 16x100G"
|
| /linux-6.8/arch/arm/include/asm/ |
| D | bL_switcher.h | 29 * The notifier chain is called with the switcher activation lock held:
|
12345678910>>...12