Home
last modified time | relevance | path

Searched full:prep (Results 1 – 6 of 6) sorted by relevance

/Documentation/devicetree/bindings/arm/
Didle-states.yaml57 ..__[EXEC]__|__[PREP]__|__[ENTRY]__|__[IDLE]__|__[EXIT]__|__[EXEC]__..
71 PREP: Preparation phase before committing the hardware to idle mode
112 has not expired. The abortable nature of the PREP period can be ignored
113 if it cannot be relied upon (e.g. the PREP deadline may occur much sooner than
311 PREP phase (see diagram 1, section 2) is non-neglibigle. In such
/Documentation/security/keys/
Dcore.rst1436 * ``int (*preparse)(struct key_preparsed_payload *prep);``
1440 instantiate key). The structure pointed to by prep looks like::
1468 * ``void (*free_preparse)(struct key_preparsed_payload *prep);``
1477 * ``int (*instantiate)(struct key *key, struct key_preparsed_payload *prep);``
1483 The prep->data and prep->datalen fields will define the original payload
1496 prep->payload.data[] to key->payload.data[], with RCU-safe assignment on
1497 the first element. It will then clear prep->payload.data[] so that the
1506 The prep->data and prep->datalen fields will define the original payload
/Documentation/core-api/
Dbus-virt-phys-mapping.rst50 Now, just as an example, on the PReP (PowerPC Reference Platform), the
/Documentation/crypto/
Dasymmetric-keys.rst263 int (*parse)(struct key_preparsed_payload *prep);
Ddescore-readme.rst159 (code obtained from prep.ai.mit.edu)
/Documentation/networking/
Dnetdev-FAQ.rst210 └─ [PATCH net-next 1/3] net: some feature prep