/linux-6.12.1/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()
|
D | nsinit.c | 4 * Module Name: nsinit - namespace initialization 42 * initialization on the objects found therein 54 "[Init] Completing Initialization of ACPI Objects\n")); in acpi_ns_initialize_objects() 56 "**** Starting initialization of namespace objects ****\n")); in acpi_ns_initialize_objects() 58 "Final data object initialization: ")); in acpi_ns_initialize_objects() 68 * is now the only one that supports deferred initialization in acpi_ns_initialize_objects() 239 ACPI_EXCEPTION((AE_INFO, status, "During device initialization")); in acpi_ns_initialize_devices() 309 * Currently, the only objects that require initialization are: 385 * Only initialization of Package objects can be deferred, in order in acpi_ns_init_one_object() 399 /* Complete the initialization/resolution of the package object */ in acpi_ns_init_one_object() [all …]
|
/linux-6.12.1/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)
|
/linux-6.12.1/drivers/net/ipa/ |
D | ipa.h | 138 * IPA initialization is broken into stages: init; config; and setup. 146 * more complex initialization by issuing "immediate commands" using 152 * loaded (in addition to some other low-level initialization). This early 153 * GSI initialization can be done either by Trust Zone on the AP or by the 159 * implements the setup phase of initialization. 161 * If the modem performs early GSI initialization, the AP needs to know
|
/linux-6.12.1/include/linux/ |
D | irqchip.h | 29 * initialization function. 34 * @fn: initialization function 67 * the association between their version and their initialization function. 75 * @fn: initialization function
|
/linux-6.12.1/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
|
/linux-6.12.1/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 …]
|
/linux-6.12.1/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
|
/linux-6.12.1/include/drm/ |
D | drm_module.h | 15 * initialization and shutdown. The provided helpers act like bus-specific 30 * the PCI driver my_pci_drv. For more complex module initialization, you 52 * drm_firmware_drivers_only(). For more complex module initialization, 115 * drm_firmware_drivers_only(). For more complex module initialization,
|
/linux-6.12.1/security/ |
D | Kconfig.hardening | 11 the initialization. As this regularly leads to exploitable 20 menu "Memory initialization" 44 This option enables initialization of stack variables at 56 bool "no automatic stack variable initialization (weakest)" 58 Disable automatic stack variable initialization. 123 Pattern initialization is known to provoke many existing bugs 142 Zero initialization provides safe defaults for strings 146 initialization.
|
/linux-6.12.1/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_ohci1394_dma - enables early OHCI1394 DMA initialization 295 /* passing ohci1394_dma=early on boot causes early OHCI1394 DMA initialization */
|
/linux-6.12.1/drivers/media/pci/mantis/ |
D | mantis_cards.c | 178 dprintk(MANTIS_ERROR, 1, "ERROR: Mantis PCI initialization failed <%d>", err); in mantis_pci_probe() 190 dprintk(MANTIS_ERROR, 1, "ERROR: Mantis I2C initialization failed <%d>", err); in mantis_pci_probe() 202 dprintk(MANTIS_ERROR, 1, "ERROR: Mantis DMA initialization failed <%d>", err); in mantis_pci_probe() 208 dprintk(MANTIS_ERROR, 1, "ERROR: Mantis DVB initialization failed <%d>", err); in mantis_pci_probe() 215 "ERROR: Mantis DVB initialization failed <%d>", err); in mantis_pci_probe() 221 dprintk(MANTIS_ERROR, 1, "ERROR: Mantis UART initialization failed <%d>", err); in mantis_pci_probe()
|
/linux-6.12.1/drivers/phy/marvell/ |
D | Kconfig | 90 SoC. This driver will do the PHY initialization and shutdown. 101 SoC. This driver will do the PHY initialization and shutdown. 112 SoC. This driver will do the PHY initialization and shutdown. 123 SoC. This driver will do the PHY initialization and shutdown.
|
/linux-6.12.1/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
|
/linux-6.12.1/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 153 * require prior initialization in case of a virtual GICv3 or trigger in kvm_vgic_dist_init() 154 * initialization when using a virtual GICv2. in kvm_vgic_dist_init() 243 * Only do initialization, but do not actually enable the [all …]
|
/linux-6.12.1/scripts/coccinelle/misc/ |
D | uninitialized_var.cocci | 12 /// changes. Keep in mind that in most cases, if an initialization is 50 coccilib.report.print_report(p[0], "WARNING this kind of initialization is deprecated") 56 coccilib.org.print_todo(p[0], "WARNING this kind of initialization is deprecated")
|
/linux-6.12.1/drivers/media/tuners/ |
D | qt1010_priv.h | 46 1f 20 ? chip initialization 47 20 e0 ? chip initialization 52 25 40 ? chip initialization
|
/linux-6.12.1/drivers/gpio/ |
D | gpiolib-devres.c | 54 * @flags: optional GPIO initialization flags 77 * @flags: optional GPIO initialization flags 101 * @flags: optional GPIO initialization flags 157 * @flags: GPIO initialization flags 200 * @flags: optional GPIO initialization flags 231 * @flags: optional GPIO initialization flags 272 * @flags: optional GPIO initialization flags
|
/linux-6.12.1/drivers/reset/ |
D | reset-intel-gw.c | 192 dev_err(dev, "regmap initialization failed\n"); in intel_reset_probe() 257 * or resource initialization happens in system core initialization. 259 * specific devices to perform reset operation as part of initialization. 260 * So perform RCU as post core initialization.
|
/linux-6.12.1/drivers/clk/bcm/ |
D | clk-kona.h | 89 /* Policy initialization macro */ 145 * Gate initialization macros. 209 /* Hysteresis initialization macro */ 281 /* Divider initialization macros */ 341 /* Selector initialization macro */ 374 /* Trigger initialization macro */ 409 /* Initialization macro for an entry in a CCU's kona_clks[] array. */ 433 /* Policy enable initialization macro */ 447 /* Policy control initialization macro */ 482 /* Initialization for common fields in a Kona ccu_data structure */
|
/linux-6.12.1/Documentation/gpu/ |
D | drm-internals.rst | 9 First, we go over some typical driver initialization requirements, like 21 Driver Initialization 48 initialization time and passed to userspace through the 64 The driver name is printed to the kernel log at initialization time, 72 Module Initialization 114 Memory Manager Initialization
|
/linux-6.12.1/Documentation/networking/devlink/ |
D | devlink-reload.rst | 23 - Devlink driver entities re-initialization, including applying 30 Other devlink entities may stay over the re-initialization: 81 # Run reload command for devlink driver entities re-initialization:
|
/linux-6.12.1/arch/arm/mach-omap2/ |
D | omap_opp_data.h | 20 * USE the following ONLY in opp data initialization common to an SoC. 52 * Initialization wrapper used to define an OPP for OMAP variants. 63 * Initialization wrapper used to define SmartReflex process data
|
/linux-6.12.1/drivers/net/wireless/intel/ipw2x00/ |
D | Kconfig | 35 initialization time, and when built-in this typically happens 37 unavailable and initialization will fail). If you do choose to build 97 initialization time, and when built-in this typically happens 99 unavailable and initialization will fail). If you do choose to build
|