| /linux/drivers/firmware/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
4 # see Documentation/kbuild/kconfig-language.rst.
7 menu "Firmware Drivers"
9 source "drivers/firmware/arm_scmi/Kconfig"
12 tristate "ARM System Control and Power Interface (SCPI) Message Protocol"
16 System Control and Power Interface (SCPI) Message Protocol is
18 Cores(AP) and the System Control Processor(SCP). The MHU peripheral
19 provides a mechanism for inter-processor communication between SCP
25 certain system clocks configuration, thermal sensors and many
37 standard for registering callbacks from the platform firmware
[all …]
|
| /linux/Documentation/ABI/stable/ |
| H A D | sysfs-driver-firmware-zynqmp | 1 What: /sys/devices/platform/firmware\:zynqmp-firmware/ggs*
9 by system to pass information between masters.
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*
35 can be used by system to pass information between
38 This register is only reset by the power-on reset
[all …]
|
| /linux/Documentation/arch/arm64/ |
| H A D | cpu-hotplug.rst | 1 .. SPDX-License-Identifier: GPL-2.0
9 CPUs online/offline using PSCI. This document is about ACPI firmware allowing
10 CPUs that were not available during boot to be added to the system later.
15 CPU Hotplug on physical systems - CPUs not present at boot
16 ----------------------------------------------------------
20 in one of the sockets can be replaced while the system is running.
24 In the arm64 world CPUs are not a single device but a slice of the system.
26 while the system is running, and ACPI is not able to sufficiently describe
31 not discoverable, and must be described by firmware.
34 boot to discover the system wide supported features. ACPI's MADT GICC
[all …]
|
| /linux/Documentation/arch/arm/keystone/ |
| H A D | knav-qmss.rst | 9 The QMSS (Queue Manager Sub System) found on Keystone SOCs is one of
10 the main hardware sub system which forms the backbone of the Keystone
11 multi-core Navigator. QMSS consist of queue managers, packed-data structure
15 management of the packet queues. Packets are queued/de-queued by writing or
29 Documentation/devicetree/bindings/soc/ti/keystone-navigator-qmss.txt
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
40 git://git.ti.com/keystone-rtos/qmss-lld.git
42 k2_qmss_pdsp_acc48_k2_le_1_0_0_9.bin firmware supports upto 48 accumulator
[all …]
|
| /linux/drivers/acpi/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
19 Linux requires an ACPI-compliant platform (hardware/firmware),
20 and assumes the presence of OS-directed configuration and power
26 the Plug-and-Play BIOS specification (PnP BIOS), the
36 ACPI is an open industry specification originally co-developed by
37 Hewlett-Packard, Intel, Microsoft, Phoenix, and Toshiba. Currently,
72 Enable in-kernel debugging of AML facilities: statistics,
97 bool "ACPI Firmware Performance Data Table (FPDT) support"
100 Enable support for the Firmware Performance Data Table (FPDT).
101 This table provides information on the timing of the system
[all …]
|
| /linux/Documentation/driver-api/nvdimm/ |
| H A 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 …]
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-firmware-dmi-entries | 1 What: /sys/firmware/dmi/entries/
5 Many machines' firmware (x86 and arm64) export DMI /
6 SMBIOS tables to the operating system. Getting at this
17 length of the entry, as well as a firmware-provided
24 system unless they know for certain what their firmware
29 assigned by the operating system an 'instance', which is
34 entries "T-0" through "T-(N-1)":
38 /sys/firmware/dmi/entries/17-0
39 /sys/firmware/dmi/entries/17-1
40 /sys/firmware/dmi/entries/17-2
[all …]
|
| H A D | sysfs-firmware-opal-powercap | 1 What: /sys/firmware/opal/powercap
3 Contact: Linux for PowerPC mailing list <linuxppc-dev@lists.ozlabs.org>
7 power-cappable component.
9 What: /sys/firmware/opal/powercap/system-powercap
10 /sys/firmware/opal/powercap/system-powercap/powercap-min
11 /sys/firmware/opal/powercap/system-powercap/powercap-max
12 /sys/firmware/opal/powercap/system-powercap/powercap-current
14 Contact: Linux for PowerPC mailing list <linuxppc-dev@lists.ozlabs.org>
15 Description: System powercap directory and attributes applicable for
21 - powercap-min : This file provides the minimum
[all …]
|
| H A 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
14 is limited to handling the system event log and getting
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:
[all …]
|
| H A D | sysfs-firmware-efi | 1 What: /sys/firmware/efi/fw_vendor
4 Description: It shows the physical address of firmware vendor field in the
5 EFI system table.
8 What: /sys/firmware/efi/runtime
12 the EFI system table.
15 What: /sys/firmware/efi/config_table
19 system table.
22 What: /sys/firmware/efi/systab
24 Contact: linux-efi@vger.kernel.org
26 Tables found via the EFI System Table. The order in
[all …]
|
| H A D | sysfs-firmware-sgi_uv | 1 What: /sys/firmware/sgi_uv/
5 The /sys/firmware/sgi_uv directory contains information
8 Under that directory are a number of read-only attributes::
18 is used to select arch-dependent addresses and features.
32 of the operating system. Each partition will have a unique
36 A partitioned UV system can have one or more coherence
41 This value can be used to identify the UV system version::
50 The /sys/firmware/sgi_uv directory also contains two directories::
57 unique ordinal value (ex. /sys/firmware/sgi_uv/hubs/hub_5)
59 Each hub object directory contains a number of read-only attributes::
[all …]
|
| H A D | sysfs-firmware-efi-esrt | 1 What: /sys/firmware/efi/esrt/
4 Description: Provides userland access to read the EFI System Resource Table
5 (ESRT), a catalog of firmware for which can be updated with
8 Users: fwupdate - https://github.com/rhinstaller/fwupdate
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>/
[all …]
|
| H A D | sysfs-devices-platform-stratix10-rsu | 1 Intel Stratix10 Remote System Update (RSU) device attributes
3 What: /sys/devices/platform/stratix10-rsu.0/current_image
10 What: /sys/devices/platform/stratix10-rsu.0/fail_image
17 What: /sys/devices/platform/stratix10-rsu.0/state
22 (RO) the state of RSU system.
30 firmware through the RSU notify command before
42 What: /sys/devices/platform/stratix10-rsu.0/version
47 (RO) the version number of RSU firmware. 19.3 or late
48 version includes information about the firmware which
63 What: /sys/devices/platform/stratix10-rsu.0/error_location
[all …]
|
| /linux/Documentation/devicetree/bindings/remoteproc/ |
| H A D | ti,omap-remoteproc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/remoteproc/ti,omap-remoteproc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Suman Anna <s-anna@ti.com>
13 The OMAP family of SoCs usually have one or more slave processor sub-systems
14 that are used to offload some of the processor-intensive tasks, or to manage
15 other hardware accelerators, for achieving various system level goals.
17 The processor cores in the sub-system are usually behind an IOMMU, and may
18 contain additional sub-modules like Internal RAM and/or ROMs, L1 and/or L2
[all …]
|
| /linux/Documentation/arch/powerpc/ |
| H A D | firmware-assisted-dump.rst | 2 Firmware-Assisted Dump
7 The goal of firmware-assisted dump is to enable the dump of
8 a crashed system, and to do so from a fully-reset system, and
9 to minimize the total elapsed time until the system is back
12 - Firmware-Assisted Dump (FADump) infrastructure is intended to replace
14 - Fadump uses the same firmware interfaces and memory reservation model
16 - Unlike phyp dump, FADump exports the memory dump through /proc/vmcore
19 - Unlike phyp dump, userspace tool does not need to refer any sysfs
21 - Unlike phyp dump, FADump allows user to release all the memory reserved
23 - Once enabled through kernel boot parameter, FADump can be
[all …]
|
| /linux/drivers/dax/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
14 device. Platform firmware or a device driver may identify a
26 libnvdimm sub-system.
38 indication from platform firmware is meant to reserve the
40 device-dax instances for these memory ranges, and that also
43 "System RAM" pool.
52 CXL RAM regions are either mapped by platform-firmware
53 and published in the initial system-memory map as "System RAM", mapped
54 by platform-firmware as "Soft Reserved", or dynamically provisioned
55 after boot by the CXL driver. In the latter two cases a device-dax
[all …]
|
| /linux/Documentation/arch/x86/ |
| H A D | microcode.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 :Authors: - Fenghua Yu <fenghua.yu@intel.com>
8 - Borislav Petkov <bp@suse.de>
9 - Ashok Raj <ashok.raj@intel.com>
13 updating the microcode on platforms beyond the OEM End-Of-Life support,
14 and updating the microcode on long-running systems without rebooting.
39 During BSP (BootStrapping Processor) boot (pre-SMP), the kernel
56 if [ -z "$1" ]; then
66 rm -rf $TMPDIR
70 mkdir -p $DSTDIR
[all …]
|
| /linux/drivers/base/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
12 Before the switch to the netlink-based uevent source, this was
18 that it creates a high system load, or on smaller systems
19 it is known to create out-of-memory situations during bootup.
48 file system will be used instead.
61 With this option enabled, it allows to bring up a system in
73 with the PROT_EXEC flag. This can break, for example, non-KMS
77 bool "Select only drivers that don't need compile-time external firmware"
80 Select this option if you don't have magic firmware for drivers that
86 bool "Disable drivers features which enable custom firmware building"
[all …]
|
| /linux/drivers/firmware/efi/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
2 menu "EFI (Extensible Firmware Interface) Support"
38 to the system's general purpose "System RAM" pool. On the
42 resource, and set aside for direct-access (device-dax) by
44 the page allocator by system administrator policy via the
45 device-dax kmem facility. Say N to have the kernel treat this
46 memory as "System RAM" by default.
66 the EFI runtime support gets system table address, memory
83 memory before executing it. For compatibility with non-EFI loaders,
95 memory from the EFI System Partition by the stub.
[all …]
|
| /linux/drivers/firmware/imx/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
7 and the firmware running on DSP.
18 The System Controller Firmware (SCFW) is a low-level system function
19 which runs on a dedicated Cortex-M core to provide power, clock, and
24 SCU firmware running on M4.
31 The System Controller Management Interface firmware (SCMI FW) is
32 a low-level system function which runs on a dedicated Cortex-M
|
| /linux/Documentation/networking/device_drivers/ethernet/netronome/ |
| H A 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 …]
|
| /linux/Documentation/driver-api/firmware/ |
| H A 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:
47 * The firmware provides very unique device specific data tailored for
[all …]
|
| /linux/drivers/mtd/devices/ |
| H A D | ms02-nv.h | 1 /* SPDX-License-Identifier: GPL-2.0-or-later */
5 * DEC MS02-NV (54-20948-01) battery backed-up NVRAM module for
16 * 0x000000 - 0x3fffff SRAM
17 * 0x400000 - 0x7fffff CSR
19 * Within the SRAM area the following ranges are forced by the system
20 * firmware:
22 * 0x000000 - 0x0003ff diagnostic area, destroyed upon a reboot
23 * 0x000400 - ENDofRAM storage area, available to operating systems
26 * the first word is used by the firmware as a status flag passed
27 * from an operating system. If anything but the valid data magic
[all …]
|
| /linux/Documentation/sound/codecs/ |
| H A D | cs35l56.rst | 1 .. SPDX-License-Identifier: GPL-2.0-only
14 The high-level summary of this document is:
17 working, DO NOT ATTEMPT TO USE FIRMWARE AND SETTINGS FROM ANOTHER LAPTOP,
30 ---------------------------------
44 Firmware chapter
47 The amplifier is controlled and managed by firmware running on the internal
48 DSP. Firmware files are essential to enable the full capabilities of the
51 Firmware is distributed in the linux-firmware repository:
52 https://gitlab.com/kernel-firmware/linux-firmware.git
65 the firmware is *mandatory* to enable receiving the audio from the CS42L43.
[all …]
|
| /linux/drivers/base/firmware_loader/ |
| H A D | fallback.c | 1 // SPDX-License-Identifier: GPL-2.0
12 #include "firmware.h"
15 * firmware fallback mechanism
19 * use small loading timeout for caching devices' firmware because all these
20 * firmware images have been loaded successfully at lease once, also system is
21 * ready for completing firmware loading now. The maximum size of firmware in
57 if (kill_all || !fw_priv->need_uevent) in kill_pending_fw_fallback_reqs()
68 * fw_load_sysfs_fallback() - load a firmware via the sysfs fallback mechanism
69 * @fw_sysfs: firmware sysfs information for the firmware to load
72 * In charge of constructing a sysfs fallback interface for firmware loading.
[all …]
|