• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 98 subscribers
  • Views 267 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.

PROCESSOR-SDK-AM67: PROCESSOR-SDK-AM67 LVDS tidss message

kazuya
Prodigy 40 points
Part Number: PROCESSOR-SDK-AM67

Tool/software:

I am using the PROCESSOR-SDK-AM67 (09.02.00.04) environment, and I am outputting video via LVDS.

When I check the kernel log in this environment, the following logs are continuously output at a certain frequency.
Can you please explain the meaning and output conditions of these logs?

tidss 30200000.dss: tidss_encoder_atomic_check
tidss 30200000.dss: tidss_plane_atomic_check
tidss 30200000.dss: tidss_crtc_atomic_check
tidss 30200000.dss: tidss_atomic_commit_tail
tidss 30200000.dss: tidss_runtime_get
tidss 30200000.dss: tidss_plane_atomic_update
tidss 30200000.dss: tidss_crtc_atomic_flush: crtc-0 is active, doesn't need modeset, event 00000000a607cee3
tidss 30200000.dss: tidss_runtime_put

  • 0
    TI__Guru 51803 points

    Hi,

    Those are the function names that are related to enabling and checking that the display pipeline is enabled. The last tidss_runtime_put is related to Linux's PM (power management) function, specifically autosuspend. 

    Therefore:

    1. These prints come from dev_dbg() function, so debug prints are enabled in either kernel config, or within the driver source code a "#define DEBUG" was put in 
    2. Most likely, the logs continuously and periodically output related to power management

    Let me know if this answers your question.

    Regards,

    Takuma

  • 0 in reply to Takuma Fujiwara
    Prodigy 40 points

    Hi Takuma,

    The current environment has "#define DEBUG" enabled.
    In the default settings of PROCESSOR-SDK-AM67(09.02.00.04), the configuration is set for HDMI output, and these logs were not being output when using HDMI output.
    When switching the output to LVDS, these logs start getting output.

    Does the presence of power management (specifically autosuspend) output differ depending on the output method?

    When using HDMI, the following log is output at a fixed interval (tidss_runtime_put was not output):
    -tidss 30220000.dss: oldi_mode = 0 : Single output over OLDI 0.
    -tidss 30220000.dss: oldi_mode = 0 : Single output over OLDI 0.

  • 0 in reply to kazuya
    TI__Guru 51803 points

    Hi Kazuya,

    I am not finding the new oldi_mode related debug prints in the driver. Maybe you have added these logs?

    In any case, what I can say is that HDMI and LVDS will use different drivers, so different functions for PM will be used. In general, the drivers are all open source and public, so you may look through them to determine where the output is coming from.

    Regards,

    Takuma