| /f-stack/freebsd/contrib/device-tree/Bindings/firmware/xilinx/ |
| H A D | xlnx,zynqmp-firmware.txt | 5 The zynqmp-firmware node describes the interface to platform firmware.
7 driver provides an interface to firmware APIs. Interface APIs can be
15 "xlnx,zynqmp-firmware" for Zynq Ultrascale+ MPSoC
16 "xlnx,versal-firmware" for Versal
17 - method: The method of calling the PM-API firmware layer.
28 firmware {
29 zynqmp_firmware: zynqmp-firmware {
30 compatible = "xlnx,zynqmp-firmware";
38 firmware {
39 versal_firmware: versal-firmware {
[all …]
|
| /f-stack/freebsd/contrib/device-tree/Bindings/soc/fsl/cpm_qe/qe/ |
| H A 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 {
|
| /f-stack/freebsd/contrib/device-tree/Bindings/arm/bcm/ |
| H A D | raspberrypi,bcm2835-firmware.yaml | 4 $id: http://devicetree.org/schemas/arm/bcm/raspberrypi,bcm2835-firmware.yaml#
7 title: Raspberry Pi VideoCore firmware driver
17 const: raspberrypi,bcm2835-firmware
25 - const: raspberrypi,bcm2835-firmware
31 Phandle to the firmware device's Mailbox.
39 const: raspberrypi,firmware-clocks
45 firmware messages.
59 firmware {
60 compatible = "raspberrypi,bcm2835-firmware", "simple-mfd";
64 compatible = "raspberrypi,firmware-clocks";
|
| H A 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";
|
| /f-stack/freebsd/contrib/device-tree/Bindings/input/touchscreen/ |
| H A 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";
|
| /f-stack/freebsd/sys/ |
| H A D | firmware.h | 53 struct firmware { struct
60 const struct firmware *firmware_register(const char *, argument
61 const void *, size_t, unsigned int, const struct firmware *);
65 const struct firmware *firmware_get_flags(const char *, uint32_t flags);
66 const struct firmware *firmware_get(const char *);
69 void firmware_put(const struct firmware *, int);
|
| /f-stack/freebsd/contrib/device-tree/Bindings/gpio/ |
| H A 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";
|
| /f-stack/freebsd/contrib/device-tree/Bindings/soc/fsl/cpm_qe/ |
| H A D | qe.txt | 26 - fsl,firmware-phandle:
32 "fsl,qe-firmware".
141 The firmware node itself contains the firmware binary contents, a compatible
144 fsl,firmware-phandle property. Other QE nodes that need the same firmware
145 should define an fsl,firmware-phandle property that points to the firmware node
156 kind of firmware it is. For QE, this should be "fsl,qe-firmware".
158 - fsl,firmware
167 qe_firmware:qe-firmware {
168 compatible = "fsl,qe-firmware";
169 fsl,firmware = [0x70 0xcd 0x00 0x00 0x01 0x46 0x45 ...];
[all …]
|
| /f-stack/freebsd/contrib/device-tree/Bindings/arm/samsung/ |
| H A D | samsung-secure-firmware.yaml | 4 $id: http://devicetree.org/schemas/arm/samsung/samsung-secure-firmware.yaml#
15 - const: samsung,secure-firmware
19 Address of non-secure SYSRAM used for communication with firmware.
30 firmware@203f000 {
31 compatible = "samsung,secure-firmware";
|
| /f-stack/freebsd/contrib/device-tree/Bindings/nvmem/ |
| H A D | xlnx,zynqmp-nvmem.txt | 2 = Zynq UltraScale+ MPSoC nvmem firmware driver binding =
5 like soc revision, IDCODE... etc, By using the firmware interface.
17 firmware {
18 zynqmp_firmware: zynqmp-firmware {
19 compatible = "xlnx,zynqmp-firmware";
|
| /f-stack/freebsd/contrib/device-tree/src/arm/ |
| H A D | bcm2835-rpi.dtsi | 15 firmware: firmware { label
16 compatible = "raspberrypi,bcm2835-firmware", "simple-mfd";
26 firmware = <&firmware>;
|
| /f-stack/freebsd/contrib/device-tree/Bindings/arm/firmware/ |
| H A D | tlm,trusted-foundations.txt | 6 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 {
|
| H A D | sdei.txt | 6 firmware-first error handling, or from an IRQ that has been promoted to
7 a firmware-assisted NMI.
11 privilege level of the SDEI firmware (specified as part of the binding
24 The sdei node should be a child node of '/firmware' and have required
30 - method : The method of calling the SDEI firmware. Permitted
37 firmware {
|
| /f-stack/freebsd/contrib/device-tree/Bindings/power/reset/ |
| H A D | xlnx,zynqmp-power.txt | 33 firmware {
34 zynqmp_firmware: zynqmp-firmware {
35 compatible = "xlnx,zynqmp-firmware";
47 firmware {
48 zynqmp_firmware: zynqmp-firmware {
49 compatible = "xlnx,zynqmp-firmware";
|
| /f-stack/freebsd/contrib/device-tree/Bindings/firmware/ |
| H A D | cznic,turris-mox-rwtm.txt | 1 Turris Mox rWTM firmware driver
8 compatible device running the Mox's rWTM firmware in the secure processor (for
9 example it is possible to flash this firmware into EspressoBin).
13 firmware {
|
| /f-stack/freebsd/contrib/device-tree/Bindings/fpga/ |
| H A D | xlnx,zynqmp-pcap-fpga.txt | 3 Programmable Logic (PL). The configuration uses the firmware interface.
17 firmware {
18 zynqmp_firmware: zynqmp-firmware {
19 compatible = "xlnx,zynqmp-firmware";
|
| /f-stack/freebsd/contrib/device-tree/Bindings/soc/bcm/ |
| H A D | raspberrypi,bcm2835-power.txt | 6 - firmware: Reference to the RPi firmware device node.
39 firmware = <&firmware>;
|
| /f-stack/freebsd/contrib/device-tree/Bindings/net/ |
| H A D | qualcomm-bluetooth.txt | 23 - firmware-name: specify the name of nvm firmware to load
39 - firmware-name: specify the name of nvm firmware to load
53 firmware-name = "nvm_00440302.bin";
66 firmware-name = "crnv21.bin";
|
| /f-stack/freebsd/contrib/device-tree/Bindings/remoteproc/ |
| H A D | wkup_m3_rproc.txt | 6 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";
|
| /f-stack/dpdk/doc/guides/nics/ |
| H A D | nfp.rst | 26 with a specific NFP firmware application. Netronome's NSP ABI
31 **[email protected]** to obtain the latest available firmware.
50 NFP PMD, along with a specific NFP firmware application.
74 stopping a PF port. Since DPDK 18.05 the firmware upload happens when
77 Depending on the Netronome product installed in the system, firmware files
79 PF looks for a firmware file in this order:
81 1) First try to find a firmware image specific for this device using the
94 Netronome's software packages install firmware files under ``/lib/firmware/netronome``
97 directory per firmware application. Options 1 and 2 for firmware filenames allow
99 different firmware to each SmartNIC.
[all …]
|
| H A D | sfc_efx.rst | 69 - Transmit VLAN insertion (if running firmware variant supports it)
118 firmware, is that it allows for a single RSS context.
125 adapters with full-feature firmware variant running.
130 If adapter firmware advertises support for tunnels then the PMD
245 Validating flow rules depends on the firmware variant.
322 - Requires firmware version:
331 update firmware and configure the adapter.
371 which may be used on DPDK firmware variant only
401 **auto** allows NIC firmware to make a choice based on
416 Choose the preferred firmware variant to use.
[all …]
|
| /f-stack/freebsd/contrib/device-tree/Bindings/mtd/partitions/ |
| H A D | brcm,bcm963xx-imagetag.txt | 6 needs to be used with an explicit firmware partition.
8 The BCM963XX ImageTag is a simple firmware header describing the offsets and
9 sizes of the rootfs and kernel parts contained in the firmware.
31 firmware@10000 {
|
| H A D | brcm,bcm947xx-cfe-partitions.txt | 21 4) TRX firmware container which can hold up to 4 subpartitions
22 5) Backup TRX firmware used after failed upgrade
25 For example both: main firmware and backup firmware use the same TRX format with
26 the same header. To distinguish currently used firmware a CFE's environment
|
| /f-stack/freebsd/kern/ |
| H A D | subr_firmware.c | 109 struct firmware fw; /* externally visible information */
135 MTX_SYSINIT(firmware, &firmware_mtx, "firmware table", MTX_DEF);
166 const struct firmware *
168 unsigned int version, const struct firmware *parent) in firmware_register()
287 const struct firmware *
341 const struct firmware *
358 firmware_put(const struct firmware *p, int flags) in firmware_put()
508 DECLARE_MODULE(firmware, firmware_mod, SI_SUB_DRIVERS, SI_ORDER_FIRST);
509 MODULE_VERSION(firmware, 1);
|
| /f-stack/freebsd/contrib/device-tree/Bindings/clock/ |
| H A D | xlnx,zynqmp-clk.txt | 3 Zynq MPSoC firmware interface
45 from firmware. Output clocks indexes are mentioned in
52 firmware {
53 zynqmp_firmware: zynqmp-firmware {
54 compatible = "xlnx,zynqmp-firmware";
|