All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shawn Guo <shawnguo@kernel.org>
To: Marek Vasut <marex@denx.de>
Cc: linux-arm-kernel@lists.infradead.org,
	Frieder Schrempf <frieder.schrempf@kontron.de>,
	Lucas Stach <l.stach@pengutronix.de>,
	NXP Linux Team <linux-imx@nxp.com>, Peng Fan <peng.fan@nxp.com>
Subject: Re: [PATCH] soc: imx: gpcv2: Synchronously suspend MIX domains
Date: Sun, 21 Nov 2021 10:24:00 +0800	[thread overview]
Message-ID: <20211121022400.GE31998@dragon> (raw)
In-Reply-To: <20211016210547.171717-1-marex@denx.de>

On Sat, Oct 16, 2021 at 11:05:47PM +0200, Marek Vasut wrote:
> In case the following power domain sequence happens, iMX8M Mini always hangs:
>   gpumix:on -> gpu:on -> gpu:off -> gpu:on
> This is likely due to another quirk of the GPC block. This situation can be
> prevented by always synchronously powering off both the domain and MIX domain.
> Make it so. This turns the aforementioned sequence into:
>   gpumix:on -> gpu:on -> gpu:off -> gpumix:off -> gpumix:on -> gpu:on
> 
> Signed-off-by: Marek Vasut <marex@denx.de>
> Cc: Frieder Schrempf <frieder.schrempf@kontron.de>
> Cc: Lucas Stach <l.stach@pengutronix.de>
> Cc: NXP Linux Team <linux-imx@nxp.com>
> Cc: Peng Fan <peng.fan@nxp.com>
> Cc: Shawn Guo <shawnguo@kernel.org>

Applied, thanks.

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      parent reply	other threads:[~2021-11-21  2:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-16 21:05 [PATCH] soc: imx: gpcv2: Synchronously suspend MIX domains Marek Vasut
2021-10-17 19:40 ` Lucas Stach
2021-10-18 12:11   ` Marek Vasut
2021-11-21  2:24 ` Shawn Guo [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=20211121022400.GE31998@dragon \
    --to=shawnguo@kernel.org \
    --cc=frieder.schrempf@kontron.de \
    --cc=l.stach@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=marex@denx.de \
    --cc=peng.fan@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 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.