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.

AM335x cpufreq warnings



Hi,

I have a AM335x board with customised kernel image and DTB.  Everything worked so far and I am trying to clean up as much as I can all the 'user.warn' and 'user.err' kernel messages but I have a few below that after searching the forum, googling, etc... I couldn't get rid of... Please could someone kindly help please? I think they all related to the clocking but I am not entirely sure.

(1)

Mar 27 22:14:12 localhost user.warn kernel: cpufreq_cpu0: failed to get cpu0 regulator: -19
Mar 27 22:14:12 localhost user.err kernel: cpufreq_cpu0: Bootloader freq 550000000Hz no match to table, Using 300000000Hz

(2)

Mar 27 22:14:12 localhost user.err kernel: platform mpu.1: FIXME: clock-name 'fck' DOES NOT exist in dt!

Mar 27 22:14:12 localhost user.err kernel: platform 49000000.edma: FIXME: clock-name 'fck' DOES NOT exist in dt!

Mar 27 22:14:12 localhost user.err kernel: platform 56000000.sgx: FIXME: clock-name 'fck' DOES NOT exist in dt!

I did see someone has asked (2) before https://e2e.ti.com/support/arm/sitara_arm/f/791/t/388498

but I still don't know how to fix them... below is the section of clocks mentioned are supposed to be relevant in my DTB:

cpus {
                #address-cells = <0x1>;
                #size-cells = <0x0>;

                cpu@0 {
                        compatible = "arm,cortex-a8";
                        device_type = "cpu";
                        reg = <0x0>;
                        operating-points = <0xf4240 0x149d58 0xc3500 0x139b88 0xafc80 0x139b88 0x927c0 0x12b128 0x7a120 0x112a88 0x493e0 0x112a88 0x43238 0x112a88>;
                        voltage-tolerance = <0x2>;
                        platform-opp-modifier = <0x2>;
                        clocks = <0x3>;
                        clock-names = "cpu";
                        clock-latency = <0x493e0>;
                        cpu0-supply = <0x4>;
                };
        };

dpll_mpu_m2_ck@44e004a8 {
                        #clock-cells = <0x0>;
                        compatible = "ti,divider-clock";
                        clocks = <0x3>;
                        reg = <0x44e004a8 0x4>;
                        bit-mask = <0x1f>;
                        index-starts-at-one;
                };
l3_gclk {
                        #clock-cells = <0x0>;
                        compatible = "fixed-factor-clock";
                        clocks = <0x5d>;
                        clock-mult = <0x1>;
                        clock-div = <0x1>;
                        linux,phandle = <0x9>;
                        phandle = <0x9>;
                };

gfx_fck_div_ck@44e0052c {
                        #clock-cells = <0x0>;
                        compatible = "ti,divider-clock";
                        clocks = <0x63>;
                        reg = <0x44e0052c 0x4>;
                        table = <0x1 0x0 0x2 0x1>;
                        bit-mask = <0x1>;
                };

Many thanks in advanced.

  • Hi,

    I will forward this to the software team.
  • Please post your Linux version.
  • The customised kernel image is based on Linux version is 3.10.62
  • This is not an official TI release. This forum supports only the official Linux SDK, released by TI.
  • Biser,
    I am also quite interested in know who to resolve the error for this issue. And we are using 3.12.10 of the Kernel (that came with the 7.0 SDK).
  • Hi,

    Can you post your dts file & the defconfig file?

    Best Regards,
    Yordan
  • Yordan,

    Attached is the a zip containing the *.dts, a log of the boot up and .config.

    What we are trying to do is eliminate kernel.err that are occurring at boot up. Besides the FIXME, below, we have others.

    Jun 24 06:05:03 Node8030dc92a94c user.err kernel: [    0.087215] platform mpu.1: FIXME: clock-name 'fck' DOES NOT exist in dt!
    Jun 24 06:05:03 Node8030dc92a94c user.err kernel: [    0.088062] platform 49000000.edma: FIXME: clock-name 'fck' DOES NOT exist in dt!
    Jun 24 06:05:03 Node8030dc92a94c user.err kernel: [    0.096419] platform 56000000.sgx: FIXME: clock-name 'fck' DOES NOT exist in dt!
    Jun 24 06:05:03 Node8030dc92a94c user.err kernel: [    0.099021] DSS not supported on this SoCtmp.zip

    Jun 24 06:05:03 Node8030dc92a94c user.err kernel: [    1.179933] omap_hsmmc 481d8000.mmc: unable to get vmmc regulator -517

    Jun 24 06:05:03 Node8030dc92a94c user.err kernel: [    0.993118] mtdoops: mtd device (mtddev=name/number) must be supplied

    Jun 24 06:05:03 Node8030dc92a94c user.err kernel: [    1.351576] cpu cpu0: cpu0 regulator not ready, retry

    Jun 24 06:05:03 Node8030dc92a94c user.err kernel: 0>[    2.267032] udevd[876]: starting version 182

     

  • Hi Peter,

    The dts seems ok, just include the irq header:
    #include <dt-bindings/interrupt-controller/irq.h>

    I see that you deviate from using i2c0 to communicate with the PMIC. Make sure that the correct I2C interface is initialized (add some debug prints in the driver).

    Also just for the test, try removing the eeprom & wake-up, sleep parts from the I2C1 bus, and see if you'll get better kernel performance.

    Best Regards,
    Yordan
  • Hi Yordan,
    What is the reason for adding #include <dt-bindings/interrupt-controller/irq.h> ?
    As for the PMIC, our hardware is connected to I2C1 instead of I2C0 (as per the EVM).

    When you say "eeprom & wake-up, sleep parts from the I2C1 bus", I am not sure what you mean? Do you want us to update the I2C1bus in the DT and remove those feature? If so, I am not sure where, We also have SFP's connected to the I2C1, hence adding eeprom as a device is required so that we can use AT24 interface.

    Also, there anything else we need to do to resolve the following:

    Jun 24 06:05:03 Node8030dc92a94c user.err kernel: [ 0.087215] platform mpu.1: FIXME: clock-name 'fck' DOES NOT exist in dt!
    Jun 24 06:05:03 Node8030dc92a94c user.err kernel: [ 0.088062] platform 49000000.edma: FIXME: clock-name 'fck' DOES NOT exist in dt!
    Jun 24 06:05:03 Node8030dc92a94c user.err kernel: [ 0.096419] platform 56000000.sgx: FIXME: clock-name 'fck' DOES NOT exist in dt!
    Jun 24 06:05:03 Node8030dc92a94c user.err kernel: [ 0.099021] DSS not supported on this SoCtmp.zip

    Jun 24 06:05:03 Node8030dc92a94c user.err kernel: [ 1.179933] omap_hsmmc 481d8000.mmc: unable to get vmmc regulator -517

    Jun 24 06:05:03 Node8030dc92a94c user.err kernel: [ 0.993118] mtdoops: mtd device (mtddev=name/number) must be supplied

    Jun 24 06:05:03 Node8030dc92a94c user.err kernel: [ 1.351576] cpu cpu0: cpu0 regulator not ready, retry

    Jun 24 06:05:03 Node8030dc92a94c user.err kernel: 0>[ 2.267032] udevd[876]: starting version 182