Searched +full:system +full:- +full:firmware (Results 1 – 25 of 1055) sorted by relevance
12345678910>>...43
| /kernel/linux/linux-6.6/drivers/firmware/ |
| 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
38 enabled or disabled via the SCP firmware
[all …]
|
| /kernel/linux/linux-5.10/drivers/firmware/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
4 # see Documentation/kbuild/kconfig-language.rst.
7 menu "Firmware Drivers"
10 tristate "ARM System Control and Management Interface (SCMI) Message Protocol"
14 ARM System Control and Management Interface (SCMI) protocol is a
15 set of operating system-independent software interfaces that are
16 used in system management. SCMI is extensible and currently provides
17 interfaces for: Discovery and self-description of the interfaces
19 a given device or domain into the various power-saving states that
37 enabled or disabled via the SCP firmware
[all …]
|
| /kernel/linux/linux-5.10/Documentation/ABI/stable/ |
| 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 …]
|
| /kernel/linux/linux-6.6/Documentation/ABI/stable/ |
| 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 …]
|
| /kernel/linux/linux-6.6/Documentation/arch/arm/keystone/ |
| 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 …]
|
| /kernel/linux/linux-5.10/Documentation/arm/keystone/ |
| 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 …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-6.6/drivers/acpi/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
18 Linux requires an ACPI-compliant platform (hardware/firmware),
19 and assumes the presence of OS-directed configuration and power
25 the Plug-and-Play BIOS specification (PnP BIOS), the
35 ACPI is an open industry specification originally co-developed by
36 Hewlett-Packard, Intel, Microsoft, Phoenix, and Toshiba. Currently,
67 Enable in-kernel debugging of AML facilities: statistics,
92 bool "ACPI Firmware Performance Data Table (FPDT) support"
95 Enable support for the Firmware Performance Data Table (FPDT).
96 This table provides information on the timing of the system
[all …]
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-firmware-opal-powercap | 1 What: /sys/firmware/opal/powercap
3 Contact: Linux for PowerPC mailing list <linuxppc-dev@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@ozlabs.org>
15 Description: System powercap directory and attributes applicable for
21 - powercap-min : This file provides the minimum
[all …]
|
| D | sysfs-firmware-dmi-entries | 1 What: /sys/firmware/dmi/entries/
5 Many machines' firmware (x86 and ia64) 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 …]
|
| 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 …]
|
| 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 …]
|
| 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 …]
|
| /kernel/linux/linux-6.6/Documentation/ABI/testing/ |
| D | sysfs-firmware-opal-powercap | 1 What: /sys/firmware/opal/powercap
3 Contact: Linux for PowerPC mailing list <linuxppc-dev@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@ozlabs.org>
15 Description: System powercap directory and attributes applicable for
21 - powercap-min : This file provides the minimum
[all …]
|
| D | sysfs-firmware-dmi-entries | 1 What: /sys/firmware/dmi/entries/
5 Many machines' firmware (x86 and ia64) 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 …]
|
| 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 …]
|
| 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 …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/remoteproc/ |
| 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 …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/remoteproc/ |
| 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 …]
|
| /kernel/linux/linux-6.6/drivers/dax/ |
| 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 …]
|
| /kernel/linux/linux-5.10/drivers/firmware/efi/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
2 menu "EFI (Extensible Firmware Interface) Support"
10 If you say Y here, you are able to get EFI (Extensible Firmware
45 Export efi runtime memory maps to /sys/firmware/efi/runtime-map.
49 See also Documentation/ABI/testing/sysfs-firmware-efi-runtime-map.
58 to specific memory range by updating original (firmware provided)
70 Ranges can be set up to this value using comma-separated list.
82 to the system's general purpose "System RAM" pool. On the
86 resource, and set aside for direct-access (device-dax) by
88 the page allocator by system administrator policy via the
[all …]
|
| /kernel/linux/linux-5.10/Documentation/networking/device_drivers/ethernet/netronome/ |
| D | nfp.rst | 1 .. SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
12 - `Overview`_
13 - `Acquiring Firmware`_
20 incorporated in the company's family of Agilio SmartNICs. The SR-IOV
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
[all …]
|
| /kernel/linux/linux-6.6/Documentation/powerpc/ |
| 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 …]
|
| /kernel/linux/linux-5.10/Documentation/powerpc/ |
| 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 …]
|
12345678910>>...43