From: "Xinlei Lee (李昕磊)" <Xinlei.Lee@mediatek.com>
To: "CK Hu (胡俊光)" <ck.hu@mediatek.com>,
"p.zabel@pengutronix.de" <p.zabel@pengutronix.de>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
"daniel@ffwll.ch" <daniel@ffwll.ch>,
"chunkuang.hu@kernel.org" <chunkuang.hu@kernel.org>,
"airlied@linux.ie" <airlied@linux.ie>,
"Jitao Shi (石记涛)" <jitao.shi@mediatek.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Project_Global_Chrome_Upstream_Group
<Project_Global_Chrome_Upstream_Group@mediatek.com>
Subject: Re: [PATCH] drm: mediatek: Modify dpi power on/off sequence.
Date: Wed, 9 Nov 2022 02:27:13 +0000 [thread overview]
Message-ID: <8bdbffecc932dbfd40c2ed4d0b5c8cbe0f84fe47.camel@mediatek.com> (raw)
In-Reply-To: <c59a202cd31d46286eff441c6f42ec309486f334.camel@mediatek.com>
On Tue, 2022-11-08 at 07:44 +0000, CK Hu (胡俊光) wrote:
> Hi, Xinlei:
>
> On Wed, 2022-10-12 at 15:48 +0800, xinlei.lee wrote:
> > On Mon, 2022-09-05 at 21:53 +0800, xinlei.lee@mediatek.com wrote:
> > > From: Xinlei Lee <xinlei.lee@mediatek.com>
> > >
> > > Modify dpi power on/off sequence so that the first gpio operation
> > > will take effect.
> > >
> > > Fixes: 6bd4763fd532 ("drm/mediatek: set dpi pin mode to gpio low
> > > to
> > > avoid leakage
> > > current")
> > >
> > > Signed-off-by: Xinlei Lee <xinlei.lee@mediatek.com>
> > >
> > > ---
> > > Base on the branch of Linux-next/master.
> > > Because dpi power_on/off is protected by dpi->refcount, the first
> > > time
> > > it cannot be powered on and off successfully, it will cause
> > > leakage.
> > > ---
> > > ---
> > > drivers/gpu/drm/mediatek/mtk_dpi.c | 12 ++++++------
> > > 1 file changed, 6 insertions(+), 6 deletions(-)
> > >
> > > diff --git a/drivers/gpu/drm/mediatek/mtk_dpi.c
> > > b/drivers/gpu/drm/mediatek/mtk_dpi.c
> > > index 630a4e301ef6..2ce1a39ce3bf 100644
> > > --- a/drivers/gpu/drm/mediatek/mtk_dpi.c
> > > +++ b/drivers/gpu/drm/mediatek/mtk_dpi.c
> > > @@ -462,9 +462,6 @@ static void mtk_dpi_power_off(struct mtk_dpi
> > > *dpi)
> > > if (--dpi->refcount != 0)
> > > return;
> > >
> > > - if (dpi->pinctrl && dpi->pins_gpio)
> > > - pinctrl_select_state(dpi->pinctrl, dpi->pins_gpio);
> > > -
> > > mtk_dpi_disable(dpi);
> > > clk_disable_unprepare(dpi->pixel_clk);
> > > clk_disable_unprepare(dpi->engine_clk);
> > > @@ -489,9 +486,6 @@ static int mtk_dpi_power_on(struct mtk_dpi
> > > *dpi)
> > > goto err_pixel;
> > > }
> > >
> > > - if (dpi->pinctrl && dpi->pins_dpi)
> > > - pinctrl_select_state(dpi->pinctrl, dpi->pins_dpi);
> > > -
> > > return 0;
> > >
> > > err_pixel:
> > > @@ -721,6 +715,9 @@ static void mtk_dpi_bridge_disable(struct
> > > drm_bridge *bridge)
> > > {
> > > struct mtk_dpi *dpi = bridge_to_dpi(bridge);
> > >
> > > + if (dpi->pinctrl && dpi->pins_gpio)
> > > + pinctrl_select_state(dpi->pinctrl, dpi->pins_gpio);
>
> I think this should be placed after mtk_dpi_power_off().
>
> > > +
> > > mtk_dpi_power_off(dpi);
> > > }
> > >
> > > @@ -728,6 +725,9 @@ static void mtk_dpi_bridge_enable(struct
> > > drm_bridge *bridge)
> > > {
> > > struct mtk_dpi *dpi = bridge_to_dpi(bridge);
> > >
> > > + if (dpi->pinctrl && dpi->pins_dpi)
> > > + pinctrl_select_state(dpi->pinctrl, dpi->pins_dpi);
> > > +
> > > mtk_dpi_power_on(dpi);
> > > mtk_dpi_set_display_mode(dpi, &dpi->mode);
> > > mtk_dpi_enable(dpi);
> >
> > Hi CK,
> >
> > Gentle ping for this patch, if there is anything I need to modify,
> > please kindly let me know.
> >
> > Best Regards!
> > xinlei
> >
Hi CK:
Yes, this pacth is mainly to remove the control of the pin from
dpi_power_on/off, because dpi_power_on/off is protected by refcount.
I will modify the position of the pull-down gpio in the next version.
Best Regards!
xinlei
prev parent reply other threads:[~2022-11-09 2:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-05 13:53 xinlei.lee
[not found] ` <9fe3a2381746b46bde171f01635d30da2cb93d64.camel@mediatek.com>
2022-11-08 7:44 ` CK Hu (胡俊光)
2022-11-09 2:27 ` Xinlei Lee (李昕磊) [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=8bdbffecc932dbfd40c2ed4d0b5c8cbe0f84fe47.camel@mediatek.com \
--to=xinlei.lee@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=airlied@linux.ie \
--cc=chunkuang.hu@kernel.org \
--cc=ck.hu@mediatek.com \
--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
all inboxes | Powered by JetHome®