From: Shawn Guo <shawnguo@kernel.org>
To: "Wang, Xiaolei" <xiaolei.wang@windriver.com>, l.stach@pengutronix.de
Cc: s.hauer@pengutronix.de, kernel@pengutronix.de,
festevam@gmail.com, linux-imx@nxp.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] soc: imx8m: Increase the clock enable before reading the register
Date: Fri, 11 Nov 2022 11:53:04 +0800 [thread overview]
Message-ID: <20221111035304.GL125525@dragon> (raw)
In-Reply-To: <f0e35731-07df-bd80-329f-a5ad9818e1e8@windriver.com>
On Fri, Nov 11, 2022 at 11:01:15AM +0800, Wang, Xiaolei wrote:
>
> On 11/11/2022 10:46 AM, Shawn Guo wrote:
> > CAUTION: This email comes from a non Wind River email account!
> > Do not click links or open attachments unless you recognize the sender and know the content is safe.
> >
> > On Fri, Oct 28, 2022 at 12:14:18PM +0800, Xiaolei Wang wrote:
> > > When executing kdump to start the second kernel,
> > > since IMX-OCOTP has turned off the clock, the clock
> > > needs to be re-enabled, otherwise the system will hang.
> > >
> > > Fixes: ac34de14ac30 ("Revert "soc: imx8m: change to use platform driver"")
> > Are you saying this fixes a regression caused by ac34de14ac30?
>
>
> Yes,
>
> Although there is a problem with commit 7d981405d0fd, it also solves the
> kexec kernel hang, commit 7d981405d0fd is reverted, and the kexec kernel
> hang will also be introduced, so the clock needs to be enabled when the
> kexec kernel starts.
Ok.
Lucas,
Any comments here?
Shawn
_______________________________________________
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-11-11 3:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 4:14 [PATCH] soc: imx8m: Increase the clock enable before reading the register Xiaolei Wang
2022-11-11 2:46 ` Shawn Guo
2022-11-11 3:01 ` Wang, Xiaolei
2022-11-11 3:53 ` Shawn Guo [this message]
2022-11-11 9:05 ` Lucas Stach
2022-11-14 8:20 ` 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=20221111035304.GL125525@dragon \
--to=shawnguo@kernel.org \
--cc=festevam@gmail.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=s.hauer@pengutronix.de \
--cc=xiaolei.wang@windriver.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).