Searched full:apis (Results 1 – 25 of 575) sorted by relevance
12345678910>>...23
| /Linux-v5.15/Documentation/PCI/endpoint/ |
| 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 …]
|
| /Linux-v5.15/Documentation/driver-api/ |
| D | nvmem.rst | 9 This document explains the NVMEM Framework along with the APIs provided,
103 3. NVMEM cell based consumer APIs
107 The NVMEM framework provides 3 APIs to read/write NVMEM cells::
118 `*nvmem_cell_get()` apis will get a reference to nvmem cell for a given id,
123 4. Direct NVMEM device based consumer APIs
127 To facilitate such consumers NVMEM framework provides below apis::
147 The difference between these apis and cell based apis is that these apis always
154 to the NVMEM it has obtained using the APIs mentioned in the above section.
155 The NVMEM framework provides 2 APIs to release a reference to the NVMEM::
162 Both these APIs are used to release a reference to the NVMEM and
|
| 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:
|
| /Linux-v5.15/Documentation/driver-api/phy/ |
| 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
100 it. This framework provides the following APIs to get a reference to the PHY.
137 to the PHY it has obtained using the APIs mentioned in the above section. The
138 PHY framework provides 2 APIs to release a reference to the PHY.
145 Both these APIs are used to release a reference to the PHY and devm_phy_put
152 created using one of the following 2 APIs::
157 Both these APIs destroy the PHY and devm_phy_destroy destroys the devres
173 There are exported APIs like phy_pm_runtime_get, phy_pm_runtime_get_sync,
|
| /Linux-v5.15/Documentation/driver-api/xilinx/ |
| 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.
|
| /Linux-v5.15/Documentation/driver-api/thermal/ |
| 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
|
| /Linux-v5.15/Documentation/userspace-api/media/dvb/ |
| 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
|
| /Linux-v5.15/arch/arm/mach-omap2/ |
| 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
|
| 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 */
|
| /Linux-v5.15/drivers/net/ethernet/brocade/bna/ |
| 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 */
|
| /Linux-v5.15/Documentation/networking/device_drivers/ethernet/freescale/dpaa2/ |
| 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.
|
| /Linux-v5.15/tools/lib/traceevent/Documentation/ |
| D | libtraceevent-func_apis.txt | 8 function related tep APIs
27 Some tools may have already a way to resolve the kernel functions. These APIs
39 resolver is used by the APIs _tep_find_function()_,
48 These APIs can be used to find function name and start address, by given
127 /* These APIs use my_resolve_kernel_addr() to resolve the addr */
157 Header file to include in order to have access to the library APIs.
|
| D | libtraceevent.txt | 34 Register / unregister APIs:
51 Event related APIs:
69 APIs related to fields from event's format files:
114 Command and task related APIs:
122 Endian related APIs:
146 The libtraceevent(3) library provides APIs to access kernel tracepoint events,
162 Header file to include in order to have access to the library APIs.
164 Header file to include in order to have access to trace sequences related APIs.
|
| /Linux-v5.15/include/linux/ |
| 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.
|
| D | cgroup_rdma.h | 36 * APIs for RDMA/IB stack to publish when a device wants to
42 /* APIs for RDMA/IB stack to charge/uncharge pool specific resources */
|
| /Linux-v5.15/drivers/gpu/drm/msm/dp/ |
| D | dp_catalog.h | 78 /* AUX APIs */
89 /* DP Controller APIs */
117 /* DP Panel APIs */
126 /* DP Audio APIs */
|
| /Linux-v5.15/Documentation/core-api/ |
| 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.
|
| /Linux-v5.15/include/linux/usb/ |
| D | ch9.h | 4 * USB device APIs. These are used by the USB device model, which is
6 * Wireless USB 1.0 (spread around). Linux has several APIs in C that
15 * device side APIs benefit from working well together.
|
| /Linux-v5.15/Documentation/userspace-api/media/v4l/ |
| D | planar-apis.rst | 3 .. _planar-apis:
6 Single- and multi-planar APIs
39 Calls that distinguish between single and multi-planar APIs
|
| D | selections-common.rst | 9 :ref:`V4L2 subdev selection APIs <v4l2-subdev-selections>` are very
16 on the two APIs.
|
| /Linux-v5.15/drivers/firmware/xilinx/ |
| D | Kconfig | 20 bool "Enable Xilinx Zynq MPSoC firmware debug APIs"
23 Say yes to enable ZynqMP firmware interface debug APIs.
|
| /Linux-v5.15/drivers/net/ethernet/mellanox/mlx5/core/esw/acl/ |
| D | lgcy.h | 9 /* Eswitch acl egress external APIs */
13 /* Eswitch acl ingress external APIs */
|
| D | ofld.h | 9 /* Eswitch acl egress external APIs */
23 /* Eswitch acl ingress external APIs */
|
| /Linux-v5.15/tools/bpf/bpftool/Documentation/ |
| D | bpftool-gen.rst | 47 family of APIs).
53 APIs for working with BPF objects. Skeleton code is intended
62 passed to existing generic libbpf APIs.
94 are interoperable with generic libbpf APIs. User should
96 object, and later use libbpf APIs to keep working with
302 /* all libbpf APIs are usable */
|
| /Linux-v5.15/Documentation/admin-guide/mm/ |
| D | numa_memory_policy.rst | 14 document attempts to describe the concepts and APIs of the 2.6 memory policy
59 :ref:`Memory Policy APIs <memory_policy_apis>` section,
80 :ref:`Memory Policy APIs <memory_policy_apis>` section,
178 This mode is only used in the memory policy APIs. Internally,
189 When specified in one of the memory policy APIs, the Default mode
375 mbind() APIs [see below] always acquire the mmap_lock for write when
408 Memory Policy APIs
411 Linux supports 3 system calls for controlling memory policy. These APIS
416 the headers that define these APIs and the parameter data types for
499 this information requires "stepping outside" the memory policy APIs to use the
|
12345678910>>...23
