Searched full:initialized (Results 1 – 25 of 212) sorted by relevance
123456789
| /Documentation/RCU/ |
| D | NMI-RCU.rst | 71 data that is to be used by the callback must be initialized up -before- 74 initialized values:: 110 initialized some data that is to be used by the new NMI 114 to the new NMI handler, but the old pre-initialized
|
| /Documentation/core-api/ |
| D | debug-objects.rst | 74 whether the object can be initialized. Initializing is not allowed for 97 whether the object can be initialized. Initializing is not allowed for 130 allow the legitimate activation of statically allocated and initialized 191 This function is called to assert that an object has been initialized. 247 The activation of statically initialized objects is a special case. When 251 this is a legitimate case of a statically initialized object or not. In 301 The handling of statically initialized objects is a special case. The 303 initialized object or not. In this case only debug_object_init()
|
| /Documentation/devicetree/bindings/gpio/ |
| D | nxp,pcf8575.yaml | 59 When a bit is set to zero, the corresponding line will be initialized to 61 When the bit is set to one, the line will be initialized to the 63 If the property is not specified all lines will be initialized to the
|
| /Documentation/filesystems/ |
| D | autofs-mount-control.rst | 216 This structure can be initialized before setting specific fields by using 250 implementation. It requires an initialized struct autofs_dev_ioctl as an 260 by loaded module. This call requires an initialized struct autofs_dev_ioctl 271 path. The open call requires an initialized struct autofs_dev_ioctl with 275 shown in /proc/mounts. The close call requires an initialized struct 287 Both of these calls require an initialized struct autofs_dev_ioctl 305 The call requires an initialized struct autofs_dev_ioctl with the 320 The call requires an initialized struct autofs_dev_ioctl with the 329 The call requires an initialized struct autofs_dev_ioctl with the 339 The call requires an initialized struct autofs_dev_ioctl with the path [all …]
|
| /Documentation/userspace-api/media/mediactl/ |
| D | media-request-ioc-reinit.rst | 38 be re-initialized and it is ready to be used again. 40 A request can only be re-initialized if it either has not been queued
|
| /Documentation/devicetree/bindings/mmc/ |
| D | mmc-pwrseq-emmc.yaml | 16 fix possible issues if bootloader has left eMMC card in initialized or 21 card if the card is left in unknown or already initialized state.
|
| /Documentation/driver-api/mei/ |
| D | mei.rst | 108 ENODEV Device or Connection is not initialized or ready. 145 ENODEV Device or Connection is not initialized or ready. 173 ENODEV Device is not initialized or the client not connected 198 ENODEV Device is not initialized or the client not connected
|
| /Documentation/fb/ |
| D | arkfb.rst | 12 - only BIOS initialized VGA devices supported 49 * secondary (not initialized by BIOS) device support
|
| D | s3fb.rst | 16 - only BIOS initialized VGA devices supported 58 * secondary (not initialized by BIOS) device support
|
| /Documentation/dev-tools/ |
| D | kmsan.rst | 85 ignore uninitialized values in that function and mark its output as initialized. 139 initialized (setting the shadow bytes to ``0x00``) is called unpoisoning. 143 that is immediately initialized). Any new heap allocation done without 165 ``c`` are uninitialized, while the lower byte is initialized. 211 If ``a`` is initialized and ``b`` is not, the shadow of the result would be 214 that variable is initialized. 306 initialized or copied, making sure shadow and origin values are copied alongside 411 ``dummy_load_page`` is zero-initialized, so reads from it always yield zeroes.
|
| /Documentation/driver-api/usb/ |
| D | usb3-debug-port.rst | 28 When DbC is initialized and enabled, it will present a debug 40 crashes very early before the regular console code is initialized. 66 initialized. After initialization, the debug host should be able
|
| /Documentation/virt/kvm/devices/ |
| D | vcpu.rst | 51 -ENODEV PMUv3 not supported or GIC not initialized 54 -EBUSY PMUv3 already initialized 70 -ENODEV PMUv3 not supported or GIC not initialized 73 -EBUSY PMUv3 already initialized or a VCPU has already run 116 -EBUSY PMUv3 already initialized, a VCPU has already run or 120 -ENODEV PMUv3 not supported or GIC not initialized
|
| /Documentation/devicetree/bindings/rtc/ |
| D | rtc-cmos.txt | 15 "Register A" and "B" are usually initialized by the firmware (BIOS for
|
| /Documentation/locking/ |
| D | percpu-rw-semaphore.rst | 19 The lock is initialized percpu_init_rwsem, it returns 0 on success and
|
| /Documentation/ABI/testing/ |
| D | sysfs-driver-hid-wiimote | 16 Description: This file contains the currently connected and initialized 33 Description: While a device is initialized by the wiimote driver, we perform
|
| /Documentation/devicetree/bindings/net/bluetooth/ |
| D | nxp,88w8987-bt.yaml | 30 Chip baudrate after FW is downloaded and initialized.
|
| /Documentation/admin-guide/blockdev/ |
| D | nbd.rst | 31 Number of block devices that should be initialized (default: 16).
|
| /Documentation/admin-guide/cgroup-v1/ |
| D | net_cls.rst | 14 This net_cls.classid value is initialized to 0.
|
| /Documentation/devicetree/bindings/power/reset/ |
| D | gpio-poweroff.yaml | 36 property is not specified, the GPIO is initialized as an output in its inactive state.
|
| /Documentation/filesystems/ext4/ |
| D | group_descr.rst | 169 - inode table and bitmap are not initialized (EXT4_BG_INODE_UNINIT). 171 - block bitmap is not initialized (EXT4_BG_BLOCK_UNINIT).
|
| /Documentation/networking/ |
| D | gen_stats.rst | 85 are responsible for making sure that the lock is initialized. 106 2) make sure you have initialized stats lock that is used to setup such
|
| D | phy-link-topology.rst | 71 resource, that gets initialized at netdevice creation. Once it's initialized,
|
| /Documentation/devicetree/bindings/hwmon/ |
| D | max6697.txt | 52 Transistor ideality will be initialized to default (1.008) if not
|
| /Documentation/devicetree/bindings/bus/ |
| D | simple-pm-bus.yaml | 14 driver, as it's typically initialized by the boot loader.
|
| /Documentation/devicetree/bindings/pci/ |
| D | host-generic-pci.yaml | 50 Firmware-initialized PCI host controller to on-chip devices found on 57 Cavium ThunderX PEM firmware-initialized PCIe host controller
|
123456789