Searched refs:firmware_class (Results 1 – 11 of 11) sorted by relevance
5 obj-$(CONFIG_FW_LOADER) += firmware_class.o6 firmware_class-objs := main.o7 firmware_class-$(CONFIG_FW_LOADER_USER_HELPER) += fallback.o8 firmware_class-$(CONFIG_EFI_EMBEDDED_FIRMWARE) += fallback_platform.o9 firmware_class-$(CONFIG_FW_LOADER_SYSFS) += sysfs.o10 firmware_class-$(CONFIG_FW_UPLOAD) += sysfs_upload.o
65 ATTRIBUTE_GROUPS(firmware_class);102 static struct class firmware_class = { variable113 int ret = class_register(&firmware_class); in register_sysfs_loader()123 class_unregister(&firmware_class); in unregister_sysfs_loader()415 f_dev->class = &firmware_class; in fw_create_instance()
14 o firmware_class path module parameter or kernel boot param25 as a module, in which case the firmware_class module will be built.98 path specified in the firmware_class path module parameter, or the99 firmware_class path kernel boot parameter if the firmware_class is141 looks for and cannot possibly be specified using the firmware_class142 path module parameter or kernel firmware_class path boot parameter143 if firmware_class is built-in.
14 The module parameter ''path'' can be passed to the firmware_class module18 * 'firmware_class.path=$CUSTOMIZED_PATH'23 * /sys/module/firmware_class/parameters/path29 echo -n /path/to/script > /sys/module/firmware_class/parameters/path
75 the new device's class (firmware_class) and group (fw_dev_attr_groups).76 This is actually where the original firmware_class module name came from,79 firmware_class. Because the attributes exposed are part of the module name, the80 module name firmware_class cannot be renamed in the future, to ensure backward105 return an error. When loading firmware the firmware_class grows a buffer
140 echo -n "$FWPATH" >/sys/module/firmware_class/parameters/path197 printf '\000' >/sys/module/firmware_class/parameters/path199 echo -n "$OLD_FWPATH" >/sys/module/firmware_class/parameters/path
311 Documentation/firmware_class/.
8144 F: Documentation/firmware_class/
[all...]