| /openbmc/openbmc/meta-openembedded/meta-multimedia/licenses/ |
| H A D | AOM-Patent-License-1.0 | 10 for sale, import or distribute any Implementation.
15 sell, offer for sale, import or distribute an Implementation under
17 this License, and must reproduce this License with any Implementation
21 root directory of the source code with its Implementation.
27 Implementation.
37 that any Implementation infringes Necessary Claims, any patent licenses
40 was in response to a corresponding suit regarding an Implementation first
45 1.4. Disclaimers. The Reference Implementation and Specification are provided
47 otherwise using the Reference Implementation or Specification is assumed
77 2.6. Implementation. "Implementation" means any implementation, including the
[all …]
|
| /openbmc/linux/lib/crypto/ |
| H A D | Kconfig | 27 accelerated implementation of the Blake2s library interface,
36 implementation is enabled, this implementation serves the users
43 accelerated implementation of the ChaCha library interface,
53 implementation is enabled, this implementation serves the users
62 by either the generic implementation or an arch-specific one, if one
69 accelerated implementation of the Curve25519 library interface,
78 implementation is enabled, this implementation serves the users
88 fulfilled by either the generic implementation or an arch-specific
105 accelerated implementation of the Poly1305 library interface,
114 implementation is enabled, this implementation serves the users
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-protocols/vsomeip/vsomeip/ |
| H A D | 0001-Update-to-C-17-560.patch | 62 implementation/message/src/deserializer.cpp | 4 +-
67 implementation/security/src/policy.cpp | 4 +-
68 implementation/security/src/security.cpp | 1 +
192 diff --git a/implementation/configuration/include/internal.hpp.in b/implementation/configuration/in…
194 --- a/implementation/configuration/include/internal.hpp.in
195 +++ b/implementation/configuration/include/internal.hpp.in
214 diff --git a/implementation/configuration/include/internal_android.hpp b/implementation/configurati…
216 --- a/implementation/configuration/include/internal_android.hpp
217 +++ b/implementation/configuration/include/internal_android.hpp
241 diff --git a/implementation/configuration/src/configuration_impl.cpp b/implementation/configuration…
[all …]
|
| /openbmc/linux/Documentation/crypto/ |
| H A D | architecture.rst | 103 the following implementations: AES-NI, assembler implementation, or
105 which cipher implementation is used? The answer to that question is the
106 priority number assigned to each cipher implementation by the kernel
109 implementations providing an implementation with that name and selects
110 the implementation with the highest priority.
113 implementation and thus does not want to rely on the priority-based
115 the cipher implementation to register a unique name in addition to
117 sure to refer to the intended cipher implementation.
133 - module: the kernel module providing the cipher implementation (or
136 - priority: the priority value of the cipher implementation
[all …]
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Control/ |
| H A D | README.msl.md | 10 If an OpenBMC implementation provides MinimumShipLevelRequired, it must be on
21 namespace. Again, there are no requirements on what an implementation does when
24 ## Implementation Notes
30 Phosphor OpenBMC provides a basic implementation of MinimumShipLevelRequired. It
32 implementation is suitable for the hypothetical platform implementation
36 implementation would need to write an application that implements
40 contributing it to Phosphor OpenBMC. A possible implementation for the
|
| 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
27 An implementation specific list of supported modes that the voltage
|
| /openbmc/linux/drivers/mailbox/ |
| H A D | Kconfig | 42 Mailbox implementation for i.MX Messaging Unit (MU).
58 An implementation of the ARM PL320 Interprocessor Communication
69 Mailbox implementation for communication with the the firmware
78 Mailbox implementation for OMAP family chips with hardware for
117 An implementation of the Altera Mailbox soft core. It is used
125 An implementation of the BCM2385 Mailbox. It is used to invoke
133 Mailbox implementation for STMicroelectonics family chips with
141 An implementation of Message Manager slave driver for Keystone
154 An implementation of the hi3660 mailbox. It is used to send message
164 An implementation of the hi6220 mailbox. It is used to send message
[all …]
|
| /openbmc/u-boot/drivers/power/regulator/ |
| H A D | Kconfig | 50 This config enables implementation of driver-model regulator uclass
68 This config enables implementation of driver-model regulator uclass
75 This config enables implementation of driver-model regulator uclass
83 This config enables implementation of driver-model regulator
99 This config enables implementation of driver-model regulator uclass
107 This config enables implementation of driver-model regulator uclass
114 This config enables implementation of driver-model regulator uclass
122 This config enables implementation of driver-model regulator uclass
138 This enables implementation of driver-model regulator uclass
195 This enables implementation of driver-model regulator uclass
[all …]
|
| /openbmc/linux/arch/openrisc/ |
| H A D | Kconfig | 87 Select this if your implementation features write through data caches.
104 Select this if your implementation has the Class II instruction l.ff1
110 Select this if your implementation has the Class II instruction l.fl1
116 Select this if your implementation has a hardware multiply instruction
122 Select this if your implementation has a hardware divide instruction
132 Select this if your implementation has support for the Class II
145 Select this if your implementation has support for the Class II
158 Select this if your implementation has support for the Class II
171 Select this if your implementation has support for the Class II
|
| /openbmc/u-boot/drivers/pinctrl/nxp/ |
| H A D | Kconfig | 18 this is a simple implementation, only parses the 'fsl,pins'
32 this is a simple implementation, only parses the 'fsl,pins'
46 this is a simple implementation, only parses the 'fsl,pins'
59 is different from the linux one, this is a simple implementation,
74 is different from the linux one, this is a simple implementation,
88 is different from the linux one, this is a simple implementation,
103 this is a simple implementation, only parses the 'fsl,pins'
|
| /openbmc/docs/designs/mctp/ |
| H A D | mctp-userspace.md | 8 This document describes a userspace implementation of MCTP infrastructure,
35 The proposed implementation here is to produce an MCTP "library" which provides
48 implementation does not make sense to include in the platform-agnostic library.
50 The reason for a library is to allow the same MCTP implementation to be used in
61 implementation for running on a Linux environment may be implemented through
78 MCTP implementation without requiring major structural changes to handler
124 implementation contained within a single process, using the libmctp API directly
129 implementation of those application-level handlers (programming language,
148 For the OpenBMC MCTP daemon implementation, testing models would depend on the
|
| /openbmc/linux/Documentation/core-api/ |
| H A D | genericirq.rst | 28 The original implementation of interrupt handling in Linux uses the
33 a quite universal set for the ARM interrupt handler implementation in
42 During the implementation we identified another type:
51 This split implementation of high-level IRQ handlers allows us to
56 The original general IRQ implementation used hw_interrupt_type
76 flow handler implementation also makes it simple to provide
82 IRQ-flow implementation for 'level type' interrupts and add a
83 (sub)architecture specific 'edge type' implementation.
225 handle_level_irq provides a generic implementation for level-triggered
238 handle_fasteoi_irq provides a generic implementation for interrupts,
[all …]
|
| /openbmc/linux/arch/arm/crypto/ |
| H A D | Kconfig | 32 Use an implementation of GHASH (used by the GCM AEAD chaining mode)
66 BLAKE2b, but slower than the NEON implementation of BLAKE2b.
67 There is no NEON implementation of BLAKE2s, since NEON doesn't
82 Crypto Extensions, typically this BLAKE2b implementation is
158 fastest AES implementation for single blocks. For multiple
159 blocks, the NEON bit-sliced implementation is usually faster.
161 This implementation may be vulnerable to cache timing attacks,
186 This implementation does not rely on any lookup tables so it is
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | Community-Spec-1.0 | 41 Licensee’s Implementation of the Draft Specification, except for those
48 that are within Scope for Licensee’s Implementation of the Approved
55 license to its Necessary Claims for its Implementation, except for those
64 the Implementation;
69 provided with the Implementation; or
78 Implementation, any licenses granted under this License to the Licensee
80 to a claim against Licensee regarding an Implementation, or 2) that claim
86 an Implementation of the Specification or are enforceable or (ii) that
87 an Implementation of the Specification would not infringe intellectual
248 of the specific part(s) of the Draft Specification whose implementation
[all …]
|
| /openbmc/linux/Documentation/arch/arm/samsung/ |
| H A D | gpio.rst | 2 Samsung GPIO implementation
8 This outlines the Samsung GPIO implementation and the architecture
15 The gpio implementation uses gpiolib as much as possible, only providing
27 implementation to configure pins as necessary.
|
| /openbmc/gpioplus/src/gpioplus/internal/ |
| H A D | fd.hpp | 22 * @param[in] sys - Optional underlying syscall implementation
31 * @param[in] sys - Optional underlying syscall implementation
41 * @param[in] sys - Optional underlying syscall implementation
57 /** @brief Gets the syscall interface implementation
59 * @return The syscall implementation
|
| /openbmc/phosphor-power/phosphor-regulators/test/ |
| H A D | mock_services.hpp | 38 * Implementation of the Services interface using mock system services.
156 * Mock implementation of the ErrorLogging interface.
161 * Mock implementation of the Journal interface.
166 * Mock implementation of the PresenceService interface.
171 * Mock implementation of the Sensors interface.
176 * Mock implementation of the VPD interface.
|
| /openbmc/docs/designs/ |
| H A D | bmc-service-failure-debug-and-recovery.md | 71 cannot be detected by service state alone. Implementation of resiliency by way
89 covers implementation-specific data transports such as D-Bus, which requires a
160 implementation. Where available the options for external consumer tend to be, in
185 implementation should capture any appropriate data needed to debug the need to
196 or PLDM. In order to avoid these in the implementation of mechanism 2, the host
221 The implementation of recovery mechanism 1 is already accounted for in the
233 #### Analysis of Implementation Methods on Power10 Platforms
235 The implementation of recovery mechanism 2 is limited to using existing
286 external signal. The implementation should have no IPC dependencies or
290 A trivial implementation of the daemon is
[all …]
|
| /openbmc/linux/drivers/char/xilinx_hwicap/ |
| H A D | fifo_icap.h | 13 * OR INFORMATION AS ONE POSSIBLE IMPLEMENTATION OF THIS FEATURE,
15 * THAT THIS IMPLEMENTATION IS FREE FROM ANY CLAIMS OF INFRINGEMENT,
17 * FOR YOUR IMPLEMENTATION. XILINX EXPRESSLY DISCLAIMS ANY
19 * IMPLEMENTATION, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OR
20 * REPRESENTATIONS THAT THIS IMPLEMENTATION IS FREE FROM CLAIMS OF
|
| H A D | buffer_icap.h | 13 * OR INFORMATION AS ONE POSSIBLE IMPLEMENTATION OF THIS FEATURE,
15 * THAT THIS IMPLEMENTATION IS FREE FROM ANY CLAIMS OF INFRINGEMENT,
17 * FOR YOUR IMPLEMENTATION. XILINX EXPRESSLY DISCLAIMS ANY
19 * IMPLEMENTATION, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OR
20 * REPRESENTATIONS THAT THIS IMPLEMENTATION IS FREE FROM CLAIMS OF
|
| /openbmc/u-boot/arch/arm/lib/ |
| H A D | cache.c | 22 * Default implementation:
31 * Default implementation of enable_caches()
32 * Real implementation should be in platform code
41 /* An empty stub, real implementation should be in platform code */ in invalidate_dcache_range()
45 /* An empty stub, real implementation should be in platform code */ in flush_dcache_range()
|
| /openbmc/linux/tools/testing/selftests/powerpc/tm/ |
| H A D | tm.h | 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/Documentation/networking/caif/ |
| H A D | linux_caif.rst | 29 The implementation of CAIF is divided into:
32 * CAIF Core Protocol Implementation
59 Implementation chapter
75 The Core CAIF implementation contains:
77 - Simple implementation of CAIF.
92 Implementation. The support functions include:
94 - CFPKT CAIF Packet. Implementation of CAIF Protocol Packet. The
98 The CAIF Protocol implementation contains:
|
| /openbmc/linux/security/selinux/ |
| H A D | xfrm.c | 148 * LSM hook implementation that authorizes that a flow can use a xfrm policy
170 * LSM hook implementation that authorizes that a state matches
256 * LSM hook implementation that checks and/or returns the xfrm sid for the
280 * LSM hook implementation that allocs and transfers uctx spec to xfrm_policy.
290 * LSM hook implementation that copies security data structure from old to new
312 * LSM hook implementation that frees xfrm_sec_ctx security information.
320 * LSM hook implementation that authorizes deletion of labeled policies.
328 * LSM hook implementation that allocates a xfrm_sec_state, populates it using
338 * LSM hook implementation that allocates a xfrm_sec_state and populates based
380 * LSM hook implementation that frees xfrm_state security information.
[all …]
|
| /openbmc/phosphor-dbus-monitor/src/ |
| H A D | propertywatch.hpp | 50 * Watch start interface implementation for PropertyWatch.
56 * Watch callback interface implementation for PropertyWatch.
140 /** @brief PropertyMatch implementation for PropertyWatchOfType.
149 /** @brief PropertyMatch implementation for PropertyWatchOfType.
159 /** @brief DBus agnostic implementation of interfacesAdded.
170 /** @brief PropertyMatch implementation for PropertyWatchOfType.
177 /** @brief DBus agnostic implementation of interfacesAdded.
|