summaryrefslogtreecommitdiffstats
path: root/include/linux/soc
diff options
context:
space:
mode:
authorBibby Hsieh <bibby.hsieh@mediatek.com>2019-08-28 21:48:12 -0400
committerJassi Brar <jaswinder.singh@linaro.org>2019-09-17 01:40:05 -0400
commit6058f11870b8e6d4f5cc7b591097c00bf69a000d (patch)
tree367fe652fffa26c359f818f2d13f78b851b7120d /include/linux/soc
parent286358c444d5bcae260659bcd8a0b3bf317e9cc8 (diff)
mailbox: mediatek: cmdq: clear the event in cmdq initial flow
GCE hardware stored event information in own internal sysram, if the initial value in those sysram is not zero value it will cause a situation that gce can wait the event immediately after client ask gce to wait event but not really trigger the corresponding hardware. In order to make sure that the wait event function is exactly correct, we need to clear the sysram value in cmdq initial flow. Fixes: 623a6143a845 ("mailbox: mediatek: Add Mediatek CMDQ driver") Signed-off-by: Bibby Hsieh <bibby.hsieh@mediatek.com> Reviewed-by: CK Hu <ck.hu@mediatek.com> Reviewed-by: Matthias Brugger <matthias.bgg@gmail.com> Signed-off-by: Jassi Brar <jaswinder.singh@linaro.org>
Diffstat (limited to 'include/linux/soc')
-rw-r--r--include/linux/soc/mediatek/mtk-cmdq.h3
1 files changed, 0 insertions, 3 deletions
diff --git a/include/linux/soc/mediatek/mtk-cmdq.h b/include/linux/soc/mediatek/mtk-cmdq.h
index 54ade13a9b15..4e8899972db4 100644
--- a/include/linux/soc/mediatek/mtk-cmdq.h
+++ b/include/linux/soc/mediatek/mtk-cmdq.h
@@ -13,9 +13,6 @@
13 13
14#define CMDQ_NO_TIMEOUT 0xffffffffu 14#define CMDQ_NO_TIMEOUT 0xffffffffu
15 15
16/** cmdq event maximum */
17#define CMDQ_MAX_EVENT 0x3ff
18
19struct cmdq_pkt; 16struct cmdq_pkt;
20 17
21struct cmdq_client { 18struct cmdq_client {