From: Anatolij Gustschin <agust@denx.de>
To: u-boot@lists.denx.de
Subject: [PATCH 1/2] cpu: imx8: fix type and rate detection
Date: Fri, 22 May 2020 23:13:18 +0200 [thread overview]
Message-ID: <20200522231318.66f39ee7@crub> (raw)
In-Reply-To: <20200516203420.24409-1-agust@denx.de>
On Sat, 16 May 2020 22:34:19 +0200
Anatolij Gustschin agust at denx.de wrote:
> CPU type and rate detection is broken, for A35 cpu we get A53:
> ...
> sc_pm_get_clock_rate: resource:0 clk:2: res:3
> Could not read CPU frequency: -22
> CPU: NXP i.MX8QXP RevB A53 at 0 MHz at 47C
>
> Fixes: 55bc96f3b675 ("cpu: imx8: fix get core name and rate")
> Signed-off-by: Anatolij Gustschin <agust@denx.de>
> ---
> drivers/cpu/imx8_cpu.c | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
Applied.
--
Anatolij
prev parent reply other threads:[~2020-05-22 21:13 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
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 [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=20200522231318.66f39ee7@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