On 24.08.2016 15:16, Josef wrote:
Hi,
Hi!
Your log indicates you're running on kernel v3.18. Cpufreq for Tegra124
is only implemented starting from v4.3, so you'd need to upgrade.
the CPU clock setup for the T124 on the Jetson K1 board seems to have some
problems while booting:
The clock-frequency parameter in the default device-tree config is missing:
[ 0.080472] /cpus/cpu@0 missing clock-frequency property
[ 0.085605] /cpus/cpu@1 missing clock-frequency property
[ 0.090963] /cpus/cpu@2 missing clock-frequency property
[ 0.096350] /cpus/cpu@3 missing clock-frequency property
But when you add it, the warning disappears, but the clock still seems not to be
set up correctly:
cpus {
cpu@0 {
clock-frequency = <1938000000>;
};
cpu@1 {
clock-frequency = <1938000000>;
}
...
[ 7.035525] cpufreq: cpufreq_online: CPU0: Running at unlisted freq: 696000 KHz
[ 7.042895] cpufreq: cpufreq_online: CPU0: Unlisted initial frequency changed
to: 714000 KHz
For me this looks like it is using the frequency set up by the u-boot boot
loader. This might also explain why the kernel currently needs about 8 seconds
to boot which seems to be way too much for a Cortex-A15 device.
Yes, this is normal. The device boots up with the CPUs on the PLLX clock
that runs at 696MHz. Later the cpufreq driver will switch to another
clock (which, btw, does not have 696 MHz as an operating point so you
will continue to see this message even on newer kernels.)
https://storage.kernelci.org/lsk/lsk-v3.18-16.07-133-ge8aab86f8308/arm-tegra_defconfig/lab-baylibre-seattle/boot-tegra124-jetson-tk1.html
Thanks,
Josef
Cheers,
Mikko.
--
To unsubscribe from this list: send the line "unsubscribe linux-tegra" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
