Lines Matching refs:names

31 …implementation, without any prior arrangement other than choosing certain names and values from di…
56 * C header files defining the types required by the driver description. The names of these header f…
67 …se names consisting of the implementation's name, a slash, and additional characters. For example,…
71 …d list in an unspecified manner. This may be, for example, a list of file names passed on a comman…
90 …e capability specifies which key types and algorithms are covered and the names of the types and f…
98 * `"names"` (optional, object). A mapping from entry point names described by the `"entry_points"` …
121 …t two of these capabilities map the entry point to the different function names, the driver specif…
266 …ming that the capability does not use the `"names"` property to declare different type and entry p…
337 …y with a capability that does not use the `"names"` property to declare different type and entry p…
514 * `"names"` (optional, object). A mapping from entry point names to C function and type names, as u…
613 …y with a capability that does not use the `"names"` property to declare different type and entry p…
875 … and one for an opaque driver. You can use the mapping in capabilities' `"names"` property to arra…
1343 …bligation for them to declare functions. The core knows what the function names and argument types…