Home
last modified time | relevance | path

Searched refs:derive (Results 1 – 22 of 22) sorted by relevance

/hardware/interfaces/security/secretkeeper/aidl/vts/
Dsecretkeeper_cli.rs47 #[derive(Parser, Debug)]
70 #[derive(Subcommand, Debug)]
82 #[derive(Args, Debug)]
92 #[derive(Args, Debug)]
98 #[derive(Args, Debug)]
104 #[derive(Args, Debug)]
Dsecretkeeper_test_client.rs104 #[derive(Debug)]
253 #[derive(Debug)]
/hardware/interfaces/security/keymint/aidl/default/ta/
Drpc.rs37 derive: T, field
52 self.derive.derive_bytes(context, output_len) in derive_bytes_from_hbk()
94 pub fn new(derive: T, sign_algo: CsrSigningAlgorithm) -> Self { in new()
96 derive, in new()
/hardware/interfaces/security/secretkeeper/default/src/
Dstore.rs26 #[derive(Default)]
/hardware/interfaces/security/keymint/aidl/default/
Dmain.rs41 #[derive(Debug, Clone)]
141 #[derive(Debug)]
/hardware/interfaces/security/authgraph/default/src/
Dmain.rs33 #[derive(Debug, Clone)]
/hardware/interfaces/security/authgraph/aidl/android/hardware/security/authgraph/
DArc.cddl92 ? 4 : [7], ; Key_ops: [derive key]
/hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/appendices/
DVK_NV_fragment_shader_barycentric.adoc104 extension, as we expect that shaders could derive variables decorated with
DVK_KHR_swapchain.adoc218 Trying to derive a hard limit from things like memory size is prone to
/hardware/interfaces/gnss/visibility_control/1.0/
DIGnssVisibilityControl.hal47 * status, or other information that can be used to derive user location to any entity when not
/hardware/interfaces/broadcastradio/1.0/
Dtypes.hal102 * supported and all options. The framework will derive the actual regions were
/hardware/interfaces/camera/device/3.2/
DICameraDeviceCallback.hal92 * call with ERROR_BUFFER as a no-op, and derive whether and when to notify
/hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/chapters/
Dexecutiongraphs.adoc105 * pname:basePipelineHandle is a pipeline to derive from
107 parameter to use as a pipeline to derive from
Dtessellation.adoc202 The method used to derive the number and spacing of segments is specified by
Dpipelines.adoc270 * pname:basePipelineHandle is a pipeline to derive from.
275 parameter to use as a pipeline to derive from.
1468 * pname:basePipelineHandle is a pipeline to derive from.
1473 parameter to use as a pipeline to derive from.
6145 * pname:basePipelineHandle is a pipeline to derive from.
6150 parameter to use as a pipeline to derive from.
6296 * pname:basePipelineHandle is a pipeline to derive from.
6301 parameter to use as a pipeline to derive from.
Dprimsrast.adoc1377 derive the value of [eq]#C~xy~'#.
1754 This base shading rate is then adjusted to derive a final shading rate.
2513 with the ordering used to derive the values of inputs decorated with
Dsparsemem.adoc704 implementation to derive the correct device virtual address.
Dfragops.adoc968 but requires being able to read from helper threads to derive the
Dfeatures.adoc2598 implementation supports the use of a shading rate image to derive an
/hardware/interfaces/keymaster/4.0/
DIKeymasterDevice.hal145 * key as input to a secure key derivation function used to derive a key that is used to encrypt the
171 * derive a key that is used to encrypt the private/secret key material.
285 * derive its value is acceptable. What follows is a recommended approach, to be executed
290 * assumed to be able to derive a unique hardware-bound key (HBK) which is used only for
/hardware/interfaces/graphics/common/1.0/
Dtypes.hal161 * buffer with this format, and it should derive the pixel format from
/hardware/interfaces/radio/1.0/
Dtypes.hal1762 // Following fields are used to derive the APDU ("command" and "length"