Home
last modified time | relevance | path

Searched refs:firmware (Results 1 – 200 of 1020) sorted by relevance

123456

/linux-4.4.14/sound/pci/asihpi/
Dhpidspcd.c29 const struct firmware *firmware; member
37 const struct firmware *firmware; in hpi_dsp_code_open() local
46 err = request_firmware(&firmware, fw_name, &dev->dev); in hpi_dsp_code_open()
48 if (err || !firmware) { in hpi_dsp_code_open()
53 if (firmware->size < sizeof(header)) { in hpi_dsp_code_open()
57 memcpy(&header, firmware->data, sizeof(header)); in hpi_dsp_code_open()
61 || (header.size != firmware->size)) { in hpi_dsp_code_open()
64 header.size, firmware->size); in hpi_dsp_code_open()
90 dsp_code->pvt->firmware = firmware; in hpi_dsp_code_open()
97 release_firmware(firmware); in hpi_dsp_code_open()
[all …]
/linux-4.4.14/Documentation/ABI/testing/
Dsysfs-firmware-efi-esrt1 What: /sys/firmware/efi/esrt/
5 (ESRT), a catalog of firmware for which can be updated with
10 What: /sys/firmware/efi/esrt/fw_resource_count
15 What: /sys/firmware/efi/esrt/fw_resource_count_max
20 really only useful to the system firmware itself.
22 What: /sys/firmware/efi/esrt/fw_resource_version
25 Description: The version of the ESRT structure provided by the firmware.
27 What: /sys/firmware/efi/esrt/entries/entry$N/
32 example: /sys/firmware/efi/esrt/entries/entry0/
34 What: /sys/firmware/efi/esrt/entries/entry$N/fw_type
[all …]
Dsysfs-firmware-memmap1 What: /sys/firmware/memmap/
5 On all platforms, the firmware provides a memory map which the
10 However, on most architectures that firmware-provided memory
16 kexec needs the raw firmware-provided memory map to setup the
19 that reason, /sys/firmware/memmap is an interface that provides
22 The structure is as follows: Under /sys/firmware/memmap there
25 /sys/firmware/memmap/0
26 /sys/firmware/memmap/1
27 /sys/firmware/memmap/2
28 /sys/firmware/memmap/3
[all …]
Dsysfs-firmware-gsmi1 What: /sys/firmware/gsmi
5 Some servers used internally at Google have firmware
13 these firmware callbacks. Currently, this functionality
19 /sys/firmware/gsmi/vars:
22 underlying implementation as /sys/firmware/efi/vars.
23 See Documentation/ABI/*/sysfs-firmware-efi-vars
27 /sys/firmware/gsmi/append_to_eventlog - write-only:
30 the firmware to be timestamped and appended to
32 interpreted by the firmware and may change from
36 firmware call.
[all …]
Dsysfs-ibft1 What: /sys/firmware/ibft/initiator
4 Description: The /sys/firmware/ibft/initiator directory will contain
8 What: /sys/firmware/ibft/targetX
11 Description: The /sys/firmware/ibft/targetX directory will contain
18 What: /sys/firmware/ibft/ethernetX
21 Description: The /sys/firmware/ibft/ethernetX directory will contain
Dsysfs-firmware-dmi-entries1 What: /sys/firmware/dmi/entries/
5 Many machines' firmware (x86 and ia64) export DMI /
17 length of the entry, as well as a firmware-provided
24 system unless they know for certain what their firmware
38 /sys/firmware/dmi/entries/17-0
39 /sys/firmware/dmi/entries/17-1
40 /sys/firmware/dmi/entries/17-2
41 /sys/firmware/dmi/entries/17-3
44 Instance numbers are used in lieu of the firmware
47 there are likely firmware images that get this wrong in
[all …]
Dsysfs-firmware-efi-runtime-map1 What: /sys/firmware/efi/runtime-map/
14 /sys/firmware/efi/runtime-map/ is the directory the kernel
19 /sys/firmware/efi/runtime-map/0
20 /sys/firmware/efi/runtime-map/1
21 /sys/firmware/efi/runtime-map/2
22 /sys/firmware/efi/runtime-map/3
Dsysfs-firmware-efi1 What: /sys/firmware/efi/fw_vendor
4 Description: It shows the physical address of firmware vendor field in the
8 What: /sys/firmware/efi/runtime
15 What: /sys/firmware/efi/config_table
22 What: /sys/firmware/efi/systab
Dsysfs-class-fpga-manager14 fix) then userspace can know, i.e. if the firmware request
15 fails, that could be due to not being able to find the firmware
28 * firmware request = firmware class request in progress
29 * firmware request error = firmware request failed
Dsysfs-firmware-log1 What: /sys/firmware/log
5 The /sys/firmware/log is a binary file that represents a
6 read-only copy of the firmware's log if one is
Dsysfs-firmware-sgi_uv1 What: /sys/firmware/sgi_uv/
5 The /sys/firmware/sgi_uv directory contains information
19 cat /sys/firmware/sgi_uv/partition_id
27 cat /sys/firmware/sgi_uv/coherence_id
Dsysfs-firmware-dmi-tables1 What: /sys/firmware/dmi/tables/
5 The firmware provides DMI structures as a packed list of
18 /sys/firmware/dmi/tables/smbios_entry_point
19 /sys/firmware/dmi/tables/DMI
Dsysfs-firmware-sfi1 What: /sys/firmware/sfi/tables/
6 so the kernel can get platform information from firmware.
14 # cd /sys/firmware/sfi/tables
Dsysfs-firmware-ofw1 What: /sys/firmware/devicetree/*
12 different subdirectory under /sys/firmware/devicetree.
14 Userspace must not use the /sys/firmware/devicetree/base
23 The contents of /sys/firmware/devicetree/ is a
Dsysfs-firmware-acpi1 What: /sys/firmware/acpi/bgrt/
6 to obtain a copy of the firmware boot splash and
9 the firmware boot splash in order to avoid jarring
13 status: 1 if the image is valid, 0 if firmware invalidated it.
21 What: /sys/firmware/acpi/hotplug/
31 of /sys/firmware/acpi/hotplug/.
47 What: /sys/firmware/acpi/hotplug/force_remove
57 What: /sys/firmware/acpi/interrupts/
82 /sys/firmware/acpi/interrupts contains a file listing
86 $ cd /sys/firmware/acpi/interrupts
Dsysfs-bus-event_source-devices-hv_24x730 the firmware. If firmware does not provide a description, no
41 provided by the firmware. If firmware does not provide a
Dsysfs-bus-pci178 Reading this attribute will provide the firmware
181 if the firmware has given a name to the PCI device.
183 system firmware provides SMBIOS type 41 string also.
186 firmware assigned name of the PCI device.
192 Reading this attribute will provide the firmware
194 PCI device. The attribute will be created only if the firmware
198 firmware assigned device type instance of the PCI
199 device that can help in understanding the firmware
206 Reading this attribute will provide the firmware
208 The attribute will be created only if the firmware has given
[all …]
Dsysfs-devices-firmware_node6 allowing the user space to check and modify some firmware
13 The /sys/devices/.../firmware/description attribute contains a string
Dsysfs-class-mic.txt58 of firmware, ramdisk, cmdline and bootmode
95 What: /sys/class/mic/mic(x)/firmware
101 /lib/firmware/ where the firmware image to be booted on the
103 firmware image location under /lib/firmware/.
111 /lib/firmware/ where the ramdisk image to be used during card
113 the ramdisk image location under /lib/firmware/.
/linux-4.4.14/Documentation/firmware_class/
DREADME9 Today, the most extended way to use firmware in the Linux kernel is linking
12 1) Some firmware is not legal to redistribute.
13 2) The firmware occupies memory permanently, even though it often is just
15 3) Some people, like the Debian crowd, don't consider some firmware free
26 "/lib/firmware/updates/" UTS_RELEASE,
27 "/lib/firmware/updates",
28 "/lib/firmware/" UTS_RELEASE,
29 "/lib/firmware"
37 - /sys/class/firmware/xxx/{loading,data} appear.
38 - hotplug gets called with a firmware identifier in $FIRMWARE
[all …]
/linux-4.4.14/drivers/bluetooth/
Dbcm203x.c170 const struct firmware *firmware; in bcm203x_probe() local
195 if (request_firmware(&firmware, "BCM2033-MD.hex", &udev->dev) < 0) { in bcm203x_probe()
201 BT_DBG("minidrv data %p size %zu", firmware->data, firmware->size); in bcm203x_probe()
203 size = max_t(uint, firmware->size, 4096); in bcm203x_probe()
208 release_firmware(firmware); in bcm203x_probe()
213 memcpy(data->buffer, firmware->data, firmware->size); in bcm203x_probe()
216 data->buffer, firmware->size, bcm203x_complete, data); in bcm203x_probe()
218 release_firmware(firmware); in bcm203x_probe()
220 if (request_firmware(&firmware, "BCM2033-FW.bin", &udev->dev) < 0) { in bcm203x_probe()
227 BT_DBG("firmware data %p size %zu", firmware->data, firmware->size); in bcm203x_probe()
[all …]
Dath3k.c206 const struct firmware *firmware) in ath3k_load_firmware() argument
210 int count = firmware->size; in ath3k_load_firmware()
222 memcpy(send_buf, firmware->data, 20); in ath3k_load_firmware()
239 memcpy(send_buf, firmware->data + sent, size); in ath3k_load_firmware()
302 const struct firmware *firmware) in ath3k_load_fwfile() argument
308 count = firmware->size; in ath3k_load_fwfile()
317 memcpy(send_buf, firmware->data, size); in ath3k_load_fwfile()
339 memcpy(send_buf, firmware->data + sent, size); in ath3k_load_fwfile()
393 const struct firmware *firmware; in ath3k_load_patch() local
418 ret = request_firmware(&firmware, filename, &udev->dev); in ath3k_load_patch()
[all …]
Dbfusb.c534 const unsigned char *firmware, int count) in bfusb_load_firmware() argument
565 memcpy(buf, firmware + sent, size); in bfusb_load_firmware()
615 const struct firmware *firmware; in bfusb_probe() local
656 if (request_firmware(&firmware, "bfubase.frm", &udev->dev) < 0) { in bfusb_probe()
661 BT_DBG("firmware data %p size %zu", firmware->data, firmware->size); in bfusb_probe()
663 if (bfusb_load_firmware(data, firmware->data, firmware->size) < 0) { in bfusb_probe()
668 release_firmware(firmware); in bfusb_probe()
701 release_firmware(firmware); in bfusb_probe()
Dbt3c_cs.c445 const unsigned char *firmware, in bt3c_load_firmware() argument
448 char *ptr = (char *) firmware; in bt3c_load_firmware()
536 const struct firmware *firmware; in bt3c_open() local
567 err = request_firmware(&firmware, "BT3CPCC.bin", &info->p_dev->dev); in bt3c_open()
573 err = bt3c_load_firmware(info, firmware->data, firmware->size); in bt3c_open()
575 release_firmware(firmware); in bt3c_open()
Dbtmrvl_sdio.h93 const char *firmware; member
104 const char *firmware; member
Dbtbcm.h71 int btbcm_patchram(struct hci_dev *hdev, const struct firmware *fw);
91 static inline int btbcm_patchram(struct hci_dev *hdev, const struct firmware *fw) in btbcm_patchram()
Dbtmrvl_sdio.c174 .firmware = "mrvl/sd8688.bin",
183 .firmware = "mrvl/sd8787_uapsta.bin",
192 .firmware = "mrvl/sd8797_uapsta.bin",
201 .firmware = "mrvl/sd8887_uapsta.bin",
210 .firmware = "mrvl/sd8897_uapsta.bin",
219 .firmware = "mrvl/sd8997_uapsta.bin",
382 const struct firmware *fw_helper = NULL; in btmrvl_sdio_download_helper()
480 const struct firmware *fw_firmware = NULL; in btmrvl_sdio_download_fw_w_helper()
481 const u8 *firmware = NULL; in btmrvl_sdio_download_fw_w_helper() local
490 ret = request_firmware(&fw_firmware, card->firmware, in btmrvl_sdio_download_fw_w_helper()
[all …]
/linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/
Dqe.txt25 - fsl,firmware-phandle:
26 Usage: required only if there is no fsl,qe-firmware child node
28 Definition: Points to a firmware node (see "QE Firmware Node" below)
29 that contains the firmware that should be uploaded for this QE.
30 The compatible property for the firmware node should say,
31 "fsl,qe-firmware".
74 This node defines a firmware binary that is embedded in the device tree, for
75 the purpose of passing the firmware from bootloader to the kernel, or from
78 The firmware node itself contains the firmware binary contents, a compatible
79 property, and any firmware-specific properties. The node should be placed
[all …]
/linux-4.4.14/drivers/net/wireless/libertas/
Dfirmware.c15 const struct firmware *helper, const struct firmware *mainfw) in lbs_fw_loaded()
31 void (*cb)(const struct firmware *fw, void *context)) in do_load_firmware()
44 static void main_firmware_cb(const struct firmware *firmware, void *context) in main_firmware_cb() argument
48 if (!firmware) { in main_firmware_cb()
55 lbs_fw_loaded(priv, 0, priv->helper_fw, firmware); in main_firmware_cb()
60 release_firmware (firmware); in main_firmware_cb()
63 static void helper_firmware_cb(const struct firmware *firmware, void *context) in helper_firmware_cb() argument
67 if (!firmware) { in helper_firmware_cb()
75 priv->helper_fw = firmware; in helper_firmware_cb()
79 lbs_fw_loaded(priv, 0, firmware, NULL); in helper_firmware_cb()
[all …]
Ddecl.h23 const struct firmware *helper, const struct firmware *mainfw);
75 const struct firmware **helper,
76 const struct firmware **mainfw);
Dif_sdio.c465 const struct firmware *fw) in if_sdio_prog_helper()
471 const u8 *firmware; in if_sdio_prog_helper() local
488 firmware = fw->data; in if_sdio_prog_helper()
504 memcpy(chunk_buffer + 4, firmware, chunk_size); in if_sdio_prog_helper()
513 firmware += chunk_size; in if_sdio_prog_helper()
564 const struct firmware *fw) in if_sdio_prog_real()
570 const u8 *firmware; in if_sdio_prog_real() local
587 firmware = fw->data; in if_sdio_prog_real()
644 memcpy(chunk_buffer, firmware, chunk_size); in if_sdio_prog_real()
654 firmware += chunk_size; in if_sdio_prog_real()
[all …]
Dif_spi.c462 const struct firmware *firmware) in if_spi_prog_helper_firmware() argument
475 bytes_remaining = firmware->size; in if_spi_prog_helper_firmware()
476 fw = firmware->data; in if_spi_prog_helper_firmware()
583 const struct firmware *firmware) in if_spi_prog_main_firmware() argument
607 bytes = firmware->size; in if_spi_prog_main_firmware()
608 fw = firmware->data; in if_spi_prog_main_firmware()
1035 const struct firmware *helper = NULL; in if_spi_init_card()
1036 const struct firmware *mainfw = NULL; in if_spi_init_card()
/linux-4.4.14/firmware/
DREADME.AddingFirmware5 This directory is only here to contain firmware images extracted from old
9 separation between code and firmware, we put the extracted firmware
12 This directory is _NOT_ for adding arbitrary new firmware images. The
13 place to add those is the separate linux-firmware repository:
15 git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
17 That repository contains all these firmware images which have been
18 extracted from older drivers, as well various new firmware images which
22 To submit firmware to that repository, please send either a git binary
24 linux-firmware@kernel.org
28 identifying the licence under which the firmware is available, and
[all …]
DWHENCE6 if known, for each piece of firmware distributed for use with the Linux
13 File: firmware/atmsar11.fw
35 Found in alsa-firmware package in hex form; no licensing information.
46 Found in alsa-firmware package in hex form with a comment claiming to
61 Found alsa-firmware package in hex form, with the following comment:
139 public access to the source code from which this firmware image is
140 derived. Except as noted below this firmware image may not be
144 Permission is hereby granted for the distribution of this firmware
148 This firmware may not be modified and may only be used with
150 keyspan.c driver which includes this firmware, in whole or in
[all …]
Dwhiteheat_loader.HEX295 * Updated the firmware with the latest provided by ConnectTech.
298 * Fixed my intel hex processing tool, so now the firmware actually
302 * Added debug loader firmware if DEBUG is #defined:
309 * Original firmware from ConnectTech massaged a little to be program
Dwhiteheat_loader_debug.HEX384 * Updated the firmware with the latest provided by ConnectTech.
387 * Fixed my intel hex processing tool, so now the firmware actually
391 * Added debug loader firmware if DEBUG is #defined:
398 * Original firmware from ConnectTech massaged a little to be program
/linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/qe/
Dfirmware.txt1 * Uploaded QE firmware
3 If a new firmware has been uploaded to the QE (usually by the
4 boot loader), then a 'firmware' child node should be added to the QE
5 node. This node provides information on the uploaded firmware that
9 - id: The string name of the firmware. This is taken from the 'id'
10 member of the qe_firmware structure of the uploaded firmware.
12 firmware they want is already present.
14 firmware binary. It is a 64-bit number represented
16 - virtual-traps: The virtual traps, taken from the firmware binary.
20 firmware {
/linux-4.4.14/drivers/media/usb/as102/
Das102_fw.c102 const struct firmware *firmware) { in as102_firmware_upload() argument
108 for (total_read_bytes = 0; total_read_bytes < firmware->size; ) { in as102_firmware_upload()
113 (u8 *) (firmware->data + total_read_bytes), in as102_firmware_upload()
124 if (total_read_bytes == firmware->size) { in as102_firmware_upload()
161 const struct firmware *firmware = NULL; in as102_fw_upload() local
183 errno = request_firmware(&firmware, fw1, &dev->dev); in as102_fw_upload()
191 errno = as102_firmware_upload(bus_adap, cmd_buf, firmware); in as102_fw_upload()
200 release_firmware(firmware); in as102_fw_upload()
206 errno = request_firmware(&firmware, fw2, &dev->dev); in as102_fw_upload()
214 errno = as102_firmware_upload(bus_adap, cmd_buf, firmware); in as102_fw_upload()
[all …]
/linux-4.4.14/include/linux/
Dfirmware.h11 struct firmware { struct
42 int request_firmware(const struct firmware **fw, const char *name,
47 void (*cont)(const struct firmware *fw, void *context));
48 int request_firmware_direct(const struct firmware **fw, const char *name,
51 void release_firmware(const struct firmware *fw);
53 static inline int request_firmware(const struct firmware **fw, in request_firmware()
62 void (*cont)(const struct firmware *fw, void *context)) in request_firmware_nowait()
67 static inline void release_firmware(const struct firmware *fw) in release_firmware()
71 static inline int request_firmware_direct(const struct firmware **fw, in request_firmware_direct()
Dihex.h34 static inline int ihex_validate_fw(const struct firmware *fw) in ihex_validate_fw()
54 static inline int request_ihex_firmware(const struct firmware **fw, in request_ihex_firmware()
58 const struct firmware *lfw; in request_ihex_firmware()
/linux-4.4.14/drivers/remoteproc/
Dremoteproc_internal.h39 const struct firmware *fw,
42 const struct firmware *fw);
43 int (*load)(struct rproc *rproc, const struct firmware *fw);
44 int (*sanity_check)(struct rproc *rproc, const struct firmware *fw);
45 u32 (*get_boot_addr)(struct rproc *rproc, const struct firmware *fw);
72 int rproc_fw_sanity_check(struct rproc *rproc, const struct firmware *fw) in rproc_fw_sanity_check()
81 u32 rproc_get_boot_addr(struct rproc *rproc, const struct firmware *fw) in rproc_get_boot_addr()
90 int rproc_load_segments(struct rproc *rproc, const struct firmware *fw) in rproc_load_segments()
100 const struct firmware *fw, int *tablesz) in rproc_find_rsc_table()
110 const struct firmware *fw) in rproc_find_loaded_rsc_table()
Dremoteproc_elf_loader.c43 rproc_elf_sanity_check(struct rproc *rproc, const struct firmware *fw)
45 const char *name = rproc->firmware;
114 u32 rproc_elf_get_boot_addr(struct rproc *rproc, const struct firmware *fw)
146 rproc_elf_load_segments(struct rproc *rproc, const struct firmware *fw)
286 rproc_elf_find_rsc_table(struct rproc *rproc, const struct firmware *fw,
319 rproc_elf_find_loaded_rsc_table(struct rproc *rproc, const struct firmware *fw)
Dremoteproc_core.c795 static int rproc_fw_boot(struct rproc *rproc, const struct firmware *fw) in rproc_fw_boot()
798 const char *name = rproc->firmware; in rproc_fw_boot()
898 static void rproc_fw_config_virtio(const struct firmware *fw, void *context) in rproc_fw_config_virtio()
958 rproc->firmware, &rproc->dev, GFP_KERNEL, in rproc_add_virtio_devices()
1043 const struct firmware *firmware_p; in rproc_boot()
1061 if (!rproc->firmware) { in rproc_boot()
1083 ret = request_firmware(&firmware_p, rproc->firmware, dev); in rproc_boot()
1314 const char *firmware, int len) in rproc_alloc() argument
1323 if (!firmware) in rproc_alloc()
1338 if (!firmware) { in rproc_alloc()
[all …]
DKconfig54 firmware onto these remote processors.
71 This module controls the name of the firmware file that gets
72 loaded on the DSP. This file must reside in the /lib/firmware
/linux-4.4.14/drivers/usb/misc/
Disight_firmware.c42 const struct firmware *firmware; in isight_firmware_load() local
50 if (request_firmware(&firmware, "isight.fw", &dev->dev) != 0) { in isight_firmware_load()
56 ptr = firmware->data; in isight_firmware_load()
68 while (ptr+4 <= firmware->data+firmware->size) { in isight_firmware_load()
82 if (ptr+llen > firmware->data+firmware->size) { in isight_firmware_load()
114 release_firmware(firmware); in isight_firmware_load()
Dezusb.c78 const struct firmware *firmware = NULL; in ezusb_ihex_firmware_download() local
81 if (request_ihex_firmware(&firmware, firmware_path, in ezusb_ihex_firmware_download()
93 record = (const struct ihex_binrec *)firmware->data; in ezusb_ihex_firmware_download()
113 record = (const struct ihex_binrec *)firmware->data; in ezusb_ihex_firmware_download()
131 release_firmware(firmware); in ezusb_ihex_firmware_download()
DKconfig9 This driver loads firmware to Emagic EMI 6|2m low latency USB
12 After firmware load the device is handled with standard linux
23 This driver loads firmware to Emagic EMI 2|6 low latency USB
26 After firmware load the device is handled with standard linux
96 driver supports the pre-programmed devices (incl. firmware)
196 with specialized device firmware for regression and stress testing,
200 including sample test device firmware and "how to use it".
216 tristate "iSight firmware loading support"
219 This driver loads firmware for USB Apple iSight cameras, allowing
223 The firmware for this driver must be extracted from the MacOS
[all …]
Demi26.c76 const struct firmware *loader_fw = NULL; in emi26_load_firmware()
77 const struct firmware *bitstream_fw = NULL; in emi26_load_firmware()
78 const struct firmware *firmware_fw = NULL; in emi26_load_firmware()
/linux-4.4.14/arch/powerpc/sysdev/qe_lib/
Dqe.c419 int qe_upload_firmware(const struct qe_firmware *firmware) in qe_upload_firmware() argument
428 if (!firmware) { in qe_upload_firmware()
433 hdr = &firmware->header; in qe_upload_firmware()
450 if ((firmware->count < 1) || (firmware->count > MAX_QE_RISC)) { in qe_upload_firmware()
456 calc_size += (firmware->count - 1) * sizeof(struct qe_microcode); in qe_upload_firmware()
458 for (i = 0; i < firmware->count; i++) in qe_upload_firmware()
465 be32_to_cpu(firmware->microcode[i].count); in qe_upload_firmware()
474 crc = be32_to_cpu(*(__be32 *)((void *)firmware + calc_size)); in qe_upload_firmware()
475 if (crc != crc32(0, firmware, calc_size)) { in qe_upload_firmware()
483 if (!firmware->split) in qe_upload_firmware()
[all …]
/linux-4.4.14/Documentation/leds/
Dleds-lp55xx.txt62 LP55xx common driver supports the firmware interface.
73 run_engine : Start program which is loaded via the firmware interface
74 firmware : Load program data
82 echo 1 > /sys/class/firmware/lp5521/loading
83 echo "4000600040FF6000" > /sys/class/firmware/lp5521/data
84 echo 0 > /sys/class/firmware/lp5521/loading
90 echo 1 > /sys/class/firmware/lp55231/loading
91 echo "9d0740ff7e0040007e00a0010000" > /sys/class/firmware/lp55231/data
92 echo 0 > /sys/class/firmware/lp55231/loading
101 echo 1 > /sys/class/firmware/lp5521/loading
[all …]
Dleds-lp5562.txt15 For the details, please refer to 'firmware' section in leds-lp55xx.txt
23 This attribute is used for programming LED data with the firmware interface.
36 the engine selection and loading the firmware.
43 echo 1 > /sys/class/firmware/lp5562/loading
44 echo "4000600040FF6000" > /sys/class/firmware/lp5562/data
45 echo 0 > /sys/class/firmware/lp5562/loading
51 echo 1 > /sys/class/firmware/lp5562/loading
52 echo "4000600040FF6000" > /sys/class/firmware/lp5562/data
53 echo 0 > /sys/class/firmware/lp5562/loading
/linux-4.4.14/Documentation/dvb/
Dttusb-dec.txt16 Hotplug firmware loader under 2.6 kernels
26 To download the firmware, use the following commands:
34 For 2.4 kernels the firmware for the DECs is compiled into the driver itself.
41 For 2.6 kernels the firmware is loaded at the point that the driver module is
42 loaded. See linux/Documentation/dvb/firmware.txt for more information.
44 Copy the three files downloaded above into the /usr/lib/hotplug/firmware or
45 /lib/firmware directory (depending on configuration of firmware hotplug).
Dlmedm04.txt1 To extract firmware for the DM04/QQBOX you need to copy the
18 An alternative but older firmware can be found on the driver
31 The LG firmware can be found on the driver
46 Other LG firmware can be extracted manually from US280D.sys
77 We need to modify id of rs2000 firmware or it will warm boot id 3344:1120.
81 Copy the firmware file(s) to /lib/firmware
Dopera-firmware.txt1 To extract the firmware for the Opera DVB-S1 USB-Box
20 Copy them into /lib/firmware/ .
22 After that the driver can load the firmware
23 (if you have enabled firmware loading
DREADME.dvb-usb6 In March 2005 I got the new Twinhan USB2.0 DVB-T device. They provided specs and a firmware.
20 - firmware requesting and loading (currently just for the Cypress USB
102 2004-07-08 - firmware-extraction-2.422-problem solved, driver is now working
103 properly with firmware extracted from 2.422
105 - changed firmware handling, see vp7041.txt sec 1.1
112 2004-05-14 - firmware loader is working
118 Most of the USB drivers need to download a firmware to the device before start
121 Have a look at the Wikipage for the DVB-USB-drivers to find out, which firmware
155 When the driver is loaded successfully, the firmware file was in
212 Jung from AVerMedia who kindly provided a special firmware to get the device
[all …]
/linux-4.4.14/Documentation/networking/
Dfore200e.txt30 The FORE Systems 200E-series driver is shipped with firmware data being
32 The supplied firmware images should work with all adapters.
34 However, if you encounter problems (the firmware doesn't start or the driver
35 is unable to read the PROM data), you may consider trying another firmware
36 version. Alternative binary firmware images can be found somewhere on the
39 You can also get the latest firmware images from FORE Systems at
41 the 'software updates' pages. The firmware binaries are part of
44 Notice that different versions of the PCA-200E firmware exist, depending
46 both little and big endian PCA firmware images.
48 Name and location of the new firmware images can be set at kernel
[all …]
/linux-4.4.14/Documentation/arm/keystone/
Dknav-qmss.txt29 Accumulator QMSS queues using PDSP firmware
31 The QMSS PDSP firmware support accumulator channel that can monitor a single
35 1 or 32 queues per channel. More description on the firmware is available in
39 k2_qmss_pdsp_acc48_k2_le_1_0_0_9.bin firmware supports upto 48 accumulator
40 channels. This firmware is available under ti-keystone folder of
41 firmware.git at
42 git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
44 To use copy the firmware image to lib/firmware folder of the initramfs or
48 "firmware file ks2_qmss_pdsp_acc48.bin downloaded for PDSP"
50 in the boot up log if loading of firmware to PDSP is successful.
[all …]
/linux-4.4.14/Documentation/devicetree/bindings/arm/bcm/
Draspberrypi,bcm2835-firmware.txt1 Raspberry Pi VideoCore firmware driver
5 - compatible: Should be "raspberrypi,bcm2835-firmware"
6 - mboxes: Phandle to the firmware device's Mailbox.
11 firmware {
12 compatible = "raspberrypi,bcm2835-firmware";
/linux-4.4.14/drivers/net/wireless/realtek/rtlwifi/rtl8192se/
Dfw.c224 struct rt_firmware *firmware = (struct rt_firmware *)rtlhal->pfirmware; in _rtl92s_firmware_checkready() local
233 firmware->fwstatus = (enum fw_status)loadfw_status; in _rtl92s_firmware_checkready()
355 struct rt_firmware *firmware = NULL; in rtl92s_download_fw() local
367 firmware = (struct rt_firmware *)rtlhal->pfirmware; in rtl92s_download_fw()
368 firmware->fwstatus = FW_STATUS_INIT; in rtl92s_download_fw()
370 puc_mappedfile = firmware->sz_fw_tmpbuffer; in rtl92s_download_fw()
373 firmware->pfwheader = (struct fw_hdr *) puc_mappedfile; in rtl92s_download_fw()
374 pfwheader = firmware->pfwheader; in rtl92s_download_fw()
375 firmware->firmwareversion = byte(pfwheader->version, 0); in rtl92s_download_fw()
376 firmware->pfwheader->fwpriv.hci_sel = 1;/* pcie */ in rtl92s_download_fw()
[all …]
Dsw.c87 static void rtl92se_fw_cb(const struct firmware *firmware, void *context) in rtl92se_fw_cb() argument
96 if (!firmware) { in rtl92se_fw_cb()
101 if (firmware->size > rtlpriv->max_fw_size) { in rtl92se_fw_cb()
105 release_firmware(firmware); in rtl92se_fw_cb()
109 memcpy(pfirmware->sz_fw_tmpbuffer, firmware->data, firmware->size); in rtl92se_fw_cb()
110 pfirmware->sz_fw_tmpbufferlen = firmware->size; in rtl92se_fw_cb()
111 release_firmware(firmware); in rtl92se_fw_cb()
/linux-4.4.14/sound/isa/wavefront/
Dwavefront_fx.c248 const struct firmware *firmware = NULL; in snd_wavefront_fx_start() local
253 err = request_firmware(&firmware, "yamaha/yss225_registers.bin", in snd_wavefront_fx_start()
260 for (i = 0; i + 1 < firmware->size; i += 2) { in snd_wavefront_fx_start()
261 if (firmware->data[i] >= 8 && firmware->data[i] < 16) { in snd_wavefront_fx_start()
262 outb(firmware->data[i + 1], in snd_wavefront_fx_start()
263 dev->base + firmware->data[i]); in snd_wavefront_fx_start()
264 } else if (firmware->data[i] == WAIT_IDLE) { in snd_wavefront_fx_start()
281 release_firmware(firmware); in snd_wavefront_fx_start()
/linux-4.4.14/Documentation/arm/
Dfirmware.txt1 Interface for registering and calling firmware-specific operations for ARM.
5 Some boards are running with secure firmware running in TrustZone secure
7 a need to provide an interface for such platforms to specify available firmware
17 and its members can be found in arch/arm/include/asm/firmware.h header.
20 set anything if platform does not require firmware operations.
22 To call a firmware operation, a helper macro is provided
31 Example of registering firmware operations:
37 /* tell platformX firmware to enter idle */
43 /* tell platformX firmware to boot CPU i */
59 Example of using a firmware operation:
D00-INDEX33 firmware.txt
34 - Secure firmware registration and calling.
/linux-4.4.14/Documentation/video4linux/cx2341x/
Dfw-calling.txt1 This page describes how to make calls to the firmware api.
6 The preferred calling convention is known as the firmware mailbox. The
16 The firmware implements 20 mailboxes of 20 32-bit words. The first 10 are
17 reserved for API calls. The second 10 are used by the firmware for event
30 perspective of the firmware.
51 doesn't handle the completed call within the timeout specified, the firmware
57 driver then sets the parameter ready bit (bit 1). The firmware scans the
62 time set in the timeout register, the firmware will reset that mailbox.
64 Event notifications are sent from the firmware to the host. The host tells the
65 firmware which events it is interested in via an API call. That call tells the
[all …]
Dfw-upload.txt1 This document describes how to upload the cx2341x firmware to the card.
7 on how to obtain the firmware.
9 The firmware stored in a Windows driver can be detected as follows:
11 - Each firmware image is 256k bytes.
24 - Issue the FWapi command to halt the encoder's firmware.
26 - Issue the FWapi command to halt the decoder's firmware.
40 - Transfer the encoder's firmware image to offset 0 in Encoder memory space.
41 - Transfer the decoder's firmware image to offset 0 in Decoder memory space.
48 - Issue status API commands to both firmware images to verify.
Dfw-decoder-api.txt1 Decoder firmware API description
4 Note: this API is part of the decoder firmware, so it's cx23415 only.
11 This API call does nothing. It may be used to check if the firmware
24 audio resumes. (This is not implemented in the firmware, leave at 0)
51 Smooth: host transfers entire stream and firmware drops unused
89 resumes. (Not implemented in the firmware, leave at 0)
168 The firmware is halted and no further API calls are serviced until
169 the firmware is uploaded again.
185 Returns decoder firmware version information
236 Setup firmware to notify the host about a particular event.
/linux-4.4.14/Documentation/hwmon/
Dnct668331 Limit register locations on Intel boards with EC firmware version 1.0
33 datasheet. Nuvoton confirms that Intel uses a special firmware version
35 firmware is held under NDA by Nuvoton and Intel and not available
40 considered too risky with this firmware and has been disabled. All limits
43 The driver has only been tested with the Intel firmware, and by default
51 firmware versions.
55 Intel DH87RL NCT6683D EC firmware version 1.0 build 04/03/13
56 Intel DH87MC NCT6683D EC firmware version 1.0 build 04/03/13
57 Intel DB85FL NCT6683D EC firmware version 1.0 build 04/03/13
Dacpi_power_meter44 There are a few other ACPI notifications that can be sent by the firmware. In
49 power[1-*]_cap will be notified if the firmware changes the power cap.
50 power[1-*]_interval will be notified if the firmware changes the averaging
/linux-4.4.14/drivers/staging/gs_fpgaboot/
DREADME2 Linux Driver Source for Xilinx FPGA firmware download
16 - Download Xilinx FPGA firmware
17 - This module downloads Xilinx FPGA firmware using gpio pins.
24 This driver provides a way to download FPGA firmware.
28 - load Xilinx FPGA bitstream format[1] firmware image file using
29 kernel firmware framework, request_firmware()
43 During FPGA firmware development, you need to download a new FPGA
53 We download FPGA firmware from user triggered or some other way, and that's it.
62 download FPGA firmware during the Linux boot, the take over the device
DKconfig2 # "xilinx FPGA firmware download, fpgaboot"
5 tristate "Xilinx FPGA firmware download module"
8 Xilinx FPGA firmware download module
/linux-4.4.14/tools/testing/selftests/firmware/
Dfw_userhelper.sh15 HAS_FW_LOADER_USER_HELPER=$(if [ -d /sys/class/firmware/ ]; then echo yes; else echo no; fi)
18 OLD_TIMEOUT=$(cat /sys/class/firmware/timeout)
29 echo "$OLD_TIMEOUT" >/sys/class/firmware/timeout
68 echo 1 >/sys/class/firmware/timeout
79 echo 4 >/sys/class/firmware/timeout
Dfw_filesystem.sh15 HAS_FW_LOADER_USER_HELPER=$(if [ -d /sys/class/firmware/ ]; then echo yes; else echo no; fi)
18 OLD_TIMEOUT=$(cat /sys/class/firmware/timeout)
29 echo "$OLD_TIMEOUT" >/sys/class/firmware/timeout
40 echo 1 >/sys/class/firmware/timeout
/linux-4.4.14/drivers/base/
DKconfig63 bool "Select only drivers that don't need compile-time external firmware"
66 Select this option if you don't have magic firmware for drivers that
72 bool "Prevent firmware from being built"
75 Say yes to avoid building firmware. Firmware is usually shipped
76 with the driver and only when updating the firmware should a
81 tristate "Userspace firmware loading support" if EXPERT
85 require userspace firmware loading support, but a module built
89 bool "Include in-kernel firmware blobs in kernel binary"
93 The kernel source tree includes a number of firmware 'blobs'
97 binary files in firmware/ to /lib/firmware/ on your system so
[all …]
Dfirmware_class.c48 static bool fw_get_builtin_firmware(struct firmware *fw, const char *name) in fw_get_builtin_firmware()
63 static bool fw_is_builtin_firmware(const struct firmware *fw) in fw_is_builtin_firmware()
76 static inline bool fw_get_builtin_firmware(struct firmware *fw, const char *name) in fw_get_builtin_firmware()
81 static inline bool fw_is_builtin_firmware(const struct firmware *fw) in fw_is_builtin_firmware()
376 static void firmware_free_data(const struct firmware *fw) in firmware_free_data()
387 static void fw_set_page_data(struct firmware_buf *buf, struct firmware *fw) in fw_set_page_data()
471 struct firmware *fw;
888 fw_create_instance(struct firmware *firmware, const char *fw_name, in fw_create_instance() argument
901 fw_priv->fw = firmware; in fw_create_instance()
966 static int fw_load_from_user_helper(struct firmware *firmware, in fw_load_from_user_helper() argument
[all …]
/linux-4.4.14/drivers/scsi/esas2r/
Desas2r_ioctl.c95 (*addr) = a->firmware.phys + offset; in get_physaddr_fm_api()
96 return a->firmware.orig_len - offset; in get_physaddr_fm_api()
104 (*addr) = a->firmware.header_buff_phys + offset; in get_physaddr_fm_api_header()
124 if (fi == &a->firmware.header) { in do_fm_api()
125 a->firmware.header_buff = dma_alloc_coherent(&a->pcid->dev, in do_fm_api()
130 firmware. in do_fm_api()
134 if (a->firmware.header_buff == NULL) { in do_fm_api()
140 memcpy(a->firmware.header_buff, fi, in do_fm_api()
142 a->save_offset = a->firmware.header_buff; in do_fm_api()
164 if (fi == &a->firmware.header) { in do_fm_api()
[all …]
/linux-4.4.14/drivers/media/i2c/cx25840/
Dcx25840-firmware.c39 static char *firmware = ""; variable
41 module_param(firmware, charp, 0444);
43 MODULE_PARM_DESC(firmware, "Firmware image to load");
72 if (firmware[0]) in get_fw_name()
73 return firmware; in get_fw_name()
111 const struct firmware *fw = NULL; in cx25840_loadfw()
/linux-4.4.14/Documentation/devicetree/bindings/arm/firmware/
Dtlm,trusted-foundations.txt6 under the /firmware/ node
10 - tlm,version-major: major version number of Trusted Foundations firmware
11 - tlm,version-minor: minor version number of Trusted Foundations firmware
14 firmware {
/linux-4.4.14/drivers/misc/mic/cosm/
Dcosm_sysfs.c236 char *firmware; in firmware_show() local
241 firmware = cdev->firmware; in firmware_show()
243 if (firmware) in firmware_show()
244 return scnprintf(buf, PAGE_SIZE, "%s\n", firmware); in firmware_show()
258 kfree(cdev->firmware); in firmware_store()
260 cdev->firmware = kmalloc(count + 1, GFP_KERNEL); in firmware_store()
261 if (!cdev->firmware) { in firmware_store()
265 strncpy(cdev->firmware, buf, count); in firmware_store()
267 if (cdev->firmware[count - 1] == '\n') in firmware_store()
268 cdev->firmware[count - 1] = '\0'; in firmware_store()
[all …]
/linux-4.4.14/firmware/keyspan/
Dusa19.HEX83 The firmware contained herein is
89 public access to the source code from which this firmware image is
90 derived. Except as noted below this firmware image may not be
94 Permission is hereby granted for the distribution of this firmware
98 This firmware may not be modified and may only be used with
100 keyspan.c driver which includes this firmware, in whole or in
Dusa19qi.HEX83 The firmware contained herein is
89 public access to the source code from which this firmware image is
90 derived. Except as noted below this firmware image may not be
94 Permission is hereby granted for the distribution of this firmware
98 This firmware may not be modified and may only be used with
100 keyspan.c driver which includes this firmware, in whole or in
Dmpr.HEX82 The firmware contained herein is
88 public access to the source code from which this firmware image is
89 derived. Except as noted below this firmware image may not be
93 Permission is hereby granted for the distribution of this firmware
97 This firmware may not be modified and may only be used with
99 keyspan.c driver which includes this firmware, in whole or in
Dusa28x.HEX123 The firmware contained herein is
129 public access to the source code from which this firmware image is
130 derived. Except as noted below this firmware image may not be
134 Permission is hereby granted for the distribution of this firmware
138 This firmware may not be modified and may only be used with
140 keyspan.c driver which includes this firmware, in whole or in
Dusa19w.HEX123 The firmware contained herein is
129 public access to the source code from which this firmware image is
130 derived. Except as noted below this firmware image may not be
134 Permission is hereby granted for the distribution of this firmware
138 This firmware may not be modified and may only be used with
140 keyspan.c driver which includes this firmware, in whole or in
Dusa28xb.HEX124 The firmware contained herein is
130 public access to the source code from which this firmware image is
131 derived. Except as noted below this firmware image may not be
135 Permission is hereby granted for the distribution of this firmware
139 This firmware may not be modified and may only be used with
141 keyspan.c driver which includes this firmware, in whole or in
Dusa18x.HEX123 The firmware contained herein is
129 public access to the source code from which this firmware image is
130 derived. Except as noted below this firmware image may not be
134 Permission is hereby granted for the distribution of this firmware
138 This firmware may not be modified and may only be used with
140 keyspan.c driver which includes this firmware, in whole or in
Dusa19qw.HEX124 The firmware contained herein is
130 public access to the source code from which this firmware image is
131 derived. Except as noted below this firmware image may not be
135 Permission is hereby granted for the distribution of this firmware
139 This firmware may not be modified and may only be used with
141 keyspan.c driver which includes this firmware, in whole or in
Dusa28xa.HEX123 The firmware contained herein is
129 public access to the source code from which this firmware image is
130 derived. Except as noted below this firmware image may not be
134 Permission is hereby granted for the distribution of this firmware
138 This firmware may not be modified and may only be used with
140 keyspan.c driver which includes this firmware, in whole or in
Dusa49w.HEX127 The firmware contained herein is
133 public access to the source code from which this firmware image is
134 derived. Except as noted below this firmware image may not be
138 Permission is hereby granted for the distribution of this firmware
142 This firmware may not be modified and may only be used with
144 keyspan.c driver which includes this firmware, in whole or in
Dusa28.HEX130 The firmware contained herein is
136 public access to the source code from which this firmware image is
137 derived. Except as noted below this firmware image may not be
141 Permission is hereby granted for the distribution of this firmware
145 This firmware may not be modified and may only be used with
147 keyspan.c driver which includes this firmware, in whole or in
Dusa49wlc.HEX128 The firmware contained herein is
134 public access to the source code from which this firmware image is
135 derived. Except as noted below this firmware image may not be
139 Permission is hereby granted for the distribution of this firmware
143 This firmware may not be modified and may only be used with
145 keyspan.c driver which includes this firmware, in whole or in
/linux-4.4.14/Documentation/scsi/
Dwd719x.txt4 The card requires firmware that can be cut out of the Windows NT driver that
8 There is no license anywhere in the file or on the page - so the firmware
9 probably cannot be added to linux-firmware.
11 This script downloads and extracts the firmware, creating wd719x-risc.bin and
12 d719x-wcs.bin files. Put them in /lib/firmware/.
/linux-4.4.14/Documentation/ABI/stable/
Dsysfs-firmware-opal-elog1 What: /sys/firmware/opal/elog
6 through the OPAL firmware interface.
9 exist until explicitly acknowledged to firmware.
11 Each log entry has a directory in /sys/firmware/opal/elog.
14 before retrieved by firmware or retrieved/acknowledged by
18 but not explicitly acknowledged them to firmware and
27 entries than firmware can, so after you acknowledge
55 the error log to firmware (and in turn
Dsysfs-class-backlight44 "firmware": The driver uses a standard firmware interface
49 interfaces are available for a single device, firmware
51 be preferred to raw control. Using a firmware
55 holdover from pre-standardisation of firmware
Dsysfs-firmware-opal-dump1 What: /sys/firmware/opal/dump
6 the FSP and platform dumps through OPAL firmware interface.
31 we could not get the type from firmware.
Dsysfs-firmware-efi-vars1 What: /sys/firmware/efi/vars
69 instructs the EFI firmware to create a
73 instructs the EFI firmware to remove any
/linux-4.4.14/drivers/media/usb/dvb-usb/
Ddvb-usb-firmware.c36 int usb_cypress_load_firmware(struct usb_device *udev, const struct firmware *fw, int type) in usb_cypress_load_firmware()
81 const struct firmware *fw = NULL; in dvb_usb_download_firmware()
83 if ((ret = request_firmware(&fw, props->firmware, &udev->dev)) != 0) { in dvb_usb_download_firmware()
86 props->firmware,ret); in dvb_usb_download_firmware()
90 info("downloading firmware from file '%s'",props->firmware); in dvb_usb_download_firmware()
115 int dvb_usb_get_hexline(const struct firmware *fw, struct hexline *hx, in dvb_usb_get_hexline()
Ddtt200u.c138 .firmware = "dvb-usb-dtt200u-01.fw",
188 .firmware = "dvb-usb-wt220u-02.fw",
238 .firmware = "dvb-usb-wt220u-fc03.fw",
288 .firmware = "dvb-usb-wt220u-zl0353-01.fw",
338 .firmware = "dvb-usb-wt220u-miglia-01.fw",
Ddvb-usb.h271 int (*download_firmware) (struct usb_device *, const struct firmware *);
272 const char *firmware; member
479 extern int usb_cypress_load_firmware(struct usb_device *udev, const struct firmware *fw, int type);
480 extern int dvb_usb_get_hexline(const struct firmware *fw, struct hexline *hx, int *pos);
Ddibusb-mb.c184 .firmware = "dvb-usb-dibusb-5.0.0.11.fw",
274 .firmware = "dvb-usb-dibusb-an2235-01.fw",
343 .firmware = "dvb-usb-adstech-usb2-02.fw",
406 .firmware = "dvb-usb-dibusb-6.0.0.8.fw",
/linux-4.4.14/drivers/net/wireless/realtek/rtlwifi/
Dcore.h76 void rtl_fw_cb(const struct firmware *firmware, void *context);
77 void rtl_wowlan_fw_cb(const struct firmware *firmware, void *context);
Dcore.c98 static void rtl_fw_do_work(const struct firmware *firmware, void *context, in rtl_fw_do_work() argument
108 if (!firmware) { in rtl_fw_do_work()
110 err = request_firmware(&firmware, in rtl_fw_do_work()
123 if (firmware->size > rtlpriv->max_fw_size) { in rtl_fw_do_work()
126 release_firmware(firmware); in rtl_fw_do_work()
130 memcpy(rtlpriv->rtlhal.pfirmware, firmware->data, in rtl_fw_do_work()
131 firmware->size); in rtl_fw_do_work()
132 rtlpriv->rtlhal.fwsize = firmware->size; in rtl_fw_do_work()
134 memcpy(rtlpriv->rtlhal.wowlan_firmware, firmware->data, in rtl_fw_do_work()
135 firmware->size); in rtl_fw_do_work()
[all …]
/linux-4.4.14/drivers/net/wireless/orinoco/
Dfw.c83 static inline const struct firmware *
105 const struct firmware *fw_entry; in orinoco_dl_firmware()
109 const char *firmware; in orinoco_dl_firmware() local
119 firmware = fw->ap_fw; in orinoco_dl_firmware()
121 firmware = fw->sta_fw; in orinoco_dl_firmware()
123 dev_dbg(dev, "Attempting to download firmware %s\n", firmware); in orinoco_dl_firmware()
132 err = request_firmware(&fw_entry, firmware, priv->dev); in orinoco_dl_firmware()
135 dev_err(dev, "Cannot find firmware %s\n", firmware); in orinoco_dl_firmware()
292 const struct firmware *fw_entry; in symbol_dl_firmware()
359 const struct firmware *fw_entry = NULL; in orinoco_cache_fw()
DKconfig38 would not support WPA or firmware download for Prism chipset.
43 bool "Cache Hermes firmware on driver initialisation"
47 Say Y to cache any firmware required by the Hermes drivers
48 on startup. The firmware will remain cached until the
51 Otherwise load the firmware from userspace as required. In
53 whenever the firmware is changed.
130 firmware, such as Symbol Wireless Networker LA4100, CompactFlash
133 This driver requires firmware download on startup. Utilities
134 for downloading Symbol firmware are available at
Dorinoco.h58 struct firmware;
164 const struct firmware *cached_pri_fw;
165 const struct firmware *cached_fw;
/linux-4.4.14/Documentation/devicetree/bindings/remoteproc/
Dwkup_m3_rproc.txt6 that cannot be controlled from the MPU. This CM3 processor requires a firmware
8 the firmware and booting of the CM3.
28 - ti,pm-firmware: Name of firmware file to be used for loading and
47 ti,pm-firmware = "am335x-pm-firmware.elf";
/linux-4.4.14/drivers/net/wireless/ipw2x00/
DKconfig22 In order to use this driver, you will need a firmware image for it.
23 You can obtain the firmware from
24 <http://ipw2100.sf.net/>. Once you have the firmware image, you
25 will need to place it in /lib/firmware.
33 rather than built-in (Y). This driver requires firmware at device
35 before the filesystem is accessible (hence firmware will be
38 including the firmware and a firmware loader in an initramfs.
84 In order to use this driver, you will need a firmware image for it.
85 You can obtain the firmware from
87 for information on where to install the firmware images.
[all …]
/linux-4.4.14/sound/pci/pcxhr/
Dpcxhr_core.h26 struct firmware;
33 int pcxhr_load_xilinx_binary(struct pcxhr_mgr *mgr, const struct firmware *xilinx, int second);
34 int pcxhr_load_eeprom_binary(struct pcxhr_mgr *mgr, const struct firmware *eeprom);
35 int pcxhr_load_boot_binary(struct pcxhr_mgr *mgr, const struct firmware *boot);
36 int pcxhr_load_dsp_binary(struct pcxhr_mgr *mgr, const struct firmware *dsp);
/linux-4.4.14/firmware/emi26/
Dloader.HEX104 * This firmware is for the Emagic EMI 2|6 Audio Interface
106 * The firmware contained herein is Copyright (c) 1999-2002 Emagic
108 * or public access to this firmware which is a trade secret of Emagic,
112 * This firmware may not be modified and may only be used with the
114 * any driver which includes this firmware, in whole or in part,
/linux-4.4.14/drivers/acpi/apei/
DKconfig29 errors are reported to firmware firstly, then reported to
30 Linux by firmware. This way, some non-standard hardware
32 by firmware to produce more valuable hardware error
39 PCIe AER errors may be reported via APEI firmware first mode.
46 Memory errors may be reported via APEI firmware first mode.
64 and firmware implementation.
/linux-4.4.14/drivers/media/usb/ttusb-dec/
DKconfig14 This driver needs external firmware. Please use the commands
18 download/extract them, and then copy them to /usr/lib/hotplug/firmware
19 or /lib/firmware (depending on configuration of firmware hotplug).
/linux-4.4.14/Documentation/video4linux/
Dcx18.txt26 You can obtain the firmware files here:
28 http://dl.ivtvdriver.org/ivtv/firmware/cx18-firmware.tar.gz
30 Untar and copy the .fw files to your firmware directory.
/linux-4.4.14/Documentation/
Dbtmrvl.txt55 These commands are used to enable host sleep or wake up firmware
59 0 -- Wake up firmware
66 # Wake up firmware
111 SD8688 firmware:
113 /lib/firmware/sd8688_helper.bin
114 /lib/firmware/sd8688.bin
119 git.infradead.org/users/dwmw2/linux-firmware.git/libertas/
Ddell_rbu.txt34 /sys/class/firmware/dell_rbu/loading
35 /sys/class/firmware/dell_rbu/data
63 This file is then copied to /sys/class/firmware/dell_rbu/data.
73 1) echo 1 > /sys/class/firmware/dell_rbu/loading
74 2) cp bios_image.hdr /sys/class/firmware/dell_rbu/data
75 3) echo 0 > /sys/class/firmware/dell_rbu/loading
77 The /sys/class/firmware/dell_rbu/ entries will remain till the following is
79 echo -1 > /sys/class/firmware/dell_rbu/loading
85 it will make the /sys/class/firmware/dell_rbu/ entries disappear.
Defi-stub.txt5 as a PE/COFF image, thereby convincing EFI firmware loaders to load
7 along with the EFI-specific entry point that the firmware loader
13 between architectures is in drivers/firmware/efi/efi-stub-helper.c.
32 the extension the EFI firmware loader will refuse to execute it. It's
34 because EFI firmware doesn't have support for them. For ARM the
Dremoteproc.txt15 control (power on, load firmware, power off) those remote processors while
32 - Boot a remote processor (i.e. load its firmware, power it on, ...).
89 const char *firmware, int len)
93 the name of the firmware to boot this rproc with, and the
119 Note: this function initiates an asynchronous firmware loading
121 firmware.
184 At this point remoteproc only supports ELF32 firmware binaries. However,
192 When the firmware is parsed, its various segments are loaded to memory
213 * struct resource_table - firmware resource table header
235 * struct fw_rsc_hdr - firmware resource entry header
[all …]
/linux-4.4.14/drivers/scsi/qla2xxx/
DKconfig10 By default, firmware for the ISP parts will be loaded
25 Upon request, the driver caches the firmware image until
30 http://ldriver.qlogic.com/firmware/
32 They are also included in the linux-firmware tree as well.
/linux-4.4.14/Documentation/powerpc/
Dbootwrapper.txt6 a boot wrapper to make it usable by the system firmware. There is no
7 standard PowerPC firmware interface, so the boot wrapper is designed to
12 The different image types are used to support all of the various firmware
14 used firmware type on general purpose PowerPC systems from Apple, IBM and
16 are a handful of other firmware implementations which are also popular. Each
17 firmware interface requires a different image format.
43 inside the image instead of provided by firmware. The
50 data from the board firmware, but simpleImages do not
51 talk to the firmware at all.
53 Planet boards using the PlanetCore firmware. Board
[all …]
D00-INDEX18 firmware-assisted-dump.txt
19 - Documentation on the firmware assisted dump mechanism "fadump".
27 - describes the layout of firmware binaries for the Freescale QUICC
Dfirmware-assisted-dump.txt6 The goal of firmware-assisted dump is to enable the dump of
13 - Fadump uses the same firmware interfaces and memory reservation model
27 Comparing with kdump or other strategies, firmware-assisted
40 and assistance from the Power firmware. The procedure is
44 Power firmware for dump preservation during OS initialization.
48 -- When a system crashes, the Power firmware will save
64 firmware will reset PCI and other hardware state. It will
84 next firmware-assisted dump registration.
89 Please note that the firmware-assisted dump feature
91 firmware versions.
[all …]
/linux-4.4.14/sound/soc/codecs/
Dwm8994.h162 const struct firmware *cur_fw;
163 const struct firmware *mbc;
164 const struct firmware *mbc_vss;
165 const struct firmware *enh_eq;
Dwm_adsp.c1053 const struct firmware *firmware; in wm_adsp_load() local
1077 ret = request_firmware(&firmware, file, dsp->dev); in wm_adsp_load()
1085 if (pos >= firmware->size) { in wm_adsp_load()
1087 file, firmware->size); in wm_adsp_load()
1091 header = (void*)&firmware->data[0]; in wm_adsp_load()
1162 while (pos < firmware->size && in wm_adsp_load()
1163 pos - firmware->size > sizeof(*region)) { in wm_adsp_load()
1164 region = (void *)&(firmware->data[pos]); in wm_adsp_load()
1262 if (pos > firmware->size) in wm_adsp_load()
1264 file, regions, pos - firmware->size); in wm_adsp_load()
[all …]
/linux-4.4.14/arch/arm/boot/dts/
Dbcm2835-rpi.dtsi19 firmware: firmware { label
20 compatible = "raspberrypi,bcm2835-firmware";
Dexynos5410-smdk5410.dts33 firmware@02037000 {
34 compatible = "samsung,secure-firmware";
/linux-4.4.14/drivers/gpu/drm/amd/amdgpu/
Damdgpu_ucode.c200 int amdgpu_ucode_validate(const struct firmware *fw) in amdgpu_ucode_validate()
241 struct amdgpu_bo **bo = &adev->firmware.fw_buf; in amdgpu_ucode_init_bo()
249 err = amdgpu_bo_create(adev, adev->firmware.fw_size, PAGE_SIZE, true, in amdgpu_ucode_init_bo()
285 ucode = &adev->firmware.ucode[i]; in amdgpu_ucode_init_bo()
296 adev->firmware.smu_load = false; in amdgpu_ucode_init_bo()
307 ucode = &adev->firmware.ucode[i]; in amdgpu_ucode_fini_bo()
313 amdgpu_bo_unref(&adev->firmware.fw_buf); in amdgpu_ucode_fini_bo()
314 adev->firmware.fw_buf = NULL; in amdgpu_ucode_fini_bo()
Damdgpu_ucode.h158 const struct firmware *fw;
170 int amdgpu_ucode_validate(const struct firmware *fw);
/linux-4.4.14/Documentation/isdn/
DREADME.icn93 The D-channel protocol is configured by loading different firmware
116 The D-channel protocol is configured by loading different firmware
119 Loading the firmware into the card:
121 The firmware is supplied together with the isdn4k-utils package. It
122 can be found in the subdirectory icnctrl/firmware/
127 pc_1t_ca.bin - Image of firmware for german 1TR6 protocol.
128 pc_eu_ca.bin - Image if firmware for EDSS1 (Euro-ISDN) protocol.
130 Assuming you have installed the utility-package correctly, the firmware
139 To load a 4B-card, the same command is used, except a second firmware
142 -> After downloading firmware, the two LEDs at the back cover of the card
DREADME.pcbit10 The common versions of the pcbit board require a firmware that is
12 firmware you need "pcbitctl" available on the standard isdn4k-utils
20 allow you to load the firmware after a hard reset.
29 manufacturer believe to be caused by bugs in the firmware. The current
DREADME.act200070 option of the "actctrl"-utility after loading the firmware into the
85 version as to the kernel-builtin one. (i.e. loading of firmware and
88 Loading the firmware into the card:
90 The firmware is supplied together with the isdn4k-utils package. It
91 can be found in the subdirectory act2000/firmware/
93 Assuming you have installed the utility-package correctly, the firmware
DREADME.avmb111 t4-files can be found at ftp://ftp.avm.de/cardware/b1/linux/firmware
24 You need at least /dev/capi20 to load the firmware.
37 To use the card you need the t4-files to download the firmware.
51 and load the firmware with
57 and load the firmware by calling
63 and load the firmware by calling
71 Init card and load firmware.
/linux-4.4.14/drivers/net/wireless/iwlwifi/
DKconfig30 In order to use this driver, you will need a firmware
35 The firmware is typically installed in /lib/firmware. You can
36 look in the hotplug script /etc/hotplug/firmware.agent to
58 This is the driver that supports the DVM firmware. The list
59 of the devices that use this firmware is available here:
60 https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi#firmware
66 This is the driver that supports the MVM firmware. The list
67 of the devices that use this firmware is available here:
68 https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi#firmware
/linux-4.4.14/Documentation/devicetree/bindings/mailbox/
Dbrcm,bcm2835-mbox.txt22 firmware: firmware {
23 compatible = "raspberrypi,firmware";
/linux-4.4.14/Documentation/devicetree/bindings/arm/samsung/
Dsamsung-boards.txt62 - firmware node, specifying presence and type of secure firmware:
63 - compatible: only "samsung,secure-firmware" is currently supported
64 - reg: address of non-secure SYSRAM used for communication with firmware
66 firmware@0203F000 {
67 compatible = "samsung,secure-firmware";
/linux-4.4.14/drivers/net/wireless/cw1200/
Dfwio.c62 const struct firmware *firmware = NULL; in cw1200_load_firmware_cw1200() local
148 ret = request_firmware(&firmware, fw_path, priv->pdev); in cw1200_load_firmware_cw1200()
176 num_blocks = (firmware->size - 1) / DOWNLOAD_BLOCK_SIZE + 1; in cw1200_load_firmware_cw1200()
179 val32 = firmware->size; /* Explicit cast from size_t to u32 */ in cw1200_load_firmware_cw1200()
211 tx_size = block_size = min_t(size_t, firmware->size - put, in cw1200_load_firmware_cw1200()
214 memcpy(buf, &firmware->data[put], block_size); in cw1200_load_firmware_cw1200()
256 release_firmware(firmware); in cw1200_load_firmware_cw1200()
/linux-4.4.14/drivers/firmware/
DKconfig52 bool "Add firmware-provided memory map to sysfs" if EXPERT
55 Add the firmware-provided (unmodified) memory map to /sys/firmware/memmap.
59 See also Documentation/ABI/testing/sysfs-firmware-memmap.
66 If your firmware supplies the PCDP table, and you want to
70 If your firmware supplies the HCDP table, and you want to
130 under /sys/firmware/dmi when this option is enabled and
161 This option enables support for communicating with the firmware on the
176 source "drivers/firmware/broadcom/Kconfig"
177 source "drivers/firmware/google/Kconfig"
178 source "drivers/firmware/efi/Kconfig"
/linux-4.4.14/sound/drivers/vx/
Dvx_hwdep.c70 const struct firmware *fw; in snd_vx_setup_firmware()
86 chip->firmware[i] = fw; in snd_vx_setup_firmware()
116 release_firmware(chip->firmware[i]); in snd_vx_free_firmware()
/linux-4.4.14/Documentation/devicetree/bindings/net/nfc/
Dpn544.txt10 - firmware-gpios: Output GPIO pin used to enter firmware download mode
33 firmware-gpios = <&gpio3 19 GPIO_ACTIVE_HIGH>;
Dnxp-nci.txt10 - firmware-gpios: Output GPIO pin used to enter firmware download mode
33 firmware-gpios = <&gpio0 31 GPIO_ACTIVE_HIGH>;
/linux-4.4.14/drivers/fmc/
Dfmc-write-eeprom.c32 static int fwe_run_tlv(struct fmc_device *fmc, const struct firmware *fw, in fwe_run_tlv()
68 static int fwe_run_bin(struct fmc_device *fmc, const struct firmware *fw) in fwe_run_bin()
82 static int fwe_run(struct fmc_device *fmc, const struct firmware *fw, char *s) in fwe_run()
109 const struct firmware *fw; in fwe_probe()
/linux-4.4.14/drivers/net/wireless/p54/
DKconfig11 These devices require softmac firmware which can be found at
23 These devices require softmac firmware which can be found at
35 supported by the fullmac driver/firmware.
37 This driver requires softmac firmware which can be found at
61 file is put at the right place. (usually /lib/firmware.)
Dp54spi.h122 const struct firmware *firmware; member
Dp54pci.h97 const struct firmware *firmware; member
Dp54spi.c171 ret = request_firmware(&priv->firmware, "3826.arm", &priv->spi->dev); in p54spi_request_firmware()
178 ret = p54_parse_firmware(dev, priv->firmware); in p54spi_request_firmware()
180 release_firmware(priv->firmware); in p54spi_request_firmware()
190 const struct firmware *eeprom; in p54spi_request_eeprom()
222 fw_len = priv->firmware->size; in p54spi_upload_firmware()
223 fw = kmemdup(priv->firmware->data, fw_len, GFP_KERNEL); in p54spi_upload_firmware()
695 release_firmware(priv->firmware); in p54spi_remove()
/linux-4.4.14/drivers/net/wireless/mwifiex/
Dsdio.h241 const char *firmware; member
274 const char *firmware; member
474 .firmware = SD8786_DEFAULT_FW_NAME,
489 .firmware = SD8787_DEFAULT_FW_NAME,
504 .firmware = SD8797_DEFAULT_FW_NAME,
519 .firmware = SD8897_DEFAULT_FW_NAME,
534 .firmware = SD8997_DEFAULT_FW_NAME,
550 .firmware = SD8887_DEFAULT_FW_NAME,
565 .firmware = SD8801_DEFAULT_FW_NAME,
Dpcie.h237 const char *firmware; member
246 .firmware = PCIE8766_DEFAULT_FW_NAME,
255 .firmware = PCIE8897_DEFAULT_FW_NAME,
264 .firmware = PCIE8997_DEFAULT_FW_NAME,
/linux-4.4.14/drivers/firmware/google/
DKconfig6 These firmware drivers are used by Google's servers. They are
27 This option enables the kernel to search for a firmware log in
29 userland in the file /sys/firmware/log.
/linux-4.4.14/drivers/net/wireless/hostap/
DKconfig36 bool "Support downloading firmware images with Host AP driver"
39 Configure Host AP driver to include support for firmware image
42 support cards that don't have firmware in flash, such as D-Link
49 bool "Support for non-volatile firmware download"
52 Allow Host AP driver to write firmware images to the non-volatile
54 Enable this option if you want to be able to change card firmware
/linux-4.4.14/Documentation/sound/alsa/
DMIXART.txt75 [As of 2.6.11, the firmware can be loaded automatically with hotplug
79 For loading the firmware automatically after the module is loaded, use a
88 The firmware binaries are installed on /usr/share/alsa/firmware
89 (or /usr/local/share/alsa/firmware, depending to the prefix option of
93 The firmware files are copyright by Digigram SA
/linux-4.4.14/Documentation/spi/
Dbutterfly6 firmware for user interfacing and/or sensors. A Butterfly is a $US20
9 develop firmware for this, and flash it using this adapter cable.
26 need to reflash the firmware, and the pins are the standard Atmel "ISP"
40 (a) flash new firmware that disables SPI (set PRR.2, and disable pullups
50 Or you could flash firmware making the AVR into an SPI slave (keeping the
55 That would let you talk to the AVR using custom SPI-with-USI firmware,
/linux-4.4.14/include/misc/
Daltera.h38 extern int altera_init(struct altera_config *config, const struct firmware *fw);
42 const struct firmware *fw) in altera_init()
/linux-4.4.14/include/sound/
Dvx_core.h30 struct firmware;
103 int (*load_dsp)(struct vx_core *chip, int idx, const struct firmware *fw);
202 const struct firmware *firmware[4]; /* loaded firmware data */ member
212 int snd_vx_load_boot_image(struct vx_core *chip, const struct firmware *dsp);
213 int snd_vx_dsp_boot(struct vx_core *chip, const struct firmware *dsp);
214 int snd_vx_dsp_load(struct vx_core *chip, const struct firmware *dsp);
Dsoc-topology.h21 struct firmware;
167 struct snd_soc_tplg_ops *ops, const struct firmware *fw,
/linux-4.4.14/Documentation/cpu-freq/
Dpcc-cpufreq.txt47 firmware and OSPM. It is a mechanism for coordinating processor
48 performance (ie: frequency) between the platform firmware and the OS.
53 OS utilizes the PCC interface to inform platform firmware what frequency the
54 OS wants for a logical processor. The platform firmware attempts to achieve
56 satisfied by platform firmware, then it usually means that power budget
65 between the OS and platform firmware. PCC also implements a "doorbell" that
66 is used by the OS to inform the platform firmware that a command has been
90 communicates the request to the platform firmware. The platform firmware is
108 This command is used by the OSPM to communicate to the platform firmware the
115 The PCC driver will load on any system where the platform firmware:
[all …]
/linux-4.4.14/arch/mips/netlogic/
DKconfig10 This DTB will be used if the firmware does not pass in a DTB
20 This DTB will be used if the firmware does not pass in a DTB
30 This DTB will be used if the firmware does not pass in a DTB
40 This DTB will be used if the firmware does not pass in a DTB
49 This DTB will be used if the firmware does not pass in a DTB
/linux-4.4.14/drivers/misc/altera-stapl/
DKconfig1 comment "Altera FPGA firmware download module"
4 tristate "Altera FPGA firmware download module"
/linux-4.4.14/Documentation/filesystems/
Defivarfs.txt16 mount -t efivarfs none /sys/firmware/efi/efivars
18 Due to the presence of numerous firmware bugs where removing non-standard
19 UEFI variables causes the system firmware to fail to POST, efivarfs
/linux-4.4.14/Documentation/acpi/
Dinitrd_table_override.txt55 # They must be put into a /kernel/firmware/acpi directory inside the
60 mkdir -p kernel/firmware/acpi
61 cp dsdt.aml kernel/firmware/acpi
66 cp facp.aml kernel/firmware/acpi
67 cp ssdt1.aml kernel/firmware/acpi
94 /sys/firmware/acpi/tables
/linux-4.4.14/drivers/net/wireless/brcm80211/brcmfmac/
Dfirmware.h38 const struct firmware *fw,
44 const struct firmware *fw,
Dfirmware.c417 const struct firmware *code;
421 void (*done)(struct device *dev, const struct firmware *fw,
425 static void brcmf_fw_request_nvram_done(const struct firmware *fw, void *ctx) in brcmf_fw_request_nvram_done()
468 static void brcmf_fw_request_code_done(const struct firmware *fw, void *ctx) in brcmf_fw_request_code_done()
503 const struct firmware *fw, in brcmf_fw_get_firmwares_pcie()
536 const struct firmware *fw, in brcmf_fw_get_firmwares()
/linux-4.4.14/Documentation/devicetree/bindings/dma/
Dbrcm,bcm2835-dma.txt5 Some arbitrary channels are used by the firmware
6 (1,3,6,7 in the current firmware version).
18 not used by the firmware in ascending order,
Dfsl-imx-sdma.txt13 firmware.
20 scripts firmware
49 22 SSI Dual FIFO (needs firmware ver >= 2)
/linux-4.4.14/Documentation/serial/
DREADME.cycladesZ2 The Cyclades-Z must have firmware loaded onto the card before it will
5 The firmware, loader program and the latest device driver code are
/linux-4.4.14/drivers/input/mouse/
Dcyapa.h254 int (*check_fw)(struct cyapa *, const struct firmware *);
257 int (*bl_initiate)(struct cyapa *, const struct firmware *);
258 int (*update_fw)(struct cyapa *, const struct firmware *);
413 int cyapa_pip_check_fw(struct cyapa *cyapa, const struct firmware *fw);
414 int cyapa_pip_bl_initiate(struct cyapa *cyapa, const struct firmware *fw);
415 int cyapa_pip_do_fw_update(struct cyapa *cyapa, const struct firmware *fw);
/linux-4.4.14/drivers/input/touchscreen/
Dili210x.c191 struct firmware_version firmware; in ili210x_i2c_probe() local
209 &firmware, sizeof(firmware)); in ili210x_i2c_probe()
287 client->irq, firmware.id, firmware.major, firmware.minor); in ili210x_i2c_probe()
/linux-4.4.14/Documentation/devicetree/bindings/arm/
Darm,scpi.txt12 All the channels reserved by remote SCP firmware for use by
32 All the clocks provided by SCP firmware via SCPI message
41 limits but only discrete points within the range. The firmware
43 index associated with it. The firmware also manages the
46 range within the specified range. The firmware provides the
85 ID) as used by the firmware. Refer to
186 temperature sensor provided by SCP firmware to setup a thermal
188 as used by the firmware.
/linux-4.4.14/drivers/isdn/hardware/mISDN/
Dspeedfax.c377 const struct firmware *firmware; in setup_instance() local
394 err = request_firmware(&firmware, "isdn/ISAR.BIN", &card->pdev->dev); in setup_instance()
402 card->name, firmware->size); in setup_instance()
428 err = card->isar.firmware(&card->isar, firmware->data, firmware->size); in setup_instance()
430 release_firmware(firmware); in setup_instance()
444 release_firmware(firmware); in setup_instance()
/linux-4.4.14/sound/firewire/oxfw/
Doxfw.c65 u32 firmware; in name_card() local
81 OXFORD_FIRMWARE_ID_ADDRESS, &firmware, 4, 0); in name_card()
84 be32_to_cpus(&firmware); in name_card()
103 v, m, firmware >> 20, firmware & 0xffff, in name_card()
/linux-4.4.14/drivers/media/platform/exynos4-is/
Dfimc-is.h145 const struct firmware *info;
175 const struct firmware *f_w;
214 const struct firmware *info;
253 struct firmware *f_w;
/linux-4.4.14/drivers/net/ethernet/sfc/
DKconfig22 (e.g. /dev/mtd1). This is required to update the firmware or
29 This exposes the on-board firmware-managed sensors as a
46 driver/firmware interaction. The tracing is actually enabled by
/linux-4.4.14/drivers/net/wireless/ath/carl9170/
DKconfig11 but it needs a special firmware (carl9170-1.fw) to do that.
13 The firmware can be downloaded from our wiki here:
28 Say Y, unless you need the LEDs for firmware debugging.
/linux-4.4.14/drivers/net/wireless/zd1211rw/
DKconfig9 Device firmware is required alongside this driver. You can download
10 the firmware distribution from http://sf.net/projects/zd1211/files/
/linux-4.4.14/drivers/nfc/nfcmrvl/
Dfw_dnld.h68 struct nfcmrvl_fw_binary_config firmware; member
74 const struct firmware *fw;
/linux-4.4.14/drivers/net/ethernet/brocade/bna/
Dcna_fwimg.c24 const struct firmware *bfi_fw;
32 const struct firmware *fw; in cna_read_firmware()
/linux-4.4.14/drivers/media/dvb-frontends/
DKconfig282 This driver needs external firmware. Please use the command
284 download/extract it, and then copy it to /usr/lib/hotplug/firmware
285 or /lib/firmware (depending on configuration of firmware hotplug).
294 This driver needs external firmware. Please use the command
296 download/extract it, and then copy it to /usr/lib/hotplug/firmware
297 or /lib/firmware (depending on configuration of firmware hotplug).
345 This driver needs external firmware. Please use the commands
348 download/extract them, and then copy them to /usr/lib/hotplug/firmware
349 or /lib/firmware (depending on configuration of firmware hotplug).
540 This driver needs external firmware. Please use the commands
[all …]
/linux-4.4.14/drivers/media/pci/cx18/
DMakefile1 cx18-objs := cx18-driver.o cx18-cards.o cx18-i2c.o cx18-firmware.o cx18-gpio.o \
4 cx18-av-core.o cx18-av-audio.o cx18-av-firmware.o cx18-av-vbi.o cx18-scb.o \
/linux-4.4.14/drivers/media/pci/ttpci/
DKconfig26 This driver needs an external firmware. Please use the script
28 download/extract it, and then copy it to /usr/lib/hotplug/firmware
29 or /lib/firmware (depending on configuration of firmware hotplug).
43 The AV7110 firmware provides some code to generate an OnScreenDisplay
150 required to have loaded firmware to tune properly.
/linux-4.4.14/drivers/staging/wilc1000/
Dlinux_wlan.c526 const struct firmware *wilc_firmware; in linux_wlan_get_firmware()
527 char *firmware; in linux_wlan_get_firmware() local
530 firmware = AP_FIRMWARE; in linux_wlan_get_firmware()
532 firmware = STA_FIRMWARE; in linux_wlan_get_firmware()
536 firmware = P2P_CONCURRENCY_FIRMWARE; in linux_wlan_get_firmware()
553 if (request_firmware(&wilc_firmware, firmware, &g_linux_wlan->wilc_sdio_func->dev) != 0) { in linux_wlan_get_firmware()
554 PRINT_ER("%s - firmare not available\n", firmware); in linux_wlan_get_firmware()
559 if (request_firmware(&wilc_firmware, firmware, &g_linux_wlan->wilc_spidev->dev) != 0) { in linux_wlan_get_firmware()
560 PRINT_ER("%s - firmare not available\n", firmware); in linux_wlan_get_firmware()
565 g_linux_wlan->firmware = wilc_firmware; in linux_wlan_get_firmware()
[all …]
/linux-4.4.14/scripts/
DMakefile.fwinst31 firmware-dirs := $(sort $(addprefix $(objtree)/$(obj)/,$(dir $(fw-external-y) $(fw-shipped-all))))
33 _dummy := $(foreach d,$(firmware-dirs), $(shell [ -d $(d) ] || mkdir -p $(d)))
/linux-4.4.14/drivers/net/wireless/iwlegacy/
DKconfig27 The microcode is typically installed in /lib/firmware. You can
28 look in the hotplug script /etc/hotplug/firmware.agent to
53 The microcode is typically installed in /lib/firmware. You can
54 look in the hotplug script /etc/hotplug/firmware.agent to
/linux-4.4.14/Documentation/devicetree/bindings/soc/ti/
Dkeystone-navigator-qmss.txt58 QMSS can be loaded with the accumulator firmware. The
59 accumulator firmware’s job is to poll a select number of
65 the buffer for descriptor information. This firmware
70 pdsp-id : QMSS PDSP running accumulator firmware
97 -- firmware : firmware to be loaded on the PDSP.
98 -- id : the qmss pdsp that will run the firmware.
/linux-4.4.14/drivers/gpu/drm/sti/
Dsti_hqvdp.c659 const struct firmware *firmware; in sti_hqvdp_start_xp70() local
678 if (request_firmware(&firmware, HQVDP_FMW_NAME, hqvdp->dev)) { in sti_hqvdp_start_xp70()
684 if (!firmware) { in sti_hqvdp_start_xp70()
689 header = (struct fw_header *)firmware->data; in sti_hqvdp_start_xp70()
690 if (firmware->size < sizeof(*header)) { in sti_hqvdp_start_xp70()
691 DRM_ERROR("Invalid firmware size (%d)\n", firmware->size); in sti_hqvdp_start_xp70()
695 header->pmem_size + header->dmem_size) != firmware->size) { in sti_hqvdp_start_xp70()
699 firmware->size); in sti_hqvdp_start_xp70()
703 data = (u8 *)firmware->data; in sti_hqvdp_start_xp70()
775 release_firmware(firmware); in sti_hqvdp_start_xp70()
/linux-4.4.14/drivers/net/wireless/brcm80211/brcmsmac/
Dmac80211_if.h58 const struct firmware *fw_bin[MAX_FW_IMAGES];
59 const struct firmware *fw_hdr[MAX_FW_IMAGES];
/linux-4.4.14/sound/pci/riptide/
Driptide.c423 struct riptide_firmware firmware; member
432 const struct firmware *fw_entry;
459 union firmware_version firmware; member
656 .firmware = {
1186 union firmware_version firmware = { .ret = CMDRET_ZERO }; in try_to_load_firmware() local
1216 SEND_GETV(cif, &firmware.ret); in try_to_load_firmware()
1218 firmware.firmware.ASIC, firmware.firmware.CODEC, in try_to_load_firmware()
1219 firmware.firmware.AUXDSP, firmware.firmware.PROG); in try_to_load_firmware()
1225 if (!memcmp(&firmware_versions[i], &firmware, sizeof(firmware))) in try_to_load_firmware()
1247 chip->firmware = firmware; in try_to_load_firmware()
[all …]
/linux-4.4.14/Documentation/devicetree/bindings/pci/
Dpci.txt4 http://www.firmware.org/1275/bindings/pci/pci2_1.pdf
9 http://www.firmware.org/1275/practice/imap/imap0_9d.pdf
/linux-4.4.14/drivers/net/wireless/prism54/
Dislpci_dev.c90 const struct firmware *fw_entry = NULL; in isl_upload_firmware()
94 rc = request_firmware(&fw_entry, priv->firmware, PRISM_FW_PDEV); in isl_upload_firmware()
98 "prism54", priv->firmware); in isl_upload_firmware()
110 "prism54", priv->firmware); in isl_upload_firmware()
473 priv->ndev->name, priv->firmware); in islpci_upload_fw()
893 strcpy(priv->firmware, ISL3877_IMAGE_FILE); in islpci_setup()
897 strcpy(priv->firmware, ISL3886_IMAGE_FILE); in islpci_setup()
901 strcpy(priv->firmware, ISL3890_IMAGE_FILE); in islpci_setup()
/linux-4.4.14/drivers/misc/mic/host/
Dmic_x100.c352 mic_x100_load_command_line(struct mic_device *mdev, const struct firmware *fw) in mic_x100_load_command_line()
384 const struct firmware *fw; in mic_x100_load_ramdisk()
449 const struct firmware *fw; in mic_x100_load_firmware()
455 rc = request_firmware(&fw, mdev->cosm_dev->firmware, &mdev->pdev->dev); in mic_x100_load_firmware()
459 rc, mdev->cosm_dev->firmware); in mic_x100_load_firmware()
/linux-4.4.14/drivers/staging/rtl8712/
Dhal_init.c44 static void rtl871x_load_fw_cb(const struct firmware *firmware, void *context) in rtl871x_load_fw_cb() argument
49 if (!firmware) { in rtl871x_load_fw_cb()
58 padapter->fw = firmware; in rtl871x_load_fw_cb()
82 const struct firmware **praw = &padapter->fw; in rtl871x_open_fw()
/linux-4.4.14/Documentation/devicetree/bindings/display/
Dsimple-framebuffer.txt3 A simple frame-buffer describes a frame-buffer setup by firmware or
29 nodes, so that the firmware only needs to update the mode information and
31 added, the simplefb nodes will already contain this info and the firmware
34 If pre-filled framebuffer nodes are used, the firmware may need extra
/linux-4.4.14/drivers/net/wireless/ath/ath10k/
Dcore.h675 const struct firmware *board;
679 const struct firmware *otp;
683 const struct firmware *firmware; member
687 const struct firmware *cal_file;
830 const struct firmware *utf;
Dcore.c326 static const struct firmware *ath10k_fetch_fw_file(struct ath10k *ar, in ath10k_fetch_fw_file()
331 const struct firmware *fw; in ath10k_fetch_fw_file()
669 if (!IS_ERR(ar->firmware)) in ath10k_core_free_firmware_files()
670 release_firmware(ar->firmware); in ath10k_core_free_firmware_files()
681 ar->firmware = NULL; in ath10k_core_free_firmware_files()
964 ar->firmware = ath10k_fetch_fw_file(ar, in ath10k_core_fetch_firmware_api_1()
967 if (IS_ERR(ar->firmware)) { in ath10k_core_fetch_firmware_api_1()
968 ret = PTR_ERR(ar->firmware); in ath10k_core_fetch_firmware_api_1()
973 ar->firmware_data = ar->firmware->data; in ath10k_core_fetch_firmware_api_1()
974 ar->firmware_len = ar->firmware->size; in ath10k_core_fetch_firmware_api_1()
[all …]
/linux-4.4.14/drivers/media/pci/cx23885/
Dcx23885-417.c900 const struct firmware *firmware; in cx23885_load_firmware() local
931 retval = request_firmware(&firmware, CX23885_FIRM_IMAGE_NAME, in cx23885_load_firmware()
943 if (firmware->size != CX23885_FIRM_IMAGE_SIZE) { in cx23885_load_firmware()
946 firmware->size, CX23885_FIRM_IMAGE_SIZE); in cx23885_load_firmware()
947 release_firmware(firmware); in cx23885_load_firmware()
951 if (0 != memcmp(firmware->data, magic, 8)) { in cx23885_load_firmware()
954 release_firmware(firmware); in cx23885_load_firmware()
960 dataptr = (u32 *)firmware->data; in cx23885_load_firmware()
961 for (i = 0; i < (firmware->size >> 2); i++) { in cx23885_load_firmware()
966 release_firmware(firmware); in cx23885_load_firmware()
[all …]
/linux-4.4.14/drivers/tc/
Dtc.c96 tdev->firmware[i] = in tc_bus_add_devices()
103 tdev->firmware[8] = 0; in tc_bus_add_devices()
108 tdev->name, tdev->firmware); in tc_bus_add_devices()
/linux-4.4.14/drivers/usb/atm/
DKconfig26 two parts of the firmware, extracted by the user space tools; see
38 install the firmware, extracted by the user space tools; see
63 the modem using a user space utility (a firmware loader for example).
/linux-4.4.14/Documentation/wimax/
DREADME.i2400m62 3. Installing the firmware
64 The firmware can be obtained from http://linuxwimax.org or might have
69 $ cp FIRMWAREFILE.sbcf /lib/firmware/i2400m-fw-BUSTYPE-1.3.sbcf
71 * NOTE: if your firmware came in an .rpm or .deb file, just install
75 Each hardware type comes with its own firmware and will not work
108 plugged in). The driver will enumerate the device, upload the firmware
113 i2400m_usb 5-4:1.0: firmware interface version 8.0.0
258 This means that the driver cannot locate the firmware file named
259 /lib/firmware/i2400m-fw-usb-1.2.sbcf. Check that the file is present in
/linux-4.4.14/drivers/media/tuners/
Dxc5000.c75 const struct firmware *firmware; member
634 const struct firmware *fw) in xc5000_fwupload()
1134 const struct firmware *fw; in xc_load_fw_and_init_tuner()
1144 if (!priv->firmware) { in xc_load_fw_and_init_tuner()
1158 priv->firmware = fw; in xc_load_fw_and_init_tuner()
1160 fw = priv->firmware; in xc_load_fw_and_init_tuner()
1307 if (!priv->firmware) in xc5000_resume()
1339 if (priv->firmware) { in xc5000_release()
1340 release_firmware(priv->firmware); in xc5000_release()
1341 priv->firmware = NULL; in xc5000_release()
/linux-4.4.14/Documentation/devicetree/bindings/i2c/
Di2c-opal.txt4 Most of the device node and properties layout is specific to the firmware and
5 used by the firmware itself for configuring the port. From the linux
/linux-4.4.14/Documentation/nfc/
Dnfc-pn544.txt16 In the normal (HCI) mode and in the firmware update mode read and
21 HCI specification. The firmware is updated using a specific protocol,
/linux-4.4.14/drivers/net/wireless/b43legacy/
Db43legacy.h643 const struct firmware *ucode;
645 const struct firmware *pcm;
647 const struct firmware *initvals;
649 const struct firmware *initvals_band;
737 const struct firmware *fwp; /* needed to pass fw pointer */
/linux-4.4.14/drivers/net/can/softing/
DKconfig25 You need firmware for these, which you can get at
28 firmware version 4.6 (softing-fw-4.6-binaries.tar.gz)
/linux-4.4.14/drivers/media/common/
Dcypress_firmware.c40 static int cypress_get_hexline(const struct firmware *fw, in cypress_get_hexline()
72 const struct firmware *fw, int type) in cypress_load_firmware()
/linux-4.4.14/drivers/staging/fsl-mc/
DTODO19 * MC firmware uprev. The MC firmware upon which the fsl-mc

123456