Searched +full:firmware +full:- +full:reset (Results 1 – 25 of 158) sorted by relevance
1234567
| /Documentation/devicetree/bindings/arm/bcm/ |
| D | raspberrypi,bcm2835-firmware.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/arm/bcm/raspberrypi,bcm2835-firmware.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Raspberry Pi VideoCore firmware driver
10 - Eric Anholt <eric@anholt.net>
11 - Stefan Wahren <wahrenst@gmx.net>
17 const: raspberrypi,bcm2835-firmware
20 - compatible
25 - const: raspberrypi,bcm2835-firmware
[all …]
|
| /Documentation/devicetree/bindings/firmware/xilinx/ |
| D | xlnx,zynqmp-firmware.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/firmware/xilinx/xlnx,zynqmp-firmware.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Xilinx firmware driver
10 - Nava kishore Manne <nava.kishore.manne@amd.com>
12 description: The zynqmp-firmware node describes the interface to platform
13 firmware. ZynqMP has an interface to communicate with secure firmware.
14 Firmware driver provides an interface to firmware APIs. Interface APIs
23 - description: For implementations complying for Zynq Ultrascale+ MPSoC.
[all …]
|
| /Documentation/ABI/stable/ |
| D | sysfs-driver-firmware-zynqmp | 1 What: /sys/devices/platform/firmware\:zynqmp-firmware/ggs*
11 The register is reset during system or power-on
17 # cat /sys/devices/platform/firmware\:zynqmp-firmware/ggs0
18 # echo <value> > /sys/devices/platform/firmware\:zynqmp-firmware/ggs0
22 # cat /sys/devices/platform/firmware\:zynqmp-firmware/ggs0
23 # echo 0x1234ABCD > /sys/devices/platform/firmware\:zynqmp-firmware/ggs0
27 What: /sys/devices/platform/firmware\:zynqmp-firmware/pggs*
38 This register is only reset by the power-on reset
39 and maintains its value through a system reset.
42 Register is reset only by a POR reset.
[all …]
|
| D | sysfs-bus-mhi | 27 Description: Initiates a SoC reset on the MHI controller. A SoC reset is
28 a reset of last resort, and will require a complete re-init.
30 non-responsive, or as a means of loading new firmware as a
37 Description: Writing a non-zero value to this file will force devices to
44 which is used to download firmware over EDL) to update firmware.
|
| /Documentation/networking/devlink/ |
| D | devlink-flash.rst | 1 .. SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
9 The ``devlink-flash`` API allows updating device firmware. It replaces the
10 older ``ethtool-flash`` mechanism, and doesn't require taking any
13 $ devlink dev flash pci/0000:05:00.0 file flash-boot.bin
15 Note that the file name is a path relative to the firmware loading path
16 (usually ``/lib/firmware/``). Drivers may send status updates to inform
22 The ``devlink-flash`` command allows optionally specifying a mask indicating
26 .. list-table:: List of overwrite mask bits
29 * - Name
30 - Description
[all …]
|
| D | devlink-reload.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 ``devlink-reload`` provides mechanism to reinit driver entities, applying
8 ``devlink-params`` and ``devlink-resources`` new values. It also provides
9 mechanism to activate firmware.
17 .. list-table:: Possible reload actions
20 * - Name
21 - Description
22 * - ``driver-reinit``
23 - Devlink driver entities re-initialization, including applying
27 * ``devlink-params`` in configuration mode ``driverinit``
[all …]
|
| D | devlink-params.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 level device functionality. Since devlink can operate at the device-wide
22 .. list-table:: Possible configuration modes
25 * - Name
26 - Description
27 * - ``runtime``
28 - set while the driver is running, and takes effect immediately. No
29 reset is required.
30 * - ``driverinit``
31 - applied while the driver initializes. Requires the user to restart
[all …]
|
| D | i40e.rst | 1 .. SPDX-License-Identifier: GPL-2.0
15 .. list-table:: devlink info versions implemented
18 * - Name
19 - Type
20 - Example
21 - Description
22 * - ``board.id``
23 - fixed
24 - K15190-000
25 - The Product Board Assembly (PBA) identifier of the board.
[all …]
|
| /Documentation/devicetree/bindings/tpm/ |
| D | tpm-common.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/tpm/tpm-common.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Lukas Wunner <lukas@wunner.de>
14 pattern: '^tpm(@[0-9a-f]+)?$'
23 linux,sml-base:
25 base address of reserved memory allocated for firmware event log
28 linux,sml-size:
30 size of reserved memory allocated for firmware event log
[all …]
|
| /Documentation/devicetree/bindings/gpu/host1x/ |
| D | nvidia,tegra234-nvdec.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/gpu/host1x/nvidia,tegra234-nvdec.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
15 - Thierry Reding <treding@gmail.com>
16 - Mikko Perttunen <mperttunen@nvidia.com>
20 pattern: "^nvdec@[0-9a-f]*$"
24 - nvidia,tegra234-nvdec
32 clock-names:
34 - const: nvdec
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-fpga-manager | 14 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
27 * reset = FPGA held in reset state
28 * firmware request = firmware class request in progress
29 * firmware request error = firmware request failed
49 * reconfig operation error - invalid operations detected by
53 * reconfig CRC error - CRC error detected by
55 * reconfig incompatible image - reconfiguration image is
57 * reconfig IP protocol error - protocol errors detected by
59 * reconfig fifo overflow error - FIFO overflow detected by
|
| D | sysfs-firmware-gsmi | 1 What: /sys/firmware/gsmi
5 Some servers used internally at Google have firmware
9 historical reasons this different entry-point has been
13 these firmware callbacks. Currently, this functionality
15 access to EFI-style variables stored in nvram.
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
[all …]
|
| D | sysfs-bus-i2c-devices-turris-omnia-mcu | 8 revisions have board information burned in the ATSHA204-A chip).
21 revisions have board information burned in the ATSHA204-A chip).
35 - ``mcu`` makes the button press event be handled by the MCU to
37 - ``cpu`` makes the button press event be handled by the CPU.
45 Description: (RW) Newer versions of the microcontroller firmware of the
53 by the firmware.
61 Description: (RO) Newer versions of the microcontroller firmware report the
63 MCU firmware is too old, this file reads 0x0.
72 part of the microcontroller firmware.
81 part of the microcontroller firmware.
[all …]
|
| D | sysfs-bus-dfl-devices-n3000-nios | 5 Description: Read-only. Returns the FEC mode of the 25G links of the
6 ethernet retimers configured by Nios firmware. "rs" for Reed
9 happens when the Nios firmware version major < 3, or no link is
17 Description: Read-only. Returns the enumeration value of the working mode of
18 the retimer A configured by the Nios firmware. The value is
19 read out from shared registers filled by the Nios firmware. Now
22 - "0": Reset
23 - "1": 4x10G
24 - "2": 4x25G
25 - "3": 2x25G
[all …]
|
| D | sysfs-class-mic | 8 PCIe form factor add-in Coprocessor card based on the Intel Many
26 MIC device. For example - "x100"
34 MIC device. For example - "A0" or "B0"
55 "resetting" A reset has been initiated for the MIC device
56 "reset_failed" The MIC device has failed to reset.
66 of firmware, ramdisk, cmdline and bootmode
68 "reset" Initiates device reset.
99 self-bootable machines. When read, this entry provides
107 What: /sys/class/mic/mic<X>/firmware
113 /lib/firmware/ where the firmware image to be booted on the
[all …]
|
| D | sysfs-bus-pci | 4 Contact: linux-pci@vger.kernel.org
15 (Note: kernels before 2.6.28 may require echo -n).
20 Contact: linux-pci@vger.kernel.org
31 (Note: kernels before 2.6.28 may require echo -n).
36 Contact: linux-pci@vger.kernel.org
55 Contact: Chris Wright <chrisw@sous-sol.org>
72 Contact: Linux PCI developers <linux-pci@vger.kernel.org>
74 Writing a non-zero value to this attribute will
76 re-discover previously removed devices.
80 Contact: Linux PCI developers <linux-pci@vger.kernel.org>
[all …]
|
| /Documentation/networking/device_drivers/ethernet/netronome/ |
| D | nfp.rst | 1 .. SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
14 - `Overview`_
15 - `Acquiring Firmware`_
16 - `Devlink Info`_
17 - `Configure Device`_
18 - `Statistics`_
25 are also incorporated in the companies' family of Agilio SmartNICs. The SR-IOV
28 Acquiring Firmware
31 The NFP3800, NFP4000 and NFP6000 devices require application specific firmware
32 to function. Application firmware can be located either on the host file system
[all …]
|
| /Documentation/devicetree/bindings/pci/ |
| D | pci.txt | 3 PCI Bus Binding to: IEEE Std 1275-1994
4 https://www.devicetree.org/open-firmware/bindings/pci/pci2_1.pdf
8 Open Firmware Recommended Practice: Interrupt Mapping
9 https://www.devicetree.org/open-firmware/practice/imap/imap0_9d.pdf
14 - linux,pci-domain:
21 - max-link-speed:
27 - reset-gpios:
29 GPIO and apply fundamental reset to endpoints.
30 - supports-clkreq:
34 not to advertise ASPM L1 Sub-States support if there is no CLKREQ signal.
[all …]
|
| /Documentation/driver-api/nvdimm/ |
| D | firmware-activate.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 NVDIMM Runtime Firmware Activation
7 Some persistent memory devices run a firmware locally on the device /
9 and health monitoring. The process of updating that firmware typically
10 involves a reboot because it has implications for in-flight memory
13 DSM specification [1], has added support for activating firmware at
17 to advertise and control their local runtime firmware activation
20 The libnvdimm bus object, ndbusX, implements an ndbusX/firmware/activate
21 attribute that shows the state of the firmware activation as one of 'idle',
24 - idle:
[all …]
|
| /Documentation/spi/ |
| D | butterfly.rst | 2 spi_butterfly - parport-to-butterfly adapter driver
7 firmware for user interfacing and/or sensors. A Butterfly is a $US20
9 sensors, LCD, flash, toggle stick, and more. You can use AVR-GCC to
10 develop firmware for this, and flash it using this adapter cable.
26 AVR and a DataFlash chip; and to the AVR reset line. This is all you
27 need to reflash the firmware, and the pins are the standard Atmel "ISP"
28 connector pins (used also on non-Butterfly AVR boards). On the parport
32 Signal Butterfly Parport (DB-25)
35 RESET J403.nRST pin 3/D1
43 (a) flash new firmware that disables SPI (set PRR.2, and disable pullups
[all …]
|
| /Documentation/devicetree/bindings/remoteproc/ |
| D | qcom,sc7180-mss-pil.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/remoteproc/qcom,sc7180-mss-pil.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Sibi Sankar <quic_sibis@quicinc.com>
13 This document describes the hardware for a component that loads and boots firmware
19 - qcom,sc7180-mss-pil
23 - description: MSS QDSP6 registers
24 - description: RMB registers
26 reg-names:
[all …]
|
| /Documentation/devicetree/bindings/usb/ |
| D | nvidia,tegra20-ehci.txt | 4 SOC is as described in the document "Open Firmware Recommended
9 - compatible : For Tegra20, must contain "nvidia,tegra20-ehci".
10 For Tegra30, must contain "nvidia,tegra30-ehci". Otherwise, must contain
11 "nvidia,<chip>-ehci" plus at least one of the above, where <chip> is
13 - nvidia,phy : phandle of the PHY that the controller is connected to.
14 - clocks : Must contain one entry, for the module clock.
15 See ../clocks/clock-bindings.txt for details.
16 - resets : Must contain an entry for each entry in reset-names.
17 See ../reset/reset.txt for details.
18 - reset-names : Must include the following entries:
[all …]
|
| /Documentation/devicetree/bindings/power/reset/ |
| D | xlnx,zynqmp-power.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/power/reset/xlnx,zynqmp-power.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Michal Simek <michal.simek@amd.com>
13 The zynqmp-power node describes the power management configurations.
18 const: xlnx,zynqmp-power
28 that will be the phandle to the intended sub-mailbox
34 xlnx,zynqmp-ipi-mailbox.txt for typical controller that
37 - description: tx channel
[all …]
|
| /Documentation/devicetree/bindings/net/wireless/ |
| D | brcm,bcm4329-fmac.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/net/wireless/brcm,bcm4329-fmac.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Arend van Spriel <arend@broadcom.com>
19 - $ref: ieee80211.yaml#
24 - items:
25 - enum:
26 - brcm,bcm43143-fmac
27 - brcm,bcm4341b0-fmac
[all …]
|
| /Documentation/devicetree/bindings/firmware/ |
| D | nvidia,tegra186-bpmp.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/firmware/nvidia,tegra186-bpmp.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Thierry Reding <thierry.reding@gmail.com>
11 - Jon Hunter <jonathanh@nvidia.com>
16 management, and reset control tasks from the CPU. The binding document
17 defines the resources that would be used by the BPMP firmware driver,
25 - .../mailbox/mailbox.txt
26 - .../mailbox/nvidia,tegra186-hsp.yaml
[all …]
|
1234567