Home
last modified time | relevance | path

Searched full:initialization (Results 1 – 25 of 4112) sorted by relevance

12345678910>>...165

/OK3568_Linux_fs/kernel/drivers/gpu/arm/bifrost/device/backend/
H A Dmali_kbase_device_csf.c66 * kbase_backend_late_init - Perform any backend-specific initialization.
178 * kbase_csf_early_init - Early initialization for firmware & scheduler.
206 * kbase_csf_late_init - late initialization for firmware.
289 "Dummy model initialization failed" },
296 { power_control_init, power_control_term, "Power control initialization failed" },
298 "Register access history initialization failed" },
299 { kbase_device_early_init, kbase_device_early_term, "Early device initialization failed" },
301 { kbase_pm_lowest_gpu_freq_init, NULL, "Lowest freq initialization failed" },
303 "Miscellaneous device initialization failed" },
305 "Priority control manager initialization failed" },
[all …]
H A Dmali_kbase_device_jm.c48 * kbase_backend_late_init - Perform any backend-specific initialization.
218 { kbase_gpu_device_create, kbase_gpu_device_destroy, "Dummy model initialization failed" },
226 "Register access history initialization failed" },
227 { kbase_device_pm_init, kbase_device_pm_term, "Power management initialization failed" },
228 { kbase_device_early_init, kbase_device_early_term, "Early device initialization failed" },
230 { kbase_pm_lowest_gpu_freq_init, NULL, "Lowest freq initialization failed" },
232 "Miscellaneous device initialization failed" },
234 "Priority control manager initialization failed" },
235 { kbase_ctx_sched_init, kbase_ctx_sched_term, "Context scheduler initialization failed" },
236 { kbase_mem_init, kbase_mem_term, "Memory subsystem initialization failed" },
[all …]
/OK3568_Linux_fs/kernel/drivers/gpu/arm/bifrost/context/backend/
H A Dmali_kbase_context_jm.c131 "Common context initialization failed" },
133 "Memory pool group initialization failed" },
135 "Memory evictable initialization failed" },
137 "MMU initialization failed" },
141 "Region tracker initialization failed" },
143 "Sticky resource initialization failed" },
144 { kbase_jit_init, kbase_jit_term, "JIT initialization failed" },
147 "JM instrumentation initialization failed" },
149 "Timers initialization failed" },
151 "Event initialization failed" },
[all …]
H A Dmali_kbase_context_csf.c90 "Common context initialization failed" },
92 "Memory pool group initialization failed" },
94 "Memory evictable initialization failed" },
96 "MMU initialization failed" },
100 "Region tracker initialization failed" },
102 "Sticky resource initialization failed" },
103 { kbase_jit_init, kbase_jit_term, "JIT initialization failed" },
105 "CSF context initialization failed" },
/OK3568_Linux_fs/kernel/drivers/acpi/acpica/
H A Dutxfinit.c4 * 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 Ddsinit.c4 * 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()
H A Dnsinit.c4 * 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 …]
/OK3568_Linux_fs/kernel/drivers/misc/habanalabs/include/common/
H A Dhl_boot_if.h19 * 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
/OK3568_Linux_fs/u-boot/arch/x86/include/asm/arch-quark/
H A Dmrc.h98 #define MRC_SUCCESS 0 /* initialization ok */
107 * - output parameters like initialization result and memory size
150 /* initialization result (non zero specifies error code) */
159 * MRC memory initialization structure
161 * post_code: a 16-bit post code of a specific initialization routine
163 * init_fn: real memory initialization routine
181 * mrc_init - Memory Reference Code initialization entry routine
/OK3568_Linux_fs/kernel/security/
H A DKconfig.hardening11 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.
119 Pattern initialization is known to provoke many existing bugs
137 Zero initialization provides safe defaults for strings
141 initialization.
/OK3568_Linux_fs/kernel/arch/mips/include/asm/octeon/
H A Dcvmx-spi.h46 /** 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)
/OK3568_Linux_fs/kernel/drivers/net/ipa/
H A Dipa.h141 * 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
/OK3568_Linux_fs/u-boot/arch/arm/mach-uniphier/dram/
H A Dddrphy-regs.h17 #define PHY_PIR_INIT BIT(0) /* Initialization Trigger */
19 #define PHY_PIR_PLLINIT BIT(4) /* PLL Initialization */
23 #define PHY_PIR_DRAMINIT BIT(8) /* DRAM Initialization */
34 #define PHY_PIR_INITBYP BIT(31) /* Initialization Bypass */
39 #define PHY_PGSR0_IDONE BIT(0) /* Initialization Done */
43 #define PHY_PGSR0_DIDONE BIT(4) /* DRAM Initialization Done */
51 #define PHY_PGSR0_DIERR BIT(20) /* DRAM Initialization Error */
H A Dddrmphy-regs.h18 #define MPHY_PIR_INIT BIT(0) /* Initialization Trigger */
20 #define MPHY_PIR_PLLINIT BIT(4) /* PLL Initialization */
24 #define MPHY_PIR_DRAMINIT BIT(8) /* DRAM Initialization */
33 #define MPHY_PIR_INITBYP BIT(31) /* Initialization Bypass */
43 #define MPHY_PGSR0_IDONE BIT(0) /* Initialization Done */
47 #define MPHY_PGSR0_DIDONE BIT(4) /* DRAM Initialization Done */
/OK3568_Linux_fs/kernel/arch/arm64/kvm/vgic/
H A Dvgic-init.c16 * 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 …]
/OK3568_Linux_fs/kernel/Documentation/driver-api/rapidio/
H A Drapidio.rst67 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 …]
/OK3568_Linux_fs/kernel/include/linux/
H A Dirqchip.h22 * initialization function.
27 * @fn: initialization function
55 * the association between their version and their initialization function.
63 * @fn: initialization function
/OK3568_Linux_fs/kernel/Documentation/crypto/
H A Dintro.rst60 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
/OK3568_Linux_fs/kernel/drivers/crypto/ux500/cryp/
H A Dcryp.h146 /* 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 */
/OK3568_Linux_fs/kernel/lib/
H A Dtest_stackinit.c91 * @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()
/OK3568_Linux_fs/kernel/drivers/firewire/
H A Dinit_ohci1394_dma.c17 * 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 */
/OK3568_Linux_fs/kernel/include/media/
H A Dv4l2-flash-led-class.h21 * 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
/OK3568_Linux_fs/u-boot/arch/x86/include/asm/
H A Di8259.h16 #define ICW1 0x0 /* Initialization Control Word 1 */
19 #define ICW2 0x1 /* Initialization Control Word 2 */
20 #define ICW3 0x1 /* Initialization Control Word 3 */
21 #define ICW4 0x1 /* Initialization Control Word 4 */
/OK3568_Linux_fs/kernel/drivers/phy/marvell/
H A DKconfig82 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.
/OK3568_Linux_fs/buildroot/package/glibc/2.28-69-g1e5c5303a522764d7e9d2302a60e4a32cdb902f1/
H A D0012-Properly-initialize-audit-cookie-for-the-dynamic-loa.patch76 +/* Check cookie initialization for many auditors. Main program.
108 +/* Check cookie initialization for many auditors. Auditor template.
178 +/* Check cookie initialization for many auditors. Auditor 1.
204 +/* Check cookie initialization for many auditors. Auditor 2.
230 +/* Check cookie initialization for many auditors. Auditor 3.
256 +/* Check cookie initialization for many auditors. Auditor 4.
282 +/* Check cookie initialization for many auditors. Auditor 5.
308 +/* Check cookie initialization for many auditors. Auditor 6.
334 +/* Check cookie initialization for many auditors. Auditor 7.
360 +/* Check cookie initialization for many auditors. Auditor 8.
[all …]

12345678910>>...165