| + | ++ | ++ | +
|---|---|---|
| + | ++ | ++ | +
| + | ++ | ++ | +
| + | ++ | ++ | +
+
+To support a chip, implement a **ChipDriver** for it. The major task is to implement the following interfaces provided by **HDF_WLAN_CORE** and **NetDevice**.
+
+| Interface| Header File| Description|
+|------|------|------|
+| HdfChipDriverFactory| `//drivers/framework/include/wifi/hdf_wlan_chipdriver_manager.h`| Factory of the **ChipDriver**, which is used to support multiple WLAN interfaces of a chip.|
+| HdfChipDriver | `//drivers/framework/include/wifi/wifi_module.h`| Manages a specific WLAN interface. Each WLAN interface corresponds to an **HdfChipDriver**.|
+|NetDeviceInterFace| `//drivers/framework/include/wifi/net_device.h`| Communicates with the protocol stack, such as sending data and setting the status of network interfaces.|
+
+To port a WLAN driver, perform the following steps:
+
+1. Create an HDF driver.
+
+You are advised to place the code file in the **//device/MySoCVendor/peripheral/wifi/chip_name/** directory.
+The file template is as follows:
+
+```C
+static int32_t HdfWlanHisiChipDriverInit(struct HdfDeviceObject *device) {
+ static struct HdfChipDriverFactory factory = CreateChipDriverFactory();
+ struct HdfChipDriverManager *driverMgr = HdfWlanGetChipDriverMgr();
+ if (driverMgr->RegChipDriver(&factory) != HDF_SUCCESS) {
+ HDF_LOGE("%s fail: driverMgr is NULL!", __func__);
+ return HDF_FAILURE;
+ }
+ return HDF_SUCCESS;
+}
+
+struct HdfDriverEntry g_hdfXXXChipEntry = {
+ .moduleVersion = 1,
+ .Init = HdfWlanXXXChipDriverInit,
+ .Release = HdfWlanXXXChipRelease,
+ .moduleName = "HDF_WIFI_CHIP_XXX"
+};
+
+HDF_INIT(g_hdfXXXChipEntry);
+```
+
+Create an **HdfChipDriverFactory** in the **CreateChipDriverFactory**. The interfaces are as follows:
+| Interface| Description|
+|------|------|
+|const char *driverName| Indicates the driver name.|
+|int32_t (*InitChip)(struct HdfWlanDevice *device)| Initializes a chip.|
+|int32_t (*DeinitChip)(struct HdfWlanDevice *device)| Deinitializes a chip.|
+|void (*ReleaseFactory)(struct HdfChipDriverFactory *factory)| Releases the **HdfChipDriverFactory** object.|
+|struct HdfChipDriver *(*Build)(struct HdfWlanDevice *device, uint8_t ifIndex)|Creates an **HdfChipDriver**. In the input parameters, **device** indicates the device information, and **ifIndex** indicates the sequence number of this interface in the chip.|
+|void (*Release)(struct HdfChipDriver *chipDriver)| Releases the **HdfChipDriver**.
+|uint8_t (*GetMaxIFCount)(struct HdfChipDriverFactory *factory)| Obtains the maximum number of interfaces supported by the current chip.|
+
+Implement the following interfaces in the **HdfChipDriver**.
+
+|Interface| Description|
+|------|------|
+|int32_t (*init)(struct HdfChipDriver *chipDriver, NetDevice *netDev)| Initializes the current network interface. The **NetDeviceInterFace** needs to be provided for the **netDev**.|
+|int32_t (*deinit)(struct HdfChipDriver *chipDriver, NetDevice *netDev)| Deinitializes the current network interface.|
+|struct HdfMac80211BaseOps *ops| Provides the WLAN basic capability interface set.|
+|struct HdfMac80211STAOps *staOps| Provides the interface set required for supporting the standalone (STA) mode.|
+|struct HdfMac80211APOps *apOps| Provides the interface set required for supporting the access point (AP) mode.|
+
+
+
+2. Compile the configuration file to describe the devices supported by the driver.
+
+Create the chip configuration file **//vendor/MyProductVendor/MyProduct/config/wifi/wlan_chip_chip_name.hcs** in the product configuration directory.
+Replace **MyProductVendor**, **MyProduct**, and **chip_name** in the path with the actual names.
+The sample code is as follows:
+```hcs
+root {
+ wlan_config {
+ chip_name :& chipList {
+ chip_name :: chipInst {
+ match_attr = "hdf_wlan_chips_chip_name"; /* Configure the matching attribute, which is used to provide the configuration root of the driver.*/
+ driverName = "driverName"; /* The value must be the same as that of driverName in HdfChipDriverFactory.*/
+ sdio {
+ vendorId = 0x0296;
+ deviceId = [0x5347];
+ }
+ }
+ }
+ }
+}
+```
+
+3. Edit the configuration file and load the driver.
+
+All device information about the product is defined in the **//vendor/MyProductVendor/MyProduct/config/device_info/device_info.hcs** file. Modify the file by adding configurations for the device named **device_wlan_chips** to the host named **network**.
+Note: The value of **moduleName** must be the same as that in the touchscreen driver.
+The sample code is as follows:
+
+```hcs
+ deviceN :: deviceNode {
+ policy = 0;
+ preload = 2;
+ moduleName = "HDF_WLAN_CHIPS";
+ deviceMatchAttr = "hdf_wlan_chips_chip_name";
+ serviceName = "driverName";
+ }
+```
+
+4. Build the driver.
+
+- Create a kernel configuration menu.
+Create a **Kconfig** file in the **//device/MySoCVendor/peripheral** directory. The file template is as follows:
+```
+config DRIVERS_WLAN_XXX
+ bool "Enable XXX WLAN Host driver"
+ default n
+ depends on DRIVERS_HDF_WIFI
+ help
+ Answer Y to enable XXX Host driver. Support chip xxx
+```
+
+Add the following sample code to the end of the **//drivers/adapter/khdf/linux/model/network/wifi/Kconfig** file to add the configuration menu to the kernel:
+```
+source "../../../../../device/MySoCVendor/peripheral/Kconfig"
+```
+
+- Create a build script.
+
+Add the following configuration to the end of the **//drivers/adapter/khdf/linux/model/network/wifi/Makefile** file:
+
+```
+HDF_DEVICE_ROOT := $(HDF_DIR_PREFIX)/../device
+obj-$(CONFIG_DRIVERS_WLAN_XXX) += $(HDF_DEVICE_ROOT)/MySoCVendor/peripheral/build/standard/
+```
+
+When **DRIVERS_WLAN_XXX** is enabled in the kernel, **makefile** in **//device/MySoCVendor/peripheral/build/standard/** is called.
+
+
+For more details, see [WLAN Development](https://gitee.com/openharmony/docs/blob/master/zh-cn/device-dev/driver/WLAN.md).
diff --git a/zh-cn/contribute/FAQ.md b/zh-cn/contribute/FAQ.md
index a6bf4efc848804b734901d919de63d96caf7227a..3ed24b895ea578cfd1b07816b5e30bb6a2d93ee2 100755
--- a/zh-cn/contribute/FAQ.md
+++ b/zh-cn/contribute/FAQ.md
@@ -2,7 +2,7 @@
[多个代码仓存在编译依赖时如何同时发起构建](#section169732563435)
-[ `Sign-off-by`相关操作](#section-sign-off)
+[ `Signed-off-by`相关操作](#section-signed-off)
[DCO校验异常处理](#section-dco)
@@ -21,7 +21,7 @@ OS\(操作系统\)开发时，经常会遇到多个代码仓的修改具有编
3. 触发构建\(详见触发构建的操作帮助\)后，构建中心会识别关联了同一Issue的PR，同时下载构建，并在代码审核通过后，同时进行合并入代码库。
-## `Sign-off-by`相关操作
+## `Signed-off-by`相关操作
### 如何在Commit中添加signoff记录
@@ -61,7 +61,7 @@ OS\(操作系统\)开发时，经常会遇到多个代码仓的修改具有编
2. Commits 中未包含 Signed-off-by信息，例如提示：
```
- 当前检测到如下commit未包含Sign-off-by信息：
+ 当前检测到如下commit未包含Signed-off-by信息：
•123123
@@ -70,7 +70,7 @@ OS\(操作系统\)开发时，经常会遇到多个代码仓的修改具有编
**解决办法**：
- 参考`Sign-off-by`相关操作，添加Sign-off-by信息。
+ 参考`Signed-off-by`相关操作，添加Signed-off-by信息。格式为：Signed-off-by: user.name