A problem with watchdog timer

[EvgeniK45]

Hello!

 

I have a problem, when activating the watchdog timer.

It's work perfectly but on every updating polling to "dmesg"

Log files are growing!

How i can switch of this messages ?

 

Help me, please!!!! 

 

dmesg example:

 

[  503.346179] wdt_restart, write reg 0xf1c20cb0

[  507.350127] wdt_restart, write reg 0xf1c20cb0

[  511.354322] wdt_restart, write reg 0xf1c20cb0

[  513.346125] wdt_restart, write reg 0xf1c20cb0

[  517.350354] wdt_restart, write reg 0xf1c20cb0

[  521.354596] wdt_restart, write reg 0xf1c20cb0

[  525.358773] wdt_restart, write reg 0xf1c20cb0

[  529.362970] wdt_restart, write reg 0xf1c20cb0

[  533.367194] wdt_restart, write reg 0xf1c20cb0

[  537.371408] wdt_restart, write reg 0xf1c20cb0

[  541.375594] wdt_restart, write reg 0xf1c20cb0

[  543.346157] wdt_restart, write reg 0xf1c20cb0

[  547.350384] wdt_restart, write reg 0xf1c20cb0

[  551.354632] wdt_restart, write reg 0xf1c20cb0

[  553.346214] wdt_restart, write reg 0xf1c20cb0

[  557.350449] wdt_restart, write reg 0xf1c20cb0

[  561.354696] wdt_restart, write reg 0xf1c20cb0

[  565.358940] wdt_restart, write reg 0xf1c20cb0

[  569.360109] wdt_restart, write reg 0xf1c20cb0

[  573.364274] wdt_restart, write reg 0xf1c20cb0

[  577.368484] wdt_restart, write reg 0xf1c20cb0

[  581.372720] wdt_restart, write reg 0xf1c20cb0

[  583.346008] wdt_restart, write reg 0xf1c20cb0

[  587.350162] wdt_restart, write reg 0xf1c20cb0

 

 

[EvgeniK45]

Ok, I'm asked and I'm answering! 

 

I found driver source file of watchdog, and comment the line which spammed to message file.

 

Here it is: pr_info("%s, write reg 0x%08x\n", __func__, (u32)&wdt_reg->ctrl);

static int wdt_restart(void)
{
#ifdef WATCHDOG_DBG
    if(NULL == wdt_reg) {
        pr_err("%s err, line %d\n", __func__, __LINE__);
        return -1;
    }
#endif

    //pr_info("%s, write reg 0x%08x\n", __func__, (u32)&wdt_reg->ctrl);
    writel((0xA57 << 1) | (1 << 0), &wdt_reg->ctrl);
    return 0;
}

I recompiled the core and the problem solved. 

 

I hope this information will be taken into consideration when creating new system images...