Searched full:initialization (Results 1 – 25 of 327) sorted by relevance
12345678910>>...14
| /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
|
| /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
|
| /Documentation/ABI/testing/ |
| 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"
|
| D | sysfs-driver-zynqmp-fpga | 38 BIT(11) 0: Initialization has not finished
39 1: Initialization finished
|
| /Documentation/driver-api/firmware/ |
| 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,
|
| /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:
|
| /Documentation/w1/masters/ |
| 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
|
| /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 …]
|
| /Documentation/core-api/ |
| D | boot-time-mm.rst | 5 Early system initialization cannot use "normal" memory management
11 boot time memory management. The architecture specific initialization
|
| D | union_find.rst | 17 Initialization: Resetting each element as an individual set, with
70 You can complete the initialization using either static or initialization
|
| D | debugging-via-ohci1394.rst | 34 Together with a early initialization of the OHCI-1394 controller for debugging,
48 completed, an initialization routine which runs pretty early has been
89 Step-by-step instructions for using firescope with early OHCI initialization:
147 4) Prepare for debugging with early OHCI-1394 initialization:
|
| D | debug-objects.rst | 17 - Initialization of active objects
70 This function is called whenever the initialization function of a real
78 problem before the real initialization of the object happens. E.g. it
93 This function is called whenever the initialization function of a real
101 problem before the real initialization of the object happens. E.g. it
|
| /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
|
| /Documentation/driver-api/ |
| D | w1.rst | 37 W1 internal initialization for master devices.
45 W1 internal initialization for master devices.
|
| D | ntb.rst | 40 mainly used to perform the proper memory window initialization. Typically
55 So typical scenario of the first type memory window initialization looks:
57 3) somehow notify a peer device of performed initialization, 4) peer device
73 Typical scenario of the second type interface initialization would be:
84 (it may fail if local memory window initialization is unsupported)
90 initialization is unsupported)
|
| /Documentation/locking/ |
| D | seqlock.rst | 56 Initialization::
98 initialization time, which enables lockdep to validate that the write
121 Initialization (replace "LOCKNAME" with one of the supported locks)::
171 Initialization::
225 /* marker; even initialization */
|
| /Documentation/admin-guide/pm/ |
| D | intel_idle.rst | 126 .. _intel-idle-initialization:
128 Initialization chapter
131 The initialization of ``intel_idle`` starts with checking if the kernel command
138 supports ``MWAIT`` (the initialization fails if that is not the case). Then,
140 driver initialization fails if the level of support is not as expected (for
158 optionally performs some CPU-specific initialization actions that may be
170 ``MWAIT`` instruction is not allowed to be used, so the initialization of
193 Setting ``max_cstate`` to 0 causes the ``intel_idle`` initialization to fail.
|
| /Documentation/devicetree/bindings/pci/ |
| D | spear13xx-pcie.txt | 14 - st,pcie-is-gen1 indicates that forced gen1 initialization is needed.
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | open-pic.txt | 32 shall not be reset during runtime initialization. No property value shall
34 initialization related to interrupt sources shall be limited to sources
|
| /Documentation/scsi/ |
| D | ufs.rst | 16 3.1 UFS controller initialization
121 3.1 UFS controller initialization
124 The initialization module brings the UFS host controller to active state
208 executing common controller initialization. If the value is available, UFS
|
| /Documentation/cpu-freq/ |
| D | cpu-drivers.rst | 17 1.1 Initialization
18 1.2 Per-CPU Initialization
36 1.1 Initialization
48 .init - A pointer to the per-policy initialization function.
90 1.2 Per-CPU Initialization
94 cpufreq driver registers itself, the per-policy initialization function
|
| /Documentation/mm/ |
| D | physical_memory.rst | 152 firmware. The bulk of the node initialization happens slightly later in the
154 :ref:`Initialization <initialization>`.
219 ``build_zonelists()`` in ``mm/page_alloc.c`` during the initialization of
259 If memory initialization on large machines is deferred then this is the first
366 Initialization chapter
|
| /Documentation/devicetree/bindings/crypto/ |
| D | xlnx,zynqmp-aes.yaml | 15 encrypt or decrypt the data with provided key and initialization vector.
|
| /Documentation/mhi/ |
| D | mhi.rst | 35 for downloading the firmware to the device before MHI initialization.
164 MHI is ready for initialization. The host can start MHI initialization by
187 MHI Initialization
|
| /Documentation/devicetree/bindings/hwmon/ |
| D | ibm,occ-hwmon.yaml | 26 be polled during driver initialization.
|
12345678910>>...14