| /kernel/linux/linux-5.10/drivers/misc/habanalabs/include/common/ |
| D | hl_boot_if.h | 19 * CPU_BOOT_ERR0_DRAM_INIT_FAIL DRAM initialization failed.
25 * CPU_BOOT_ERR0_TS_INIT_FAIL Thermal Sensor initialization failed.
29 * CPU_BOOT_ERR0_DRAM_SKIPPED DRAM initialization has been skipped.
30 * Skipping DRAM initialization has been
32 * and FW skipped the DRAM initialization.
44 * The NIC FW loading and initialization
47 * CPU_BOOT_ERR0_SECURITY_NOT_RDY Chip security initialization has been
|
| /kernel/linux/linux-5.10/drivers/acpi/acpica/ |
| D | utxfinit.c | 4 * Module Name: utxfinit - External interfaces for ACPICA initialization
34 * called, so any early initialization belongs here.
51 ACPI_EXCEPTION((AE_INFO, status, "During OSL initialization")); in acpi_initialize_subsystem()
60 "During initialization of globals")); in acpi_initialize_subsystem()
80 "During Namespace initialization")); in acpi_initialize_subsystem()
89 "During OSI interfaces initialization")); in acpi_initialize_subsystem()
106 * DESCRIPTION: Completes the subsystem initialization including hardware. in ACPI_EXPORT_SYMBOL_INIT()
117 * The early initialization phase is complete. The namespace is loaded, in ACPI_EXPORT_SYMBOL_INIT()
163 * initialization control methods are run (_REG, _STA, _INI) on the in ACPI_EXPORT_SYMBOL_INIT()
178 * hardware initialization. in ACPI_EXPORT_SYMBOL_INIT()
[all …]
|
| D | dsinit.c | 4 * Module Name: dsinit - Object initialization namespace walk
39 * Currently, the only objects that require initialization are:
76 "During Region initialization %p [%4.4s]", in acpi_ds_init_one_object()
152 * necessary initialization on the objects found therein
173 "**** Starting initialization of namespace objects ****\n")); in acpi_ds_initialize_objects()
205 "\nACPI table initialization:\n")); in acpi_ds_initialize_objects()
|
| /kernel/linux/linux-4.19/drivers/acpi/acpica/ |
| D | utxfinit.c | 4 * Module Name: utxfinit - External interfaces for ACPICA initialization
34 * called, so any early initialization belongs here.
51 ACPI_EXCEPTION((AE_INFO, status, "During OSL initialization")); in acpi_initialize_subsystem()
60 "During initialization of globals")); in acpi_initialize_subsystem()
80 "During Namespace initialization")); in acpi_initialize_subsystem()
89 "During OSI interfaces initialization")); in acpi_initialize_subsystem()
106 * DESCRIPTION: Completes the subsystem initialization including hardware. in ACPI_EXPORT_SYMBOL_INIT()
117 * The early initialization phase is complete. The namespace is loaded, in ACPI_EXPORT_SYMBOL_INIT()
163 * initialization control methods are run (_REG, _STA, _INI) on the in ACPI_EXPORT_SYMBOL_INIT()
178 * hardware initialization. in ACPI_EXPORT_SYMBOL_INIT()
[all …]
|
| /kernel/linux/linux-4.19/include/linux/ |
| D | irqchip.h | 20 * initialization function.
25 * @fn: initialization function
31 * the association between their version and their initialization function.
39 * @fn: initialization function
|
| /kernel/linux/linux-4.19/arch/mips/include/asm/octeon/ |
| D | cvmx-spi.h | 46 /** Callbacks structure to customize SPI4 initialization sequence */
155 * Get current SPI4 initialization callbacks
164 * Set new SPI4 initialization callbacks
181 * SPI initialization to abort)
198 * SPI initialization to abort)
215 * SPI initialization to abort)
232 * SPI initialization to abort)
249 * SPI initialization to abort)
265 * SPI initialization to abort)
|
| /kernel/linux/linux-5.10/arch/mips/include/asm/octeon/ |
| D | cvmx-spi.h | 46 /** Callbacks structure to customize SPI4 initialization sequence */
155 * Get current SPI4 initialization callbacks
164 * Set new SPI4 initialization callbacks
181 * SPI initialization to abort)
198 * SPI initialization to abort)
215 * SPI initialization to abort)
232 * SPI initialization to abort)
249 * SPI initialization to abort)
265 * SPI initialization to abort)
|
| /kernel/linux/linux-5.10/drivers/net/ipa/ |
| D | ipa.h | 141 * IPA initialization is broken into stages: init; config; and setup.
149 * the AP to perform more complex initialization by issuing "immediate
155 * loaded (in addition to some other low-level initialization). This early
156 * GSI initialization can be done either by Trust Zone on the AP or by the
162 * implements the setup phase of initialization.
164 * If the modem performs early GSI initialization, the AP needs to know
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | irqchip.h | 22 * initialization function.
27 * @fn: initialization function
55 * the association between their version and their initialization function.
63 * @fn: initialization function
|
| /kernel/linux/linux-5.10/security/ |
| D | Kconfig.hardening | 11 the initialization. As this regularly leads to exploitable
20 menu "Memory initialization"
34 This option enables initialization of stack variables at
46 bool "no automatic initialization (weakest)"
48 Disable automatic stack variable initialization.
104 Pattern initialization is known to provoke many existing bugs
118 Zero initialization provides safe defaults for strings,
|
| /kernel/linux/linux-4.19/Documentation/crypto/ |
| D | intro.rst | 60 1. Initialization of a cipher handle.
67 When using the initialization API calls, a cipher handle is created and
68 returned to the consumer. Therefore, please refer to all initialization
70 to receive and subsequently to use. The initialization API calls have
|
| /kernel/linux/linux-5.10/Documentation/crypto/ |
| D | intro.rst | 60 1. Initialization of a cipher handle.
67 When using the initialization API calls, a cipher handle is created and
68 returned to the consumer. Therefore, please refer to all initialization
70 to receive and subsequently to use. The initialization API calls have
|
| /kernel/linux/linux-5.10/arch/arm64/kvm/vgic/ |
| D | vgic-init.c | 16 * Initialization rules: there are multiple stages to the vgic
17 * initialization, both for the distributor and the CPU interfaces. The basic
21 * initialization flags to ensure they don't look at uninitialized data
26 * - kvm_vgic_early_init(): initialization of static data that doesn't
30 * - vgic_init(): allocation and initialization of the generic data
37 * - kvm_vgic_vcpu_init(): initialization of static data that
48 * Only do initialization of static structures that don't require any
146 * require prior initialization in case of a virtual GICv3 or trigger in kvm_vgic_dist_init()
147 * initialization when using a virtual GICv2. in kvm_vgic_dist_init()
182 * Only do initialization, but do not actually enable the
[all …]
|
| /kernel/linux/linux-4.19/virt/kvm/arm/vgic/ |
| D | vgic-init.c | 27 * Initialization rules: there are multiple stages to the vgic
28 * initialization, both for the distributor and the CPU interfaces. The basic
32 * initialization flags to ensure they don't look at uninitialized data
37 * - kvm_vgic_early_init(): initialization of static data that doesn't
41 * - vgic_init(): allocation and initialization of the generic data
48 * - kvm_vgic_vcpu_init(): initialization of static data that
59 * Only do initialization of static structures that don't require any
167 * require prior initialization in case of a virtual GICv3 or trigger in kvm_vgic_dist_init()
168 * initialization when using a virtual GICv2. in kvm_vgic_dist_init()
203 * Only do initialization, but do not actually enable the
[all …]
|
| /kernel/linux/linux-5.10/drivers/phy/marvell/ |
| D | Kconfig | 82 SoC. This driver will do the PHY initialization and shutdown.
93 SoC. This driver will do the PHY initialization and shutdown.
104 SoC. This driver will do the PHY initialization and shutdown.
115 SoC. This driver will do the PHY initialization and shutdown.
|
| /kernel/linux/linux-4.19/Documentation/timers/ |
| D | hpet.txt | 20 The driver supports detection of HPET driver allocation and initialization
23 initialization. An example of this initialization can be found in
|
| /kernel/linux/linux-5.10/include/media/ |
| D | v4l2-flash-led-class.h | 21 * struct v4l2_flash_ctrl_data - flash control initialization data, filled
24 * @config: initialization data for a control
53 * struct v4l2_flash_config - V4L2 Flash sub-device initialization data
121 * @config: initialization data for V4L2 Flash sub-device
142 * @config: initialization data for V4L2 Flash sub-device
|
| /kernel/linux/linux-4.19/drivers/crypto/ux500/cryp/ |
| D | cryp.h | 146 /* Cryp Initialization structure */
174 * @init_vect_0_l: Initialization vector 0l register
175 * @init_vect_0_r: Initialization vector 0r register
176 * @init_vect_1_l: Initialization vector 1l register
177 * @init_vect_1_r: Initialization vector 0r register
255 /* Initialization functions */
|
| /kernel/linux/linux-5.10/drivers/crypto/ux500/cryp/ |
| D | cryp.h | 146 /* Cryp Initialization structure */
174 * @init_vect_0_l: Initialization vector 0l register
175 * @init_vect_0_r: Initialization vector 0r register
176 * @init_vect_1_l: Initialization vector 1l register
177 * @init_vect_1_r: Initialization vector 0r register
255 /* Initialization functions */
|
| /kernel/linux/linux-4.19/Documentation/rapidio/ |
| D | rapidio.txt | 64 The RapidIO subsystem defines the format and initialization method for subsystem
92 3. Subsystem Initialization
97 within the subsystem controller driver's initialization code calls function
123 automatically during kernel initialization time using corresponding module
150 initialization routine. In this case an enumerating module shall be loaded
209 initialization routine calls rio_init_mports() to perform enumeration or
241 process from module initialization routine.
259 table entry contains a pointer to a switch-specific initialization routine that
261 hardware initialization if necessary. A RapidIO switch does not have a unique
297 initialization.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/driver-api/rapidio/ |
| D | rapidio.rst | 67 The RapidIO subsystem defines the format and initialization method for subsystem
98 3. Subsystem Initialization
103 within the subsystem controller driver's initialization code calls function
129 automatically during kernel initialization time using corresponding module
156 initialization routine. In this case an enumerating module shall be loaded
217 initialization routine calls rio_init_mports() to perform enumeration or
249 process from module initialization routine.
267 table entry contains a pointer to a switch-specific initialization routine that
269 hardware initialization if necessary. A RapidIO switch does not have a unique
305 initialization.
[all …]
|
| /kernel/linux/linux-5.10/lib/ |
| D | test_stackinit.c | 91 * @var_type: type to be tested for zeroing initialization
93 * @init_level: what kind of initialization is performed
260 /* Static initialization: padding may be left uninitialized. */
263 /* Dynamic initialization: padding may be left uninitialized. */
266 /* Runtime initialization: padding may be left uninitialized. */
269 /* No initialization without compiler instrumentation. */
327 * GCC nor Clang have a way to perform initialization of variables in
358 /* Padding initialization depends on compiler behaviors. */ in test_stackinit_init()
|
| /kernel/linux/linux-4.19/drivers/gpio/ |
| D | devres.c | 58 * @flags: optional GPIO initialization flags
76 * @flags: optional GPIO initialization flags
95 * @flags: optional GPIO initialization flags
133 * @dflags: GPIO initialization flags
176 * @flags: GPIO initialization flags
231 * @flags: optional GPIO initialization flags
259 * @flags: optional GPIO initialization flags
294 * @flags: optional GPIO initialization flags
|
| /kernel/linux/linux-5.10/drivers/firewire/ |
| D | init_ohci1394_dma.c | 17 * To use physical DMA after the initialization of the firewire stack,
19 * which may be caused by the firewire stack initialization.
84 /* Resets an OHCI-1394 controller (for sane state before initialization) */
171 * OHCI1394 initialization itself and any device going on- or offline
222 * The initialization causes at least one IEEE1394 bus reset. Enabling in init_ohci1394_reset_and_init_dma()
286 * setup_init_ohci1394_early - enables early OHCI1394 DMA initialization
295 /* passing ohci1394_dma=early on boot causes early OHCI1394 DMA initialization */
|
| /kernel/linux/linux-5.10/Documentation/timers/ |
| D | hpet.rst | 22 The driver supports detection of HPET driver allocation and initialization
25 initialization. An example of this initialization can be found in
|