[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170612153752.3b71516c@karo-electronics.de>
Date: Mon, 12 Jun 2017 15:37:52 +0200
From: Lothar Waßmann <LW@...O-electronics.de>
To: Fabio Estevam <festevam@...il.com>
Cc: Leonard Crestez <leonard.crestez@....com>,
Bai Ping <ping.bai@....com>,
"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
Shawn Guo <shawnguo@...nel.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
Eduardo Valentin <edubezval@...il.com>,
Sascha Hauer <kernel@...gutronix.de>,
Fabio Estevam <fabio.estevam@....com>,
Zhang Rui <rui.zhang@...el.com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH 2/2] ARM: dts: imx6ul: Add imx6ul-tempmon
Hi,
On Mon, 12 Jun 2017 10:22:45 -0300 Fabio Estevam wrote:
> On Mon, Jun 12, 2017 at 8:47 AM, Leonard Crestez
> <leonard.crestez@....com> wrote:
>
> > However it seems that this might be accidental, it just happens that
> > the OCOTP clock starts as enabled and is only disabled later in the
>
> Most likely because U-Boot enabled the OCOTP clock as it reads the
> speed grading fuse.
>
No, the imx6q_opp_check_speed_grading() runs on an i.MX6Q which, as
mentioned in my other mail <20170612124029.1643469d@...o-electronics.de>,
does not require any clock to be enabled for accessing the OCOTP regs.
Lothar Waßmann
Powered by blists - more mailing lists