| /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:
|
| H A D | vfio-mediated-device.rst | 19 developers had to create their own management interfaces and APIs, and then
24 The VFIO driver framework provides unified APIs for direct device access. It is
41 supports VFIO APIs. The mediated bus driver adds a mediated device to and
54 | | driver | | probe()/remove() | | APIs
249 Translation APIs for Mediated Devices
252 The following APIs are provided for translating user pfn to host pfn in a VFIO
|
| /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,
|
| /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 …]
|
| /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
|
| /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.
|
| /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
|
| /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 */
|
| /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
|
| /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.
|
| /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 */
|
| /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.
|
| /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
78 use new scope APIs described in
86 `dma_alloc*` APIs.
|
| /linux/drivers/gpu/drm/msm/dp/ |
| H A D | dp_catalog.h | 41 /* AUX APIs */
53 /* DP Controller APIs */
86 /* DP Panel APIs */
97 /* DP Audio APIs */
|
| /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.
|
| /linux/tools/lib/bpf/ |
| H A D | libbpf_legacy.h | 4 * Libbpf legacy APIs (either discouraged or deprecated, as mentioned in [0])
48 * Return actual error codes from low-level APIs directly, not just -1.
117 /* "Discouraged" APIs which don't follow consistent libbpf naming patterns.
118 * They are normally a trivial aliases or wrappers for proper APIs and are
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | planar-apis.rst | 3 .. _planar-apis:
6 Single- and multi-planar APIs
39 Calls that distinguish between single and multi-planar APIs
|
| H A D | selections-common.rst | 9 :ref:`V4L2 subdev selection APIs <v4l2-subdev-selections>` are very
16 on the two APIs.
|
| /linux/Documentation/admin-guide/mm/ |
| H A D | numa_memory_policy.rst | 12 document attempts to describe the concepts and APIs of the 2.6 memory policy
57 :ref:`Memory Policy APIs <memory_policy_apis>` section,
78 :ref:`Memory Policy APIs <memory_policy_apis>` section,
176 This mode is only used in the memory policy APIs. Internally,
187 When specified in one of the memory policy APIs, the Default mode
382 mbind() APIs [see below] always acquire the mmap_lock for write when
415 Memory Policy APIs
418 Linux supports 4 system calls for controlling memory policy. These APIS
423 the headers that define these APIs and the parameter data types for
520 this information requires "stepping outside" the memory policy APIs to use the
|
| /linux/drivers/firmware/xilinx/ |
| H A D | Kconfig | 20 bool "Enable Xilinx Zynq MPSoC firmware debug APIs"
23 Say yes to enable ZynqMP firmware interface debug APIs.
|
| /linux/drivers/net/ethernet/mellanox/mlx5/core/esw/acl/ |
| H A D | lgcy.h | 9 /* Eswitch acl egress external APIs */
13 /* Eswitch acl ingress external APIs */
|
| /linux/Documentation/networking/ |
| H A D | sriov.rst | 4 NIC SR-IOV APIs
18 Since the legacy APIs do not integrate well with the rest of the stack
|
| /linux/arch/arc/kernel/ |
| H A D | stacktrace.c | 3 * stacktrace.c : stacktracing APIs needed by rest of kernel
9 * -Implemented CONFIG_STACKTRACE APIs, primarily save_stack_trace_tsk( )
11 * -Iterator based approach to have single copy of unwinding core and APIs
163 * callbacks called by unwinder iterator to implement kernel APIs
230 * APIs expected by various kernel sub-systems
|