update docs

Signed-off-by: Nannie_wangli <annie.wangli@huawei.com>

en/device-dev/driver/driver-platform-mipidsi-des.md

 # MIPI DSI<a name="EN-US_TOPIC_0000001160971534"></a>
 
--   [Overview](#section16806142183217)
--   [Available APIs](#section12720125432316)
--   [Usage Guidelines](#section037231715335)
-    -   [How to Use](#section49299119344)
-    -   [Obtaining a MIPI DSI Device Handle](#section5126155683811)
-    -   [Setting MIPI DSI Configuration Parameters](#section201164274344)
-    -   [Sending/Receiving the Pointer to a Command](#section199401342173415)
-    -   [Releasing the MIPI DSI Device Handle](#section161011610357)
-
--   [Usage Example](#section17470126123520)
-
 ## Overview<a name="section16806142183217"></a>
 
 -   The Display Serial Interface \(DSI\) is a specification stipulated by the Mobile Industry Processor Interface \(MIPI\) Alliance, aiming to reduce the cost of display controllers in a mobile device. It defines a serial bus and communication protocol among the host, the source of image data, and the target device. In this way, the DSI can send pixel data or commands to peripherals \(usually LCDs or similar display devices\) in serial mode, or reads information such as status and pixel from the peripherals.

en/device-dev/driver/driver-platform-mipidsi-develop.md

 # MIPI DSI<a name="EN-US_TOPIC_0000001199825369"></a>
 
--   [Overview](#section1266787503161538)
--   [How to Develop](#section545182932161538)
-    -   [MipiDsiCntlrMethod](#section10711202141617)
-
--   [Development Example](#section1167576616161538)
 
 ## Overview<a name="section1266787503161538"></a>
 
@@ -13,31 +8,9 @@ The Display Serial Interface \(DSI\) is a specification developed by the Mobile
 **Figure  1**  Service-free mode<a name="fig207610236189"></a>  
 ![](figures/service-free-mode.png "service-free-mode")
 
-## How to Develop<a name="section545182932161538"></a>
-
-The MIPI DSI module adaptation involves the following steps:
+## Available APIs<a name="section752964871810"></a>
 
-1.  Instantiate the driver entry.
-    -   Instantiate the  **HdfDriverEntry**  structure.
-    -   Call  **HDF\_INIT**  to register the  **HdfDriverEntry**  instance with the HDF framework.
-
-2.  Configure attribute files.
-    -   Add the  **deviceNode**  information to the  **device\_info.hcs**  file.
-    -   \(Optional\) Add the  **mipidsi\_config.hcs**  file.
-
-3.  Instantiate the MIPI DSI controller object.
-    -   Initialize  **MipiDsiCntlr**.
-    -   Instantiate  **MipiDsiCntlrMethod**  in the  **MipiDsiCntlr**  object.
-
-        >![](../public_sys-resources/icon-note.gif) **NOTE:** 
-        >For details, see  [MipiDsiCntlrMethod](#section10711202141617)  and  [Table 1](#table218771071713).
-
-
-4.  Debug the driver.
-    -   \(Optional\) For new drivers, verify basic functions, for example, verify the information returned after the connect operation and whether data is successfully transmitted.
-
-
-### MipiDsiCntlrMethod<a name="section10711202141617"></a>
+MipiDsiCntlrMethod
 
 ```
 struct MipiDsiCntlrMethod {// Member functions of the core layer structure
@@ -127,6 +100,31 @@ struct MipiDsiCntlrMethod {// Member functions of the core layer structure
 </tbody>
 </table>
 
+## How to Develop<a name="section545182932161538"></a>
+
+The MIPI DSI module adaptation involves the following steps:
+
+1.  Instantiate the driver entry.
+    -   Instantiate the  **HdfDriverEntry**  structure.
+    -   Call  **HDF\_INIT**  to register the  **HdfDriverEntry**  instance with the HDF framework.
+
+2.  Configure attribute files.
+    -   Add the  **deviceNode**  information to the  **device\_info.hcs**  file.
+    -   \(Optional\) Add the  **mipidsi\_config.hcs**  file.
+
+3.  Instantiate the MIPI DSI controller object.
+    -   Initialize  **MipiDsiCntlr**.
+    -   Instantiate  **MipiDsiCntlrMethod**  in the  **MipiDsiCntlr**  object.
+
+        >![](../public_sys-resources/icon-note.gif) **NOTE:** 
+        >For details, see  [MipiDsiCntlrMethod](#section10711202141617)  and  [Table 1](#table218771071713).
+
+
+4.  Debug the driver.
+    -   \(Optional\) For new drivers, verify basic functions, for example, verify the information returned after the connect operation and whether data is successfully transmitted.
+
+
+
 ## Development Example<a name="section1167576616161538"></a>
 
 The following uses  **mipi\_tx\_hi35xx.c**  as an example to present the contents that need to be provided by the vendor to implement device functions.