summaryrefslogtreecommitdiff
path: root/drivers/nvdimm
diff options
context:
space:
mode:
authorBibby Hsieh <bibby.hsieh@mediatek.com>2019-08-29 04:48:12 +0300
committerJassi Brar <jaswinder.singh@linaro.org>2019-09-17 08:40:05 +0300
commit6058f11870b8e6d4f5cc7b591097c00bf69a000d (patch)
tree367fe652fffa26c359f818f2d13f78b851b7120d /drivers/nvdimm
parent286358c444d5bcae260659bcd8a0b3bf317e9cc8 (diff)
downloadlinux-6058f11870b8e6d4f5cc7b591097c00bf69a000d.tar.xz
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 'drivers/nvdimm')
0 files changed, 0 insertions, 0 deletions