| /kernel/linux/linux-6.6/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-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-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-6.6/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-6.6/sound/pci/hda/ |
| D | Kconfig | 85 bool "Support initialization patch loading for HD-audio"
116 comment "Set to Y if you want auto-loading the side codec driver"
132 comment "Set to Y if you want auto-loading the side codec driver"
181 comment "Set to Y if you want auto-loading the side codec driver"
193 comment "Set to Y if you want auto-loading the codec driver"
203 comment "Set to Y if you want auto-loading the codec driver"
214 comment "Set to Y if you want auto-loading the codec driver"
224 comment "Set to Y if you want auto-loading the codec driver"
238 comment "Set to Y if you want auto-loading the codec driver"
248 comment "Set to Y if you want auto-loading the codec driver"
[all …]
|
| /kernel/linux/linux-6.6/Documentation/translations/zh_CN/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 …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-5.10/sound/pci/hda/ |
| D | Kconfig | 96 bool "Support initialization patch loading for HD-audio"
113 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"
134 comment "Set to Y if you want auto-loading the codec driver"
144 comment "Set to Y if you want auto-loading the codec driver"
158 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"
179 comment "Set to Y if you want auto-loading the codec driver"
189 comment "Set to Y if you want auto-loading the codec driver"
198 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-6.6/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:
21 The kernel can update microcode very early during boot. Loading
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
[all …]
|
| /kernel/linux/linux-6.6/drivers/base/firmware_loader/ |
| D | Kconfig | 5 tristate "Firmware loading facility" if EXPERT
10 This enables the firmware loading facility in the kernel. The kernel
94 This option enables a sysfs loading facility to enable firmware
95 loading to the kernel through userspace as a fallback mechanism
106 the requested firmware a sysfs fallback loading facility is made
114 This used to be the default firmware loading facility, and udev used
116 loading facility functionality in udev has been removed, as such it
123 Since this was the default firmware loading facility at one point,
150 for provisioning. Since udev's firmware loading facility has been
159 certain you need to support some really custom firmware loading
[all …]
|
| D | sysfs.c | 18 * There is a small window in which user can write to 'loading' in __fw_load_abort()
19 * between loading done/aborted and disappearance of 'loading' in __fw_load_abort()
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()
141 * firmware_loading_store() - set value in the 'loading' control file
144 * @buf: buffer to scan for loading control value
160 int loading = simple_strtol(buf, NULL, 10); in firmware_loading_store() local
167 switch (loading) { in firmware_loading_store()
178 * Several loading requests may be pending on in firmware_loading_store()
[all …]
|
| D | fallback.c | 19 * use small loading timeout for caching devices' firmware because all these
21 * ready for completing firmware loading now. The maximum size of firmware in
68 * In charge of constructing a sysfs fallback interface for firmware loading.
76 /* fall back on userspace loading */ in fw_load_sysfs_fallback()
138 dev_dbg(device, "firmware: %s loading timed out\n", in fw_load_from_user_helper()
203 * @opt_flags: options to control firmware loading behaviour, as defined by
208 * a fallback mechanism through userspace by exposing a sysfs loading
209 * interface. Userspace is in charge of loading the firmware through the sysfs
210 * loading interface. This sysfs fallback mechanism may be disabled completely
|
| /kernel/linux/linux-6.6/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/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-6.6/Documentation/admin-guide/acpi/ |
| D | ssdt-overlays.rst | 18 way to augment firmware ACPI configuration is by dynamically loading
70 Loading ACPI SSDTs from initrd
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
98 Loading ACPI SSDTs from EFI variables
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
168 Loading ACPI SSDTs from configfs
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
|
| /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-6.6/kernel/module/ |
| D | Kconfig | 51 with loading modules when it shouldn't or if you want to help
63 bool "Debug duplicate modules with auto-loading"
79 module requests to help identify if module auto-loading may be the
93 completes. Subsequent auto-loading requests for the same module do
101 abuse was due to module auto-loading. These issues are currently only
104 module auto-loading is not the culprit. There may very well still be
105 many duplicate module auto-loading requests which could be optimized
116 auto-loading requests using WARN_ON() instead of pr_warn(). You
124 bool "Forced module loading"
127 Allow loading of modules without version information (ie. modprobe
[all …]
|
| /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-6.6/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.
|