HOME
Shop
  • English
  • 简体中文
HOME
Shop
  • English
  • 简体中文
  • Product Series

    • FPGA+ARM

      • GM-3568JHF

        • 1. Introduction

          • About GM-3568JHF
        • 2. Quick Start

          • 00 Introduction
          • 01 Environment Setup
          • 02 Compilation Instructions
          • 03 Flashing Guide
          • 04 Debug Tools
          • 05 Software Update
          • 06 View Information
          • 07 Test Commands
          • 08 App Compilation
          • 09 Source Code Acquisition
        • 3. Peripherals and Interfaces

          • 01 USB
          • 02 Display and Touch
          • 03 Ethernet
          • 04 WIFI
          • 05 Bluetooth
          • 06 TF-Card
          • 07 Audio
          • 08 Serial Port
          • 09 CAN
          • 10 RTC
        • 4. Application Development

          • 01 UART read and write case
          • 02 Key detection case
          • 03 LED light flashing case
          • 04 MIPI screen detection case
          • 05 Read USB device information example
          • 06 FAN Detection Case
          • 07 FPGA FSPI Communication Case
          • 08 FPGA DMA read and write case
          • 09 GPS debugging case
          • 10 Ethernet Test Cases
          • 11 RS485 reading and writing examples
          • 12 FPGA IIC read and write examples
          • 13 PN532 NFC card reader case
          • 14 TF card reading and writing case
        • 5. QT Development

          • 01 ARM64 cross compiler environment construction
          • 02 QT program added automatic startup service
        • 6. RKNN_NPU Development

          • 01 RK3568 NPU Overview
          • 02 Development Environment Setup
          • Run Official YOLOv5 Example
          • Model Conversion Detailed Explanation
          • Run Custom Model on Board
        • 7. FPGA Development

          • ARM and FPGA Communication
          • /fpga-arm/GM-3568JHF/FPGA/ch02-FPGA-Development-Manual.html
        • 8. Others

          • 01 Modification of the root directory file system
          • 02 System auto-start service
        • 9. Download

          • Download Resources
    • ShimetaPi

      • M4-R1

        • 1. Introduction

          • 1.1 About M4-R1
        • 2. Quick Start

          • 2.1 OpenHarmony Overview
          • 2.2 Image Burning
          • 2.3 Development Environment Preparation
          • 2.4 Hello World Application
        • 3. Application Development

          • 3.1 Getting Started

            • 3.1.1 ArkTS Language Overview
            • 3.1.2 UI Components (Part 1)
            • 3.1.3 UI Components (Part 2)
            • 3.1.4 UI Components (Part 3)
          • 3.2 Advanced

            • 3.2.1 Getting Started Guide
            • 3.2.2 Usage of Third Party Libraries
            • 3.2.3 Deployment of the Application
            • 3.2.4 Factory Reset
            • 3.2.5 System Debug
            • 3.2.6 APP Stability Testing
            • 3.2.7 Application Testing
          • 3.3 Getting Docs

            • 3.3.1 Official Website Information
          • 3.4 Development Instructions

            • 3.4.1 Full SDK
            • 3.4.2 Introduction of Third Party Libraries
            • 3.4.3 Introduction of HDC Tool
            • 3.4.4 Restore Factory Mode
            • 3.4.5 Update System API
          • 3.5 First Application

            • 3.5.1 First ArkTS App
          • 3.6 Application Demo

            • 3.6.1 UART Tool
            • 3.6.2 Graphics Tablet
            • 3.6.3 Digital Clock
            • 3.6.4 WIFI Tool
        • 4. Device Development

          • 4.1 Ubuntu Environment Development

            • 4.1.1 Environment Setup
            • 4.1.2 Download Source Code
            • 4.1.3 Compile Source Code
          • 4.2 Using DevEco Device Tool

            • 4.2.1 Tool Introduction
            • 4.2.2 Environment Construction
            • 4.2.3 Import SDK
            • 4.2.4 Function Introduction
        • 5. Peripherals and Interfaces

          • 5.1 Raspberry Pi Interfaces
          • 5.2 GPIO Interface
          • 5.3 I2C Interface
          • 5.4 SPI Communication
          • 5.5 PWM Control
          • 5.6 Serial Port Communication
          • 5.7 TF Card Slot
          • 5.8 Display Screen
          • 5.9 Touch Screen
          • 5.10 Audio
          • 5.11 RTC
          • 5.12 Ethernet
          • 5.13 M.2
          • 5.14 MINI PCIE
          • 5.15 Camera
          • 5.16 WIFI BT
          • 5.17 HAT
        • 6. FAQ

          • 6.1 Download Link
      • M5-R1

        • 1. Introduction

          • M5-R1 Development Documentation
        • 2. Quick Start

          • OpenHarmony Overview
          • Image Burning
          • Development Environment Preparation
          • Hello World Application and Deployment
        • 3. Peripherals and Interfaces

          • 3.1 Raspberry Pi Interfaces
          • 3.2 GPIO Interface
          • 3.3 I2C Interface
          • 3.4 SPI Communication
          • 3.5 PWM Control
          • 3.6 Serial Port Communication
          • 3.7 TF Card Slot
          • 3.8 Display Screen
          • 3.9 Touch Screen
          • 3.10 Audio
          • 3.11 RTC
          • 3.12 Ethernet
          • 3.13 M.2
          • 3.14 MINI PCIE
          • 3.15 Camera
          • 3.16 WIFI BT
          • 3.17 HAT
        • 4. Application Development

          • 4.1 Getting Started

            • 4.1.1 ArkTS Language Overview
            • 4.1.2 UI Components (Part 1)
            • 4.1.3 UI Components (Part 2)
            • 4.1.4 UI Components (Part 3)
          • 4.2 Advanced

            • 4.2.1 Getting Started Guide
            • 4.2.2 Usage of Third Party Libraries
            • 4.2.3 Deployment of the Application
            • 4.2.4 Factory Reset
            • 4.2.5 System Debug
            • 4.2.6 APP Stability Testing
            • 4.2.7 Application Testing
        • 5. Device Development

          • 5.1 Environment Setup
          • 5.2 Download Source Code
          • 5.3 Compile Source Code
        • 6. Download

          • Data Download
    • OpenHarmony

      • SC-3568HA

        • 1. Introduction

          • 1.1 About SC-3568HA
        • 2. Quick Start

          • 2.1 OpenHarmony Overview
          • 2.2 Image Burning
          • 2.3 Development Environment Preparation
          • 2.4 Hello World Application
        • 3. Application Development

          • 3.1 ArkUI

            • 3.1.1 ArkTS Language Overview
            • 3.1.2 UI Components (Part 1)
            • 3.1.3 UI Components (Part 2)
            • 3.1.4 UI Components (Part 3)
          • 3.2 Advanced

            • 3.2.1 Getting Started Guide
            • 3.2.2 Usage of Third Party Libraries
            • 3.2.3 Deployment of the Application
            • 3.2.4 Factory Reset
            • 3.2.5 System Debug
            • 3.2.6 APP Stability Testing
            • 3.2.7 Application Testing
        • 4. Device Development

          • 4.1 Environment Setup
          • 4.2 Download Source Code
          • 4.3 Compile Source Code
        • 5. Peripherals and Interfaces

          • 5.1 Raspberry Pi Interfaces
          • 5.2 GPIO Interface
          • 5.3 I2C Interface
          • 5.4 SPI Communication
          • 5.5 PWM Control
          • 5.6 Serial Port Communication
          • 5.7 TF Card Slot
          • 5.8 Display Screen
          • 5.9 Touch Screen
          • 5.10 Audio
          • 5.11 RTC
          • 5.12 Ethernet
          • 5.13 M.2
          • 5.14 MINI PCIE
          • 5.15 Camera
          • 5.16 WIFI BT
          • 5.17 HAT
        • 6. FAQ

          • 6.1 Download Link
      • M-K1HSE

        • 1. Introduction

          • 1.1 Product Introduction
        • 2. Quick Start

          • 2.1 Debug Tool Installation
          • 2.2 Development Environment Setup
          • 2.3 Source Code Download
          • 2.4 Build Instructions
          • 2.5 Flashing Guide
          • 2.6 APT Update Sources
          • 2.7 View Board Info
          • 2.8 CLI LED and Key Test
          • 2.9 GCC Build Programs
        • 3. Application Development

          • 3.1 Basic Application Development

            • 3.1.1 Development Environment Preparation
            • 3.1.2 First Application HelloWorld
            • 3.1.3 Develop HAR Package
          • 3.2 Peripheral Application Cases

            • 3.2.1 UART Read/Write
            • 3.2.2 Key Demo
            • 3.2.3 LED Flash
        • 4. Peripherals and Interfaces

          • 4.1 Standard Peripherals

            • 4.1.1 USB
            • 4.1.2 Display and Touch
            • 4.1.3 Ethernet
            • 4.1.4 WIFI
            • 4.1.5 Bluetooth
            • 4.1.6 TF Card
            • 4.1.7 Audio
            • 4.1.8 Serial Port
            • 4.1.9 CAN
            • 4.1.10 RTC
          • 4.2 Interfaces

            • 4.2.1 Audio
            • 4.2.2 RS485
            • 4.2.3 Display
            • 4.2.4 Touch
        • 5. System Customization Development

          • 5.1 System Porting
          • 5.2 System Customization
          • 5.3 Driver Development
          • 5.4 System Debugging
          • 5.5 OTA Upgrade
        • 6. Download

          • 6.1 Download
    • EVS-Camera

      • CF-NRS1

        • 1. Introduction

          • 1.1 About CF-NRS1
          • 1.2 Event-Based Concepts
          • 1.3 Quick Start
          • 1.4 Resources
        • 2. Development

          • 2.1 Development Overview

            • 2.1.1 Shimetapi Hybrid Camera SDK Introduction
          • 2.2 Environment & API

            • 2.2.1 Environment Overview
            • 2.2.2 Development API Overview
          • 2.3 Linux Development

            • 2.3.1 Linux SDK Introduction
            • 2.3.2 Linux SDK API
            • 2.3.3 Linux Algorithm
            • 2.3.4 Linux Algorithm API
          • 2.4 Service & Web

            • 2.4.1 EVS Server
            • 2.4.2 Time Server
            • 2.4.3 EVS Web
        • 3. Download

          • 3.1 Download
        • 4. Common Problems

          • 4.1 Common Problems
      • CF-CRA2

        • 1. Introduction

          • 1.1 About CF-CRA2
        • 2. Download

          • 2.1 Download
      • EVS Module

        • 1. Related Concepts
        • 2. Hardware Preparation and Environment Configuration
        • 3. Example Program User Guide
        • Resources Download
    • AI-model

      • 1684XB-32T

        • 1. Introduction

          • AIBOX-1684XB-32 Introduction
        • 2. Quick Start

          • First time use
          • Network Configuration
          • Disk usage
          • Memory allocation
          • Fan Strategy
          • Firmware Upgrade
          • Cross-Compilation
          • Model Quantization
        • 3. Application Development

          • 3.1 Development Introduction

            • Sophgo SDK Development
            • SOPHON-DEMO Introduction
          • 3.2 Large Language Models

            • Deploying Llama3 Example
            • /ai-model/AIBOX-1684XB-32/application-development/LLM/Sophon_LLM_api_server-Development-AIBOX-1684XB-32.html
            • /ai-model/AIBOX-1684XB-32/application-development/LLM/MiniCPM-V-2_6-AIBOX-1684XB-32.html
            • /ai-model/AIBOX-1684XB-32/application-development/LLM/Qwen-2-5-VL-demo-Development-AIBOX-1684XB-32.html
            • /ai-model/AIBOX-1684XB-32/application-development/LLM/Qwen-3-chat-demo-Development-AIBOX-1684XB-32.html
            • /ai-model/AIBOX-1684XB-32/application-development/LLM/Qwen3-Qwen Agent-MCP.html
            • /ai-model/AIBOX-1684XB-32/application-development/LLM/Qwen3-langchain-AI Agent.html
          • 3.3 Deep Learning

            • ResNet (Image Classification)
            • LPRNet (License Plate Recognition)
            • SAM (Universal Image Segmentation Foundation Model)
            • YOLOv5 (Object Detection)
            • OpenPose (Human Keypoint Detection)
            • PP-OCR (Optical Character Recognition)
        • 4. Download

          • Resource Download
      • 1684X-416T

        • 1. Introduction

          • AIBOX-1684X-416 Introduction
        • 2. Demo Simple Operation Guide

          • Simple instructions for using shimeta smart monitoring demo
      • RDK-X5

        • 1. Introduction

          • RDK-X5 Hardware Introduction
        • 2. Quick Start

          • RDK-X5 Quick Start
        • 3. Application Development

          • 3.1 AI Online Model Development

            • AI Online Development - Experiment01
            • AI Online Development - Experiment02
            • AI Online Development - Experiment03
            • AI Online Development - Experiment04
            • AI Online Development - Experiment05
            • AI Online Development - Experiment06
          • 3.2 Large Language Models (Voice)

            • Voice LLM Application - Experiment01
            • Voice LLM Application - Experiment02
            • Voice LLM Application - Experiment03
            • Voice LLM Application - Experiment04
            • Voice LLM Application - Experiment05
            • Voice LLM Application - Experiment06
          • 3.3 40pin-IO Development

            • 40pin IO Development - Experiment01
            • 40pin IO Development - Experiment02
            • 40pin IO Development - Experiment03
            • 40pin IO Development - Experiment04
            • 40pin IO Development - Experiment05
            • 40pin IO Development - Experiment06
            • 40pin IO Development - Experiment07
          • 3.4 USB Module Development

            • USB Module Usage - Experiment01
            • USB Module Usage - Experiment02
          • 3.5 Machine Vision

            • Machine Vision Technology Development - Experiment01
            • Machine Vision Technology Development - Experiment02
            • Machine Vision Technology Development - Experiment03
            • Machine Vision Technology Development - Experiment04
          • 3.6 ROS2 Base Development

            • ROS2 Basic Development - Experiment01
            • ROS2 Basic Development - Experiment02
            • ROS2 Basic Development - Experiment03
            • ROS2 Basic Development - Experiment04
      • RDK-S100

        • 1. Introduction

          • 1.1 About RDK-S100
        • 2. Quick Start

          • 2.1 First Use
        • 3. Application Development

          • 3.1 AI Online Model Development

            • 3.1.1 Volcano Engine Doubao AI
            • 3.1.2 Image Analysis
            • 3.1.3 Multimodal Visual Analysis
            • 3.1.4 Multimodal Image Comparison
            • 3.1.5 Multimodal Document Analysis
            • 3.1.6 Camera AI Vision Analysis
          • 3.2 Large Language Models

            • 3.2.1 Speech Recognition
            • 3.2.2 Voice Conversation
            • 3.2.3 Multimodal Image Analysis
            • 3.2.4 Multimodal Image Comparison
            • 3.2.5 Multimodal Document Analysis
            • 3.2.6 Multimodal Vision Application
          • 3.3 40pin-IO Development

            • 3.3.1 GPIO Output LED Blink
            • 3.3.2 GPIO Input
            • 3.3.3 Key Control LED
            • 3.3.4 PWM Output
            • 3.3.5 Serial Output
            • 3.3.6 I2C Experiment
          • 3.4 USB Module Development

            • 3.4.1 USB Voice Module
            • 3.4.2 Sound Source Localization
          • 3.5 Machine Vision

            • 3.5.1 USB Camera
            • 3.5.2 Image Processing Basics
            • 3.5.3 Object Detection
            • 3.5.4 Image Segmentation
          • 3.6 ROS2 Base Development

            • 3.6.1 Environment Setup
            • 3.6.2 Create and Build Workspace
            • 3.6.3 ROS2 Topic Communication
            • 3.6.4 ROS2 Camera Application
    • Core-Board

      • C-3568BQ

        • 1. Introduction

          • C-3568BQ Introduction
      • C-3588LQ

        • 1. Introduction

          • C-3588LQ Introduction
      • GC-3568JBAF

        • 1. Introduction

          • GC-3568JBAF Introduction
      • C-K1BA

        • 1. Introduction

          • C-K1BA Introduction

