Driver services are objects of capabilities provided by HDF driver devices to external systems and are managed by the HDF in a unified manner. Driver service management involves publishing and obtaining driver services.
Driver services are objects of capabilities provided by HDF driver devices to external systems and are managed by the HDF in a unified manner. Driver service management involves publishing and obtaining driver services.
The HDF uses the **policy** field in the configuration file to define policies for drivers to publish services externally. The values this field are as follows:
The HDF uses the **policy** field in the configuration file to define policies for a driver to provide services externally. The values this field are as follows:
```
```
typedef enum {
typedef enum {
/* The driver does not provide services. */
/* The driver does not provide services. */
...
@@ -37,28 +37,28 @@ The table below describes the APIs for driver service management.
...
@@ -37,28 +37,28 @@ The table below describes the APIs for driver service management.
**Table 1** APIs for driver service management
**Table 1** APIs for driver service management
| API| Description|
| API| Description|
| -------- | -------- |
| -------- | -------- |
| int32_t (\*Bind)(struct HdfDeviceObject \*deviceObject); | Binds a service API to the HDF. You need to implement the **Bind()** function.|
| int32_t (\*Bind)(struct HdfDeviceObject \*deviceObject) | Binds a service API to the HDF. You need to implement the **Bind()** function.|
| const struct HdfObject \*DevSvcManagerClntGetService(const char \*svcName); | Obtains a driver service.|
| int HdfDeviceSubscribeService(<br>struct HdfDeviceObject \*deviceObject, const char \*serviceName, struct SubscriberCallback callback); | Subscribes to a driver service.|
|int HdfDeviceSubscribeService(struct HdfDeviceObject \*deviceObject, const char \*serviceName, struct SubscriberCallback callback) | Subscribes to a driver service.|
## How to Develop
## How to Develop
The development procedure is as follows:
The development procedure is as follows:
1. Define the services to be provided by the driver.
1. Define the services to be published by the driver.
```
```
Define the driver service structure.
// Define the driver service structure.
struct ISampleDriverService {
struct ISampleDriverService {
struct IDeviceIoService ioService; // The first member must be of the IDeviceIoService type.
struct IDeviceIoService ioService; // The first member must be of the IDeviceIoService type.
int32_t (*ServiceA)(void); // API of the first driver service.
int32_t (*ServiceA)(void); // API of the first driver service.
int32_t (*ServiceB)(uint32_t inputCode); // API of the second driver service. You can add more as required.
int32_t (*ServiceB)(uint32_t inputCode); // API of the second driver service. You can add more as required.
};
};
Implement the driver service APIs.
// Implement the driver service APIs.
int32_t SampleDriverServiceA(void)
int32_t SampleDriverServiceA(void)
{
{
// You need to implement the service logic.
// You need to implement the service logic.
...
@@ -73,7 +73,7 @@ The development procedure is as follows:
...
@@ -73,7 +73,7 @@ The development procedure is as follows:
```
```
2. Bind the driver service to the HDF and implement the **Bind()** function in the **HdfDriverEntry** structure.
2. Bind the driver service to the HDF and implement the **Bind()** function in the **HdfDriverEntry** structure.
If the kernel mode is unaware of the time for loading drivers on the same host, use the subscription mechanism provided by the HDF to subscribe to the drivers. After the drivers are loaded, the HDF sends the driver services to the subscriber. The implementation is as follows:
If the kernel mode is unaware of the time for loading drivers on the same host, use the subscription mechanism provided by the HDF to subscribe to the drivers. After the drivers are loaded, the HDF publishes the driver services to the subscriber.
```
The implementation is as follows:
// Callback invoked to return the driver services after the subscribed driver is loaded.
// object is the pointer to the private data of the subscriber, and service is the pointer to the subscribed service object.