56 lines
1.8 KiB
Plaintext
56 lines
1.8 KiB
Plaintext
|
config PRINTK_MTK
|
||
|
|
bool "mediatek printk enchange control"
|
||
|
|
depends on PRINTK
|
||
|
|
help
|
||
|
|
PRINTK_MTK which is used to control whether
|
||
|
|
to enable medaitek
|
||
|
|
printk enhcange feature
|
||
|
|
it include follow feature
|
||
|
|
|
||
|
|
config PRINTK_MTK_UART_CONSOLE
|
||
|
|
bool "Printk MTK UART controller"
|
||
|
|
depends on PRINTK_MTK
|
||
|
|
help
|
||
|
|
PRINTK_MTK_UART_CONSOLE which is used to control whether to
|
||
|
|
control printk to uart console. when boot up finish
|
||
|
|
uart console do not output printk log.
|
||
|
|
also RD can set the setting by command.
|
||
|
|
|
||
|
|
config LOG_TOO_MUCH_WARNING
|
||
|
|
bool "printk too much warning"
|
||
|
|
depends on PRINTK_MTK && MTK_ENG_BUILD && MTK_AEE_FEATURE
|
||
|
|
help
|
||
|
|
LOG_TOO_MUCH_WARNING which is used to control whether to
|
||
|
|
detect printk too much issue. kernel log too much will detect and
|
||
|
|
create a exception when printk log large than
|
||
|
|
LOG_TOO_MUCH_DETECT_COUNT in one second.
|
||
|
|
|
||
|
|
config LOG_TOO_MUCH_DETECT_COUNT
|
||
|
|
hex "printk too much detect count"
|
||
|
|
default 0xC8
|
||
|
|
depends on LOG_TOO_MUCH_WARNING
|
||
|
|
help
|
||
|
|
LOG_TOO_MUCH_DETECT_COUNT which is used to
|
||
|
|
define printk log much detect count.
|
||
|
|
the value is xxx line per second.
|
||
|
|
when log larger the level will trigger warning exception.
|
||
|
|
|
||
|
|
config LOG_TOO_MUCH_DETECT_GAP
|
||
|
|
hex "detect log too much delay time"
|
||
|
|
default 1
|
||
|
|
depends on LOG_TOO_MUCH_WARNING
|
||
|
|
help
|
||
|
|
LOG_TOO_MUCH_DETECT_GAP which is used to
|
||
|
|
define printk log much detect gap.
|
||
|
|
the value is seconds.
|
||
|
|
only after the gap seconds, the next detect can start.
|
||
|
|
|
||
|
|
config CONSOLE_LOCK_DURATION_DETECT
|
||
|
|
bool "Console lock duration detection"
|
||
|
|
depends on MTK_ENG_BUILD
|
||
|
|
help
|
||
|
|
When one cpu exec console_unlock, it may be writing to console
|
||
|
|
for long time and if log is too much. This may Trigger HWT.
|
||
|
|
We should better detect the duration in console.
|
||
|
|
and ifthe duration is over criteria, it will Report DB.
|