12 Screen

1 Introduction to Mainstream Display Interfaces

In embedded devices and consumer electronics products. MIPI DSI, eDP, and HDMI are three mainstream display interfaces used to transmit video data and commands between hosts (such as SoCs, computers, motherboards) and displays (screens).

Each has its own focus and is applied in different fields. Below I will introduce these three display methods in detail.

1.1 MIPI Screen

MIPI (Mobile Industry Processor Interface) is a series of open standards developed by the MIPI Alliance, specifically designed for mobile devices (such as smartphones, tablets, laptops, IoT devices, automotive, etc.), featuring low power consumption, high integration, and strong anti-interference capability.

MIPI interface is not a single interface. The MIPI Alliance primarily customizes standard interfaces and specifications for mobile processors. Developed interfaces are widely used in processors, cameras, displays, baseband modems, and other devices. Common interfaces are MIPI DSI (Display Interface) and MIPI CSI (Camera Interface). This article only introduces MIPI DSI.

MIPI Interface

The MIPI DSI interface consists of data lanes and clock lanes, all differential signals. The data lanes can be configured as 1/2/3/4 lanes, and there is one pair of clock lanes, with a maximum of 10 pins. RK3568 uses 4 lanes by default to drive MIPI screens. Of course, for smaller screens, 2 lanes can also be used. For MIPI DSI interfaces, the most commonly used are 2 lanes and 4 lanes.

