| /kernel/linux/linux-4.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
|
| /kernel/linux/linux-5.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
|
| /kernel/linux/linux-4.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 …]
|
| /kernel/linux/linux-5.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 …]
|
| /kernel/linux/linux-4.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 …]
|
| /kernel/linux/linux-4.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 …]
|
| /kernel/linux/linux-4.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 …]
|
| /kernel/linux/linux-5.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 …]
|
| /kernel/linux/linux-5.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 …]
|
| /kernel/linux/linux-5.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/aborted and disappearance of 'loading' in __fw_load_abort()
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()
225 * firmware_loading_store() - set value in the 'loading' control file
228 * @buf: buffer to scan for loading control value
244 int loading = simple_strtol(buf, NULL, 10); in firmware_loading_store() local
[all …]
|
| /kernel/linux/linux-4.19/drivers/base/firmware_loader/ |
| D | fallback.c | 35 * use small loading timeout for caching devices' firmware because all these
37 * ready for completing firmware loading now. The maximum size of firmware in
88 * There is a small window in which user can write to 'loading' in __fw_load_abort()
89 * between loading done and disappearance of 'loading' in __fw_load_abort()
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()
237 * firmware_loading_store() - set value in the 'loading' control file
240 * @buf: buffer to scan for loading control value
256 int loading = simple_strtol(buf, NULL, 10); in firmware_loading_store() local
[all …]
|
| 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
|
| /kernel/linux/linux-4.19/Documentation/acpi/ |
| D | ssdt-overlays.txt | 13 way to augment firmware ACPI configuration is by dynamically loading
66 == Loading ACPI SSDTs from initrd ==
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
93 == Loading ACPI SSDTs from EFI variables ==
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
160 == Loading ACPI SSDTs from configfs ==
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
|
| /kernel/linux/linux-5.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 …]
|
| /kernel/linux/linux-5.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
|
| /kernel/linux/linux-4.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:
16 The kernel can update microcode very early during boot. Loading
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
|
| /kernel/linux/linux-5.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
|
| /kernel/linux/linux-5.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.
|
| /kernel/linux/linux-5.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.
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | evm | 74 Loading an HMAC key is the only way to disable metadata
77 Until key loading has been signaled EVM can not create
79 INTEGRITY_UNKNOWN. Loading keys and signaling EVM
83 creating and loading existing trusted/encrypted keys,
87 core/ima-setup) have support for loading keys at boot
|
| /kernel/linux/linux-5.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
|
| /kernel/linux/linux-4.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
|