[panel-simple-dsi driver was added in 2022 but looks like a duplicate and code is buggy - removal?]

Full remove warning :

ret = of_get_drm_display_mode(panel->dev->of_node, mode, p->desc->bus_format,
change to:
ret = of_get_drm_display_mode(panel->dev->of_node, mode, (u32 *)&p->desc->bus_format,

and delete unused variable line 379,470,525

I am not familiar upstream policy and it aim is not bit-to-bit compatible with the rockchip kernel.

This patch driver make drive a dsi panel easy, so I shared this to armbian build system.I hope it help someone drive dsi panel easy.

[panel-simple-dsi driver was added in 2022 but looks like a duplicate and code is buggy - removal?]

I'm sorry about this driver has  4 warnings when I checked it,and the  bus_format  actually is bus_flags, I used the wrong name, although it not effect  use, I will fix it when I have time in the future.

This dirver is differ in upstream panel-simple-dsi, panel-simple-dsi actually contain a lot sets panel model.but this panel-dsi-simple is universal driver,you just put init code,config to dts and not need adjsut driver c code when drive a new panel model.

[nanoPC-T4: trying to enable eDP LCD display]

@Erica

I have encountered something troublesome, and I am troubled by it.
I'm afraid I don't have time to deal with this problem, so don't wait for me,I'm sorry.

[nanoPC-T4: trying to enable eDP LCD display]

@Erica

now apt system media edge is 6.2.0,current is 6.1.11,maybe you can try:

If you decide use 6.2:

apt install linux-headers-edge-media

If you decide use 6.1:

apt install linux-headers-current-media

armbian build system has some adjustments,so I am not sure it compatible your system and I am not know how find the deb.

[nanoPC-T4: trying to enable eDP LCD display]

@Erica 

It depends on linux-headers-xxx-xxx, like below:

root@MusicPI:~# dpkg -l |grep linux-headers
ii  linux-headers-edge-media             23.02.2                                   arm64        Linux kernel headers for 6.2.0-media on arm64 edge

[nanoPC-T4: trying to enable eDP LCD display]

@atonejust worked,driver in here https://github.com/iamdrq/panel-edp-friendlyelec

[nanoPC-T4: trying to enable eDP LCD display]

@EricaCould you have a look right top's message box?I known how enable overlay on nanopct4 that used media kernel.that is a little trouble.

[nanoPC-T4: trying to enable eDP LCD display]

@atoneOk,I saw that.But nanopct4 used media kernel that it use extlinux havn't overlay.

It need adjust some file in path /boot,I send mesage to Erica

[Orange Pi 4 Kernel 5.10.y MIPI DSI Panel sucessful]

@suhail

dtc /sys/firmware/fdt > now.dts

Please execute upper command then upload the now.dts file to there.

[nanoPC-T4: trying to enable eDP LCD display]

@EricaOk,let's look whether boot over extlinux

ls -alh /boot

 

[nanoPC-T4: trying to enable eDP LCD display]

@EricaPlease show me

uname -a

 

[Possible to get Jammy (5.15 kernel) to use DSI/TP display]

If you need help @ me  please else I don't recive notify and my time zone is GMT+8.

https://www.armbian.com/rockpro64/ at the bottom Rolling weekly releases has linux 6.1 image .

Of course,I suggest you use a sdcard as test first if you use emmc now.

I don't have a rockpro64, only have nanopct4 and orangepi4 as rk3399 board. But I guess it has same way that they also use rk3399.

 

1. I suppose you use linux kernel 6.x at rockpro64 and swtich user to root, create pine64-lcd.dts and put below content:

/dts-v1/;
/plugin/;

/ {
  compatible = "rockchip,rk3399";
	
  fragment@0 {
    target=<&backlight>;
    __overlay__ {
      status = "okay";
    };
  };
  
  fragment@1 {
    target=<&touch>;
    __overlay__ {
      status = "okay";
    };
  };
  
  fragment@2 {
    target=<&mipi_dsi>;
    __overlay__ {
      status = "okay";
    };
  }; 
  
  fragment@3 {
    target=<&vopl>;
    __overlay__ {
      status = "okay";
    };
  };

  fragment@4 {
    target=<&vopl_mmu>;
    __overlay__ {
      status = "okay";
    };
  };
  
  fragment@5 {
    target=<&vopb>;
    __overlay__ {
      status = "okay";
    };
  };

  fragment@6 {
    target=<&vopb_mmu>;
    __overlay__ {
      status = "okay";
    };
  };
};

 

2. exec below command, then reboot.

armbian-add-overlay pine64-lcd.dts

 

[OrangePI 4B and 10.1 MIPI DSI LCD + Touch - DTS integration]

Could you use edge kernel linux 6.1? Because it includes drivers that it doesn't need build kernel by yourself.

And which model your lcd? It marks on the lcd back board.

[Possible to get Jammy (5.15 kernel) to use DSI/TP display]

So, it worked now ?

[Possible to get Jammy (5.15 kernel) to use DSI/TP display]

Actually, this easy. Because I found main line kernel support this display panel since linux 6.0,touch https://github.com/torvalds/linux/blob/4fe89d07dcc2804c8b562f6c7896a45643d34b2f/arch/arm64/boot/dts/rockchip/rk3399-rockpro64.dtsi#L582,lcd https://github.com/torvalds/linux/blob/4fe89d07dcc2804c8b562f6c7896a45643d34b2f/arch/arm64/boot/dts/rockchip/rk3399-rockpro64.dtsi#L629

 

If use linux 5.15, you need copy upper 2 section dts and enable touch,lcd as overlay.

If use linux 6.0 and latter,you just enable touch,lcd  as overlay.

[Possible to get Jammy (5.15 kernel) to use DSI/TP display]

Are you have a worked linux image or you said a android ? Could you show me detail source code adreess you uesed ? And which you uesed dsi/ tp board detail model ?

[Possible to get Jammy (5.15 kernel) to use DSI/TP display]

A bit little trouble. in fact dsi lcd and touch pannel need dts mark device,pin, then driver matched, then load init...

[Bluetooth(AP6256) with kernel 6.0.11 dose not work?]

@Igorboard-pbp-fix-wonky-wifi-bt.patch this patch cause  bluetooth problem.

[Orange Pi 4 microphone problem]

@Jack953 Maybe asound.state problem, I opened a PR.

Fix mic for rt5651 asound.state by iamdrq · Pull Request #4331 · armbian/build (github.com)

[How use armbian-add-overlay on latest armbian 22.08]

Yes, This way very cool that can load overlay on running  system. But it reboot loosed and I hope overlay on boot 

[How use armbian-add-overlay on latest armbian 22.08]

root@nanopct4:/boot/overlay-user# armbian-add-overlay lcd-mipi-opi4.dts
Armbian is not installed properly. Missing armbian-release or armbianEnv.txt

I found 22.08 using extlinux.conf instead of the legacy set of boot.scr + text files.

That will miss overlay  function when using  extlinux ?

[Mainline VPU]

On 12/2/2021 at 2:45 PM, usual user said:

But I still don't understand why you insist to involve the 3D accelerator in the video pipeline while the VOP can scan out video formats directly.

Oh, What is the VOP ? The auto negotiation selects XvImageSink(It has a window border better than waylandsink,glimagesink) that renders video frames to a drawable (XWindow) , but I use wayland it start a xwayland do it that I think it cost something.I did some test on my device, the best way is glimagesink that 4K 30fps normal paly only around 18% cpu (but  it 's strange  that some 1080p video waylandsink better than glimagesink), and I found  this gl way also work on browser like webkit.

[Mainline VPU]

7 hours ago, usual user said:

Plays for me: video-pipeline-glimagesink.pdf

But auto negotiation selects better default: video-pipeline-autovideosink.pdf

What MESA version you are running?

  Reveal hidden contents

glxinfo -B

name of display: :0
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Panfrost (0xffffffff)
    Device: Mali-T860 (Panfrost) (0xffffffff)
    Version: 21.3.0
    Accelerated: yes
    Video memory: 3834MB
    Unified memory: yes
    Preferred profile: core (0x1)
    Max core profile version: 3.1
    Max compat profile version: 3.1
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.1
OpenGL vendor string: Panfrost
OpenGL renderer string: Mali-T860 (Panfrost)
OpenGL core profile version string: 3.1 Mesa 21.3.0
OpenGL core profile shading language version string: 1.40
OpenGL core profile context flags: (none)

OpenGL version string: 3.1 Mesa 21.3.0
OpenGL shading language version string: 1.40
OpenGL context flags: (none)

OpenGL ES profile version string: OpenGL ES 3.1 Mesa 21.3.0
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10

 

 

Big thanks for your Mesa version info. I found my version is 21.2.2 (this is latest version on my running ubuntu now). It's worked when upgraded to test version 21.3.0~rc5-1 (download from debian package system by hand) !

[Mainline VPU]

3 hours ago, usual user said:

Yes, but I prefer the video pipeline that gst-play auto negotiates because it gives me a resizeable, semitransparent window while moveing and window decorations.

 

It is probably to blame a misconfigured display pipeline of the compositor if the video pipeline is identical.
Maybe attach the video pipeline that is negotiated with this command on GNOME:

GST_DEBUG_DUMP_DOT_DIR=. gst-play-1.0 demo320x240.mp4.149ba2bb88584b89814a1c41b5feef77.mp4

For visualisation convert the dot-file by:

dot -Tpdf foo.dot > foo.pdf

 

I found this isn't video decode problem just now.

gst-launch-1.0 videotestsrc ! glimagesink -v

this test also not work.

[Mainline VPU]

3 hours ago, usual user said:

This one is playing: video-pipeline.pdf

ok. thanks. are you run it on wayland and rk3399 soc ? it's so strange why fail on my device.