From: Fabio Estevam <festevam@denx.de>
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>,
Shawn Guo <shawnguo@kernel.org>
Subject: Re: [PATCH v3] soc: imx: gpcv2: Assert reset before ungating clock
Date: Sat, 13 Aug 2022 08:38:30 -0300 [thread overview]
Message-ID: <b74e8fc8c7eb361bf3c425ef8dae8a22@denx.de> (raw)
In-Reply-To: <20220812170802.205244-1-marex@denx.de>
Hi Marek,
On 12/08/2022 14:08, Marek Vasut wrote:
> In case the power domain clock are ungated before the reset is
> asserted,
> the system might freeze completely. This is likely due to a device is
> an
> undefined state being attached to bus, which sporadically leads to a
> bus
> hang. Assert the reset before the clock are enabled to assure the
> device
> is in defined state before being attached to bus.
>
> Fixes: fe58c887fb8ca ("soc: imx: gpcv2: add support for optional
> resets")
> Signed-off-by: Marek Vasut <marex@denx.de>
Reviewed-by: Fabio Estevam <festevam@denx.de>
_______________________________________________
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:[~2022-08-13 11:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-12 17:08 [PATCH v3] soc: imx: gpcv2: Assert reset before ungating clock Marek Vasut
2022-08-13 11:38 ` Fabio Estevam [this message]
2022-08-15 7:53 ` Lucas Stach
2022-08-21 13:35 ` 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=b74e8fc8c7eb361bf3c425ef8dae8a22@denx.de \
--to=festevam@denx.de \
--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 \
--cc=shawnguo@kernel.org \
/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).