| /OK3568_Linux_fs/kernel/lib/crypto/ |
| H A D | Kconfig | 21 This symbol can be depended upon by arch implementations of the
23 fallback, e.g., for SIMD implementations. If no arch specific
37 This symbol can be depended upon by arch implementations of the
39 fallback, e.g., for SIMD implementations. If no arch specific
63 This symbol can be depended upon by arch implementations of the
65 fallback, e.g., for SIMD implementations. If no arch specific
99 This symbol can be depended upon by arch implementations of the
101 fallback, e.g., for SIMD implementations. If no arch specific
|
| /OK3568_Linux_fs/external/chromium/licenses/ |
| H A D | LICENSE.89 | 34 "These implementations" means the copyrightable works that implement the WebM
40 run, modify and propagate the contents of these implementations of WebM, where
43 infringed by these implementations of WebM. This grant does not include claims
45 implementations. If you or your agent or exclusive licensee institute or order
48 counterclaim in a lawsuit) alleging that any of these implementations of WebM
49 or any code incorporated within any of these implementations of WebM
52 for these implementations of WebM shall terminate as of the date such
|
| /OK3568_Linux_fs/kernel/crypto/ |
| H A D | fips140-selftests.c | 14 * is somewhat helpful. Basically, all implementations of all FIPS approved
27 * There is some ambiguity about whether all implementations of each algorithm
29 * implementation. To be safe we test all implementations, except ones that can
35 * implementations in the Python packages hashlib, pycryptodome, and
119 * The optional list of implementations to test. @func will be called
591 * because this module's implementations of AES-GCM won't actually be
598 * implementations of "cmac(aes)" such as "cmac-aes-ce", as they don't
605 /* "cmac" template with all "aes" implementations */
609 /* All standalone implementations of "cmac(aes)" */
633 * implementations of "ecb(aes)" such as "ecb-aes-ce", as they don't
[all …]
|
| /OK3568_Linux_fs/kernel/fs/crypto/ |
| H A D | Kconfig | 25 # Also note that this option only pulls in the generic implementations of the
26 # algorithms, not any per-architecture optimized implementations. It is
27 # strongly recommended to enable optimized implementations too. It is safe to
28 # disable these generic implementations if corresponding optimized
29 # implementations will always be available too; for this reason, these are soft
31 # implementations if you're sure they will never be needed, though.
|
| /OK3568_Linux_fs/kernel/Documentation/admin-guide/device-mapper/ |
| H A D | dm-log.rst | 15 implementations use to perform logging operations (see
17 logging implementations are available and provide different
43 so log implementations can be done there. This is done by forwarding most
53 There are currently two userspace log implementations that leverage this
54 framework - "clustered-disk" and "clustered-core". These implementations
56 can be used in a shared-storage environment when the cluster log implementations
|
| /OK3568_Linux_fs/external/security/rk_tee_user/v2/export-ta_arm32/host_include/mbedtls/ |
| H A D | rsa_internal.h | 9 * implementations to use them in their own code, as it is conceived that the
11 * implementations.
14 * implementations should not use these functions directly, and should instead
78 * an RSA context. Alternative implementations need not
106 * an RSA context. Alternative implementations need not
132 * an RSA context. Alternative implementations need not
157 * an RSA context. Alternative implementations need not
193 * an RSA context. Alternative implementations need not
|
| /OK3568_Linux_fs/external/security/rk_tee_user/v2/export-ta_arm64/include/mbedtls/ |
| H A D | rsa_internal.h | 9 * implementations to use them in their own code, as it is conceived that the
11 * implementations.
14 * implementations should not use these functions directly, and should instead
78 * an RSA context. Alternative implementations need not
106 * an RSA context. Alternative implementations need not
132 * an RSA context. Alternative implementations need not
157 * an RSA context. Alternative implementations need not
193 * an RSA context. Alternative implementations need not
|
| /OK3568_Linux_fs/external/security/rk_tee_user/v2/export-ta_arm64/host_include/mbedtls/ |
| H A D | rsa_internal.h | 9 * implementations to use them in their own code, as it is conceived that the
11 * implementations.
14 * implementations should not use these functions directly, and should instead
78 * an RSA context. Alternative implementations need not
106 * an RSA context. Alternative implementations need not
132 * an RSA context. Alternative implementations need not
157 * an RSA context. Alternative implementations need not
193 * an RSA context. Alternative implementations need not
|
| /OK3568_Linux_fs/external/security/rk_tee_user/v2/export-ta_arm32/include/mbedtls/ |
| H A D | rsa_internal.h | 9 * implementations to use them in their own code, as it is conceived that the
11 * implementations.
14 * implementations should not use these functions directly, and should instead
78 * an RSA context. Alternative implementations need not
106 * an RSA context. Alternative implementations need not
132 * an RSA context. Alternative implementations need not
157 * an RSA context. Alternative implementations need not
193 * an RSA context. Alternative implementations need not
|
| /OK3568_Linux_fs/buildroot/dl/qt5location/git/src/location/maps/ |
| H A D | qgeomappingmanagerengine.cpp | 90 from the implementations provided by other plugins to \a managerName.
93 amongst plugin implementations.
102 itself from the implementations provided by other plugins.
105 amongst plugin implementations.
116 amongst plugin implementations.
127 amongst plugin implementations.
|
| H A D | qgeocodingmanagerengine.cpp | 99 from the implementations provided by other plugins to \a managerName.
102 amongst plugin implementations.
111 itself from the implementations provided by other plugins.
114 amongst plugin implementations.
125 amongst plugin implementations.
136 amongst plugin implementations.
|
| H A D | qgeoroutingmanagerengine.cpp | 102 from the implementations provided by other plugins to \a managerName.
105 amongst plugin implementations.
114 itself from the implementations provided by other plugins.
117 amongst plugin implementations.
128 amongst plugin implementations.
139 amongst plugin implementations.
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/arm/ |
| H A D | psci.yaml | 41 For implementations complying to PSCI versions prior to 0.2.
45 For implementations complying to PSCI 0.2.
49 For implementations complying to PSCI 0.2.
59 For implementations complying to PSCI 1.0.
63 For implementations complying to PSCI 1.0.
124 helps to implement support for OSI mode and OS implementations may choose
|
| /OK3568_Linux_fs/kernel/mm/ |
| H A D | zpool.c | 7 * This is a common frontend for memory storage pool implementations.
149 * Implementations must guarantee this to be thread-safe.
207 * Implementations must guarantee this to be thread-safe,
232 * Implementations must guarantee this to be thread-safe.
248 * Implementations must guarantee this to be thread-safe.
269 * Implementations must guarantee this to be thread-safe.
288 * Implementations must guarantee this to be thread-safe,
311 * Implementations must guarantee this to be thread-safe.
|
| /OK3568_Linux_fs/kernel/Documentation/crypto/ |
| H A D | architecture.rst | 23 The kernel crypto API provides implementations of single block ciphers
101 The kernel crypto API may provide multiple implementations of a template
103 the following implementations: AES-NI, assembler implementation, or
109 implementations providing an implementation with that name and selects
243 existing cipher implementations. The first section addresses the most
258 generic C implementations (gcm.c, aes-generic.c, ctr.c, ghash-generic.c,
262 It is possible that some streamlined cipher implementations (like
263 AES-NI) provide implementations merging aspects which in the view of the
374 Keyed message digest implementations again follow the same concept as
|
| H A D | intro.rst | 27 - data transformation implementations (typically ciphers) that can be
33 implementations (i.e. implementations of ciphers and other
|
| /OK3568_Linux_fs/kernel/Documentation/netlabel/ |
| H A D | draft-ietf-cipso-ipsecurity-01.txt | 117 not appear as the DOI identifier in any CIPSO option. Implementations
150 identifier field in the CIPSO header, implementations should assume that
160 types, implementations will require the DOI identifier as well as the tag
163 interoperability with other networks will not be an issue. Implementations
237 speed many implementations including router implementations.
334 speed many implementations including router implementations.
386 speed many implementations including router implementations.
447 parameters are required for CIPSO implementations:
543 CIPSO implementations that support only one label are not required to
544 support the parameters described above. These limited implementations are
|
| /OK3568_Linux_fs/kernel/drivers/net/ethernet/ibm/emac/ |
| H A D | emac.h | 28 /* Common registers across all EMAC implementations. */
42 /* Registers unique to EMAC4 implementations */
53 /* Registers unique to EMAC4SYNC implementations */
62 /* Common registers across all EMAC implementations. */
72 /* Registers unique to EMAC4 implementations */
76 /* Registers unique to EMAC4SYNC implementations */
|
| /OK3568_Linux_fs/kernel/Documentation/core-api/ |
| H A D | genericirq.rst | 67 Analysing a couple of architecture's IRQ subsystem implementations
75 which is normally one of the generic implementations. (This high-level
86 of existing implementations, the __do_IRQ() super-handler is still
177 Default flow implementations
184 default flow implementations. The following helper functions are
219 Default flow handler implementations
349 implementations.
392 To avoid copies of identical implementations of IRQ chips the core
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/mfd/ |
| H A D | google,cros-ec.yaml | 24 For implementations of the EC is connected through I2C.
27 For implementations of the EC is connected through SPI.
30 For implementations of the EC is connected through RPMSG.
57 Some implementations of the EC include a small nvram space used to
|
| /OK3568_Linux_fs/buildroot/package/tcllib/ |
| H A D | Config.in | 6 implementations of standard data structures to
7 implementations of common networking protocols. The intent
|
| /OK3568_Linux_fs/kernel/drivers/crypto/caam/ |
| H A D | Kconfig | 97 bool "Register algorithm implementations with the Crypto API"
128 bool "Register hash algorithm implementations with Crypto API"
137 bool "Register public key cryptography implementations with Crypto API"
|
| /OK3568_Linux_fs/kernel/drivers/net/wireless/intel/iwlwifi/ |
| H A D | iwl-drv.h | 91 * This component is also in charge of managing the several implementations of
93 * different implementations will differ in the way they implement mac80211's
117 * specific system flows implementations. For example, the bus specific probe
129 * implementations. For example, the bus specific remove function should first
|
| /OK3568_Linux_fs/buildroot/package/opengl/libgbm/ |
| H A D | Config.in | 8 # gbm implementations should select
18 # gbm implementations should select
|
| /OK3568_Linux_fs/kernel/net/ipv6/ |
| H A D | Kconfig | 58 implementations of the algorithms that RFC 8221 lists as MUST be
61 implementations of any needed algorithms when available.
73 implementations of the algorithms that RFC 8221 lists as MUST be
76 implementations of any needed algorithms when available.
|