diff --git a/en/device-dev/driver/driver-peripherals-face_auth-des.md b/en/device-dev/driver/driver-peripherals-face_auth-des.md index e6caa2dbd78783b209a89ee9504e5e2a977a69ad..ee46bddf934e7bd83cf3af016ecf5ff3eaefdde0 100644 --- a/en/device-dev/driver/driver-peripherals-face_auth-des.md +++ b/en/device-dev/driver/driver-peripherals-face_auth-des.md @@ -115,7 +115,7 @@ The following uses the Hi3516D V300 development board as an example to demonstra The development procedure is as follows: -1. Develop the Face_auth driver based on the HDF. The **Bind()**, **Init()**, **Release()**, and **Dispatch()** functions are used. For details about the code, see [face_auth_interface_driver.cpp](https://gitee.com/openharmony/drivers_peripheral/blob/master/face_auth/hdi_service/src/face_auth_interface_driver.cpp). +1. Develop the Face_auth driver based on the HDF. The **Bind()**, **Init()**, **Release()**, and **Dispatch()** functions are used. For details about the code, see [face_auth_interface_driver.cpp](https://gitee.com/openharmony/drivers_peripheral/tree/OpenHarmony-3.2-Beta2/face_auth/hdi_service/src/face_auth_interface_driver.cpp). ```c++ // Create an IRemoteObject object by using the custom HdfFaceAuthInterfaceHost object, which consists of the IoService object and HDI service. @@ -214,7 +214,7 @@ The development procedure is as follows: HDF_INIT(g_faceAuthInterfaceDriverEntry); ``` -2. Implement the API for obtaining the executor list. For details about the code, see [face_auth_interface_service.cpp](https://gitee.com/openharmony/drivers_peripheral/blob/master/face_auth/hdi_service/src/face_auth_interface_service.cpp). +2. Implement the API for obtaining the executor list. For details about the code, see [face_auth_interface_service.cpp](https://gitee.com/openharmony/drivers_peripheral/tree/OpenHarmony-3.2-Beta2/face_auth/hdi_service/src/face_auth_interface_service.cpp). ```c++ // Executor implementation class @@ -267,7 +267,7 @@ The development procedure is as follows: } ``` -3. Implement each function of the executor. For details about the code, see [executor_impl.cpp](https://gitee.com/openharmony/drivers_peripheral/blob/master/face_auth/hdi_service/src/executor_impl.cpp). +3. Implement each function of the executor. For details about the code, see [executor_impl.cpp](https://gitee.com/openharmony/drivers_peripheral/tree/OpenHarmony-3.2-Beta2/face_auth/hdi_service/src/executor_impl.cpp). ```c++ // Obtain the executor information. diff --git a/en/device-dev/driver/driver-peripherals-fingerprint_auth-des.md b/en/device-dev/driver/driver-peripherals-fingerprint_auth-des.md index 3faccd3bd3fa7b6facbebf557f8133108ac16cfc..d1b0b8b26a448cea8087741fcd74680bb9dc226f 100644 --- a/en/device-dev/driver/driver-peripherals-fingerprint_auth-des.md +++ b/en/device-dev/driver/driver-peripherals-fingerprint_auth-des.md @@ -4,7 +4,9 @@ ### Function -Fingerprint authentication is indispensable in identity authentication scenarios, such as device unlocking, payment, and app logins. The fingerprint authentication (Fingerprint_auth) module provides fingerprint authentication for a device after a user enrolls a fingerprint. The figure below shows the fingerprint authentication architecture. +Fingerprint authentication is indispensable in identity authentication scenarios, such as device unlocking, payment, and app logins. The fingerprint authentication (Fingerprint_auth) module provides fingerprint authentication for a device after a user enrolls a fingerprint. + +The figure below shows the fingerprint authentication architecture. The Fingerprint_auth driver is developed based on the Hardware Driver Foundation (HDF). It shields hardware differences and provides stable fingerprint authentication capabilities for the upper-layer user authentication (User_auth) framework and Fingerprint_auth service. It provides APIs for obtaining the fingerprint authentication executor list, executor information, and template information by template ID, comparing fingerprint template information of the executor and that of User_auth, enrolling or deleting fingerprints, and performing fingerprint authentication. @@ -65,11 +67,7 @@ The identity authentication consists of the User_auth framework and basic authen ### Working Principles -The fingerprint_auth driver provides stable basic fingerprint authentication capabilities for the upper-layer User_auth framework and Fingerprint_auth service to ensure successful fingerprint authentication on devices. - -The figure below shows the interaction between the Fingerprint_auth service and the Fingerprint_auth driver. - -The Fingerprint_auth service obtains the executor information by using **GetExecutorInfo()** and registers the executor with the User_auth framework. The Fingerprint_auth service exchanges information with the Fingerprint_auth driver for authentication, identification, and query through the executor APIs. +The fingerprint_auth driver provides stable basic fingerprint authentication capabilities for the upper-layer User_auth framework and Fingerprint_auth service to ensure successful fingerprint authentication on devices. The figure below shows the interaction between the Fingerprint_auth service and the Fingerprint_auth driver. The Fingerprint_auth service obtains executor information by using **GetExecutorInfo()** and registers the executor with the User_auth framework. The Fingerprint_auth service exchanges information with the Fingerprint_auth driver for authentication, identification, and query through the executor APIs. You can develop drivers to call Hardware Device Interface (HDI) APIs based on the HDF and the chip you use. **Figure 2** Interaction between the Fingerprint_auth service and Fingerprint_auth driver @@ -129,7 +127,7 @@ The following uses the Hi3516D V300 development board as an example to demonstra The development procedure is as follows: -1. Develop the Fingerprint_auth driver based on the HDF using the **Bind()**, **Init()**, **Release()**, and **Dispatch()** functions. For details about the code, see [fingerprint_auth_interface_driver.cpp](https://gitee.com/openharmony/drivers_peripheral/blob/master/fingerprint_auth/hdi_service/src/fingerprint_auth_interface_driver.cpp).
The sample code is as follows: +1. Develop the Fingerprint_auth driver based on the HDF using the **Bind()**, **Init()**, **Release()**, and **Dispatch()** functions. For details about the code, see [fingerprint_auth_interface_driver.cpp](https://gitee.com/openharmony/drivers_peripheral/tree/OpenHarmony-3.2-Beta2/fingerprint_auth/hdi_service/src/fingerprint_auth_interface_driver.cpp).
The sample code is as follows: ```c++ // Create an IRemoteObject object by using the custom HdfFingerprintAuthInterfaceHost object, which consists of the IoService object and HDI service. @@ -228,7 +226,7 @@ The development procedure is as follows: HDF_INIT(g_fingerprintAuthInterfaceDriverEntry); ``` -2. Implement the API for obtaining the executor list. For details about the code, see [fingerprint_auth_interface_service.cpp](https://gitee.com/openharmony/drivers_peripheral/blob/master/fingerprint_auth/hdi_service/src/fingerprint_auth_interface_service.cpp).
The sample code is as follows: +2. Implement the API for obtaining the executor list. For details about the code, see [fingerprint_auth_interface_service.cpp](https://gitee.com/openharmony/drivers_peripheral/tree/OpenHarmony-3.2-Beta2/fingerprint_auth/hdi_service/src/fingerprint_auth_interface_service.cpp).
The sample code is as follows: ```c++ // Executor implementation class @@ -281,7 +279,7 @@ The development procedure is as follows: } ``` -3. Implement each function of the executor. For details about the code, see [executor_impl.cpp](https://gitee.com/openharmony/drivers_peripheral/blob/master/fingerprint_auth/hdi_service/src/executor_impl.cpp).
The sample code is as follows: +3. Implement each function of the executor. For details about the code, see [executor_impl.cpp](https://gitee.com/openharmony/drivers_peripheral/tree/OpenHarmony-3.2-Beta2/fingerprint_auth/hdi_service/src/executor_impl.cpp).
The sample code is as follows: ```c++ // Obtain the executor information. @@ -364,7 +362,7 @@ The development procedure is as follows: return HDF_SUCCESS; } - // Delete a fingerprint template. + // Delete fingerprints. int32_t Delete(const std::vector& templateIdList) { IAM_LOGI("interface mock start"); diff --git a/en/device-dev/driver/driver-peripherals-pinauth-des.md b/en/device-dev/driver/driver-peripherals-pinauth-des.md index 08a3ac84a224ca046bd7b2439199011f3d934da5..e76aebb40c7628b90e141c0494b8d550f41c16b3 100644 --- a/en/device-dev/driver/driver-peripherals-pinauth-des.md +++ b/en/device-dev/driver/driver-peripherals-pinauth-des.md @@ -56,7 +56,7 @@ The identity authentication consists of User_auth and basic authentication servi The Pin_auth driver provides basic PIN authentication capabilities for the upper-layer User_auth and Pin_auth service to ensure successful PIN authentication. You can develop drivers to call Hardware Device Interface (HDI) APIs based on the HDF and the chip you use. -**Figure 2** Pin_auth service and pin_auth driver APIs +**Figure 2** Pin_auth service and Pin_auth driver APIs ![image](figures/pin_auth_service_and_driver_interaction.png "interaction between the pin_auth service and driver") @@ -110,7 +110,7 @@ The following uses the RK3568 platform as an example to demonstrate how to devel The development procedure is as follows: -1. Develop the Pin_auth driver based on the HDF. The **Bind()**, **Init()**, **Release()**, and **Dispatch()** functions are used. For details about the code, see [pin_auth_interface_driver.cpp](https://gitee.com/openharmony/drivers_peripheral/blob/master/pin_auth/hdi_service/src/pin_auth_interface_driver.cpp). +1. Develop the Pin_auth driver based on the HDF. The **Bind()**, **Init()**, **Release()**, and **Dispatch()** functions are used. For details about the code, see [pin_auth_interface_driver.cpp](https://gitee.com/openharmony/drivers_peripheral/blob/OpenHarmony-3.2-Beta2/pin_auth/hdi_service/service/src/pin_auth_interface_driver.cpp). ```c++ // Create the PinAuthInterfaceService object by using the custom HdfPinAuthInterfaceHost object, which consists of the IoService object and HDI service. @@ -212,7 +212,8 @@ The development procedure is as follows: -1. Obtain the executor list. For details about the code, see [pin_auth_interface_service.cpp](https://gitee.com/openharmony/drivers_peripheral/blob/master/pin_auth/hdi_service/src/pin_auth_interface_service.cpp). +2. Obtain the executor list. For details about the code, see, see [pin_auth_interface_service.cpp]( +https://gitee.com/openharmony/drivers_peripheral/blob/OpenHarmony-3.2-Beta2/pin_auth/hdi_service/service/src/pin_auth_interface_service.cpp). ```c++ // Executor implementation class @@ -285,7 +286,7 @@ The development procedure is as follows: -1. Implement each function of the executor. For details about the code, see [executor_impl.cpp](https://gitee.com/openharmony/drivers_peripheral/blob/master/pin_auth/hdi_service/src/executor_impl.cpp). +3. Implement each function of the executor. For details about the code, see [executor_impl.cpp](https://gitee.com/openharmony/drivers_peripheral/blob/OpenHarmony-3.2-Beta2/pin_auth/hdi_service/service/src/executor_impl.cpp). ```c++ // Obtain executor information (example only). diff --git a/en/device-dev/driver/driver-peripherals-user-auth-des.md b/en/device-dev/driver/driver-peripherals-user-auth-des.md index 757e98ede25199d9486e5f7bfaf3eb67f48bee3a..112d0bcb412f7ead10bab23ab993a09026e44916 100644 --- a/en/device-dev/driver/driver-peripherals-user-auth-des.md +++ b/en/device-dev/driver/driver-peripherals-user-auth-des.md @@ -10,7 +10,7 @@ The User_auth driver is developed based on the Hardware Driver Foundation (HDF). **Figure 1** User authentication architecture -![image](figures/user_auth_architecture.png "User authentication architecture") +![image](figures/user_auth_architecture.png "User Authentication Architecture") ### Basic Concepts The identity authentication consists of the User_auth framework and basic authentication services (including PIN authentication and facial recognition). It supports basic functions such as setting and deleting user credentials and performing authentication. @@ -141,7 +141,7 @@ The following uses the Hi3516D V300 development board as an example to demonstra The development procedure is as follows: -1. Develop the User_auth driver based on the HDF. The **Bind()**, **Init()**, **Release()**, and **Dispatch()** functions are used. For details about the code, see [user_auth_interface_driver.cpp](https://gitee.com/openharmony/drivers_peripheral/blob/master/user_auth/hdi_service/service/user_auth_interface_driver.cpp). +1. Develop the User_auth driver based on the HDF. The **Bind()**, **Init()**, **Release()**, and **Dispatch()** functions are used. For details about the code, see [user_auth_interface_driver.cpp](https://gitee.com/openharmony/drivers_peripheral/tree/OpenHarmony-3.2-Beta2/user_auth/hdi_service/service/user_auth_interface_driver.cpp). ```c++ // Create an IRemoteObject object by using the custom HdfUserAuthInterfaceHost object, which consists of the IoService object and HDI service. @@ -238,7 +238,7 @@ The development procedure is as follows: #endif ``` -2. Register the executor. For details about the code, see [user_auth_interface_service.cpp](https://gitee.com/openharmony/drivers_peripheral/blob/master/user_auth/hdi_service/service/user_auth_interface_service.cpp). +2. Register the executor. For details about the code, see [user_auth_interface_service.cpp](https://gitee.com/openharmony/drivers_peripheral/tree/OpenHarmony-3.2-Beta2/user_auth/hdi_service/service/user_auth_interface_service.cpp). ```c++ // Add an executor. @@ -260,7 +260,7 @@ The development procedure is as follows: } ``` -3. Enroll user authentication data. For details about the code, see [user_auth_interface_service.cpp](https://gitee.com/openharmony/drivers_peripheral/blob/master/user_auth/hdi_service/service/user_auth_interface_service.cpp). +3. Enroll user authentication data. For details about the code, see [user_auth_interface_service.cpp](https://gitee.com/openharmony/drivers_peripheral/tree/OpenHarmony-3.2-Beta2/user_auth/hdi_service/service/user_auth_interface_service.cpp). ```c++ // Open a session for authentication credential management. @@ -397,7 +397,7 @@ The development procedure is as follows: { IAM_LOGI("start"); if (param.challenge.size() != sizeof(uint64_t)) { - IAM_LOGE("challenge copy failed"); + IAM_LOGE("Failed to copy challenge"); return RESULT_BAD_PARAM; } GlobalLock(); @@ -410,7 +410,7 @@ The development procedure is as follows: solutionIn.authTrustLevel = param.authTrustLevel; if (memcpy_s(&solutionIn.challenge, sizeof(uint64_t), ¶m.challenge[0], param.challenge.size()) != EOK) { - IAM_LOGE("challenge copy failed"); + IAM_LOGE("Failed to copy challenge"); GlobalUnLock(); return RESULT_BAD_COPY; } @@ -456,7 +456,7 @@ The development procedure is as follows: UserAuthTokenHal authTokenHal; info.result = RequestAuthResultFunc(contextId, scheduleResultBuffer, &authTokenHal); if (info.result != RESULT_SUCCESS) { - IAM_LOGE("Failed to execute the function"); + IAM_LOGE("Failed to execute func"); DestoryBuffer(scheduleResultBuffer); GlobalUnLock(); return info.result; @@ -481,7 +481,7 @@ The development procedure is as follows: uint32_t scheduleIdNum = 0; int32_t ret = CancelContextFunc(contextId, nullptr, &scheduleIdNum); if (ret != RESULT_SUCCESS) { - IAM_LOGE("Failed to execute the function"); + IAM_LOGE("Failed to execute func"); GlobalUnLock(); return ret; }