Searched full:api (Results 1 – 25 of 930) sorted by relevance
12345678910>>...38
| /Documentation/dev-tools/kunit/api/ |
| D | index.rst | 4 API Reference
17 This page documents the KUnit kernel testing API. It is divided into the
20 Core KUnit API
23 Documentation/dev-tools/kunit/api/test.rst
25 - Documents all of the standard testing API
27 Documentation/dev-tools/kunit/api/resource.rst
29 - Documents the KUnit resource API
31 Documentation/dev-tools/kunit/api/functionredirection.rst
33 - Documents the KUnit Function Redirection API
35 Driver KUnit API
[all …]
|
| /Documentation/crypto/ |
| D | intro.rst | 1 Kernel Crypto API Interface Specification
7 The kernel crypto API offers a rich set of cryptographic ciphers as well
9 This document contains a description of the API and provides example
12 To understand and properly use the kernel crypto API a brief explanation
13 of its structure is given. Based on the architecture, the API can be
16 the API function call documentation are given at the end.
18 The kernel crypto API refers to all algorithms as "transformations".
20 cryptographic operations, the kernel crypto API also knows compression
23 The kernel crypto API serves the following entity types:
28 called by consumers using the kernel crypto API
[all …]
|
| D | index.rst | 2 Crypto API
8 This documentation outlines the Linux kernel crypto API with its
9 concepts, details about developing cipher implementations, employment of the API
17 api-intro
20 async-tx-api
25 api
26 api-samples
|
| D | api.rst | 8 api-skcipher
9 api-aead
10 api-digest
11 api-rng
12 api-akcipher
13 api-kpp
|
| D | architecture.rst | 1 Kernel Crypto API Architecture
7 The kernel crypto API provides different API calls for the following
23 The kernel crypto API provides implementations of single block ciphers
24 and message digests. In addition, the kernel crypto API provides
60 The kernel crypto API provides synchronous and asynchronous API
63 When using the synchronous API operation, the caller invokes a cipher
64 operation which is performed synchronously by the kernel crypto API.
66 Therefore, the kernel crypto API calls work like regular function calls.
67 For synchronous operation, the set of API calls is small and
70 Asynchronous operation is provided by the kernel crypto API which
[all …]
|
| D | api-intro.rst | 4 Scatterlist Cryptographic API
10 The Scatterlist Crypto API takes page vectors (scatterlists) as
24 API.
31 Conceptually, the API layering looks like this::
33 [transform api] (user interface)
35 [algorithm api] (for registering algorithms)
37 The idea is to make the user interface and algorithm registration API
41 The API currently supports five main types of transforms: AEAD (Authenticated
52 Here's an example of how to use the API::
94 When using the API for ciphers, performance will be optimal if each
[all …]
|
| /Documentation/userspace-api/media/ |
| D | glossary.rst | 10 userspace API documentation. This is Work In Progress.
20 CEC API
21 **Consumer Electronics Control API**
23 An API designed to receive and transmit data via an HDMI
43 Digital TV API
44 **Previously known as DVB API**
46 An API designed to control a subset of the :term:`Media Hardware`
116 Media API
120 - :term:`CEC API`;
121 - :term:`Digital TV API`;
[all …]
|
| D | intro.rst | 7 This document covers the Linux Kernel to Userspace API's used by video
22 The media infrastructure API was designed to control such devices. It is
28 2. The :ref:`second part <dvbapi>` covers the API used for digital TV and
30 called as DVB API, in fact it covers several different video standards
35 3. The :ref:`third part <remote_controllers>` covers the Remote Controller API.
37 4. The :ref:`fourth part <media_controller>` covers the Media Controller API.
39 5. The :ref:`fifth part <cec>` covers the CEC (Consumer Electronics Control) API.
42 mixers, PCM capture, PCM playback, etc, which are controlled via ALSA API. For
|
| /Documentation/userspace-api/media/v4l/ |
| D | selection-api.rst | 3 .. _selection-api:
5 Cropping, composing and scaling -- the SELECTION API
12 selection-api-intro.rst
13 selection-api-targets.rst
14 selection-api-configuration.rst
15 selection-api-vs-crop-api.rst
16 selection-api-examples.rst
|
| D | selection-api-vs-crop-api.rst | 6 Comparison with old cropping API
9 The selection API was introduced to cope with deficiencies of the
10 older :ref:`CROP API <crop>`, that was designed to control simple
11 capture devices. Later the cropping API was adopted by video output
13 video signal is inserted. It should be considered as an API abuse
15 selection API makes a clear distinction between composing and cropping
18 The CROP API lacks any support for composing to and cropping from an
21 API. Cropping a smaller image from a larger one is achieved by setting
29 The selection API deals with configuration of buffer
31 the selection API the concepts of the padded target and constraints
[all …]
|
| D | planar-apis.rst | 15 Initially, V4L2 API did not support multi-planar buffers and a set of
17 constitute what is being referred to as the "multi-planar API".
19 Some of the V4L2 API calls and structures are interpreted differently,
20 depending on whether single- or multi-planar API is being used. An
31 Multi-planar API introduces new multi-planar formats. Those formats use
33 the multi-planar API and a multi-planar format. Multi-planar API calls
35 in multi-planar API structures), while the single-planar API cannot
|
| D | v4l2.rst | 7 Part I - Video for Linux API
10 This part describes the Video for Linux API version 2 (V4L2 API) specification.
41 - Subdev selections API.
49 - Original author of the V4L2 API and documentation.
58 - Original author of the V4L2 API and documentation.
62 - Documented the Digital Video timings API.
71 - Designed and documented the multi-planar API.
75 - SDR API.
91 …control ioctls, major parts of the sliced VBI API, the MPEG encoder and decoder APIs and the DV Ti…
145 Update several sections of "Common API Elements": "Opening and Closing
[all …]
|
| /Documentation/admin-guide/media/ |
| D | intro.rst | 22 - Remote Controller API;
23 - HDMI CEC API;
24 - Video4Linux API;
25 - Media controller API;
26 - Video4Linux Request API (experimental);
27 - Digital TV API (also known as DVB API).
|
| /Documentation/driver-api/ |
| D | reset.rst | 4 Reset controller API
12 The reset controller API is split into two parts:
13 the `consumer driver interface <#consumer-driver-interface>`__ (`API reference
14 <#reset-consumer-api>`__), which allows peripheral drivers to request control
16 <#reset-controller-driver-interface>`__ (`API reference
17 <#reset-controller-driver-api>`__), which is used by drivers for reset
22 functionality, restart handlers are out of scope for the reset controller API.
27 The reset controller API uses these terms with a specific meaning:
57 This interface provides an API that is similar to the kernel clock framework.
67 A stub version of this API is provided when the reset controller framework is
[all …]
|
| D | regulator.rst | 8 Voltage and current regulator API
32 The regulator API uses a number of terms which may not be familiar:
61 This offers a similar API to the kernel clock framework. Consumer
62 drivers use `get <#API-regulator-get>`__ and
63 `put <#API-regulator-put>`__ operations to acquire and release
64 regulators. Functions are provided to `enable <#API-regulator-enable>`__
65 and `disable <#API-regulator-disable>`__ the regulator and to get and
72 A stub version of this API is provided when the regulator framework is
78 The regulator API provides reference counted enabling and disabling of
153 API reference
[all …]
|
| /Documentation/userspace-api/media/dvb/ |
| D | dvbapi.rst | 7 Part II - Digital TV API
12 This API is also known as Linux **DVB API**.
22 - the Digital TV API version
23 (e. g. DVB API version 3 or DVB API version 5);
53 - Original author of the Digital TV API documentation.
57 - Original author of the Digital TV API documentation.
61 - Ported document to Docbook XML, addition of DVBv5 API, documentation gaps fix.
74 got fixed for the non-legacy API.
80 Digital TV API.
84 Add more information about DVBv5 API, better describing the frontend
|
| D | legacy_dvb_decoder_api.rst | 14 This API has originally been designed for DVB only and is therefore limited to
17 To circumvent this limitations the more versatile :ref:`V4L2 <v4l2spec>` API has
18 been designed. Which replaces this part of the DVB API.
20 Nevertheless there have been projects build around this API.
21 To ensure compatibility this API is kept as it is.
23 .. attention:: Do **not** use this API in new drivers!
27 Pipelines should be set up using the :ref:`Media Controller API<media_controller>`.
39 The API has been designed for DVB and compatible broadcastsystems.
|
| /Documentation/sound/kernel-api/ |
| D | alsa-driver-api.rst | 2 The ALSA Driver API
26 PCM API
44 PCM DMA Engine API
49 Control/Mixer API
56 AC97 Codec API
61 Virtual Master Control API
66 MIDI API
69 Raw MIDI API
73 MPU401-UART API
77 Proc Info API
[all …]
|
| /Documentation/driver-api/xilinx/ |
| D | eemi.rst | 24 IOCTL API is for device control and configuration. It is not a system
25 IOCTL but it is an EEMI API. This API can be used by master to control
27 specific. This API also manage shared device configuration.
35 Refer EEMI API guide [0] for IOCTL specific parameters and other EEMI APIs.
39 [0] Embedded Energy Management Interface (EEMI) API guide:
40 https://www.xilinx.com/support/documentation/user_guides/ug1200-eemi-api.pdf
|
| /Documentation/netlabel/ |
| D | introduction.rst | 16 layer, and the kernel security module API.
26 the NetLabel kernel security module API described below.
41 Security Module API
44 The purpose of the NetLabel security module API is to provide a protocol
46 to protocol independence, the security module API is designed to be completely
50 Detailed information about the NetLabel security module API can be found in the
|
| /Documentation/translations/zh_CN/driver-api/phy/ |
| D | phy.rst | 4 :Original: Documentation/driver-api/phy/phy.rst
77 提供了 2 个 API 来创建 PHY。
87 PHY 驱动程序可以使用上述两个 API 之一，通过传递设备指针和 phy_ops
99 控制器必须先获取对 PHY 的引用，然后才能使用 PHY。此框架提供以下 API
156 当控制器不再需要 PHY 时，它必须使用上一节中提到的 API 释放对已获得
157 的 PHY 的引用。PHY 框架提供了 2 个 API 来释放对 PHY 的引用。
164 这两个 API 都用于释放对 PHY 的引用，并且 devm_phy_put 会销毁与此
170 当创建 PHY 的驱动程序被卸载时，它应该使用以下 2 个 API 之一销毁其创
176 这两个 API 都会销毁 PHY，并且 devm_phy_destroy 会销毁与此 PHY 关
190 phy_pm_runtime_put。有导出的 API，如 phy_pm_runtime_get、
[all …]
|
| /Documentation/core-api/ |
| D | maple_tree.rst | 24 use the normal API. An :ref:`maple-tree-advanced-api` exists for more complex
34 :ref:`maple-tree-advanced-api`, but are blocked by the normal API.
40 :ref:`maple-tree-advanced-api`. This is useful for users who must guarantee a
45 .. _maple-tree-normal-api:
47 Normal API
78 worth looking at the mas_for_each() API in the :ref:`maple-tree-advanced-api`
82 not allocate memory, please see :ref:`maple-tree-advanced-api` for this use case.
132 .. _maple-tree-advanced-api:
134 Advanced API
137 The advanced API offers more flexibility and better performance at the
[all …]
|
| /Documentation/bpf/libbpf/ |
| D | libbpf_naming_convention.rst | 3 API naming convention
6 libbpf API provides access to a few logically separated groups of
9 new function or type is added to keep libbpf API clean and consistent.
11 All types and functions provided by libbpf API should have one of the
28 Another class of types and functions provided by libbpf API is "objects"
68 API documentation above. See API naming convention to choose the right
145 API documentation convention
148 The libbpf API is documented via comments above definitions in
175 description about this API. It starts with the name of the API, denoted in bold
177 function. Follow with the short description of the API. A longer form description
|
| /Documentation/sound/designs/ |
| D | compress-offload.rst | 2 ALSA Compress-Offload API
12 Since its early days, the ALSA API was defined with PCM support or
15 extend the existing API to compressed data streams.
22 mostly because of a lack of a generic API available in the mainline
25 Rather than requiring a compatibility break with an API change of the
26 ALSA PCM interface, a new 'Compressed Data' API is introduced to
29 The design of this API was inspired by the 2-year experience with the
31 API in the mainline kernel instead of the staging tree and make it
54 - Focus on main formats. This API provides support for the most
62 cycles. The new API needs to provide a generic way of listing these
[all …]
|
| /Documentation/translations/zh_CN/core-api/ |
| D | index.rst | 3 :Original: Documentation/core-api/index.rst
27 kernel-api
112 mm-api
119 dma-api
120 dma-api-howto
|
12345678910>>...38