| /external/wpa_supplicant_8/wpa_supplicant/ |
| D | driver_i.h | 2 * wpa_supplicant - Internal driver interface wrappers
13 #include "drivers/driver.h"
19 if (wpa_s->driver->init2) { in wpa_drv_init()
26 return wpa_s->driver->init2(wpa_s, ifname, in wpa_drv_init()
30 if (wpa_s->driver->init) { in wpa_drv_init()
31 return wpa_s->driver->init(wpa_s, ifname); in wpa_drv_init()
38 if (wpa_s->driver->deinit) in wpa_drv_deinit()
39 wpa_s->driver->deinit(wpa_s->drv_priv); in wpa_drv_deinit()
45 if (wpa_s->driver->set_param) in wpa_drv_set_param()
46 return wpa_s->driver->set_param(wpa_s->drv_priv, param); in wpa_drv_set_param()
[all …]
|
| /external/mbedtls/docs/ |
| D | psa-driver-example-and-guide.md | 1 # PSA Cryptoprocessor driver development examples
3 …Driver Interface has only been partially implemented. As a result, the deliverables for writing a …
5 …driver system. The [PSA Driver Interface](https://github.com/Mbed-TLS/mbedtls/blob/development/doc…
6 …Driver [Developer](https://github.com/Mbed-TLS/mbedtls/blob/development/docs/proposed/psa-driver-d…
16 …Driver Interface specification specifies which cryptographic operations can be accelerated by thir…
18 There are two types of drivers: *transparent* or *opaque*. See below an excerpt from the PSA Driver…
19 …hey are typically used for hardware **accelerators**. When a transparent driver is available for a…
20 …driver is invoked for the specific [key location](https://github.com/Mbed-TLS/mbedtls/blob/develop…
22 …driver dispatch layer** (also called a driver wrapper layer). For each cryptographic operation tha…
24 …ong-term goal is for the driver dispatch layer to be auto-generated using a JSON driver descriptio…
[all …]
|
| /external/openthread/third_party/mbedtls/repo/docs/ |
| D | psa-driver-example-and-guide.md | 1 # PSA Cryptoprocessor driver development examples
3 …Driver Interface has only been partially implemented. As a result, the deliverables for writing a …
5 …driver system. The [PSA Driver Interface](https://github.com/Mbed-TLS/mbedtls/blob/development/doc…
6 …Driver [Developer](https://github.com/Mbed-TLS/mbedtls/blob/development/docs/proposed/psa-driver-d…
16 …Driver Interface specification specifies which cryptographic operations can be accelerated by thir…
18 There are two types of drivers: *transparent* or *opaque*. See below an excerpt from the PSA Driver…
19 …hey are typically used for hardware **accelerators**. When a transparent driver is available for a…
20 …driver is invoked for the specific [key location](https://github.com/Mbed-TLS/mbedtls/blob/develop…
22 …driver dispatch layer** (also called a driver wrapper layer). For each cryptographic operation tha…
24 …ong-term goal is for the driver dispatch layer to be auto-generated using a JSON driver descriptio…
[all …]
|
| /external/coreboot/src/vendorcode/intel/edk2/edk2-stable202005/MdePkg/Include/Library/ |
| D | UefiDriverEntryPoint.h | 14 ///Declare the PI Specification Revision that this driver requires to execute correctly.
19 /// Declare the EFI/UEFI Specification Revision to which this driver is implemented
30 …The entry point of PE/COFF Image for a DXE Driver, DXE Runtime Driver, DXE SMM Driver, or UEFI Dri…
32 This function is the entry point for a DXE Driver, DXE Runtime Driver, DXE SMM Driver,
33 or UEFI Driver. This function must call ProcessLibraryConstructorList() and
43 …aram ImageHandle The image handle of the DXE Driver, DXE Runtime Driver, DXE SMM Driver, or UEFI…
46 @retval EFI_SUCCESS The DXE Driver, DXE Runtime Driver, DXE SMM Driver,
47 or UEFI Driver exited normally.
65 …aram ImageHandle The image handle of the DXE Driver, DXE Runtime Driver, DXE SMM Driver, or UEFI…
68 @retval EFI_SUCCESS The DXE Driver, DXE Runtime Driver, DXE SMM Driver,
[all …]
|
| /external/coreboot/src/vendorcode/intel/edk2/UDK2017/MdePkg/Include/Library/ |
| D | UefiDriverEntryPoint.h | 20 ///Declare the PI Specification Revision that this driver requires to execute correctly.
25 /// Declare the EFI/UEFI Specification Revision to which this driver is implemented
36 …The entry point of PE/COFF Image for a DXE Driver, DXE Runtime Driver, DXE SMM Driver, or UEFI Dri…
38 This function is the entry point for a DXE Driver, DXE Runtime Driver, DXE SMM Driver,
39 or UEFI Driver. This function must call ProcessLibraryConstructorList() and
49 …aram ImageHandle The image handle of the DXE Driver, DXE Runtime Driver, DXE SMM Driver, or UEFI…
52 @retval EFI_SUCCESS The DXE Driver, DXE Runtime Driver, DXE SMM Driver,
53 or UEFI Driver exited normally.
71 …aram ImageHandle The image handle of the DXE Driver, DXE Runtime Driver, DXE SMM Driver, or UEFI…
74 @retval EFI_SUCCESS The DXE Driver, DXE Runtime Driver, DXE SMM Driver,
[all …]
|
| /external/coreboot/src/vendorcode/intel/edk2/edk2-stable202302/MdePkg/Include/Library/ |
| D | UefiDriverEntryPoint.h | 14 /// Declare the PI Specification Revision that this driver requires to execute correctly.
19 /// Declare the EFI/UEFI Specification Revision to which this driver is implemented
29 …The entry point of PE/COFF Image for a DXE Driver, DXE Runtime Driver, DXE SMM Driver, or UEFI Dri…
31 This function is the entry point for a DXE Driver, DXE Runtime Driver, DXE SMM Driver,
32 or UEFI Driver. This function must call ProcessLibraryConstructorList() and
42 …aram ImageHandle The image handle of the DXE Driver, DXE Runtime Driver, DXE SMM Driver, or UEFI…
45 @retval EFI_SUCCESS The DXE Driver, DXE Runtime Driver, DXE SMM Driver,
46 or UEFI Driver exited normally.
63 …aram ImageHandle The image handle of the DXE Driver, DXE Runtime Driver, DXE SMM Driver, or UEFI…
66 @retval EFI_SUCCESS The DXE Driver, DXE Runtime Driver, DXE SMM Driver,
[all …]
|
| /external/coreboot/src/vendorcode/intel/edk2/edk2-stable202111/MdePkg/Include/Library/ |
| D | UefiDriverEntryPoint.h | 14 ///Declare the PI Specification Revision that this driver requires to execute correctly.
19 /// Declare the EFI/UEFI Specification Revision to which this driver is implemented
30 …The entry point of PE/COFF Image for a DXE Driver, DXE Runtime Driver, DXE SMM Driver, or UEFI Dri…
32 This function is the entry point for a DXE Driver, DXE Runtime Driver, DXE SMM Driver,
33 or UEFI Driver. This function must call ProcessLibraryConstructorList() and
43 …aram ImageHandle The image handle of the DXE Driver, DXE Runtime Driver, DXE SMM Driver, or UEFI…
46 @retval EFI_SUCCESS The DXE Driver, DXE Runtime Driver, DXE SMM Driver,
47 or UEFI Driver exited normally.
65 …aram ImageHandle The image handle of the DXE Driver, DXE Runtime Driver, DXE SMM Driver, or UEFI…
68 @retval EFI_SUCCESS The DXE Driver, DXE Runtime Driver, DXE SMM Driver,
[all …]
|
| /external/coreboot/src/mainboard/ocp/tiogapass/include/ |
| D | tp_pch_gpio.h | 13 PAD_CFG_GPI_TRIG_OWN(GPP_A0, NONE, DEEP, OFF, DRIVER),
33 PAD_CFG_GPI_TRIG_OWN(GPP_A10, NONE, DEEP, OFF, DRIVER),
35 PAD_CFG_GPI_TRIG_OWN(GPP_A11, NONE, DEEP, OFF, DRIVER),
37 PAD_CFG_GPI_TRIG_OWN(GPP_A12, NONE, PLTRST, OFF, DRIVER),
39 PAD_CFG_GPI_TRIG_OWN(GPP_A13, NONE, DEEP, OFF, DRIVER),
41 PAD_CFG_GPI_TRIG_OWN(GPP_A14, NONE, DEEP, OFF, DRIVER),
43 PAD_CFG_GPI_TRIG_OWN(GPP_A15, NONE, DEEP, OFF, DRIVER),
45 PAD_CFG_GPI_TRIG_OWN(GPP_A16, NONE, DEEP, OFF, DRIVER),
47 PAD_CFG_GPI_TRIG_OWN(GPP_A17, NONE, DEEP, OFF, DRIVER),
49 PAD_CFG_GPI_TRIG_OWN(GPP_A18, NONE, DEEP, OFF, DRIVER),
[all …]
|
| /external/mbedtls/docs/architecture/testing/ |
| D | driver-interface-test-strategy.md | 1 # Mbed TLS driver interface test strategy
3 This document describes the test strategy for the driver interfaces in Mbed TLS. Mbed TLS has inter…
5 The driver interfaces are standardized through PSA Cryptography functional specifications.
7 ## Secure element driver interface testing
9 ### Secure element driver interfaces
11 #### Opaque driver interface
13 The [unified driver interface](../../proposed/psa-driver-interface.md) supports both transparent dr…
17 #### Dynamic secure element driver interface
19 The dynamic secure element driver interface (SE interface for short) is defined by [`psa/crypto_se_…
21 …driver usable by Mbed TLS, the initialization code must call `psa_register_se_driver` with a struc…
[all …]
|
| /external/openthread/third_party/mbedtls/repo/docs/architecture/testing/ |
| D | driver-interface-test-strategy.md | 1 # Mbed TLS driver interface test strategy
3 This document describes the test strategy for the driver interfaces in Mbed TLS. Mbed TLS has inter…
5 The driver interfaces are standardized through PSA Cryptography functional specifications.
7 ## Secure element driver interface testing
9 ### Secure element driver interfaces
11 #### Opaque driver interface
13 The [unified driver interface](../../proposed/psa-driver-interface.md) supports both transparent dr…
17 #### Dynamic secure element driver interface
19 The dynamic secure element driver interface (SE interface for short) is defined by [`psa/crypto_se_…
21 …driver usable by Mbed TLS, the initialization code must call `psa_register_se_driver` with a struc…
[all …]
|
| /external/wpa_supplicant_8/src/ap/ |
| D | ap_drv_ops.h | 2 * hostapd - Driver operations
128 if (!hapd->driver || !hapd->driver->send_action_cancel_wait || in hostapd_drv_send_action_cancel_wait()
131 hapd->driver->send_action_cancel_wait(hapd->drv_priv); in hostapd_drv_send_action_cancel_wait()
159 #include "drivers/driver.h"
179 if (hapd->driver == NULL || in hostapd_drv_set_countermeasures()
180 hapd->driver->hapd_set_countermeasures == NULL) in hostapd_drv_set_countermeasures()
182 return hapd->driver->hapd_set_countermeasures(hapd->drv_priv, enabled); in hostapd_drv_set_countermeasures()
190 if (hapd->driver == NULL || hapd->driver->set_sta_vlan == NULL) in hostapd_drv_set_sta_vlan()
192 return hapd->driver->set_sta_vlan(hapd->drv_priv, addr, ifname, in hostapd_drv_set_sta_vlan()
199 if (hapd->driver == NULL || hapd->driver->get_inact_sec == NULL) in hostapd_drv_get_inact_sec()
[all …]
|
| D | ap_drv_ops.c | 2 * hostapd - Driver operations
242 if (hapd->driver == NULL || hapd->driver->set_ap_wps_ie == NULL) in hostapd_reset_ap_wps_ie()
245 return hapd->driver->set_ap_wps_ie(hapd->drv_priv, NULL, NULL, NULL); in hostapd_reset_ap_wps_ie()
254 if (hapd->driver == NULL || hapd->driver->set_ap_wps_ie == NULL) in hostapd_set_ap_wps_ie()
261 ret = hapd->driver->set_ap_wps_ie(hapd->drv_priv, beacon, proberesp, in hostapd_set_ap_wps_ie()
289 * MLD peers). Thus, do not propagate the change to the driver for the in hostapd_set_authorized()
325 * driver for the link stations. in hostapd_set_sta_flags()
388 if (hapd->driver == NULL || hapd->driver->set_wds_sta == NULL) in hostapd_set_wds_sta()
394 return hapd->driver->set_wds_sta(hapd->drv_priv, addr, aid, val, in hostapd_set_wds_sta()
402 if (hapd->driver == NULL || hapd->driver->add_sta_node == NULL) in hostapd_add_sta_node()
[all …]
|
| /external/mbedtls/library/ |
| D | psa_crypto_se.h | 30 * driver persistent data.
36 * which doesn't have a driver.
40 /** The maximum number of registered secure element driver locations. */
57 /** A structure that describes a registered secure element driver.
59 * A secure element driver table entry contains a pointer to the
60 * driver's method table as well as the driver context structure.
64 /** Return the secure element driver information for a lifetime value.
67 * \param[out] p_methods On output, if there is a driver,
70 * \param[out] p_drv_context On output, if there is a driver,
76 * \p lifetime corresponds to a registered driver.
[all …]
|
| D | psa_crypto_se.c | 32 /* Driver lookup */
60 /* In the driver table, location=0 means an entry that isn't used. in psa_get_se_driver_entry()
61 * No driver has a location of 0 because it's a reserved value in psa_get_se_driver_entry()
63 * a driver entry for location 0. */ in psa_get_se_driver_entry()
76 const psa_se_drv_table_entry_t *driver) in psa_get_se_driver_methods() argument
78 return driver->methods; in psa_get_se_driver_methods()
82 psa_se_drv_table_entry_t *driver) in psa_get_se_driver_context() argument
84 return &driver->u.context; in psa_get_se_driver_context()
91 psa_se_drv_table_entry_t *driver = psa_get_se_driver_entry(lifetime); in psa_get_se_driver() local
93 *p_methods = (driver ? driver->methods : NULL); in psa_get_se_driver()
[all …]
|
| /external/openthread/third_party/mbedtls/repo/library/ |
| D | psa_crypto_se.h | 37 * driver persistent data.
43 * which doesn't have a driver.
47 /** The maximum number of registered secure element driver locations. */
64 /** A structure that describes a registered secure element driver.
66 * A secure element driver table entry contains a pointer to the
67 * driver's method table as well as the driver context structure.
71 /** Return the secure element driver information for a lifetime value.
74 * \param[out] p_methods On output, if there is a driver,
77 * \param[out] p_drv_context On output, if there is a driver,
83 * \p lifetime corresponds to a registered driver.
[all …]
|
| D | psa_crypto_se.c | 32 /* Driver lookup */
60 /* In the driver table, location=0 means an entry that isn't used. in psa_get_se_driver_entry()
61 * No driver has a location of 0 because it's a reserved value in psa_get_se_driver_entry()
63 * a driver entry for location 0. */ in psa_get_se_driver_entry()
76 const psa_se_drv_table_entry_t *driver) in psa_get_se_driver_methods() argument
78 return driver->methods; in psa_get_se_driver_methods()
82 psa_se_drv_table_entry_t *driver) in psa_get_se_driver_context() argument
84 return &driver->u.context; in psa_get_se_driver_context()
91 psa_se_drv_table_entry_t *driver = psa_get_se_driver_entry(lifetime); in psa_get_se_driver() local
93 *p_methods = (driver ? driver->methods : NULL); in psa_get_se_driver()
[all …]
|
| /external/mbedtls/tests/suites/ |
| D | test_suite_psa_crypto_driver_wrappers.data | 1 sign_hash transparent driver: in driver ECDSA SECP256R1 SHA-256
5 sign_hash transparent driver: fallback ECDSA SECP256R1 SHA-256
9 sign_hash transparent driver: error ECDSA SECP256R1 SHA-256
13 sign_hash transparent driver: fake ECDSA SECP256R1 SHA-256
17 sign_hash transparent driver: in driver RSA PKCS#1 v1.5, raw
21 sign_hash transparent driver: fallback RSA PKCS#1 v1.5, raw
25 sign_hash transparent driver: error RSA PKCS#1 v1.5, raw
29 sign_hash transparent driver: fake RSA PKCS#1 v1.5, raw
33 sign_hash transparent driver: in driver RSA PKCS#1 v1.5 SHA-256
37 sign_hash transparent driver: fallback RSA PKCS#1 v1.5 SHA-256
[all …]
|
| /external/openthread/third_party/mbedtls/repo/tests/suites/ |
| D | test_suite_psa_crypto_driver_wrappers.data | 1 sign_hash transparent driver: in driver ECDSA SECP256R1 SHA-256
5 sign_hash transparent driver: fallback ECDSA SECP256R1 SHA-256
9 sign_hash transparent driver: error ECDSA SECP256R1 SHA-256
13 sign_hash transparent driver: fake ECDSA SECP256R1 SHA-256
17 sign_hash transparent driver: in driver RSA PKCS#1 v1.5, raw
21 sign_hash transparent driver: fallback RSA PKCS#1 v1.5, raw
25 sign_hash transparent driver: error RSA PKCS#1 v1.5, raw
29 sign_hash transparent driver: fake RSA PKCS#1 v1.5, raw
33 sign_hash transparent driver: in driver RSA PKCS#1 v1.5 SHA-256
37 sign_hash transparent driver: fallback RSA PKCS#1 v1.5 SHA-256
[all …]
|
| /external/openthread/third_party/mbedtls/repo/docs/proposed/ |
| D | psa-driver-developer-guide.md | 1 PSA Cryptoprocessor driver developer's guide
5 …tate of drivers Mbed TLS, see our [PSA Cryptoprocessor driver development examples](../psa-driver-…
9 …bed TLS and drivers, refer to the [PSA Cryptoprocessor Driver Interface specification](psa-driver-…
11 …change: until further notice, we do not guarantee backward compatibility with existing driver code.
17 The PSA cryptography driver interface provides a way to build Mbed TLS with additional code that im…
21 …hey are typically used for hardware **accelerators**. When a transparent driver is available for a…
22 … smartcard, a secure enclave, etc. An opaque driver is invoked for the specific key location that …
24 ### Deliverables for a driver
26 …driver, you need to implement some functions with C linkage, and to declare these functions in a *…
28 …driver description file is JSON. The structure of this JSON file is specified in the section [“Dri…
[all …]
|
| D | psa-driver-interface.md | 1 PSA Cryptoprocessor Driver Interface
8 …tate of drivers Mbed TLS, see our [PSA Cryptoprocessor driver development examples](../psa-driver-…
12 ### Purpose of the driver interface
16 …driver interface allows implementations of the PSA Cryptography API to be built compositionally. A…
22 The PSA Cryptography driver interface supports two types of cryptoprocessors, and accordingly two t…
24 …hey are typically used for hardware **accelerators**. When a transparent driver is available for a…
25 …secure enclave, etc. An opaque driver is invoked for the specific [key location](#lifetimes-and-lo…
33 [Req.compile] It is possible to compile the code of each driver and of the core separately, and lin…
37 …ation. Driver calls are simple C function calls. Interactions with platform-specific hardware happ…
43 [Req.mechanisms] Drivers can specify which mechanisms they support. A driver's code will not be inv…
[all …]
|
| /external/mbedtls/docs/proposed/ |
| D | psa-driver-developer-guide.md | 1 PSA Cryptoprocessor driver developer's guide
5 …tate of drivers Mbed TLS, see our [PSA Cryptoprocessor driver development examples](../psa-driver-…
9 …bed TLS and drivers, refer to the [PSA Cryptoprocessor Driver Interface specification](psa-driver-…
11 …change: until further notice, we do not guarantee backward compatibility with existing driver code.
17 The PSA cryptography driver interface provides a way to build Mbed TLS with additional code that im…
21 …hey are typically used for hardware **accelerators**. When a transparent driver is available for a…
22 … smartcard, a secure enclave, etc. An opaque driver is invoked for the specific key location that …
24 ### Deliverables for a driver
26 …driver, you need to implement some functions with C linkage, and to declare these functions in a *…
28 …driver description file is JSON. The structure of this JSON file is specified in the section [“Dri…
[all …]
|
| D | psa-driver-interface.md | 1 PSA Cryptoprocessor Driver Interface
8 …tate of drivers Mbed TLS, see our [PSA Cryptoprocessor driver development examples](../psa-driver-…
12 ### Purpose of the driver interface
16 …driver interface allows implementations of the PSA Cryptography API to be built compositionally. A…
22 The PSA Cryptography driver interface supports two types of cryptoprocessors, and accordingly two t…
24 …hey are typically used for hardware **accelerators**. When a transparent driver is available for a…
25 …secure enclave, etc. An opaque driver is invoked for the specific [key location](#lifetimes-and-lo…
33 [Req.compile] It is possible to compile the code of each driver and of the core separately, and lin…
37 …ation. Driver calls are simple C function calls. Interactions with platform-specific hardware happ…
43 [Req.mechanisms] Drivers can specify which mechanisms they support. A driver's code will not be inv…
[all …]
|
| /external/swiftshader/tests/VulkanUnitTests/ |
| D | Device.cpp | 16 #include "Driver.hpp"
19 : driver(nullptr) in Device()
26 const Driver *driver, VkDevice device, VkPhysicalDevice physicalDevice, in Device() argument
28 : driver(driver) in Device()
38 driver->vkDeviceWaitIdle(device); in ~Device()
39 driver->vkDestroyDevice(device, nullptr); in ~Device()
49 const Driver *driver, VkInstance instance, std::unique_ptr<Device> &out) in CreateComputeDevice() argument
55 result = GetPhysicalDevices(driver, instance, physicalDevices); in CreateComputeDevice()
64 int queueFamilyIndex = GetComputeQueueFamilyIndex(driver, physicalDevice); in CreateComputeDevice()
94 result = driver->vkCreateDevice(physicalDevice, &deviceCreateInfo, nullptr, &device); in CreateComputeDevice()
[all …]
|
| /external/autotest/client/site_tests/network_CastTDLS/ |
| D | network_CastTDLS.py | 36 def _navigate_url(self, driver, url): argument
39 @param driver: The chromedriver instance.
42 if driver.current_url != url:
43 driver.get(url)
44 driver.refresh()
46 def _set_focus_tab(self, driver, tab_handle): argument
49 @param driver: The chromedriver instance.
50 @param tab_handle: The chrome driver handle of the tab.
52 driver.switch_to_window(tab_handle)
53 driver.get_screenshot_as_base64()
[all …]
|
| /external/clang/docs/ |
| D | DriverInternals.rst | 2 Driver Design & Internals
11 This document describes the Clang driver. The purpose of this document
12 is to describe both the motivation and design goals for the driver, as
18 The Clang driver is intended to be a production quality compiler driver
20 interface which is compatible with the gcc driver.
22 Although the driver is part of and driven by the Clang project, it is
31 The number one goal of the driver is to ease the adoption of Clang by
33 call GCC. Although this makes the driver much more complicated than
41 The driver was designed to be flexible and easily accommodate new uses
42 as we grow the clang and LLVM infrastructure. As one example, the driver
[all …]
|