[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOMZO5BP4fPyzDmSg+DFLRYh3QMf-8T0gqvnZn6mEMt-QqSgfw@mail.gmail.com>
Date: Thu, 8 Jun 2017 13:45:35 -0300
From: Fabio Estevam <festevam@...il.com>
To: Leonard Crestez <leonard.crestez@....com>
Cc: Shawn Guo <shawnguo@...nel.org>, Bai Ping <ping.bai@....com>,
"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.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
On Thu, Jun 8, 2017 at 1:26 PM, Leonard Crestez <leonard.crestez@....com> wrote:
> + tempmon: tempmon {
> + compatible = "fsl,imx6ul-tempmon", "fsl,imx6sx-tempmon";
> + interrupts = <GIC_SPI 49 IRQ_TYPE_LEVEL_HIGH>;
> + fsl,tempmon = <&anatop>;
> + fsl,tempmon-data = <&ocotp>;
> + clocks = <&clks IMX6UL_CLK_PLL3_USB_OTG>;
Does the IMX6UL_CLK_PLL3_USB_OTG clock really control tempmon? Please
double check.
Powered by blists - more mailing lists