Searched full:api (Results 1 – 25 of 624) sorted by relevance
12345678910>>...25
| /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 | api.rst | 11 api-skcipher
12 api-aead
13 api-digest
14 api-rng
15 api-akcipher
16 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 | index.rst | 2 Linux Kernel Crypto API
8 This documentation outlines the Linux kernel crypto API with its
9 concepts, details about developing cipher implementations, employment of the API
24 api
25 api-samples
|
| D | api-skcipher.rst | 10 Symmetric Key Cipher API
14 :doc: Symmetric Key Cipher API
28 Single Block Cipher API
32 :doc: Single Block Cipher API
37 Asynchronous Block Cipher API - Deprecated
41 :doc: Asynchronous Block Cipher API
55 Synchronous Block Cipher API - Deprecated
59 :doc: Synchronous Block Cipher API
|
| D | api-intro.txt | 2 Scatterlist Cryptographic API
6 The Scatterlist Crypto API takes page vectors (scatterlists) as
19 API.
26 Conceptually, the API layering looks like this:
28 [transform api] (user interface)
30 [algorithm api] (for registering algorithms)
32 The idea is to make the user interface and algorithm registration API
36 The API currently supports five main types of transforms: AEAD (Authenticated
47 Here's an example of how to use the API:
88 When using the API for ciphers, performance will be optimal if each
[all …]
|
| D | async-tx-api.txt | 1 Asynchronous Transfers/Transforms API
8 3.1 General format of the API
26 The async_tx API provides methods for describing a chain of asynchronous
30 that is written to the API can optimize for asynchronous operation and
31 the API will fit the chain of operations to the available offload
36 The API was initially designed to offload the memory copy and
42 1/ implicit synchronous path: users of the API do not need to know if
46 2/ cross channel dependency chains: the API allows a chain of dependent
48 API automatically handles cases where the transition from one operation
55 3.1 General format of the API:
[all …]
|
| D | userspace-if.rst | 7 The concepts of the kernel crypto API visible to kernel space is fully
9 crypto API high level discussion for the in-kernel use cases applies
17 crypto API. A working example of this description is libkcapi that can
21 Some details of the in-kernel kernel crypto API aspects do not apply to
23 and asynchronous invocations. The user space API call is fully
28 User Space API General Remarks
31 The kernel crypto API is accessible from user space. Currently, the
56 A cipher is accessed with the same name as done for the in-kernel API
60 To interact with the kernel crypto API, a socket must be created by the
65 The following API calls assume that the socket descriptor is already
[all …]
|
| D | api-rng.rst | 7 Crypto API Random Number API
11 :doc: Random number generator API
|
| /Documentation/media/uapi/v4l/ |
| D | selection-api.rst | 10 .. _selection-api:
12 Cropping, composing and scaling -- the SELECTION API
19 selection-api-intro.rst
20 selection-api-targets.rst
21 selection-api-configuration.rst
22 selection-api-vs-crop-api.rst
23 selection-api-examples.rst
|
| D | selection-api-vs-crop-api.rst | 13 Comparison with old cropping API
16 The selection API was introduced to cope with deficiencies of the
17 older :ref:`CROP API <crop>`, that was designed to control simple
18 capture devices. Later the cropping API was adopted by video output
20 video signal is inserted. It should be considered as an API abuse
22 selection API makes a clear distinction between composing and cropping
25 The CROP API lacks any support for composing to and cropping from an
28 API. Cropping a smaller image from a larger one is achieved by setting
36 The selection API deals with configuration of buffer
38 the selection API the concepts of the padded target and constraints
[all …]
|
| D | planar-apis.rst | 22 Initially, V4L2 API did not support multi-planar buffers and a set of
24 constitute what is being referred to as the "multi-planar API".
26 Some of the V4L2 API calls and structures are interpreted differently,
27 depending on whether single- or multi-planar API is being used. An
38 Multi-planar API introduces new multi-planar formats. Those formats use
40 the multi-planar API and a multi-planar format. Multi-planar API calls
42 in multi-planar API structures), while the single-planar API cannot
|
| D | v4l2.rst | 14 Part I - Video for Linux API
17 This part describes the Video for Linux API version 2 (V4L2 API) specification.
53 - Subdev selections API.
61 - Original author of the V4L2 API and documentation.
69 - Original author of the V4L2 API and documentation.
73 - Documented the Digital Video timings API.
81 - Designed and documented the multi-planar API.
85 - SDR API.
101 …control ioctls, major parts of the sliced VBI API, the MPEG encoder and decoder APIs and the DV Ti…
155 Update several sections of "Common API Elements": "Opening and Closing
[all …]
|
| /Documentation/media/kapi/ |
| D | v4l2-clocks.rst | 8 This is a temporary API and it shall be replaced by the generic
9 clock API, when the latter becomes widely available.
17 clock API usage. E.g. V4L2 has to support clock provider driver unregistration
19 a V4L2 clock helper API has been developed and is provided to bridge and
22 The API consists of two parts: two functions to register and unregister a V4L2
24 a clock object, similar to the respective generic clock API calls:
27 clock operations that will be called when clock users invoke respective API
31 architectures this API will be removed.
|
| /Documentation/media/ |
| 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/media/uapi/dvb/ |
| D | dvbapi.rst | 15 Part II - Digital TV API
20 This API is also known as Linux **DVB API**.
30 - the Digital TV API version
31 (e. g. DVB API version 3 or DVB API version 5);
66 - Original author of the Digital TV API documentation.
70 - Original author of the Digital TV API documentation.
74 - Ported document to Docbook XML, addition of DVBv5 API, documentation gaps fix.
87 got fixed for the non-legacy API.
93 Digital TV API.
97 Add more information about DVBv5 API, better describing the frontend
|
| D | intro.rst | 43 The first API for Digital TV cards we used at Convergence in late 1999 was an
44 extension of the Video4Linux API which was primarily developed for frame
50 standard Linux Digital TV API. As a commitment to the development of terminals
54 Convergence provided a first implementation of the Linux Digital TV API.
55 Convergence was the maintainer of the Linux Digital TV API in the early
58 Now, the API is maintained by the LinuxTV community (i.e. you, the reader
59 of this document). The Linux Digital TV API is constantly reviewed and
129 The Linux Digital TV API lets you control these hardware components through
169 API include files
173 Digital TV API include files should be included in application sources with a
[all …]
|
| /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/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/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/driver-api/xilinx/ |
| D | eemi.rst | 51 IOCTL API is for device control and configuration. It is not a system
52 IOCTL but it is an EEMI API. This API can be used by master to control
54 specific. This API also manage shared device configuration.
62 Refer EEMI API guide [0] for IOCTL specific parameters and other EEMI APIs.
66 [0] Embedded Energy Management Interface (EEMI) API guide:
67 https://www.xilinx.com/support/documentation/user_guides/ug1200-eemi-api.pdf
|
| /Documentation/ |
| D | DMA-API.txt | 7 This document describes the DMA API. For a more gentle introduction
8 of the API (and actual examples), see Documentation/DMA-API-HOWTO.txt.
10 This API is split into two pieces. Part I describes the basic API.
14 should only use the API described in part I.
188 This API returns the mask that the platform requires to
240 Not all memory regions in a machine can be mapped by this API.
242 physical memory. Since this API does not provide any scatter/gather
245 this API should be obtained from sources which guarantee it to be
268 line width. In order for memory mapped by this API to operate
272 may not be known at compile time, the API will not enforce this
[all …]
|
| /Documentation/driver-api/ |
| 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/block/ |
| D | inline-encryption.rst | 11 To allow for testing, we also want a crypto API fallback when actual
14 of the underlying devices if present, or else fall back to crypto API
77 need for a crypto API fallback, or if we are want to use IE with layered
82 crypto API. Blk-crypto maintains an internal KSM that serves as the crypto
83 API fallback.
94 to the crypto API *before* sending the bio to the device.
99 request queue that the bio is being submitted to (or the crypto API fallback
108 crypto API fallback KSM in blk-crypto performs crypto on the device's behalf.
121 then it will program it into blk-crypto's internal KSM for crypto API
126 programmed into a keyslot in the *crypto API fallback* KSM.
[all …]
|
| /Documentation/power/regulator/ |
| D | design.rst | 2 Regulator API design notes
6 of the design considerations which impact the regulator API design.
20 The API should make no changes to the hardware state unless it has
36 The consumer API should be structured so that these use cases are
|
12345678910>>...25