Firefly Open Source Community

   Login   |   Register   |
New_Topic
12
New Topic
Print Previous Topic Next Topic

RK3399 DisplaPort no 4K resolution

28

Credits

0

Prestige

0

Contribution

new registration

Rank: 1

Credits
28

RK3399 DisplaPort no 4K resolution

Posted at 3/22/2018 18:16:39      View:13762 | Replies:12        Print      Only Author   [Copy Link] 1#
Last edited by fl0wtec In 3/23/2018 07:51 Editor

Hi,

the RK3399 has an USB-C/DP port.

Android reports max. resolution of 1920 x 1200 @ 60 Hz.

How to enable UHD/4K 3849 x 2160 @ 60Hz via DisplayPort on RK3399?

Thanks
fl0wtec
Reply

Use props Report

792

Credits

10

Prestige

10

Contribution

advanced

Rank: 4

Credits
792
Posted at 3/23/2018 16:41:34        Only Author  2#
Have you try Android7.1.2 ?
Reply

Use props Report

28

Credits

0

Prestige

0

Contribution

new registration

Rank: 1

Credits
28
Posted at 3/24/2018 02:17:19        Only Author  3#
Last edited by fl0wtec In 3/24/2018 02:18 Editor

Hi,
can you please post a link where I can get Androi 7.1.2 Firmware image for RK3399?

Google drive only lists 7.1.1:



Thanks
fl0wtec
Reply

Use props Report

792

Credits

10

Prestige

10

Contribution

advanced

Rank: 4

Credits
792
Posted at 3/24/2018 09:09:07        Only Author  4#
fl0wtec Posted at 3/24/2018 02:17
Hi,
can you please post a link where I can get Androi 7.1.2 Firmware image for RK3399?

http://en.t-firefly.com/doc/download/index/id/3.html
Reply

Use props Report

28

Credits

0

Prestige

0

Contribution

new registration

Rank: 1

Credits
28
Posted at 3/24/2018 16:40:11        Only Author  5#
Last edited by fl0wtec In 3/24/2018 16:43 Editor

Hi,

with Firefly-RK3399_Android7.1.2_MP_180126 image it gets even worse.
Nothing to choose from anymore:




Auto defaults to 1920 x 1080 @60Hz:



Can you please enable DP output with 3840 x 2160@60Hz?

Thanks
BR
fl0wtec
Reply

Use props Report

792

Credits

10

Prestige

10

Contribution

advanced

Rank: 4

Credits
792
Posted at 3/26/2018 09:18:08        Only Author  6#
fl0wtec Posted at 3/24/2018 16:40
Hi,

with Firefly-RK3399_Android7.1.2_MP_180126 image it gets even worse.

need to modify  dts file and complie your kernel and resource.
make the DP connector support vopb.
patch below

&hdmi_in_vopb {
        status = "okay";
};
&hdmi_in_vopl {
        status = "disabled";
};

&dp_in_vopb {
    status = "okay";
};

&dp_in_vopl {
    status = "okay";
};
Reply

Use props Report

40

Credits

0

Prestige

0

Contribution

new registration

Rank: 1

Credits
40
Posted at 3/30/2018 23:30:09        Only Author  7#
leung先森 Posted at 3/26/2018 09:18
need to modify  dts file and complie your kernel and resource.
make the DP connector support vopb ...

not work
Reply

Use props Report

28

Credits

0

Prestige

0

Contribution

new registration

Rank: 1

Credits
28
Posted at 3/31/2018 00:56:36        Only Author  8#
Dear leung先森,

can you please be more specific and tell us which .dts file exactly needs to be modified?

Can you please provide an image where DP output is enabled with 3840 x 2160@60Hz?

Thanks!
BR
fl0wtec
Reply

Use props Report

792

Credits

10

Prestige

10

Contribution

advanced

Rank: 4

Credits
792
Posted at 4/2/2018 10:32:14        Only Author  9#
fl0wtec Posted at 3/31/2018 00:56
Dear leung先森,

can you please be more specific and tell us which .dts file exactly needs to be m ...

kernel/arch/arm64/boot/dts/rockchip/rk3399-firefly.dts
complie it and flash resource.img and kernel.img
Reply

Use props Report

8

Credits

0

Prestige

0

Contribution

new registration

