loading (reference) in projects: linux-6.12.1

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

/linux-6.12.1/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_upload.sh	`46 echo 1 > "$DIR"/"$name"/loading 48 echo 0 > "$DIR"/"$name"/loading 70 echo 1 > "$DIR"/"$name"/loading 72 echo 0 > "$DIR"/"$name"/loading`
/linux-6.12.1/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-6.12.1/Documentation/translations/zh_CN/dev-tools/
D	gdb-kernel-debugging.rst	71 loading vmlinux 73 loading @0xffffffffa0020000: /home/user/linux/build/net/netfilter/xt_tcpudp.ko 74 loading @0xffffffffa0016000: /home/user/linux/build/net/netfilter/xt_pkttype.ko 75 loading @0xffffffffa0002000: /home/user/linux/build/net/netfilter/xt_limit.ko 76 loading @0xffffffffa00ca000: /home/user/linux/build/net/packet/af_packet.ko 77 loading @0xffffffffa003c000: /home/user/linux/build/fs/fuse/fuse.ko 79 loading @0xffffffffa0000000: /home/user/linux/build/drivers/ata/ata_generic.ko 94 loading @0xffffffffa0034000: /home/user/linux/build/lib/libcrc32c.ko 95 loading @0xffffffffa0050000: /home/user/linux/build/lib/lzo/lzo_compress.ko 96 loading @0xffffffffa006e000: /home/user/linux/build/lib/zlib_deflate/zlib_deflate.ko [all …]
/linux-6.12.1/Documentation/translations/zh_TW/dev-tools/
D	gdb-kernel-debugging.rst	67 loading vmlinux 69 loading @0xffffffffa0020000: /home/user/linux/build/net/netfilter/xt_tcpudp.ko 70 loading @0xffffffffa0016000: /home/user/linux/build/net/netfilter/xt_pkttype.ko 71 loading @0xffffffffa0002000: /home/user/linux/build/net/netfilter/xt_limit.ko 72 loading @0xffffffffa00ca000: /home/user/linux/build/net/packet/af_packet.ko 73 loading @0xffffffffa003c000: /home/user/linux/build/fs/fuse/fuse.ko 75 loading @0xffffffffa0000000: /home/user/linux/build/drivers/ata/ata_generic.ko 90 loading @0xffffffffa0034000: /home/user/linux/build/lib/libcrc32c.ko 91 loading @0xffffffffa0050000: /home/user/linux/build/lib/lzo/lzo_compress.ko 92 loading @0xffffffffa006e000: /home/user/linux/build/lib/zlib_deflate/zlib_deflate.ko [all …]
/linux-6.12.1/Documentation/dev-tools/
D	gdb-kernel-debugging.rst	59 Note: Some distros may restrict auto-loading of gdb scripts to known safe 60 directories. In case gdb reports to refuse loading vmlinux-gdb.py, add:: 77 loading vmlinux 79 loading @0xffffffffa0020000: /home/user/linux/build/net/netfilter/xt_tcpudp.ko 80 loading @0xffffffffa0016000: /home/user/linux/build/net/netfilter/xt_pkttype.ko 81 loading @0xffffffffa0002000: /home/user/linux/build/net/netfilter/xt_limit.ko 82 loading @0xffffffffa00ca000: /home/user/linux/build/net/packet/af_packet.ko 83 loading @0xffffffffa003c000: /home/user/linux/build/fs/fuse/fuse.ko 85 loading @0xffffffffa0000000: /home/user/linux/build/drivers/ata/ata_generic.ko 101 loading @0xffffffffa0034000: /home/user/linux/build/lib/libcrc32c.ko [all …]
/linux-6.12.1/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-6.12.1/Documentation/arch/x86/
D	microcode.rst	11 The kernel has a x86 microcode loading facility which is supposed to 12 provide microcode loading methods in the OS. Potential use cases are 16 The loader supports three loading methods: 93 Late loading 103 The loading mechanism looks for microcode blobs in 107 Since kernel 5.19, late loading is not enabled by default. 111 Why is late loading dangerous? 188 Is the microcode suitable for late loading? 191 Late loading is done when the system is fully operational and running 192 real workloads. Late loading behavior depends on what the base patch on [all …]
/linux-6.12.1/drivers/base/firmware_loader/
D	sysfs.c	130 int loading = 0; in firmware_loading_show() local 134 loading = fw_state_is_loading(fw_sysfs->fw_priv); in firmware_loading_show() 137 return sysfs_emit(buf, "%d\n", loading); in firmware_loading_show() 160 int loading = simple_strtol(buf, NULL, 10); in firmware_loading_store() local 167 switch (loading) { in firmware_loading_store() 215 dev_err(dev, "%s: unexpected value (%d)\n", __func__, loading); in firmware_loading_store() 229 DEVICE_ATTR(loading, 0644, firmware_loading_show, firmware_loading_store);
D	Kconfig	5 tristate "Firmware loading facility" if EXPERT 10 This enables the firmware loading facility in the kernel. The kernel 101 This option enables a sysfs loading facility to enable firmware 102 loading to the kernel through userspace as a fallback mechanism 113 the requested firmware a sysfs fallback loading facility is made 121 This used to be the default firmware loading facility, and udev used 123 loading facility functionality in udev has been removed, as such it 130 Since this was the default firmware loading facility at one point, 157 for provisioning. Since udev's firmware loading facility has been 166 certain you need to support some really custom firmware loading [all …]
/linux-6.12.1/drivers/md/dm-vdo/
D	admin-state.c	`29 .loading = true, 35 .loading = true, 46 .loading = true, 52 .loading = true, 59 .loading = true, 104 .loading = true, 375 return check_code(operation->loading, operation, "load operation", waiter); in vdo_assert_load_operation()`
D	admin-state.h	`19 bool loading; member 114 return vdo_get_admin_state_code(state)->loading; in vdo_is_state_loading()`
/linux-6.12.1/sound/pci/hda/
D	Kconfig	85 bool "Support initialization patch loading for HD-audio" 136 comment "Set to Y if you want auto-loading the side codec driver" 153 comment "Set to Y if you want auto-loading the side codec driver" 206 comment "Set to Y if you want auto-loading the side codec driver" 218 comment "Set to Y if you want auto-loading the codec driver" 228 comment "Set to Y if you want auto-loading the codec driver" 239 comment "Set to Y if you want auto-loading the codec driver" 249 comment "Set to Y if you want auto-loading the codec driver" 263 comment "Set to Y if you want auto-loading the codec driver" 273 comment "Set to Y if you want auto-loading the codec driver" [all …]
/linux-6.12.1/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	fw_upload.rst	`11 upload uses the same loading and data sysfs files described in the 21 firmware upload by echoing a 1 to the loading sysfs file for the target 23 file. After writing the firmware data, the user echos 0 to the loading 24 sysfs file to signal completion. Echoing 0 to loading also triggers the 116 In addition to the loading and data sysfs files, there are additional`
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-6.12.1/Documentation/ABI/testing/
D	sysfs-class-firmware	`7 after you echo 1 to the loading sysfs file. When the firmware 8 image write is complete, echo 0 to the loading sysfs file. This 37 What: /sys/class/firmware/.../loading 41 Description: The loading sysfs file is used for both firmware-fallback and 42 for firmware uploads. Echo 1 onto the loading file to indicate`
/linux-6.12.1/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-6.12.1/kernel/module/
D	Kconfig	52 with loading modules when it shouldn't or if you want to help 64 bool "Debug duplicate modules with auto-loading" 80 module requests to help identify if module auto-loading may be the 94 completes. Subsequent auto-loading requests for the same module do 102 abuse was due to module auto-loading. These issues are currently only 105 module auto-loading is not the culprit. There may very well still be 106 many duplicate module auto-loading requests which could be optimized 117 auto-loading requests using WARN_ON() instead of pr_warn(). You 125 bool "Forced module loading" 128 Allow loading of modules without version information (ie. modprobe [all …]
/linux-6.12.1/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-6.12.1/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-6.12.1/security/tomoyo/
D	Kconfig	`48 needed before loading the policy. For example, you can activate 49 immediately after loading the fixed part of policy which will allow 52 loading the variant part of policy. Since you can start using`
/linux-6.12.1/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-6.12.1/tools/testing/selftests/livepatch/
D	README	`55 general module loading and livepatch loading helpers (waiting for patch`

12 3 4 5 6 7 8 9 10 11

Project(s)

Full Search
Definition
Symbol
File Path
History
Type