| /openbmc/linux/lib/crypto/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
26 Declares whether the architecture provides an arch-specific
27 accelerated implementation of the Blake2s library interface,
35 fallback, e.g., for SIMD implementations. If no arch specific
36 implementation is enabled, this implementation serves the users
42 Declares whether the architecture provides an arch-specific
43 accelerated implementation of the ChaCha library interface,
52 fallback, e.g., for SIMD implementations. If no arch specific
53 implementation is enabled, this implementation serves the users
62 by either the generic implementation or an arch-specific one, if one
[all …]
|
| /openbmc/linux/Documentation/arch/arm/samsung/ |
| H A D | gpio.rst | 2 Samsung GPIO implementation
6 ------------
8 This outlines the Samsung GPIO implementation and the architecture
9 specific calls provided alongside the drivers/gpio core.
13 -------------------
15 The gpio implementation uses gpiolib as much as possible, only providing
16 specific calls for the items that require Samsung specific handling, such
17 as pin special-function or pull resistor control.
23 -----------------
25 Pin configuration is specific to the Samsung architecture, with each SoC
[all …]
|
| /openbmc/docs/designs/mctp/ |
| H A D | mctp-userspace.md | 8 This document describes a userspace implementation of MCTP infrastructure,
20 provides a socket-based interface for other processes to send and receive
24 handling local MCTP-stack configuration, like local EID assignments.
30 2. one or more binding implementations (eg, MCTP-over-serial), which interact
33 3. an interface to handler applications over a unix-domain socket.
35 The proposed implementation here is to produce an MCTP "library" which provides
38 - an "upper" messaging transmit/receive interface, for tx/rx of a full message
39 to a specific endpoint (ie, (1) above)
41 - a "lower" hardware binding for transmit/receive of individual packets,
45 The lower interface would be plugged in to one of a number of hardware-specific
[all …]
|
| /openbmc/linux/Documentation/core-api/ |
| H A D | genericirq.rst | 7 :Copyright: |copy| 2005-2010: Thomas Gleixner
8 :Copyright: |copy| 2005-2006: Ingo Molnar
28 The original implementation of interrupt handling in Linux uses the
29 __do_IRQ() super-handler, which is able to deal with every type of
33 a quite universal set for the ARM interrupt handler implementation in
36 - Level type
38 - Edge type
40 - Simple type
42 During the implementation we identified another type:
44 - Fast EOI type
[all …]
|
| /openbmc/u-boot/doc/imx/misc/ |
| H A D | sdp.txt | 1 -------------
2 SDP in U-Boot
3 -------------
9 The implementation in U-Boot uses the USB Downloader Gadget (g_dnl) to
10 provide a SDP implementation over USB. This allows to download program
11 images to the target in SPL/U-Boot using the same protocol/tooling the
15 protocols allow to access a USB device without OS specific drivers. The
16 U-Boot implementation has primarly been tested using the open source
20 install U-Boot without a JTAG debugger, using the USB boot mode as
25 specific image header (see doc/README.imximage). There are extensions
[all …]
|
| /openbmc/linux/include/uapi/linux/ |
| H A D | socket.h | 1 /* SPDX-License-Identifier: GPL-2.0 WITH Linux-syscall-note */
8 #define _K_SS_MAXSIZE 128 /* Implementation specific max size */
20 /* Following field(s) are implementation specific */
21 char __data[_K_SS_MAXSIZE - sizeof(unsigned short)];
25 void *__align; /* implementation specific desired alignment */
|
| H A D | tee.h | 2 * Copyright (c) 2015-2016, Linaro Limited
37 * Each TEE driver defines a TEE specific protocol which is used for the
52 #define TEE_MEMREF_NULL (__u64)(-1) /* NULL MemRef Buffer */
55 * TEE Implementation ID
61 * OP-TEE specific capabilities
66 * struct tee_ioctl_version_data - TEE version
67 * @impl_id: [out] TEE implementation id
68 * @impl_caps: [out] Implementation specific capabilities
71 * Identifies the TEE implementation, @impl_id is one of TEE_IMPL_ID_* above.
72 * @impl_caps is implementation specific, for example TEE_OPTEE_CAP_*
[all …]
|
| /openbmc/linux/tools/testing/selftests/powerpc/tm/ |
| H A D | tm.h | 1 /* SPDX-License-Identifier: GPL-2.0-only */
38 * Transactional Memory was removed in ISA 3.1. A synthetic TM implementation
40 * synthetic implementation immediately fails after tbegin. This failure sets
41 * Bit 7 (Failure Persistent) and Bit 15 (Implementation-specific).
49 * times in case we got an Implementation-specific failure on a non ISA in htm_is_synthetic()
50 * v3.1 system. On these systems the Implementation-specific failure in htm_is_synthetic()
|
| /openbmc/linux/drivers/rapidio/switches/ |
| H A D | idt_gen2.c | 1 // SPDX-License-Identifier: GPL-2.0-or-later
219 * This routine performs device-specific initialization only. in idtg2_em_init()
223 pr_debug("RIO: %s [%d:%d]\n", __func__, rdev->destid, rdev->hopcount); in idtg2_em_init()
225 /* Set Port-Write info CSR: PRIO=3 and CRF=1 */ in idtg2_em_init()
237 /* Use Port-Writes for LT layer error reporting. in idtg2_em_init()
238 * Enable per-port reset in idtg2_em_init()
251 /* Configure reporting of implementation specific errors/events */ in idtg2_em_init()
255 /* Use Port-Writes for port error reporting and enable error logging */ in idtg2_em_init()
256 tmp = RIO_GET_TOTAL_PORTS(rdev->swpinfo); in idtg2_em_init()
275 /* Use Port-Writes for lane error reporting (when enabled) in idtg2_em_init()
[all …]
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Control/ |
| H A D | VoltageRegulatorMode.interface.yaml | 3 Control.VoltageRegulatorProfile.Supported is read only. Implementation of
7 and sets the implementation specific mode for the voltage regulator to run
8 in. The definitions of said enum are implementation defined, as systems
22 - name: Supported
25 - readonly
27 An implementation specific list of supported modes that the voltage
30 - name: Selected
|
| H A D | ThermalMode.interface.yaml | 6 Implementation of this interface populates the list of supported modes.
8 Implementation specific mode for the thermal control application
12 - name: Supported
15 - readonly
17 An implementation specific list of supported modes that the thermal
19 - name: Current
|
| /openbmc/qemu/include/accel/ |
| H A D | accel-cpu-target.h | 3 * This header is used only by target-specific code.
8 * See the COPYING file in the top-level directory.
15 * This header is used to define new accelerator-specific target-specific
17 * It uses CPU_RESOLVING_TYPE, so this is clearly target-specific.
19 * Do not try to use for any other purpose than the implementation of new
20 * subclasses in target/, or the accel implementation itself in accel/
26 #define TYPE_ACCEL_CPU "accel-" CPU_RESOLVING_TYPE
27 #define ACCEL_CPU_NAME(name) (name "-" TYPE_ACCEL_CPU)
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Dump/ |
| H A D | Create.interface.yaml | 5 Any OpenBMC implementation should provide one implementation of
7 /xyz/openbmc_project/dump/<dump type>. On multi-host or on multi-BMC systems
9 /xyz/openbmc_project/dump/<dump type><instance-id>.
12 - name: CreateDump
16 - name: AdditionalData
20 this case should be an implementation specific enum defined for
21 the specific type of dump either in xyz or in a domain. The
23 enum-format string is required to come from a parallel class
24 with this specific Enum name. All of the Enum strings should be
34 - name: Path
[all …]
|
| /openbmc/openbmc/meta-phosphor/recipes-phosphor/pldm/ |
| H A D | pldm_git.bb | 2 LICENSE = "Apache-2.0"
8 DESCRIPTION = "Implementation of the PLDM specifications"
12 DEPENDS += "phosphor-dbus-interfaces"
13 DEPENDS += "nlohmann-json"
16 DEPENDS += "phosphor-logging"
20 PACKAGE_BEFORE_PN:append = " pldmtool pldm-libs"
28 FILES:pldm-libs = "${libdir}/lib*${SOLIBS}"
33 PACKAGECONFIG[transport-mctp-demux] = "-Dtransport-implementation=mctp-demux"
34 PACKAGECONFIG[transport-af-mctp] = "-Dtransport-implementation=af-mctp"
35 PACKAGECONFIG[oem-ibm] = "-Doem-ibm=enabled, -Doem-ibm=disabled, , squashfs-tools"
[all …]
|
| /openbmc/linux/Documentation/mm/damon/ |
| H A D | design.rst | 1 .. SPDX-License-Identifier: GPL-2.0
13 - Operations Set: Implements fundamental operations for DAMON that depends on
14 the given monitoring target address-space and available set of
16 - Core: Implements core logics including monitoring overhead/accurach control
17 and access-aware system operations on top of the operations set layer, and
18 - Modules: Implements kernel modules for various purposes that provides
23 ---------------------------
26 implementations for specific operations that are dependent on and optimized for
38 For example, physical memory, virtual memory, swap space, those for specific
45 --------------------
[all …]
|
| /openbmc/docs/designs/ |
| H A D | bmc-service-failure-debug-and-recovery.md | 16 - A class of failure exists where a BMC service has entered a failed state but
18 - A class of failure exists under which we can attempt debug data collection
21 This proposal argues for and proposes a software-driven debug data capture and
26 By necessity, BMCs are not self-contained systems. BMCs exist to service the
27 needs of both the host system by providing in-band platform services such as
29 out-of-band system management interfaces such as error reporting, platform
35 are usually a domain-specific Linux distributions with complex or highly coupled
40 recovery in the face of well-defined error conditions, but the need to mitigate
41 ill-defined error conditions or entering unintended software states remains.
60 As the state transformations to enter the ill-defined or unintended software
[all …]
|
| /openbmc/linux/Documentation/driver-api/rapidio/ |
| H A D | mport_cdev.rst | 17 for user-space applications. Most of RapidIO operations are supported through
24 Using available set of ioctl commands user-space applications can perform
27 - Reads and writes from/to configuration registers of mport devices
29 - Reads and writes from/to configuration registers of remote RapidIO devices.
32 - Set RapidIO Destination ID for mport devices (RIO_MPORT_MAINT_HDID_SET)
33 - Set RapidIO Component Tag for mport devices (RIO_MPORT_MAINT_COMPTAG_SET)
34 - Query logical index of mport devices (RIO_MPORT_MAINT_PORT_IDX_GET)
35 - Query capabilities and RapidIO link configuration of mport devices
37 - Enable/Disable reporting of RapidIO doorbell events to user-space applications
39 - Enable/Disable reporting of RIO port-write events to user-space applications
[all …]
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/ |
| H A D | Manager.v1_22_0.json | 4 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
5 …"copyright": "Copyright 2014-2025 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or…
12 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
43 "description": "The available OEM-specific actions for this resource.",
44 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
58 … "Oem": "The controller supports a command shell connection through an OEM-specific protocol.",
69 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
84 …on": "This property enumerates the command shell connection types that the implementation allows.",
94 …hall contain the maximum number of concurrent service sessions that this implementation supports.",
130 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
[all …]
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
| H A D | Manager.v1_22_0.json | 4 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
5 …"copyright": "Copyright 2014-2025 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or…
12 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
43 "description": "The available OEM-specific actions for this resource.",
44 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
58 … "Oem": "The controller supports a command shell connection through an OEM-specific protocol.",
69 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
84 …on": "This property enumerates the command shell connection types that the implementation allows.",
94 …hall contain the maximum number of concurrent service sessions that this implementation supports.",
130 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
[all …]
|
| /openbmc/linux/Documentation/staging/ |
| H A D | remoteproc.rst | 10 of operating system, whether it's Linux or any other flavor of real-time OS.
12 OMAP4, for example, has dual Cortex-A9, dual Cortex-M3 and a C64x+ DSP.
13 In a typical configuration, the dual cortex-A9 is running Linux in a SMP
22 platform-specific remoteproc drivers only need to provide a few low-level
24 (for more information about the virtio-based rpmsg bus and its drivers,
118 name of this remote processor, platform-specific ops handlers,
154 This is called by the platform-specific rproc implementation, whenever
172 This function should be called when the platform specific rproc
173 implementation decides to remove the rproc device. it should
180 Returns 0 on success and -EINVAL if @rproc isn't valid.
[all …]
|
| /openbmc/intel-ipmi-oem/docs/ |
| H A D | Intel_IPMI_Platform_Events.md | 3 In many cases Manufacturers-specific IPMI Platfrom Events are stored in binary
8 events originating from Intel Management Engine (ME) is used as a case-study.
9 General design of the solution is followed by tailored-down implementation for
14 - **IPMI** - Intelligent Platform Management Interface; standarized binary
16 - **Platform Event** - specific type of IPMI binary payload, used for encoding
17 and sending asynchronous one-way messages to recipient `[1]-29.3`
18 - **ME** - Intel Management Engine, autonomous subsystem used for remote
20 - **Redfish** - modern datacenter management protocol, built around REST
22 - **OpenBMC** - open-source BMC implementation with Redfish-oriented interface
28 between entities in data-center. Recipient is responsible to receive data,
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/opp/ |
| H A D | opp-v2-base.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/opp/opp-v2-base.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Viresh Kumar <viresh.kumar@linaro.org>
13 Devices work at voltage-current-frequency combinations and some implementations
25 pattern: '^opp-table(-[a-z0-9]+)?$'
27 opp-shared:
36 '^opp(-?[0-9]+)*$':
39 One or more OPP nodes describing voltage-current-frequency combinations.
[all …]
|
| /openbmc/linux/drivers/mmc/host/ |
| H A D | dw_mmc.h | 1 /* SPDX-License-Identifier: GPL-2.0-or-later */
17 #include <linux/fault-inject.h>
59 * struct dw_mci - MMC controller state shared between all slots
77 * @dma_64bit_address: Whether DMA supports 64-bit address mode or not.
80 * @dma_ops: Pointer to platform-specific DMA callbacks.
84 * @dms: structure of slave-dma private data.
107 * @drv_data: Driver specific data for identified variant of the controller
108 * @priv: Implementation defined private data.
122 * @quirks: Set of quirks that apply to specific versions of the IP.
134 * @lock is a softirq-safe spinlock protecting @queue as well as
[all …]
|
| /openbmc/phosphor-gpio-monitor/ |
| H A D | README.md | 5 ### `phosphor-gpio-monitor`
8 take action if requested. This implementation uses GPIO keys and only supports
12 ### `phosphor-multi-gpio-monitor`
14 This daemon accepts command line parameter as a well-defined GPIO configuration
20 New implementation (phosphor-multi-gpi
[all...] |
| /openbmc/linux/drivers/net/wireless/intel/iwlwifi/ |
| H A D | iwl-drv.h | 1 /* SPDX-License-Identifier: GPL-2.0 OR BSD-3-Clause */
3 * Copyright (C) 2005-2014, 2020-2021, 2023 Intel Corporation
4 * Copyright (C) 2013-2014 Intel Mobile Communications GmbH
14 #define NVM_RF_CFG_DASH_MSK(x) (x & 0x3) /* bits 0-1 */
15 #define NVM_RF_CFG_STEP_MSK(x) ((x >> 2) & 0x3) /* bits 2-3 */
16 #define NVM_RF_CFG_TYPE_MSK(x) ((x >> 4) & 0x3) /* bits 4-5 */
17 #define NVM_RF_CFG_PNUM_MSK(x) ((x >> 6) & 0x3) /* bits 6-7 */
18 #define NVM_RF_CFG_TX_ANT_MSK(x) ((x >> 8) & 0xF) /* bits 8-11 */
19 #define NVM_RF_CFG_RX_ANT_MSK(x) ((x >> 12) & 0xF) /* bits 12-15 */
29 * DOC: Driver system flows - drv component
[all …]
|