RK3568 has one MIPI DSI interface, so it also has one MIPI DSI host peripheral for driving MIPI DSI screens. This MIPI DSI HOST kernel complies with the MIPI protocol. MIPI DSI HOST is used to connect the kernel and D-PHY. RK3568's MIPI DSI HOST interface supports 1~4 lanes.

The features supported by RK3568's MIPI DSI HOST controller are as follows:

  • Compliant with MIPI Alliance standards
  • Supports DPI interface color mapping, with 16/18/24 bit color depth
  • All DPI interface signal polarity programmable
  • Supports up to 4 Lane D-PHY data lanes
  • Data0 supports dual-line communication and Escape mode
  • Can transmit all Generic commands
  • Supports EOTP packets

The block diagram of RK3568's MIPI DSI HOST controller is shown in the figure below:

MIPI Controller Block Diagram (For more detailed introduction or questions about the above content, please refer to the official website: https://www.mipi.org/)

1.2 HDMI Screen

HDMI stands for High Definition Multimedia Interface, which is a pure digital audio and video transmission interface that sends audio and video data simultaneously through a single cable. It is currently widely used in TVs, monitors, computers, set-top boxes, and other fields.

Rockchip's RK3568 chip has a built-in HDMI peripheral interface that can be used to connect HDMI displays. In this chapter, we will learn how to use RK3568's HDMI interface.

The HDMI block diagram is as follows:

HDMI Structure Block Diagram

The functions implemented by the several channels in the figure are:

  • TMDS: Transmit audio and video data
  • CEC: Implement remote control functionality
  • DDC: Implement screen resolution adaptation, obtain different screen parameter information through DDC
  • HPD: Implement hot-plugging

HDMI has five types of interfaces as follows:

HDMI Interface Types

The most commonly used interface type is Type A port. Our M4-R1 development board is also equipped with Type A port.

Below is an introduction to the Type A interface. The corresponding pin diagram and pin definitions are shown in the figures:

HDMI Pin Definition

RK3568 has a built-in HDMI TX peripheral that can be used to connect HDMI displays. RK3568's HDMI interface supports versions 1.4a and 2.0a, providing a convenient screen connection method for consumer electronics such as DVD players, camcorders, and cameras. RK3568's HDMI peripheral includes one HDMI transmission controller and one PHY. The features supported by RK3568 HDMI are as follows:

①、Video formats:

  • CEA-861-E standard supported video formats, 1080p@60Hz or 720p/1080i@120Hz
  • HDMI 1.4b supported video formats:
    • CEA-861-E video formats up to 1080p@120Hz
    • Supports 4K×2K
    • Supports 3D video (TMDS clock up to 340MHz)
  • Supports HDMI 2.0 video formats

②、Color support: RGB 4:4:4

③、Pixel clock: 13.5MHz-600MHz

④、Supports up to 192KHz audio sampling rate per IEC60958 standard

⑤、Supports I2C DDC, EDID block read mode

⑥、Supports up to 2160p@60Hz, RGB 4:4:4

(For more detailed introduction or questions about the above content, please refer to the official website: https://www.hdmi.org/)

1.3 eDP Screen

eDP (Embedded DisplayPort) is a digital display interface standard designed specifically for internal connections. It was developed by the Video Electronics Standards Association (VESA) to serve as the main interconnection standard between motherboards and built-in displays in laptops, tablets, all-in-one machines, and other devices. The eDP interface typically uses an FPC interface, connected to the motherboard. Laptops usually use eDP screens, and the screens also have digital microphones and cameras. The screen can also choose touch functionality.

eDP Interface

Simply put, eDP is an optimized and extended version of the DisplayPort standard in the embedded field. It inherits the high-performance characteristics of DisplayPort and has been enhanced for the space, power consumption, and cost requirements of embedded devices.

eDP Structure Diagram

eDP interface composition:

  • Main-Link (Main Channel): Used for transmitting video/audio data, composed of high-speed differential pairs (TX0~TX3), up to 4 channels (lanes), but some screens only use 2 lanes
  • AUX CH (Auxiliary Channel): Low-speed single-pair differential line (AUX+/-), used for transmitting configuration commands and parameters
  • HPD (Hot Plug Detect): Represents the hot-plug detection channel, used to detect HPD signal driven by the Sink end (screen), notifying the Source end whether a device is connected (optional)

The features supported by RK3568 eDP are as follows:

FeatureSpecification
Supported VersioneDP 1.3
Maximum Resolution2560x1600 @ 60Hz
Data Channels (Lanes)Up to 4 physical channels
Color DepthSupports up to 10bit RGB output
Auxiliary Channel (AUX)Supports AUX CH communication
Hot Plug Detect (HPD)Supports Hot Plug Detect
Panel Self Refresh (PSR)Supports Panel Self Refresh

(For more detailed introduction or questions about the above content, please refer to the official website: https://www.edp.com/zh-hans/node)

1.4 Summary

The above three display interfaces are currently the most mainstream high-performance screen interfaces. If you need to choose from the three, the biggest difference may be the interface size:

  • MIPI DSI Interface: If your device is a small device like a mobile phone screen, the compact MIPI DSI interface is recommended
  • eDP Interface: For slightly larger mobile devices like laptops, choose eDP interface screens with moderate size
  • HDMI Interface: For desktop computer monitors, TVs, and other fixed large-screen devices for personal use, HDMI, DP and other larger but high-speed interfaces are recommended

2 Three Screen Board Card Interfaces

2.1 MIPI DSI Interface

Board MIPI Interface

2.2 HDMI Interface

Board HDMI Interface

2.3 eDP Interface

Board eDP Interface

3 Screen DTS Configuration and Switching Method Introduction

3.1 Principle Introduction

Since the device trees for RK3568's three screen interfaces (MIPI DSI, HDMI, eDP) are too complex, often one peripheral involves multiple device tree files. Due to space limitations and considering that most friends are beginners, we will only analyze some board-level configuration files in this and subsequent chapters, summarizing some core content for everyone, aiming to help everyone understand these relatively complex peripheral modules. We cannot provide file addresses for everyone.

Before that, let me introduce 2 basic concepts:

1 VOP (Video Output Processor) is RK3568's video output processor, responsible for managing all display outputs. There are three video ports: vp0, vp1, and vp2.

VOP routing determines which video pipeline connects to which display interface. The specific content is as follows:

Video PortRouting ConfigurationTarget Interface
vp0vp0_out_dsi0MIPI DSI0
vp0vp0_out_dsi1MIPI DSI1
vp0vp0_out_edpeDP
vp0vp0_out_hdmiHDMI
vp1vp1_out_dsi0MIPI DSI0
vp1vp1_out_dsi1MIPI DSI1
vp1vp1_out_edpeDP
vp1vp1_out_hdmiHDMI
vp1vp1_out_lvdsLVDS
vp2vp2_out_lvdsLVDS
vp2vp2_out_rgbRGB

2 PHY (Physical Layer) is the physical layer interface, responsible for converting between digital signals and physical transmission media. Different screen interfaces require different PHY. The specific content is as follows.

PHY TypeNode NameBase AddressFunction Description
Video PHYvideo_phy00xfe850000Used for MIPI DSI interface physical layer signal processing
Video PHYvideo_phy10xfe860000Used for MIPI DSI interface physical layer signal processing
eDP PHYedp_phy0xfdcb0000Specifically used for eDP interface physical layer processing
HDMI PHYBuilt-in PHY-HDMI controller has built-in PHY function, configured via rockchip,phy-table for different frequency parameters

3.2 MIPI DTS Configuration

&dsi0 {
    status = "okay";

    dsi0_panel: panel@0 {
        compatible = "simple-panel-dsi";
        reg = <0>;
        backlight = <&backlight>;
        prepare-delay-ms = <2>;
        reset-delay-ms = <100>;
        init-delay-ms = <20>;
        enable-delay-ms = <120>;
        disable-delay-ms = <50>;
        unprepare-delay-ms = <20>;
        width-mm = <68>;
        height-mm = <121>;

        dsi,flags = <(MIPI_DSI_MODE_VIDEO | MIPI_DSI_MODE_VIDEO_BURST |
                      MIPI_DSI_MODE_LPM | MIPI_DSI_MODE_EOT_PACKET)>;
        dsi,format = <MIPI_DSI_FMT_RGB888>;
        dsi,lanes = <4>;

        pinctrl-names = "default";
        pinctrl-0 = <&mipi_power_en>;
        enable-gpios = <&gpio3 RK_PB6 GPIO_ACTIVE_HIGH>;

        panel-init-sequence = [
            05 64 01 11
            39 00 04 FF 98 81 03
            /* ... more initialization commands ... */
        ];
    };
};

&dsi0_in_vp1 {
    status = "okay";
};

&route_dsi0 {
    status = "okay";
    connect = <&vp1_out_dsi0>;
};
  • compatible = "simple-panel-dsi" : Generic DSI panel driver
  • dsi,lanes = <4> : 4-lane data transmission
  • dsi,format = <MIPI_DSI_FMT_RGB888> : RGB888 color format
  • dsi,flags : DSI working mode (video mode, burst mode, etc.)
  • enable-gpios : Panel enable GPIO control
  • panel-init-sequence : Panel initialization command sequence
  • connect = <&vp1_out_dsi0> : Connect to VOP's VP1 port

3.3 EDP DTS Configuration

&edp {
	status = "okay";
	force-hpd;

	ports {
		port@1 {
			reg = <1>;

			edp_out: endpoint {
				remote-endpoint = <&panel_in>;
			};
		};
	};
};

&route_edp {
	status = "okay";
	connect = <&vp1_out_edp>;
};

&edp_phy {
	status = "okay";
};

&edp_in_vp0 {
	status = "disabled";
};

&edp_in_vp1 {
	status = "okay";
};

&edp_panel {
	power-supply = <&vcc3v3_lcd0_n>;
};

&backlight {
	status = "okay";
	enable-gpios = <&gpio3 RK_PB5 GPIO_ACTIVE_HIGH>;
	pinctrl-names = "default";
	pinctrl-0 = <&backlight_en>;
};
  • Controller enable: status = "okay" enables the eDP controller
  • Hot plug detection: force-hpd forces hot plug detection
  • Port connection: Define output endpoint through ports node, connect to panel input
  • VOP routing: route_edp configures connection to VOP1 output (vp1_out_edp)
  • Physical layer: Enable eDP PHY (edp_phy)
  • Input endpoint: Disable VOP0 input (edp_in_vp0), enable VOP1 input (edp_in_vp1)
  • Power management: Panel power supply configured as vcc3v3_lcd0_n
  • Backlight control: Control backlight enable via GPIO3_PB5

3.4 HDMI DTS Configuration

&hdmi {
	status = "okay";
	rockchip,phy-table =
		<92812500  0x8009 0x0000 0x0270>,
		<165000000 0x800b 0x0000 0x026d>,
		<185625000 0x800b 0x0000 0x01ed>,
		<297000000 0x800b 0x0000 0x01ad>,
		<594000000 0x8029 0x0000 0x0088>,
		<000000000 0x0000 0x0000 0x0000>;
};

&hdmi_in_vp0 {
	status = "okay";
};

&hdmi_in_vp1 {
	status = "disabled";
};

&hdmi_sound {
	status = "okay";
};

&route_hdmi {
	status = "okay";
	connect = <&vp0_out_hdmi>;
};
  • Controller enable: status = "okay" enables the HDMI controller
  • PHY parameter table: rockchip,phy-table defines PHY configuration parameters for different frequencies
    • Supports frequency range from 92.8MHz to 594MHz
    • Each row contains: frequency, configuration register 1, configuration register 2, configuration register 3
  • VOP routing: Enable VOP0 input (hdmi_in_vp0), disable VOP1 input (hdmi_in_vp1)
  • Audio support: Enable HDMI audio (hdmi_sound)
  • Routing configuration: route_hdmi connects to VOP0 output (vp0_out_hdmi)

3.5 Switching Screen Display Method

Currently, M4-R1 supports MIPI0, EDP, HDMI, 3 display methods. The default display is MIPI0+HDMI simultaneous display.

To switch screen usage, modify the file out/kernel/src_tmp/linux-5.10/arch/arm64/boot/dts/rockchip/rk3568-toybrick-x0-linux.dts:

Use MIPI0:

/dts-v1/;
#include "rk3568.dtsi"
#include "rk3568-linux.dtsi"
#include "rk3568-toybrick-x0.dtsi"
#include "rk3568-toybrick-mipi-tx0-beiqicloud.dtsi"
//#include "rk3568-toybrick-mipi-tx1.dtsi"
//#include "rk3568-toybrick-edp.dtsi"

Use EDP:

/dts-v1/;
#include "rk3568.dtsi"
#include "rk3568-linux.dtsi"
#include "rk3568-toybrick-x0.dtsi"
//#include "rk3568-toybrick-mipi-tx0-beiqicloud.dtsi"
//#include "rk3568-toybrick-mipi-tx1.dtsi"
#include "rk3568-toybrick-edp.dtsi"
Edit this page on GitHub
Last Updated:
Contributors: ZSL