Searched full:initialisation (Results 1 – 25 of 37) sorted by relevance
12
| /Documentation/arm/ |
| D | setup.rst | 2 Kernel initialisation parameters on ARM Linux
5 The following document describes the kernel initialisation parameter
9 This structure is used to pass initialisation parameters from the
11 through the kernel initialisation process. As a general rule, it
|
| D | cluster-pm-race-avoidance.rst | 72 It may be part way through the process of initialisation and
469 initialisation: any other CPUs must wait for this to complete before
472 Cluster-level initialisation may involve actions such as configuring
|
| D | kernel_user_helpers.rst | 73 field can be read once during the initialisation of a library or
|
| /Documentation/devicetree/bindings/regulator/ |
| D | cirrus,lochnagar.txt | 22 - VDDCORE : Initialisation data for the VDDCORE regulator, which
30 - MICVDD : Initialisation data for the MICVDD regulator, which
37 - MIC1VDD, MIC2VDD : Initialisation data for the MICxVDD supplies.
|
| D | max8973-regulator.txt | 20 -maxim,dvs-default-state: Default state of GPIO during initialisation.
|
| /Documentation/power/regulator/ |
| D | machine.rst | 6 initialisation code to configure the regulator subsystem.
16 initialisation code by creating a struct regulator_consumer_supply for
|
| D | overview.rst | 46 bootloader, firmware or kernel board initialisation code.
105 level board initialisation code. It is used to constrain a
|
| /Documentation/driver-api/usb/ |
| D | callbacks.rst | 83 genuine error occurred during initialisation which prevented a driver
90 initialisation that doesn't take too long is a good idea here.
|
| D | anchors.rst | 15 Allocation and Initialisation
|
| /Documentation/devicetree/bindings/arm/ |
| D | pmu.yaml | 80 appropriate initialisation. Note that this property is
|
| /Documentation/filesystems/caching/ |
| D | operations.txt | 11 (*) Operation record initialisation.
37 OPERATION RECORD INITIALISATION
|
| D | object.txt | 108 (2) Initialisation: states that perform lookups in the cache and validate
169 There are initialisation states in which the object sets itself up and accesses
|
| /Documentation/networking/ |
| D | z8530book.rst | 85 channels and do any necessary board level initialisation to configure
134 a channel be aware that the documentation recommends initialisation
138 initialisation values in an array of u8 type. The first value is the
|
| D | lapb-module.txt | 25 The two LAPB specific structures are the LAPB initialisation structure and
30 LAPB Initialisation Structure
|
| /Documentation/usb/ |
| D | functionfs.rst | 12 This in particular means that the composite initialisation functions
|
| /Documentation/i2c/ |
| D | upgrading-clients.rst | 59 /* rest of the initialisation goes here. */
254 /* rest of the initialisation goes here. */
|
| /Documentation/sound/soc/ |
| D | machine.rst | 56 initialisation e.g. the machine audio map can be connected to the codec audio
|
| /Documentation/filesystems/ |
| D | sysfs-pci.txt | 73 the count. Even when it returns to 0, though, some of the initialisation
|
| /Documentation/fb/ |
| D | ep93xx-fb.rst | 40 your board initialisation function::
|
| D | sstfb.rst | 183 initialisation will fail. This is specifically true for
|
| /Documentation/arm/samsung-s3c24xx/ |
| D | gpio.rst | 53 during initialisation.
|
| D | overview.rst | 280 with the rest of the initialisation code::
|
| /Documentation/ |
| D | padata.txt | 113 padata, but the structure should be zeroed at initialisation time, and the
|
| /Documentation/input/ |
| D | ff.rst | 33 initialisation phase. This happens for example with my "AVB Top Shot Pegasus".
|
| /Documentation/input/devices/ |
| D | iforce-protocol.rst | 302 Initialisation of the device
|
12