You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I understand I have to sync the ExtClock, presumably 19,2 Mhz, despite being slightly too low for the 20-24Mhz range allowed for the MT9M114, is closer than the 25 Mhz that pmt_clk_1 has before atomisp is probed. I don't know how to get extclock within the 20-24Mhz range.
I somewhere read the only link-frequency for the MT9M114 is 384 Mhz for 768 Mb/sec over a single MIPI-lane. Is that correct?
Should link freq be put to 3840 by
//sensor->pll.m = 10;
//sensor->pll.n = 0;
//sensor->pll.p1 = 3;
or should we first aim for lower frequencies, for example the default HpllFreq at 2000 and the default active DFS at 400 for baytrail?
Would that fit the expected 1280*720 30p requirements?
The original Yocto DFS-tables mentioned multiple device specific frequencies:
@EasyNetDev @jwrdegoede
I understand I have to sync the ExtClock, presumably 19,2 Mhz, despite being slightly too low for the 20-24Mhz range allowed for the MT9M114, is closer than the 25 Mhz that pmt_clk_1 has before atomisp is probed. I don't know how to get extclock within the 20-24Mhz range.
I somewhere read the only link-frequency for the MT9M114 is 384 Mhz for 768 Mb/sec over a single MIPI-lane. Is that correct?
Should link freq be put to 3840 by
//sensor->pll.m = 10;
//sensor->pll.n = 0;
//sensor->pll.p1 = 3;
or should we first aim for lower frequencies, for example the default HpllFreq at 2000 and the default active DFS at 400 for baytrail?
Would that fit the expected 1280*720 30p requirements?
The original Yocto DFS-tables mentioned multiple device specific frequencies:
(from the yocto project, https://github.com/intel-aero/meta-intel-aero/blob/4ebb7cc829f57306b9895f20af8fd17987089392/recipes-kernel/linux/linux-yocto/0013-temp-atomisp-support.patch)
The text was updated successfully, but these errors were encountered: