Home
last modified time | relevance | path

Searched full:fw (Results 1 – 25 of 93) sorted by relevance

1234

/Documentation/ABI/testing/
Dsysfs-platform-sst-atom8 If the FW has never been loaded it will display::
10 "FW not yet loaded"
12 If FW has been loaded it will display::
19 0d: BYT FW
20 0b: BSW FW
21 07: Merrifield FW
Dsysfs-class-mei21 Description: Display fw status registers content
23 The ME FW writes its status information into fw status
24 registers for BIOS and OS to monitor fw health.
67 FW components.
90 The ME FW writes Glitch Detection HW (TRC)
92 for BIOS and OS to monitor fw health.
/Documentation/networking/device_drivers/ethernet/amd/
Dpds_core.rst25 pds_core 0000:b5:00.0: FW: 1.60.0-73
27 pds_core 0000:b6:00.0: FW: 1.60.0-73
40 fw 1.51.0-73
42 fw.goldfw 1.15.9-C-22
43 fw.mainfwa 1.60.0-73
44 fw.mainfwb 1.60.0-57
57 * - ``fw``
60 * - ``fw.goldfw``
63 * - ``fw.mainfwa``
66 * - ``fw.mainfwb``
[all …]
/Documentation/networking/devlink/
Dmlx5.rst130 * - ``fw.psid``
133 * - ``fw.version``
199 fw reporter
201 The fw reporter implements `diagnose` and `dump` callbacks.
202 It follows symptoms of fw error such as fw syndrome by triggering
203 fw core dump and storing it into the dump buffer.
204 The fw reporter diagnose command can be triggered any time by the user to check
205 current fw status.
209 - Check fw heath status::
211 $ devlink health diagnose pci/0000:82:00.0 reporter fw
[all …]
Dnfp.rst48 * - ``fw.bundle_id``
51 * - ``fw.mgmt``
54 * - ``fw.cpld``
57 * - ``fw.app``
60 * - ``fw.undi``
63 * - ``fw.ncsi``
Dbnxt.rst65 * - ``fw.psid``
68 * - ``fw``
71 * - ``fw.mgmt``
74 * - ``fw.mgmt.api``
77 * - ``fw.nsci``
80 * - ``fw.roce``
Di40e.rst26 * - ``fw.mgmt``
31 * - ``fw.mgmt.api``
37 * - ``fw.mgmt.build``
41 * - ``fw.undi``
51 * - ``fw.psid.api``
55 * - ``fw.bundle_id``
Ddevlink-info.rst15 - name the per component FW versions (as opposed to the crowded ethtool
154 fw section in Generic Versions
158 fw.mgmt, fw.app, etc.
160 fw.mgmt
167 fw.mgmt.api
173 fw.app
178 fw.undi
183 fw.ncsi
189 fw.psid
195 fw.roce
[all …]
Dsfc.rst21 * - ``fw.mgmt.suc``
25 * - ``fw.mgmt.cmc``
35 * - ``fw.app``
50 * - ``fw.exprom``
55 * - ``fw.uefi``
Dice.rst117 * - ``fw.mgmt``
124 * - ``fw.mgmt.api``
131 * - ``fw.mgmt.build``
135 * - ``fw.undi``
145 * - ``fw.psid.api``
149 * - ``fw.bundle_id``
154 * - ``fw.app.name``
160 * - ``fw.app``
164 that both the name (as reported by ``fw.app.name``) and version are
166 * - ``fw.app.bundle_id``
[all …]
Dmlxsw.rst54 * - ``fw.psid``
57 * - ``fw.version``
78 * - ``fw.psid``
81 * - ``fw.version``
Ddevlink-region.rst57 pci/0000:00:05.0/fw-health: size 64 snapshot [1 2] max 8
67 $ devlink region dump pci/0000:00:05.0/fw-health snapshot 1
74 $ devlink region read pci/0000:00:05.0/fw-health snapshot 1 address 0 length 16
78 $ devlink region read pci/0000:00:05.0/fw-health address 16 length 16
Dhns3.rst23 * - ``fw``
26 * - ``fw.scc``
/Documentation/devicetree/bindings/display/bridge/
Dmegachips-stdpxxxx-ge-b850v3-fw.txt2 STDP4028-ge-b850v3-fw bridges (LVDS-DP)
3 STDP2690-ge-b850v3-fw bridges (DP-DP++)
12 suffix "-ge-b850v3-fw" to make it clear that the driver is for the bridges with
19 stdp4028-ge-b850v3-fw required properties:
20 - compatible : "megachips,stdp4028-ge-b850v3-fw"
26 stdp2690-ge-b850v3-fw required properties:
27 compatible : "megachips,stdp2690-ge-b850v3-fw"
37 compatible = "megachips,stdp4028-ge-b850v3-fw";
66 compatible = "megachips,stdp2690-ge-b850v3-fw";
/Documentation/admin-guide/media/
Dlmedm04.rst23 will produce dvb-usb-lme2510c-s7395.fw
36 will produce dvb-usb-lme2510c-s7395.fw
53 will produce dvb-usb-lme2510-lg.fw
59 dd if=US280D.sys ibs=1 skip=42360 count=3924 of=dvb-usb-lme2510-lg.fw
66 dd if=US280D.sys ibs=1 skip=35200 count=3850 of=dvb-usb-lme2510c-lg.fw
78 dd if=US290D.sys ibs=1 skip=36856 count=3976 of=dvb-usb-lme2510-s0194.fw
87 dd if=US290D.sys ibs=1 skip=33152 count=3697 of=dvb-usb-lme2510c-s0194.fw
97 dd if=US2B0D.sys ibs=1 skip=34432 count=3871 of=dvb-usb-lme2510c-rs2000.fw
105 echo -ne \\xF0\\x22 | dd conv=notrunc bs=1 count=2 seek=266 of=dvb-usb-lme2510c-rs2000.fw
Dopera-firmware.rst24 dvb-usb-opera-01.fw
25 dvb-usb-opera1-fpga-01.fw
/Documentation/driver-api/mei/
Dhdcp.rst6 ME FW as a security engine provides the capability for setting up
10 ME FW prepares HDCP2.2 negotiation parameters, signs and encrypts them
14 Similarly, the HDCP2.2 sink's response is transferred to ME FW
18 upon request ME FW will configure the port as authenticated and supply
/Documentation/devicetree/bindings/net/dsa/
Dlantiq,gswip.yaml43 gphy-fw:
55 - lantiq,xrx200-gphy-fw
56 - lantiq,xrx300-gphy-fw
57 - lantiq,xrx330-gphy-fw
58 - const: lantiq,gphy-fw
182 gphy-fw {
185 compatible = "lantiq,xrx200-gphy-fw", "lantiq,gphy-fw";
/Documentation/ABI/stable/
Dfirewire-cdev1 What: /dev/fw[0-9]+
6 The character device files /dev/fw* are the interface between
14 Each /dev/fw* is associated with one IEEE 1394 node, which can
15 be remote or local nodes. Operations on a /dev/fw* file have
50 operations are restricted to /dev/fw* files that are associated
57 A /dev/fw* file remains associated with one particular node
93 /dev/fw*, offset = 0.
Dsysfs-bus-firewire1 What: /sys/bus/firewire/devices/fw[0-9]+/
20 What: /sys/bus/firewire/devices/fw[0-9]+/units
39 /dev/fw[0-9]+ character device files
42 What: /sys/bus/firewire/devices/fw[0-9]+/is_local
54 What: /sys/bus/firewire/devices/fw[0-9]+[.][0-9]+/
114 What: /sys/bus/firewire/drivers/sbp2/fw*/host*/target*/*:*:*:*/ieee1394_id
116 /sys/bus/ieee1394/drivers/sbp2/fw*/host*/target*/*:*:*:*/ieee1394_id
/Documentation/devicetree/bindings/net/bluetooth/
Dnxp,88w8987-bt.yaml13 are used during FW download. To enable power save mode, the host
26 fw-init-baudrate:
30 Chip baudrate after FW is downloaded and initialized.
47 fw-init-baudrate = <3000000>;
/Documentation/devicetree/bindings/firmware/
Dqemu,fw-cfg-mmio.yaml4 $id: http://devicetree.org/schemas/firmware/qemu,fw-cfg-mmio.yaml#
29 const: qemu,fw-cfg-mmio
50 fw-cfg@9020000 {
51 compatible = "qemu,fw-cfg-mmio";
/Documentation/scsi/
DChangeLog.megaraid_sas115 1. Continue booting immediately if FW in FAULT at driver load time.
201 will allow the fw to do the chip reset which will not
210 which not returned by FW to driver's pending queue. Driver
211 will re-issue those pending cmds again to FW after the OCR
218 d). in Driver's ISR routine, if driver get the FW state as
219 state change, FW in Failure status and FW support online controller
223 OCR to finish, then issue the cmds to FW.
226 OCR to see if driver can bring back the FW.
232 3. In driver's timeout routine, driver will do three time reset if fw is in
233 failed state. Driver will kill adapter if can't bring back FW after the
[all …]
/Documentation/driver-api/media/drivers/ccs/
Dccs.rst23 ccs/ccs-sensor-vvvv-mmmm-rrrr.fw (sensor) and
24 ccs/ccs-module-vvvv-mmmm-rrrr.fw (module).
28 ccs/smiapp-sensor-vv-mmmm-rr.fw (sensor) and
29 ccs/smiapp-module-vv-mmmm-rrrr.fw (module).
33 ccs/smia-sensor-vv-mmmm-rr.fw (sensor).
/Documentation/devicetree/bindings/remoteproc/
Dti,pru-rproc.yaml145 firmware-name = "am335x-pru0-fw";
154 firmware-name = "am335x-pru1-fw";
184 firmware-name = "am65x-pru0_0-fw";
196 firmware-name = "am65x-rtu0_0-fw";
208 firmware-name = "am65x-txpru0_0-fw";
217 firmware-name = "am65x-pru0_1-fw";
229 firmware-name = "am65x-rtu0_1-fw";
241 firmware-name = "am65x-txpru0_1-fw";

1234