| /openbmc/linux/Documentation/PCI/endpoint/ |
| H A D | pci-endpoint.rst | 34 The EPC library provides APIs to be used by the controller that can operate
35 in endpoint mode. It also provides APIs to be used by function driver/library
38 APIs for the PCI controller Driver
41 This section lists the APIs that the PCI Endpoint core provides to be used
81 EPC APIs for the PCI Endpoint Function Driver
84 This section lists the APIs that the PCI Endpoint core provides to be used
120 Other EPC APIs
123 There are other APIs provided by the EPC library. These are used for binding
125 using these APIs.
160 The EPF library provides APIs to be used by the function driver and the EPC
[all …]
|
| /openbmc/linux/Documentation/driver-api/ |
| H A D | nvmem.rst | 9 This document explains the NVMEM Framework along with the APIs provided,
99 3. NVMEM cell based consumer APIs
103 The NVMEM framework provides 3 APIs to read/write NVMEM cells::
114 `*nvmem_cell_get()` apis will get a reference to nvmem cell for a given id,
119 4. Direct NVMEM device based consumer APIs
123 To facilitate such consumers NVMEM framework provides below apis::
143 The difference between these apis and cell based apis is that these apis always
150 to the NVMEM it has obtained using the APIs mentioned in the above section.
151 The NVMEM framework provides 2 APIs to release a reference to the NVMEM::
158 Both these APIs are used to release a reference to the NVMEM and
|
| H A D | slimbus.rst | 92 Driver and Controller APIs:
113 Clock-pause APIs:
120 The framework supports regmap and read/write apis to exchange control-information
121 with a SLIMbus device. APIs can be synchronous or asynchronous.
122 The header file <linux/slimbus.h> has more documentation about messaging APIs.
124 Messaging APIs:
129 Streaming APIs:
|
| /openbmc/libpldm/ |
| H A D | CHANGELOG.md | 40 as testing. There should be no impact on users of the stable APIs/ ABIs.
45 The change removes redundant APIs in the process.
47 - Returned error values for the following stable APIs have changed their
93 improve ergonomics for the iterator APIs.
144 - Register assignment for parameters of a number of APIs changed with increased
189 - The following APIs are deprecated as unsafe due to various unfixable CWE
288 APIs.
299 - pdr: Add related decode_entity_auxiliary_names_pdr() APIs
313 - pdr: Stabilise related decode_entity_auxiliary_names_pdr() APIs
314 - platform: Rework decode/encode_pldm_message_poll_event_data() APIs
[all …]
|
| H A D | README.md | 123 off of deprecated APIs by constraining the library ABI to the stable category.
132 1. Add the required APIs to `libpldm`
133 2. Use the new APIs from `libpldm` in the dependent application or library
135 Adding APIs to a library is a difficult task. Generally, once an API is exposed
138 right, all new APIs must first be exposed in the testing category. Concretely:
140 Patches adding new APIs MUST mark them as testing and MUST NOT mark them as
201 3. Implement the public OEM APIs under `src/oem/${OEM_NAME}/`
|
| /openbmc/linux/Documentation/networking/devlink/ |
| H A D | index.rst | 10 Driver facing APIs are currently transitioning to allow more explicit
11 locking. Drivers can use the existing ``devlink_*`` set of APIs, or
12 new APIs prefixed by ``devl_*``. The older APIs handle all the locking
14 the main devlink object is itself registered. The newer ``devl_*`` APIs assume
|
| /openbmc/phosphor-logging/docs/ |
| H A D | structured-logging.md | 3 There are currently two APIs for structured logging:
44 The pre-C++20 logging APIs presented by phosphor-logging are
67 The post-C++20 logging APIs presented by phosphor-logging are `lg2::log`. The
110 The APIs can handle (and format appropriately) any data of the following types:
114 exceptions, and pointers. The APIs will also allow arbitrary type formatting for
117 The APIs also perform compile-time analysis of the arguments to give descriptive
140 The journald APIs require that keys (also called data 'headers') may only
158 be obvious that the application is writing to the journal. The `lg2` APIs detect
191 4. The previous APIs had no mechanism to generate dynamic user-friendly strings
196 data to `stdout` and some to `logging::log` APIs. `lg2` automatically detects
[all …]
|
| /openbmc/linux/Documentation/driver-api/phy/ |
| H A D | phy.rst | 7 This document explains the Generic PHY Framework along with the APIs provided,
78 to make use of it. The PHY framework provides 2 APIs to create the PHY.
88 The PHY drivers can use one of the above 2 APIs to create the PHY by passing
101 it. This framework provides the following APIs to get a reference to the PHY.
164 to the PHY it has obtained using the APIs mentioned in the above section. The
165 PHY framework provides 2 APIs to release a reference to the PHY.
172 Both these APIs are used to release a reference to the PHY and devm_phy_put
179 created using one of the following 2 APIs::
184 Both these APIs destroy the PHY and devm_phy_destroy destroys the devres
200 There are exported APIs like phy_pm_runtime_get, phy_pm_runtime_get_sync,
|
| /openbmc/docs/ |
| H A D | glossary.md | 15 OpenBMC system. OpenBMC D-Bus APIs are documented in
28 Phosphor - Informally designates OpenBMC software or APIs designed for use
32 OpenBMC provides Redfish REST APIs for platform management.
34 REST - Representational State Transfer. OpenBMC provides REST APIs.
|
| /openbmc/linux/Documentation/bpf/libbpf/ |
| H A D | libbpf_overview.rst | 15 * Provides high-level and low-level APIs for user space programs to interact
16 with BPF programs. The low-level APIs wrap all the bpf system call
22 * Provides BPF-side APIS, including BPF helper definitions, BPF maps support,
32 BPF App Lifecycle and libbpf APIs
38 a common set of data. libbpf provides APIs that user space programs can use to
72 BPF skeleton is an alternative interface to libbpf APIs for working with BPF
73 objects. Skeleton code abstract away generic libbpf APIs to significantly
88 optional, you can have more control by using libbpf APIs directly)
94 was possible to do with generic libbpf APIs is still possible even when the BPF
111 ``bpf_object_find_program_by_name()`` APIs, reducing errors due to BPF source
[all …]
|
| /openbmc/linux/Documentation/driver-api/xilinx/ |
| H A D | eemi.rst | 9 driver provides an interface to firmware APIs. Interface APIs can be
19 Any driver who wants to communicate with PMC using EEMI APIs use the
35 Refer EEMI API guide [0] for IOCTL specific parameters and other EEMI APIs.
|
| /openbmc/docs/security/ |
| H A D | network-security-considerations.md | 39 on port 443 is used to provide REST APIs and serve Web applications. These
71 - Phosphor REST APIs
89 - HTTPS for Web and REST APIs.
153 ### TCP port 443 - HTTPS REST APIs and Web application
157 - The Redfish REST APIs.
182 #### REST APIs
200 credentials to invoke Phosphor D-Bus REST APIs. Note, however, that the X-Auth
203 General security considerations for REST APIs apply:
214 and password-based authentication, and REST APIs for subsequent access.
|
| /openbmc/linux/Documentation/driver-api/thermal/ |
| H A D | cpu-cooling-api.rst | 2 CPU cooling APIs How To
14 The generic cpu cooling(freq clipping) provides registration/unregistration APIs
16 the user. The registration APIs returns the cooling device pointer.
18 1. cpu cooling APIs
21 1.1 cpufreq registration/unregistration APIs
|
| /openbmc/docs/designs/oem/google/ |
| H A D | root_of_trust.md | 1 # Google Specific APIs - A New Service Root for Google
12 Trust (RoT) chips. Google needs APIs that are not in the Redfish standard yet.
21 mechanisms. Google wants to extend the support to include REST based APIs. The
29 - Create a new service root of Google specific APIs.
79 Considered adding the new APIs as an OEM extension to the TPM resource. However,
|
| /openbmc/linux/Documentation/userspace-api/media/dvb/ |
| H A D | legacy_dvb_apis.rst | 6 Digital TV Deprecated APIs
9 The APIs described here **should not** be used on new drivers or applications.
16 The APIs described here doesn't necessarily reflect the current
|
| /openbmc/linux/arch/arm/mach-omap2/ |
| H A D | omap-smc.S | 3 * OMAP34xx and OMAP44xx secure APIs file.
36 * Low level common routine for secure HAL and PPA APIs.
37 * @id: Application ID of HAL APIs
59 * Low level common routine for secure HAL and PPA APIs via smc #1
|
| H A D | omap-secure.h | 41 /* Secure Monitor mode APIs */
52 /* Secure PPA(Primary Protected Application) APIs */
60 /* Secure RX-51 PPA (Primary Protected Application) APIs */
|
| /openbmc/linux/drivers/net/ethernet/brocade/bna/ |
| H A D | bna.h | 257 /* APIs for BNAD */
269 /* APIs for RxF */
295 /* APIs for BNA */
300 /* APIs for ENET */
305 /* APIs for BNAD */
332 /* APIs for BNA */
337 /* APIs for ENET */
342 /* APIs for BNAD */
396 /* APIs for BNAD */
|
| /openbmc/linux/Documentation/networking/device_drivers/ethernet/freescale/dpaa2/ |
| H A D | dpio-driver.rst | 21 subcomponents, and its APIs.
43 DPIO service-- provides APIs to other Linux drivers for services
145 The qbman-portal component provides APIs to do the low level hardware
152 The qbman-portal APIs are not public to other drivers, and are
158 Frame descriptor and scatter-gather definitions and the APIs used to
161 Dequeue result struct and parsing APIs are defined in dpaa2-global.h.
|
| /openbmc/linux/include/linux/ |
| H A D | extcon-provider.h | 19 /* Following APIs register/unregister the extcon device. */
27 /* Following APIs allocate/free the memory of the extcon device. */
38 * Following APIs set the connected state of each external connector.
47 * Following APIs set the property of each external connector.
|
| /openbmc/linux/Documentation/core-api/ |
| H A D | memory-allocation.rst | 7 Linux provides a variety of APIs for memory allocation. You can
14 Most of the memory allocation APIs use GFP flags to express how that
18 Diversity of the allocation APIs combined with the numerous GFP flags
26 Of course there are cases when other allocation APIs and different GFP
77 use new scope APIs described in
85 `dma_alloc*` APIs.
|
| /openbmc/linux/drivers/gpu/drm/msm/dp/ |
| H A D | dp_catalog.h | 79 /* AUX APIs */
91 /* DP Controller APIs */
125 /* DP Panel APIs */
134 /* DP Audio APIs */
|
| /openbmc/u-boot/board/intel/galileo/ |
| H A D | galileo.c | 14 * We cannot use any public GPIO APIs in <asm-generic/gpio.h> to control this
15 * pin, as these APIs will eventually call into gpio_ich6_ofdata_to_platdata()
17 * APIs which will trigger PCI enumeration process.
|
| /openbmc/linux/include/linux/usb/ |
| H A D | ch9.h | 4 * USB device APIs. These are used by the USB device model, which is
6 * Wireless USB 1.0 spec (now defunct). Linux has several APIs in C that
15 * device side APIs benefit from working well together.
|
| /openbmc/qemu/docs/devel/ |
| H A D | index-api.rst | 1 Internal QEMU APIs
4 Details about how QEMU's various internal APIs. Most of these are
|