loading (reference) in projects: Linux-v5.15

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

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

12 3 4 5 6 7 8 9 10

/Linux-v5.15/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 …]`
/Linux-v5.15/Documentation/leds/
D	leds-lp55xx.rst	93 echo 1 > /sys/class/firmware/lp5521/loading 95 echo 0 > /sys/class/firmware/lp5521/loading 103 echo 1 > /sys/class/firmware/lp55231/loading 105 echo 0 > /sys/class/firmware/lp55231/loading 115 echo 1 > /sys/class/firmware/lp5521/loading 117 echo 0 > /sys/class/firmware/lp5521/loading 126 echo 1 > /sys/class/firmware/lp5523/loading 128 echo 0 > /sys/class/firmware/lp5523/loading 132 As soon as 'loading' is set to 0, registered callback is called. 143 echo 1 > /sys/class/firmware/lp8501/loading [all …]
D	leds-lp5562.rst	`44 Before loading the LP5562 program data, engine_mux should be written between 45 the engine selection and loading the firmware. 47 RGB is used for loading RGB program data, W is used for W program data. 53 echo 1 > /sys/class/firmware/lp5562/loading 55 echo 0 > /sys/class/firmware/lp5562/loading 62 echo 1 > /sys/class/firmware/lp5562/loading 64 echo 0 > /sys/class/firmware/lp5562/loading`
/Linux-v5.15/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-v5.15/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-v5.15/sound/pci/hda/
D	Kconfig	85 bool "Support initialization patch loading for HD-audio" 102 comment "Set to Y if you want auto-loading the codec driver" 112 comment "Set to Y if you want auto-loading the codec driver" 123 comment "Set to Y if you want auto-loading the codec driver" 133 comment "Set to Y if you want auto-loading the codec driver" 147 comment "Set to Y if you want auto-loading the codec driver" 157 comment "Set to Y if you want auto-loading the codec driver" 167 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" 188 comment "Set to Y if you want auto-loading the codec driver" [all …]
/Linux-v5.15/drivers/base/firmware_loader/
D	Kconfig	5 tristate "Firmware loading facility" if EXPERT 8 This enables the firmware loading facility in the kernel. The kernel 75 This option enables a sysfs loading facility to enable firmware 76 loading to the kernel through userspace as a fallback mechanism 87 the requested firmware a sysfs fallback loading facility is made 95 This used to be the default firmware loading facility, and udev used 97 loading facility functionality in udev has been removed, as such it 104 Since this was the default firmware loading facility at one point, 131 for provisioning. Since udev's firmware loading facility has been 140 certain you need to support some really custom firmware loading [all …]
D	fallback.c	214 int loading = 0; in firmware_loading_show() local 218 loading = fw_sysfs_loading(fw_sysfs->fw_priv); in firmware_loading_show() 221 return sysfs_emit(buf, "%d\n", loading); in firmware_loading_show() 244 int loading = simple_strtol(buf, NULL, 10); in firmware_loading_store() local 251 switch (loading) { in firmware_loading_store() 292 dev_err(dev, "%s: unexpected value (%d)\n", __func__, loading); in firmware_loading_store() 303 static DEVICE_ATTR(loading, 0644, firmware_loading_show, firmware_loading_store);
/Linux-v5.15/Documentation/driver-api/firmware/
D	fallback-mechanisms.rst	58 interface as a loading facility: 63 First lets document the shared sysfs loading facility. 65 Firmware sysfs loading facility 77 given that originally the only firmware loading mechanism available was the 83 To load firmware using the sysfs interface we expose a loading indicator, 86 * /sys/$DEVPATH/loading 89 To upload firmware you will echo 1 onto the loading file to indicate 90 you are loading firmware. You then write the firmware into the data file, 92 the loading file. 95 direct firmware loading fails and if the fallback mechanism is enabled for your [all …]
D	lookup-order.rst	`19 is issued or the custom firmware loading is relied upon for firmware 20 loading up to the timeout value.`
/Linux-v5.15/Documentation/x86/
D	microcode.rst	`10 The kernel has a x86 microcode loading facility which is supposed to 11 provide microcode loading methods in the OS. Potential use cases are 15 The loader supports three loading methods: 92 Late loading 109 The loading mechanism looks for microcode blobs in 116 The loader supports also loading of a builtin microcode supplied through`
D	usb-legacy-support.rst	`35 can be solved by loading the USB drivers prior to loading the`
/Linux-v5.15/Documentation/admin-guide/acpi/
D	ssdt-overlays.rst	18 way to augment firmware ACPI configuration is by dynamically loading 73 This option allows loading of user defined SSDTs from initrd and it is useful 79 in loading multiple tables. Only SSDT and OEM tables are allowed. See 103 is also work underway to implement EFI support for loading user defined SSDTs 104 and using this method will make it easier to convert to the EFI loading 171 This option allows loading of user defined SSDTs from user space via the configfs 176 New tables can be loading by creating new directories in /sys/kernel/config/acpi/table
/Linux-v5.15/Documentation/core-api/
D	symbol-namespaces.rst	29 its configuration, reject loading the module or warn about a missing import. 116 At module loading time (e.g. ``insmod``), the kernel will check each symbol 119 the kernel is to reject loading modules that don't specify sufficient imports. 120 An error will be logged and loading will be failed with EINVAL. In order to 121 allow loading of modules that don't satisfy this precondition, a configuration 123 enable loading regardless, but will emit a warning.
/Linux-v5.15/usr/
D	Kconfig	`60 Support loading of a gzip encoded initial ramdisk or cpio buffer. 68 Support loading of a bzip2 encoded initial ramdisk or cpio buffer 76 Support loading of a LZMA encoded initial ramdisk or cpio buffer 84 Support loading of a XZ encoded initial ramdisk or cpio buffer. 92 Support loading of a LZO encoded initial ramdisk or cpio buffer 100 Support loading of a LZ4 encoded initial ramdisk or cpio buffer 108 Support loading of a ZSTD encoded initial ramdisk or cpio buffer.`
/Linux-v5.15/tools/testing/selftests/livepatch/
D	README	`42 general module loading and livepatch loading helpers (waiting for patch`
/Linux-v5.15/Documentation/networking/device_drivers/ethernet/netronome/
D	nfp.rst	`41 Recent versions of management firmware supports loading application 42 firmware from flash when the host driver gets probed. The firmware loading 85 is system loading wrong driver or firmware on boot, but when driver is 99 nfp: netronome/nic_AMDA0081-0001_1x40.nffw: found, loading... 109 Firmware loading policy 112 Firmware loading policy is controlled via three HWinfo parameters`
/Linux-v5.15/security/tomoyo/
D	Kconfig	`50 needed before loading the policy. For example, you can activate 51 immediately after loading the fixed part of policy which will allow 54 loading the variant part of policy. Since you can start using`
/Linux-v5.15/Documentation/ABI/testing/
D	evm	`83 Until key loading has been signaled EVM can not create 89 creating and loading existing trusted/encrypted keys, 93 core/ima-setup) have support for loading keys at boot`
/Linux-v5.15/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-v5.15/Documentation/admin-guide/
D	dell_rbu.rst	`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-v5.15/Documentation/userspace-api/ebpf/
D	index.rst	`8 source code or loading kernel modules. eBPF programs can be attached to various`
/Linux-v5.15/tools/perf/Documentation/
D	perf-kallsyms.txt	`24 Increase verbosity level, showing details about symbol table loading, etc.`
/Linux-v5.15/Documentation/devicetree/bindings/fpga/
D	lattice-machxo2-spi.txt	`3 Lattice MachXO2 FPGAs support a method of loading the bitstream over`
/Linux-v5.15/security/integrity/
D	Kconfig	`76 bool "Enable loading of platform and blacklisted keys for POWER" 81 Enable loading of keys to the .platform keyring and blacklisted`

12 3 4 5 6 7 8 9 10