AM625: clk_set_rate failing on TIDSS driver, SYSFW bug?

Hi,

Just to clarify, is this the issue where you don't get exact pixel clock value or you get 0 for the pixel clock? Also, are you able to replicate the issue with our latest 10.0 SDK?

Regards,
Krunal

Krunal Bhargav34 said:

Just to clarify, is this the issue where you don't get exact pixel clock value or you get 0 for the pixel clock?

You should be able to find the specific issue description in the original e2e post, as wrote there the issue if that we get a `0`.

Krunal Bhargav34 said:

Also, are you able to replicate the issue with our latest 10.0 SDK?

The issue is not systematic, I cannot really tell. However you wrote that you can replicate the issue, so the question does not seem relevant.

BTW, the issue was reported directly to TI by Tomi, as wrote in the original e2e post.