[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <DB3PR0402MB39160D3F0D03B968B7CBE25AF5CD0@DB3PR0402MB3916.eurprd04.prod.outlook.com>
Date: Sat, 28 Mar 2020 12:07:15 +0000
From: Anson Huang <anson.huang@....com>
To: Adam Ford <aford173@...il.com>,
arm-soc <linux-arm-kernel@...ts.infradead.org>
CC: Adam Ford-BE <aford@...conembedded.com>,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Shawn Guo <shawnguo@...nel.org>,
Sascha Hauer <s.hauer@...gutronix.de>,
Pengutronix Kernel Team <kernel@...gutronix.de>,
Fabio Estevam <festevam@...il.com>,
dl-linux-imx <linux-imx@....com>,
devicetree <devicetree@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: RE: i.MX8MN Errors on 5.6-RC7
Hi, Adam
> Subject: i.MX8MN Errors on 5.6-RC7
>
> I am getting a few errors on the i.MX8MN:
>
> [ 0.000368] Failed to get clock for /timer@...a0000
> [ 0.000380] Failed to initialize '/timer@...a0000': -22
> [ 7.203447] caam 30900000.caam: Failed to get clk 'ipg': -2
> [ 7.334741] caam 30900000.caam: Failed to request all necessary clocks
> [ 7.438651] caam: probe of 30900000.caam failed with error -2
> [ 7.854193] imx-cpufreq-dt: probe of imx-cpufreq-dt failed with error -2
>
> I was curious to know if anyone else is seeing similar errors. I already
> submitted a proposed fix for a DMA timeout (not shown here) which
> matched work already done on i.MX8MQ and i.MX8MM.
>
> I am not seeing huge differences between 8MM and 8MN in the nodes which
> address the timer, caam or imx-cpufreq-dt.
>
> If anyone has any suggestions, I'd love to try them.
Which board did you try? I just run it on i.MX8MN-EVK board, no such failure:
root@...8mnevk:~# uname -a
Linux imx8mnevk 5.6.0-rc7 #621 SMP PREEMPT Sat Mar 28 19:56:30 CST 2020 aarch64 aarch64 aarch64 GNU/Linux
root@...8mnevk:~# dmesg | grep fail
[ 0.719353] imx-sdma 302b0000.dma-controller: Direct firmware load for imx/sdma/sdma-imx7d.bin failed with error -2
[ 0.941304] calling net_failover_init+0x0/0x8 @ 1
[ 0.941310] initcall net_failover_init+0x0/0x8 returned 0 after 0 usecs
[ 1.135885] calling failover_init+0x0/0x24 @ 1
[ 1.135897] initcall failover_init+0x0/0x24 returned 0 after 6 usecs
root@...8mnevk:~#
Thanks,
Anson
Powered by blists - more mailing lists