[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHCN7xJSKH-gXA5ncFS3h6_2R28rn70O3HfT=ActS1XVgCFSeg@mail.gmail.com>
Date: Fri, 27 Mar 2020 21:49:48 -0500
From: Adam Ford <aford173@...il.com>
To: arm-soc <linux-arm-kernel@...ts.infradead.org>
Cc: Adam Ford-BE <aford@...conembedded.com>,
Adam Ford <aford173@...il.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>,
NXP Linux Team <linux-imx@....com>,
Anson Huang <Anson.Huang@....com>,
devicetree <devicetree@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
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.
adam
Powered by blists - more mailing lists