Searched full:firmware (Results 1 – 25 of 438) sorted by relevance
12345678910>>...18
| /Documentation/driver-api/firmware/ |
| D | firmware_cache.rst | 2 Firmware cache
5 When Linux resumes from suspend some device drivers require firmware lookups to
7 firmware lookups are not possible, during this short period of time firmware
9 the root filesystem for firmware delays user experience with device
10 functionality. In order to support these requirements the firmware
11 infrastructure implements a firmware cache for device drivers for most API
14 The firmware cache makes using certain firmware API calls safe during a device
16 the firmware by themselves for dealing with firmware loss during system resume.
18 The firmware cache works by requesting for firmware prior to suspend and
19 caching it in memory. Upon resume device drivers using the firmware API will
[all …]
|
| D | built-in-fw.rst | 2 Built-in firmware
5 Firmware can be built-in to the kernel, this means building the firmware
6 into vmlinux directly, to enable avoiding having to look for firmware from
7 the filesystem. Instead, firmware can be looked for inside the kernel
8 directly. You can enable built-in firmware using the kernel configuration
14 There are a few reasons why you might want to consider building your firmware
18 * Firmware is needed for accessing the boot device, and the user doesn't
19 want to stuff the firmware into the boot initramfs.
22 able to make use of built-in firmware:
24 * Legalese - firmware is non-GPL compatible
[all …]
|
| D | fallback-mechanisms.rst | 6 filesystem lookup on the root filesystem or when the firmware simply cannot be
8 configuration options related to supporting the firmware fallback mechanism are:
10 * CONFIG_FW_LOADER_USER_HELPER: enables building the firmware fallback
15 enable the kobject uevent fallback mechanism on all firmware API calls
21 manually load the firmware. Read below for more details.
31 Justifying the firmware fallback mechanism
40 * Races upon resume from suspend. This is resolved by the firmware cache, but
41 the firmware cache is only supported if you use uevents, and its not
44 * Firmware is not accessible through typical means:
46 * The firmware provides very unique device specific data tailored for
[all …]
|
| D | lookup-order.rst | 2 Firmware lookup order
5 Different functionality is available to enable firmware to be found.
6 Below is chronological order of how firmware will be looked for once
7 a driver issues a firmware API call.
9 * The ''Built-in firmware'' is checked first, if the firmware is present we
11 * The ''Firmware cache'' is looked at next. If the firmware is found we
15 * If no firmware has been found and the fallback mechanism was enabled
17 is issued or the custom firmware loading is relied upon for firmware
|
| D | request_firmware.rst | 5 You would typically load firmware and then load it into your device somehow.
6 The typical firmware work flow is reflected below::
8 if(request_firmware(&fw_entry, $FIRMWARE, device) == 0)
12 Synchronous firmware requests
15 Synchronous firmware requests will wait until the firmware is found or until
38 Asynchronous firmware requests
41 Asynchronous firmware requests allow driver code to not have to wait
42 until the firmware or an error is returned. Function callbacks are
43 provided so that when the firmware or an error is found the driver is
55 Some devices have an optimization in place to enable the firmware to be
[all …]
|
| D | direct-fs-lookup.rst | 5 Direct filesystem lookup is the most common form of firmware lookup performed
6 by the kernel. The kernel looks for the firmware directly on the root
7 filesystem in the paths documented in the section 'Firmware search paths'.
12 It is recommended you keep /lib/firmware paths on your root filesystem,
17 Firmware and initramfs
20 Drivers which are built-in to the kernel should have the firmware integrated
23 available. Stuffing the firmware into initramfs resolves this race issue,
26 There are circumstances that justify not wanting to include firmware into
27 initramfs, such as dealing with large firmware firmware files for the
|
| D | fw_search_path.rst | 2 Firmware search paths
5 The following search paths are used to look for firmware on your
9 * /lib/firmware/updates/UTS_RELEASE/
10 * /lib/firmware/updates/
11 * /lib/firmware/UTS_RELEASE/
12 * /lib/firmware/
25 You would echo into it your custom path and firmware requested will be
|
| D | other_interfaces.rst | 1 Other Firmware Interfaces
7 .. kernel-doc:: drivers/firmware/dmi_scan.c
13 .. kernel-doc:: drivers/firmware/edd.c
29 .. kernel-doc:: include/linux/firmware/intel/stratix10-svc-client.h
32 .. kernel-doc:: include/linux/firmware/intel/stratix10-svc-client.h
35 .. kernel-doc:: include/linux/firmware/intel/stratix10-svc-client.h
38 .. kernel-doc:: include/linux/firmware/intel/stratix10-svc-client.h
41 .. kernel-doc:: include/linux/firmware/intel/stratix10-svc-client.h
44 .. kernel-doc:: drivers/firmware/stratix10-svc.c
|
| /Documentation/networking/device_drivers/netronome/ |
| D | nfp.rst | 13 - `Acquiring Firmware`_
24 Acquiring Firmware
27 The NFP4000 and NFP6000 devices require application specific firmware
28 to function. Application firmware can be located either on the host file system
29 or in the device flash (if supported by management firmware).
31 Firmware files on the host filesystem contain card type (`AMDA-*` string), media
32 config etc. They should be placed in `/lib/firmware/netronome` directory to
33 load firmware from the host file system.
35 Firmware for basic NIC operation is available in the upstream
36 `linux-firmware.git` repository.
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-firmware-efi-esrt | 1 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 …]
|
| D | sysfs-firmware-gsmi | 1 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 …]
|
| D | sysfs-firmware-memmap | 1 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 …]
|
| D | sysfs-ibft | 1 What: /sys/firmware/ibft/initiator
4 Description: The /sys/firmware/ibft/initiator directory will contain
5 files that expose the iSCSI Boot Firmware Table initiator data.
8 What: /sys/firmware/ibft/targetX
11 Description: The /sys/firmware/ibft/targetX directory will contain
12 files that expose the iSCSI Boot Firmware Table target data.
18 What: /sys/firmware/ibft/ethernetX
21 Description: The /sys/firmware/ibft/ethernetX directory will contain
22 files that expose the iSCSI Boot Firmware Table NIC data.
25 What: /sys/firmware/ibft/acpi_header
[all …]
|
| D | sysfs-firmware-dmi-entries | 1 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 …]
|
| /Documentation/devicetree/bindings/soc/fsl/cpm_qe/qe/ |
| D | firmware.txt | 1 * 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 {
|
| /Documentation/devicetree/bindings/firmware/xilinx/ |
| D | xlnx,zynqmp-firmware.txt | 2 Device Tree Bindings for the Xilinx Zynq MPSoC Firmware Interface
5 The zynqmp-firmware node describes the interface to platform firmware.
6 ZynqMP has an interface to communicate with secure firmware. Firmware
7 driver provides an interface to firmware APIs. Interface APIs can be
14 - compatible: Must contain: "xlnx,zynqmp-firmware"
15 - method: The method of calling the PM-API firmware layer.
24 firmware {
25 zynqmp_firmware: zynqmp-firmware {
26 compatible = "xlnx,zynqmp-firmware";
|
| /Documentation/devicetree/bindings/soc/fsl/cpm_qe/ |
| D | qe.txt | 26 - fsl,firmware-phandle:
27 Usage: required only if there is no fsl,qe-firmware child node
29 Definition: Points to a firmware node (see "QE Firmware Node" below)
30 that contains the firmware that should be uploaded for this QE.
31 The compatible property for the firmware node should say,
32 "fsl,qe-firmware".
135 * QE Firmware Node
137 This node defines a firmware binary that is embedded in the device tree, for
138 the purpose of passing the firmware from bootloader to the kernel, or from
141 The firmware node itself contains the firmware binary contents, a compatible
[all …]
|
| /Documentation/networking/ |
| D | fore200e.txt | 20 Firmware Copyright Notice
27 Firmware Updates
30 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
[all …]
|
| /Documentation/devicetree/bindings/input/touchscreen/ |
| D | raspberrypi,firmware-ts.txt | 1 Raspberry Pi firmware based 7" touchscreen
5 - compatible: "raspberrypi,firmware-ts"
8 - firmware: Reference to RPi's firmware device node
17 firmware: firmware-rpi {
18 compatible = "raspberrypi,bcm2835-firmware";
22 compatible = "raspberrypi,firmware-ts";
|
| /Documentation/devicetree/bindings/gpio/ |
| D | raspberrypi,firmware-gpio.txt | 3 The Raspberry Pi 3 GPIO expander is controlled by the VC4 firmware. The
4 firmware exposes a mailbox interface that allows the ARM core to control the
8 firmware node.
12 - compatible : Should be "raspberrypi,firmware-gpio"
21 firmware: firmware-rpi {
22 compatible = "raspberrypi,bcm2835-firmware";
26 compatible = "raspberrypi,firmware-gpio";
|
| /Documentation/leds/ |
| D | leds-lp55xx.rst | 58 ( Firmware Interface )
66 LP55xx common driver supports the firmware interface.
82 Start program which is loaded via the firmware interface
83 firmware:
93 echo 1 > /sys/class/firmware/lp5521/loading
94 echo "4000600040FF6000" > /sys/class/firmware/lp5521/data
95 echo 0 > /sys/class/firmware/lp5521/loading
103 echo 1 > /sys/class/firmware/lp55231/loading
104 echo "9d0740ff7e0040007e00a0010000" > /sys/class/firmware/lp55231/data
105 echo 0 > /sys/class/firmware/lp55231/loading
[all …]
|
| /Documentation/media/dvb-drivers/ |
| D | ttusb-dec.rst | 18 - Hotplug firmware loader
27 Getting the Firmware
29 To download the firmware, use the following commands:
38 Hotplug Firmware Loading
41 Since 2.6 kernels, the firmware is loaded at the point that the driver module
44 Copy the three files downloaded above into the /usr/lib/hotplug/firmware or
45 /lib/firmware directory (depending on configuration of firmware hotplug).
|
| /Documentation/arm/keystone/ |
| D | knav-qmss.rst | 31 Accumulator QMSS queues using PDSP firmware
33 The QMSS PDSP firmware support accumulator channel that can monitor a single
37 1 or 32 queues per channel. More description on the firmware is available in
42 k2_qmss_pdsp_acc48_k2_le_1_0_0_9.bin firmware supports upto 48 accumulator
43 channels. This firmware is available under ti-keystone folder of
44 firmware.git at
46 git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
48 To use copy the firmware image to lib/firmware folder of the initramfs or
52 "firmware file ks2_qmss_pdsp_acc48.bin downloaded for PDSP"
54 in the boot up log if loading of firmware to PDSP is successful.
[all …]
|
| /Documentation/arm/ |
| D | firmware.rst | 2 Interface for registering and calling firmware-specific operations for ARM
7 Some boards are running with secure firmware running in TrustZone secure
9 a need to provide an interface for such platforms to specify available firmware
12 Firmware operations can be specified by filling in a struct firmware_ops
19 and its members can be found in arch/arm/include/asm/firmware.h header.
22 set anything if platform does not require firmware operations.
24 To call a firmware operation, a helper macro is provided::
33 Example of registering firmware operations::
39 /* tell platformX firmware to enter idle */
45 /* tell platformX firmware to boot CPU i */
[all …]
|
| /Documentation/devicetree/bindings/arm/bcm/ |
| D | raspberrypi,bcm2835-firmware.txt | 1 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";
|
12345678910>>...18