Searched full:apis (Results 1 – 25 of 1196) sorted by relevance
12345678910>>...48
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-5.10/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:
|
| /kernel/linux/linux-6.6/Documentation/driver-api/ |
| 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
|
| 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:
|
| /kernel/linux/linux-5.10/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.
15 audio and video APIs. No modern drivers should use it. Instead, audio and
16 video should be using the V4L2 and ALSA APIs, and the pipelines should
21 The APIs described here doesn't necessarily reflect the current
|
| /kernel/linux/linux-5.10/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,
|
| /kernel/linux/linux-6.6/Documentation/networking/devlink/ |
| 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
|
| /kernel/linux/linux-6.6/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
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,
|
| /kernel/linux/linux-6.6/Documentation/bpf/libbpf/ |
| 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 …]
|
| /kernel/linux/linux-5.10/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.
|
| /kernel/linux/linux-6.6/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.
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-6.6/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 */
|
| /kernel/linux/linux-5.10/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 */
|
| /kernel/linux/linux-5.10/Documentation/networking/device_drivers/ethernet/freescale/dpaa2/ |
| D | dpio-driver.rst | 20 subcomponents, and its APIs.
42 DPIO service-- provides APIs to other Linux drivers for services
144 The qbman-portal component provides APIs to do the low level hardware
151 The qbman-portal APIs are not public to other drivers, and are
157 Frame descriptor and scatter-gather definitions and the APIs used to
160 Dequeue result struct and parsing APIs are defined in dpaa2-global.h.
|
| /kernel/linux/linux-5.10/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.
|
| /kernel/linux/linux-6.6/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.
|
| /kernel/linux/linux-6.6/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.
|
| /kernel/linux/linux-5.10/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.
|
12345678910>>...48