mirror of
https://gitee.com/openharmony/drivers_framework
synced 2024-11-23 13:00:07 +00:00
fix peripheral readme
This commit is contained in:
kevin
parent
ae17147853
commit
c79899bde0
10
README.md
10
README.md
@ -112,7 +112,7 @@ void SampleDriverRelease(struct HdfDeviceObject *deviceObject)
|
||||
}
|
||||
```
|
||||
|
||||
For details, see [HDF Overview](en-us_topic_0000001051611604.md).
|
||||
For details, see [HDF Overview](https://gitee.com/openharmony/docs/blob/master/en/device-dev/driver/hdf.md).
|
||||
|
||||
### Sensor<a name="section188637474417"></a>
|
||||
|
||||
@ -121,7 +121,7 @@ The sensor driver module is developed based on the HDF and supports functions su
|
||||
- APIs for implementing sensor driver module capabilities: Implement the capabilities of registering, loading, and deregistering sensor drivers as well as detecting sensor device depending on the HDF, normalize APIs for sensor devices of the same type, and offer APIs for parsing register configurations, abstract APIs for bus access, and abstract platform APIs.
|
||||
- APIs to be implemented by developers: Based on the HDF Configuration Source \(HCS\), implement differentiated configuration for sensors of the same type and serialized configuration of sensor device parameters, and offer APIs for some sensor device operations to simplify the sensor driver development.
|
||||
|
||||
For details, see [Sensor Driver Overview](en-us_topic_0000001078401780.md).
|
||||
For details, see [Sensor Driver Overview](https://gitee.com/openharmony/docs/blob/master/en/device-dev/driver/sensor.md).
|
||||
|
||||
### Display<a name="section161502341317"></a>
|
||||
|
||||
@ -130,7 +130,7 @@ The display driver model that is developed based on the HDF shields the differen
|
||||
- APIs for implementing display driver module capabilities: Implement the Hardware Driver Interfaces \(HDIs\) and their adaptation with the chip platform. In addition, the kernel-mode driver abstracts the common services of the panel driver and provides capabilities of initializing the panel, obtaining the panel configuration, powering on/off the panel, and implementing the backlight control.
|
||||
- APIs to be implemented by developers: Complete the board-level HCS configuration and private data configuration of the panel, or offer differentiated APIs for some components to ensure efficient development of the display driver.
|
||||
|
||||
For details, see [LCD Overview](en-us_topic_0000001052857284.md).
|
||||
For details, see [LCD Overview](https://gitee.com/openharmony/docs/blob/master/en/device-dev/driver/lcd.md).
|
||||
|
||||
### Input<a name="section12629164020115"></a>
|
||||
|
||||
@ -139,7 +139,7 @@ The input driver model is developed based on the HDF, provides unified driver AP
|
||||
- APIs for implementing input driver module capabilities: Implement the HDIs and provide capabilities of managing devices, controlling services, and reporting data. Besides, the input driver model provides a unified driver for different input devices and the capabilities of registering/unregistering an input device, reporting event data, parsing configuration, and loading a common driver.
|
||||
- APIs to be implemented by developers: Based on the provided platform driver, add the device descriptions as well as private configuration of the input device and implement differentiated APIs to greatly shorten the time required for developing input drivers.
|
||||
|
||||
For details, see [Touchscreen Overview](en-us_topic_0000001052857350.md).
|
||||
For details, see [Touchscreen Overview](https://gitee.com/openharmony/docs/blob/master/en/device-dev/driver/touchscreen.md).
|
||||
|
||||
### WLAN<a name="section11408103183114"></a>
|
||||
|
||||
@ -148,7 +148,7 @@ The WLAN module is developed based on the HDF and supports cross-OS migration, c
|
||||
- APIs for implementing WLAN driver module capabilities: Implement the APIs of the WLAN HDI layer and provide capabilities of setting/obtaining the MAC address, obtaining the feature type, and setting the transmit power for upper-layer input services, as well as the capabilities of creating/releasing a **WifiModule**, connecting to/disconnecting from a WLAN hotspot, and applying for/releasing a **NetBuf** for developers.
|
||||
- APIs to be implemented by developers: Based on the provided platform driver, complete the board-level HCS configuration as well as the differentiated WLAN configuration, and offer APIs for initializing, deregistering, enabling, and disabling a network device.
|
||||
|
||||
For details, see [WLAN Overview](en-us_topic_0000001051643558.md).
|
||||
For details, see [WLAN Overview](https://gitee.com/openharmony/docs/blob/master/en/device-dev/driver/wlan.md).
|
||||
|
||||
## Repositories Involved<a name="section1371113476307"></a>
|
||||
|
||||
|
||||
10
README_zh.md
10
README_zh.md
@ -112,7 +112,7 @@ void SampleDriverRelease(struct HdfDeviceObject *deviceObject)
|
||||
}
|
||||
```
|
||||
|
||||
HDF驱动框架详细开发请参考[驱动开发指南](zh-cn_topic_0000001051611604.md)。
|
||||
HDF驱动框架详细开发请参考[驱动开发指南](https://gitee.com/openharmony/docs/blob/master/zh-cn/device-dev/driver/HDF%E9%A9%B1%E5%8A%A8%E6%A1%86%E6%9E%B6.md)。
|
||||
|
||||
### Sensor框架模型说明<a name="section188637474417"></a>
|
||||
|
||||
@ -121,7 +121,7 @@ HDF驱动框架详细开发请参考[驱动开发指南](zh-cn_topic_00000010516
|
||||
- Sensor驱动模型基础能力部分：依赖HDF驱动框架实现Sensor器件驱动的注册，加载，去注册，器件探测等能力，提供同一类型Sensor器件驱动归一接口, 寄存器配置解析操作接口，总线访问抽象接口，平台抽象接口。
|
||||
- 开发者实现的部分：依赖HDF驱动框架的HCS\(**H**DF **C**onfiguration **S**ource\)配置管理，根据同类型Sensor差异化配置，实现Sensor器件参数序列化配置和器件部分操作接口，简化Sensor器件驱动开发。
|
||||
|
||||
基于Sensor驱动模型开发Sensor器件驱动请参考[Sensor驱动开发指南](zh-cn_topic_0000001078401780.md)。
|
||||
基于Sensor驱动模型开发Sensor器件驱动请参考[Sensor驱动开发指南](https://gitee.com/openharmony/docs/blob/master/zh-cn/device-dev/driver/SENSOR.md)。
|
||||
|
||||
### Display框架模型说明<a name="section161502341317"></a>
|
||||
|
||||
@ -130,7 +130,7 @@ HDF驱动框架详细开发请参考[驱动开发指南](zh-cn_topic_00000010516
|
||||
- Display驱动模型基础能力部分：包括HDI（**H**ardware **D**river **I**nterfaces）接口的定义及其实现框架，以及芯片平台对HDI接口的适配实现；内核驱动部分抽象了Panel驱动的公共业务，提供基础的Panel初始化、器件配置信息获取、上下电、背光设置等公共流程。
|
||||
- 驱动开发者实现的部分：需要完成板级的HCS配置及Panel私有数据配置，或者实现部分器件差异化接口，保证显示屏驱动开发高效便捷。
|
||||
|
||||
基于Display驱动模型开发LCD器件驱动请参考[LCD驱动开发指南](zh-cn_topic_0000001052857284.md)。
|
||||
基于Display驱动模型开发LCD器件驱动请参考[LCD驱动开发指南](https://gitee.com/openharmony/docs/blob/master/zh-cn/device-dev/driver/LCD.md)。
|
||||
|
||||
### Input框架模型说明<a name="section12629164020115"></a>
|
||||
|
||||
@ -139,7 +139,7 @@ HDF驱动框架详细开发请参考[驱动开发指南](zh-cn_topic_00000010516
|
||||
- Input驱动模型基础能力部分：包括Input HDI层的接口定义及公共实现，对上层输入服务提供设备管理、业务控制、数据上报等驱动能力接口；而Input驱动模型提供不同类型Input设备的归一化驱动, 包括输入设备的注册和注销、event数据的上报通道、配置信息的解析、公共驱动的加载等能力。
|
||||
- 开发者实现的部分：根据驱动模型提供的平台驱动，需要完成设备描述配置及器件私有配置，以及实现预留的器件差异化接口，借由此驱动模型，可大幅缩减Input设备驱动的开发周期。
|
||||
|
||||
基于Input驱动模型开发Touchscreen器件驱动请参考[Touchscreen驱动开发指南](zh-cn_topic_0000001052857350.md)。
|
||||
基于Input驱动模型开发Touchscreen器件驱动请参考[Touchscreen驱动开发指南](https://gitee.com/openharmony/docs/blob/master/zh-cn/device-dev/driver/TOUCHSCREEN.md)。
|
||||
|
||||
### WLAN框架模型说明<a name="section11408103183114"></a>
|
||||
|
||||
@ -148,7 +148,7 @@ HDF驱动框架详细开发请参考[驱动开发指南](zh-cn_topic_00000010516
|
||||
- WLAN驱动模型基础能力部分：包括WLAN HDI层的接口定义及公共实现，对上层输入服务提供如设置MAC地址，获取设备的MAC地址，获取特性的类型，设置发射功率等能力；对驱动开发者提供创建/释放WifiModule，关联/取消关联，申请/释放NetBuf等能力。
|
||||
- 驱动开发者实现的部分：根据驱动模型提供的平台驱动，需要完成板级的HCS配置及WLAN芯片的私有配置，以及实现预留的初始化/注销网络设备、打开/关闭网络设备等相关接口。
|
||||
|
||||
基于WLAN驱动模型开发WLAN器件驱动请参考[WLAN驱动开发指南](zh-cn_topic_0000001051643558.md)。
|
||||
基于WLAN驱动模型开发WLAN器件驱动请参考[WLAN驱动开发指南](https://gitee.com/openharmony/docs/blob/master/zh-cn/device-dev/driver/WLAN.md)。
|
||||
|
||||
## 相关仓<a name="section1371113476307"></a>
|
||||
|
||||
|
||||
Loading…
Reference in New Issue
Block a user