From: Anatolij Gustschin <agust@denx.de>
To: u-boot@lists.denx.de
Subject: [PATCH 2/2] thermal: imx_scu_thermal: fix getting DT alert property value
Date: Sun, 17 May 2020 13:18:28 +0200 [thread overview]
Message-ID: <20200517131828.2c3686e5@crub> (raw)
In-Reply-To: <DB6PR0402MB2760850751DBD92D8D0F432088BB0@DB6PR0402MB2760.eurprd04.prod.outlook.com>
Hi Peng,
On Sun, 17 May 2020 10:04:58 +0000
Peng Fan peng.fan at nxp.com wrote:
> Hi Anatolij,
>
> > Subject: [PATCH 2/2] thermal: imx_scu_thermal: fix getting DT alert property
> > value
> >
> > Fix boot hang with endless loop outputting:
> > CPU Temperature (47200C) has beyond alert (0C), close to critical (0C)
> > waiting...
>
> Could you share more info which part was broken?
I've tested i.MX8QXP based capricorn/giedi board (giedi_defconfig, imx8-giedi.dts)
and it was not booting:
U-Boot SPL 2020.07-rc2-00124-g515f613253 (May 16 2020 - 09:22:49 +0200)
Trying to boot from MMC1
Load image from MMC/SD 0x3ec00
U-Boot 2020.07-rc2-00124-g515f613253 (May 16 2020 - 09:22:49 +0200) ##v01.07
sc_pm_get_clock_rate: resource:0 clk:2: res:3
Could not read CPU frequency: -22
CPU Temperature (34800C) has beyond alert (0C), close to critical (0C) waiting...
CPU Temperature (35000C) has beyond alert (0C), close to critical (0C) waiting...
CPU Temperature (35000C) has beyond alert (0C), close to critical (0C) waiting...
CPU Temperature (34800C) has beyond alert (0C), close to critical (0C) waiting...
CPU Temperature (34600C) has beyond alert (0C), close to critical (0C) waiting...
CPU Temperature (35000C) has beyond alert (0C), close to critical (0C) waiting...
...
Other i.MX8QXP based boards might be broken as well.
--
Anatolij
next prev parent reply other threads:[~2020-05-17 11:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-16 20:34 [PATCH 1/2] cpu: imx8: fix type and rate detection Anatolij Gustschin
2020-05-16 20:34 ` [PATCH 2/2] thermal: imx_scu_thermal: fix getting DT alert property value Anatolij Gustschin
2020-05-17 10:04 ` Peng Fan
2020-05-17 11:18 ` Anatolij Gustschin [this message]
2020-05-17 14:43 ` Peng Fan
2020-05-17 14:53 ` Anatolij Gustschin
2020-05-19 9:35 ` Anatolij Gustschin
2020-05-19 10:05 ` Peng Fan
2020-05-19 10:26 ` Anatolij Gustschin
2020-05-19 11:45 ` Peng Fan
2020-05-19 22:05 ` Anatolij Gustschin
2020-05-19 23:37 ` Anatolij Gustschin
2020-05-18 23:32 ` Fabio Estevam
2020-05-19 4:17 ` Heiko Schocher
2020-05-19 8:47 ` Anatolij Gustschin
2020-05-19 11:57 ` Fabio Estevam
2020-05-19 8:19 ` Anatolij Gustschin
2020-05-19 23:31 ` [PATCH] cpu: imx8: use intended cpu-thermal device when getting temp value Anatolij Gustschin
2020-05-20 2:17 ` Peng Fan
2020-05-22 21:14 ` Anatolij Gustschin
2020-05-17 10:02 ` [PATCH 1/2] cpu: imx8: fix type and rate detection Peng Fan
2020-05-22 21:13 ` Anatolij Gustschin
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=20200517131828.2c3686e5@crub \
--to=agust@denx.de \
--cc=u-boot@lists.denx.de \
/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