GLSDK 7.02.00.02

Hello Yangwoo,

According to GLSDK release notes FPDLink display is not supported.

You can try following settings to test:

Testing with FPDLink Display setup

H/W setup

• DRA7xx EVM + 12V supply for the EVM.
• FPDLink Cable between DRA7xx and De-serilzer board (DS90UB928Q).
• 5V power supply for De-serializer board.
• LCD Adapter board (DS90UH928Q) that sits on De-serializer board.
• LCD Adapter cable which is between LCD panel and the Adapter board.
• 12V power supply for LCD Adapter board.
• The actual LCD panel (LG101(10.1in) or AUO (7.1 in))
• Please refer the picture which shows the overall setup attached here

Kernel Configuration

    -> Device Drivers
      -> Graphics support
        -> OMAP2+ Display Subsystem support (OMAP2_DSS [=y])
          -> OMAP2/3 Display Device Drivers
            <*> LG101 LCD Panel
    -> Device Drivers
      -> Graphics support
        -> OMAP2+ Display Subsystem support (OMAP2_DSS [=y])
          -> OMAP2/3 Display Device Drivers
            <*> SERLINK
    -> Device Drivers
      -> Graphics support
        -> OMAP2+ Display Subsystem support (OMAP2_DSS [=y])
          -> OMAP2/3 Display Device Drivers
            <*> DSERLINK

Testing

On power-cycle, the EVM should boot and show the Tux Logo. 
Given below is a snippet from the modetest - it should show the FPDLink Display connected via the following path. The connector-id, crtc-id or plane-ids may change based on the release or kernel version.

Encoders:
id      crtc    type    possible crtcs  possible clones
3       10      TMDS    0x00000003      0x00000000
11      14      TMDS    0x00000002      0x00000000 ---------------------------> FPDLink

Connectors:
id      encoder status          type    size (mm)       modes   encoders
4       3       connected       unknown 0x0             1       3
  modes:
        name refresh (Hz) hdisp hss hse htot vdisp vss vse vtot)
  800x480 60 800 841 890 931 480 493 497 526 flags: nhsync, nvsync; type: preferred, driver
  props:
        1 EDID:
                flags: immutable blob
                blobs:

                value:  2 DPMS:
                flags: enum
                enums: On=0 Standby=1 Suspend=2 Off=3
                value: 0
12      11      connected       unknown 0x0             1       11 -----------> FPDLink
  modes:
        name refresh (Hz) hdisp hss hse htot vdisp vss vse vtot)
  1280x800 57 1280 1312 1360 1440 800 804 807 814 flags: nhsync, nvsync; type: preferred, driver
  props:
        1 EDID:
                flags: immutable blob
                blobs:

                value:  2 DPMS:
                flags: enum
                enums: On=0 Standby=1 Suspend=2 Off=3
                value: 0


About your last question, take a look in GLSDK Software developer's guide:

Wayland/Weston

Starting from GLSDK 6.04, the supported Wayland/Weston version brings in the multiple display support in extended desktop mode and the ability to drag-and-drop windows from one display to the other.

To execute the demos, the graphics driver must be initialized by running pvrsrvinit if this has not been done earlier.

  target # pvrsrvinit

To launch weston, do the following:

On default display (LCD):

  target # weston --tty=1 --connector=4

On secondary display (HDMI):

  target # weston --tty=1 --connector=16

On the third display (FPD link):

  target # weston --tty=1 --connector=21

On all connected displays (LCD, HDMI and FPDLink):

  target # weston --tty=1

By default, the screensaver timeout is configured to 300 seconds. 

The user can change the screensaver timeout using a command line option

 --idle-time=<number of seconds>

For example, to set timeout of 10 minutes and weston configured to display on all connectors, use the below command:

 weston --tty=1 --idle-time=600

To disable the screen timeout and to configure weston configured to display on all connectors, use the below command:

 weston --tty=1 --idle-time=0

Best regards,
Yanko

Hello Yanko

Thank you for your answer.

I had already tried all that you have suggested
Below is my result
For this test I removed hdmi driver from kernel config for clarity of ser/des display

<TEST1>
Enable two serdes display with kernel config change
- config DRM_OMAP_NUM_CRTCS = 2
- connector4 = serdes display1,  connector16 = serdes display2
A. $ weston --tty=1  // pass, I can see weston background on both two display
B. $ weston --tty=1 --connector=4 // pass
C. $ weston --tty=1 --connector=4 // pass
D. $ fliptest -s 4:1280x720   // pass
E. $ fliptest -s 16:1280x720 // pass

<TEST2>
Enable three serdes display with kernel config change
- config DRM_OMAP_NUM_CRTCS = 3
- connector4 = serdes display1, connector16 = serdes display2, connector20 = serdes display3
A. $ weston --tty=1  // Fail, log is printed constantly with "VBlank is pending for connector = 16 " and I can't not see any display drawing
B. $ weston --tty=1 --connector=4      //pass
C. $ weston --tty=1 --connector=16    //pass
D. $ weston --tty=1 --connector=20    //fail, blank screen showing
F. $ fliptest -s 4:1280x720   //pass
G. $ fliptest -s 16:1280x720 //pass
H. $ fliptest -s 20:1280x720 //pass

My focusing is... more the three display out on weston. I don't what I missed in this test..
Could you check if it is possible to display more then 3 display on weston?

Thank you