Genio 1200-demo

This page provides board-specific information on the display interfaces of the MT8395 P1V6 (Genio 1200) demo board. For common display and compositor information, please visit the Display page.

Display Interfaces on MT8395 P1V6 (Genio 1200) demo board

IoT Yocto supports three display interfaces on MT8395 P1V6 (Genio 1200) demo board:

• HDMI

• DisplayPort(DP) through USB Type-C port

• Embedded Display Port(eDP) with eDP Panel BOE NE135FBM

As of v22.2 release, the DSI0 port (LCM1) are supported on IoT Yocto.

By default rity-demo-image enables HDMI only. DP and eDP can be enabled by loading the device tree overlay during the flash programming process.

HDMI

Starting from v22.1 release HDMI is the default display interface for the prebuilt rity-demo-image for Genio 1200-demo board. The associated display data pipeline can process up to 4K(3840 x 2160) with 60Hz refresh rate.

Note

The HDMI interface is mutually exclusive to the DisplayPort interface provided by the USB Type-C port on the Genio 1200-demo board.

To restore the device tree setting back to the default device tree of the Genio 1200-demo board, flash the board with:

aiot-flash -i rity-demo-image

After boot into the console you can use modeprint mediatek command to check if the HDMI port has been properly configured:

root@i1200-demo:~# modeprint mediatek
Starting test
Resources

count_connectors : 1
count_encoders   : 1
count_crtcs      : 2
count_fbs        : 0

Connector: HDMI-A-1

DisplayPort

To enable DisplayPort, load the dtbo file display-dp.dtbo during flashing process:

aiot-flash -i rity-demo-image --load-dtbo display-dp.dtbo

If you don’t want to re-flash the entire root file system, you can simply update the overlay configuration with:

aiot-flash -i rity-demo-image --load-dtbo display-dp.dtbo kernel mmc0boot1

Note

The DisplayPort interface is mutually exclusive to the HDMI interface on the Genio 1200-demo board.

The display-dp overlay file essentially disables hdmi0 node and re-configures the audio link to display port.

root@i1200-demo:~# modeprint mediatek
Starting test
Resources

count_connectors : 1
count_encoders   : 1
count_crtcs      : 2
count_fbs        : 0

Connector: DP-1

The associated display data pipeline can process up to 4K(3840x2160) with 60Hz refresh rate.

DSI (LCM1)

Starting from v22.2 release, the DSI0 port on MT8395 driver is enabled and integrated with a BOE TV101WUM-NL6 panel for evaluation.

Hardware Setup

Follow these steps to connect the BOE TV101WUM-NL6 panel to the demo board:

• First, remove the 5V DC jack and USB-C from MT8395 Demo Board to power off the board.

• Then, connect the DSI Panel BOE TV101WUM-NL6 to the LCM1 connector on MT8395 Demo Board. You need to align the pin 40 of the cable:

  

  to the pin 40 of the LCM1 connector on the board:

  

The result should look like this:

Enable DSI Interface

The DSI0 and related device nodes are disabled by default in the board device tree in the prebuilt rity-demo-image image. To evaluate the DSI panel, you need to enable DSI0 and related device nodes by loading the following device tree overlay:

aiot-flash -i rity-demo-image --load-dtbo display-dsi.dtbo

This device tree overlay enables the DSI output interface and also the panel. Please refer to the dtbo file of the demo board. to check which nodes are enabled by the dtbo.

Please note that DSI and eDP output interfaces are mutually exclusive, i.e. these two interfaces cannot be enabled in the same device tree.

Embedded DisplayPort

Hardware Setup

The prebuilt rity-demo-image supports BOE NE135FBM panel with a eDP cable, as shown below:

Please always use this associated cable to connect to the panel. Connect the side labeled as MB to the Genio 1200-demo board, and the LCM side to the panel, as show below:

To enable Embedded DisplayPort and the BOE NE135FBM panel, load the overlay file:

aiot-flash -i rity-demo-image --load-dtbo panel-boe-ne135fbm.dtbo

If you don’t want to re-flash the entire root file system, you can simply update the overlay configuration with:

aiot-flash -i rity-demo-image --load-dtbo panel-boe-ne135fbm.dtbo kernel mmc0boot1

The associated display data pipeline can process up to 2K(2256x1504) with 60Hz refresh rate.

eDP + HDMI

The eDP port can be used simultaneously with one of the HDMI and DP port. This is because they use a different underlying display data pipeline, abstracted as different crtc in the DRM framework.

Therefore after loading the panel-boe-ne135fbm.dtbo you should see two connectors and two crtcs available:

root@i1200-demo:~# modeprint mediatek
Starting test
Resources

count_connectors : 2
count_encoders   : 2
count_crtcs      : 2
count_fbs        : 0

Connector: eDP-1
        id             : 32
        encoder id     : 31
        conn           : connected
        size           : 280x190 (mm)
        count_modes    : 2
        count_props    : 5
        props          : 1 2 5 6 4
        count_encoders : 1
        encoders       : 31
Mode: "2256x1504" 2256x1504 60
Mode: "2256x1504" 2256x1504 48
Connector: HDMI-A-1
        id             : 34
        encoder id     : 33
        conn           : connected
        size           : 520x290 (mm)
        count_modes    : 33
        count_props    : 5
        props          : 1 2 5 6 4
        count_encoders : 1
        encoders       : 33
Mode: "1920x1080" 1920x1080 60
Mode: "1920x1080" 1920x1080 60
Mode: "1920x1080" 1920x1080 50
Mode: "1600x1200" 1600x1200 60

eDP + DP

You can configure the eDP + DP combination with:

aiot-flash -i rity-demo-image --load-dtbo panel-boe-ne135fbm.dtbo --load-dtbo display-dp.dtbo

Related Kernel Source Files

• The board dts file is located in the kernel path arch/arm64/boot/dts/mediatek/mt8195-demo.dts.

• The driver for display data path and interfaces are located under the drivers/gpu/drm/mediatek, the same as other DRM drivers.

• The driver for PHY hardware are located under the drivers/phy/mediatek path, such as:

  • drivers/phy/mediatek/phy-mtk-dp.c

  • drivers/phy/mediatek/phy-mtk-hdmi-mt8195.c

• The USB Type-C associated drivers:

  • IT5205 driver are located in drivers/usb/typec/mux/it5205fn.c

  • The MT6360 driver for USB Type-C are located in drivers/usb/typec/tcpm/tcpci_mt6360.c

Please note that the support for MT8395 on IoT Yocto starts from mtk-v5.15 kernel and the Yocto kirkstone branch.

The device tree overlay files are not located in the kernel source. Instead, these overlay files are managed in the Yocto meta layer meta-mediatek-bsp’s kirkstone/recipes-kernel/dtbo/mt8195-demo directory.