| /linux/Documentation/gpu/nova/core/ |
| H A D | devinit.rst | 4 Device Initialization (devinit)
10 Device initialization (devinit) is a crucial sequence of register read/write operations
15 Unit) microcontroller of the GPU. This interpreter executes a "script" of initialization
31 Low-level Firmware Initialization Flow
35 considered unusable until this initialization process completes.
46 Before the driver can proceed with further initialization, it must wait for a signal
47 indicating that core initialization is complete (known as GFW_BOOT). This signal is
57 The initialization process involves careful privilege management. For example, before
|
| /linux/drivers/net/ipa/ |
| H A 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/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
|
| /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,
|
| /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
|
| /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
|
| /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.
|
| /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 …]
|
| /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) */
172 * OHCI1394 initialization itself and any device going on- or offline
227 * The initialization causes at least one IEEE1394 bus reset. Enabling in init_ohci1394_reset_and_init_dma()
295 * setup_ohci1394_dma - enables early OHCI1394 DMA initialization
305 /* passing ohci1394_dma=early on boot causes early OHCI1394 DMA initialization */
|
| /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()
|
| /linux/scripts/coccinelle/misc/ |
| H A 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/drivers/media/tuners/ |
| H A D | qt1010_priv.h | 46 1f 20 ? chip initialization
47 20 e0 ? chip initialization
52 25 40 ? chip initialization
|
| /linux/arch/arm/mach-omap2/ |
| H A 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/Documentation/networking/devlink/ |
| H A 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/rust/pin-init/ |
| H A D | README.md | 27 It also allows in-place initialization of big `struct`s that would otherwise produce a stack
38 <https://rust-for-linux.com/the-safe-pinned-initialization-problem>.
40 This library allows you to do in-place initialization safely.
73 Aside from pinned initialization, this library also supports in-place construction without
151 actually does the initialization in the correct way. Here are the things to look out for
153 - when the closure returns `Ok(())`, then it has completed the initialization successfully, so
156 you need to take care to clean up anything if your initialization fails mid-way,
|
| /linux/drivers/phy/realtek/ |
| H A D | Kconfig | 17 DWC3 USB IP. This driver will do the PHY initialization
29 DWC3 USB IP. This driver will do the PHY initialization
|
| /linux/include/soc/at91/ |
| H A D | sama7-ddr.h | 15 #define DDR3PHY_PIR (0x04) /* DDR3PHY PHY Initialization Register */
20 #define DDR3PHY_PIR_INIT (1 << 0) /* Initialization Trigger */
27 #define DDR3PHY_PGSR_IDONE (1 << 0) /* Initialization Done */
71 #define UDDRC_DFIMISC_DFI_INIT_COMPLETE_EN (1 << 0) /* PHY initialization complete enable signal */
|
| /linux/Documentation/w1/masters/ |
| H A D | omap-hdq.rst | 26 initialization pulse.In HDQ mode, the firmware does not require the host to
27 create an initialization pulse to the slave.However, the slave can be reset by
28 using an initialization pulse (also referred to as a break pulse).The slave
|
| /linux/drivers/clk/bcm/ |
| H A 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/drivers/edac/ |
| H A D | edac_module.c | 100 * module initialization entry point
113 * Harvest and clear any boot/initialization PCI parity errors in edac_init()
116 * module initialization. We should also do an initial clear in edac_init()
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-bus-dfl-devices-emif | 13 Description: Read-only. It indicates if the initialization completed on
14 this memory interface. "1" for initialization complete, "0"
|
| /linux/Documentation/driver-api/firmware/ |
| H A D | introduction.rst | 24 are already using asynchronous initialization mechanisms which will not
26 processing firmware might, and this can still delay boot or initialization,
|
| /linux/sound/usb/line6/ |
| H A D | variax.c | 51 This message is sent by the device during initialization and identifies
60 This message is the last one sent by the device during initialization.
81 not run immediately after initialization, must not run in interrupt
135 /* notify of complete initialization: */ in line6_variax_process_message()
|
| /linux/drivers/net/wireless/intel/iwlegacy/ |
| H A D | prph.h | 121 * 1) Initialization -- performs hardware calibration and sets up some
125 * The initialization program must be used when initially setting up the
157 * The bootstrap uCode (already in instruction SRAM) loads initialization
158 * uCode. Initialization uCode performs data initialization, sends
164 * byte count register ("1" in MSbit tells initialization uCode to load
184 * image and the cached (modified) runtime data (*not* the initialization
188 * NOTE: Initialization uCode does *not* run as part of the save/restore
193 * RFKILL should use complete restarts (with total re-initialization) of uCode,
305 * Initialization:
338 * write and read pointers (idxes) during (re-)initialization (i.e. when
|
| /linux/drivers/ntb/hw/idt/ |
| H A D | Kconfig | 11 initialization of EEPROM connected to master SMbus of the switch or
26 kernel PCI fixups. That's why the alternative pre-initialization
|