Home
last modified time | relevance | path

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

1234567891011

/linux/tools/testing/selftests/firmware/
A Dfw_fallback.sh31 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 …]
A Dfw_filesystem.sh337 while [ ! -e "$DIR"/"$name"/loading ]; do
346 echo -1 >"$DIR"/"$name"/loading
/linux/Documentation/leds/
A Dleds-lp55xx.rst93 echo 1 > /sys/class/firmware/lp5521/loading
95 echo 0 > /sys/class/firmware/lp5521/loading
103 echo 1 > /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
143 echo 1 > /sys/class/firmware/lp8501/loading
145 echo 0 > /sys/class/firmware/lp8501/loading
152 echo 1 > /sys/class/firmware/lp8501/loading
[all …]
A Dleds-lp5562.rst44 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/Documentation/dev-tools/
A Dgdb-kernel-debugging.rst55 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
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
98 loading @0xffffffffa0050000: /home/user/linux/build/lib/lzo/lzo_compress.ko
[all …]
/linux/sound/pci/hda/
A DKconfig85 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/Documentation/firmware_class/
A Dhotplug-script11 echo 1 > /sys/$DEVPATH/loading
13 echo 0 > /sys/$DEVPATH/loading
15 echo -1 > /sys/$DEVPATH/loading
/linux/drivers/base/firmware_loader/
A DKconfig5 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
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
163 This option enables the support for loading compressed firmware
[all …]
A Dfallback.c214 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/Documentation/driver-api/firmware/
A Dfallback-mechanisms.rst58 interface as a loading facility:
63 First lets document the shared sysfs loading facility.
65 Firmware sysfs loading facility
86 * /sys/$DEVPATH/loading
89 To upload firmware you will echo 1 onto the loading file to indicate
92 the loading file.
102 echo 1 > /sys/$DEVPATH/loading
105 return an error. When loading firmware the firmware_class grows a buffer
141 commit be2ea723b1d0 ("udev: remove userspace firmware loading support")
160 echo 1 > /sys/$DEVPATH/loading
[all …]
A Dlookup-order.rst19 is issued or the custom firmware loading is relied upon for firmware
20 loading up to the timeout value.
/linux/Documentation/x86/
A Dmicrocode.rst10 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
A Dusb-legacy-support.rst35 can be solved by loading the USB drivers prior to loading the
/linux/Documentation/admin-guide/acpi/
A Dssdt-overlays.rst18 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/Documentation/core-api/
A Dsymbol-namespaces.rst29 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/usr/
A DKconfig60 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/Documentation/networking/device_drivers/ethernet/netronome/
A Dnfp.rst41 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/tools/testing/selftests/livepatch/
A DREADME42 general module loading and livepatch loading helpers (waiting for patch
/linux/security/tomoyo/
A DKconfig50 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/Documentation/ABI/testing/
A Devm84 Until key loading has been signaled EVM can not create
90 creating and loading existing trusted/encrypted keys,
94 core/ima-setup) have support for loading keys at boot
/linux/Documentation/devicetree/bindings/remoteproc/
A Dwkup_m3_rproc.txt7 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/Documentation/admin-guide/
A Ddell_rbu.rst48 /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
A Dinit.rst30 hardware. In case you tried loading a non-binary file here (shell script?),
39 (after all loading the init binary is a CRITICAL and hard transition step
/linux/security/integrity/
A DKconfig76 bool "Enable loading of platform and blacklisted keys for POWER"
81 Enable loading of keys to the .platform keyring and blacklisted
/linux/Documentation/devicetree/bindings/net/dsa/
A Dlantiq-gswip.txt28 Required properties for GPHY firmware loading:
32 for the loading of the firmware into the embedded

Completed in 33 milliseconds

1234567891011