From: CK Hu <ck.hu@mediatek.com>
To: <xinlei.lee@mediatek.com>, <chunkuang.hu@kernel.org>,
<p.zabel@pengutronix.de>, <airlied@linux.ie>, <daniel@ffwll.ch>,
<matthias.bgg@gmail.com>
Cc: <dri-devel@lists.freedesktop.org>,
<linux-mediatek@lists.infradead.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <rex-bc.chen@mediatek.com>,
<Project_Global_Chrome_Upstream_Group@mediatek.com>,
Jitao Shi <jitao.shi@mediatek.com>
Subject: Re: [2/3] drm/mediatek: Separate poweron/poweroff from enable/disable and define new funcs
Date: Thu, 24 Feb 2022 13:37:50 +0800 [thread overview]
Message-ID: <4abb07d9673fb0e602ae26de233b45471b9e62e2.camel@mediatek.com> (raw)
In-Reply-To: <1644589818-13066-3-git-send-email-xinlei.lee@mediatek.com>
Hi, Xinlei:
On Fri, 2022-02-11 at 22:30 +0800, xinlei.lee@mediatek.com wrote:
> From: Jitao Shi <jitao.shi@mediatek.com>
>
> In order to match the changes of DSI RX devices (for example,
> anx7625),
> the poweron/poweroff of dsi is extracted from enable/disable and
> defined as new funcs (pre_enable/post_disable).
Does DSI not work with anx7625 now? This patch is a bug-fix or new
feature? If this patch is a bug-fix, please add 'Fixes' tag [1].
[1]
https://www.kernel.org/doc/html/v5.16/process/submitting-patches.html
Regards,
CK
>
> Signed-off-by: Jitao Shi <jitao.shi@mediatek.com>
> Signed-off-by: Xinlei Lee <xinlei.lee@mediatek.com>
> ---
> drivers/gpu/drm/mediatek/mtk_dsi.c | 45 ++++++++++++++++++++++----
> ------------
> 1 file changed, 26 insertions(+), 19 deletions(-)
>
> diff --git a/drivers/gpu/drm/mediatek/mtk_dsi.c
> b/drivers/gpu/drm/mediatek/mtk_dsi.c
> index 6d7b66d..e47c338 100644
> --- a/drivers/gpu/drm/mediatek/mtk_dsi.c
> +++ b/drivers/gpu/drm/mediatek/mtk_dsi.c
> @@ -679,16 +679,6 @@ static void mtk_dsi_poweroff(struct mtk_dsi
> *dsi)
> if (--dsi->refcount != 0)
> return;
>
> - /*
> - * mtk_dsi_stop() and mtk_dsi_start() is asymmetric, since
> - * mtk_dsi_stop() should be called after
> mtk_drm_crtc_atomic_disable(),
> - * which needs irq for vblank, and mtk_dsi_stop() will disable
> irq.
> - * mtk_dsi_start() needs to be called in
> mtk_output_dsi_enable(),
> - * after dsi is fully set.
> - */
> - mtk_dsi_stop(dsi);
> -
> - mtk_dsi_switch_to_cmd_mode(dsi, VM_DONE_INT_FLAG, 500);
> mtk_dsi_reset_engine(dsi);
> mtk_dsi_lane0_ulp_mode_enter(dsi);
> mtk_dsi_clk_ulp_mode_enter(dsi);
> @@ -703,17 +693,9 @@ static void mtk_dsi_poweroff(struct mtk_dsi
> *dsi)
>
> static void mtk_output_dsi_enable(struct mtk_dsi *dsi)
> {
> - int ret;
> -
> if (dsi->enabled)
> return;
>
> - ret = mtk_dsi_poweron(dsi);
> - if (ret < 0) {
> - DRM_ERROR("failed to power on dsi\n");
> - return;
> - }
> -
> mtk_dsi_set_mode(dsi);
> mtk_dsi_clk_hs_mode(dsi, 1);
>
> @@ -727,7 +709,16 @@ static void mtk_output_dsi_disable(struct
> mtk_dsi *dsi)
> if (!dsi->enabled)
> return;
>
> - mtk_dsi_poweroff(dsi);
> + /*
> + * mtk_dsi_stop() and mtk_dsi_start() is asymmetric, since
> + * mtk_dsi_stop() should be called after
> mtk_drm_crtc_atomic_disable(),
> + * which needs irq for vblank, and mtk_dsi_stop() will disable
> irq.
> + * mtk_dsi_start() needs to be called in
> mtk_output_dsi_enable(),
> + * after dsi is fully set.
> + */
> + mtk_dsi_stop(dsi);
> +
> + mtk_dsi_switch_to_cmd_mode(dsi, VM_DONE_INT_FLAG, 500);
>
> dsi->enabled = false;
> }
> @@ -765,10 +756,26 @@ static void mtk_dsi_bridge_enable(struct
> drm_bridge *bridge)
> mtk_output_dsi_enable(dsi);
> }
>
> +static void mtk_dsi_bridge_pre_enable(struct drm_bridge *bridge)
> +{
> + struct mtk_dsi *dsi = bridge_to_dsi(bridge);
> +
> + mtk_dsi_poweron(dsi);
> +}
> +
> +static void mtk_dsi_bridge_post_disable(struct drm_bridge *bridge)
> +{
> + struct mtk_dsi *dsi = bridge_to_dsi(bridge);
> +
> + mtk_dsi_poweroff(dsi);
> +}
> +
> static const struct drm_bridge_funcs mtk_dsi_bridge_funcs = {
> .attach = mtk_dsi_bridge_attach,
> .disable = mtk_dsi_bridge_disable,
> .enable = mtk_dsi_bridge_enable,
> + .pre_enable = mtk_dsi_bridge_pre_enable,
> + .post_disable = mtk_dsi_bridge_post_disable,
> .mode_set = mtk_dsi_bridge_mode_set,
> };
>
next prev parent reply other threads:[~2022-02-24 5:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-11 14:30 [0/3] Cooperate with DSI RX devices to modify dsi funcs and delay mipi high to cooperate with panel sequence xinlei.lee
2022-02-11 14:30 ` [1/3] drm/mediatek: Adjust the timing of mipi signal from LP00 to LP11 xinlei.lee
2022-02-14 2:54 ` CK Hu
2022-02-11 14:30 ` [2/3] drm/mediatek: Separate poweron/poweroff from enable/disable and define new funcs xinlei.lee
2022-02-24 5:37 ` CK Hu [this message]
2022-02-11 14:30 ` [3/3] drm/mediatek: keep dsi as LP00 before dcs cmds transfer xinlei.lee
2022-02-25 2:18 ` CK Hu
2022-02-14 2:32 ` [0/3] Cooperate with DSI RX devices to modify dsi funcs and delay mipi high to cooperate with panel sequence CK Hu
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=4abb07d9673fb0e602ae26de233b45471b9e62e2.camel@mediatek.com \
--to=ck.hu@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=airlied@linux.ie \
--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 \
--cc=rex-bc.chen@mediatek.com \
--cc=xinlei.lee@mediatek.com \
/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
all inboxes | Powered by JetHome®