From: "CK Hu (胡俊光)" <ck.hu@mediatek.com>
To: "Shuijing Li (李水静)" <Shuijing.Li@mediatek.com>,
"chunkuang.hu@kernel.org" <chunkuang.hu@kernel.org>,
"Jitao Shi (石记涛)" <jitao.shi@mediatek.com>,
"daniel@ffwll.ch" <daniel@ffwll.ch>,
"p.zabel@pengutronix.de" <p.zabel@pengutronix.de>,
"airlied@gmail.com" <airlied@gmail.com>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
"angelogioacchino.delregno@collabora.com"
<angelogioacchino.delregno@collabora.com>
Cc: "dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Project_Global_Chrome_Upstream_Group
<Project_Global_Chrome_Upstream_Group@mediatek.com>
Subject: Re: [PATCH] mediatek: dsi: Correct calculation formula of PHY Timing
Date: Wed, 20 Mar 2024 06:28:25 +0000 [thread overview]
Message-ID: <f75837894e356b072481b69e7b4745bfce90ec1c.camel@mediatek.com> (raw)
In-Reply-To: <20240315072945.19502-1-shuijing.li@mediatek.com>
Hi, Shuijing:
On Fri, 2024-03-15 at 15:29 +0800, Shuijing Li wrote:
> This patch correct calculation formula of PHY timing.
> Make actual phy timing more accurate.
Please define what is accurate and how much this patch improve. For
example, the spec define event 2 happen after event 1 and the duration
between event 1 and event 2 should be from 50us to 100us. But current
duration is 60us and is near the boundary. So this patch make the
duration to 70us so it is near the safe range.
Regards,
CK
>
> Signed-off-by: Shuijing Li <shuijing.li@mediatek.com>
> ---
> drivers/gpu/drm/mediatek/mtk_dsi.c | 33 +++++++++++++++-------------
> --
> 1 file changed, 17 insertions(+), 16 deletions(-)
>
> diff --git a/drivers/gpu/drm/mediatek/mtk_dsi.c
> b/drivers/gpu/drm/mediatek/mtk_dsi.c
> index a2fdfc8ddb15..d1bd7d671880 100644
> --- a/drivers/gpu/drm/mediatek/mtk_dsi.c
> +++ b/drivers/gpu/drm/mediatek/mtk_dsi.c
> @@ -235,22 +235,23 @@ static void mtk_dsi_phy_timconfig(struct
> mtk_dsi *dsi)
> u32 data_rate_mhz = DIV_ROUND_UP(dsi->data_rate, 1000000);
> struct mtk_phy_timing *timing = &dsi->phy_timing;
>
> - timing->lpx = (60 * data_rate_mhz / (8 * 1000)) + 1;
> - timing->da_hs_prepare = (80 * data_rate_mhz + 4 * 1000) / 8000;
> - timing->da_hs_zero = (170 * data_rate_mhz + 10 * 1000) / 8000 +
> 1 -
> - timing->da_hs_prepare;
> - timing->da_hs_trail = timing->da_hs_prepare + 1;
> -
> - timing->ta_go = 4 * timing->lpx - 2;
> - timing->ta_sure = timing->lpx + 2;
> - timing->ta_get = 4 * timing->lpx;
> - timing->da_hs_exit = 2 * timing->lpx + 1;
> -
> - timing->clk_hs_prepare = 70 * data_rate_mhz / (8 * 1000);
> - timing->clk_hs_post = timing->clk_hs_prepare + 8;
> - timing->clk_hs_trail = timing->clk_hs_prepare;
> - timing->clk_hs_zero = timing->clk_hs_trail * 4;
> - timing->clk_hs_exit = 2 * timing->clk_hs_trail;
> + timing->lpx = (80 * data_rate_mhz / (8 * 1000)) + 1;
> + timing->da_hs_prepare = (59 * data_rate_mhz + 4 * 1000) / 8000
> + 1;
> + timing->da_hs_zero = (163 * data_rate_mhz + 11 * 1000) / 8000 +
> 1 -
> + timing->da_hs_prepare;
> + timing->da_hs_trail = (78 * data_rate_mhz + 7 * 1000) / 8000 +
> 1;
> +
> + timing->ta_go = 4 * timing->lpx;
> + timing->ta_sure = 3 * timing->lpx / 2;
> + timing->ta_get = 5 * timing->lpx;
> + timing->da_hs_exit = (118 * data_rate_mhz / (8 * 1000)) + 1;
> +
> + timing->clk_hs_prepare = (57 * data_rate_mhz / (8 * 1000)) + 1;
> + timing->clk_hs_post = (65 * data_rate_mhz + 53 * 1000) / 8000 +
> 1;
> + timing->clk_hs_trail = (78 * data_rate_mhz + 7 * 1000) / 8000 +
> 1;
> + timing->clk_hs_zero = (330 * data_rate_mhz / (8 * 1000)) + 1 -
> + timing->clk_hs_prepare;
> + timing->clk_hs_exit = (118 * data_rate_mhz / (8 * 1000)) + 1;
>
> timcon0 = timing->lpx | timing->da_hs_prepare << 8 |
> timing->da_hs_zero << 16 | timing->da_hs_trail << 24;
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2024-03-20 6:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-15 7:29 [PATCH] mediatek: dsi: Correct calculation formula of PHY Timing Shuijing Li
2024-03-15 9:15 ` AngeloGioacchino Del Regno
2024-03-20 6:28 ` CK Hu (胡俊光) [this message]
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=f75837894e356b072481b69e7b4745bfce90ec1c.camel@mediatek.com \
--to=ck.hu@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=Shuijing.Li@mediatek.com \
--cc=airlied@gmail.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chunkuang.hu@kernel.org \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jitao.shi@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=p.zabel@pengutronix.de \
/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