Rank: 1

Credits
8
Posted at 4/3/2018 17:11:51        Only Author  10#

RE: RK3399 DisplaPort no 4K resolution

Last edited by Markie In 4/4/2018 14:23 Editor

Dear all,

additional info below (edit 2018-04-04)

I too try to get a DisplayPort 4K monitor  (AOC U2879VF) working, however no success yet.
I have modified the DTS-file accordingly, and I see a couple of things:

1) 'dumpsys SurfaceFlinger' shows 2 displays: "Built-in screen" and "HDMI screen". The latter is the the DisplayPort 4K monitor. The naming is hardcoded in the Android source, and reading the EDID shows it is the correct monitor (and I have no display connected via HDMI). Only one monitor via HDMI shows only "Built-in screen". I don't think this is an issue, as Android tries to clone to each video output.

2) I guess the VOP_LITTLE seems to be selected for DisplayPort output (and not the VOP_BIG), as the current mode is 2560x1440@60p and the modes list does not contain above this (also not 3840x2160p60), while the monitor is capable.
  1. $cat /sys/devices/platform/display-subsystem/drm/card0/card0-DP-1/modes
  2. 2560x1440p60
  3. 1920x1080p60
  4. 1920x1080p60
  5. 1920x1080p60
  6. ...
Copy the code
3) Although the monitor should accept 2560x1440@60p, there is no image on the monitor and I get the following dmesg/console-output when connecting the monitor:
  1. [   13.220928] fusb302 4-0022: attention, dp_status a
  2. [   13.227559] cdn-dp fec00000.dp: [drm:cdn_dp_pd_event_work] Connected without sink. Assert hpd
  3. [   13.287002] cdn-dp fec00000.dp: [drm:cdn_dp_pd_event_work] Connected, not enabled. Enabling cdn
  4. [   14.239036] fusb302 4-0022: attention, dp_status 8a
  5. [   14.241816] cdn-dp fec00000.dp: [drm:cdn_dp_pd_event_work] Connected with sink. Re-train link
  6. [   57.438951] fusb302 4-0022: attention, dp_status 18a
  7. [   57.444952] cdn-dp fec00000.dp: [drm:cdn_dp_pd_event_work] Connected with sink. Re-train link
  8. [   69.396299] fusb302 4-0022: attention, dp_status 18a
  9. [   69.402256] cdn-dp fec00000.dp: [drm:cdn_dp_pd_event_work] Connected with sink. Re-train link
  10. [   71.460755] fusb302 4-0022: attention, dp_status 18a
  11. [   71.467507] cdn-dp fec00000.dp: [drm:cdn_dp_pd_event_work] Connected with sink. Re-train link
  12. [   72.984966] fusb302 4-0022: attention, dp_status 18a
  13. [   72.992195] cdn-dp fec00000.dp: [drm:cdn_dp_pd_event_work] Connected with sink. Re-train link
  14. [   96.583813] fusb302 4-0022: attention, dp_status a
  15. [   96.591843] cdn-dp fec00000.dp: [drm:cdn_dp_pd_event_work] Connected with sink. Re-train link
  16. [   97.572369] fusb302 4-0022: attention, dp_status 8a
  17. [   97.579922] cdn-dp fec00000.dp: [drm:cdn_dp_pd_event_work] Connected with sink. Re-train link
  18. [  138.177425] fusb302 4-0022: attention, dp_status 18a
  19. [  138.185544] cdn-dp fec00000.dp: [drm:cdn_dp_pd_event_work] Connected with sink. Re-train link
Copy the code
Resulting in some questions:
1) How can I verify which VOP is "used" for which display?
2) How to make sure VOP_BIG is "used"?
3) Do you have any information about this "dp_status 18a"? Maybe to suspect the monitor ...

additional info: I see a difference between boards, as I have boards with different production dates/stickers
- one board with production date 2017-08-22: see above observations
- one board with production date 2018-03-29: works out of the box! (although only 2560x1440@60p, and not yet 3840x2160@60p)
I don't know whether there is a hardware change, or it is subject to hardware component variations, ...

Thanks in advance,
With kind regards, Mark
Reply

Use props Report

Return to List
12
You need to log in before you can reply Login | Register

This forum Credits Rules

Quick Reply Back to top Back to list