dmc: adding a data to identify violation stauts [1/1]
authorTao Zeng <tao.zeng@amlogic.com>
Wed, 5 Jun 2019 08:04:24 +0000 (16:04 +0800)
committerJianxin Pan <jianxin.pan@amlogic.com>
Tue, 11 Jun 2019 03:31:36 +0000 (20:31 -0700)
commite9fd8597f446d6ff8e42b8d963b6ca2ece5c3d91
treed8369329eb1fd54942c150ade4b111dec3d40a0a
parent150b354ece757063ec0fdd1474ccbcd941d5471d
dmc: adding a data to identify violation stauts [1/1]

PD#TV-5802

Problem:
irq of dmc violation happens very qiuckly, which may
have some wrong report if violation print in workqueu.

Solution:
Add a data to identify it. If data is null, then it's a
fake violation

Verify:
txhd

Change-Id: I402763fa2d20cfae3dc2d9647f7b2c2fb29ce966
Signed-off-by: Tao Zeng <tao.zeng@amlogic.com>
drivers/amlogic/ddr_tool/dmc_g12.c
drivers/amlogic/ddr_tool/dmc_gx.c
drivers/amlogic/ddr_tool/dmc_monitor.c
include/linux/amlogic/dmc_monitor.h