| /Linux-v5.10/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.10/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 | 67 echo "$0: filesystem loading works"
72 echo "$0: firmware loading: async trigger not present, ignoring test" >&2
85 echo "$0: async filesystem loading works"
89 # Try platform (EFI embedded fw) loading too
91 echo "$0: firmware loading: platform trigger not present, ignoring test" >&2
109 echo "$0: platform loading works"
337 while [ ! -e "$DIR"/"$name"/loading ]; do
342 echo "$DIR/$name/loading" >&2
346 echo -1 >"$DIR"/"$name"/loading
|
| /Linux-v5.10/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.10/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"
168 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"
187 comment "Set to Y if you want auto-loading the codec driver"
[all …]
|
| /Linux-v5.10/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 | 38 * use small loading timeout for caching devices' firmware because all these
40 * ready for completing firmware loading now. The maximum size of firmware in
91 * There is a small window in which user can write to 'loading' in __fw_load_abort()
92 * between loading done and disappearance of 'loading' in __fw_load_abort()
215 int loading = 0; in firmware_loading_show() local
219 loading = fw_sysfs_loading(fw_sysfs->fw_priv); in firmware_loading_show()
222 return sysfs_emit(buf, "%d\n", loading); in firmware_loading_show()
226 * firmware_loading_store() - set value in the 'loading' control file
229 * @buf: buffer to scan for loading control value
245 int loading = simple_strtol(buf, NULL, 10); in firmware_loading_store() local
[all …]
|
| /Linux-v5.10/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 …]
|
| /Linux-v5.10/Documentation/admin-guide/acpi/ |
| D | ssdt-overlays.rst | 18 way to augment firmware ACPI configuration is by dynamically loading
71 Loading ACPI SSDTs from initrd
74 This option allows loading of user defined SSDTs from initrd and it is useful
80 in loading multiple tables. Only SSDT and OEM tables are allowed. See
99 Loading ACPI SSDTs from EFI variables
104 is also work underway to implement EFI support for loading user defined SSDTs
105 and using this method will make it easier to convert to the EFI loading
167 Loading ACPI SSDTs from configfs
170 This option allows loading of user defined SSDTs from userspace via the configfs
175 New tables can be loading by creating new directories in /config/acpi/table/ and
|
| /Linux-v5.10/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:
20 The kernel can update microcode very early during boot. Loading
92 Late loading
109 The loading mechanism looks for microcode blobs in
116 The loader supports also loading of a builtin microcode supplied through
|
| /Linux-v5.10/Documentation/core-api/ |
| D | symbol-namespaces.rst | 16 === 4 Loading Modules that use namespaced Symbols
29 its configuration, reject loading the module or warn about a missing import.
113 4. Loading Modules that use namespaced Symbols
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.10/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
109 Support loading of a ZSTD encoded initial ramdisk or cpio buffer.
|
| /Linux-v5.10/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.10/kernel/ |
| D | kexec.c | 128 * Loading another kernel to switch to if this one in do_kexec_load()
213 * kexec can be used to circumvent module loading restrictions, so in kexec_load_check()
214 * prevent loading in that case in kexec_load_check()
251 * region when loading crash kernels we need a mutex here to in SYSCALL_DEFINE4()
253 * simultaneously, and to prevent a crash kernel from loading in SYSCALL_DEFINE4()
305 * region when loading crash kernels we need a mutex here to in COMPAT_SYSCALL_DEFINE4()
307 * simultaneously, and to prevent a crash kernel from loading in COMPAT_SYSCALL_DEFINE4()
|
| /Linux-v5.10/Documentation/ABI/testing/ |
| D | evm | 55 Until key loading has been signaled EVM can not create
57 INTEGRITY_UNKNOWN. Loading keys and signaling EVM
61 creating and loading existing trusted/encrypted keys,
65 core/ima-setup) have support for loading keys at boot
|
| /Linux-v5.10/tools/testing/selftests/livepatch/ |
| D | test-callbacks.sh | 15 # Test a combination of loading a kernel module and a livepatch that
93 livepatch: applying patch '$MOD_LIVEPATCH' to loading module '$MOD_TARGET'
111 # Test loading the livepatch after a targeted kernel module, then unload
189 livepatch: applying patch '$MOD_LIVEPATCH' to loading module '$MOD_TARGET'
208 # A simple test of loading a livepatch without one of its patch target
247 # status code will propagate back to the module-loading subsystem.
308 livepatch: applying patch '$MOD_LIVEPATCH' to loading module '$MOD_TARGET'
323 # Test loading multiple targeted kernel modules. This test-case is
329 # - Proceed with loading the livepatch and another ordinary target
358 livepatch: applying patch '$MOD_LIVEPATCH' to loading module '$MOD_TARGET'
[all …]
|
| /Linux-v5.10/fs/xfs/libxfs/ |
| D | xfs_btree_staging.c | 26 * bulk loading code uses the staging btree cursor to abstract the details of
32 * construction by the bulk loading code. Staging btree cursors point to fake
36 * the _stage_cursor function for a specific btree type. When bulk loading is
57 * Bulk loading uses a separate callback to obtain new blocks from a
58 * preallocated list, which prevents ENOSPC failures during loading.
99 * Bulk Loading for AG Btrees
182 * Bulk Loading for Inode-Rooted Btrees
266 * Bulk Loading of Staged Btrees
278 * "Bulk Loading for AG Btrees" and "Bulk Loading for Inode-Rooted Btrees" for
290 * save them for later use by ->claim_block(). Bulk loading requires all
[all …]
|
| /Linux-v5.10/drivers/usb/misc/ |
| D | isight_firmware.c | 3 * Driver for loading USB isight firmware
9 * need firmware to be loaded beforehand. After firmware loading, the device
16 * The isight firmware loading was reverse engineered by Johannes Berg
105 printk(KERN_ERR "isight firmware loading completion failed\n"); in isight_firmware_load()
|
| /Linux-v5.10/drivers/net/wireless/mediatek/mt76/mt76x0/ |
| D | pci_mcu.c | 62 "Could not get hardware semaphore for loading fw\n"); in mt76x0e_load_firmware()
74 dev_dbg(dev->mt76.dev, "loading FW - ILM %u\n", ilm_len); in mt76x0e_load_firmware()
80 dev_dbg(dev->mt76.dev, "loading FW - IVB %u\n", in mt76x0e_load_firmware()
88 dev_dbg(dev->mt76.dev, "loading FW - DLM %u\n", dlm_len); in mt76x0e_load_firmware()
|
| /Linux-v5.10/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.10/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.10/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.10/scripts/gdb/linux/ |
| D | symbols.py | 36 # Disable pagination while reporting symbol (re-)loading.
126 gdb.write("loading @{addr}: {filename}\n".format(
139 gdb.write("loading vmlinux\n")
183 gdb.write("Note: symbol update on module loading not supported "
|
| /Linux-v5.10/drivers/nfc/nfcmrvl/ |
| D | fw_dnld.c | 123 nfc_info(priv->dev, "FW loading over (%d)]\n", error); in fw_dnld_over()
137 nfc_err(priv->dev, "FW loading timeout"); in fw_dnld_timeout()
317 /* FW Loading is done */ in process_state_fw_dnld()
393 nfc_info(priv->dev, "FW loading: helper loaded"); in process_state_boot()
395 nfc_info(priv->dev, "FW loading: firmware loaded"); in process_state_boot()
447 nfc_err(priv->dev, "FW loading error"); in fw_dnld_rx_work()
533 nfc_info(priv->dev, "loading helper"); in nfcmrvl_fw_dnld_start()
536 nfc_info(priv->dev, "loading firmware"); in nfcmrvl_fw_dnld_start()
|
