| /openbmc/linux/Documentation/crypto/ |
| H A D | intro.rst | 8 as other data transformation mechanisms and methods to invoke these.
27 - data transformation implementations (typically ciphers) that can be
32 however, does not discuss all API calls available to data transformation
37 Note: The terms "transformation" and cipher algorithm are used
43 The transformation implementation is an actual code or interface to
44 hardware which implements a certain transformation with precisely
47 The transformation object (TFM) is an instance of a transformation
48 implementation. There can be multiple transformation objects associated
49 with a single transformation implementation. Each of those
50 transformation objects is held by a crypto API consumer or another
[all …]
|
| H A D | devel-algos.rst | 4 Registering And Unregistering Transformation
8 API. One is used to register a generic cryptographic transformation,
19 former function registers a single transformation, while the latter
20 works on an array of transformation descriptions. The latter is useful
52 This section describes the simplest of all transformation
62 filled in with proper callbacks to implement this transformation.
103 This section describes the multi-block cipher transformation
105 which operate on scatterlists of data supplied to the transformation
141 Registering And Unregistering The Transformation
144 There are multiple ways to register a HASH transformation, depending on
[all …]
|
| /openbmc/linux/include/linux/ |
| H A D | crypto.h | 190 * @cia_min_keysize: Minimum key size supported by the transformation. This is
191 * the smallest key length supported by this transformation
196 * @cia_max_keysize: Maximum key size supported by the transformation. This is
197 * the largest key length supported by this transformation
202 * @cia_setkey: Set key for the transformation. This function is used to either
204 * transformation context for programming it later. Note that this
205 * function does modify the transformation context. This function
207 * transformation object, so one must make sure the key is properly
226 * transformation context, the key might need to be re-programmed
228 * modify the transformation context, as this function may be
[all …]
|
| /openbmc/linux/net/xfrm/ |
| H A D | Kconfig | 23 tristate "Transformation user configuration interface"
26 Support for Transformation(XFRM) user configuration interface
37 Transformation(XFRM) user configuration interface like IPsec
43 tristate "Transformation virtual interface"
51 bool "Transformation sub policy support"
61 bool "Transformation migrate database"
72 bool "Transformation statistics"
76 statistics about transformation error (or almost error) factor
|
| /openbmc/linux/Documentation/networking/ |
| H A D | xfrm_proc.rst | 10 Transformation Statistics
14 dropped by the transformation code and why. These counters are defined
36 Transformation protocol specific error
40 Transformation mode specific error
91 Transformation protocol specific error
94 Transformation mode specific error
|
| /openbmc/linux/include/crypto/ |
| H A D | hash.h | 47 * @digestsize: Size of the result of the transformation. A buffer of this size
52 * @statesize: Size of the block for partial state of the transformation. A
54 * will save the partial state of the transformation into it. On the
87 * @init: **[mandatory]** Initialize the transformation context. Intended only to initialize the
88 * state of the HASH transformation at the beginning. This shall fill in
90 * transformation. No data processing happens at this point. Driver code
92 * @update: **[mandatory]** Push a chunk of data into the driver for transformation. This
95 * function must not finalize the HASH transformation by calculating the
97 * transformation. This function shall not modify the transformation
99 * transformation object. Data processing can happen synchronously
[all …]
|
| H A D | skcipher.h | 70 * @min_keysize: Minimum key size supported by the transformation. This is the
71 * smallest key length supported by this transformation algorithm.
75 * @max_keysize: Maximum key size supported by the transformation. This is the
76 * largest key length supported by this transformation algorithm.
80 * @setkey: Set key for the transformation. This function is used to either
82 * transformation context for programming it later. Note that this
83 * function does modify the transformation context. This function can
84 * be called multiple times during the existence of the transformation
97 * key was stored in transformation context, the key might need to be
99 * shall not modify the transformation context, as this function may
[all …]
|
| H A D | aead.h | 123 * transformation. A transformation may support smaller tag sizes.
128 * @setauthsize: Set authentication size for the AEAD transformation. This
130 * authentication tag to be either generated by the transformation
141 * @init: Initialize the cryptographic transformation object. This function
142 * is used to initialize the cryptographic transformation object.
144 * after the transformation context was allocated. In case the
147 * requirement of the transformation and put any software fallbacks
149 * @exit: Deinitialize the cryptographic transformation object. This is a
|
| H A D | akcipher.h | 102 * @init: Initialize the cryptographic transformation object.
104 * transformation object. This function is called only once at
105 * the instantiation time, right after the transformation context
109 * transformation and put any software fallbacks in place.
110 * @exit: Deinitialize the cryptographic transformation object. This is a
292 * Function assumes that the key is already set in the transformation. If this
|
| /openbmc/linux/include/sound/sof/ |
| H A D | channel_map.h | 16 * \brief Channel map, specifies transformation of one-to-many or many-to-one.
26 * Ext ID is the identifier of external part of the transformation. Depending
49 * More than one transformation per a single channel is allowed (in case
51 * A channel may be skipped in the transformation list, then it is filled
52 * with 0's by the transformation function.
|
| /openbmc/linux/include/crypto/internal/ |
| H A D | acompress.h | 21 * @init: Initialize the cryptographic transformation object.
23 * transformation object. This function is called only once at
24 * the instantiation time, right after the transformation context
28 * transformation and put any software fallbacks in place.
29 * @exit: Deinitialize the cryptographic transformation object. This is a
|
| /openbmc/linux/net/ipv6/ |
| H A D | Kconfig | 52 tristate "IPv6: AH transformation"
67 tristate "IPv6: ESP transformation"
82 tristate "IPv6: ESP transformation offload"
87 Support for ESP transformation offload. This makes sense
107 tristate "IPv6: IPComp transformation"
|
| /openbmc/linux/Documentation/userspace-api/media/drivers/ |
| H A D | dw100.rst | 7 programmable geometrical transformation on the input image to correct distortion
10 The transformation function is exposed by the hardware as a grid map with 16x16
|
| /openbmc/openbmc/meta-yadro/ |
| H A D | README.md | 4 address their IT transformation challenges and offering game-changing products
|
| /openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/ |
| H A D | python3-trafaret_2.1.1.bb | 1 SUMMARY = "Ultimate transformation library that supports validation, contexts and aiohttp."
|
| H A D | python3-pydbus_0.6.0.bb | 11 file://0003-Support-transformation-between-D-Bus-errors-and-exce.patch \
|
| /openbmc/linux/drivers/media/platform/nxp/dw100/ |
| H A D | Kconfig | 13 transformation on source images through a programmable dewarping map.
|
| /openbmc/linux/arch/xtensa/include/asm/ |
| H A D | kasan.h | 21 /* Offset for mem to shadow address transformation */
|
| /openbmc/linux/Documentation/timers/ |
| H A D | highres.rst | 66 Figure #3 (OLS slides p.18) illustrates the transformation.
139 Figure #4 (OLS slides p.20) illustrates the transformation.
205 Figure #5 (OLS slides p.22) illustrates the transformation.
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-printing/qpdf/ |
| H A D | qpdf_11.9.1.bb | 1 DESCRIPTION = "PDF transformation/inspection software"
|
| /openbmc/linux/net/ipv4/ |
| H A D | Kconfig | 341 tristate "IP: AH transformation"
356 tristate "IP: ESP transformation"
371 tristate "IP: ESP transformation offload"
376 Support for ESP transformation offload. This makes sense
396 tristate "IP: IPComp transformation"
|
| /openbmc/linux/Documentation/gpu/amdgpu/display/ |
| H A D | index.rst | 20 2. Perform required transformation;
|
| /openbmc/openbmc/poky/meta/recipes-support/apr/apr-util/ |
| H A D | 0001-test_transformation-Check-if-transform-is-supported-.patch | 23 /* 4. Transformation using charset aliases */
|
| /openbmc/linux/Documentation/devicetree/bindings/iio/ |
| H A D | mount-matrix.txt | 178 producing the transformation matrix.
183 mechanically mounted in an ideal way and we need no transformation):
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-graphics/fbida/files/ |
| H A D | support-jpeg-turbo.patch | 56 * This file contains image transformation routines and other utility code
76 * Lossless image transformation routines. These routines work on DCT
903 + * and transformation is not perfect. Otherwise returns TRUE.
941 + /* Return right away if -perfect is given and transformation is not perfect.
1603 + * Determine whether lossless transformation is perfectly
1604 + * possible for a specified image and transformation.
1609 + * transform: transformation identifier.
1617 + * TRUE = perfect transformation possible
1618 + * FALSE = perfect transformation not possible
1690 - JXFORM_NONE, /* no transformation */
[all …]
|