From: Yongqiang Niu <yongqiang.niu@mediatek.com>
To: CK Hu <ck.hu@mediatek.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
Rob Herring <robh+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>
Cc: David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
Mark Rutland <mark.rutland@arm.com>,
<dri-devel@lists.freedesktop.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>,
Yongqiang Niu <yongqiang.niu@mediatek.com>
Subject: [PATCH v8, 5/6] drm/mediatek: add RDMA fifo size error handle
Date: Thu, 10 Dec 2020 17:07:41 +0800 [thread overview]
Message-ID: <1607591262-21736-6-git-send-email-yongqiang.niu@mediatek.com> (raw)
In-Reply-To: <1607591262-21736-1-git-send-email-yongqiang.niu@mediatek.com>
This patch add RDMA fifo size error handle
rdma fifo size will not always bigger than the calculated threshold
if that case happened, we need set fifo size as the threshold
Signed-off-by: Yongqiang Niu <yongqiang.niu@mediatek.com>
---
drivers/gpu/drm/mediatek/mtk_disp_rdma.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/gpu/drm/mediatek/mtk_disp_rdma.c b/drivers/gpu/drm/mediatek/mtk_disp_rdma.c
index 794acc5..0508392 100644
--- a/drivers/gpu/drm/mediatek/mtk_disp_rdma.c
+++ b/drivers/gpu/drm/mediatek/mtk_disp_rdma.c
@@ -151,6 +151,10 @@ static void mtk_rdma_config(struct mtk_ddp_comp *comp, unsigned int width,
* account for blanking, and with a pixel depth of 4 bytes:
*/
threshold = width * height * vrefresh * 4 * 7 / 1000000;
+
+ if (threshold > rdma_fifo_size)
+ threshold = rdma_fifo_size;
+
reg = RDMA_FIFO_UNDERFLOW_EN |
RDMA_FIFO_PSEUDO_SIZE(rdma_fifo_size) |
RDMA_OUTPUT_VALID_FIFO_THRESHOLD(threshold);
--
1.8.1.1.dirty
next prev parent reply other threads:[~2020-12-10 9:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-10 9:07 [PATCH v8, 0/6] drm/mediatek: add support for mediatek SOC MT8183 Yongqiang Niu
2020-12-10 9:07 ` [PATCH v8, 1/6] dt-bindings: mediatek: add rdma_fifo_size description for mt8183 display Yongqiang Niu
2020-12-10 15:40 ` Chun-Kuang Hu
2020-12-11 0:43 ` Yongqiang Niu
2020-12-11 14:46 ` Chun-Kuang Hu
2020-12-11 3:40 ` Rob Herring
2020-12-10 9:07 ` [PATCH v8, 2/6] dt-bindings: mediatek: add " Yongqiang Niu
2020-12-10 15:36 ` Chun-Kuang Hu
2020-12-11 3:41 ` Rob Herring
2020-12-10 9:07 ` [PATCH v8, 3/6] soc: mediatek: mmsys: add mt8183 function call for setting the routing registers Yongqiang Niu
2020-12-11 14:36 ` Chun-Kuang Hu
2020-12-10 9:07 ` [PATCH v8, 4/6] drm/mediatek: add fifo_size into rdma private data Yongqiang Niu
2020-12-10 9:07 ` Yongqiang Niu [this message]
2020-12-10 15:50 ` [PATCH v8, 5/6] drm/mediatek: add RDMA fifo size error handle Chun-Kuang Hu
2020-12-11 0:45 ` Yongqiang Niu
2020-12-14 14:54 ` Chun-Kuang Hu
2021-01-05 6:36 ` Yongqiang Niu
2021-01-05 23:09 ` Chun-Kuang Hu
2020-12-10 9:07 ` [PATCH v8, 6/6] drm/mediatek: add support for mediatek SOC MT8183 Yongqiang Niu
2020-12-17 9:03 ` Hsin-Yi Wang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1607591262-21736-6-git-send-email-yongqiang.niu@mediatek.com \
--to=yongqiang.niu@mediatek.com \
--cc=airlied@linux.ie \
--cc=ck.hu@mediatek.com \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).