| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/State/Boot/ |
| H A D | Progress.interface.yaml | 31 Primary Processor Initialization
34 Processor and Memory Bus Initialization
37 Memory Initialization
40 Secondary Processor Initialization
43 PCI resource initialization
58 Motherboard/Basebord Initialization.
|
| /openbmc/linux/drivers/acpi/acpica/ |
| H A 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 …]
|
| H A 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()
|
| /openbmc/u-boot/arch/x86/include/asm/arch-quark/ |
| H A D | mrc.h | 97 #define MRC_SUCCESS 0 /* initialization ok */
106 * - output parameters like initialization result and memory size
149 /* initialization result (non zero specifies error code) */
158 * MRC memory initialization structure
160 * post_code: a 16-bit post code of a specific initialization routine
162 * init_fn: real memory initialization routine
180 * mrc_init - Memory Reference Code initialization entry routine
|
| /openbmc/linux/arch/mips/include/asm/octeon/ |
| H A 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)
|
| /openbmc/u-boot/arch/arm/mach-uniphier/dram/ |
| H A D | ddrphy-regs.h | 16 #define PHY_PIR_INIT BIT(0) /* Initialization Trigger */
18 #define PHY_PIR_PLLINIT BIT(4) /* PLL Initialization */
22 #define PHY_PIR_DRAMINIT BIT(8) /* DRAM Initialization */
33 #define PHY_PIR_INITBYP BIT(31) /* Initialization Bypass */
38 #define PHY_PGSR0_IDONE BIT(0) /* Initialization Done */
42 #define PHY_PGSR0_DIDONE BIT(4) /* DRAM Initialization Done */
50 #define PHY_PGSR0_DIERR BIT(20) /* DRAM Initialization Error */
|
| H A D | ddrmphy-regs.h | 17 #define MPHY_PIR_INIT BIT(0) /* Initialization Trigger */
19 #define MPHY_PIR_PLLINIT BIT(4) /* PLL Initialization */
23 #define MPHY_PIR_DRAMINIT BIT(8) /* DRAM Initialization */
32 #define MPHY_PIR_INITBYP BIT(31) /* Initialization Bypass */
42 #define MPHY_PGSR0_IDONE BIT(0) /* Initialization Done */
46 #define MPHY_PGSR0_DIDONE BIT(4) /* DRAM Initialization Done */
|
| /openbmc/linux/drivers/net/ipa/ |
| H A D | ipa.h | 144 * IPA initialization is broken into stages: init; config; and setup.
152 * more complex initialization by issuing "immediate commands" using
158 * loaded (in addition to some other low-level initialization). This early
159 * GSI initialization can be done either by Trust Zone on the AP or by the
165 * implements the setup phase of initialization.
167 * If the modem performs early GSI initialization, the AP needs to know
|
| /openbmc/qemu/include/crypto/ |
| H A D | ivgen.h | 28 * This module provides a framework for generating initialization
31 * initialization vector for use for encryption of data in that
35 * <title>Encrypting block data with initialization vectors</title>
105 * @alg: the initialization vector generation algorithm
111 * Create a new initialization vector generator that uses
150 * Calculate a new initialization vector for the data
|
| /openbmc/linux/include/linux/ |
| H A D | irqchip.h | 29 * initialization function.
34 * @fn: initialization function
67 * the association between their version and their initialization function.
75 * @fn: initialization function
|
| /openbmc/linux/Documentation/crypto/ |
| H A 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
|
| /openbmc/u-boot/arch/x86/include/asm/ |
| H A D | i8259.h | 15 #define ICW1 0x0 /* Initialization Control Word 1 */
18 #define ICW2 0x1 /* Initialization Control Word 2 */
19 #define ICW3 0x1 /* Initialization Control Word 3 */
20 #define ICW4 0x1 /* Initialization Control Word 4 */
|
| /openbmc/linux/include/drm/ |
| H A 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,
|
| /openbmc/linux/include/media/ |
| H A 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
|
| /openbmc/linux/Documentation/driver-api/rapidio/ |
| H A 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 …]
|
| /openbmc/linux/arch/arm64/kvm/vgic/ |
| H A 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
155 * require prior initialization in case of a virtual GICv3 or trigger in kvm_vgic_dist_init()
156 * initialization when using a virtual GICv2. in kvm_vgic_dist_init()
191 * Only do initialization, but do not actually enable the
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-graphics/lvgl/files/ |
| H A D | 0004-Factor-out-fbdev-initialization-code.patch | 4 Subject: [PATCH 4/6] Factor out fbdev initialization code
6 Pull fbdev initialization code into separate function and add ifdef
8 preparation for addition of other backend initialization example
|
| /openbmc/linux/drivers/phy/marvell/ |
| H A 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.
|
| /openbmc/docs/designs/ |
| H A D | bios-bmc-smm-error-logging.md | 40 2. After initialization, the BIOS shall not have to wait for an ack back from
73 …i>BIT2 - BMC_READY<ul><li>BMC sets this bit once it has received any initialization information it…
76 …s overflow and not already overflowed</li></ul><li>BIT2 - Incomplete Initialization<ul><li>Set whe…
82 ### Initialization subsection
90 If there are any further initialization between the BIOS and the BMC required,
92 initialization completes. If the BIOS does not see the flag being set, the BIOS
93 shall set the `Incomplete Initialization` flag to notify the BMC to reinitialize
154 - Initialization
|
| /openbmc/linux/security/ |
| H A 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.
|
| /openbmc/openpower-proc-control/extensions/phal/ |
| H A D | common_utils.cpp | 34 throw std::runtime_error("pdbg target initialization failed"); in phal_init()
40 throw std::runtime_error("libekb initialization failed"); in phal_init()
46 throw std::runtime_error("libipl initialization failed"); in phal_init()
|
| /openbmc/linux/Documentation/timers/ |
| H A 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
|
| /openbmc/linux/drivers/firewire/ |
| H A 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 */
|
| /openbmc/linux/drivers/media/pci/mantis/ |
| H A 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()
|
| /openbmc/u-boot/board/armltd/integrator/ |
| H A D | README | 34 In case c) it may be necessary for U-Boot to perform CM dependent initialization.
47 Code specific to initialization of a particular ARM processor has been placed in
58 Code specific to the initialization of the CM, rather than the cpu, and initialization
|