loading (reference) in projects: Linux-v4.19

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched refs:loading (Results 1 – 25 of 217) sorted by relevance

12 3 4 5 6 7 8 9

/Linux-v4.19/tools/testing/selftests/firmware/
D	fw_fallback.sh	`31 while [ ! -e "$DIR"/"$name"/loading ]; do 40 echo 1 >"$DIR"/"$name"/loading 42 echo 0 >"$DIR"/"$name"/loading 58 while [ ! -e "$DIR"/"$name"/loading ]; do 67 echo -1 >"$DIR"/"$name"/loading 87 while [ ! -e "$DIR"/"$name"/loading ]; do 96 echo 1 >"$DIR"/"$name"/loading 98 echo 0 >"$DIR"/"$name"/loading 120 while [ ! -e "$DIR"/"$name"/loading ]; do 129 echo -1 >"$DIR"/"$name"/loading [all …]`
D	fw_filesystem.sh	`220 while [ ! -e "$DIR"/"$name"/loading ]; do 229 echo -1 >"$DIR"/"$name"/loading`
/Linux-v4.19/Documentation/leds/
D	leds-lp55xx.txt	82 echo 1 > /sys/class/firmware/lp5521/loading 84 echo 0 > /sys/class/firmware/lp5521/loading 90 echo 1 > /sys/class/firmware/lp55231/loading 92 echo 0 > /sys/class/firmware/lp55231/loading 101 echo 1 > /sys/class/firmware/lp5521/loading 103 echo 0 > /sys/class/firmware/lp5521/loading 110 echo 1 > /sys/class/firmware/lp5523/loading 112 echo 0 > /sys/class/firmware/lp5523/loading 116 As soon as 'loading' is set to 0, registered callback is called. 124 echo 1 > /sys/class/firmware/lp8501/loading [all …]
D	leds-lp5562.txt	`35 Before loading the LP5562 program data, engine_mux should be written between 36 the engine selection and loading the firmware. 38 RGB is used for loading RGB program data, W is used for W program data. 43 echo 1 > /sys/class/firmware/lp5562/loading 45 echo 0 > /sys/class/firmware/lp5562/loading 51 echo 1 > /sys/class/firmware/lp5562/loading 53 echo 0 > /sys/class/firmware/lp5562/loading`
/Linux-v4.19/Documentation/dev-tools/
D	gdb-kernel-debugging.rst	55 Note: Some distros may restrict auto-loading of gdb scripts to known safe 56 directories. In case gdb reports to refuse loading vmlinux-gdb.py, add:: 73 loading vmlinux 75 loading @0xffffffffa0020000: /home/user/linux/build/net/netfilter/xt_tcpudp.ko 76 loading @0xffffffffa0016000: /home/user/linux/build/net/netfilter/xt_pkttype.ko 77 loading @0xffffffffa0002000: /home/user/linux/build/net/netfilter/xt_limit.ko 78 loading @0xffffffffa00ca000: /home/user/linux/build/net/packet/af_packet.ko 79 loading @0xffffffffa003c000: /home/user/linux/build/fs/fuse/fuse.ko 81 loading @0xffffffffa0000000: /home/user/linux/build/drivers/ata/ata_generic.ko 97 loading @0xffffffffa0034000: /home/user/linux/build/lib/libcrc32c.ko [all …]
/Linux-v4.19/Documentation/firmware_class/
D	hotplug-script	`11 echo 1 > /sys/$DEVPATH/loading 13 echo 0 > /sys/$DEVPATH/loading 15 echo -1 > /sys/$DEVPATH/loading`
/Linux-v4.19/Documentation/driver-api/firmware/
D	fallback-mechanisms.rst	57 interface as a loading facility: 62 First lets document the shared sysfs loading facility. 64 Firmware sysfs loading facility 76 given that originally the only firmware loading mechanism available was the 82 To load firmware using the sysfs interface we expose a loading indicator, 85 * /sys/$DEVPATH/loading 88 To upload firmware you will echo 1 onto the loading file to indicate 89 you are loading firmware. You then write the firmware into the data file, 91 the loading file. 94 direct firmware loading fails and if the fallback mechanism is enabled for your [all …]
D	lookup-order.rst	`17 is issued or the custom firmware loading is relied upon for firmware 18 loading up to the timeout value.`
/Linux-v4.19/sound/pci/hda/
D	Kconfig	79 bool "Support initialization patch loading for HD-audio" 95 comment "Set to Y if you want auto-loading the codec driver" 105 comment "Set to Y if you want auto-loading the codec driver" 115 comment "Set to Y if you want auto-loading the codec driver" 125 comment "Set to Y if you want auto-loading the codec driver" 139 comment "Set to Y if you want auto-loading the codec driver" 149 comment "Set to Y if you want auto-loading the codec driver" 159 comment "Set to Y if you want auto-loading the codec driver" 169 comment "Set to Y if you want auto-loading the codec driver" 178 comment "Set to Y if you want auto-loading the codec driver" [all …]
/Linux-v4.19/Documentation/x86/
D	microcode.txt	`6 The kernel has a x86 microcode loading facility which is supposed to 7 provide microcode loading methods in the OS. Potential use cases are 11 The loader supports three loading methods: 86 2. Late loading 103 The loading mechanism looks for microcode blobs in 110 The loader supports also loading of a builtin microcode supplied through`
D	usb-legacy-support.txt	`30 Problem 1) can be solved by loading the USB drivers prior to loading the`
/Linux-v4.19/drivers/base/firmware_loader/
D	Kconfig	4 tristate "Firmware loading facility" if EXPERT 7 This enables the firmware loading facility in the kernel. The kernel 70 This option enables a sysfs loading facility to enable firmware 71 loading to the kernel through userspace as a fallback mechanism 82 the requested firmware a sysfs fallback loading facility is made 90 This used to be the default firmware loading facility, and udev used 92 loading facility functionality in udev has been removed, as such it 99 Since this was the default firmware loading facility at one point, 126 for provisioning. Since udev's firmware loading facility has been 135 certain you need to support some really custom firmware loading
D	fallback.c	212 int loading = 0; in firmware_loading_show() local 216 loading = fw_sysfs_loading(fw_sysfs->fw_priv); in firmware_loading_show() 219 return sprintf(buf, "%d\n", loading); in firmware_loading_show() 256 int loading = simple_strtol(buf, NULL, 10); in firmware_loading_store() local 264 switch (loading) { in firmware_loading_store() 311 dev_err(dev, "%s: unexpected value (%d)\n", __func__, loading); in firmware_loading_store() 322 static DEVICE_ATTR(loading, 0644, firmware_loading_show, firmware_loading_store);
/Linux-v4.19/Documentation/acpi/
D	ssdt-overlays.txt	13 way to augment firmware ACPI configuration is by dynamically loading 68 This option allows loading of user defined SSDTs from initrd and it is useful 74 in loading multiple tables. Only SSDT and OEM tables are allowed. See 97 is also work underway to implement EFI support for loading user defined SSDTs 98 and using this method will make it easier to convert to the EFI loading 162 This option allows loading of user defined SSDTs from userspace via the configfs 167 New tables can be loading by creating new directories in /config/acpi/table/ and
/Linux-v4.19/security/tomoyo/
D	Kconfig	`49 needed before loading the policy. For example, you can activate 50 immediately after loading the fixed part of policy which will allow 53 loading the variant part of policy. Since you can start using`
/Linux-v4.19/Documentation/ABI/testing/
D	evm	`48 Until key loading has been signaled EVM can not create 54 creating and loading existing trusted/encrypted keys, 58 core/ima-setup) have support for loading keys at boot`
/Linux-v4.19/Documentation/devicetree/bindings/remoteproc/
D	wkup_m3_rproc.txt	`7 binary to accomplish this. The wkup_m3 remoteproc driver handles the loading of 28 - ti,pm-firmware: Name of firmware file to be used for loading and`
/Linux-v4.19/usr/
D	Kconfig	`61 Support loading of a gzip encoded initial ramdisk or cpio buffer. 70 Support loading of a bzip2 encoded initial ramdisk or cpio buffer 79 Support loading of a LZMA encoded initial ramdisk or cpio buffer 88 Support loading of a XZ encoded initial ramdisk or cpio buffer. 97 Support loading of a LZO encoded initial ramdisk or cpio buffer 106 Support loading of a LZ4 encoded initial ramdisk or cpio buffer`
/Linux-v4.19/Documentation/livepatch/
D	callbacks.txt	25 - A module notifier can't stop a to-be-patched module from loading. 134 Test a combination of loading a kernel module and a livepatch that 215 …[ 46.560845] livepatch: applying patch 'livepatch_callbacks_demo' to loading module 'livepatch_c… 241 Test loading the livepatch after a targeted kernel module, then unload 319 …[ 66.669196] livepatch: applying patch 'livepatch_callbacks_demo' to loading module 'livepatch_c… 348 A simple test of loading a livepatch without one of its patch target 396 code will propagate back to the module-loading subsystem. The result is 449 …[ 90.796976] livepatch: applying patch 'livepatch_callbacks_demo' to loading module 'livepatch_c… 471 Test loading multiple targeted kernel modules. This test-case is 491 Proceed with loading the livepatch and another ordinary target module, [all …]
/Linux-v4.19/Documentation/
D	dell_rbu.txt	`48 /sys/class/firmware/dell_rbu/loading 94 1) echo 1 > /sys/class/firmware/dell_rbu/loading 96 3) echo 0 > /sys/class/firmware/dell_rbu/loading 103 echo -1 > /sys/class/firmware/dell_rbu/loading`
/Linux-v4.19/tools/perf/Documentation/
D	perf-kallsyms.txt	`24 Increase verbosity level, showing details about symbol table loading, etc.`
/Linux-v4.19/Documentation/serial/
D	00-INDEX	`4 - info on Cyclades-Z firmware loading.`
/Linux-v4.19/Documentation/devicetree/bindings/fpga/
D	lattice-machxo2-spi.txt	`3 Lattice MachXO2 FPGAs support a method of loading the bitstream over`
/Linux-v4.19/Documentation/media/dvb-drivers/
D	opera-firmware.rst	`30 (if you have enabled firmware loading`
/Linux-v4.19/Documentation/admin-guide/
D	init.rst	`33 In case you tried loading a non-binary file here (shell script?), 42 (after all loading the init binary is a CRITICAL and hard transition step`

12 3 4 5 6 7 8 9