From: Lucas Stach <l.stach@pengutronix.de> To: Adam Ford <aford173@gmail.com> Cc: Shawn Guo <shawnguo@kernel.org>, Rob Herring <robh+dt@kernel.org>, Fabio Estevam <festevam@gmail.com>, NXP Linux Team <linux-imx@nxp.com>, Frieder Schrempf <frieder.schrempf@kontron.de>, Marek Vasut <marex@denx.de>, Tim Harvey <tharvey@gateworks.com>, devicetree <devicetree@vger.kernel.org>, arm-soc <linux-arm-kernel@lists.infradead.org>, Sascha Hauer <kernel@pengutronix.de>, patchwork-lst@pengutronix.de Subject: Re: [PATCH v5 01/18] Revert "soc: imx: gpcv2: move reset assert after requesting domain power up" Date: Sun, 03 Oct 2021 21:46:34 +0200 [thread overview] Message-ID: <5bb6b455f2e055a7f99d79a9cc108a565b71bf0e.camel@pengutronix.de> (raw) In-Reply-To: <CAHCN7x+GgH5Lu-2jmVy6tcnB08Wn1=naePWEVMJ+HzZE_k9q0Q@mail.gmail.com> Hi Adam, Am Sonntag, dem 03.10.2021 um 05:43 -0500 schrieb Adam Ford: > On Fri, Oct 1, 2021 at 8:00 PM Lucas Stach <l.stach@pengutronix.de> wrote: > > > > This reverts commit a77ebdd9f553. It turns out that the VPU domain has no > > different requirements, even though the downstream ATF implementation seems > > to suggest otherwise. Powering on the domain with the reset asserted works > > fine. As the changed sequence has caused sporadic issues with the GPU > > domains, just revert the change to go back to the working sequence. > > > > Cc: <stable@vger.kernel.org> # 5.14 > > Signed-off-by: Lucas Stach <l.stach@pengutronix.de> > > Acked-by: Peng Fan <peng.fan@nxp.com> > > --- > > Lucas, > > I applied your series to the 5.14.y kernel to test with the > imx8mm-beacon board, but I found that it doesn't wake from sleep. > I'll experiment with other versions of ATF. If nobody else has this > problem, I'll assume, it's an error on my part. I've tested this series on the i.MX8MM-EVK and a custom (not yet public) i.MX8MM board and both did work as expected with both system suspend/resume and runtime power management for the display parts. I've used the upstream TF-A release v2.5. Regards, Lucas > > adam > > > drivers/soc/imx/gpcv2.c | 4 ++-- > > 1 file changed, 2 insertions(+), 2 deletions(-) > > > > diff --git a/drivers/soc/imx/gpcv2.c b/drivers/soc/imx/gpcv2.c > > index 34a9ac1f2b9b..8b7a01773aec 100644 > > --- a/drivers/soc/imx/gpcv2.c > > +++ b/drivers/soc/imx/gpcv2.c > > @@ -244,6 +244,8 @@ static int imx_pgc_power_up(struct generic_pm_domain *genpd) > > goto out_regulator_disable; > > } > > > > + reset_control_assert(domain->reset); > > + > > if (domain->bits.pxx) { > > /* request the domain to power up */ > > regmap_update_bits(domain->regmap, GPC_PU_PGC_SW_PUP_REQ, > > @@ -266,8 +268,6 @@ static int imx_pgc_power_up(struct generic_pm_domain *genpd) > > GPC_PGC_CTRL_PCR); > > } > > > > - reset_control_assert(domain->reset); > > - > > /* delay for reset to propagate */ > > udelay(5); > > > > -- > > 2.30.2 > >
WARNING: multiple messages have this Message-ID (diff)
From: Lucas Stach <l.stach@pengutronix.de> To: Adam Ford <aford173@gmail.com> Cc: Shawn Guo <shawnguo@kernel.org>, Rob Herring <robh+dt@kernel.org>, Fabio Estevam <festevam@gmail.com>, NXP Linux Team <linux-imx@nxp.com>, Frieder Schrempf <frieder.schrempf@kontron.de>, Marek Vasut <marex@denx.de>, Tim Harvey <tharvey@gateworks.com>, devicetree <devicetree@vger.kernel.org>, arm-soc <linux-arm-kernel@lists.infradead.org>, Sascha Hauer <kernel@pengutronix.de>, patchwork-lst@pengutronix.de Subject: Re: [PATCH v5 01/18] Revert "soc: imx: gpcv2: move reset assert after requesting domain power up" Date: Sun, 03 Oct 2021 21:46:34 +0200 [thread overview] Message-ID: <5bb6b455f2e055a7f99d79a9cc108a565b71bf0e.camel@pengutronix.de> (raw) In-Reply-To: <CAHCN7x+GgH5Lu-2jmVy6tcnB08Wn1=naePWEVMJ+HzZE_k9q0Q@mail.gmail.com> Hi Adam, Am Sonntag, dem 03.10.2021 um 05:43 -0500 schrieb Adam Ford: > On Fri, Oct 1, 2021 at 8:00 PM Lucas Stach <l.stach@pengutronix.de> wrote: > > > > This reverts commit a77ebdd9f553. It turns out that the VPU domain has no > > different requirements, even though the downstream ATF implementation seems > > to suggest otherwise. Powering on the domain with the reset asserted works > > fine. As the changed sequence has caused sporadic issues with the GPU > > domains, just revert the change to go back to the working sequence. > > > > Cc: <stable@vger.kernel.org> # 5.14 > > Signed-off-by: Lucas Stach <l.stach@pengutronix.de> > > Acked-by: Peng Fan <peng.fan@nxp.com> > > --- > > Lucas, > > I applied your series to the 5.14.y kernel to test with the > imx8mm-beacon board, but I found that it doesn't wake from sleep. > I'll experiment with other versions of ATF. If nobody else has this > problem, I'll assume, it's an error on my part. I've tested this series on the i.MX8MM-EVK and a custom (not yet public) i.MX8MM board and both did work as expected with both system suspend/resume and runtime power management for the display parts. I've used the upstream TF-A release v2.5. Regards, Lucas > > adam > > > drivers/soc/imx/gpcv2.c | 4 ++-- > > 1 file changed, 2 insertions(+), 2 deletions(-) > > > > diff --git a/drivers/soc/imx/gpcv2.c b/drivers/soc/imx/gpcv2.c > > index 34a9ac1f2b9b..8b7a01773aec 100644 > > --- a/drivers/soc/imx/gpcv2.c > > +++ b/drivers/soc/imx/gpcv2.c > > @@ -244,6 +244,8 @@ static int imx_pgc_power_up(struct generic_pm_domain *genpd) > > goto out_regulator_disable; > > } > > > > + reset_control_assert(domain->reset); > > + > > if (domain->bits.pxx) { > > /* request the domain to power up */ > > regmap_update_bits(domain->regmap, GPC_PU_PGC_SW_PUP_REQ, > > @@ -266,8 +268,6 @@ static int imx_pgc_power_up(struct generic_pm_domain *genpd) > > GPC_PGC_CTRL_PCR); > > } > > > > - reset_control_assert(domain->reset); > > - > > /* delay for reset to propagate */ > > udelay(5); > > > > -- > > 2.30.2 > > _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-10-03 19:46 UTC|newest] Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-02 0:59 [PATCH v5 00/18] i.MX8MM GPC improvements and BLK_CTRL driver Lucas Stach 2021-10-02 0:59 ` Lucas Stach 2021-10-02 0:59 ` [PATCH v5 01/18] Revert "soc: imx: gpcv2: move reset assert after requesting domain power up" Lucas Stach 2021-10-02 0:59 ` Lucas Stach 2021-10-03 10:43 ` Adam Ford 2021-10-03 10:43 ` Adam Ford 2021-10-03 19:46 ` Lucas Stach [this message] 2021-10-03 19:46 ` Lucas Stach 2021-10-04 0:03 ` Adam Ford 2021-10-04 0:03 ` Adam Ford 2021-10-02 0:59 ` [PATCH v5 02/18] soc: imx: gpcv2: Turn domain->pgc into bitfield Lucas Stach 2021-10-02 0:59 ` Lucas Stach 2021-10-02 0:59 ` [PATCH v5 03/18] soc: imx: gpcv2: Set both GPC_PGC_nCTRL(GPU_2D|GPU_3D) for MX8MM GPU domain Lucas Stach 2021-10-02 0:59 ` Lucas Stach 2021-10-02 0:59 ` [PATCH v5 04/18] soc: imx: gpcv2: add lockdep annotation Lucas Stach 2021-10-02 0:59 ` Lucas Stach 2021-10-02 0:59 ` [PATCH v5 05/18] soc: imx: gpcv2: add domain option to keep domain clocks enabled Lucas Stach 2021-10-02 0:59 ` Lucas Stach 2021-10-02 0:59 ` [PATCH v5 06/18] soc: imx: gpcv2: keep i.MX8M* bus " Lucas Stach 2021-10-02 0:59 ` Lucas Stach 2021-10-02 0:59 ` [PATCH v5 07/18] soc: imx: gpcv2: support system suspend/resume Lucas Stach 2021-10-02 0:59 ` Lucas Stach 2021-12-08 13:47 ` [PATCH] hack: soc: imx: gpcv2: avoid unbalanced powering off of one device Martin Kepplinger 2021-12-08 13:47 ` Martin Kepplinger 2021-12-08 14:05 ` Lucas Stach 2021-12-08 14:05 ` Lucas Stach 2021-12-22 8:12 ` Martin Kepplinger 2021-12-22 8:12 ` Martin Kepplinger 2021-10-02 0:59 ` [PATCH v5 08/18] dt-bindings: soc: add binding for i.MX8MM VPU blk-ctrl Lucas Stach 2021-10-02 0:59 ` Lucas Stach 2021-10-02 0:59 ` [PATCH v5 09/18] dt-bindings: power: imx8mm: add defines for VPU blk-ctrl domains Lucas Stach 2021-10-02 0:59 ` Lucas Stach 2021-10-02 0:59 ` [PATCH v5 10/18] soc: imx: add i.MX8M blk-ctrl driver Lucas Stach 2021-10-02 0:59 ` Lucas Stach 2021-10-02 0:59 ` [PATCH v5 11/18] dt-bindings: soc: add binding for i.MX8MM DISP blk-ctrl Lucas Stach 2021-10-02 0:59 ` Lucas Stach 2021-10-02 0:59 ` [PATCH v5 12/18] dt-bindings: power: imx8mm: add defines for DISP blk-ctrl domains Lucas Stach 2021-10-02 0:59 ` Lucas Stach 2021-10-02 0:59 ` [PATCH v5 13/18] soc: imx: imx8m-blk-ctrl: add DISP blk-ctrl Lucas Stach 2021-10-02 0:59 ` Lucas Stach 2021-10-02 0:59 ` [PATCH v5 14/18] arm64: dts: imx8mm: add GPC node Lucas Stach 2021-10-02 0:59 ` Lucas Stach 2021-10-02 0:59 ` [PATCH v5 15/18] arm64: dts: imx8mm: put USB controllers into power-domains Lucas Stach 2021-10-02 0:59 ` Lucas Stach 2021-10-02 0:59 ` [PATCH v5 16/18] arm64: dts: imx8mm: Add GPU nodes for 2D and 3D core Lucas Stach 2021-10-02 0:59 ` Lucas Stach 2021-10-02 0:59 ` [PATCH v5 17/18] arm64: dts: imx8mm: add VPU blk-ctrl Lucas Stach 2021-10-02 0:59 ` Lucas Stach 2021-10-02 0:59 ` [PATCH v5 18/18] arm64: dts: imx8mm: add DISP blk-ctrl Lucas Stach 2021-10-02 0:59 ` Lucas Stach 2021-10-05 6:40 ` [PATCH v5 00/18] i.MX8MM GPC improvements and BLK_CTRL driver Shawn Guo 2021-10-05 6:40 ` Shawn Guo
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=5bb6b455f2e055a7f99d79a9cc108a565b71bf0e.camel@pengutronix.de \ --to=l.stach@pengutronix.de \ --cc=aford173@gmail.com \ --cc=devicetree@vger.kernel.org \ --cc=festevam@gmail.com \ --cc=frieder.schrempf@kontron.de \ --cc=kernel@pengutronix.de \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-imx@nxp.com \ --cc=marex@denx.de \ --cc=patchwork-lst@pengutronix.de \ --cc=robh+dt@kernel.org \ --cc=shawnguo@kernel.org \ --cc=tharvey@gateworks.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.