• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 99 subscribers
  • Views 2313 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

DRA745: How to change connector and crtc ID in DRM in processor SDK (kernel 4.4)

Dong Yang
Expert 5210 points
Part Number: DRA745

Dear expert, 

I would like to know on how to change connector and crtc ID in DRM in processor SDK (kernel 4.4).  The connector and crtc id was changed in kernel 4.4 comparing to 3.14.  Customer would like to keep the same connector and crtc id as 3.14. 

Regards

Dong

  • 0
    TI__Expert 4885 points
    Hi, Dong,

    Your question has been forwarded for an answer to expert.

    Regards,
    Mariya
  • 0 in reply to Mariya Petkova
    TI__Expert 5970 points
    Dong,

    The connector ID's are picked by kernel at runtime. There is no way to force them. The recommended way is to iterate over connectors and pick the connector id based on the name.

    regards,
    Venkat
  • 0 in reply to Venkat Mandela
    TI__Expert 5210 points

    Venkat,

    How to identify the two connector as the two connectors' name is  "unknown" as below? 

    >> The recommended way is to iterate over connectors and pick the connector id based on the name.

    Regards

    Dong

    Here is result for modetest in Linux 3.14

    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)
  960x1280 59 960 990 991 1020 1280 1300 1301 1320 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
16     15     connected        unknown         0x0            1       15
  modes:
         name refresh (Hz) hdisp hss hse htot vdisp vss vse vtot)
  800x480 30 800 810 822 832 480 490 518 528 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

     

  • 0 in reply to Dong Yang
    TI__Expert 5970 points
    Dong,

    I see a different output on K4.4 and K3.14. The LCD connector is shown an unknown and the HDMI connector is correctly identified. Below is the edited output of "modetest -c".

    K4.4
    Connectors:
    id encoder status name size (mm) modes encoders
    32 31 connected unknown-1 0x0 1 31
    36 0 connected HDMI-A-1 1600x900 22 35

    K3.14
    Connectors:
    id encoder status type size (mm) modes encoders
    4 3 connected unknown 0x0 1 3
    16 0 connected HDMI-A 1600x900 22 15

    You can look at

    github.com/.../connector.cpp

    where the connectors are being identified based on connector type. My original mail incorrectly mentioned this as connector name.

    In the log that you shared, are both connectors LCD's? I see that both connector types are shown as unknown. In that case, you may have to look at the connector resolution to identify the display.

    regards,
    Venkat