From: Leonard Crestez <leonard.crestez@nxp.com>
To: "ulf.hansson@linaro.org" <ulf.hansson@linaro.org>,
"l.stach@pengutronix.de" <l.stach@pengutronix.de>,
Anson Huang <anson.huang@nxp.com>
Cc: "A.s. Dong" <aisheng.dong@nxp.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
dl-linux-imx <linux-imx@nxp.com>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
Fabio Estevam <fabio.estevam@nxp.com>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Robin Gong <yibin.gong@nxp.com>,
"kernel@pengutronix.de" <kernel@pengutronix.de>
Subject: Re: [PATCH v2 1/2] soc: imx: gpc: Disable 6sl display power gating for ERR006287
Date: Tue, 10 Jul 2018 13:18:00 +0000 [thread overview]
Message-ID: <8aba202031bb222d9d78f8ac272757c930aff0c5.camel@nxp.com> (raw)
In-Reply-To: <CAPDyKFoELWSiZ4cfOByziPQzqW7Tx3m29qKu9uCKPHO1gXO4YA@mail.gmail.com>
On Tue, 2018-07-10 at 00:33 +0200, Ulf Hansson wrote:
> On 9 July 2018 at 14:23, Leonard Crestez <leonard.crestez@nxp.com>
> wrote:
> > The imx6sl chip errata document describes ERR006287 like this:
> >
> > """
> > Upon resuming from power gating, the modules in the display power
> > domain
> > (eLCDIF, EPDC, PXP and SPDC) might fail to perform register reads
> > correctly.
> >
> > When the modules listed above are used, do not use power gating on
> > the
> > display power domain.
> > """
> >
> > Link: https://emea01.safelinks.protection.outlook.com/?url=https%3A
> > %2F%2Fwww.nxp.com%2Fdocs%2Fen%2Ferrata%2FIMX6SLCE.pdf%23page%3D62&a
> > mp;data=02%7C01%7Cleonard.crestez%40nxp.com%7Cdbc5b00a97c548c470320
> > 8d5e5ebfb24%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C1%7C6366677240
> > 50833256&sdata=VgYIGGTYQ0ChR%2FCEBSZJ1D1JyfJRDi96YHa%2Byt4Qr5s%
> > 3D&reserved=0
> >
> > Handle this in linux in the same way as imx6qp ERR009619: make the
> > DISP
> > domain return -EBUSY on power_off.
> >
> > Signed-off-by: Leonard Crestez <leonard.crestez@nxp.com>
> > ---
> > drivers/soc/imx/gpc.c | 10 ++++++++++
> > 1 file changed, 10 insertions(+)
> >
> > diff --git a/drivers/soc/imx/gpc.c b/drivers/soc/imx/gpc.c
> > index 526f2d02dc78..6b726dada560 100644
> > --- a/drivers/soc/imx/gpc.c
> > +++ b/drivers/soc/imx/gpc.c
> > @@ -339,30 +339,35 @@ static struct imx_pm_domain imx_gpc_domains[]
> > = {
> > };
> >
> > struct imx_gpc_dt_data {
> > int num_domains;
> > bool err009619_present;
> > + bool err006287_present;
> > };
> >
> > static const struct imx_gpc_dt_data imx6q_dt_data = {
> > .num_domains = 2,
> > .err009619_present = false,
> > + .err006287_present = false,
> > };
> >
> > static const struct imx_gpc_dt_data imx6qp_dt_data = {
> > .num_domains = 2,
> > .err009619_present = true,
> > + .err006287_present = false,
> > };
> >
> > static const struct imx_gpc_dt_data imx6sl_dt_data = {
> > .num_domains = 3,
> > .err009619_present = false,
> > + .err006287_present = true,
> > };
> >
> > static const struct imx_gpc_dt_data imx6sx_dt_data = {
> > .num_domains = 4,
> > .err009619_present = false,
> > + .err006287_present = false,
> > };
> >
> > static const struct of_device_id imx_gpc_dt_ids[] = {
> > { .compatible = "fsl,imx6q-gpc", .data = &imx6q_dt_data },
> > { .compatible = "fsl,imx6qp-gpc", .data = &imx6qp_dt_data
> > },
> > @@ -467,10 +472,15 @@ static int imx_gpc_probe(struct
> > platform_device *pdev)
> > /* Disable PU power down in normal operation if ERR009619
> > is present */
> > if (of_id_data->err009619_present)
> > imx_gpc_domains[GPC_PGC_DOMAIN_PU].flags |=
> > PGC_DOMAIN_FLAG_NO_PD;
> >
> > + /* Disable DISP power down in normal operation if ERR006287
> > is present */
> > + if (of_id_data->err006287_present)
> > + imx_gpc_domains[GPC_PGC_DOMAIN_DISPLAY].flags |=
> > + PGC_DOMAIN_FLAG_NO_PD;
> > +
>
> This looks like a use-case for an always powered on PM domain?
>
> If that's the case, GENPD_FLAG_ALWAYS_ON does the trick, but more
> efficient as it enables genpd to take a few shortcuts when trying to
> power of a PM domain.
GENPD_FLAG_ALWAYS_ON would be a reasonable here.
I searched but I've been unable to find a good reference for scenarios
where power gating DISP on 6sl is still supported. I think it should be
safe to turn off in suspend but this is only based based on old commits
from the imx internal tree.
Right now displays on imx6sl don't work at all because nothing is
inside the DISP and it gets powered off. Fixing this in the safest and
most uncontroversial way would be worthwhile, yes?
next prev parent reply other threads:[~2018-07-10 13:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-09 12:23 [PATCH v2 0/2] Fix imx6sl display power domain Leonard Crestez
2018-07-09 12:23 ` [PATCH v2 1/2] soc: imx: gpc: Disable 6sl display power gating for ERR006287 Leonard Crestez
2018-07-09 22:33 ` Ulf Hansson
2018-07-10 13:18 ` Leonard Crestez [this message]
2018-07-09 12:23 ` [PATCH v2 2/2] ARM: dts: imx6sl: Convert gpc to new bindings Leonard Crestez
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=8aba202031bb222d9d78f8ac272757c930aff0c5.camel@nxp.com \
--to=leonard.crestez@nxp.com \
--cc=aisheng.dong@nxp.com \
--cc=anson.huang@nxp.com \
--cc=fabio.estevam@nxp.com \
--cc=kernel@pengutronix.de \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=shawnguo@kernel.org \
--cc=ulf.hansson@linaro.org \
--cc=yibin.gong@nxp.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;
as well as URLs for NNTP newsgroup(s).